On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
WHAT IS RAD ???
RAD model is Rapid Application Development model.
It is a type of Incremental model.
In RAD the Components are developed in
It is a faster software development process.
PHASES IN RAD
Requirements Planning phase
User design phase
1. Requirements Planning phase
Users, managers, and IT staff members discuss on
They discuss on System requirements.
They also discuss on Project scope
It decide who will generate software.
It tells what software will do.
2. User design phase
It is also called as Modeling phase.
User Design phase is a continuous interactive process.
During this phase, users interact with software model.
It allows users to understand, modify the System.
It approve a working model of the system that meets
3. Construction phase
Focuses on program and application development task.
* Programming and application development,
* Unit-integration and
* System testing.
4. Cutover phase
It is the final ( Phase ) tasks in the System Development
Life Cycle (SDLC).
Its tasks are
* Data conversion,
* Full-scale testing,
* System change over,
* User training.
In this phase the new system is built, and delivered.
RAD reduces the development time.
Increases reusability of components.
Greater Customer Satisfaction.
Faster Delivery Time.
Simple and Better Quality.
Requires highly skilled developers/designers.
RAD is not appropriate when technical risk are high.
Cant use for small projects.
Absence of reusable component can lead to failure
of the project.
A prototype is the sample implementation of the real system.
A prototype is a toy implementation of the system.
It shows limited and main functional capabilities of the
The customer provides suggestion and improvements on the
A prototype is a model or a program which is not based on
After a prototype is built, it is delivered to the customer
for the evaluation.
It helps the customer determine how the feature will
function in the final software.
It is a very useful technique to obtain accurate
requirements of the system.
TYPES OF PROTOTYPE
1 Throwaway prototypes
2 Evolutionary Prototypes
Prototype developed as part of a throw-away approach.
It will not form part of the final solution.
It is a useful way of exploring ideas, and gaining
feedback from user.
It is initial prototype is presented to user.
They Provide feedback and suggestion for improvement.
Each stage of this prototype evolves toward the final
system hence it is called as Evolutionary Prototype
Users are actively involved in the development.
Errors can be detected much earlier.
Missing functionality can be identified easily.
It reduces risk of failure.
It is a slow process.
It is not complete model.
It is time consuming model.
It should be developed or built on company's cost.