Solution

Prototyping Model

Definition: Build quick prototype (throwaway or evolutionary) to clarify unclear requirements via customer feedback, then build actual product.

Steps: Requirements Gathering (vague) → Quick Design → Build Prototype → Customer Evaluation → Refine Prototype → Engineer Final Product

Advantages:

• Requirement clarity, better customer involvement
• Early risk detection, reduces rework
• Demonstrates feasibility

Problems / Disadvantages:

• Customer may confuse prototype with product (expects quick delivery)
• Developer may take shortcuts (poor design compromises)
• Scope creep, cost/schedule uncertainty
• Extra effort if throwaway prototype discarded

Use when: Requirements vague, GUI-heavy, innovative, human-computer interaction systems.