Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Process-Centered Requirements Engineering
Process-Centered Requirements Engineering
Software Change Impact Analysis
Software Change Impact Analysis
Modern Information Retrieval
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Whole program Path-Based dynamic impact analysis
Proceedings of the 25th International Conference on Software Engineering
Program slices: formal, psychological, and practical investigations of an automatic program abstraction method
Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Change Impact Analysis for Requirement Evolution using Use Case Maps
IWPSE '05 Proceedings of the Eighth International Workshop on Principles of Software Evolution
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods
IEEE Transactions on Software Engineering
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
Impact Analysis using Class Interaction Prediction Approach
Proceedings of the 2010 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the 9th SoMeT_10
Cyber-physical systems: imminent challenges
Proceedings of the 17th Monterey conference on Large-Scale Complex IT Systems: development, operation and management
Outsourcing location selection with SODA: a requirements based decision support methodology and tool
CAiSE'13 Proceedings of the 25th international conference on Advanced Information Systems Engineering
Investigating dependencies in software requirements for change propagation analysis
Information and Software Technology
| Hi-index | 0.00 |
Requirement change occurs during the entire software lifecycle,which is not only inevitable but also necessary. However, uncontrolled requirementchange will lead to a huge waste of time and effort. Most studiesabout the change impact analysis assume changes take place in code, which resultsin the analysis only at the source code level and ignoring the requirementchange is the fundamental cause. This paper introduces a Requirement CentricTraceability (RCT) approach to analyze the change impact at the requirementlevel. The RCT combines with the requirement interdependency graph and dynamicrequirement traceability to identify the potential impact of requirementchange on the entire system in late phase. This approach has been successfullyapplied to a real-life project, and the benefits and lessons learned will also bediscussed.