가치분석을 통한 휘처 기반의 요구사항 추적 기법

다국어 초록 (Multilingual Abstract)

Traceability links are logical links between individual requirements and other system elements such as architecture descriptions, source code, and test cases. These are useful for requirements change impact analysis, requirements conflict analysis, and requirements consistency checking. However, establishing and maintaining traceability links places a big burden since complex systems have especially yield an enormous number of various artifacts. We propose a feature-oriented requirements tracing method to manage requirements with cost?benefit analysis, including value consideration and intermediate catalysis using features. Our approach offers two contributions to the study of requirements tracing: (1)We introduce feature modeling as intermediate catalysis to generate traceability links between user requirements and implementation artifacts. (2)We provide value consideration with cost and efforts to identify traceability links based on prioritized requirements, thus assigning a granularity level to each feature. In this paper, we especially present the results of a case study which is carried out in Apartment Ubiquitous Platform to integrate and connect home services in an apartment complex in details.

참고문헌 (Reference)

1 "？The Missing Link in Requirements Engineering？" 30-39, 1993

2 "？An Incremental Integration Tool between Requirements Engineering and Programming in the Large？ Proceedings of the IEEE International Symposium on Requirements Engineering" 4 82-6 89, 1993

3 "？A Constraint Programming Language for Life-cycle Engineering？ Artificial Intelligence in Engineering" 206-220, 1990

4 "Value-based Software Engineering" 2005

5 "Towards Value-Based Requirements Traceability" Chicago Illinois 2005

6 "Supporting Evolutionary Development by Feature Models and Traceability Links" 370-377, May.2004

7 "Software Requirements 2/E" Microsoft Press 2003

8 "IEE Colloquium on Tools and Techniques for Maintaining Traceability during Design" 2-, 1991

9 "Concepts and Guidelines of Feature Modeling for Product Line Software Engineering" 2319 : 62-77, 2002

10 "An Object-Oriented Tool for Tracing Requirements" 52-64, 1996

11 "A Scenario-Driven Approach to Traceability" Toronto, Canada 123-132, May.2001

12 "A Feature-Oriented Reuse Method with Domain-Specific Reference Architectures？" 143-168, 1998

13 "A Case Study on Value-based Requirements Tracing" 60-69, 2005