Requirements change management on feature-oriented requirements tracing

6Citations
Citations of this article
25Readers
Mendeley users who have this article in their library.
Get full text

Abstract

User requirements have been changed during development progresses, since they are impossible to define all of software requirements. These requirements change leads to mistakes because the developers cannot completely understand the software structure and behavior, or they cannot discover all parts affected by a change. Therefore, requirement changes have to be managed and assessed to ensure that they are feasible, make economic sense, and contribute to the business needs of the customer organization. We propose requirements change management process on feature-oriented requirements tracing. It is based on value analysis and feature-oriented requirement traceability links. Our approach offers two contributions to the study of requirements change: (1)We define a requirements change tree model to make user requirements change request generalize by feature level. (2)We provide overall process such as change request normalization, change impact analysis, change request alternative design, change request implementation, and change request evaluation. In addition, we especially summarize the results of a case study which is carried out in asset management portal system. © Springer-Verlag Berlin Heidelberg 2007.

Cite

CITATION STYLE

APA

Ahn, S., & Chong, K. (2007). Requirements change management on feature-oriented requirements tracing. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 4706 LNCS, pp. 296–307). Springer Verlag. https://doi.org/10.1007/978-3-540-74477-1_29

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free