Programming at this point consists of fundamentally three
steps:
- Develop program source code according to specifications and
installation standards.
- Compile the source code and produce object code. This
includes correcting grammatical/syntactical errors (obtain
a "clean" compile.
- Link all object code and run time libraries to produce an
executable program.
This may vary depending on the method of implementation.
Some application development aids (program generators) may
develop object code directly from specifications. As such,
step one is not required to produce source code. If a single
module is being produced, then steps one and two are all that
are required.
The primary concern is the preparation of the program to
meet the logic and environmental specifications established by
the computer procedure designer. Program efficiency is
dependent upon the coding technique used and the skills of the
programmer. The programmer is responsible for assuring that any
and all conditions are accounted and provided for in the
program. Cleverness in coding may be satisfying to the
programmer engaged in the 'sport' but usually results in cryptic
software that is difficult to modify or maintain. Simplicity
should be the goal.
If Software Engineering has properly planned and reviewed
the logic during Activity A, the major problem during this
activity will be that of administrative errors created while
translating the logic into source code statements. Therefore,
Software Engineering should check for language form, conventions
and planning oversights. It is also suggested that Software
Engineering annotate any source code as it is written. This
annotation will be useful during 'debugging' and future
maintenance.
If, by chance, changes are encountered in the software
structure, then the Program/Module Specification and Software
Structure Charts are updated accordingly. However, such changes
should be minor at this point. Major modifications will require
the Software Engineer to revert back to Phase 4-II, Activity B.