SYSTEM LIFE CYCLE

RAD – INVOLVES THE USER
RAPID APPLICATION DEVELOPMENT




Create a “Plane” that can fly the furthest
You have 10 Minutes to create the perfect paper aeroplane
5 minutes modification
Which can fly the furthest?
RAPID APPLICATION DESIGN
Cutover
Requirements
Planning
Construction
User design
REASONS FOR USING RAD
• In certain situations, a usable 80% solution can be
produced in 20% of the time that would have been
required to produce a total solution.
• In certain situations, the business requirements for a
system can be fully satisfied even if some of its
operational requirements are not satisfied.
•
In certain situations, the acceptability of a system can
be
assessed against the agreed minimum useful set of
requirements rather than all requirements.
PROBLEMS ADDRESSED BY RAD
•
With conventional methods, there is a long delay before the customer
gets to see any results.
•
With conventional methods, development can take so long that the
customer's business has fundamentally changed by the time the
system is ready for use.
•
With conventional methods, there is nothing until 100% of the process
is finished, then 100% of the software is delivered.