Software Development Models: Pick the Right One by Spotting Keywords, Not by Memorizing

01 What is a software development model?

A software development model describes the approach used to move a project from requirements to delivery. Some projects follow a linear sequence (requirements → design → coding → testing → delivery), while others need rapid prototyping, risk analysis, or incremental releases.

02 Mapping keywords to models

When faced with a question, ask five questions: Are the requirements stable? Are they clearly expressed? Is the risk high? Does the project need batch delivery? Must it respond quickly to change? The answers point to a specific model:

Stable requirements → Waterfall or V‑Model

Unclear requirements → Prototype model

High risk → Spiral model

Batch delivery needed → Incremental model

Frequent changes → Iterative model or Agile/Scrum

03 Waterfall model

Stages flow sequentially: requirements analysis, high‑level design, detailed design, coding, testing, maintenance. It works well for projects with clear, stable requirements, mature technology, and strict documentation needs. Drawbacks include poor adaptability to change, late defect detection, high rework cost, and delayed user feedback.

04 V‑Model

Each development stage has a corresponding testing stage: requirements ↔ acceptance testing, high‑level design ↔ system testing, detailed design ↔ integration testing, coding ↔ unit testing. The model emphasizes that testing is planned alongside development.

05 Prototype model

Used when users cannot articulate their needs. A quick prototype is built, shown to users, and iteratively refined based on feedback, gradually clarifying requirements. Risks include users mistaking the prototype for the final product, quality issues if the prototype is turned into production without proper rework, and scope creep.

06 Spiral model

Centers on risk analysis. Each spiral consists of planning, risk analysis, engineering, and user evaluation, then repeats. Suitable for large, complex, high‑risk projects (e.g., aerospace, core financial systems) where each iteration assesses technical, cost, schedule, and requirement risks.

07 Incremental model

The system is delivered in functional increments. Core functionality is released first, followed by additional features in subsequent batches. Example: an e‑commerce platform released in four versions (browsing + login, then cart + order, then payment + order query, then points + coupons). Benefits include early user value, risk distribution, and easier refinement.

08 Iterative model

Focuses on repeated improvement. A rough version is built first, then each iteration refines the system (e.g., first iteration enables order flow, second adds inventory checks, third adds coupons, fourth optimizes performance). Distinguishes from incremental: incremental adds new functionality blocks, while iterative refines the same functionality over cycles.

09 Agile development

Prioritizes rapid response to change through short cycles, frequent deliveries, close customer involvement, and teamwork. Suitable for fast‑changing requirements, internet products, and environments with smooth communication. Drawbacks include high team skill demands and potential loss of scope control.

10 Scrum framework

Key terms: Sprint (short cycle), Product Backlog, Sprint Backlog, Daily Scrum, Product Owner, Scrum Master, Development Team. Scrum implements Agile principles via these artifacts and events.

11 Selection table

Summarizes which model fits which scenario:

Stable, clear requirements → Waterfall

Development‑test correspondence → V‑Model

Unclear requirements → Prototype

Large, complex, high‑risk → Spiral

Batch delivery → Incremental

Multi‑round refinement → Iterative

Fast‑changing needs → Agile/Scrum

12 Practice questions

1. A new data‑analysis platform with vague requirements and a need for a demonstrable UI should use the Prototype model because it clarifies needs through quick mock‑ups and user feedback.

2. A aerospace control system that is large, technically complex, and high‑risk should use the Spiral model, as each cycle focuses on risk analysis before proceeding.

Self‑test

What projects suit the Waterfall model? – Stable, clear requirements, mature technology.

What is the biggest drawback of Waterfall? – Poor fit for changing requirements, late defect discovery, high rework cost.

What does the V‑Model emphasize? – One‑to‑one mapping between development and testing phases.

Which model fits unclear user requirements? – Prototype model.

Which model fits large, complex, high‑risk projects? – Spiral model.

Which model supports batch delivery? – Incremental model.

Which model uses multi‑round refinement? – Iterative model.

Which approach suits fast‑changing needs? – Agile development.

What is a Sprint in Scrum? – A short‑duration iteration.

How to differentiate Incremental vs Iterative? – Incremental adds functionality blocks; Iterative refines the same system over cycles.

Remember: match the keyword cues to the appropriate model to answer exam scenarios quickly.