Contact Us

Contact Us

Project Establish and Maintain Requirement Traceability Process

Objectives

  1. An objective of maintaining traceability among requirements and other work products helps determine that all customer requirements have been completely addressed and that all work products can be traced to valid source requirements.
  2. Traceability is particularly needed in conducting the impact analysis of requirements changes on the project’s activities and work products.

Process Entry/Exit Criteria

Entry Criteria Exit Criteria
  • Requirements and other work products among which traceability is to be maintained are available.
  • Authorized changes have occurred in the baseline requirements and other work products.
  • Requirement Traceability Matrix is prepared, reviewed and evolved for next required information throughout the project life.
  • RTM is updated due to authorized changes in the requirements and other work products.

Process Inputs/Outputs

Inputs Outputs
  • Analysis and Design Specification
  • Test Cases
  • Source Code
  • Requirement Traceability Matrix

Tasks

  1. Assigned Role(s) starts developing requirement traceability with the finalization of Requirement Specification, then after Analysis and Design Speciation, then after completion of Coding and Test Case Designing; and this process gets evolve as next required information is available according to Requirement Traceability Matrix (RTM) template.
  2. Assigned roles review the Requirement Traceability Matrix (RTM) after each iteration.
  3. Assigned Role(s) updates the requirement traceability matrix as a result of authorized changes in baselined artifacts.

Guidelines to Establish and Maintain Requirement Traceability

  1. Requirement Traceability Matrix (RTM) maintains the traceability among the output of different project phases (i.e. requirements, source code, test cases, etc.) so, by nature, RTM is an evolving document and requires information of different phases to be completed. Initially, Requirement Traceability Matrix (RTM) is prepared by Development Team usually after approval and baselining of requirements and reviewed by the Development Team Lead; and when Test cases are available, it is updated by the Quality Assurance team and reviewed by the Quality Assurance Team Lead to provide traceability between requirement and test cases; and after development, it is again updated by Development team and reviewed by the Development Team Lead to maintain the relationship of requirements with code components.
  2. Requirement Traceability Matrix (RTM) may also be updated due to authorized changes in baselined requirements, test cases, and code.
  3. An assigned role can also start the creation of Requirement Traceability Matrix (RTM) in later phases of development if he feels that there is not enough information available after Requirements Specification approval or analysis and design approval.