메뉴 건너뛰기




Volumn , Issue , 2005, Pages 60-69

A case study on value-based requirements tracing

Author keywords

Case study; Empirical evaluation; Requirements tracing; Value based software engineering

Indexed keywords

COMPLEXATION; ECONOMIC AND SOCIAL EFFECTS; PARAMETER ESTIMATION; PROCESS CONTROL; PROJECT MANAGEMENT;

EID: 32344447956     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1081706.1081717     Document Type: Conference Paper
Times cited : (76)

References (22)
  • 1
    • 3042605483 scopus 로고    scopus 로고
    • Value-based software engineering
    • March
    • B. Boehm, "Value-Based Software Engineering", ACM Software Engineering Notes, 28(2), March 2003
    • (2003) ACM Software Engineering Notes , vol.28 , Issue.2
    • Boehm, B.1
  • 2
    • 0037341431 scopus 로고    scopus 로고
    • Value-based software engineering: A case study
    • B. Boehm, L.G. Huang, "Value-Based Software Engineering: A Case Study", IEEE Computer, 36(3), 33-41, 2003
    • (2003) IEEE Computer , vol.36 , Issue.3 , pp. 33-41
    • Boehm, B.1    Huang, L.G.2
  • 3
    • 0025508474 scopus 로고
    • A constraint programming language for life-cycle engineering
    • J. Bowen, P. O'Grady, L. Smith, "A Constraint Programming Language for Life-cycle Engineering", Artificial Intelligence in Engineering, vol. 5, no. 4, pp. 206-220, 1990
    • (1990) Artificial Intelligence in Engineering , vol.5 , Issue.4 , pp. 206-220
    • Bowen, J.1    O'Grady, P.2    Smith, L.3
  • 5
    • 0037328519 scopus 로고    scopus 로고
    • A scenario-driven approach to trace dependency analysis
    • A. Egyed, "A Scenario-Driven Approach to Trace Dependency Analysis", IEEE Transactions on Software Engineering, 2003, pp. 116-132
    • (2003) IEEE Transactions on Software Engineering , pp. 116-132
    • Egyed, A.1
  • 9
    • 32344441946 scopus 로고    scopus 로고
    • Reconciling software requirements and architectures with intermediate models
    • Springer, ISSN: 1619-1366
    • P. Grünbacher, A. Egyed, N. Medvidovic, "Reconciling Software Requirements and Architectures with Intermediate Models", Software and System Modeling (So-SyM), Vol. 3, no. 3, Springer, pp. 235-253, 2004, ISSN: 1619-1366
    • (2004) Software and System Modeling (So-SyM) , vol.3 , Issue.3 , pp. 235-253
    • Grünbacher, P.1    Egyed, A.2    Medvidovic, N.3
  • 13
    • 0142130178 scopus 로고
    • The missing link in requirements engineering
    • H. Kaindl, "The Missing Link in Requirements Engineering", ACM SigSoft Software Engineering Notes, vol. 18, no. 2, pp. 30-39, 1993
    • (1993) ACM SigSoft Software Engineering Notes , vol.18 , Issue.2 , pp. 30-39
    • Kaindl, H.1
  • 15
    • 79952243801 scopus 로고
    • An incremental integration tool between requirements engineering and programming in the large
    • San Diego, California, Jan. 4-6
    • M. Lefering, "An Incremental Integration Tool between Requirements Engineering and Programming in the Large", Proceedings of the IEEE International Symposium on Requirements Engineering, San Diego, California, Jan. 4-6, pp. 82-89, 1993
    • (1993) Proceedings of the IEEE International Symposium on Requirements Engineering , pp. 82-89
    • Lefering, M.1
  • 17
    • 0003748765 scopus 로고
    • "Capability Maturity Model for Software", Version 1.1
    • CMU-SEI-93-TR-024, February
    • M.C. Paulk, B. Curtis, M.B. Chrissis, C.V. Weber, "Capability Maturity Model for Software", Version 1.1, Technical Report, CMU-SEI-93-TR-024, February 1993
    • (1993) Technical Report
    • Paulk, M.C.1    Curtis, B.2    Chrissis, M.B.3    Weber, C.V.4
  • 18
    • 0030105847 scopus 로고    scopus 로고
    • An object-oriented tool for tracing requirements
    • F.A.C. Pinheiro, J. A.Goguen, "An Object-Oriented Tool for Tracing Requirements". IEEE Software 13(2), 1996, 52-64.
    • (1996) IEEE Software , vol.13 , Issue.2 , pp. 52-64
    • Pinheiro, F.A.C.1    Goguen, J.A.2
  • 20
    • 0035107781 scopus 로고    scopus 로고
    • Toward reference models for requirements traceability
    • January
    • B. Ramesh, M. Jarke, "Toward Reference Models for Requirements Traceability", IEEE Transactions on Software Engineering, Vol. 27, No. 1, pp. 58-93, January 2001
    • (2001) IEEE Transactions on Software Engineering , vol.27 , Issue.1 , pp. 58-93
    • Ramesh, B.1    Jarke, M.2
  • 22
    • 0013459568 scopus 로고
    • Why and how of requirements tracing
    • July
    • R. Watkins, M. Neal, "Why and how of Requirements Tracing", IEEE Software, vol. 11, no. 7, pp. 104-106, July 1994
    • (1994) IEEE Software , vol.11 , Issue.7 , pp. 104-106
    • Watkins, R.1    Neal, M.2


* 이 정보는 Elsevier사의 SCOPUS DB에서 KISTI가 분석하여 추출한 것입니다.