L4

Question 1

Goals of IxD

Answer 1

Develop usable products

Question 2

Framing the Problem Space

Answer 2

Underlying assumptions and claims need to be made explicit

Question 3

Conceptual Model

Answer 3

A way for designers to straighten out their thinking before they start laying out widgets

An outline of what users can do with the product

It is an abstract model

Question 4

Aim with interaction design process & lifecycle model

Answer 4

Developing a product that helps its users achieve their goals

Question 5

How to do ID?

Answer 5

1. Identity needs and requirements
2. Develop alternative designs to meet the requirements
3. Create interactive versions to be communicated and assessed
4. Evaluate what is being built during the process

Question 6

Why is it important to involve users?

Answer 6

To ensure that development continuous to take users’ activities into account
- involvement helps developers to gain a better understanding of users’ goals
- more appropriate and usable product

Expectations management
- realistic expectations
- no surprises - no disappointments
- timely training
- communication, but no hype

Ownership
Make the user active stakeholders
- more likely to forgive or accept problems
- can make a big difference to acceptance and success of product

Question 7

Three caregories of user:

Answer 7

1. Primary: frequent hands-on
2. Secondary: occasional or via someone else
3. Tertiary: affected by its introduction, or will influence its purchase

Wider term: stakeholders

Question 8

Personas

Answer 8

A fictional character representing different user type within a targeted demographic

A narrative,
describing a usage pattern
embodied in a functional user
by means of text and images
and based in a project data

A tool in UCD projects

Communicated through any kind of deliverables

A way to package the users’ capabilities characteristics etc

Helps bring users into the design team and make them as team as the technical details and the design concepts

This description is the base starting point of a persona

Benefits:

Users’ goals and needs become a common point is focus for the team

Solution can be guided by meeting the needs of user personas

Features can be prioritised based in the needs of one or more personas

Provide a human “face” so as to focus empathy on the personas represented by the demographics

Question 9

What are we trying to achieve in the requirements activity and how? (Two aims) (three ways)

Answer 9

Two aims:
1. Understand as much as possible about users, task, context
2. Produce a stable set of requirements

How?
- data gathering activities
- data analysis activities
- all of this a iterative

Question 10

Why is getting requirements rights crucial?

Answer 10

This stage is where failure occurs most commonly

Question 11

Different kinds of requirements

Answer 11

Functional:
- what the system should do
- historically the main

Non-functional:
- memory size, response time

Data:
- what kinds of data need to be stored?
- how will they be stored (ex database)?

Environment or context of use:
- physical: dusty, noisy, vibration, light, heat, humidity etc
- social: sharing of files, if displays, in paper, across, great distances, with individually, privacy for clients
- organisational: hierarchy, IT department’s attitude and remit, user support, communications structure and infrastructure, availability of training