8.2 Understanding Prototypes

A prototype is an early, simplified model of a software product built to test concepts, explore design options, and gather user feedback before committing to full-scale development. Prototyping is a key activity in the Software Development Life Cycle (SDLC) and is especially valuable when requirements are unclear or likely to change.

---

Why Prototype?

Prototyping helps teams:

• Clarify requirements — stakeholders can see and interact with a model rather than reading abstract specifications.
• Reduce risk — misunderstandings and technical problems are discovered early, before significant resources are spent.
• Gather feedback — real users evaluate the prototype and suggest improvements.
• Validate design decisions — layout, navigation, and workflows can be tested cheaply.

---

Types of Prototypes by Fidelity

Low-fidelity prototypes are quick and cheap to produce, making them ideal for early-stage brainstorming. High-fidelity prototypes are used later to validate detailed design and usability.

---

Types of Prototyping Approaches

1. Throwaway (Rapid) Prototyping

A small part of the system is built quickly to clarify requirements. Once the requirements are understood, the prototype is discarded and the actual system is built from scratch.

• Best for: Highly uncertain or ambiguous requirements.
• Advantage: Prevents poor requirements from being locked in.
• Disadvantage: Time spent on the prototype does not directly contribute to the final product.

2. Evolutionary Prototyping

The prototype is continuously refined through multiple iterations based on user feedback until it eventually becomes the final system.

• Best for: Projects where requirements are expected to change frequently.
• Advantage: Reduces duplication of effort; the prototype is never wasted.
• Disadvantage: Without careful management, the system can become difficult to maintain.

3. Incremental Prototyping

The final system is built as a series of prototypes, each adding more functionality. The prototypes are eventually integrated into the complete product.

4. Extreme Prototyping

Commonly used in web development; consists of three phases — building a static prototype, making it functional with simulated services, and finally integrating real services.

---

Prototyping in the SDLC

Prototyping fits into the design phase of the SDLC but influences all stages:

1. Analysis — prototype helps elicit and confirm requirements.
2. Design — prototype tests UI/UX decisions.
3. Coding — evolutionary prototypes feed directly into implementation.
4. Testing — prototype is evaluated by users; feedback drives iteration.

The iterative cycle of Build → Evaluate → Refine is central to prototyping.

---

Prototyping as a Data-Collection Tool

Prototypes are also used as a data-collection approach (SLO CS-11-G-01). By observing how users interact with a prototype, developers gather qualitative data (e.g., user confusion, workflow preferences) and quantitative data (e.g., task completion times, error rates) that inform the final design.

---

Creating, Testing, and Iterating a Prototype (Business Context)

For a business idea, the prototype development cycle involves:

1. Define the problem — identify the user need your product addresses.
2. Sketch / Wireframe — create a low-fidelity prototype of the key screens or features.
3. Build — develop a higher-fidelity interactive prototype.
4. Test — present the prototype to target users; collect structured feedback.
5. Iterate — revise the prototype based on feedback and repeat until the design is validated.

This cycle aligns with the Minimum Viable Product (MVP) philosophy: launch the simplest version that delivers core value, then improve based on real-world feedback.

---

Summary Table