Prototyping

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/30

encourage image

There's no tags or description

Looks like no tags are added yet.

31 Terms

1
New cards
What is a wireframe? (3)
A two-dimensional skeletal outline of a webpage or app; gives an overview of page structure, layout, information architecture, user flow, functionality and intended behaviours; keeps styling, colour and graphics to a minimum because it usually represents the initial product concept
2
New cards
When does wireframing take place? (1)
Early in the project lifecycle
3
New cards
What are the advantages of wireframing? (3)
Gives an early visual to review with the client; lets users review it as early feedback for prototype usability tests; checks that page content and functionality are positioned correctly for user and business needs
4
New cards
What are the disadvantages of wireframing? (3)
Without design or technical detail, the client may find the concept hard to grasp; supporting communication is often needed to explain why elements are positioned as they are; added content may be too much to fit the wireframe layout
5
New cards
What is the template for designing a wireframe? (4)
Divide the page into a grid of rows and columns; place a block for each main area (header, navigation, content, footer); add placeholders for text, images and controls; label each block with its purpose
6
New cards
What is a prototype? (3)
A tool for traversing a design space where design alternatives and their rationales can be explored; a way for designers to communicate the rationale of their design decisions; stimulates reflection and helps designers frame, refine and discover possibilities (Lim et al., 2008)
7
New cards
What are the types of prototype? (3)
Paper (low fidelity); Wizard of Oz; digital (high fidelity) and real system (native)
8
New cards
What is a paper (Lo-Fi) prototype? (3)
Often surprisingly effective; the experimenter plays the computer; focused on broad design ideas
9
New cards
What is a Wizard of Oz prototype? (3)
The user's computer is a slave to the experimenter's computer; the experimenter provides the computer's output; especially useful for AI and other hard-to-implement systems
10
New cards
What is a digital (Hi-Fi) prototype? (2)
Built in software tools (e.g. Visual Basic, Visio, PowerPoint, web tools even for non-web UIs); looks and feels like the anticipated final product
11
New cards
What is the difference between horizontal and vertical prototypes? (2)
Horizontal covers breadth (many features, little depth); vertical covers depth (few features in full detail)
12
New cards
Why is a sketchier prototype better for early design? (3)
Use paper or sketchy tools rather than real widgets; real-looking widgets make people focus on the wrong issues such as colours, alignment and names; sketchy prototypes keep the focus on overall structure and fundamental design
13
New cards
What are the features of a Hi-Fi prototype? (3)
Useful for detailed evaluation of the main design elements; a crucial stage in client acceptance; generally developed fairly well into the project
14
New cards
What does Hi-Fi mean in terms of look and functionality? (2)
Similar in look and feel to the anticipated final product; not necessarily similar in functionality
15
New cards
How is a Hi-Fi prototype produced? (2)
In the development environment that will be used for implementation; or in packages that let interactive effects be mocked up easily
16
New cards
What are the problems with Hi-Fi prototypes? (3)
People believe them; they suggest the system can definitely be implemented; developers are reluctant to discard them because of the time and effort spent
17
New cards
What is the commitment problem? (3)
Writing and debugging lots of code creates a psychological sense of commitment; you are tempted to keep code that should be scrapped; it is hard to throw away work you have put effort into
18
New cards
How does paper prototyping break the commitment problem? (3)
It forces you to throw the prototype away; a paper mockup forms no part of the finished software; this maximises creative freedom in early iterations
19
New cards
What are the features of a Lo-Fi prototype? (3)
Focused on broad design ideas (content, form, structure, tone, key functionality, navigation); designed to be produced and thrown away quickly; captures very early design thinking and helps generate and evaluate many design solutions
20
New cards
What materials can be used for a Lo-Fi prototype? (3)
Screen-sized pieces of stiff paper and index cards; Post-its in different colours; overlays of acetate to simulate dynamic features
21
New cards
When should you switch from a Lo-Fi to a Hi-Fi prototype? (2)
When you are spending lots of time replicating design details on paper; because the whole point of Lo-Fi is a low investment in the build
22
New cards
What are the main practical issues with paper prototypes? (4)
Robustness (how long will it last); scope (too much detail); instructions (will someone know what to do); flexibility (can it be adjusted quickly)
23
New cards
How is a Lo-Fi prototype used in practice? (4)
Designers sit alongside the people who will use the final system and make the prototype work; record comments and design issues as they arise; give a structuring narrative because people find it hard to react without instruction; step through a scenario or carry out a task
24
New cards
What are the practicalities of building a prototype? (6)
Don't worry about efficiency or robustness; use fake data and fake the system (no back end); don't use real widgets, just show what they look like; use a storyboard of screens (can be wireframe style); show just the outlines of controls; support some behaviour such as changing screens, like a movie of the interaction
25
New cards
What is the goal of a quick prototype? (1)
To see some of the interface very quickly (within hours)
26
New cards
What are the trade-offs in prototyping? (4)
High-quality graphics make convincing prototypes but may cause premature commitment to design decisions; special-purpose prototypes answer specific questions but are expensive to build for every issue; realistic prototypes make user test data more valid but may postpone testing or require throw-away builds; iterative refinement allows continual testing but may discourage radical transformations
27
New cards
What should a good prototyping tool do? (4)
Allow easy, rapid modification of interface details or functionality; allow direct manipulation of components for designers who are not programmers; facilitate code reuse for incremental and evolutionary prototypes; not constrain the designer to default styles for interface objects
28
New cards
What questions can a prototype help answer? (2)
Is this approach a good idea; what are the real requirements and specifications
29
New cards
How is a prototype used to test whether an approach is a good idea? (5)
Usually only a few test users are needed (most benefit comes from the first 3); refine the interface after each test; transfer the design from UI specialists to programmers; often better than written specifications; compare Design A versus Design B
30
New cards
How are prototypes used to find the real requirements? (2)
As a basis for participatory design; involves users in the design process, not just the evaluation
31
New cards
What is the template for a prototype task? (4)
Choose the task or scenario to test; build the screens needed for each step; link the screens so the user can move between them; test with users and record feedback