Policies Section
  1. Software Project Lifecycle
  2. Best Project Development Method
  3. Software Project Documentation Requirements
  4. Software Project Documentation Standards
  5. Project Planning Phase
  6. Functional Requirements Specification
  7. Project Charter
  8. Project Plan
  9. Project Analysis Phase
  10. Project Design Phase
  11. Project Development Phase
  12. Programming Standards
  13. Project Testing Phase
  14. Software Test Plan
  15. Project Implementation Phase
  16. Software Installation Manual
  17. Software Maintenance Plan
  18. Configuration Management Plan
  19. Users Guide
  20. Project Maintenance Phase
Policies Section

8 Project Development Phase

The code is written according to the design document. Several software reviews should be done during the coding phase. Source code should be delivered at the end of the implementation phase but most of the source code is written during the coding phase. There should be minimum coding standards such as how many comments should be entered, documentation of module interdependancies, and parameters passed and used by functions.

Design should be kept modular.

Development Standards

Design specifications must be discussed by programmers with project participants before programming begins. The programmers access to programs, data, and systems that are not part of their responsibilities should be limited by development standards.

Coding Standards

Specifies layout of code. Specifies naming conventions of functions and libraries.

Software Documentation Standards

Detailed application descriptions, system narratives


The following documents will be created or started:

  • Technical documentation should be completed
  • Test Plan should be created