Rapid Application Development RAD model in SDLC is a software development process and type of Incremental Process Model. It emphasizes a short development cycle. The RAD model is a “high speed” adaption of the Waterfall Model, in which it is achieved by using a component based construction approach. It is developed faster and of higher quality through requirement gathering, early planning, well designed and construction, reuse and deployment followed by review.
If requirements are clear, well understood and project scope is constrained, RAD process enables a development team to create a fully functional system within a short time period.
RAD model maps into the basic framework activities like
A] Communication -:
It works to understand the requirement, business problem and information that must accommodate.
B] Planning -:
It is very essential part of development to run multiple team works parallel on different system. It is used to conduct smooth functionality.
C] Modeling -:
It establishes design representation of system that serves to RAD model. It encompasses into three major phases viz.
I] Business Modeling -:
It is designed to represent flow of information and distribute information between different business channels.
II] Data Modeling -:
Information is gathered, analyzed set of data object. It defines and establishes relation between data objects.
III] Process Modeling -:
Defined data object is converted into business information to achieve objective.
D] Construction -:
It emphasizes the use of the pre-existing software component and code generation.
E] Deployment -:
Deploy and ready to access system after construction and testing.
When RAD model used -:
RAD model is used when all requirements are clear and well understood. It should be designed and developed within short time period.
Drawback of RAD model -:
1. Sufficient human resource require to complete large product
2. It will fail if not committed to RAD activities
3. It will be problematic when it is not modularized and building properly
4. It may not be appropriate when technical risk are high