Requirements-Traceability in der industriellen Praxis - Ziele und Einsatz

Als wichtiges Kriterium fur den erfolgreichen Einsatz von Traceability in der Praxis wird die Anpassung der Traceability-Links an konkrete Projekte genannt. Dabei geht es neben der Integration in den konkreten Softwareentwicklungsprozess und die spezifische Unternehmenskultur auch um eine Anpassung an die konkreten Aktivitaten, die mit Traceability unterstutzt werden sollen. Es wird das Ergebnis einer Studie vorgestellt, welche untersucht, fur welche Nutzungsszenarien Traceability in der Praxis eingesetzt wird.

[1]  Timothy C. Lethbridge,et al.  Software Engineering Data Collection for Field Studies , 2008, Guide to Advanced Empirical Software Engineering.

[2]  Ilka Philippow,et al.  Motivation Matters in the Traceability Trenches , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[3]  Jane Cleland-Huang.  Just Enough Requirements Traceability , 2006, COMPSAC.

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

[5]  B. Ramesh,et al.  Issues in the development of a requirements traceability model , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[6]  Jens von Pilgrim,et al.  A survey of traceability in requirements engineering and model-driven development , 2010, Software & Systems Modeling.

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

[8]  Tobias Hildenbrand,et al.  Towards End-to-End Traceability: Insights and Implications from Five Case Studies , 2009, 2009 Fourth International Conference on Software Engineering Advances.

[9]  WinklerStefan,et al.  A survey of traceability in requirements engineering and model-driven development , 2010 .

[10]  Julia Rubin,et al.  Model traceability , 2006, IBM Syst. J..

[11]  Paul Grünbacher,et al.  Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne , 2006, 21st IEEE/ACM International Conference on Automated Software Engineering (ASE'06).

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

[13]  A. Ahmad,et al.  Documenting Requirements Traceability Information for Small Projects , 2007, 2007 IEEE International Multitopic Conference.

[14]  George Spanoudakis,et al.  Software Traceability : A Roadmap , 2005 .

[15]  Klaus Pohl,et al.  Adapting traceability environments to project-specific needs , 1998, CACM.

[16]  Vassilka Kirova,et al.  Effective requirements traceability: Models, tools, and practices , 2008, Bell Labs Technical Journal.

[17]  Steve Riddle,et al.  Overcoming the traceability benefit problem , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[18]  Dr. Hossein Saiedian,et al.  The Importance of Traceability Why Software Requirements Traceability Remains a Challenge , .

[19]  Steve Riddle,et al.  Position Paper: Enabling Traceability , 2002 .