VBM - Vision Based Methodology™

Activity 9: Constructing the System

Program Skeletons - Objects

At the present time, it is almost unthinkable not to use some form of program skeletons (objects/classes) as a starting point for programming. Unless it happens to be a single highly customized program for a personal computer, and the programmer is working alone with no standards, and no prior program "pattern" examples exist, then it may be safe to say that a skeleton cannot be obtained or does not need to be developed. But in almost all other situations, creating a cloneable skeleton is recommended for these reasons:

• Insures a consistent approach will be used for every program. (This is a true source of relief to the maintenance programmers who will work with the system once it is complete. Nothing gives a maintenance programmer a greater sense of confidence that a consistent, "patterned" approach).
• Makes program logic "cloning" much easier.
• Makes the review process more routine.
• Assists new programmers in getting the overall coding approach "vision" more quickly.
• Results in a highly professional result.

Listed below are a few of the minimum skeletons (objects/classes) which should be developed:

• Menu
• Scrolling List
• Look-up
• Table/File Maintenance - Single Record
• Table/File Maintenance - Header with Scrolling Details

Bottom-Up Programming

Programming is a personal thing. Probably no other activity so closely reflects the way a person assimilates, organizes, and expresses procedural thinking. Creating a program in one's mind and then transferring the "image" to paper, is a highly unique and individualized process. This is one reason programmers are sometimes uncomfortable with code reviews or walk-thrus. If the review is not carefully handled, it can turn into a critique of a person's thinking process. Undoubtedly, that is a situation no one would particularly enjoy.

Even after recognizing these sensitivities, one approach toward "programming from scratch" seems to be quite superior in both its simplicity and speed. That technique is bottom up programming! It can be even more effective if a program skeleton is utilized as a starting point. Listed below are the steps which are typically followed in this programming approach:

First, create the "utility" paragraphs or modules:

• Create an individual paragraph or module for each "write" to a file or report.
• Do the same for each "read" to or from a file.
• Create an individual paragraph or module for each "format" of a report line or file record.
• Create the same for every database access call (one per SQL statement).
• Create one paragraph to handle major error (abend) processing.
• Create the same for each external program call.
• Create a unique paragraph or module for each internal array operation

Next, create the "processing" paragraphs or modules:

• Create one driver paragraph or module at the top of the program.
• Create one initialization and one termination paragraph or module.

Last create all required "processing" paragraphs or modules.

These should consist of unique logic, decision paths, calculations, and calls to the lower level "utility" paragraphs or modules.