在網(wǎng)上下載了一個(gè)講義,是關(guān)于怎么在紙上構(gòu)建產(chǎn)品原型的,讀來(lái)受益匪淺。很可惜這個(gè)PDF文件的講義上沒(méi)有作者的姓名和地址,可能是來(lái)自英國(guó)的,因?yàn)槔锩嫣岬搅藙颉T诖酥x謝了。
費(fèi)了一點(diǎn)時(shí)間把它翻譯過(guò)來(lái),這是前半部分,后半部分由我的好朋友王峰協(xié)作,一并謝謝了。以下是中英文對(duì)照。
2007-4-27翻譯初稿 2007-4-29校對(duì)
第二部分由我的朋友王峰翻譯,等我校對(duì)了一起發(fā)上來(lái)。
紙上原型
Today’s Topics
- Paper prototypes
- Wizard of Oz prototypes
Today we’re going to talk about protototyping: producing cheaper, less accurate renditions of your target interface. Prototyping is essential in the early iterations of a spiral design process, and it’s useful in later iterations too. 今天,我們講產(chǎn)品原型:以低投入的、非精確的形式設(shè)計(jì)目標(biāo)產(chǎn)品界面。在早期的迭代式設(shè)計(jì)流程中,原型是一個(gè)基本的方法,而且在之后的迭代(設(shè)計(jì))中也是基本方法。
Why Prototype? 為什么用原型?
- Get feedback earlier, cheaper
快速且低成本地獲得反饋
- Experiment with alternatives
在多種可能中對(duì)比試驗(yàn)
- Easier to change or throw away
輕松修改或者放棄設(shè)計(jì)
We build prototypes for several reasons, all of which largely boil down to cost. 我們因?yàn)橐恍┰驑?gòu)建產(chǎn)品原型,這些原因絕大多數(shù)出于成本的考慮
First, prototypes are much faster to build than finished implementations, so we can evaluate them sooner and get early feedback about the good and bad points of a design. 首先,原型能以比完成(開(kāi)發(fā))快得多的方式構(gòu)建產(chǎn)品行為。這樣,我們能夠很快評(píng)估設(shè)計(jì)方案,獲得關(guān)于設(shè)計(jì)的優(yōu)點(diǎn)和缺點(diǎn)的早期反饋。
Second, if we have a design decision that is hard to resolve, we can build multiple prototypes embodying the different alternatives of the decision. 第二,當(dāng)如果我們的設(shè)計(jì)中包含很難解決的內(nèi)容時(shí),那么我們能夠構(gòu)建多個(gè)應(yīng)對(duì)方案,這些方案考慮了對(duì)多種可能的情況。
Third, if we discover problems in the design, a prototype can be changed more easily, for the same reasons it could be built faster. Prototypes are more malleable. Most important, if the design flaws are serious, a prototype can be thrown away. It’s important not to commit strongly to design ideas in the early stages of design. Unfortunately, writing and debugging a lot of code creates a psychological sense of commitment which is hard to break. You don’t want to throw away something you’ve worked hard on, so you’re tempted to keep some of the code around, even if it really should be scrapped. 第三,當(dāng)我們發(fā)現(xiàn)設(shè)計(jì)中的問(wèn)題時(shí),能夠更容易修改原型,同樣的原因,它能夠被更快地創(chuàng)建。原型具有更強(qiáng)的可塑性。最重要的是,如果設(shè)計(jì)的缺陷非常嚴(yán)重,這個(gè)原型可以很輕松的放棄。有一點(diǎn)很重要,在早期的設(shè)計(jì)工作中不需要做出完善的設(shè)計(jì)。不幸的是,在編寫和調(diào)試大量的代碼來(lái)創(chuàng)建實(shí)際可操作的事務(wù)之后,再想改變就很難了,你不希望丟棄費(fèi)了很大精力的工作成果,所以,你總是試圖保留一些代碼,盡管它們確實(shí)是無(wú)用的。
The prototyping techniques we’ll see in this lecture actually force you to throw the prototype away. For example, a paper mockup won’t form any part of a finished software implementation. This is a good mindset to have in early iterations, since it maximizes your creative freedom. 我們?cè)谶@個(gè)講座中將要看到的原型法會(huì)促使你丟棄(一些不成功的)原型。例如,一個(gè)紙上的模型不屬于任何一個(gè)完成了的可執(zhí)行的軟件。在早期的產(chǎn)品設(shè)計(jì)迭代中,這是一個(gè)好的方法,因?yàn)樗茏畲笙薅鹊膶?shí)現(xiàn)你的創(chuàng)造自由。
Prototype Fidelity 原型的設(shè)計(jì)精度
- Low fidety: omits details
低精度:忽略細(xì)節(jié)
- High fidety: more like finished product
高精度:更像一個(gè)已經(jīng)完成的產(chǎn)品
An essential property of a prototyping technique is its fidelity, which is simply how similar it is to the finished interface. Low-fidelity prototypes omit details, use cheaper materials, or use different interaction techniques. High-fidelity prototypes are very similar to the finished product. 原型方法的基本屬性就是它的精度,簡(jiǎn)言之,精度就是它與完成產(chǎn)品的界面的接近程度。低精度的原型忽略了細(xì)節(jié),使用低成本的材料,或者使用不同的交互技術(shù)。高精度的原型非常接近已經(jīng)完成的產(chǎn)品。
出處:大智交互設(shè)計(jì)
責(zé)任編輯:moby
上一頁(yè) 下一頁(yè) 在紙張上設(shè)計(jì)軟件產(chǎn)品原型的方法 [2]
|