Tài liệu User Experience Re-Mastered Your Guide to Getting the Right Design- P6 docx

236 User Experience Re-Mastered: Your Guide to Getting the Right Design

ITERATION 5: FROM PAPER PROTOTYPE TO CODED

PROTOTYPE

In the last stages of prototyping, many open design and technical questions can

be answered. The required functionality, the audience, and the business case

are already fi rm (see Fig. 7.10 ) and no longer the source of focus. Now, a high￾fi delity prototype like the one shown in Fig. 7.11 is used to fi rm up the remain￾ing requirements and design details.

Paper Prototype

Business

Functional

Audience

User needs

User needs

Design

Technical

Development

Assumptions

Coded Prototype

Business

Functional

Audience

User needs

Design

Technical

Development

Requirements

Assumptions Requirements

5

FIGURE 7.10

Late high-fi delity prototypes come closer to resembling a software product as well as the

requirements.

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

Verify Prototype Assumptions and Requirements CHAPTER 7 237

FIGURE 7.11

Late prototypes resemble the real software as the requirements become fi rmer, and more

advanced prototype development can take place with greater confi dence.

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

238 User Experience Re-Mastered: Your Guide to Getting the Right Design

ITERATION 6: FROM CODED PROTOTYPE TO

SOFTWARE REQUIREMENTS

In the last step, specifying the requirements from a late high-fi delity user-facing

prototype (here in the form of a coded prototype) enables us to, fi nally, say that

we have validated all the software requirements (see Fig. 7.12 ). The worksheet

that was the basis for evaluating the prototype requirements could now almost

double for a table of contents or central reference point for the software require￾ments. So the journey from the interplay of assumptions and requirements is

now complete with the fi nal product shown in Fig. 7.13 ready to ship; prototyp￾ing has been the primary aid in validating assumptions and transforming them

into requirements. Although, it is important to note that prototyping has been

an aid, not the sole source of requirements validation, such as focus groups,

usability testing, market research, and competitive analysis.

Assumptions

Coded Prototype

Business

Functional

Audience

User needs

Design

Technical

Development

Software Prototype

Business

Functional

Audience

User needs

Design

Technical

Development

Requirements

Assumptions Requirements

6

FIGURE 7.12

Only at the end of the

prototyping process

do the assumptions

fi nally give way to

concrete data to base

the software creation

and development.

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

Verify Prototype Assumptions and Requirements CHAPTER 7 239

SUMMARY

We reviewed requirements setting for prototyping as the fi rst step toward

collectingprototype content. We have seen that prototyping requirements try

to come as close as necessary to the actual business, functional, technical, and

usability requirements. However, a prototype also has the fl exibility to be based

on assumptions. In fact, prototyping can be used to play with assumptions while

being gradually turned into concrete validated requirements. For this validation,

a worksheet template supports the three-step process:

FIGURE 7.13

The fi nal end product

for time entry at the

end of the project.

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

240 User Experience Re-Mastered: Your Guide to Getting the Right Design

Following this validation process and using the worksheet template, you can

be assured that your prototype will address exactly the right assumptions and

requirements your team judges to be important. The worksheet, with the priori￾tization of requirements and assumptions, also helps others understand what

they should and should not be looking for when reviewing your prototype.

1STEP

STEP 2

STEP 3 Gather

• Requirements

Inventory

• Requirements

• Assumptions

Prioritize

• Worksheet 3.1

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.