SupplementaryDiscussion MODULE03

BCS/BIT313k Supplement Materials: Module 3
IDENTIFYING AND
CHOOSING A
RIGHT PROBLEM
PROBLEM ANALYSIS
 It’s the process of understanding and defining
the problem to be solved
 It’s not problem solving
 Problem solving identifies solutions that
conform to the needs and constrains of the
problem.
 Common Problem:
 Propose a solution too early
 Not considering the restrictions and possible
shortcuts associated with the problem
 Result : Incomplete or Excessive Solution
June Arreb C. Danila 1

STEPS FOR PROBLEM ANALYSIS

1. Define the Problem
2. Understand the Root Causes
3. Identify the Affected People
4. Define the Scope of the Solution
5. Identify Solution Constraints
STEP 1: DEFINE THE PROBLEMS

 The most difficult part but the most
important
 Can’t state the problem  Can’t even know
where to begin in solving it
 Some Helping Tips:
 Put the problems in writing
 Get multiple perspectives
 Look for deeper problems

STEP 2: UNDERSTAND THE ROOT

CAUSES
 What’s the problem behind the problem?
 Many times, The problems being seen is not
the main/core problem
 The problems is just the result of the root
causes
 Some Guide Questions:
 What is the primary problem?
 What are the contributing factors?
 Who knows about the problem?
STEP 3: IDENTIFY THE AFFECTED

PEOPLE
 Each problem will affect a given group of
people, known as stakeholders
 Each stakeholders have different needs and
concerns
 Possible Stakeholders:
 Customer – served by the solution
 User – apply or use the solution
 Management or Authorities – controls the
solution
 Project Sponsor – initiates or funds for the
solution

STEP 4: DEFINE THE SCOPE OF THE

SOLUTION
Scope of the Solution
 The boundaries need to work within to solve
the problem
 Addresses the things that are within control
by the proponent to address
 Two perspectives of a solution:
 Internal – focuses on the problem to be solved
from the perspective of the proponent
 External – focuses on the people or things that
interact from the outside such as customers,
suppliers and users
Scope of the Solution

STEP 5:
IDENTIFY SOLUTION CONSTRAINTS
Solution Constraints
 The barriers to solve the problem
 A know lack of something or an inhibitor

such as:
 Lack of time to complete the solution
 Lack of money to perform the solution
 Lack of people to work on the solution
 Lack of technology to give a leverage in solving the problem
 Political problems which inhibit people from cooperating in
solving the problem
 Environmental problems, which inhibit a solution due to the
nature of the business, technical environment, geographic
environment, etc.
CHOOSING A RIGHT PROBLEM

AND POSSIBLE SOLUTION
For BSCS:
 Guide Questions:
 Do the main problems has already an existing
solution?
 Do the main problems can be solve by creating
or applying (adapting or modifying) algorithm
(algorithmic-based solution)?
 What is/are the possible research area/s of the
defined solution to the problem (Tip: read and
study each research area)?

CHOOSING A RIGHT PROBLEM

AND POSSIBLE SOLUTION
For BSIT:
 Do the main problems has already an existing
solution?
 What is/are the possible IT research area/s of
the defined solution to the problem (Tip: read
and study each research area)?
SOURCES & REFERENCES:

 Rice, R. (n.d.). Solving the Right Problem – Step One
in Software Development. Requirements Articles |
Articles.
https://riceconsulting.com/home/index.php/Requirem
ents-Articles/solving-the-right-problem-step-one-in-
software-development.html
 CHED Memorandum Order(CMO) No 25, Series of

2015. https://ched.gov.ph/wp-
content/uploads/2017/10/CMO-no.-25-s.-2015.pdf

SOFTWARE
PLANNING
PROBLEM DOMAIN
 The area of expertise or application that
needs to be examined to solve a problem
 a set of circumstances to provide a
solutions.
 Example:
 Designing and developing a new system to
improve the enrolment procedures of UNC
 Developing a decision support system for
Evacuation planning and procedure of UNC-
DRRMC

SOFTWARE SYSTEM ANALYST

 One of the key persons during software
planning
 Do the key activities of System Analysis:
 Collecting and interpreting information
 Identifying the problem domain or the problems
 Decomposition of a solution
SOFTWARE SYSTEM ANALYST

 Qualities of a System Analyst:
 Problem solver
 Good communicator (technical and non-
technical)
 Self motivated and disciplined
 Has strong personal and professional ethics
 Knowledgeable and has expertise

INFORMATION GATHERING
The key resource of

successful software
project is
information
THE STAKEHOLDERS
 Possible sources of information
Some Universal Categories of

Stakeholders:
 End Users
• Direct Users
• Secondary Users
 Beneficiaries
 Authorities

THE STAKEHOLDERS
Categories of Users in an
Organization:
 Operational Users
 Supervisory Users
 Executive-level Users
INFORMATION GATHERING
METHODS
Interactive Methods:
 Interview
 Joint Application Design (JAD)
 Using Questionnaire
Unobtrusive Methods:
 Sampling
 Investigation
 Quantitative Documents
 Qualitative Documents

ASSIGNMENT TASK
(INDIVIDUAL TASK)
 Task: Essay discussion of initial software
plan
 What is your target problem domain?
 What specific customer problems and needs you
want to address?
 Who is your stakeholders and why?
 What information and data you will gather from
each stakeholder?
 What information gathering methods you will
use to gather that information?
INITIAL PROJECT REQUIREMENT

TASK
 Summarize each group member essay
discussion and fill up the
Project Requirement 1: Initial Software
Plan form

SupplementaryDiscussion MODULE03

Uploaded by

Copyright:

Available Formats

SupplementaryDiscussion MODULE03

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SupplementaryDiscussion MODULE03

Uploaded by

Copyright:

Available Formats

BCS/BIT313k Supplement Materials: Module 3

June Arreb C. Danila 1

STEPS FOR PROBLEM ANALYSIS

STEP 1: DEFINE THE PROBLEMS

June Arreb C. Danila 2

STEP 2: UNDERSTAND THE ROOT

STEP 3: IDENTIFY THE AFFECTED

June Arreb C. Danila 3

STEP 4: DEFINE THE SCOPE OF THE

Scope of the Solution

June Arreb C. Danila 4

 A know lack of something or an inhibitor

CHOOSING A RIGHT PROBLEM

June Arreb C. Danila 5

CHOOSING A RIGHT PROBLEM

SOURCES & REFERENCES:

 CHED Memorandum Order(CMO) No 25, Series of

June Arreb C. Danila 6

June Arreb C. Danila 7

SOFTWARE SYSTEM ANALYST

SOFTWARE SYSTEM ANALYST

June Arreb C. Danila 8

The key resource of

Some Universal Categories of

June Arreb C. Danila 9

 Joint Application Design (JAD)

June Arreb C. Danila 10

INITIAL PROJECT REQUIREMENT

June Arreb C. Danila 11

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.