Murach's Mainframe COBOL |
||
| Chapter 4 | How to design, code, and test a structured program | |
| How to develop a structured program | 106 | |
| A complete procedure for developing a structured program | 106 | |
| The specifications for a summary report-preparation program | 108 | |
| How to design a structured program | 110 | |
| The terms for working with a structure chart | 110 | |
| How to name the modules in a chart | 110 | |
| How to design the first two levels of a chart | 112 | |
| How to design the legs of a chart | 114 | |
| How to add the Read and Write modules to a chart | 116 | |
| How to number the modules in a chart | 118 | |
| How to draw charts that won’t fit on one page | 118 | |
| Alternatives to the structure chart | 120 | |
| When and how to use pseudocode | 122 | |
| The basics of using pseudocode | 122 | |
| How to use pseudocode for the critical modules of a program | 124 | |
| How to code each module so it is independent | 126 | |
| How to code and test a program from the top down | 128 | |
| How to plan the coding and testing sequence | 128 | |
| How to code the new modules for each phase of testing | 130 | |
| How to code program stubs | 132 | |
| The code for the summary report-preparation program | 134 | |
| The Data Division code | 134 | |
| The Procedure Division code | 136 | |
| How COBOL programming compares to object-oriented programming | 142 | |
| Perspective | 144 | |
| t | ||
|
© Copyright 1998-2009 Mike Murach & Associates, Inc. All rights reserved. |
||
|
|
|
