requirements traceabiity - the tie that binds

Requirements Traceability

The Tie That Binds

J John JonesBuilding Business Capability - November 2, 2016

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


Requirements TraceabilityWho is John Jones?


Requirements TraceabilityWho is John Jones?

Nope!


Requirements TraceabilityJ. John Jones

• At UPS-SCS sinceJuly 2013

• Nearly 36 years atEastman Kodak

• Began as Programmer• Added Designer• Added Analyst

• BS in Computer SciencePennsylvania State University

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

LinkedIn: www.linkedin.com/jjohnjonesEmail: [email protected]

mailto:[email protected]

Requirements TraceabilityWe like to connect things.



Connect the dots.



Connect the dots.

Sometimes, the connections are easy to see.


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.


Genealogy



Genealogy

Look back to know where we came from



Genealogy

Look ahead to see the possibilities of wherewe are going.


Requirements TraceabilityBusiness Analysis – Trace Requirements


Requirements TraceabilityBusiness Analysis – Trace RequirementsBABOK® Guide 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® Guide 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® Guide 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® Guide 3REQUIREMENTS LIFE CYCLE MANAGEMENTTrace RequirementsDescription:Requirements traceability identifies and documents the lineage of each requirement, including its backward traceability, its forward traceability, and itsrelationship 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 there is implemented functionality that is not supported by anyrequirement.

Requirements TraceabilityWhy trace requirements?


Requirements TraceabilityWhy trace requirements?Impact Analysis If requirement J changes, what else has to

be reviewed for potential change?


Requirements TraceabilityWhy trace requirements?Impact Analysis

Discovery of inconsistencies and gaps

If requirement J changes, what else has to be reviewed for potential change?

Why does requirement G says the opposite of related requirement H?




Insight into scope and complexity of a change



If requirement J changes, how much work is needed to update all related requirements?




Insight into scope and complexity of a change



If requirement J changes, how much work is needed to update all related requirements?

Assessment of addressed and skipped requirements

If requirement D has a related requirement, but requirement E does not.


Requirements TraceabilityWhat do we trace?


Requirements TraceabilityWhat do we trace? From BABOK® Guide 1.6 Draft

Requirements TraceabilityWhat do we trace? From BABOK® Guide 3

Process Traceability Software Requirements Traceability


Requirements TraceabilityWhat do we trace? When working in Agile?


Requirements TraceabilityWhat do we trace? When working in Agile

Acceptance Criteria traces to User Story



Acceptance Criteria traces to User Storywritten on the same card



Acceptance Criteria traces to User Storywritten on the same card


Relationships betweenEpic and FeatureFeature and User StoryUser Story and Iteration

Requirements TraceabilityHow can we record the traceability?

Requirements TraceabilityHow can we record the traceability?

• Don’t explicitly

• Let the structure of your repository show the relationship

• Let the attributes of the requirement show the relationship

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

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

Simplest form



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



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



The Tie That Binds

Questions?(for me or each other!)



The Tie That Binds

Thank You!
