Presented on Oct 28, 2014 at the Greater Atlanta Chapter IIBA. People seek to make connections of items to make sense of them in a larger context. As children (or adults), we connect the dots to form a picture of something recognizable. As a business analyst, we connect requirements and other analysis outputs to get the bigger picture of an initiative and to check the completeness of our work. We will explore how IIBA® has defined requirement traceability, how traceability works, and the benefits of the practice to the current project and future analysis.

1. Requirements Traceability
The Tie That Binds
J John Jones
Greater Atlanta Chapter IIBA - October 28, 2014

2. Requirements Traceability
Who is John Jones? Let’s “Google” me!

3. Requirements Traceability
Who is John Jones?
Nope!

4. Requirements Traceability
Who is John Jones? Google me!
Not quite

5. Requirements Traceability
J. John Jones
• At UPS-SCS since
July 2013
• Nearly 36 years at
Eastman Kodak
• Began as Programmer
• Added Designer
• Added Analyst
• BS in Computer Science
Penn State University
• CBAP® in May 2014 UPS BA Certification in August 2014
LinkedIn: www.linkedin.com/jjohnjones
Email: jjohnjjr@yahoo.com

6. Requirements Traceability
We like to connect things.

7. Requirements Traceability
We like to connect things.
Connect the dots.

8. Requirements Traceability
We like to connect things.
Connect the dots.
Sometimes, the connections
are easy to see.

9. Requirements Traceability
We like to connect things.
Connect the dots.
Sometimes, the connections
are easy to see.

10. Requirements Traceability
We 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.

11. Requirements Traceability
We 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.

12. Requirements Traceability
We like to connect things.
Genealogy

13. Requirements Traceability
We like to connect things.
Genealogy
Look back to know where we
came from

14. Requirements Traceability
We like to connect things.
Genealogy
Look ahead to see the
possibilities of where
we are going.

15. Requirements Traceability
Business Analysis – Trace Requirements

16. Requirements Traceability
Business Analysis – Trace Requirements
BABOK 1.6 Draft
REQUIREMENTS
MANAGEMENT &
PLANNING
MANAGE
REQUIREMENTS SCOPE
Structure Requirements
for Traceability
Description:
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.

17. Requirements Traceability
Business Analysis – Trace Requirements
BABOK 1.6 Draft
REQUIREMENTS
MANAGEMENT &
PLANNING
MANAGE
REQUIREMENTS SCOPE
Structure Requirements
for Traceability
Description:
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 2
REQUIREMENTS MANAGEMENT
& COMMUNICATION
Manage Requirements
Traceability
Description:
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

18. Requirements Traceability
Business Analysis – Trace Requirements
BABOK 1.6 Draft
REQUIREMENTS
MANAGEMENT &
PLANNING
MANAGE
REQUIREMENTS SCOPE
Structure Requirements
for Traceability
Description:
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 2
REQUIREMENTS MANAGEMENT
& COMMUNICATION
Manage Requirements
Traceability
Description:
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 Draft
REQUIREMENTS LIFE CYCLE
MANAGEMENT
Trace Requirements
Description:
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.

19. Requirements Traceability
Why 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?

20. Requirements Traceability
What do we trace?

21. Requirements Traceability
What do we trace? From BABOK 1.6 Draft

22. Requirements Traceability
What do we trace? From BABOK 1.6 Draft

23. Requirements Traceability
What do we trace? From BABOK 1.6 Draft

24. Requirements Traceability
What do we trace? Example of a framework
Business Problem /
Business Required traceability
Initiative
Project
Objectives
Project
Objectives
Business
Business
Requirements
Requirements
Functional
Requirements
Functional
Requirements
PDD/Scope
UUses eC aCsaesses
Business
Rules
Business
Rules
Business Problem /
Opportunity
Opportunity
Non-functional
Requirements
Non-functional
Requirements
Recommended traceability.
Business
Initiative
Context Level
Context Level
Diagram
Diagram
External
Agent
External
Agent
Essential
Business
Processes
Essential
Business
Processes
CaCpaapbaibliitliyty
Business Process
Business Process
Diagram
Diagram
Business
Data Entity
Business
Data Entity
User Interface
Requirement
User Interface
Requirement
Reporting
Requirement
Reporting
Requirement
Service Level
Agreement
Service Level
Agreement
Business
Business
Requirements
Requirements
UUses eC aCsaesses
PDD/Scope
Item
Item
Can Trace Downstream to All Items
• Project focus
• Business level
• Project
requirements
about the
business
• Project
requirements
about the
solution

25. Requirements Traceability
What do we trace?
Agile methodology
to Sprints for implementation
Trace from Epic
to supporting User Stories

26. Requirements Traceability
What 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

27. Requirements Traceability
How can we record the traceability? (Coverage Matrix)

28. Requirements Traceability
How can we record the traceability? (Coverage Matrix)
Spreadsheet
Simplest form

29. Requirements Traceability
How can we record the traceability? (Coverage Matrix)
Spreadsheet
Multiple levels of traceability add difficulty to recording
A possible solution is to start with
rows of all requirements
columns of possible connections
a cell is marked if there is a connection.
Additional sheets will look for marked intersections to
highlight.

30. Requirements Traceability
How can we record the traceability?
Requirement Management Tool

31. Requirements Traceability
How 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.

32. Requirements Traceability
How 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

33. Requirements Traceability
What are some best practice suggestions?

34. Requirements Traceability
What 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

35. 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 Jones
Greater Atlanta Chapter IIBA - October 28, 2014

36. Requirements Traceability
The Tie That Binds
Questions?
(for me or each other!)
J John Jones
Greater Atlanta Chapter IIBA - October 28, 2014

37. Requirements Traceability
The Tie That Binds
Thank You!
J John Jones
Greater Atlanta Chapter IIBA - October 28, 2014