Chapter 11 discusses prototyping and its uses within the design
process. I think it can be useful to invest time in prototyping because it can give a different
insight as to how a product's interface functions. The book describes two
different types of prototyping, low and high fidelity prototypes. I think
that is important to start off with using low fidelity prototypes out of
cardboard and paper then move on to high fidelity prototypes using software.
This is because designing the interface is an iterative process and low
fidelity prototypes are easier to alter and improve upon. If we were to use a
high fidelity prototype first, we would spend more time on coding the interface
and debugging it rather than focusing on perfecting the interface's features to
suit the user's requirements.
Chapter 13 defines four evaluation
paradigms, quick and dirty, usability testing, field studies and predictive
evaluation. This chapter also provides the DECIDE framework. I think that this a useful guideline for people who are unsure where to begin when evaluating user needs. I noticed how the DECIDE framework has appeared during our museum visit. We have asked the museum visitors about practical problems as well as deciding how to deal with the ethics of anonymity.
Questions to discuss:
Which evaluation paradigm is most suited
to our project and is it feasible (in terms of the time it takes to perform the
evaluations)?
Inga kommentarer:
Skicka en kommentar