Requirements traceability: Theory and practice

  • Authors:

  • Balasubramaniam Ramesh;Curtis Stubbs;Timothy Powers;Michael Edwards

  • Affiliations:

  • Department of Computer Information Systems, Georgia State University, Atlanta, GA 30303, USA. E-mail: bramesh@cis.gsu.edu.;Air Test and Evaluation Center Squadron One (VX‐1), Patuxent River, MD 20670, USA;US Coast Guard Commander (TMM), 17th Coast Guard District, Juneau, AK 99802, USA;Code B44, NSWCDD, 10901 New Hampshire Avenue, Silver Spring, MD 20903, USA

  • Venue:
  • Annals of Software Engineering
  • Year:
  • 1997

Quantified Score

Hi-index 0.03

Visualization

Abstract

Current literature as well as standards that mandate requirements traceability do not provide a comprehensive model of what information should be captured and used as a part of a traceability scheme, leading to wide variation in the quality and usefulness of traceability practice across systems development efforts. In this paper, we present a framework for representing and developing a traceability scheme. The experiences of an organization using traceability as an important component of a quality software engineering process are discussed. Models describing the traceability practice in the organization, as well as issues and lessons learned, both from organizational and technical perspectives, from implementing a comprehensive traceability practice are presented.