C3 DESIGN TECHNIQUES Flashcards

1
Q

It is important to identify the characteristics of target user population

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Characteristics to identify of the target user population

A
Age, gender, culture, language
Education (Literacy? Numeracy?)
Physical Limitations
Computer Experience (typing?)
Motivation, attitude
Domain Experience
Application Experience
Work environment and other social context
Relationships and communication patterns
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Many applications have only one kind of user

A

False (have several kinds)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Kinds of users can be categorized to what way?

A
By role (student, teacher)
By characteristics (age, motivation)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Is a fictitious character used as a specific representative of a user class

A

Persona

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Advantages of Persona

A

Convenient handle for talking about user classes
Focuses on a typical user, rather than extreme
Encourage empathy

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Disadvantages of Persona

A

May be misleading

Stereotype trap

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Techniques on doing User analysis

A

Questionnaires
Interviews
Observation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Obstacles encountered on User Analysis

A

Developers and users are sometimes systematically isolated from each other
Some users are expensive to talk to

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

You’ll identify the individual tasks the program might solve. What analysis is this?

A

Task Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Each task is a goal

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Often helps to start with overall goal of the system and then decompose it hierarchically into tasks

A

Task Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Essential Parts of Task Analysis

A

What needs to be done?
What must be done first to make it possible?
What steps are involved in doing the task?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Other Questions to Ask about a Task

A

Where is the task performed?
What is the environment like? Noisy, dirty, dangerous?
How often is the task performed?
What are its time or resource constraints?
How is the task learned?
What can go wrong? (Exceptions, errors, emergencies)
Who else is involved in the task?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How to do a Task analysis?

A

Interviews with users

Direct observation of users performing tasks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Important things to identify in the domain

A

People (user classes)
Physical objects
Information Objects

17
Q

It is not important to determine important relations between the things

A

False

18
Q

Identify multiplicities of things are relations is important

A

True

19
Q

CRUD stands for

A

Create, Read, Update, Delete

20
Q

This asks on what the system should do?

A

Requirements Analysis

21
Q

Common Errors in User Analysis

A

Describing what your ideal users should be,

rather than what they actually are

22
Q

Common Errors in Task Analysis

A

Thinking from the system’s point of view, rather than the user’s

Fixating too early on a UI design vision

Bogging down in what users do now, rather than why they do it

Duplicating a bad existing procedure in software

Failing to capture good aspects of existing procedure

23
Q

Questions to Ask for better User an Task Analysis

A

Why do you do this? (goal)

How do you do it? (subtasks)

24
Q

Weaknesses to look in current situation

A

Goal failures
Wasted time
User Irritation

25
Q

Hints for Better User and Task Analysis

A

Questions to ask
Look for weaknesses in current situation
Contextual inquiry
Participatory Design

26
Q

Observe users doing real work in the real work environment

A

Contextual Inquiry

27
Q

It is important to establish master-apprentice relationship

A

True

28
Q

This include representative users directly in the design team

A

Participatory Design

29
Q

Identify the user classes

A

User analysis

30
Q

Discover tasks

A

Task Analysis

31
Q

Finds the entities and relationships in the domain

A

Domain Analysis