Creation of Requirement Traceability Matrix using rrc objective

Download 12.68 Kb.
Date conversion03.01.2017
Size12.68 Kb.
Girish Patil Page 1/3/2017

Creation of Requirement Traceability Matrix using RRC

Objective – This document helps you to create the traceability matrix using Rational Requirement Composer.
Assumptions – The association between RRC, RQM and RTC exists and RRC artifacts are linked to RQM and RTC artifacts and In RRC following types of artifacts exists–

  1. Functional Requirements

  2. Design Document(ex: use case)

  3. Technical Specification

  4. System Components

  5. Software Modules(ex: Story board diagram)

Description about RTM - A traceability matrix is a document, usually in the form of a table, that correlates any two base lined documents that require a many-to-many relationship to determine the completeness of the relationship. It is often used with high-level requirements (these often consist of marketing requirements) and detailed requirements of the product to the matching parts of high-level design, detailed design, test plan, and test cases.
A requirements traceability matrix may be used to check to see if the current project requirements are being met, and to help in the creation of a request for proposal,[1] software requirements specification,[2] various deliverable documents, and project plan tasks.
Below screen shots provides an overview on Requirements Traceability matrix template:

In this Functional Requirements is linked to documents – Design Document, Technical Specification, System components, Software modules, Test cases, Implemented docs i.e. to development docs like user stories, tasks etc.
So to create this type of matrix in RRC, we need to create a view and link types.
Create a link type as DD (Design Document) – which links Functional Requirements and Design documents.
Create a link type as FR (Functional Requirements) – which links Customer documents and Functional Requirements.
Create a link type as TS (Technical Specification) – which links Functional Requirements and Technical Specifications.
Create a link type as SC (System Components) – which links Functional Requirements and System components.
Create a link type as SM (Software Module) – which links Functional Requirements and Software components.
Validated by and Implemented by link types are already exists in our RRC.
How to create link types?

  1. Login to RRC with admin role and click artifactsBrowse artifacts.

  1. Click on Manage Project Properties

  1. Click on Link types.

  1. Click on Add button

  1. Enter name of Link type as DD

8. Click on save button. In the same way create link types - FR, TS, SC, and SM

Now we need to create artifacts of type –

Functional Requirements, Design Document (ex: use case), Technical Specification, System Components, Software Modules (ex: Story board diagram)

Create separate folders for each type of artifact type and create the artifacts under those folders.
Next establish the linkage between the artifacts using created link types.
Now navigate functional requirements folder and add the columns by clicking on the “Change column Display settings”

Add the required columns i.e. FR, DD, TS, SC, SM, Validated by and Implemented by and click on Ok button.
Then save the view by clicking save view button –
Name the view as RTM i.e. Requirements Traceability Matrix.
If this needs to exported in excel then select all the rows and select option export

You can get the exported matrix in this format –


Let me know if you need any help regarding the same.

The database is protected by copyright © 2017
send message

    Main page