Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
An Object-Oriented Tool for Tracing Requirements
IEEE Software
IBM Systems Journal - Model-driven software development
Rule-Based Maintenance of Post-Requirements Traceability Relations
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
5th international workshop on Traceability in Emerging Forms of Software Engineering (TEFSE 2009)
ICSE '09 COMPANION Proceedings of the 2009 31st International Conference on Software Engineering: Companion Volume
A visual traceability modeling language
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part I
Analyzing the role of tags as lightweight traceability links
Proceedings of the 6th International Workshop on Traceability in Emerging Forms of Software Engineering
Trace queries for safety requirements in high assurance systems
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Which traceability visualization is suitable in this context? a comparative study
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Controversy Corner: Towards automated traceability maintenance
Journal of Systems and Software
Agile requirements traceability using domain-specific modelling languages
Proceedings of the 2012 Extreme Modeling Workshop
A visual language for modeling and executing traceability queries
Software and Systems Modeling (SoSyM)
Hi-index | 0.00 |
It is widely assumed that following a process is a good thing if you want to achieve and exploit the benefits of traceability on a software development project. A core component of any such process is the definition and use of a traceability information model. Such models provide guidance as to those software development artifacts to collect and those relations to establish, and are designed to ultimately support required project analyses. However, traceability still tends to be undertaken in rather ad hoc ways in industry, with unpredictable results. We contend that one reason for this situation is that current software development tools provide little support to practitioners for building and using customized project-specific traceability information models, without which even the simplest of processes are problematic to implement and gain the anticipated benefits from. In this paper, we highlight the typical decisions involved in creating a basic traceability information model, suggest a simple UML-based representation for its definition, and illustrate its central role in the context of a modeling tool. The intent of this paper is to re-focus attention on very practical ways to apply traceability information models in practice so as to encourage wider adoption.