Development methodology

• Iterative development methodology


  Often referred to as the 'Waterfall model'
• Iterative stages of software development

  1. Analysis

  2. Design

  3. Implementation

  4. Testing

  5. Documentation

  6. Evaluation
• Client


  Heavily involved in the initial analysis stage and again at the end of development
• Client involvement


  Little or no involvement during the design, implementation and early testing phases
• Teams


  • Analysts, programmers, testers and documenters work independently on each phase of development
• Documentation


  • A detailed project specification is created during the analysis phase
  • Further documentation will be produced during design, implementation and testing phases
• Progress measurement


  Measured against project milestones set out in the analysis phase
• Iterative development


  A predictive methodology
• Analysis phase


  Important in setting out milestones at the start of the project
• Changing project direction


  Can be difficult without returning to analysis phase
• Iterative development


  Better suited to projects which need to strictly match the specification set out during analysis
• Testing


  Carried out once the implementation phase is complete