Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Development - Coggle Diagram

- - - - Simple, so easy to manage
      - Everyone on the project is very clear on their responsibilities at each stage
      - Clear deliverables
      - Easy to see if a project is running to schedule
      - Suited towards large scale development projects with clear requirements and very little risk
    - - Carries a lot of risk
      - User doesn’t see solution until it is near its end
      - Misunderstanding / changing requirements can be disastrous
      - Requirements must be very well understood, so unsuitable to complex projects
  - - - Requirements don’t need to be entirely clear from the beginning
      - Focus groups involving the end user can be used to gather requirements rather than producing a formal document
      - Continuous user feedback throughout promotes good usibility
      - Suited towards projects where the end requirements are not fully understood
    - - Focuses on usibility rather than efficiency
      - Regular contact with the user must be maintained at all times
      - Scales poorly for large projects with big teams
  - - - Promotes risk management
      - Excellent for projects that involve a high level of risk
      - Suited towards large-scale projects carrying lots of risk where requirements may not initially be fully understood
    - - Complex nature of risk analysis increases costs
      - Poor risk analysis may be disastrous
  - - - Emphasises programming, promoting quality of end product
      - Core principles and processes promote respect and collaboration, leading to a highly productive development team
      - Suitable for projects where quality of the final product is important
    - - Requires a team of programmers working in close collaboration - not suited towards projects widely distributed geographically
      - Client must commit to having a full-time representative working with the development team
      - Some processes involved are costly
  - - - Test-driven development
      - Simple design
      - Refactoring
      - Continuous integration
      - Code standards
      - Whole team
      - Customer tests
      - Planning games
      - Small releases
      - Sustainable pace
      - Paired programming
      - Collective code ownership
- - - - No data is entered
    - - Data which should be rejected by the program
    - - Data which should be accepted by the program without causing errors
    - - Valid data which is on the edge of the accepted validation limits
- - - - Oval: terminal
      - Rectangle: process
      - Diamond: decision
      - Parallelogram: in/output
      - Double rectangle: subroutine
      - Arrow: line