Rapid Application Development
(RAD)
Methodology to decrease design and
implementation time
Radically
Rapid Applications
Development (RAD)
Five key factors
1. Extensive user involvement
2. Joint Application Design sessions
3. Prototyping
4. Integrated CASE tools
5. Code generators
B.2
The Process of Developing an
Application Rapidly
RAD is a general strategy rather than a single
methodology
Goals
To analyze a business process rapidly
To design a viable system solution through
intense cooperation between users and
developers
To get the finished application into the hands of
the users quickly
Traditional SDLC steps are followed, but phases are
combined
Iteration is limited to design and development
phases
B.3
Components of RAD
User involvement is key to success
Prototyping is conducted in sessions similar
to Joint Application Design (JAD)
Prototyping screens become screens within
the production system
CASE tools are used to design the prototypes
B.4
Approaches to RAD
Martin’s RAD Life Cycle
Systems requirement determination is done in context
of a discussion of business problems and business
areas
User Design
End users and IS professionals participate in JAD
workshops
CASE tools are used to support prototyping
Construction
Designer creates code using code generator
End user validates screens and other aspects of design
Cutover
New system is delivered to end users
B.5
Advantages Disadvantages
Dramatic time savings the More speed and lower cost may
systems development effort lead to lower overall system
quality
Can save time, money and Danger of misalignment of
human effort system developed via RAD with
the business due to missing
information
Tighter fit between user May have inconsistent internal
requirements and system designs within and across
specifications systems
Works especially well where Possible violation of
speed of development is programming standards related
important to inconsistent naming
conventions and inconsistent
documentation
Ability to rapidly change system Difficulty with module reuse for
design as demanded by users future systems
System optimized for users Lack of scalability designed into
involved in RAD process system
Concentrates on essential system Lack of attention to later systems
elements from user viewpoint administration built into system
B.6 Strong user stake and ownership High cost of commitment on the
of system part of key user personnel