Model-based traceability

Authors:
Jane Cleland-Huang;Jane Huffman Hayes;J. M. Domel
Affiliations:
School of Computing, DePaul University, USA;Department of Computer Science, University of Kentucky, USA;School of Computing, DePaul University, USA
Venue:
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Year:
2009

Citing 5
Cited 3

Toward Reference Models for Requirements Traceability

IEEE Transactions on Software Engineering
Supporting document and data views of source code

Proceedings of the 2002 ACM symposium on Document engineering
Guest Editor's Introduction: Model-Driven Engineering

Computer
Poirot: A Distributed Tool Supporting Enterprise-Wide Automated Traceability

RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Best Practices for Automated Traceability

Computer

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 systematic review of the use of requirements engineering techniques in model-driven development

MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
Inter-modelling with patterns

Software and Systems Modeling (SoSyM)

Quantified Score

Hi-index	0.00

Visualization

Abstract

Many organizations invest considerable cost and effort in building traceability matrices in order to comply with regulatory requirements or process improvement initiatives. Unfortunately, these matrices are frequently left un-used and project stakeholders continue to perform critical software engineering activities such as change impact analysis or requirements satisfaction assessment without benefit of the established traces. A major reason for this is the lack of a process framework and associated tools to support the use of these trace matrices in a strategic way. In this position paper, we present a model-based approach designed to help organizations gain full benefit from the traces they develop and to allow project stakeholders to plan, generate, and execute trace strategies in a graphical modeling environment. The approach includes a standard notation for capturing strategic traceability decisions in the form of a graph, and also notation for modeling reusable trace queries using augmented sequence diagrams. All of the model elements, including project specific data, are represented using XML. The approach is demonstrated through examples from a traffic simulator project composed of requirements, UML class diagrams, code, test cases, and test case results.