Requirements Traceability

The Tie That Binds

J John JonesGreater Atlanta Chapter IIBA - October 28, 2014

Requirements TraceabilityWho is John Jones? Let’s “Google” me!

Requirements TraceabilityWho is John Jones?

Nope!

Requirements TraceabilityWho is John Jones? Google me!

Not quite

Requirements TraceabilityJ. John Jones

• At UPS-SCS sinceJuly 2013

• Nearly 36 years atEastman Kodak

• Began as Programmer• Added Designer• Added Analyst

• BS in Computer SciencePenn State University

• CBAP® in May 2014 UPS BA Certification in August 2014

LinkedIn: www.linkedin.com/jjohnjonesEmail: jjohnjjr@yahoo.com

Requirements TraceabilityWe like to connect things.

Requirements TraceabilityWe like to connect things.

Connect the dots.

Requirements TraceabilityWe like to connect things.

Connect the dots.

Sometimes, the connections are easy to see.

Requirements TraceabilityWe like to connect things.

Connect the dots.

Sometimes, the connections are easy to see.

Requirements TraceabilityWe like to connect things.

Connect the dots.

Sometimes because of the complexity and lack of framework, it’s hard to get the picture until we draw all the lines.

Requirements TraceabilityWe like to connect things.

Connect the dots.

Sometimes because of the complexity and lack of framework, it’s hard to get the picture until we draw all the lines.

Requirements TraceabilityWe like to connect things.

Genealogy

Requirements TraceabilityWe like to connect things.

Genealogy

Look back to know where we came from

Requirements TraceabilityWe like to connect things.

Genealogy

Look ahead to see the possibilities of wherewe are going.

Requirements TraceabilityBusiness Analysis – Trace Requirements

Requirements TraceabilityBusiness Analysis – Trace RequirementsBABOK 1.6 DraftREQUIREMENTS MANAGEMENT & PLANNINGMANAGE REQUIREMENTS SCOPEStructure Requirements for TraceabilityDescription:Requirements traceability supports the ability to trace a requirement through the development life cycle. The ability to track the requirements is an important technique used to detect missing functionality or identity if implemented functionality is not supported by a specific requirement.

Requirements TraceabilityBusiness Analysis – Trace RequirementsBABOK 1.6 DraftREQUIREMENTS MANAGEMENT & PLANNINGMANAGE REQUIREMENTS SCOPEStructure Requirements for TraceabilityDescription:Requirements traceability supports the ability to trace a requirement through the development life cycle. The ability to track the requirements is an important technique used to detect missing functionality or identity if implemented functionality is not supported by a specific requirement.

BABOK 2REQUIREMENTS MANAGEMENT & COMMUNICATIONManage Requirements TraceabilityDescription:Requirements are related to other requirements, to solution components, and to other artifacts such as test cases. “Tracing” a requirement refers to the ability to look at a requirement and the others to which it is related. Tracing links business requirements to stakeholder and solution requirements, to other artifacts produced by the team, and to solution components

Requirements TraceabilityBusiness Analysis – Trace RequirementsBABOK 1.6 DraftREQUIREMENTS MANAGEMENT & PLANNINGMANAGE REQUIREMENTS SCOPEStructure Requirements for TraceabilityDescription:Requirements traceability supports the ability to trace a requirement through the development life cycle. The ability to track the requirements is an important technique used to detect missing functionality or identity if implemented functionality is not supported by a specific requirement.

BABOK 2REQUIREMENTS MANAGEMENT & COMMUNICATIONManage Requirements TraceabilityDescription:Requirements are related to other requirements, to solution components, and to other artifacts such as test cases. “Tracing” a requirement refers to the ability to look at a requirement and the others to which it is related. Tracing links business requirements to stakeholder and solution requirements, to other artifacts produced by the team, and to solution components

BABOK 3 Public DraftREQUIREMENTS LIFE CYCLE MANAGEMENTTrace RequirementsDescription:Requirements traceability identifies and documents the lineage of each requirement, including its backward traceability, its forward traceability, and its relationship to other requirements. Traceability is used to help ensure that the solution conforms to requirements and to assist in scope, change, risk, time, cost, and communication management. It is also used to detect missing functionality or to identify if implemented functionality is not supported by a specific requirement.

Requirements TraceabilityWhy trace requirements?Requirements Allocation

Requirements Coverage

Impact Analysis

If requirement J is included in the solution scope, what else needs to be included in support of that requirement?

Does requirement G have the necessary related and supporting requirements?Is requirement H connected to the business objective?

If requirement D changes, what else has to be reviewed that is connected to the requirement?

Requirements TraceabilityWhat do we trace?

Requirements TraceabilityWhat do we trace? From BABOK 1.6 Draft

Requirements TraceabilityWhat do we trace? From BABOK 1.6 Draft

Requirements TraceabilityWhat do we trace? From BABOK 1.6 Draft

Requirements TraceabilityWhat do we trace? Example of a framework

Project ObjectivesProject

Objectives

Business RequirementsBusiness

Requirements

Functional RequirementsFunctional

RequirementsUse CasesUse Cases

BusinessRules

BusinessRules

Business Problem / Opportunity

Business Problem / Opportunity

Non-functional Requirements

Non-functional Requirements

Recommended traceability.

Required traceabilityBusiness Initiative

Business Initiative

Context Level Diagram

Context Level Diagram

External Agent

External Agent

Essential Business Processes

Essential Business Processes

CapabilityCapabilityBusiness Process

DiagramBusiness Process

Diagram

BusinessData EntityBusiness

Data Entity

User Interface Requirement

User Interface Requirement

Reporting RequirementReporting

Requirement

Service Level Agreement

Service Level Agreement

Business RequirementsBusiness

RequirementsUse CasesUse Cases

PDD/Scope Item

PDD/Scope Item

Can Trace Downstream to All Items

• Project focus

• Business level

• Project requirements about the business

• Project requirements about the solution

Requirements TraceabilityWhat do we trace?Agile methodology

to Sprints for implementation

Trace from Epic

to supporting User Stories

Requirements TraceabilityWhat do we trace?Agile methodology

to Sprints for implementation

Trace from Epic

to supporting User Stories

Connect related User Stories based on necessity, effort, value

Requirements TraceabilityHow can we record the traceability? (Coverage Matrix)

Requirements TraceabilityHow can we record the traceability? (Coverage Matrix)Spreadsheet

Simplest form

Requirements TraceabilityHow can we record the traceability? (Coverage Matrix)Spreadsheet

Multiple levels of traceability add difficulty to recording

A possible solution is to start withrows of all requirementscolumns of possible connectionsa cell is marked if there is a connection.

Additional sheets will look for marked intersections to highlight.

Requirements TraceabilityHow can we record the traceability?Requirement Management Tool

Requirements TraceabilityHow can we record the traceability?Requirement Management Tool

• Possible relationships are defined in the tool, noting those that are required for completeness.

• As a requirement is defined, relationships are built to the predefined connections.

• Tool reports will show either established relationships (impact analysis) or missing relationships (requirement coverage).

• Repository of related requirements provides impact analysis of the next project.

Requirements TraceabilityHow can we record the traceability?Genealogy software?

Relation from one level to the next level down is a parent-child relation.• From a Business Requirement to Functional

Requirements

Relation between items at the same level is difficult to show• Between Functional Requirements

Relations that relate from two levels is difficult• From a Project Objective to a Business Requirement• From an Essential Business Process to the same

Business Requirement

Requirements TraceabilityWhat are some best practice suggestions?

Requirements TraceabilityWhat are some best practice suggestions?

• Define your necessary relationships• Limited• Sensible directionality• Think of use by BAs and consumers

• Document relationships as elicitation progresses, not at the end

• Store Traceability Matrix with the requirements

Requirements Traceability

The Tie That Binds

• Relate requirements logically to each other

• Use those relationships in verifying coverage of deliverables or impact analysis of a change

• Maintain the relationships for reference in the next project

J John JonesGreater Atlanta Chapter IIBA - October 28, 2014

Requirements Traceability

The Tie That Binds

Questions?(for me or each other!)

J John JonesGreater Atlanta Chapter IIBA - October 28, 2014

Requirements Traceability

The Tie That Binds

Thank You!

J John JonesGreater Atlanta Chapter IIBA - October 28, 2014