Rapid Application Development (RAD)

 
Rapid Application Development (RAD) is a form of agile software development methodology that prioritizes rapid prototype releases and iterations. 

Unlike the Waterfall method, RAD emphasizes the use of software and user feedback over strict planning and requirements recording.
 
Steps or Phases in RAD
 
Step 1. Define and finalize project requirements

• During this step, stakeholders sit together to define and finalize project requirements such as project goals, expectations, timelines, and budget.  
• When you have clearly defined and scoped out each aspect of the project’s requirements, you can seek management approvals.

 
Step 2: Begin building prototypes

• As soon as you finish scoping the project, you can begin development.  
• Designers and developers will work closely with clients to create and improve upon working prototypes until the final product is ready.

Step 3: Gather user feedback

• In this step, prototypes and beta systems are converted into working models. 
• Developers then gather feedback from users to tweak and improve prototypes and create the best possible product.

 
Step 4: Test

• This step requires you to test your software product and ensure that all its moving parts work together as per client expectations.   
• Continue incorporating client feedback as the code is tested and retested for its smooth functioning. 

Step 5: Present your system

• This is the final step before the finished product goes to launch.   
• It involves data conversion and user training.
  

 
Advantages 

• Enhanced flexibility and adaptability as developers can make adjustments quickly during the development process.  
• Quick iterations that reduce development time and speed up delivery. 
• Encouragement of code reuse, which means less manual coding, less room for errors, and shorter testing times.  
• Increased customer satisfaction due to high-level collaboration and coordination between stakeholders (developers, clients, and end users).  
• Better risk management as stakeholders can discuss and address code vulnerabilities while keeping development processes going.
  

 
Disadvantages 

•  Only systems that can be modularized  can be built using RAD.  
• Inapplicable to cheaper projects as cost of Modelling and automated code generation is very high.  
• Only suitable for systems that are component based and scalable.  
• Requires user involvement throughout the life cycle.  
• Suitable for project requiring shorter development times.