SDLC

• SDLC

  • later error is detected, more expensive, because reworking
• Traditional SDLC

  1. investigate
  2. analysis
  3. design
  4. implementation
  5. Maintenance and review

  
  

  Advantage

  • max management control
  • documentation
  • can trace back
  • give mid product to see user review

  
  

  Disadvantage

  • results might not be users' need
  • documentation is expensive and time-consuming
  • hard for user to know mid product is needed or not
• Prototyping SDLC

  • repetitive progress until user satisfy

  1. Investigate and analyze
  2. develop prototype
  3. operate
  4. improve and modify

  
  

  Advantage

  • user is part of development
  • user more positive
  • operational only cost weeks
  • early detection of error

  
  

  Disadvantage

  • final solution might just little better
  • no formal review
  • no documentation
  • backup, recovery , security, performance might get missed ( in rush)
• Rapid Application Development (SDLC)

  • use rapid prototyping
  • system development project adapts quickly

  Advantage

  • application to production is fastest
  • documentation produced once every task is finished
  • lot of teamwork

  Disadvantage

  • overwork for developers
  • user and analysts must be skillful
  • need more users' and stakeholders' time
• End-user system development (SDLC)

  • business manager and user are primary effort