Sei sulla pagina 1di 17

RAD Model

Presented By:
Mansoor Nasab Abbasi
442-FBAS/MSSE/F16
Kashif Aftab
435-FBAS/MSSE/F16
Definition:
Rapid application development
RAD is incremental software development
process model that allows usable systems
to be built in as little as 60-90 days.
The RAD model used for information
systems development.
Model Phases
Business modeling
Data modeling
Process modeling
Application generation
Testing and turnover
Business Modeling:
The information flow among business
functions is defined by answering
questions like what information drives the
business process, what information is
generated, who generates it, where does
the information go, who process it and so
on.
Data Modeling
The information collected from business
modeling is refined into a set of data
objects (entities) that are needed to
support the business.
The attributes (character of each entity)
are identified and the relation between
these data objects (entities) is defined
Process Modeling
The data object defined in the data
modeling phase are transformed to
achieve the information flow necessary to
implement a business function.
Processing descriptions are created for
adding, modifying, deleting or retrieving a
data object
Application Generation
Automated tools are used to facilitate
construction of the software;
Testing and Turn over
Many of the programming components
have already been tested since RAD
emphasis reuse.
This reduces overall testing time. But
new components must be tested and
all interfaces must be fully exercised.
Structure of RAD
The key players in a RAD

Sponsor
Requirements Planning Team
User Design Team
User Review Board
Training Manager
Project Manager
Construction (SWAT) Team
Workshop Leader
RAD Requirements
CASE tool
CASE Maker's Totem 5.0 ,Rational rose
Data dictionary
Storyboard
Risk Register
Development model based on RAD

Agile software development


Joint Application Development (JAD)
Scrum
Extreme Programming (XP)
The James Martin RAD method
The James Martin RAD method

Requirements planning phase


User design phase
Construction phase
Cutover phase
Advantages:

Quick initial reviews are possible

Constant integration isolate problems and


encourage customer feedback
Disadvantage
Requires a systematic approach for
modularized
Requires highly skilled and well-trained
developers
THANKS

Potrebbero piacerti anche