Standard Development Life Cycle
The development phase is a “built to design” process. Requirement of Inputs, outputs, and
the letter but should first be followed. The main reason, this is what was approved and
signed off. As much as we do not like scope creep, the business does not like to deviate from
what was already approved.
If your unit testing does find a flaw in the process, write a formal document of your findings.
Describe the flaw and if possible, make a suggestion to a fix. The design document should be
modified and signed off before any changes are made before the re-development. This one
flaw may also recall other design documents that are related to the process. For the change
that was discovered will probably cause other design changes.
In the development process, debugging will also be necessary. Check the design and make
sure the correct fields are being used. Your bug in the program could be just a simple move
of the wrong field. There are many reasons for the code to be canceling. Too many to list but
debugging is part of the development phase.
Earlier, unit testing was mentioned. The purpose of unit testing is to validate the module in
design. Verify the testing for the particular program in design. The Testing Phase will
address the full testing for the entire process.
Benefits of the Development Phase.
- Coding straight to the design
- Design can be handed off to a developer
- Logic flow should be followed to the letter
- Prototypes will have your results for the unit tests
This file is not intended to be viewed directly using a web browser. To create a viewable file, use the Preview in Browser or Publish to Yahoo! Web Hosting commands from within Yahoo! SiteBuilder.