Course contentsShow
← Software Engineering
Lesson 138 of 1,9334. Requirements EngineeringFree lesson

Prototyping for Requirements Discovery

Use throwaway prototypes and mockups to clarify ambiguous requirements and validate understanding early.

Prototyping for Requirements Discovery

What you'll learn: How throwaway prototypes help you uncover hidden requirements and validate understanding before building the real thing.

The Core Idea

When stakeholders struggle to articulate what they need—or when you're unsure if you've understood them correctly—building a quick, rough prototype can break through the confusion. These throwaway prototypes (also called mockups or proof-of-concepts) aren't meant to become production code. They exist purely to spark conversations, clarify vague ideas, and test assumptions early when changes cost almost nothing.

Think of it like sketching house floor plans on napkins before hiring architects. The napkin isn't the blueprint—it's a tool to discover what you actually want.

Why Prototyping Works for Discovery

Some requirements are hard to express in words alone. Stakeholders might say "the dashboard should be intuitive," but what does that actually mean? Show them three different dashboard layouts, and suddenly they can point and say, "This one, but with those features moved here."

Prototypes:

  • Surface ambiguities: When stakeholders see it, they realize what they forgot to mention
  • Validate understanding: You demonstrate your interpretation; they correct misunderstandings immediately
  • Explore alternatives: Quickly compare different approaches before committing
  • Reduce risk: Discovering a fundamental misunderstanding in a prototype takes hours; discovering it in production code takes months

Throwaway vs. Evolutionary

Crucially, these discovery prototypes are disposable. They're built with shortcuts, hardcoded data, and zero concern for quality. Once they've served their purpose—clarifying requirements—you throw them away and build properly. Trying to evolve a quick mockup into production software creates technical debt from day one.

Key Takeaway: Throwaway prototypes are low-cost conversation starters that reveal what stakeholders really need, turning abstract requirements into concrete understanding before you write a single line of production code.