Effective prototyping for software makers

Arnowitz, J., Arent, M., & Berger, N. (2007). Effective prototyping for software makers. San Francisco: Morgan Kaufmann (Elsevier), pp. 21-50.


Verify prototyping assumptions and requirements:
4 requierments categories:

1. Business/marketing requirements: define the needs of business or marketplace. Derived from market field research, market analysis, competitive analysis, domain expertise, sales force intelligence, focus groups
2. Functional requirements: define the functionality necessary to support the business and market requirements. Derived from field research with user research, market analysis, competitive analysis, domain expertise, force sales intelligence, usability testing
3. Technical requirements: technology needed to implement the requires functionality. Derived from technology research, technical analysis, competitive analysis, technology expertise, sales force intelligence
4. Usability requirements: define the user experience and needed for user adoption of the software. Derived from any combination of user research, task analysis, competitive analysis, domain expertise, sales force intelligence, customer support intelligence, design and prototyping, usability testing

Transforming assumptions into requirements: iterative 3 steps

Step1: gather business, functional, technical, and usability requirements

Step2: inventorize requirements

Step3: prioritize requirements and assumptions

Iteration 1: From idea to first visualization

Iteration 2: From quick wireframe to wireframe

Iteration 3: From wireframe to storyboard

Iteration 4: From storyboard to paper prototype

Iteration 5: From paper prototype to coded prototype

Iteration 6: From coded prototype to software requirements