1. Analyzing and representing the activities of your users
Task Analysis
Analyzing and representing the activities of your users

2. Project Part 1 reminder Due Sept. 20 (less than 2 weeks!)
READ description and template
Focus on the problem, not the solution
Start gathering your data now!
Ask for help and feedback
Good communication skills are key
And please spell and grammar check

3. Results of Requirments Gathering & Task Analysis
Real-world constraints
User characteristics + Personas
Task - subtask decomposition
Includes sequencing information
Use Cases & Scenarios
Possibly workflow diagrams, flow charts, ER or object models
Usability Requirements

4. Making Sense Card Sorting Affinity Diagrams
Software tools for task analysis
Software tools for flow charting
Software tools for analysis of activities
Outline programs

5. Affinity Diagram - “Sorted Cards”
From Interaction Design, Preece Rogers and Sharp

6. Task Analysis
Process of analyzing and documenting how people perform their jobs or activities
Task-subtask decomposition

7. Task Model as an Outline
Lists, outlines, matrices
Use expanding/collapsing outline tool
Add detail progressively
Know in advance how much detail is enough
Can add linked outlines for specific subtasks
Good for sequential tasks
Does not support parallel tasks well
Does not support branching well

8. Task Model as an Outline - Example
Using a lawnmower to cut grass
Step 1. Examine lawn
Make sure grass is dry
Look for objects laying in the grass
Step 2. Inspect lawnmower
Check components for tightness
Check that grass bag handle is securely fastened to the grass bag support
Make sure grass bag connector is securely fastened to bag adaptor
Make sure that deck cover is in place
Check for any loose parts (such as oil caps)
Check to make sure blade is attached securely
Check engine oil level
Remove oil fill cap and dipstick
Wipe dipstick
Replace dipstick completely in lawnmower
Remove dipstick
Check that oil is past the level line on dipstick …

9. Hierarchical Task Analysis (HTA)
Graphical notation & decomposition of tasks
Goals – what the user wants to achieve
Tasks – do these to achieve the goals
Not necessarily computer related
Sequential dependencies
Create new document before entering text
Multiple occurrences of tasks
Subtasks – lower-level tasks
Tasks organized into plans
Clusters of subtasks with a preferred order and prerequisite conditions

10. Task Model - Borrow Book
Sequences added as annotations
Can also show hierarchy as indented text
Goal
Tasks to
complete goal
Subtasks to
carry out
one task
From Interaction Design, Preece Rogers and Sharp

11. Another representation
0. In order to borrow a book from the library
1. go to the library
2. find the required book
2.1 access library catalogue
2.2 access the search screen
2.3 enter search criteria
2.4 identify required book
2.5 note location
3. go to correct shelf and retrieve book
4. take book to checkout counter

12. HTA: Types of Plans Fixed sequence Optional tasks Waiting events
Cycles
Time-sharing
Discretionary

13. HTA

14. Use Case Description of a user’s goal in using a system
Focuses on user-system interaction
One path through a use case is sometimes called a scenario
Often presented as a series of steps
Diagram of actors and use cases

15. Use Case example Arrange Meeting
1. The user chooses the option to arrange a meeting.
2. The system prompts user for the names of attendees.
3. The user types in a list of names.
4. The system checks that the list is valid.
5. The system prompts the user for meeting constraints.
6. The user types in meeting constraints.
7. The system searches the calendars for a date that satisfies the constraints.
8. The system displays a list of potential dates.
9. The user chooses one of the dates.
10. The system writes the meeting into the calendar.
11. The system s all the meeting participants informing them of them appointment

16. Use Case Diagram

17. Essential Use Case
Description of important or frequent user interactions
Tries to avoid assumptions of use cases
More generalized steps, user roles
Three parts:
Name
User intention
System responsibility

18. Essential Use Case Example
Arrange-Meeting
USER INTENTION SYSTEM RESPONSIBILITY
Arrange a meeting
Request meeting attendees
and constraints
Identify meeting attendees
Suggest potential dates
Choose preferred date
Book meeting

19. Entity Relationship Diagrams
Object Oriented Models
Objects/people with links to related objects
Stress relationship between objects and actions
Links described functionally and in terms of strength
Task: Develop design for final project
objects - pens, paper, drawing tools, etc.
actors - Mary, Bob, Sally
composite objects - the “team”
About relations, not procedures
Complements HTA & flow charts

20. Object Model: Simple Drawing System
Objects
page, line, point
Relations
page contains zero or more lines and points
Lines defined by two points
Actions on objects
Page: clear
Points: create, delete, move
Lines: create, delete, move
Etc

21. Object Model: Line Text Editor
Objects
Files, lines, characters
Relations
File is sequence of lines
Line is sequence of characters
Actions on objects
Files: create, delete, rename
Lines: create, delete, move, copy
Characters: insert, delete, move, copy

22. Workflow Documents going from one person/organization to another
Multiple participants in an activity

23. Workflow Example - Document Flow
Create Travel
Request
(Traveler)
Ensure Funds
Available
(Accounting)
Approval
(Dean)
Notification of
Approval
(Dean)
No Funds
Notification of
Approval
(Dean)
Make Trip
(Traveler)
Complete Expense
Report
(Traveler)
Approval
(Accounting)
Etc

24. From Interaction Design, Preece Rogers and Sharp

25. Flow Charts Flow Chart of Task Steps Complete, can become complex
Sequential flow, branching, parallel tasks.
Includes actions, decisions, logic, by all elements of the system
Mature, well-known, good tools for doing it

26. Flow Chart Example Start Continue? Document Manual Operation Y N Input
Display
End

27. Usability Requirements
Usability goals: such as learnability, consistency, robustness, etc.
For each – ways to measure and judge success
Time to complete key tasks - min, max
Time to become proficient - do given set of tasks in given time
Subjective satisfaction
MUST have this at start
Refine for later testing

28. Usability Requirements Example
Usability Current Worst Target Best Observed
Attribute Level Value Value Value Value
Initial Use: Time to
edit a given document
during first use of system
Learnability: Time to edit a
given document after one
hour of use
Time to create
outline
Subjective
first impression

29. Summary Determine what data you need
Gather it using various appropriate methods and techniques
Represent the tasks and subtasks, plus other related information
Use this data as basis for design
Note: Be efficient!

30. Assignment: Persona
Think about all the characteristics of a user that may be important, their goals and motivations
Not a wish list of things the person wants…
You should create multiple personas for different types of users
So what should distinguish each one?

31. Exercise Movie ticket kiosk
What data gathering techniques would you use? Who would you talk to?
What are typical user characteristics?
What is a typical scenario of use?
What is an atypical or problem scenario?
What would you represent using HTA?
What could you represent using ER diagram?
What could you represent using flowchart?