Three Reasons to Throw Away your

Requirements Documents Sponsored by

Link to watch webcast recording on-demand

Featured Presenters

Our knowledgeable speaker today is:

Andy Gurd

Senior Go-To-Market Manager

IBM Rational

Follow on Twitter: @andygurd

or find me on LinkedIn

The ROI of better Requirements Management

$0

$50,000

$100,000

$150,000

$200,000

$250,000

$300,000

$350,000

$400,000

$450,000

$500,000

Before After

Rework

Testing

69% net reduction in the cost of quality

Return on investment within 6 months

>75% improvement in productivity

“In 6 months since deployment we’ve seen a 69% net reduction in the cost of test preparation, testing, and rework by using IBM Rational DOORS and an improved requirements management process.

Our team is testing and reworking comparable functionality in one sixth the calendar time and one third the person hours. And we are able to better meet the needs of our stakeholders."

Mia McCroskey, Senior Project Manager for Product Development at Emerging Health, Montefiore IT

Link to full case study

Images courtesy of:

scottchan / www.freedigitalphotos.net

siraphat / www.freedigitalphotos.net

digitalart / www.freedigitalphotos.net

Reason #1 - Collaboration

• Screenplay/script like

requirements

• Script / requirements needed to

determine impact of any changes

• Script / requirements form the hub

for co-ordinating successful

teamwork

Requirements collaboration -

Documents/Spreadsheets

V1

Requirements Analyst /

Systems Engineer

Engineering

Manager Engineering Team

User Reqts User Reqts

Comment on User Reqts

V2

Technical Requirements Technical Requirements

V1 V2

Requirements collaboration –

Integrated RM Tool Systems Engineer

Project Manager

“I need to implement a process that enforces

traceability between all my project

information and supply chain”

“I need to be able to manage the

relationship between customer

requirements and downstream design”

QA Manager “Everyone need to be following

the same process and creating

the same metrics and reports”

Engineers “I need access to a

live central

repository and to

know that I am

looking at the latest

approved

requirements”

Developers “I need a process

that ensures

traceability between

my requirements

and changes. I

need to know the

status of those

changes”

But I’m comfortable with docs and

spreadsheets, wont this be a difficult

transition?

• Familiar hierarchical structure of a document and rich text editing

• Columns like a spreadsheet for additional properties

• Management of individual requirements for tracking and reuse

In-Context Collaboration

Collaboration through

information discussions or

by formal review

Email notification available

for review updates

Dashboard widgets to show

review participation and

status

Notification to personal dashboard

Comments can be

used inside or outside

of a review

© 2013 IBM Corporation

Software and Systems Engineering | Rational

The need:

MBDA’s design teams were widely dispersed, with the challenge to share and

unify the specific knowledge of local individual engineers and designers.

Communication and traceability across the company's engineering organizations

were complex. They needed to improve and standardize its approach for defining,

communicating and analyzing the design for each missile system.

The solution:

The client deployed Rational DOORS® and Rhapsody® to provide a model-based

systems engineering platform to help widely distributed design and engineering

teams analyze and communicate the software, mechanical and electrical

requirements of its various missile systems.

The benefits:

Reduced typical system design time, speeding time to market, increasing

customer satisfaction and providing a critical differentiator in a highly

competitive market.

Speeds identification of design incompatibilities, helping to avoid critical

programming delays.

Eased identification and communication of defects in the system, component

requirements and designs.

Solution components:

• IBM® Rational® DOORS®

• IBM Rational Rhapsody®

• IBM Rational Rhapsody Gateway

Aerospace and Defense | Complex and Embedded Systems | Systems Engineering | United States

MBDA Missile Systems Increased customer satisfaction and provided a critical differentiator in a highly competitive market

9

“MBDA has the ability to define

and model all the requirements

of a complex missile system very

early in the development process.

This differentiates MBDA

capabilities in a highly competitive

global marketplace.”

MBDA Missile Systems

Link to Case Study

Image courtesy of Bill Longshaw /

www.freedigitalphotos.net

Reason #2 – Traceability

• Breadcrumb trail = weak

traceability

• Product & systems development

needs stronger traceability

• Need easy way to create manage

and traceability

• Traceability helps with

conformance to customer

requirements and compliance to

regulations

Traceability

Use Cases

Test Cases

Stakeholder

Requirements

Systems

Requirements

Subsystem

Requirements

Test Cases

Standards

Related Blog Posts:

What is Traceability?

The uses and value of traceability

Traceability – Documents/Spreadsheets

Multiple documents to manage Need a way to identify requirements

If a requirement changes, you need to open multiple documents to determine impact and update

Traceability – Integrated RM Tool

• Multi-level graphical analysis

• Traceability views

System

Requirements

Linked

Subsystem

Requirements

Linked

Stakeholder

Requirements

© 2013 IBM Corporation

Software and Systems Engineering | Rational

Invensys Rail Dimetronic Speeds innovation with a unified platform for multi-stage development processes

14 Electronics | Complex and Embedded Systems | Real-time and embedded | Spain

Solution components:

• IBM® Rational® Rhapsody

• IBM Rational DOORS

• IBM Rational Synergy

• IBM Rational Change

• IBM Rational Publishing Engine

• IBM Software Services

The need:

Faced with demands to keep pace with railway system standards while

simultaneously meeting customer needs and ensuring its systems’ integration

with other railway technologies, Invensys Rail Dimetronic needed to modernize

its development processes, from code management to change management.

The solution:

Incorporated system intelligence into its development process by deploying an

application development platform that leverages signaling system usage results to

model system reliability and to highlight areas requiring improvement. Developers

can analyze requirements changes, quickly modeling, configuring, validating and

demonstrating the integration of components. Modeling code changes in real-time

supports early error correction. Tracking changes through automated

requirements management allows compliance with traceability and safety

standards.

The benefits:

Reduced time-to-market for signaling systems products by 40%.

Facilitated 100% compliance rate with ERTMS standards for code

traceability and safety.

Reduced cost and risks of development and documentation.

“Innovation and process flexibility

are important in allowing us to

differentiate our offerings. We’re

now able to ensure that our design

can be rapidly adapted, not only

to customer needs, but to changing

ERTMS requirements,

at a reasonable cost.”

Francisco Lozano

ERTMS Program Manager

Link to Case Study

Try to hold back the tide Go with the flow Take control

Images courtesy of

George Stojkovic / www.freedigitalphotos.net

Graeme Weatherston / www.freedigitalphotos.net

Reason #3 – Agility

• Approaches to managing

change to requirements

Supplementing the backlog with more

granular, contextual requirements

Roadmap/Strategy,

Enhancement

Requests,

Problem Reports

Prioritized Backlog

User Story 1

User Story 2

Epic 1

User Story 3

…..

Requirements and supporting information

Scenario

Storyboard

Note

User Requirement A

User Requirement B

User Requirement C

…..

Prioritized User Stories

& Epics

Trace to

Requirements Modules ,

Requirements &

supporting artifacts

Backlog and requirements

Summary

• Agility without control = chaos!

– Requirements need to persist

beyond an iteration

– Requirements and supporting

information add more granularity to

user stories and epics

– Link requirements and task

management for traceability

Summary

• Agility without control = chaos!

• Traceability provides rationale

and context

– Retrace to key design decisions and

customer requirements

– RM tool makes traceability a benefit

not an overhead

Summary

• Agility without control = chaos!

• Traceability provides rationale and

context

• Effective collaboration is essential

– Must have access to the right version

/ view of requirements for your role

– RM tool provides informal and formal

collaboration techniques

Summary

• Agility without control = chaos!

• Traceability provides rationale and

context

• Effective collaboration is essential

• Improving your Requirements

Management process supported

by an RM tool can deliver

significant quantitative and

qualitative benefits

$0

$50,000

$100,000

$150,000

$200,000

$250,000

$300,000

$350,000

$400,000

$450,000

$500,000

Before After

Rework

Testing

Thank you for attending

Please visit our sponsor and any of the resources below:

• Video: Better requirements. Enhanced business agility. Fast ROI.

Featuring Emerging Health, Montefiore IT

• Requirements Management on ibm.com

• IBM Rational DOORS Next Generation on jazz.net

• IBM Requirements Management blog:

http://ibm.co/requirementsmanagementblog

• Follow on Twitter: @rationalrdm

• DOORS LinkedIn Group: linkd.in/WWSF6a