2. GOOD DESIGN AND PROGRAMMING
PRACTICE INCLUDES
Styles and format
Structured programming
Coupling and Cohension
Documentation and source control
Scheduling
3. 1. STYLES AND FORMAT
Pseudocode before program.
Add appropriate comments : Readable and clear, concise, correct.
Name variables properly. Minimize use of global variables.
Don’t pass pointer.
Include brief header before each routine including objectives and summary.
4. 2. STRUCTURED PROGRAMMING
Establish framework for generating code that is more readable, reliable and
maintainable.
Framework based on clearly defined modules or procedures.
Structured programming encourages the installation and testing of one module
at a time to simplify the verification of the software.
5. 3. COUPLING AND COHESION
coupling is the degree of interdependence between software modules; a
measure of how closely connected two routines or modules are
Modules should have minimum Communication or coupling.
Coupling types:
Loose coupling(modules interact with one another through a simple and stable
interface)
Tight coupling(A module modifies or relies on the interval workings of another
module).
Cohesion measures the strength of relationship between pieces of functionality
within a given module.
A cohesive module performs a single task.
Modules should have maximum cohesion.
6. 4. DOCUMENTATION AND SOURCE
CONTROL
Documentation describes the overall system function.
Backup file sources to prevent loss of data and code.
Back up source files: disks, CD, tape drivers.
Store multiple copies in separate location.
File storage is cheap but reconstructing lost data is expensive and impossible.
7. 5. Scheduling
It estimates software development time.
Should record all efforts expended in current jobs to estimate future job.
Timing of meeting, planning, designing, debugging testing should be properly
planned.