Scribd
Upload
38 views3 pages

Software Engineering - Rapid Application Development Model (RAD)

The Rapid Application Development (RAD) model was proposed by IBM in the 1980s and features the use of powerful development tools to break projects into independently developed modules that are later combined. Each module goes through analysis, design, coding, and testing similar to the waterfall model. RAD aims to deliver working software in short timeframes of 60-90 days through iterative prototyping and feedback from users. The RAD process involves four phases: requirements planning, user description, construction, and cutover testing between modules before acceptance testing.

Uploaded by

Shoeb Akibul Islam
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
38 views3 pages

Software Engineering - Rapid Application Development Model (RAD)

The Rapid Application Development (RAD) model was proposed by IBM in the 1980s and features the use of powerful development tools to break projects into independently developed modules that are later combined. Each module goes through analysis, design, coding, and testing similar to the waterfall model. RAD aims to deliver working software in short timeframes of 60-90 days through iterative prototyping and feedback from users. The RAD process involves four phases: requirements planning, user description, construction, and cutover testing between modules before acceptance testing.

Uploaded by

Shoeb Akibul Islam
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/ 3

Software Engineering | Rapid application development

model (RAD)
The Rapid Application Development Model was first proposed by IBM in 1980’s. 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 waterfall model i.e
analyzing, designing, coding and then testing, etc. as shown in the figure.
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:
1. 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
final refined model.
2. 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.
3. 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.
4. 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 the
taking feedback. After validation by the customer, SRS document is developed and the
design is finalised.
Advantages –
 Use of reusable components helps to reduce the cycle time of the project.
 Feedback from the customer is available at initial stages.
 Reduced costs as fewer developers are required.
 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 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 for 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
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 ability to use powerful techniques is a necessity.
5. The model should be chosen when the budget permits the use of automated tools
and techniques required.

You might also like