RAD stands for Rapid Application Development

The RAD life cycle model is used to complete large projects in a much shorter time period

RAD stands for Reusable Application Design

The RAD life cycle model is able to adjust to users requirements that change

The RAD life cycle model will only work if software is coded as separate modules

The RAD life cycle model is quicker because it does not go through all the stages of a general life cycle model

The RAD life cycle model is quicker because it reuses modules in different iterations

In the RAD life cycle model, each iteration produce a prototype

The RAD life cycle model makes a prototype very early and then refines and develops it

The RAD life cycle model gathers user requirements from workshops and user groups rather than written project documents

The RAD life cycle model builds in deadlines for completion of each prototype

The RAD life cycle model uses iterations

In the RAD life cycle model, the user/customer gets feedback after each iteration

In the RAD life cycle model, user documentation is a priority

The RAD life cycle can use fewer people but they must be highly skilled

In the RAD life cycle model, some features may not be available for the first release

The RAD life cycle model is highly adaptable and flexible to changes

The focus of the RAD life cycle model are building prototypes and iterations

In the RAD life cycle model there is more focus on planning than on design

In a RAD life cycle model, if a feature is not completed on time it is not included in the final system

In a RAD life cycle model, programmers will often use software application systems than write code

In a RAD life cycle project, prototypes allow the user to see how a system might look and make suggestions