CMPD114: C Programming: Chapter 2: Problem Solving
CMPD114: C Programming: Chapter 2: Problem Solving
CMPD114: C Programming: Chapter 2: Problem Solving
SECTION 1
SECTION 2
Specification of Needs
To understand exactly:
what the problem is what is needed to solve it what the solution should provide if there are constraints and special conditions.
Problem Analysis
In the analysis phase, we should identify the following:
Inputs to the problem, their form and the input media to be used Outputs expected from the problem, their form and the output media to be used Special constraints or conditions (if any) Formulas or equations to be used
prepared by NI, edited by MAF
An algorithm is a sequence of a finite number of steps arranged in a specific logical order which, when executed, produces the solution for a problem. An algorithm must satisfy these requirements:
It may have an input(s) It must have an output It should not be ambiguous (there should not be different interpretations to it)
prepared by NI, edited by MAF Every step in algorithm must be clear as what
Control Structure
In order to tackle a problem, we need
a correct algorithm to apply the algorithm at the 'good' moment to decide which algorithm to apply (sometimes there are more than one, depending on conditions) to know if a certain operation must be repeated In short: we need a suitable Control Structure In 1966, two researchers, C. Bohn and G. Jacopini, demonstrated that any algorithm can be described using only 3 control structures: sequence, selection and repetition.
prepared by NI, edited by MAF
Pseudocodes
A pseudocode is a semiformal, Englishlike language with limited vocabulary that can be used to design and describe algorithms. Criteria of a good pseudocode:
Easy to understand, precise and clear Gives the correct solution in all cases Eventually ends
prepared by NI, edited by MAF
Example 4
Note that in this algorithm, we are using both the sequence and repetition control structure
prepared by NI, edited by MAF
date
Flowcharts
Flowcharts is a graph used to depict or show a step by step solution using symbols which represent a task. The symbols used consist of geometrical shapes that are connected by flow lines. It is an alternative to pseudocoding; whereas a pseudocode description is verbal, a flowchart is graphical in nature.
prepared by NI, edited by MAF
Flowchart Symbols
Terminal symbol - indicates the beginning and end points of an algorithm. Process symbol - shows an instruction other than input, output or selection. Input-output symbol - shows an input or an output operation. Disk storage I/O symbol - indicates input from or output to disk storage. Printer output symbol - shows hardcopy printer output.
prepared by NI, edited by MAF
Statement 1
Statement 2
Statement 3
No
Condition
Yes
elsestatement(s)
thenstatement(s)
yes Condition no
Loop Statement(s)
Flowchart example 1
Begin
Display age
End
Flowchart example 2
Begin
Read age
YES
NO
print retired
End
Flowchart example 5
Begin
sum = 0 current_number = 1
print sum
Flowchart - exercises
Write the equivalent flowchart for each of the examples given in pseudocoding, i.e
Example 3 Example 4 Example 7 Example 8
Implementation
The process of implementing an algorithm by writing a computer program using a programming language (for example, using C language) The output of the program must be the solution of the intended problem The program must not do anything that it is not supposed to do
(Think of those many viruses, buffer overflows, trojan horses, etc. that we experience almost daily. All these result from programs doing more than they were intended to do)
prepared by NI, edited by MAF
Documentation
Contains details produced at all stages of the program development cycle. Can be done in 2 ways:
Writing comments between your line of codes Creating a separate text file to explain the program
Important not only for other people to use or modify your program, but also for you to understand your own program after a long time (believe me, you will forget the details of your own program after some time ...)
prepared by NI, edited by MAF
Documentation cont
Documentation is so important because: You may return to this program in future to use the whole of or a part of it again Other programmer or end user will need some information about your program for reference or maintenance You may someday have to modify the program, or may discover some errors or weaknesses in your program Although documentation is listed as the last stage of software development method, it is actually an ongoing process which should be done from the very beginning of the software development process.
prepared by NI, edited by MAF
Volume calculation
Write a pseudocode and a flowchart for a C program that read the value of the height, width and length of a box from the user and print its volume.
Sum of 1 to n
Write a pseudocode and a flowchart for a program that reads a positive integer n and then computes and prints the sum of all integers between 1 and n.
Summary
This chapter introduced the concept of problem solving-a process of transforming the description of a problem into a solution. A commonly used method SDM which consists of 6 steps 3 basic control structures : sequence, selection and repetition structures Pseudocode vs. Flow chart
prepared by NI, edited by MAF