Rapid Application Development
Rapid means Fast
The Rapid Application Development methodology was developed to respond to the need to deliver systems very fast. The RAD approach is not appropriate for every project - an application that determines the taxes you should pay every year and is based on RAD might not instill much confidence. Project scope, size and circumstances all determine the success of a RAD approach. The following categories indicate suitability for a RAD approach:
-
Project Scope
- Suitable - Focused and well defined objectives.
- Unsuitable - Broad or obscurely defined objectives.
-
Project Data
- Suitable - Data for the project already exists (completely or in part). The project largely comprises analysis or reporting of the data.
- Unsuitable - Complex or vast amounts of data must be analyzed, designed and created within the scope of the project.
-
Project Decisions
- Suitable - Decisions can be made by a small number of people who are available and preferably co-located.
- Unsuitable - Many people must be involved in the decisions on the project, the decision makers are not available on a timely basis or they are geographically dispersed.
-
Project Team
- Suitable - The project team is small (preferably six people or less).
- Unsuitable - The project team is large or there are multiple teams whose work needs to be coordinated.
-
Project Technical Architecture
- Suitable - The technical architecture is defined clearly and the key technology components are in place and tested.
- Unsuitable - The technical architecture is unclear and much of the technology will be used for the first time within the project.
-
Project Technical Requirements
- Suitable - Technical requirements (response times, throughput, database sizes, etc.) are reasonable and well within the capabilities of the technology being used.
- Unsuitable - Technical requirements are tight for the equipment to be used.
