User Centred Design - Revision history

Suhridk: /* Conceptual Design */

2012-01-18T17:43:28Z

Conceptual Design

Suhridk: /* Interaction Design Patterns */

2012-01-17T19:11:42Z

Interaction Design Patterns

Suhridk: /* Evaluation */

2012-01-17T19:01:39Z

Evaluation

Suhridk: /* High Fi Prototypes */

2012-01-17T19:01:10Z

High Fi Prototypes

Suhridk: /* Match between system and real world */

2012-01-17T15:02:10Z

Match between system and real world

Suhridk: /* Readability */

2012-01-17T11:20:12Z

Readability

Suhridk: /* Closure */

2012-01-17T11:06:38Z

Closure

Suhridk: /* Consistency */

2012-01-17T10:43:35Z

Consistency

Suhridk: /* Memory Load */

2012-01-17T10:42:29Z

Memory Load

Suhridk: /* Natural Language Interaction */

2012-01-17T10:37:07Z

Natural Language Interaction

@@ Line 57: / Line 57: @@
 ** A clear set of concepts that can be applied to an application
 ** A clear set of relationships that describe how those concepts relate to one another – A mapping from the concepts and relationships we want to use to a mental model of the users who will be using our system
 * How ? '''Metaphors.'''
 * The notion of a metaphor in interaction design is the translation of the physical to the digital – where you borrow concepts and rules so that users can apply their knowledge of the physical world.

← Older revision		Revision as of 19:11, 17 January 2012
Line 231:		Line 231:
	= Interaction Design Patterns =		= Interaction Design Patterns =

−	*	+	* Examine the interaction between a user and the system.
		+	* Describe challenges a user faces when performing a particular task.
		+	* Provides a language for designers and users to communicate with.
		+	* Describe dynamic, changing systems.
		+	* Vary in level of abstraction.. eg. high level - return to safe state, to application specific such as Web tabbed navigation.
		+	* e.g. Breadcrumb trail, Drag and Drop,
		+	* Closed loop in public display systems.
		+	* Wizard - lead the user through interface step by step.
		+	* Pattern languages also exist.

← Older revision		Revision as of 19:01, 17 January 2012
Line 228:		Line 228:
	* Representative set of users perform representative tasks, work naturally and provide ratings at the end of the session.		* Representative set of users perform representative tasks, work naturally and provide ratings at the end of the session.
	* Identifying problems: through think aloud protocol or retrospective verbal protocol.		* Identifying problems: through think aloud protocol or retrospective verbal protocol.
		+
		+	= Interaction Design Patterns =
		+
		+	*

← Older revision		Revision as of 19:01, 17 January 2012
Line 219:		Line 219:
	* Uses material we expect to find in the end product, looks like the final thing.		* Uses material we expect to find in the end product, looks like the final thing.
	* "Real" look and feel, serves as a living specification. Disadvantages: worth the expense if it might be changed later ? Developers can be reluctant to change it.		* "Real" look and feel, serves as a living specification. Disadvantages: worth the expense if it might be changed later ? Developers can be reluctant to change it.
		+
		+	= Evaluation =
		+
		+	* Heuristic Evaluation: Experts go through a system looking for problems guided by heuristics.
		+	* Experts do it individually and then come together go through all problems they found and agree on a final set of problems and a rating of severity for each problem.
		+	* Also can be collaborative.
		+	* User evaluations: done by real users. See how system performs on usability criteria.
		+	* Representative set of users perform representative tasks, work naturally and provide ratings at the end of the session.
		+	* Identifying problems: through think aloud protocol or retrospective verbal protocol.

← Older revision		Revision as of 15:02, 17 January 2012
Line 197:		Line 197:
	* e.g. use shopping basket.		* e.g. use shopping basket.
	* Make information appear in a natural and logical order. for e.g. for Arabic countries, natural reading order is right to left.		* Make information appear in a natural and logical order. for e.g. for Arabic countries, natural reading order is right to left.
		+
		+	= Prototypes =
		+
		+	* Need a bridge between talking to users in the abstract and building a full blown system.
		+	* Prototyping is that bridge.
		+	* Very useful while discussing ideas with stakeholders.
		+	* Encourages reflection on design, explore alternative designs without committing to one idea.
		+	* Dimensions:
		+	** Fidelity: Rough and ready or fully working applications.
		+	** Evolutionary Fitness: Something we carry forward in each stage, abandoned as soon as evaluation is done.
		+
		+	== Low Fi Prototype ==
		+
		+	* A low fidelity prototype is a rough and ready prototype: easy to make, clear to stakeholders that they can be criticized, designers dont have too much stake in them.
		+	* Storyboarding: Each panel demonstrates a beat in time. A beat can be changes of context within an application, users inputting something, system responding with feedback or errors.
		+	* Interaction Sketching: creation of thumbnails, layouts rapidly. Produce many designs to explore design space. Lots of tools, templates available.
		+	* Wizard of Oz: Human simulates the system.
		+
		+	== High Fi Prototypes ==
		+
		+	* Uses material we expect to find in the end product, looks like the final thing.
		+	* "Real" look and feel, serves as a living specification. Disadvantages: worth the expense if it might be changed later ? Developers can be reluctant to change it.

← Older revision		Revision as of 11:20, 17 January 2012
Line 188:		Line 188:
	* Fonts		* Fonts
	* Colour/Background		* Colour/Background
		+	* Group things that are used together.
		+	* Alignment, Multiple columns etc.
		+
		+	== Match between system and real world ==
		+
		+	* Speak users language, follow real world conventions, making info appear in a natural and logical order.
		+	* No computing language or HCI language.
		+	* e.g. use shopping basket.
		+	* Make information appear in a natural and logical order. for e.g. for Arabic countries, natural reading order is right to left.

← Older revision		Revision as of 11:06, 17 January 2012
Line 182:		Line 182:

	* The sense of having completed something.		* The sense of having completed something.
		+	* e.g. getting money in the atm.
		+
		+	== Readability ==
		+
		+	* Fonts
		+	* Colour/Background

← Older revision		Revision as of 10:43, 17 January 2012
Line 178:		Line 178:
	* Design interfaces should have similar operations and use similar elements for similar tasks.		* Design interfaces should have similar operations and use similar elements for similar tasks.
	* Main benefits are consistent interfaces are easier to learn and use, can predict operations, less likely to make errors.		* Main benefits are consistent interfaces are easier to learn and use, can predict operations, less likely to make errors.
		+
		+	== Closure ==
		+
		+	* The sense of having completed something.

← Older revision		Revision as of 10:42, 17 January 2012
Line 163:		Line 163:
	* Use recognition rather than recall.		* Use recognition rather than recall.
	* One of the key reasons to move to direct manipulation is not having to rely on recall memory.		* One of the key reasons to move to direct manipulation is not having to rely on recall memory.
		+
		+	== Visibility of System Status ==
		+
		+	* Make what has to be done completely obvious.
		+
		+	== Feedback ==
		+
		+	* Providing info to the user on the current state of the system, what has been achieved.
		+	* Helps the user keep track of where they are in the interaction.
		+	* Feedback has to be immediate rather than delayed.
		+
		+	== Consistency ==
		+
		+	* Design interfaces should have similar operations and use similar elements for similar tasks.
		+	* Main benefits are consistent interfaces are easier to learn and use, can predict operations, less likely to make errors.

← Older revision		Revision as of 10:37, 17 January 2012
Line 146:		Line 146:
	* Weakness - get into loops if recognition fails.		* Weakness - get into loops if recognition fails.
	* Accent problem.		* Accent problem.
		+
		+	= Interaction Design =
		+
		+	* Draw on HTA's, scenarios, goals/plans, interaction styles, devices and...
		+	* Principles.
		+	* Numerous researches have come up with a set of principles to guide interaction design:
		+	** Shneiderman's 8 golden rules.
		+	** Nielsen's 10 usability heuristics.
		+
		+	== Support User Goals ==
		+
		+	* Make goal satisfaction conditions visible and easy to infer.
		+
		+	== Memory Load ==
		+
		+	* Use recognition rather than recall.
		+	* One of the key reasons to move to direct manipulation is not having to rely on recall memory.