FasTLInC: a constraint-based tracing approach
Journal of Systems and Software
Event-Based Traceability for Managing Evolutionary Change
IEEE Transactions on Software Engineering
requirements uncertainty: influencing factors and concrete improvements
Proceedings of the 27th international conference on Software engineering
Requirements change management process models: an evaluation
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
The impact of requirements changes on specifications and state machines
Software—Practice & Experience
The How? When? and What? for the Process of Re-planning for Product Releases
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
Coordinated software development: a framework for reasoning about trace links in software systems
INES'09 Proceedings of the IEEE 13th international conference on Intelligent Engineering Systems
Requirements modeling for embedded realtime systems
MBEERTS'07 Proceedings of the 2007 International Dagstuhl conference on Model-based engineering of embedded real-time systems
Requirements maturation analysis based on the distance between the source and developers
Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
Rigorous identification and encoding of trace-links in model-driven engineering
Software and Systems Modeling (SoSyM)
Empirical Software Engineering
| Hi-index | 0.00 |
Changing requirements are a major source of risk to software development projects, but are generally not included in hazard identification and risk assessment procedures at present because the information needed is not collected or recorded by current requirements methods. It is proposed that change analysis should be an integral part of the entire development process so that change can be handled in a better-informed way with the associated risks being made apparent. Sensitivity analysis is proposed as the principal means of predicting two categories of hazard: which requirements are unstable and which design areas are most susceptible to changes in requirements. Impact analysis supports the decision-making process concerning the implementation of changes, and is also used to predict the impact of potential change for the assessment of risk. The paper considers what information is needed to enable sensitivity and impact analysis to provide an effective means of change analysis and what methods provide such information, emphasizing the importance of traceability and the capture of design rationale. Because the potential for change would be made apparent early in the lifecycle the outcome should be a substantial contribution towards the goal of minimizing the adverse impact of changing requirements on the project objectives.