Software Engineering Prototype Model

Software Engineering

Prototype Model

Software prototyping creates a working model (prototype) of the system to help clarify requirements and gather customer feedback before full-scale development.

The Prototype model extends the iterative approach by building prototypes early to validate ideas.
It is widely used when requirements are unclear or when stakeholders need to see a working example to provide feedback.
Developers build a simplified version (prototype) quickly to demonstrate functionality and collect changes.
After refining the prototype based on feedback, the final system design and development proceed with clearer requirements.

Steps followed in the Prototyping Model

Requirement Recognition and Gathering

Collect the primary requirements and identify the core functionality to include in the prototype. Focus on the areas most in need of clarification.

Prototype Development

Quickly build a working prototype that demonstrates selected features and workflows. The prototype need not be fully functional or efficient — its purpose is communication.

Customer Review and Refinement

Present the prototype to stakeholders, collect feedback, and update the prototype as needed. Repeat this cycle until stakeholders are satisfied and requirements are stabilized.

Advantages of Prototype Model

Improves requirement clarity and increases stakeholder confidence.
Allows early detection and removal of defects, reducing overall cost.
High flexibility — requirements can evolve based on real feedback.
Helps identify missing functionality and usability issues early.
Reduces risk by validating concepts before heavy investment.

Disadvantages of Prototype Model

Can be costly and time-consuming if prototypes are iterated excessively.
Prototype code is sometimes inappropriately promoted to production, leading to poor-quality systems.
May produce insufficient documentation if focus stays on throwaway prototypes.
Stakeholders might expect the prototype's features to appear in the final system without understanding trade-offs.
If the prototype is repeatedly rejected, development time and cost can increase significantly.

Courses

Chapters