A Requirements Management Process to improve the Requirements Management of Development Methodologies


The KIPS Transactions:PartD, Vol. 9, No. 1, pp. 81-90, Feb. 2002
10.3745/KIPSTD.2002.9.1.81,   PDF Download:

Abstract

More than 50% of defects and errors in the software development projects are related to the requirements[14]. But the development methodologies can not provide enough supports to the requirements management and changes. In the real world, the requirements keep changing as the requirements at the early development phase are usually incomplete, the developer's understanding of the problem will be constantly changed during the software process, and new requirements may emerge with the organizational and environmental changes. In this paper, a requirements management process that can be integrated into the development methodologies is proposed to extend the requirements management over the whole development life-cycle and to support the requirements changes at the design/implementation/test phases. To evaluate the proposed process, it was compared to the existing requirements management processes and models, and examined through a integration test with a widely used development methodology 'MaRMI' to show the expected improvements at each development phase.


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. C. Shin and Y. s. Koo, "A Requirements Management Process to improve the Requirements Management of Development Methodologies," The KIPS Transactions:PartD, vol. 9, no. 1, pp. 81-90, 2002. DOI: 10.3745/KIPSTD.2002.9.1.81.

[ACM Style]
Jong Cheol Shin and Yeon seol Koo. 2002. A Requirements Management Process to improve the Requirements Management of Development Methodologies. The KIPS Transactions:PartD, 9, 1, (2002), 81-90. DOI: 10.3745/KIPSTD.2002.9.1.81.