Scribd
Upload
18 views17 pages

RAD Model

Uploaded by

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

RAD Model

Uploaded by

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

RAD

1
Rapid Application
Development
 RAD is a techniques/ method that emphasize on user
involvement and evolutionary working with prototypes of a
system to accelerate the system development process.
 RAD is based on building prototypes that evolve into finished
systems.

• A prototype is a smaller-scale, representative or working model of the


users’ requirements or a proposed design for an information system.
Rapid Application development…

 A rapidly changing business environments,


businesses have to respond to new
opportunities and competition. This requires
software and rapid development and rapid
delivery of software systems.
 Businesses may be willing to accept lower
quality software if rapid delivery of essential
functionality is possible.
Characteristics of RAD
 The processes of application specification, design and
implementation are concurrent.

 There is no detailed specification and design documentation is


minimized.

 The system is developed in a series of increments. End users


evaluate each increment.

 User interfaces are usually developed using an interactive


development system.
Definition:
RAD is a software development
methodol-ogy that uses minimal
planning in favor of rapid prototyping.
RAD allows software to be written much
faster, and makes it easier to change
requirements.

6-5
RAD Life Cycle

6
RAD Phases
 The three broad phases to RAD are :

• Requirements/ Analysis.
• Design/ Construct.
• Implementation.

6-7
RAD is a Martin
Approach
The Martin approach includes 4
phases:

• Requirements planning.
• User design.
• Construction.
• Cutover.

6-8
Martin Approach to RAD

6-9
Requirements Planning
Phase
 Users and analysts meet to identify
objectives of the system oriented
toward solving business problems
 Requirements planning is much like
traditional problem definition and
systems analysis.

6-10
RAD Design Workshop
• Design & refine phase.

• GDSS (Group decision support systems) to help users agree


on designs.

• Programmers and analysts can build and show


visual representations of the designs.

• Users respond to actual working prototypes,


Analysts refine designed modules based on user
responses.

6-11
Implementation or Cutover Phase

 The cutover phase is similar to the traditional


implementation phase
 When a system built, the new systems or
partial systems are tested and introduced to
the organization.
 When creating new systems, there is no need
to run old systems in parallel.
 Cutover Key activities include
• training the users,
• converting or installing the system & completing the
necessary documentation.
6-12
RAD benefits
 In RAD tools are used to generate
screens and show the overall flow of
the application.
 Users approve the design with the
visual model.
 Implementation is less stressful
because users helped to design.

6-13
When to Use RAD
• When programmers & analysts are
experienced.
• The project involves like ecommerce
application and needs quick results.
• Users are sophisticated and highly engaged
with the goals of the company.

6-14
Advantages of RAD
 Increase speed of development
 Increase quality through the
involvement of the user with analysis
in design stages.
 The software is drastically reduced
due to a reduced requirement
analysis phase.

15
Disadvantages of RAD
 Many try and hurry the project too much

 Loosely documented.

 Reduced features occur due to time boxing.

 RAD may not be useful for large, highly complex


projects.

 When the team ignores necessary quality parameters


such as consistency, reliability and standardization.

 Reduced Scalability, and reduced features.


6-16
The End

17

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy