RAD (Rapid Application Development) Process Model:
- It is a type of incremental model. In RAD model the components or functions are developed in parallel as if they were mini projects.
- The developments are time boxed, delivered and then assembled into a working prototype.
- This can quickly give the customer something to see and use and to provide feedback regarding the delivery and their requirements.
| Advantages | Disadvantages |
|---|---|
| Reduced development time | For large but scalable projects RAD requires sufficient human resources. |
| Increases reusability of components | Projects fail if developers and customers are not committed in a much shortened time-frame. |
| Quick initial reviews occur | Problematic if system cannot be modularized. |
| Encourages customer feedback | Not appropriate when technical risks are high (heavy use of new technology). |
| Integration from very beginning solves a lot of integration issues. |
When to use RAD model?
- RAD should be used when there is a need to create a system that can be modularized in 2-3 months of time.
- It should be used if there’s high availability of designers for modeling and the budget is high enough to afford their cost along with the cost of automated code generating tools.
- RAD SDLC model should be chosen only if resources with high business knowledge are available and there is a need to produce the system in a short span of time (2-3 months).