Rapid Application Developement Model in Software Engineering Models

1.  AHMAD JUNAID TARIQ
 FA17-BCS-004
 HAFIZ MUHAMMAD WALEED
 SP17-BCS-013

2. Rapid
Application
Development
Model
RAD

3.  It is adoption of waterfall model, It aims at
developing a software in a short span of
time.
 It is a type of Incremental model.
 In RAD the Components are developed in
parallel Manner.
 It is a faster software development process.
 This can quickly give the customer
something to see and use and to provide
feedback regarding the delivery and their
requirements.

5. REQUIREMEN
T PLANNING
 During this initial stage
designers, developers, and
users come to a rough
agreement on project scope
and application requirements,
so that future stages with
prototyping can begin.

6. USER DESIGN
 User feedback is gathered
with heavy emphasis on
determining the system
architecture. This allows
initial modeling and
prototypes to be created.
This step is repeated as
often as necessary as the
project evolves.

7. CONSTRUCTI
ON
 Once basic user and system
design has begun, the
construction phase is where
most of the actual application
coding, testing, and integration
takes place.
 Along with User Design,
the Rapid Construction phase is
repeated as often as necessary,
as new components are required
or alterations are made to meet
the needs of the project.

8.  Final Cutover (or Transition) stage
allows the development team time to
move components to a live production
environment, where any necessary full-
scale testing or team training can take
place.

9.  Requirements can be changed at any
time
 Encourages and priorities customer
feedback
 Reviews are quick
 Development time is drastically
reduced
 More productivity with fewer people
 Time between prototypes and
iterations is short
 Needs strong team collaboration
 Cannot work with large teams
 Needs highly skilled developers
 Needs user requirement
throughout the life cycle of the
product
 Only suitable for projects which
have a small development time
 More complex to manage when
compared to other models

10.  When a system needs to be produced in a short span of time
 When the requirements are known
 When the user will be involved all through the life cycle
 When technical risk is less

11.  RAD design philosophies, such
as quick prototyping, receiving
constant feedback into how an
app works, and easy
maintenance.
 This provides you with a
platform to create apps quickly.
 Moreover, since you can test it
out before you release it into
your office environment, you
have an idea of whether it
actually works as intended or
not.