Rapid application development model (RAD)
The Rapid Application Development Model was first proposed by IBM in the 1980s.
When the requirements are fully understood then the RAD model is used.
Unlike the traditional SDLC model in which the end product is available in the end, in
the RAD model (Rapid Application Development) after each iteration the model is
shown to the client and based on the feedback of the client, necessary changes will be
done,
hence in this, there is the total involvement of the client in every phase of the model.
When to use the RAD Model?
• Well-understood Requirements: When project requirements are
stable and transparent, RAD is appropriate.
• Time-sensitive Projects: Suitable for projects that need to be
developed and delivered quickly due to tight deadlines.
• Small to Medium-Sized Projects: Better suited for smaller initiatives
requiring a controllable number of team members.
• High User Involvement: Fits where ongoing input and interaction from users are
essential.
• Innovation and Creativity: Helpful for tasks requiring creative inquiry and
innovation.
• Prototyping: It is necessary when developing and improving prototypes is a key
component of the development process.
• Low technological Complexity: Suitable for tasks using comparatively
straightforward technological specifications.
RAD (Rapid Application Development) is a concept that products
can be developed faster and of higher quality through:
•Gathering requirements using workshops or focus groups
•Prototyping and early, reiterative user testing of designs
•The re-use of software components
The various phases of RAD are as follows:
• [Link] Modelling: The information flow among business functions is defined
by answering questions like what data drives the business process, what data is
generated, who generates it, where does the information go, who process it and so
on.
• 2. Data Modelling: The data collected from business modeling is refined into a
set of data objects (entities) that are needed to support the business. The attributes
(character of each entity) are identified, and the relation between these data objects
(entities) is defined.
3. Process Modelling: The information object defined in the data modeling phase are
transformed to achieve the data flow necessary to implement a business function.
Processing descriptions are created for adding, modifying, deleting, or retrieving a data
object.
4. Application Generation: Automated tools are used to facilitate construction of the
software; even they use the 4th GL techniques.
5. Testing & Turnover: Many of the programming components have already been
tested since RAD emphasis reuse. This reduces the overall testing time. But the new
part must be tested, and all interfaces must be fully exercised.
Benefits of RAD Model
• Better quality software: It provides better quality of software that is
more usable and more focused on businesses.
• Better reusability: RAD Models has a better reusability of components.
• Flexible: RAD Models are more flexible as it helps in easy adjustments.
• Minimum failures: It helps in completing projects within time and within
budget. Failures are minimum in RAD Model.