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


The KIPS Transactions:PartD, Vol. 17, No. 4, pp. 271-282, Aug. 2010
10.3745/KIPSTD.2010.17.4.271,   PDF Download:

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.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
J. Y. Kim, S. Y. Rhew, M. S. Hwang, "A Study of Requirement Change Management and Traceability Effect Using Traceability Table," The KIPS Transactions:PartD, vol. 17, no. 4, pp. 271-282, 2010. DOI: 10.3745/KIPSTD.2010.17.4.271.

[ACM Style]
Ju Young Kim, Sung Yul Rhew, and Man Su Hwang. 2010. A Study of Requirement Change Management and Traceability Effect Using Traceability Table. The KIPS Transactions:PartD, 17, 4, (2010), 271-282. DOI: 10.3745/KIPSTD.2010.17.4.271.