Goal-centric traceability for managing non-functional requirements
Proceedings of the 27th international conference on Software engineering
Fixing Inconsistencies in UML Design Models
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Combining Single-Version and Evolutionary Dependencies for Software-Change Prediction
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Supporting Change Impact Analysis for Service Oriented Business Applications
SDSOA '07 Proceedings of the International Workshop on Systems Development in SOA Environments
ACM Transactions on Software Engineering and Methodology (TOSEM)
Adams re-trace: traceability link recovery via latent semantic indexing
Proceedings of the 30th international conference on Software engineering
Cost-based BDI plan selection for change propagation
Proceedings of the 7th international joint conference on Autonomous agents and multiagent systems - Volume 1
Requirements Modeling and Validation Using Bi-layer Use Case Descriptions
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
Automating regression test selection based on UML designs
Information and Software Technology
The impact of requirements changes on specifications and state machines
Software—Practice & Experience
Generating and Evaluating Choices for Fixing Inconsistencies in UML Design Models
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Characterizing software architecture changes: A systematic review
Information and Software Technology
A holistic approach to managing software change impact
Journal of Systems and Software
A flexible requirements analysis approach for software product lines
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
A framework for reviewing domain specific conceptual models
Computer Standards & Interfaces
Proceedings of the 33rd International Conference on Software Engineering
Inconsistency management framework for model-based development
Proceedings of the 33rd International Conference on Software Engineering
A taxonomy for software change impact analysis
Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th annual ERCIM Workshop on Software Evolution
Layered class diagrams: supporting the design process
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Rule-Based impact propagation for trace replay
ICCBR'11 Proceedings of the 19th international conference on Case-Based Reasoning Research and Development
Information and Software Technology
Recovering test-to-code traceability using slicing and textual analysis
Journal of Systems and Software
| Hi-index | 0.00 |
The use of Unified Modeling Language (UML)analysis/design models on large projects leads to a largenumber of interdependent UML diagrams. As softwaresystems evolve, those diagrams undergo changes to, forinstance, correct errors or address changes in therequirements. Those changes can in turn lead tosubsequent changes to other elements in the UMLdiagrams. Impact analysis is then defined as the processof identifying the potential consequences (side-effects) ofa change, and estimating what needs to be modified toaccomplish a change. In this article, we propose a UMLmodel-based approach to impact analysis that can beapplied before any implementation of the changes, thusallowing an early decision-making and change planningprocess. We first verify that the UML diagrams areconsistent (consistency check). Then changes between twodifferent versions of a UML model are identifiedaccording to a change taxonomy, and model elementsthat are directly or indirectly impacted by those changes(i.e., may undergo changes) are determined usingformally defined impact analysis rules (written withObject Constraint Language). A measure of distancebetween a changed element and potentially impactedelements is also proposed to prioritize the results ofimpact analysis according to their likelihood ofoccurrence. We also present a prototype tool thatprovides automated support for our impact analysisstrategy, that we then apply on a case study to validateboth the implementation and methodology.