Marquez - CIS162AB - Structure Charts

MCC - Marquez - CIS162AB - C++ Level I
Sturcture Charts

A structure chart or hierarchy chart is a design tool that shows the overall structure of a program, but omits the specific programming logic. This method is refered to as the top-down design methodology or divide-and-conquer method. Structure charts are developed at a much higher level than flowcharts, because only what tasks need to be completed is depicted, and not how they will be completed. Flowcharts depict how it is going to be completed.

An overly simplified method to developing structure charts is:

  1. Identify and order the major processes that need to be completed.

  2. Determine which processes could be stand-alone functions.
     These will then become individual boxes on the structure chart.

  3. Develop the structure chart.

  4. If desired, flowcharts could be developed for each process/box.

The chart is read from top to bottom and from left to right. Each module may be subdivided into a succession of submodules that branch out under it. Typically, after the activities in a module and it's submodules are carried out, the module to the right of the current module is considered. A quick glance at the hierarchy chart reveals each task performed in the program and where it is performed.

The main benefit of structure charts is in the initial planning of a program. We break down the major parts of a program so we can see what must be done in general. From that point, we can refine each module into more detail plans using flowcharts.

Structure Chart for P05_ex and P06_ex below:

Flowchart of module inputPrice in P05_ex and P06_ex:

Revised: 08/15/2003 - www.mc.maricopa.edu/~marquez/cis162ab/p06_structurecharts.html