Please enable JavaScript.
Coggle requires JavaScript to display documents.
Ch.21 Problem-solving Procedures - Coggle Diagram
Ch.21 Problem-solving Procedures
21.1 Problem-solving Concepts
Problem-solving
The need for a systematic way of solving problems
21.2 Problem-solving Procedures
Six-step procedure of problem-solving
Promblem Identification
Promblem analysis
Algorthm design
Developing a solution
Debugging and testing
Documentation
Although it appears at the last stage of the problem-solving procedure, it should be carried
out throughout the whole process.
Describe in detail what a certain program is for and how it is desinged, developed and tested.
Desinging
The process of locating and fixing defects in a program
The checking processes required to ensure that a program fulfils the purposes for which it
was created
Testing
Ensure that a program works and is free of error
There are various techniques we can adopt in developing a solution for a problem.
Each module has a specification
A module specification helps us understand how data is transmitted among modules.
Includes
Outputs (information retured)
Processing steps (logic used)
A description of inputs (data recieves)
A finite sequence of steps arranged in specific logical order to generate a solution to a problem
Two common ways to design and represent algorithms
Pseudocode
to represent an algorithm in narrative form
Flow chart
to represent the logic and actions of an algorithm graphically
In-depth consideration of the identified problem
Look into the problem from different perspectives in order to diagnose it correctly and
gain a full picture of it.
We can use an Input-Proces-Output Chart (IPO chart) to analyze the problem.
The initial step of solving a problem
Obtain a precise definition of the problem
Asking queation about the problem can help identify the problem more clearly.
21.4 Different Ways to Solve the Same Problems
Solve a problem systematically by top-down or bottom-up approach
The botton-up appreach
Start at the component level or the concrete level and the components are grouped
together to form a system.
The top-down appreach
Start at the system level or the abstract level and divides the task into several
manageable modules.