Thursday, December 27, 2012


  • Requirements planning phase - a workshop utilizing structured discussion of business problems.
  • User description phase – automated tools capture information from users.
  • Construction phase – productivity tools, such as code generators, screen generators, etc. inside a time-box. (“Do until done”)
  • Cut over phase  -- installation of the system, user acceptance testing and user training.

RAD - Strengths:

  • Reduced cycle time and improved productivity with fewer people means lower costs.
  • Time-box approach mitigates cost and schedule risk.
  • Customer involved throughout the complete cycle minimizes risk of not achieving customer satisfaction and business needs.
  • Focus moves from documentation to code.
  • Uses modeling concepts to capture information about business, data, and processes.

RAD - Drawbacks:

  • Accelerated development process must give quick responses to the user.
  • Risk of never achieving closure .
  • Hard to use with legacy systems.
  • Requires a system that can be modularized.
  • Developers and customers must be committed to rapid-fire activities in an abbreviated time frame.

When To Use RAD:

  • Reasonably well-known requirements.
  • User involved throughout the life cycle.
  • Project can be time-boxed.
  • Functionality delivered in increments.
  • High performance not required.
  • Low technical risks.
  • System can be modularized.


No comments:

Post a Comment

I would like to thank you for your comments..! Please keep commenting. To get posts and updates via mail, I would suggest you to subscribe the Blog. Thanks Again..!

Google Search