baconf - requirement traceability - julen mohanty

Requirement Traceability

Julen C MohantyCitigroup Technology Services

Saturday, July 17, 2010Business Analyst Conference

BA Conference 2

Table of Content

What is Traceability Matrix

Components of Requirement

How to Trace

Traceability Matrix Example

Why is it Required

The Myth

7/17/2010

BA Conference 3


7/17/2010

A Traceability Matrix is a document, usually in the form of a table, that correlates any two baselined documents that require a many to many

relationship to determine the completeness of the relationship. - WIKI

I would say: Traceability Matrix is a document, where we would like to be able to trace back and forth how and where any work product

fulfills the directions of the preceding (source) product.

Contd..

BA Conference 47/17/2010

Contextual links between the various Requirements&

Relationship between Work Products developed


Effective Implementation and Verification of Requirements

Business Rqmt

User RqmtFunctional

RqmtTest

Rqmt

BRDTDD

FRD

Test Plan

CODE

Test Cases

BA Conference 5

Components of Software Requirements

7/17/2010

Business Requirements

Vision & Scope Document

User Requirements

Use Case Document

Quality Attributes

Functional Requirements

System Requirements

Nonfunctional Requirements

Constraints

Software Requirement Specification

BA Conference 6

How to Trace

7/17/2010

• Has at least one to one relationship

• Makes relationship between requirements & within requirements

• Document the functions next to each of the Requirements they are related to

• Same way Tech Design next to each functions and that’s how till

implementation

• Customer can give inputs when things are ambiguous.

BA Conference 7

Traceability Matrix - Example

7/17/2010

Requirement Traceability Matrix

Project Name:

Project ID:

Project Team: Requirement

Category Description BRD Sections

FRD Sections

TDD Sections

Dev Test Plan Sections

UAT Sections

Level 1


Requirements Functions DesignDevelop

ment TestingBusiness Require

ment

Technical Requirem

ents

User Requirements

Func. Sub Func. LLD HLD

Databse

Design

Development

module No.

Unit Testin

gSIT UAT

Level 2



REQUIREMENTS TRACEABILITY MATRIX REQUIREMENTS TRACEABILITY MATRIXProject Name: Project Name:

National Center: National Center:

Project Manager Name:

Project Manager Name:

Project Description:

Project Description:

IDAssocID

Technical Assumption(s)

and/ or Customer Need(s)

FunctionalRequirement Status

Architectural/ Design

DocumentTechnical

SpecificationSystem

Component(s)

SoftwareModule(s)

Test Case

NumberTested

InImplement

ed InVerificati

onAdditionalComments

001 1.1.1 002 2.2.2 003 3.3.3 004 4.4.4 005 5.5.5 006

Requirements_Traceability_Matrix_Template

Attached Template for use, by Audience

Level 3 – Working


BA Conference 10

Why to use Traceability Matrix

7/17/2010

• Has relationship back & forth from Requirement to Implementation

• Makes relationship between requirements & within requirements

• Traces back a function to it’s requirements, or technical design to it’s function, or

even a code to it’s technical design/ function / requirement

• Can check whether any requirement has at least one design solution and by

checking the solution(s) you may see whether the requirement is sufficiently

solved by this (or the set of) connected design(s)

• If you have to change any requirement, you can see which designs are affected.

And if you change any design, you can check which requirements may be affected

and see what the impact is.

• Identify those areas with a higher number of defects and analyze the root causesContd..


• In a Design-Code Traceability Matrix you can do the same to keep track of how

and which code solves a particular design and how changes in design or code

affect each other. Take e.g. the Requirement of UserFriendliness (UF).

• If a design solution does not solve any requirement, it should be deleted, as it is

of no value

• It shows has the system been adequately tested

• It helps to minimize scope creep

• Customer requirements through development and testing verifies that the

customer requirements are implemented and tested

• Most important : It says things that can be reused

• It’s a Six Sigma project management matrix table

Why to use Traceability Matrix

BA Conference 12

Previous Stage v/s Current Stage

7/17/2010

Previous Stage

• Traceability is just to check required Capabilities• Check system Capabilities• Mere Exercise in Thoroughness & Completeness in project• To show the delivered features & functionalities• Sometime as just Customer asks

Current Stage

• Advent of Requirement Management tools it has helped support project management• Helps in Impact Analysis• Takes care of change management• Easy to handle Defect management• Process improvement substantially• Effective team communication• Better Project Control• Assured quality

BA Conference 13

Summary

7/17/2010

Traceability is “the ability to follow the life of a requirement, in both

forwards and backwards direction, i.e., from its origins, through its

development and specification, to its subsequent deployment and

use, and go through periods of ongoing refinement and iteration in

any of these phases”.

BA Conference 14

The Myth

7/17/2010

Do your duty to the best of your ability, result will automatically follow.

You may be doing your duty to the best of your ability, but without proper direction it maybe of no use. Use traceability Matrix…

BA Conference 15

Thank You

[email protected]

www.twitter.com/julenmohanty

Julen C Mohanty

www.linkedin.com/in/julenmohanty

7/17/2010

baconf - requirement traceability - julen mohanty

Documents