Browse > Article
http://dx.doi.org/10.3745/KIPSTD.2010.17D.4.271

A Study of Requirement Change Management and Traceability Effect Using Traceability Table  

Kim, Ju-Young (대림산업 정보시스템실)
Rhew, Sung-Yul (숭실대학교 컴퓨터학부)
Hwang, Man-Su (신흥대학 컴퓨터정보계열)
Abstract
Insufficient requirement management accounts for 54% ofunsuccessful software development projects and 22% of insufficient requirement management comes from requirement change management. Hence, requirement management activities are important to reduce failure rates and a tracing method is suggested as the major factor in requirements change management. A traceability table is easy to use because of its legibility accurate tracing. However, traceability tables of existing studies have failed to concretely suggest method of change management and effect of traceability. Also, studies of methods to estimate change impact is complex. Hence, this study suggests how to use a traceability table to manage changes in requirements. Together, in comparison to existing studies, this study suggests easier methods to estimate change rate and change impact. Also Fifteen projects were sampled to test the hypothesis that traceability table influences the success of projects and that it decreases the failure rate that comes from the insufficient requirements management.
Keywords
Requirement; Requirement Traceability; Trace Table; Requirement Change Management;
Citations & Related Records
Times Cited By KSCI : 2  (Citation Analysis)
연도 인용수 순위
1 Project Management Body Of Knowledge 2nd Edition, PMI, 2000.
2 김계수, 인과분석 연구방법론, 청람, 2006
3 K. Weigers, Software Requirements, Redmond:Microsoft Press, 2003.
4 Project Closed Report, 대림아이앤에스, 2008. 12.
5 G, Anoniol, G. Canfora, G. Gasazza, A. De Lucia, “Recovering Traceability Links between Code and Documentation,” IEEE Transaction on Software Engineering, Vol.28 No.10, pp.970-983, 2002. 10.   DOI   ScienceOn
6 J. Cleland-Huang, D. Schmelzer, Dynamically Tracing Non-Functional Requirements through Design Pattern Invariants, Workshop on Traceability in Emerging Forms of Software Engineering, in conjunction with IEEE International Conference on Automated Software Engineering, 2003. 10.
7 A. Egyed, “A Scenario-Driven Approach to Traceability”, Proceedings of The 23rd International Conference on Software Engineering, pp.123-132, 2000. 06.
8 김주영, 류성열, 요구사항 추적테이블의 확장 및 정규화 방안, 한국정보처리학회 논문지 제16권 제2호, 2009. 04.   과학기술학회마을   DOI   ScienceOn
9 Joost de Wit, Maria Laura Ponisio, Looking for Reasons behind Sucess in Dealing with Requirements Change, Technical Report TR-CTIT-08-07, Centre for Telematics and Information Technology, University of Twente, Enschede, 2008. 08.
10 L. Goldin and A, Finkelstein, “Abstraction-based requirements management,” Proceedings of The 2006 ACM International workshop on Role of abstraction in software engineering (ROA '06), New York, NY, USA, pp.3-10, 2006. 05.   DOI
11 D. Zowghi and N, Nurmuliani, “A study of the impact of requirements volatility on software project performance,” Proceedings of The Ninth Asia-Pacific Software Engineering Conference(APSEC ’02), Washington, DC, USA, pp.3-13, 2002. 12.
12 Luigi Lavazza, Giuseppe Valetto, “Enhancing Requirement and Change Management through Process Modeling and Measurement,” Proceedings of The 4th International Conference on Requirements Engineering (ICRE’00), pp. 106-118, 2000. 01.
13 정규장, “개발방법론의 요구사항 변경관리를 개선하기 위한 프로세스 모델”, 정보과학회 논문지 소프트웨어 및 응용 제 30권 제6호, pp 504-514, 2003. 06.   과학기술학회마을
14 정유신, CMMI 기반 요구사항 추적성관리 프로세스 준수의 결함감소 효과 분석 연구, 서강대학교 석사학위 논문, 2007. 12.
15 Standish Group, CHAOS Reports(1994), 1995.
16 Standish Group, CHAOS Reports(2004), 2004. 01.
17 CMMI Product Team, Capability Maturity Mode Integration (CMMI), Software Engineering Institude(SEI), 2002.
18 M. Elizabeth C. Hull, Introduction to SW Verification and Validation, Requirements Engineering, 2005.
19 Balasubramaniam Ramesh, Toward Reference Models for Requirements Traceability, IEEE Transactions on software Engineering Vol.27 No.1, 2001. 01.   DOI   ScienceOn