© 2006 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice

Lesson learned in applying requirements

management (RM)

Some of the slides © Integrate 2006

Updated: 1-2-07

HP-Indigo: Hagit Tsafriri, Shmulik Matis, Tsahi Rosenbaom, Shamai Opfer

Methoda: Ran Lavi

3 20-Nov-2006 RM for INCOSE

About HP-Indigo

• Examples for Series 1 presses:

• Examples for series 2 presses:

4 20-Nov-2006 RM for INCOSE

Requirements – the effect on quality

5 20-Nov-2006 RM for INCOSE

Requirements definition – a challenge

6 20-Nov-2006 RM for INCOSE

The basic requests process

• In HP-Indigo we defined a special type of requirement: A REQUEST

• A request is a requirement that is allocated to someone else than yourself

Person A Person B

Satisfy request:

Define requirements

Issue a request

7 20-Nov-2006 RM for INCOSE

The basic method – for multi-product

B A

A spec

Request1 product X

B spec

Requirement1

product X ‘assigned to’ B link

Requirement2 product X

Requirement1 product X

link

Request2 Requirement3

link

‘assigned to’ B

product Y product Y

,Y

8 20-Nov-2006 RM for INCOSE

Requirements hierarchy

Marketing System

Sub-

system

Sub-

system

SW

system

SW

sub-

system

SW

sub-

system

SW

sub-

system

9 20-Nov-2006 RM for INCOSE

Inheritance flow – process overview

Leading

product

Sub-

system

Sub-

system

Derived

product

Inherit

Delta

request

10 20-Nov-2006 RM for INCOSE

Progress monitoring

Number of requirements and % approved

0

1000

2000

3000

4000

5000

6000

7000

8000

900004/0

9/2

005

27/0

9/2

005

02/1

1/2

005

06/1

2/2

005

03/0

1/2

006

07/0

2/2

006

09/0

3/2

006

28/0

4/2

006

16/0

5/2

006

12/0

6/2

006

02/0

7/2

006

09/0

7/2

006

23/0

7/2

006

15/0

8/2

006

27/0

8/2

006

22/1

0/2

006

0%

10%

20%

30%

40%

50%

60%

Parameters

Requirements

%_approved

שחרר שדות עמוד כאן

Date

Data

11 20-Nov-2006 RM for INCOSE

Traceability status monitoring

Overall number of requests to software and number of satisfied requests

0

200

400

600

800

1000

1200

1400

04/0

9/2

005

27/0

9/2

005

02/1

1/2

005

06/1

2/2

005

03/0

1/2

006

07/0

2/2

006

09/0

3/2

006

28/0

4/2

006

16/0

5/2

006

12/0

6/2

006

02/0

7/2

006

09/0

7/2

006

23/0

7/2

006

15/0

8/2

006

27/0

8/2

006

22/1

0/2

006

Assigned_ Satisfied_

12 20-Nov-2006 RM for INCOSE

Requirements distribution

3403

770

4514

2866

Marketing

System

Sub-System

Software

13 20-Nov-2006 RM for INCOSE

Lesson learned

• Management sponsorship is a must

• “Pay as you go” – don’t attempt to solve all your problems at the start

• We applied distributed system engineering – every sub system owner is managing his own requirements and interfaces – controversial

• RM made it possible to measure progress of requirements definitions, implementation and verification

• Timing (when to apply RM in a project life cycle)

General

14 20-Nov-2006 RM for INCOSE

Lesson learned

• Your opposition today might become your biggest support in the future (or not…)

• Holding hands is a must

• Training of new users must be 1/1

• Group workshops for advanced users is very beneficial

• Updating spec’s is perceived as low priority documentation task, compared to other “burning” tasks of the designer – requires on going education effort

People

15 20-Nov-2006 RM for INCOSE

Lesson learned

• Facilitated interaction between different disciplines – engineers, scientists, etc.

• Improved communications between remote sites but required special attention

• Requirements and parameters, together with design considerations and links, lead to comprehensive documentation data base

− Achieved structured spec’s by using predefined templates (e.g. industry std, MIL)

• Requirements with "TBD's" that are used as flags and place holders are problematic – horizon and/or assumptions are also needed!

Collaboration

16 20-Nov-2006 RM for INCOSE

The road never ends

17 20-Nov-2006 RM for INCOSE

תודה