Experience report: implementing requirement traceability throughout the software development life cycle

Akman S., Ozmut M., Aydin B., Gokturk S.

JOURNAL OF SOFTWARE-EVOLUTION AND PROCESS, vol.28, no.11, pp.950-954, 2016 (SCI-Expanded) identifier identifier

  • Publication Type: Article / Article
  • Volume: 28 Issue: 11
  • Publication Date: 2016
  • Doi Number: 10.1002/smr.1824
  • Journal Indexes: Science Citation Index Expanded (SCI-EXPANDED), Scopus
  • Page Numbers: pp.950-954
  • Keywords: application life cycle management, configuration management, requirement traceability, software process improvement
  • Middle East Technical University Affiliated: No


The developed traceability model is essential in helping project members, project managers and customers, all understand the product at all stages of the software development life cycle and maintain the integrity of the design information. Utilizing a well designed development environment and an environment support team is vital in maintaining the requirement traceability. With the requirement traceability, the customers' requirement status can be monitored and the relationships among requirements, design decisions, and code can be accessed to reuse already developed products or analyze the change impacts, which in turn benefits companies by lowering the development and maintenance cost. This paper describes how requirement traceability is supported in an information technology solution provider company, with the improvement of integrated tool infrastructure, the transformation of the tool infrastructure, and the challenges that were faced during the transformation. Throughout this improvement project, not only the tools and their capabilities were looked into but also the company culture and the already acquired know-how in using many infrastructure tools such as Enterprise Project Management, JIRA, Team Foundation Server, Quality Center, Enterprise Architect, SVN, and Eclipse.