| Murach's Structured COBOL | ||
| Chapter 4 | How to design, code, and test a structured program | |
| How to develop a structured program | 134 | |
| A complete procedure for developing a structured program | 134 | |
| The specifications for a summary report-preparation program | 136 | |
| How to design a structured program | 138 | |
| The terms for working with a structure chart | 138 | |
| How to name the modules in a chart | 138 | |
| How to design the first two levels of a chart | 140 | |
| How to design the legs of a chart | 142 | |
| How to add the Read and Write modules to a chart | 144 | |
| How to number the modules in a chart | 146 | |
| How to draw charts that won't fit on one page | 146 | |
| Alternatives to the structure chart | 148 | |
| When and how to use pseudocode | 150 | |
| The basics of using pseudocode | 150 | |
| How to use pseudocode for the critical modules of a program | 152 | |
| How to code each module so it is independent | 154 | |
| How to code and test a program from the top down | 156 | |
| How to plan the coding and testing sequence | 156 | |
| How to code the new modules for each phase of testing | 158 | |
| How to code program stubs | 160 | |
| The code for the summary report-preparation program | 162 | |
| The Data Division code | 162 | |
| The Procedure Division code | 164 | |
| Perspective | 170 | |
| t | ||
| [Book summary] | ||
|
© Copyright 1998-2008 Mike Murach & Associates, Inc. All rights reserved. |
||