4. ABOUT THE
PROJECT
2. Research the stages of the problem
solving process-problem definition,
problem analysis (including functional
and non-functional requirements),
identify and evaluate possible solutions.
6. Problem solving
Problem definition: A formal statement of a problem that needs to be
solved. It is usually written in terms of what the problem is, what is
required to solve it, and what the goal is. The problem definition should
be clear, concise, and easy to understand.
Diagnose the circumstance to keep your focus on the problem and not
merely its indications. Use cause-and-effect diagrams to establish and
examine root causes, and flowcharts to show the anticipated steps of a
process while solving problems.
7. Problem solving
Key problem-solving steps are explained in the sections that follow.
These actions encourage the participation of interested parties, the use of
factual information, the comparison of expectations with reality, and the
concentration on a problem's underlying causes. You ought to start by:
8. Problem Solving
Reviewing and capturing the functioning of current processes
(i.e., who does what, with what information, using what tools,
communicating with what organizations and individuals, in
what time frame, using what format).
● Evaluating the possible impact of new tools and revised
policies in the development of your "what should be"
model.
● In order to effectively manage and run a successful
organization, leadership must guide their employees
and develop problem-solving techniques.
10. Problem Analysis
Problem analysis: the process of defining a problem and
decomposing the overall system into smaller parts to identify
possible inputs, processes and outputs associated with the problem.
In analyzing a problem, you should consider the variables that
make up the problem.
Compiling the information you currently have on the problem and
requirements will generate a clear image in your head of the
possible means of solving it.
In the compilation of information you will need to know the
requirements for creation of the application or algorithm. These
requirements are divided into functional and non-functional
requirements.
11. Problem Analysis
Functional requirements meaning what is directly required from
the program (what the program does). Non-functional
requirements meaning the parameters that the program has to
function at in order to run at scale.
Let us use an example of a program that plays chess. The
functional requirements are the program moves the pieces in the
way chess is standardized to play and visualizes this to the
person/people playing. The non-functional requirements would
consider the factors such as the hardware running the game and
the time allotted to make the game and things such as:
12. Problem Analysis
The algorithm used to calculate the moves.
OR
The way the game is visualized would be considered.
3D
2D
14. Identifying & Evaluating Solutions
This step in the problem solving process consists of brainstorming:
concentrating on generating as many solutions as possible without
pre-judging any potential solutions but treating each idea as a new idea
and worthy of consideration.
Evaluation which is the process that allows us to make sure our solution
does the job it has been designed to do and to think about how it could be
improved. You will be required to assess each solution in terms of
efficiency, ease of implementation etc. Apply screening criteria to
eliminate potential solutions which are not suitable (does not solve the
problem); feasible (possible) or acceptable (worth the risk /worth the
cost/legal).
15. Identifying & Evaluating Solutions
When evaluating a solution one should consider the following:
● If A particular alternative will solve the problem without causing other unexpected
problems
● If all Individuals involved in the process will accept the solution
● If the solution/alternative fits within the organizational constraints (time, budget,
resources etc).
