Getting back to basics: Promoting the use of a traceability information model in practice
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Enabling Automated Traceability Maintenance through the Upkeep of Traceability Relations
ECMDA-FA '09 Proceedings of the 5th European Conference on Model Driven Architecture - Foundations and Applications
Enabling Automated Traceability Maintenance by Recognizing Development Activities Applied to Models
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
A state-based approach to traceability maintenance
Proceedings of the 6th ECMFA Traceability Workshop
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
Graph-based traceability: a comprehensive approach
Software and Systems Modeling (SoSyM)
Software and Systems Modeling (SoSyM)
Service-oriented architecture modeling: bridging the gap between structure and behavior
Proceedings of the 14th international conference on Model driven engineering languages and systems
Controversy Corner: Towards automated traceability maintenance
Journal of Systems and Software
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
An accurate set of traceability relations between software development artifacts is desirable to support evolutionary development. However, even where an initial set of traceability relations has been established, their maintenance during subsequent development activities is time consuming and error prone, which results in traceability decay. This paper focuses solely on the problem of maintaining a set of traceability relations in the face of evolutionary change, irrespective of whether generated manually or via automated techniques, and it limits its scope to UML-driven development activities post-requirements specification. The paper proposes an approach for the automated update of existing traceability relations after changes have been made to UML analysis and design models. The update is based upon predefined rules that recognize elementary change events as constituent steps of broader development activities. A prototype traceMaintainer has been developed to demonstrate the approach. Currently, traceMaintainer can be used with two commercial software development tools to maintain their traceability relations. The prototype has been used in two experiments. The results are discussed and our ongoing work is summarized.