PHASE 1 Plan

PHASE 2 Specification

PHASE 1 Design

PHASE 1 Results

This chapter focuses on transforming prototyping assumptions and requirements into a basis for a prototype design. Before you can effectively prototype, the first important activity is reviewing the balance of assumptions and requirements, including business/marketing, functional, technical, and usability ones. This review will help you determine whether you need more requirements before proceeding to build a prototype. It is also the point where you and your team can be clear about the assumptions (if any) being used as a basis for a software concept. Prototypes allow these assumptions and requirements to be validated, invalidated, ...

Get Effective Prototyping for Software Makers now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.