Scribd
Upload
11 views9 pages

Week 4

The Rapid Application Development (RAD) model, proposed by IBM in the 1980s, emphasizes the use of powerful development tools and techniques to create software in short time frames, typically 60-90 days. It involves four basic phases: Requirements Planning, User Description, Construction, and Cutover, allowing for modular development and customer feedback throughout the process. While RAD offers advantages such as reduced costs and faster delivery, it requires skilled professionals and is not suitable for small-scale projects or those that cannot be modularized.

Uploaded by

mujtabajamal2004
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views9 pages

Week 4

The Rapid Application Development (RAD) model, proposed by IBM in the 1980s, emphasizes the use of powerful development tools and techniques to create software in short time frames, typically 60-90 days. It involves four basic phases: Requirements Planning, User Description, Construction, and Cutover, allowing for modular development and customer feedback throughout the process. While RAD offers advantages such as reduced costs and faster delivery, it requires skilled professionals and is not suitable for small-scale projects or those that cannot be modularized.

Uploaded by

mujtabajamal2004
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Software Engineering | Rapid

application development model


(RAD)
Rapid application development model (RAD)
• The Rapid Application Development Model was first proposed by IBM
in the 1980s. The critical feature of this model is the use of powerful
development tools and techniques.
• A software project can be implemented using this model if the
project can be broken down into small modules wherein each module
can be assigned independently to separate teams.
• These modules can finally be combined to form the final product.
• Development of each module involves the various basic steps as in
the waterfall model i.e. analyzing, designing, coding, and then
testing, etc.
• Another striking feature of this model is a short time span i.e. the
time frame for delivery(time-box) is generally 60-90 days.
The use of powerful developer tools such as JAVA, C++, Visual BASIC, XML, etc. is also an
integral part of the projects.
This model consists of 4 basic phases:
• Requirements Planning – It involves the use of various techniques used in
requirements elicitation like brainstorming, task analysis, form analysis, user scenarios,
FAST (Facilitated Application Development Technique), etc. It also consists of the entire
structured plan describing the critical data, methods to obtain it, and then processing
it to form a final refined model.
• User Description – This phase consists of taking user feedback and building the
prototype using developer tools. In other words, it includes re-examination and
validation of the data collected in the first phase. The dataset attributes are also
identified and elucidated in this phase.
• Construction – In this phase, refinement of the prototype and delivery takes place. It
includes the actual use of powerful automated tools to transform process and data
models into the final working product. All the required modifications and
enhancements are too done in this phase.
• Cutover – All the interfaces between the independent modules developed by separate
teams have to be tested properly. The use of powerfully automated tools and subparts
makes testing easier. This is followed by acceptance testing by the user.
The process involves building a rapid prototype, delivering it to the customer, and taking
feedback. After validation by the customer, the SRS document is developed and the
design is finalized.
When to use RAD Model?
When the customer has well-known requirements, the user is involved throughout the
life cycle, the project can be time boxed, the functionality delivered in increments, high
performance is not required, low technical risks are involved and the system can be
modularized. In these cases, we can use the RAD Model.
Advantages:
• The use of reusable components helps to reduce the cycle time of the project.
• Feedback from the customer is available at the initial stages.
• Reduced costs.
• The use of powerful development tools results in better quality products in
comparatively shorter time spans.
• The progress and development of the project can be measured through the various
stages.
• It is easier to accommodate changing requirements due to the short iteration time
spans.
Disadvantages:
• The use of powerful and efficient tools requires highly skilled
professionals.
• The absence of reusable components can lead to the failure of the
project.
• The team leader must work closely with the developers and
customers to close the project in time.
• The systems which cannot be modularized suitably cannot use this
model.
• Customer involvement is required throughout the life cycle.
• It is not meant for small-scale projects as in such cases, the cost of
using automated tools and techniques may exceed the entire budget
of the project.
Applications:
1. This model should be used for a system with known requirements
and requiring a short development time.
2. It is also suitable for projects where requirements can be
modularized and reusable components are also available for
development.
3. The model can also be used when already existing system
components can be used in developing a new system with minimum
changes.
4. This model can only be used if the teams consist of domain experts.
This is because relevant knowledge and the ability to use powerful
techniques are a necessity.
5. The model should be chosen when the budget permits the use of
automated tools and techniques required.
RAD Model vs Traditional SDLC
RAD Traditional SDLC

1. Stages are not well defined. Structured Methodology and well-defined stages.

Different stages of application development can be Follows a predictive, inflexible and rigid approach for
2.
reviewed and repeated as the approach is iterative. application development.

The use of automated RAD tools and techniques enable


3. faster and easier prototypes which are then used to Prototyping is difficult and requires more time and effort.
develop the final product.

It is not necessary to know all the requirements All the requirements should be known before starting the
4.
beforehand. project due to rigidity of the models.

Difficult to accommodate changes due to sequential


5. Easier to accommodate changes.
nature of models
Extensive customer feedback leading to more
6. customer satisfaction and better quality of final Limited customer feedback.
software.

Stringent and extensive documentation of the entire


7. It involves minimal documentation.
project process is necessary.

Separate small teams can be assigned to individual As there is no modularisation, a larger team is required
8.
modules. for different stages with strictly defined roles.

Generally preferred for projects with shorter time Used for projects with longer development schedules
9. durations and budgets large enough to afford the and where budgets do not allow the use of expensive
use of automated tools and techniques. and powerful tools.

Use of reusable components helps to reduce the The use of powerful and efficient tools requires highly
10.
cycle time of the project. skilled professionals.

You might also like