RAPID DEVELOPMENT Kelompok 03 Andiga Putra Ferry Gunawan Ivan Jonathan Stephen Sutandhi William

Outline INTRODUCTION LITERATURE REVIEW DISCUSSION CONCLUSION AND SUGGESTIONS

INTRODUCTION BACKGROUNDSCOPE PURPOSE AND BENEFIT METHODOLOGY WRITING SYSTEMATIC

Literature Review Definition of Rapid Development Definition of Application Definition of Information Definition of System Definition of Information System Definition of System Development Cycle

DISCUSSION

ADVANTAGE OF RAPID Faster Delivery Time Lower Cost due to Reusing Existing Items Lower Maintenance Better Project Management Reduced RisksBetter Quality

DISADVANTAGE OF RAPID Business Requirements System That Can Be Modularized Requires Highly Skilled Developers/Designers Too High Dependency on Modeling Skills Requires High Budget Product May Lose its Competitive Edge Programmers of The Project are Required to Work in Pairs Need The Commitment of Both Customer and Developer to Complete a Project

STEP OF RAPID DEVELOPMENT Construction phase Cutover phase User design phase Requirements Planning phase

AGILE VS RAPID DEVELOPMENT Agile does not allow prototypes Agile projects logically break down the solution into features Agile teams are democratic Rapid was based on designing prototypes the Rapid approach did not do this In contrast, RAD solutions were not based around the concept of a common architecture and thus individuals worked in silos. AGILE DEVELOPMENTRAPID DEVELOPMENT

CONCLUSION & SUGGESTION

Q & A