RAD is a software development methodology that focuses on rapid prototyping and fast delivery of software.

In RAD, a working model (prototype) is developed quickly and improved based on user feedback.

It is an incremental and high-speed version of the linear model, where development is done using component-based construction.

If requirements are well understood, RAD can deliver a fully functional system in a short time (about 60–90 days).

Phases of RAD Model

1. Requirement Planning

• Requirements are gathered using techniques like brainstorming.
• Strong communication between users and developers.

2. User Design / User Description

• Users and developers work together.
• Requirements are analyzed and refined.

3. Construction (Development Phase)

• System design, coding, and testing are done.
• Prototype is developed and refined repeatedly.

4. Cutover (Deployment)

• Final system is installed.
• Includes user acceptance testing and training.

RAD Model Flow

Requirement Planning → User Design → Construction → Cutover (Deployment)

Advantages of RAD Model

1. Faster Development
   • Reduces overall development time.
2. Component Reusability
   • Existing components can be reused.
3. Customer Feedback
   • Continuous user involvement improves quality.
4. Early Integration
   • Integration issues are solved early.
5. Quick Results
   • Working system is delivered quickly.

Disadvantages of RAD Model

1. Requires Skilled Team
   • Needs highly experienced developers.
2. High Dependency on Modeling Skills
   • Good design skills are necessary.
3. Continuous Customer Involvement
   • Customer must be available throughout the process.
4. Not Suitable for All Projects
   • Only works well for modular and well-defined systems.

The Evolutionary Model is a software development process in which the system is developed in iterations (repeated cycles).

Each iteration produces an improved and more complete version of the software until the final product is achieved.

It is also called an Iterative Model because development happens step-by-step in cycles.

Key Concept

• Software is not built all at once.
• It is developed in small parts (increments).
• Each cycle improves the previous version.
• Feedback is taken after every iteration.

Working of Evolutionary Model

Step 1: Requirement

• Basic requirements are collected.

Iteration Cycle (Repeated Steps)

Each build goes through the same phases:

Build 1

• Design & Development
• Testing
• Implementation (Release of first version)

Build 2

• Improved Design & Development
• Testing
• Implementation (Improved version)

Build 3

• Further Design & Development
• Testing
• Implementation (Final improved version)

Final Product

• After multiple iterations, a complete and refined software system is produced.

Advantages of Evolutionary Model

1. Early Delivery
   • Working software is available early.
2. Customer Feedback
   • Users can give feedback after each iteration.
3. Easy to Manage Changes
   • Changes can be added in next cycle.
4. Reduced Risk
   • Problems are identified early.
5. Better Quality
   • Continuous improvement improves final product.

Disadvantages of Evolutionary Model

1. Difficult to Manage
   • Multiple iterations can be complex.
2. Requires Strong Planning
   • Needs proper control and scheduling.
3. Not Suitable for Small Projects
   • Can be time-consuming for simple systems.
4. More Costly
   • Repeated cycles increase cost.

The Spiral Model is a software development process model that combines the features of:

•  Iterative Model (repeated development cycles)
•  Linear / Waterfall Model (step-by-step structured phases)
•  Strong focus on risk analysis

It was proposed by Barry Boehm.

The model develops software in repeated loops (spirals), and each loop improves the product step by step.

 Structure of Spiral Model

Each loop (cycle) in the spiral has 4 main phases:

A. Objective Identification (Planning Phase)

In this phase, we define:

• What is the goal of the project?
• What are the requirements?
• What are the alternatives?
• What are the constraints (budget, time, technology)?

 Output: Clear objectives and plan for the iteration

B. Risk Analysis (Most Important Phase)

In this phase, we:

• Identify possible risks (cost, time, technical issues)
• Analyze how serious they are
• Find solutions to reduce risks

 Example risks:

• Budget overrun
• Wrong requirements
• Technology failure

 If risks are high, we may use prototyping to test ideas.

C. Development and Testing (Engineering Phase)

In this phase:

• Actual software is developed
• Coding is done
• Testing is performed
• Integration of modules happens

 Output: Working version of software (increment)

D. Review & Planning Next Iteration

In this phase:

• Customer feedback is taken
• Product is evaluated
• Decision is made:
  • Continue next spiral cycle OR
  • Stop development if complete

 Next loop is planned with improvements

 Diagram Concept 

Each loop of spiral = one development cycle:

Planning → Risk Analysis → Development → Testing → Review → Next Loop

 Advantages of Spiral Model

a.  Best for large and complex projects
b. Strong risk management
c. Early detection of problems
d. Software is developed in early stages (prototypes available)
e. Flexible to changes

 Disadvantages of Spiral Model

a. Very costly model
b. Complex to manage
c. Not suitable for small projects
d. Requires expert risk analysis
e. Too much documentation and control

 When to Use Spiral Model?

Use it when:

• Project is large and complex
• Risk is high
• Requirements are unclear
• Example: Banking systems, defense systems, aerospace software

 Example of Spiral Model

 Example: Online Banking System

A bank wants to build a secure mobile banking app.

 Spiral Cycle 1:

• Plan: Basic login + account view
• Risk: Security issues in authentication
• Solution: Use OTP + encryption
• Develop: Simple login system
• Review: Customer testing

 Spiral Cycle 2:

• Plan: Add money transfer feature
• Risk: Transaction failure, fraud risk
• Solution: Two-factor authentication
• Develop: Transfer module
• Review: Feedback collected

 Spiral Cycle 3:

• Plan: Add bill payment system
• Risk: Payment gateway failure
• Solution: Backup gateway integration
• Develop & Test feature