Waterfall RAD Incremental Prototype Spiral

Features Step by Step High speed Successive A simplified model Iterative nature of the Prototyping Model
Approach. Next adaptation of enlargements and of the system with the controlled and systematic
step can not start waterfall model. refinements of a system (prototype) is built approach of the Waterfall Model
unless previous Development is through multiple mini fast to make the • Used in projects where risk
step is through done for SDLCs. client have a feel of factor is high: military, research-
independent the system. oriented.
components in Customer’s • Performs risk evaluation in each
parallel and requirements are While building cycle.
then integrated gradually known prototype the • Can be integrated with other life
minimum amount of cycles.
coding is done
• Multiple cycles performed.
without
Each cycle consists of:
implementing
1. Determine objectives,
coding standard,
alternatives, constraints
error management,
2. Evaluate alternatives,
normalization etc.
identify & resolve risk
(e.g. risk analysis,
It is a way of
prototype, simulation)
understanding
3. Develop and verify
requirements from
product: prototype,
the customer
product or other
deliverable
4. Plan next phase:
Review findings of this
round and plan goals
for next round

When to When the When a system When the objectives of When When Risk is high
Use requirements are can be broken the system can be Requirements are
clear into achieved by dividing the not completely
independent system into sub systems known
sub systems with a core system.
The core system of sub
system will serve the
 Waterfall RAD Incremental Prototype Spiral
basic needs and the
subsequent systems will
serve the incremental
needs

When there is a
technical/resource risk
Disad 1.Requiremen 1.Performa 1.Difficulty in 1.Does not 1.No scheduled project completion.
vanta ts have to be nce issue. managing multiple work well for
ge fully concurrent production 2.A dedicated team for risk analysis
understood to 2.Technical increments system is required
implement this issues are
model high 2.Customer
sees a
2.As one 3.Interopera 'working'
phase bility issue model and
depends on with gets impatient.
the other so it existing
causes delay systems 3.Developer
may make
3.Things keep 4. Resource implementation
coming in for may be an compromises
a particular issue to get prototype
phase even working quickly.
after the
phase is
signed off

4.Rigid Model