1. PROBLEM DEFINITION AND
ANALYSIS: The problem for which a
program is required is carefully studied to understand what it is all about;
its functions, requirements, the input data to be supplied and the output
information required.
2. GENERAL PROGRAM DESIGN: After a careful analysis of the problem, a generalized and broad
design of the problem is made. Then, the entire design is broken down into
small, tangible and discreet units called ‘modules’ with each modules carrying
out a well-defined unambiguous function. This system of breaking down the
design into small unit is a called ‘top-down’ modular approach. Each of this
module is further breaking down into smaller sub-modules until each unit can no
longer be modularized
3. DETAILED PROGRAM DESIGN: Having broken the general design into its smallest tangible
functioning units/modules as in step two above, a detailed logic of each
sub-modules is designed. Usually, this detailed design is accomplished using
some structured flow charts and pseudocodes.
4. PROGRAM DESK CHECKING: Then, each of the modules, so broken down is properly desk-checked
to locate and correct as many errors as possible. Desk-checking is getting some
pieces of raw data to trace manually the efficacy of the program logic as it is
written as if one is processor (computer) executing the program instructions.
5. PROGRAM/MODULE CODING: The
pseudocode/flowchart for each module designed in step three is now coded in
Visual Basic by programmer well versed in the language. The coding can be done
in a top-down manner just as in the general program design. By this, we mean
the higher level modules are coded first before the lower level modules. Each
module should be properly documented stating its function.
6. PROGRAM TESTING: At this stage, some test data satisfying all possible condition in
the program are assembled and their expected outputs prepared. The program
should then be tested with the data so collected. Compilation of the program
should first be done if a compiled language such as Visual Basic is used.
7. PROGRAM DOCUMENTATION: the detailed program flowcharts/pseudocodes, description of the
logic and coding, test data, test runs with test output and source listing etc
will be assembled and saved for maintenance purposes once the testing of step
six and complete debugging of the program has been done.
0 Comments