Bridging the Requirements to Design Traceability Gap

  • Bernhard Turban
  • Markus Kucera
  • Athanassios Tsakpinis
  • Christian Wolff
Part of the Lecture Notes in Electrical Engineering book series (LNEE, volume 38)


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.


Requirements engineering Traceability Design Rationale management Decision Embedded systems SPICE ISO15504 ISO 12207 CMMi 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    O. Benediktsson, R. Hunter and A.D. McGettrick. Processes for Software in Safety Critical Systems. In: Software Process: Improvement and Practice 6 (1), 47–62 (2001)CrossRefGoogle Scholar
  2. 2.
    K. Hörmann, L. Dittmann, B. Hindel and M. Müller. SPICE in der Praxis, Interpretationshilfe für Anwender und Assessoren, dpunkt Verlag, Heidelberg (2006)Google Scholar
  3. 3.
    R. Kneuper. CMMI. Verbesserung von Softwareprozessen mit Capability Maturity Model Integration. Volume 2, dpunkt Verlag, Heidelberg (2006)Google Scholar
  4. 4.
    Ch. Rupp. Requirements-Engineering und –Management, Volume 2, Hanser, München (2002).Google Scholar
  5. 5.
    M. Lindvall. A study of traceability in object-oriented systems development. Licenciate thesis, Linköping University, Institute of Technology, Sweden (1994)Google Scholar
  6. 6.
    A. von Knethen. Change-Oriented Requirements Traceability. Support for Evolution of Embedded Systems, Fraunhofer IRB Verlag, Stuttgart (2001).Google Scholar
  7. 7.
    Ch. Ebert. Systematisches Requirements Management, dpunkt, Heidelberg (2005).Google Scholar
  8. 8.
    B. Paech, A. Dutoit, D. Kerkow and A. von Knethen. Functional requirements, nonfunctional requirements, and architecture should not be separated – A position paper, REFSQ Essen (2002).Google Scholar
  9. 9.
    O. Gotel, O. and A. Finkelstein. An Analysis of the Requirements Traceability Problem. Proceedings First International Conference on Requirements Engineering 1994, pp. 94–101 (1994).Google Scholar
  10. 10.
    S. Rochimah, W. Wan Kadir and A. Abdullah. An Evaluation of Traceability Approaches to Support Software Evolution. International Conference on Software Engineering Advances (ICSEA) (2007).Google Scholar
  11. 11.
    A. Egyed and P. Grünbacher. Indentifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help. IEEE SW November/December (2004).Google Scholar
  12. 12.
    B. Ramesh and M. Jarke. Toward Reference Models for Requirements Traceability. IEEE Transactions on Software Engineering, 27(1) (2001).Google Scholar
  13. 13.
    G. Spanoudakis, A. Zisman, E. Perez-Minana and P. Krause. Rule-Based Generation of Requirements Traceability Relations, Journal of Systems and Software, 105–227 (2004).Google Scholar
  14. 14.
    G. Spanoudakis, “Plausible and Adaptive Requirement Traceability Structures,” in Proc. 14th International Conf. Software Eng. and Knowledge Eng. (2002). 15. M. Müller, K. Hörmann, L. Dittmann and J. Zimmer. Automotive SPICE in der Praxis: Interpretationshilfe für Anwender und Assessoren. Dpunkt 1. Auflage, Heidelberg (2007).Google Scholar
  15. 15.
    M. Müller, K. Hörmann, L. Dittmann and J. Zimmer. Automotive SPICE in der Praxis: Interpretationshilfe für Anwender und Assessoren. Dpunkt 1. Auflage, Heidelberg (2007).Google Scholar
  16. 16.
    W. Kunz and H. Rittel. Issues as elements of information systems. Working Paper 131, Center for Urban and Regional Development, University of California, Berkeley (1970).Google Scholar
  17. 17.
    A. Egyed, P. Grünbacher, M. Heindl and S. Biffl, Value-Based Requirements Traceability: Lessons Learned. 15th IEEE International Requirements Engineering Conference (2007).Google Scholar
  18. 18.
    B. Turban, M. Kucera, A. Tsakpinis and Ch. Wolff, An Integrated Decision Model For Efficient Requirement Traceability in SPICE Compliant Development, Fifth Workshop on Intelligent Solutions in Embedded Systems (WISES), Madrid (2007).Google Scholar
  19. 19.
    P. Liggesmeyer and D. Rombach (Eds.): Software Engineering eingebetteter Systeme Grundlagen – Methodik – Anwendungen. Volume 1., Elsevier, München (2005).Google Scholar
  20. 20.
    A. Dutoit, A., R. McCall, I. Mistrik and B. Paech (Eds.). Rationale Management in Software Engineering. Springer, Berlin (2006).Google Scholar
  21. 21.
    A. Tang, Y. Jin and J. Han, A rationale-based architecture model for design traceability and reasoning. Journals of Systems and Software Volume 80(6) 919–934. (2007).Google Scholar
  22. 22.
    A. Dutoit, R. McCall, I. Mistrik and B. Paech. Rationale Management in Software Engineering: Concepts and Techniques. In [20 (p.1–48)] (2006).Google Scholar
  23. 23.
    E. Gamma, R. Helm, R. Johnson and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, Reading, MA (1995).Google Scholar
  24. 24.
    N.B. Harrison, P. Avgerion and U. Zdun, Using Patterns to Capture Architectural Decisions. IEEE Software 38–45 July/August (2007).Google Scholar
  25. 25.
    T. Posch, K. Birken and M. Gerdom, Basiswissen Softwarearchitektur- Verstehen, entwerfen, bewerten und dokumentieren. dpunkt, Heidelberg (2004).zbMATHGoogle Scholar
  26. 26.
    P. Clements, R. Kazman and M. Klein, Evaluating Software Architectures – Methods and case studies. Addison-Wesley, New York (2002).Google Scholar
  27. 27.
    M. Moro, Modellbasierte Qualitätsbewertung von Softwaresystemen, Books on Demand GmbH, 1. Auflage (2004).Google Scholar
  28. 28.
    A. von Knethen, A Trace Model for System Requirements Changes on Embedded Systems, In Proc. of 4th International Workshop on Principles of SW Evolution, Sept. (2001).Google Scholar
  29. 29.
    R. Pettit, Lessons Learned Applying UML in Embedded Software Systems Design, Second IEEE Workshop on Software Technologies for Future Embedded and Ubiquitous Systems, Wien (2004).Google Scholar

Copyright information

© Springer Science+Business Media B.V. 2009

Authors and Affiliations

  • Bernhard Turban
    • 1
  • Markus Kucera
    • 2
  • Athanassios Tsakpinis
    • 2
  • Christian Wolff
    • 3
  1. 1.Electronic Systems Engineering, MBtech GroupGermany
  2. 2.Competence Center SE, University of Applied SciencesGermany
  3. 3.Media Computing, University of RegensburgGermany

Personalised recommendations