ICPM

This email address is being protected from spambots. You need JavaScript enabled to view it. This email address is being protected from spambots. You need JavaScript enabled to view it. The International Community for Project Managers
Brought to you by TenStep, Inc.
2363 St. David's Square
Kennesaw, GA 30152
877-536-8434 or 770-795-9097

This email address is being protected from spambots. You need JavaScript enabled to view it.
You are here: Home Blogs Use Traceability to Ensure All Requirements are Met
Wednesday, 04 January 2017 18:21

Use Traceability to Ensure All Requirements are Met

Written by 
Rate this item
(0 votes)
This content is from the TenStep weekly "tips" email dated 2017.4.1

Use Traceability to Ensure All Requirements are Met

Traceability refers to the ability to trace, or track, requirements throughout the lifecycle and into the final solution. Tracking requirements through the project ensures that all requirements are built into the design, all requirements are built into the solution, all requirements are tested and all requirements are implemented in the final solution. This is part of a structured lifecycle process.

Use a Traceability Matrix

The easiest way to create a link between your requirements and other development elements is by developing a Traceability Matrix. You could number the requirements as "1", "2", "3", etc. However, you might want to build more sophistication into the numbering scheme such as "TAB-001", "TAB-002", "DIS-001", "DIS-002", etc.

The Simple Approach

Tracking requirements can be done in a couple simple ways. One way, probably the simplest, is to just validate that each requirement is accounted for in each project phase. For instance, something like the following table might do.

Requirement#

Design

Construct

Implement

TAB-001

X

X

X

TAB-002

X

X



TAB-003

X

X



The "X" in each box validates that each particular requirement was accounted for in each phase.

A Little More Sophisticated

A more sophisticated example is shown below. In this case, the requirements are tracked through each project phase and the individual components are also identified. 

Requirement#

Design Element

Construct Component

Test Case

TAB-001

D-APR607P

C-APR607P

T-004-01

TAB-002

D-ARX607P

C-ARX607P

T-004-09, T-004-15

TAB-003

D-APC103D
D-APC103E


C-APC103D
C-APC103E


T-004-22

This tracking requires the team to keep more details as the requirements are proceeding through the lifecycle. However, it may be helpful to understand the details of the initial requirement, the design element, the component that contains the code for the requirement and the particular test case that ensured that the requirement worked correctly.

The key thing to remember about traceability is that it must be enforced throughout the lifecycle or else it does not work. If the team assigns tracking numbers to the requirements, but the requirements are not tracked in subsequent phases, the whole tracking scheme will break down.


At TenStep we are dedicated to helping organizations achieve their goals and strategies through the successful execution of critical business projects. We provide training, consulting and products for organizations to help them set up an environment where projects are successful. This includes help with strategic planning, portfolio management, program / project management, Project Management Offices (PMOs) and project lifecycles. For more information, visit www.TenStep.com or contact us at This email address is being protected from spambots. You need JavaScript enabled to view it.
Read 674 times
Login to post comments

News and Promotions

Keep up to date with the latest happenings by signing up for our newsletter. Subscribe below.

Twitter Update

Who's Online

We have 891 guests and no members online

Got something to say?