1

Chapter 5: The Five Steps in

Problem Analysis

The five steps in problem analysis.

Team
Skill 1
2
Problem Analysis
Problem analysis is the process of understanding
real-world problems and user needs and proposing
solutions to meet those needs.
A problem can be defined as the difference between
things as perceived and things as desired.

what is vs. what should be

what is given vs. what is needed

The goal of problem analysis is to gain a better
understanding of the problem being solved before
development begins.
!
The "ive #teps in Problem Analysis
1. $ain agreement on the problem definition.
2. %nderstand the root causes&the problem
behind the problem.
!. 'dentify the sta(eholders and the users.
). *efine the solution system boundary.
+. 'dentify the constraints to be imposed on the
solution.
)
#tep 1, $ain Agreement on the
Problem *efinition
-ne of the simplest ways to gain this agreement is to
simply write the problem down and see whether everyone
agrees.
Problem statement format,
.lement *escription
The problem of ... *escribe the problem
Affects ... 'dentify sta(eholders affected by the problem
And results in ... *escribe the impact of this problem on
sta(eholders and business activity
/enefits of a
solution ...
'ndicate the proposed solution and list a few
(ey benefits
+
.0ample, #ales -rder Problem
#tatement
1
#tep 2, %nderstand the 2oot 3auses
4The Problem /ehind the Problem5
2oot cause analysis is a systematic way of
uncovering the root6 or underlying6 cause of an
identified problem or a symptom of a problem.
.0ample, a mail-order catalogue company
addresses the problem of insufficient profitability

cost of non-conformance, cost of waste produced

Too much scrap
7
"ishbone *iagram of 2oot 3auses
8
Pareto 3hart of 2oot 3auses
9uality data demonstrates that many root causes are simply
not worth fi0ing.
A replacement of the e0isting sales order entry system can be
at least a partial solution to the problem of too much scrap.
:
%nfolding the Problem
Problem to Solve Technique Applied
;ac( of Profitability Total 9uality <anagement

3ost of 3onformance "ishbone *iagram

Too much scrap Pareto 3hart

'naccurate sales orders =ew software solution
1>
#tep !, 'dentify the #ta(eholders and
the %sers
%nderstanding the needs of the users and
other sta(eholders is a (ey factor in
developing an effective solution.
A sta(eholder is anyone who could be
materially affected by the implementation
of a new system or application.
11
#tep !, (Contd)
The following ?uestions can be helpful in identifying
sta(eholders

@ho are the users of the systemA

@ho is the customer 4economic buyer5 for the systemA

@ho else will be affected by the outputs the system

producesA

@ho will evaluate and approve the system when it is

delivered and deployedA

Are there any other internal or e0ternal users of the system

whose needs must be addressedA

@ho will maintain the new systemA

's there anyone else who caresA

12
.0ample, %sers and #ta(eholders of
#ales -rder .ntry #ystem
1!
#tep ), *efine the #olution #ystem
/oundary
@e divide the world in two,
1. -ur system
2. Things that interact with our system
#ystem /oundary is an interface between the
system and the environment or other systems
1)
What is a
system?
.0amples,
Political system
.ducational system
3omputer system
;ibrary system B
1+
#ystems <ain 3haracteristics
.0ists in an environment6
with a boundary.
Cas inputs and outputs.
Cas interfaces for communications.
<ay have sub-systems.
Cas a control mechanism6
with feedbac( and feed-forward.
11
Actors
An actor is someone or something outside the
system that interacts with the system
17
'dentifying Actors, Celpful 9uestions
@ho will supply6 use6 or remove information from
the systemA
@ho will operate the systemA
@ho will perform any system maintenanceA
@here will the system be usedA
@here does the system get its informationA
@hat other e0ternal systems will interact with the
systemA
These ?uestions help to construct a system perspective.
18
#ystem Perspective
't is a bloc( diagram that describes the boundaries of the
system6 the users6 and other interfaces
1:
#tep +, 'dentify the 3onstraints to /e
'mposed on the #olution
A constraint is a restriction on the degree of
freedom we have in providing a solution.
A variety of sources of constraints must be
considered.
2>
Potential #ources of #ystem 3onstraints
21
Potential #ources of #ystem 3onstraints
22
#ources of 3onstraints and Their
2ationale for #ales -rder .ntry #ystem
2!
Dey Points
Problem analysis is the process of understanding
real-world problems and userEs needs and
proposing solutions to meet those needs.
The goal of problem analysis is to gain a better
understanding of the problem being solved6 before
development begins.
To identify the root cause6 or the problem behind
the problem6 as( the people directly involved.
'dentifying the actors on the system is a (ey step in
problem analysis.
2)
@hatFs =e0tA
2+
Problem Analysis for <ore #pecific
Applications
3h 1, /usiness modeling6 techni?ues for
'#G'T applications
3h 7, #ystems .ngineering6 techni?ues for
embedded applications
... /ut weFll s(ip these.