An end-to-end industrial software traceability tool

Traceability is an important aspect of software development that is often required by various professional standards and government agencies. Yet current industrial approaches do not typically address end-to-end traceability. Moreover, many industry projects become entangled in process overhead and fail to derive much benefit from current traceability solutions. This paper presents a successful end-to-end software traceability tool developed at Wonderware, a software development company and a business unit of Invensys Systems, Inc. This process-oriented approach achieves comprehensive traceability and supports the entire software development life cycle by focusing on both requirements traceability and process traceability. We offer new perspectives in analyzing the problem as well as general traceability guidelines. These guidelines have emerged from the experience of implementing and deploying the traceability tool within actual company constraints. We discuss encouraging results and point to the advantages gained in using our approach.

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

[2]  Margaret E. Singleton Automating Code and Documentation Management , 1987 .

[3]  Jane Huffman Hayes,et al.  Humans in the traceability loop: can't live with 'em, can't live without 'em , 2005, TEFSE '05.

[4]  Dean Leffingwell The Role of Requirements Traceability in System Development , 1996 .

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

[6]  Balasubramaniam Ramesh,et al.  Implementing requirements traceability: a case study , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[7]  Alexander Egyed,et al.  A scenario-driven approach to traceability , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[8]  Klaus Pohl,et al.  Integrating Requirement and Architecture Information: A Scenario and Meta-Model Based Approach , 2001 .

[9]  Stefan Biffl,et al.  A value-based approach for understanding cost-benefit trade-offs during automated software traceability , 2005, TEFSE '05.

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

[11]  Jeff Green,et al.  Automating traceability for generated software artifacts , 2004, Proceedings. 19th International Conference on Automated Software Engineering, 2004..

[12]  Dolores R. Wallace,et al.  A framework for the development and assurance of high integrity software , 1994 .

[13]  Mark J. Gerken,et al.  The knowledge-based software assistant: a formal, object oriented software development environment , 1996, Proceedings of the IEEE 1996 National Aerospace and Electronics Conference NAECON 1996.

[14]  Barry W. Boehm,et al.  Value-Based Software Engineering: A Case Study , 2003, Computer.

[15]  K. Anderson,et al.  Towards large-scale information integration , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.

[16]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

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

[18]  Carl K. Chang,et al.  Event-Based Traceability for Managing Evolutionary Change , 2003, IEEE Trans. Software Eng..

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

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

[21]  Steve Riddle,et al.  Tailoring Traceability Information to Business Needs , 2006 .

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

[23]  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).

[24]  Jane Cleland-Huang,et al.  A heterogeneous solution for improving the return on investment of requirements traceability , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[25]  Giuliano Antoniol,et al.  Design-code traceability recovery: selecting the basic linkage properties , 2001, Sci. Comput. Program..