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.
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.
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
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