C3 DESIGN TECHNIQUES Flashcards
It is important to identify the characteristics of target user population
True
Characteristics to identify of the target user population
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
Many applications have only one kind of user
False (have several kinds)
Kinds of users can be categorized to what way?
By role (student, teacher) By characteristics (age, motivation)
Is a fictitious character used as a specific representative of a user class
Persona
Advantages of Persona
Convenient handle for talking about user classes
Focuses on a typical user, rather than extreme
Encourage empathy
Disadvantages of Persona
May be misleading
Stereotype trap
Techniques on doing User analysis
Questionnaires
Interviews
Observation
Obstacles encountered on User Analysis
Developers and users are sometimes systematically isolated from each other
Some users are expensive to talk to
You’ll identify the individual tasks the program might solve. What analysis is this?
Task Analysis
Each task is a goal
True
Often helps to start with overall goal of the system and then decompose it hierarchically into tasks
Task Analysis
Essential Parts of Task Analysis
What needs to be done?
What must be done first to make it possible?
What steps are involved in doing the task?
Other Questions to Ask about a Task
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 to do a Task analysis?
Interviews with users
Direct observation of users performing tasks
Important things to identify in the domain
People (user classes)
Physical objects
Information Objects
It is not important to determine important relations between the things
False
Identify multiplicities of things are relations is important
True
CRUD stands for
Create, Read, Update, Delete
This asks on what the system should do?
Requirements Analysis
Common Errors in User Analysis
Describing what your ideal users should be,
rather than what they actually are
Common Errors in Task Analysis
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
Questions to Ask for better User an Task Analysis
Why do you do this? (goal)
How do you do it? (subtasks)
Weaknesses to look in current situation
Goal failures
Wasted time
User Irritation
