Presentation from June 26, 2002 Dinner Meeting

8/9/2019 Presentation from June 26, 2002 Dinner Meeting

1/22

Getting to Requirements:

The W5H Challenge

James N MartinAerospace Corporation

James R van Gaasbeek

Northrop Grumman Corporation


2/22

6/26/01 d6 2

The W5HTechnique

What, Who, Where,When, Why & How

a sound basis for questions in the

early stages of requirements definition


3/22

6/26/01 d6 3

Traditional Systems

Engineering Process


4/22

6/26/01 d6 4

As proposed by theproject sponsor

Asspecified inthe project request

As designed bythe analyst

As produced bythe bean counters

As installed at theuserssite

What the userwanted

The Systems Engineering

Challenge


5/22

6/26/01 d6 5

From Customer to Solution

Systems

Engineering

Customer

Requirements

System

Requirements &

SystemSolution

Traditional

Engineering Analysis

Tools & Techniques

From Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to SolutionFrom Customer to Solution


6/22

6/26/01 d6 6

Whats Wrong with this

Picture?

Assumptions:

Customer actually knows what they want

Customer can write good requirements

Customer represents all stakeholders

Systems

Engineering SystemRequirements &

SystemSolution

CustomerRequirements


7/22

6/26/01 d6 7

Where do Requirements Come

From?


8/22

6/26/01 d6 8

Where do Requirements Come

From?

Requirements are like

coal

Coal doesnt come from

anywhere

you have to GO GET IT !!!


9/22

6/26/01 d6 9

Getting to Requirements

Systems

Engineering

Initial

Requirements

Definition

Initial

Requirements

Wants, Needs &

Expectations

Constraints,Conditions

& Challenges

System

Requirements &

SystemSolution


10/22

6/26/01 d6 10

Initial Requirements Using Non-

EngineeringTechniques

Systems

Engineering

Initial

Requirements

Definition

Non-Traditional,

Non-Engineering Analysis

Tools & Techniques

Initial

Requirements

System

Requirements &

SystemSolution


11/22

6/26/01 d6 11

Many Stakeholders

Initial

Requirements

Definition

Customer

Users

Operators

Maintainers

Developers

Others

Requirements,Requirements,

Constraints &Constraints &ObjectivesObjectives

that definethe

problemspace

Stakeholder Wants,Stakeholder Wants,

Needs & ExpectationsNeeds & Expectations


12/22

6/26/01 d6 12

Example: The Four Whos

Who benefits?

Who pays?

Who supplies?

Who loses?


13/22

6/26/01 d6 13

Another Example:

The Five Whys

Why do you want a 10,000 GHz Pentium chip?

Graphics are too slow to appear on screen.

Why do you want fast graphics?

So I can more quickly get data for my analysis.

Why do you need graphics to get data?

I dont. Thats the only way I can get the data.

Why do you need the data?

To prepare my monthly progress report.

Why do you do this manually?

The data warehouse is too difficult to set up scripting

for automated data retrieval.


14/22

6/26/01 d6 14

Systems

Leadership

Systems-Unique Roles


15/22

6/26/01 d6 15

Different Questions for

Different Roles

Who

Engineers

Managers

Leaders

Questions

What?HowWell?

HowMuch?

When?

ForWhom?

Why?

Results

Functions &Performance

Cost &

Schedule

Purpose &

Vision


16/22

6/26/01 d6 16

BuildingFrameworks

W5HW5H

ElementsElements

AspectsAspectsof theof the

SystemSystem


17/22

6/26/01 d6 17

Zachman ArchitecturalFramework

for Information Systems

DATA FUNCTION NETWORK PEOPLE TIME MOTIVATION

SCOPE

ENTERPRISE

MODEL

SYSTEM

MODEL

TECHNOLOGY

MODEL

COMPONENTS

What How Where Who When Why


18/22

e.g. DATA

ENTE ISE A CHITECTU E - A F AMEWO K

Builder

SCO

E(CONTEXTUAL)

MODEL(CONCE

TUAL)

ENTE

ISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(

HYSICAL)

DETAILED

E

ESEN-TATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONINGENTE

ISE

DATA FUNCTION NETWO K

e.g. Data Defi

iti

Ent = FieldReln = Address

e.g.

hysical Data Model

Ent = Segment/Table/etc.

Reln =

ointer/Key/etc.

e.g. Logical Data Model

Ent = Data Entity

Reln = Data Relationship

e.g.Semantic Model

Ent = Business Entity

Reln = BusinessRelationship

List ofThingsImportant

to the Business

ENTITY = Class ofBusiness Thing

List of rocessesthe

Business

erforms

Function = Class of

Business

rocess

e.g. "Application Architecture"

I/O = User

iews

Proc.= Application Function

e.g. "System Design"

I/O = Screen/Device Formats

Proc.= ComputerFunction

e.g. "Program"

I/O = Control Block

Proc.= LanguageStmt

e.g. FUNCTION

e.g. BusinessProcess Model

Proc. = BusinessProcess

I/O = BusinessResources

List ofLocationsin whichthe Business Operates

Node = Major BusinessLocation

e.g. Logistics Network

Node = Business Location

Link = Business Linkage

e.g. "DistributedSystem

Node = I/S Function(Processor,Storage,etc)Link = Line Characteristics

e.g. "System Architecture"

Node = Hardware/SystemSoftware

Link = LineSpecifications

e.g. "Network Architecture"

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture"

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYCONSTRAINED

MODEL(PHYSICAL)

DETAILEDREPRESEN-

TATIONS(OUT-OF

CONTEXT)

Sub-

Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g.RuleSpecification

End = Sub-condition

Means = Step

e.g.Rule Design

End = Condition

Means = Action

e.g., BusinessRule Model

End = Structural AssertionMeans =Action Assertion

End = Business Objective

Means = BusinessStrategy

List ofBusiness Goals/Strat

Ends/Means=MajorBus. Goal/CriticalSuccess Factor

List ofEventsSignificant

Time = MajorBusiness Event

e.g.ProcessingStructure

Cycle = Processing CycleTime= SystemEvent

e.g. ControlStructure

Cycle = Component Cycle

Time = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g.SCHEDULE

e.g. MasterSchedule

Time = Business Event

Cycle = Business Cycle

List ofOrganizations

People = MajorOrganizations

e.g. Work Flow Model

People = Organization Unit

Work = WorkProduct

e.g. Human Interface

People = RoleWork = Deliverable

e.g.Presentation Architecture

People = User

Work = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportantto the Business


Copyright - John . Zachman, Zachman International

SCOPE(CONTEXTUAL)

Architecture

e.g.STRATEGY ENTERPRISE

e.g. BusinessPlan

TM

Zachman Institute for Framework dvancement - (810) 231-0531


19/22

6/26/01 d6 19

Requirements over the System

Life Cycle

DA A ON NETWO K PEOPLE TIME MOTIVATION

DE IGN &

DEVELOPMENT

TE T &

EVALUATION

P ODUCTION &

DEPLOYMENT

OPE ATION &

UPPPO T

ETI EMENT &

DI PO AL



20/22

6/26/01 d6 20

Getting to Requirements

Systems

Engineering

Initial

Requirements

Definition

Initial

Requirements

Wants, Needs &

Expectations

Constraints,

Conditions

& Challenges

System

Requirements &

SystemSolution


21/22

6/26/01 d6 21

The Eternal Question

Question:

Can the system do Ecks, Wye, andZee?

Answer:

It depends

on What, Who, Where, When, Why and How.


22/22

6/26/01 d6 22

Conclusions

The W5H technique is useful throughout

the system life cycle

Especially useful in the early stages when

the problem is fuzzy

Helps get all the issues on the table

Presentation from June 26, 2002 Dinner Meeting

Documents