Analyzing and Systematizing Current Traceability Schemas

The aim of this work is to produce a traceability model to enhance processes and tasks, which make extensive use of traceability information such as, V&V, change management and impact analysis, under the roundtrip engineering approach. This paper analyzes several current traceability approaches, in order to obtain their relevant features, to identify overlaps and inconsistencies between them, and to select the best traceability practices. It was identified that, several issues still make difficult the adoption of a wide-scale traceability activity, in the software/system engineering practice, such as, there is a lack of a commonly accepted traceability definition, a standard way of specifying traceability between artifacts, and a traceability type classification. Basing on these findings, an approach for a "traceability schema specification" and a first implementation on a software/system engineering environment are provided. The schema attempts to systematize the definition, deployment and maintenance of a traceability implementation

[1]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[2]  Matthias Jarke,et al.  Requirements tracing , 1998, CACM.

[3]  Patricio Letelier A Framework for Requirements Traceability in UML-based Projects , 2002 .

[4]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .

[5]  Barry W. Boehm,et al.  Value-based software engineering: reinventing , 2003, SOEN.

[6]  Juan Garbajosa Sopeña,et al.  The Need for a Unifying Traceability Scheme , 2005 .

[7]  Arie van Deursen Recovering Rationale , 2001 .

[8]  Eila Niemelä,et al.  Tool support for traceable product evolution , 2004, Eighth European Conference on Software Maintenance and Reengineering, 2004. CSMR 2004. Proceedings..

[9]  David C. Brown,et al.  Reasoning with Design Rationale , 2000, AID.

[10]  Dar-Biau Liu,et al.  Metrics for requirements engineering , 1995, J. Syst. Softw..

[11]  RameshBalasubramaniam,et al.  Toward Reference Models for Requirements Traceability , 2001 .

[12]  A. Crespo,et al.  Automated integrated support for requirements-area and validation processes related to system development , 2004, 2nd IEEE International Conference on Industrial Informatics, 2004. INDIN '04. 2004.

[13]  Anne Persson,et al.  Requirements Interdependencies: State of the Art and Future Challenges , 2005 .

[14]  Standard Glossary of Software Engineering Terminology , 1990 .

[15]  Cmmi Product Team Capability Maturity Model® Integration (CMMI), Version 1.1--Staged Representation , 2002 .

[16]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[17]  Andrea Zisman,et al.  Rule-based generation of requirements traceability relations , 2004, J. Syst. Softw..

[18]  Alexander Egyed,et al.  Automating requirements traceability: Beyond the record & replay paradigm , 2002, Proceedings 17th IEEE International Conference on Automated Software Engineering,.

[19]  Balasubramaniam Ramesh,et al.  Factors influencing requirements traceability practice , 1998, CACM.

[20]  Åsa G. Dahlstedt,et al.  Requirements Interdependencies-Moulding the State of Research into a Research Agenda , 2003 .

[21]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..