Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
1. Introduction to 
Rapid Application Development 
Kasun RangaWijeweera 
(krw19870829@gmail.com)
What is RAD? 
• Usable systems are built within a short period 
of time 
• In generic terms RAD is 
– “Speedy development”...
Principles of RAD 
• 20/80 Rule: Usable 80% solution can be 
developed in 20% of time required for the total 
solution 
• ...
Traditional Development Issues 
• Cost and schedule overruns 
• Product not fit for business 
• High workload 
• Projects ...
Reasons for Project Failures 
• Risks associated with teams 
• Risks associated with technology 
• Risks associated with r...
Conventional Methods! 
• Long delay before customer sees the result 
• Development takes longer time and business 
may cha...
History of RAD 
• Spiral model 
• Evolutionary life cycle 
• Rapid iterative productive prototyping 
• RAD – Early 90s
Classic Mistakes 
• People related 
• Product related 
• Technology related 
• Process related
People Related Mistakes 
• Undermined motivation 
• Weak personnel 
• Employee problems 
• Heroics 
• Unrealistic expectat...
Product Related Mistakes 
• Requirements gold plating 
• Developer gold plating 
• Feature creep 
– Changes of the require...
Technology Related Mistakes 
• Silver Bullet Syndrome 
– Too much rely on new technologies 
• Switching tools at the middl...
Process Related Mistakes 
• Lack of risk management 
• Contractor failure 
• Lack of planning 
• Premature convergence 
• ...
Why use RAD? 
• Converging early to a design acceptable by the 
customer 
• Saving development time 
• Preventing cost ove...
Choose Most Rapid Model? 
• How well the customer and the client 
understand the requirements at the beginning 
• Level of...
Thank you!
Prochain SlideShare
Chargement dans…5
×

Introduction to Rapid Application Development

958 vues

Publié le

Provides an introduction to RAD

Publié dans : Logiciels
  • Login to see the comments

Introduction to Rapid Application Development

  1. 1. 1. Introduction to Rapid Application Development Kasun RangaWijeweera (krw19870829@gmail.com)
  2. 2. What is RAD? • Usable systems are built within a short period of time • In generic terms RAD is – “Speedy development” – “Shorter schedule”
  3. 3. Principles of RAD • 20/80 Rule: Usable 80% solution can be developed in 20% of time required for the total solution • System can satisfy all business requirements even if some operational requirements are not satisfied • A system can be accepted if it can satisfy agreed minimum useful set of requirements
  4. 4. Traditional Development Issues • Cost and schedule overruns • Product not fit for business • High workload • Projects get cancelled • Friction among managers, developers and customers
  5. 5. Reasons for Project Failures • Risks associated with teams • Risks associated with technology • Risks associated with requirements
  6. 6. Conventional Methods! • Long delay before customer sees the result • Development takes longer time and business may change meanwhile • There is nothing until the entire project is finished
  7. 7. History of RAD • Spiral model • Evolutionary life cycle • Rapid iterative productive prototyping • RAD – Early 90s
  8. 8. Classic Mistakes • People related • Product related • Technology related • Process related
  9. 9. People Related Mistakes • Undermined motivation • Weak personnel • Employee problems • Heroics • Unrealistic expectations • Noisy offices • Adding people to a late project • Friction between customers and developers
  10. 10. Product Related Mistakes • Requirements gold plating • Developer gold plating • Feature creep – Changes of the requirements occur for a long period of time • Push me….Pull me negotiation • Research oriented development
  11. 11. Technology Related Mistakes • Silver Bullet Syndrome – Too much rely on new technologies • Switching tools at the middle of the project – Learning curve, rework • Overestimated savings from new tools or methods • Lack of automated source code control
  12. 12. Process Related Mistakes • Lack of risk management • Contractor failure • Lack of planning • Premature convergence • Planning to catch up later – Code like hell programming • Wastage of time at the fuzzy front end
  13. 13. Why use RAD? • Converging early to a design acceptable by the customer • Saving development time • Preventing cost overruns • Preventing runaway schedules
  14. 14. Choose Most Rapid Model? • How well the customer and the client understand the requirements at the beginning • Level of awareness about the system architecture • Amount of reliability • How much planning ahead?
  15. 15. Thank you!

×