[go: up one dir, main page]
Scribd
Upload
2 views9 pages

Problem Solving

The document outlines a classical problem-solving approach for building systems, emphasizing the importance of understanding the problem context, defining requirements, and evaluating solutions. It distinguishes between symptoms and underlying problems, highlighting the need for a systems perspective in business contexts. Techniques such as object-oriented analysis and the use of Unified Modeling Language (UML) are suggested for modeling and analyzing business problems.

Uploaded by

gufran.qureshi506
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
2 views9 pages

Problem Solving

The document outlines a classical problem-solving approach for building systems, emphasizing the importance of understanding the problem context, defining requirements, and evaluating solutions. It distinguishes between symptoms and underlying problems, highlighting the need for a systems perspective in business contexts. Techniques such as object-oriented analysis and the use of Unified Modeling Language (UML) are suggested for modeling and analyzing business problems.

Uploaded by

gufran.qureshi506
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 9

Problem-Solving Approach

 A methodology is, first and foremost, a problem-solving


approach to building systems.

 The classical problem-solving approach is as follows:

 Study and understand the problem (opportunity, and/or directive) and


its system context.
 Define the requirements of a suitable solution.
 Identify candidate solutions and select the ``best'' solution.
 Design and/or implement the solution.
 Observe and evaluate the solution's impact, and refine the solution
accordingly.
Defining a problem in a systems
context
• A problem
– a basic condition that is causing undesirable
results

• Symptoms
– are signals of an underlying problem

Separate symptoms from problems!


In the business world all you see are
symptoms

How to see unstructured problems and


solve them?

Models and systems approach help you.


Systems context
The business organization or process in
which a problem arises could be viewed as
a system of
• input,
• processing
• output
• feedback and
• control components
Symptom: Sales are declining
Problem: Salespersons are loosing orders, because they cannot get
info on product prices and availability
Techniques to examine business
problems:
• Identification business objects, how they
are related , and analyzing the data that is
needed by end users

• Focusing on business processes and


activities
Modeling objects:
Object-oriented Analysis
Account

Number
Name
Client...
Open account
Close account

Savings Account Checking Account


Modeling objects:
Event-driven Approach
When some business event occurs, an object
function is called or property is modified

Benefits of OOA: changes are made only to


needed classes of objects
Analyzing Systems:
Unified Modeling Language (UML)
Example: Rolling Thunder Bicycles

You might also like