Problem
Analysis
SENG 231 - Chapter 5
Team Skill # 1
Problem Analysis
• Problem analysis is the process of understanding real-world
problems and user needs and proposing solutions to meet
those needs.
What is Problem ?
• 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”
Goal of problem analysis
• The goal of problem analysis is to gain a better understanding
of the problem being solved before development begins.
The Five Steps in Problem Analysis
1. Gain agreement on the problem definition.
2. Understand the root causes—the problem behind the
problem.
3. Identify the stakeholders and the users.
4. Define the solution system boundary.
5. Identify the constraints to be imposed on the solution.
Step 1: Gain Agreement on the Problem
Definition
• One of the simplest ways to gain this agreement is to simply
write the problem down and see whether everyone agrees.
• Problem statement format:
Example: Sales Order Problem Statement
Step 2: Understand the Root Causes (The
Problem Behind the Problem)
• Root cause analysis is a systematic way of uncovering the root,
or underlying, cause of an identified problem or a symptom of
a problem.
• Example: a mail-order catalogue company addresses the
problem of insufficient profitability
• cost of non-conformance: cost of waste produced
• Too much scrap
Fishbone Diagram of Root Causes
Pareto Chart of Root Causes
• Quality data demonstrates that many root causes are simply not
worth fixing.
• A replacement of the existing sales order entry system can be at
least a partial solution to the problem of too much scrap.
Unfolding the Problem
Problem to Solve Technique Applied
• Lack of Profitability Total Quality Management
↓
• Cost of Conformance Fishbone Diagram
↓
• Too much scrap Pareto Chart
↓
• Inaccurate sales orders New software solution
Step 3: Identify the Stakeholders and the
Users
• Understanding the needs of the users and other stakeholders
is a key factor in developing an effective solution.
• A stakeholder is anyone who could be materially affected by
the implementation of a new system or application.
Step 3: (Cont’d)
• The following questions can be helpful in identifying
stakeholders
• Who are the users of the system?
• Who is the customer (economic buyer) for the system?
• Who else will be affected by the outputs the system produces?
• Who will evaluate and approve the system when it is delivered
and deployed?
• Are there any other internal or external users of the system
whose needs must be addressed?
• Who will maintain the new system?
• Is there anyone else who cares?
Example: Users and Stakeholders of Sales
Order Entry System
Step 4: Define the Solution System Boundary
• We divide the world in two:
1. Our system
2. Things that interact with our system
• System Boundary is an interface between the system and
the environment or other systems
What is a system?
• Examples:
• Political system
• Educational system
• Computer system
• Library system …
Systems Main Characteristics
• Exists in an environment,
• with a boundary.
• Has inputs and outputs.
• Has interfaces for communications.
• May have sub-systems.
• Has a control mechanism,
• with feedback and feed-forward.
Actors
• An actor is someone or something outside the system that
interacts with the system
Identifying Actors: Helpful Questions
• Who will supply, use, or remove information from the system?
• Who will operate the system?
• Who will perform any system maintenance?
• Where will the system be used?
• Where does the system get its information?
• What other external systems will interact with the system?
These questions help to construct a system perspective.
System Perspective
• It is a block diagram that describes the boundaries of the
system, the users, and other interfaces
Step 5: Identify the Constraints to Be Imposed
on the Solution
• 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.
Potential Sources of System Constraints
Potential Sources of System Constraints
Sources of Constraints and Their Rationale for
Sales Order Entry System
Key Points
• Problem analysis is the process of understanding real-world
problems and user's needs and proposing solutions to meet
those needs.
• The goal of problem analysis is to gain a better understanding
of the problem being solved, before development begins.
• To identify the root cause, or the problem behind the
problem, ask the people directly involved.
• Identifying the actors on the system is a key step in problem
analysis.