




Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Learn the effective prototyping process in four phases: Plan, Specification, Design, and Results. This guide covers steps for verifying requirements, creating task flows, determining content and fidelity, choosing a method, formulating design criteria, and implementing the design. Use this process to create clickable prototypes for software and design projects.
Typology: Papers
1 / 8
This page cannot be seen from the preview
Don't miss anything!





1
STEP^2 Develop Task Flows
P H A S E^2
Choose a Method
ch 7 STEP^5
Validate the Design
ch 12 (^10) STEP
Deploy the Design
ch 13 (^11) STEP
3 Create the Design
ch 10 8 STEP
ch 4
4
Choose a Tool
ch 8 6
Define Content and Fidelity
ch 5 3 STEP
STEP
Determine Characteristics
ch 6 STEP^4
Select Design Criteria
ch 9 (^7) STEP
Review the Design
ch 11
STEP^9
STEP^1^ Verify Requirements
ch 3
The Effective Prototyping Process
CHAPTER
THE EFFECTIVE
PROTOTYPING
PROCESS
Prototyping is a process anyone can learn and master. Although few master every aspect, there is enough latitude in prototyping that we can all find our own niche in using prototyping for communicating software requirements, designs, and ideas. That those ideas may get passed on and iterated, changed, and refined is all part of the process of software creation. If one chooses wisely and sets expectations accordingly, effective prototyping is a repeatable predictable process of which the results are anything but guesswork. This process is not specialized, complicated, nor lengthy. Effective prototyping is a four-phase process of 11 steps that anyone with an interest can accomplish, whether to create prototypes yourself, manage prototyping in your software creation process, or any other reasonable purpose.
Phase I helps you to determine prototyping needs and to plan the prototyping process accordingly. You will decide what aspects of the software should or should not be prototyped to provide maximum benefit to your prototyping effort.
This book presents a prototyping method in steps that are meant to be scaled to fit the prototyping activity. There will be some steps you will want to follow very closely and use the guided procedures to make sure you get every last detail correct. For quick prototyping, with less of a demand on diligence, you should know the steps and take them into consideration. For example, if you will spend 2 weeks prototyping, then spending half a day planning is not unreasonable. However, if you will just create a quick prototype in an hour, then knowing what the planning issues are and making a more cursory planning would be a reasonable approach.
Step 6 matches your prototyping tool to the method you selected in Step 5. We encourage you to prototype with anything you desire because we believe it is more empowering to use a skill set you already possess and a tool you’re already familiar with. You can maximize the creative time spent prototyping rather than succumbing to the steep learning curve of a less familiar prototyping tool. Chapters 22 through 26 cover some prototyping tools you may already have on your computer but perhaps never realized their uses for prototyping: Office productivity applications (Microsoft Word, Excel, and PowerPoint), Visio, and Acrobat.
After specifying a prototyping strategy, Phase III focuses on executing the prototype through good design. For the accomplished prototyper, good design is already part of the professional practice, and these steps may seem naive or too simplified. For the first-time prototyper, Phase III provides a handy guide to learning how to prototype, including basic steps, good practice, and a guide through making design choices and how to execute them.
or too few details leads to an ineffective use of your time—either in extra time spent prototyping or time spent on a prototype test that is unable to receive needed feedback. It is important to distinguish between the end users of your software and the stakeholders who will help you make the software. Step 4 details the different characteristics of prototypes: audience, stage, speed, longevity, expression, fidelity, style, and medium. Next, you map your prototyping characteristics and content to a method that most closely matches your needs.
Step 5 discusses how to decide which method is right for your current situation. A helpful table and worksheet are included at the end of the chapter to assist you in choosing the right method.
Phase III: Design (Chapters 9 and 10) | 23
The worksheets in this book are works in progress and will be subject to revision and specialization as people outside of the domains we are familiar with begin to use them. You should view the worksheets in this book as a current snapshot of possible future iterations that we plan to make available on our web site: www.effectiveprototyping.com For free updates to these worksheets as well as ability to participate in any discussions about them we invite you to our website.
A key factor in effective prototyping is the ability to defend your prototype’s design. Savvy designers have a unique sensibility for combining design guidelines with technical, end-user, and business requirements to form an elegant solution. A design rationale, based partly on design guidelines, is one of the more successful methods for outlining design decisions. However, not everyone is a designer, and it is not necessary to become one. Step 7 lists some best practices in design guidelines from the fields of cognitive psychology, graphic design, and information design. These design guidelines ensure that your page/screen compositions are not arbitrarily conceived. Even if your prototype cannot be considered the best design, it should be understandable to a general audience, and you should be able to explain the rationale for your decisions.
Step 8 discusses methods for tying together guidelines and requirements to achieve best practice design. In the end, the quality of your prototype is based on the quality of user research, accurate definition of requirements, and your own design exploration/iteration and analysis. Your analysis can only be as thorough as your own well-rounded understanding of the guidelines and requirements as well as an appreciation for the needs of your audience.
Of all the activities of prototyping, the results phase is the one that is perhaps most thoroughly covered by other texts. Therefore it is also where we spend the least amount of our attention. This section is more for the novice who:
A Is not familiar with the proper way to conduct prototype reviews A Has never been involved with the activities and issues of usability testing A Has little experience creating a prototype and converting it into a product These chapters are mostly high-level discussions with pointers to where you can find more information on these well-covered topics.
Step 9 outlines reviews with internal stakeholders and ways to ensure that an effective prototype goes on for validation. Likewise, this chapter discusses the issues around reviews: what to look for and what strategies to use.
Step 10 discusses prototype validation through usability testing and other validation techniques with external stakeholders.
24 | Chapter 2: The Effective Prototyping Process
26 | Chapter 2: The Effective Prototyping Process
“The click thing?” asked Art. “So what do we do now?” asked Ina. “No prototype, full stop,” said Dirk. “Maybe I can put something together,” said Ina. “How?” asked Dirk. “I can just sketch some wireframes real quick,” said Art. “They won’t click,” brooded Dirk, “Whatever that means.” “Well, let’s think this thing out, what would be the most effective way to prototype?” asked Ina. Let’s see what Alfredo thinks.