Skip this Video
Download Presentation

Loading in 2 Seconds...

play fullscreen
1 / 5

Conclusion - PowerPoint PPT Presentation

  • Uploaded on

13. Conclusion. Simple Program Design Third Edition A Step-by-Step Approach. 13. Objectives. Revision of the steps required to achieve good top-down program design. 13. Simple Program Design.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Conclusion' - scot

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript


Simple Program Design

Third Edition

A Step-by-Step Approach

  • Revision of the steps required to achieve good top-down program design
simple program design
13Simple Program Design
  • The aim of this textbook has been to encourage programmers to follow a series of simple steps in order to develop solution algorithms to given programming problems
  • These steps are:

1. Define the problem

2. Group the activities into subtasks or functions. Not all the activities to be performed may have been listed in the defining diagram

3. Construct a hierarchy chart. Just as a company director can change the organization of the company to suit its operation, so you can change the organization of the modules in the hierarchy chart

simple program design1
13Simple Program Design

4. Establish the logic of the mainline of the algorithm. Use pseudocode and the three basic control structures to establish this logic. The mainline should show the main processing functions of the problem and the order in which they are to be performed

5. Develop the pseudocode for each successive module in the hierarchy chart

6. Desk check the solution algorithm. This detection of errors, early in the design process, can save many frustrating hours during the testing phase. It is essential that the programmer desk checks the solution algorithm, yet this step is often ignored

  • This chapter has revised the steps required to achieve good top-down program design
  • Program design is considered good if it is easy to read and understand and easy to alter
  • If you follow these six steps in the development of an algorithm, you will rapidly achieve a high level of competence