The Facility for Automated and Self-Maintainable Traceability



This chapter introduces the facility for automated, dynamic, accurate, precise, and self-maintainable traceabilities among related software documents and test cases and source code established through test case execution and some keywords used within the test case descriptions to indicate the format of the documents as well as the file paths and the bookmarks for automatically opening the documents from the corresponding positions when the related test case is selected for forward tracing or traced backwards from the corresponding source code. When a test case is executed, a Time Tag will be automatically inserted into both the test case description and the database of the test coverage measurement results for mapping them together. No matter if the contents of a document are modified, or the parameters of a test case are changed, or the corresponding source code is modified, after rerunning the test case the traceabilities will be updated automatically without any manual rework. Here a “document” means a regular file for requirement specification, design description, test requirement specification, user manual, project development plan, cost report, or a Web page as well as a batch file for dynamically running a related program such as a tool for selectively playing back the GUI operations captured with the test case execution, and displaying the test coverage measurement result shown in a new type of control flow diagram which is ­interactive and traceable with untested source modules and branches highlighted at the same time for automated software acceptance testing.


Source Code Test Coverage Requirement Validation Requirement Traceability Test Script 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. [Amb05]
    Ambler SW (2005) A manager’s introduction to the rational unified process (RUP). Ambysoft.
  2. [Kan09]
    Kannenberg A et al (2009) Why software requirements traceability remains a challenge. CrossTalk, Jul/Aug 2009 IssueGoogle Scholar
  3. [Ram01]
    Ramesh B, Jarke M (2001) Toward reference models for requirements traceability. IEEE Trans Software Eng 1:58–93CrossRefGoogle Scholar
  4. [Ril07]
    Rilling J et al (2007) CASCON 2007 workshop report, traceability in software engineering – past, present and future. IBM Technical Report: TR-74-211, October 25, 2007Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2011

Authors and Affiliations

  1. 1.OaklandUSA

Personalised recommendations