Bridging the Requirements to Design Traceability Gap

Requirement traceability ensures that software products meet their requirements and additionally makes the estimation of the consequences of requirement changes possible. In this article a case study analyses symptoms of this problem in the process model of ISO 12207, the foundation of SPICE (ISO 15504), and CMMi. Our analysis is directed at deriving a concept for the integrated extension of current traceability models with the aspect of documented design decisions. This integrated decision model is presented along with an additional case study which illustrates the advantages of this approach for traceability.

[1]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[2]  Mikael Lindvall.  A study of traceability in object-oriented systems development , 1994 .

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

[4]  R.G. Pettit.  Lessons learned applying UML in embedded software systems designs , 2004, Second IEEE Workshop on Software Technologies for Future Embedded and Ubiquitous Systems, 2004. Proceedings..

[5]  Stefan Biffl,et al.  Value-Based Requirements Traceability: Lessons Learned , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[6]  Wan M. N. Wan-Kadir,et al.  An Evaluation of Traceability Approaches to Support Software Evolution , 2007, International Conference on Software Engineering Advances (ICSEA 2007).

[7]  Raymond McCall,et al.  Rationale Management in Software Engineering: Concepts and Techniques , 2006 .

[8]  Uwe Zdun,et al.  Using Patterns to Capture Architectural Decisions , 2007, IEEE Software.

[9]  Raymond McCall,et al.  Rationale Management in Software Engineering , 2006 .

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

[11]  Antje von Knethen.  A trace model for system requirements changes on embedded systems , 2001, IWPSE '01.

[12]  Antje von Knethen,et al.  Change-Oriented Requirements Traceability: Support for Evolution of Embedded Systems , 2002, ICSM.

[13]  Alexander Egyed,et al.  Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help , 2004, IEEE Software.

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

[15]  Antony Tang,et al.  A rationale-based architecture model for design traceability and reasoning , 2007, J. Syst. Softw..

[16]  Rick Kazman,et al.  Evaluating Software Architectures: Methods and Case Studies , 2001 .

[17]  George Spanoudakis.  Plausible and adaptive requirement traceability structures , 2002, SEKE '02.

[18]  R. B. Hunter,et al.  Processes for software in safety critical systems , 2001, Softw. Process. Improv. Pract..

[19]  Markus Kucera,et al.  An Integrated Decision Model For Efficient Requirement Traceability In SPICE Compliant Development , 2007, 2007 Fifth Workshop on Intelligent Solutions in Embedded Systems.