Fall 2002CS/PSY 67501 Task Analysis Analyzing and describing how people do their jobs/work  -> Go to their environment Examine users’ tasks to better.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

Task Analysis Material from Authors of Human Computer Interaction Alan Dix, et al.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Task Analysis EDU 553 – Principles of Instructional Design Dr. Steve Broskoske.
IAT 334 Interface Design Task Analysis
Chapter 2- Visual Basic Schneider
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
Lecture 13 Revision IMS Systems Analysis and Design.
Task Analysis.
Task Analysis Analyzing and representing the activities of your users.
Computers: Tools for an Information Age
Preece Chapter 7.7 & Mc Cracken Chapter 3
Analyzing and representing the activities of your users
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
Requirements Gathering & Task Analysis – Part 1 of 5 Why, What and How – an Overview This material has been developed by Georgia Tech HCI faculty, and.
Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.
Requirements Gathering & Task Analysis – Part 5 of 5
Requirements Gathering Methods for Requirements Gathering and Requirements Gathering.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 The Traditional Approach to Requirements
Lecture Outline 11 The Development of Information Systems Chapter 8 page 390+
Data Gathering CS361.
Systems Analysis and Design in a Changing World, Fifth Edition
ITEC224 Database Programming
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 5 Requirements Gary Marsden ( ) July 2002.
UML & Prototyping. What is a prototype? A prototype is a small-scale model. It can be (among other things): a series of screen sketches a storyboard,
Data Analysis, Interpretation, & Presentation: Lies, Damn Lies, and Statistics CS561.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Using Information Technology Chapter 11 Information Systems.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Chapter 9 Moving to Design
CMPUT 301: Lecture 16 Task Analysis II Lecturer: Martin Jagersand Department of Computing Science University of Alberta Notes based on previous courses.
Software Design Deriving a solution which satisfies software requirements.
Systems Analysis and Design in a Changing World, 3rd Edition
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Observing Users (finishing up) CS352. Announcements, Activity Notice upcoming due dates (web page) Discussion: –Did your observations have enough detail.
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Analysis and Design in a Changing World, 6th Edition
Task Analysis …and we’ll really get to Ethics this time.
Task analysis Chapter 5. By the end of this chapter you should be able to... Describe HTA and its features Explain the purpose of task analysis and modelling.
Observing Users CS352 Usability Engineering Summer 2010.
Task Analysis Overview, utility Types of task analysis Sources and use.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Data Gathering CS352. Project Proposal Requirements I want: Name of team members Project description (what do you want to do) –This should include a description.
Chapter 2- Visual Basic Schneider1 Chapter 2 Problem Solving.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Data gathering (Chapter 7 Interaction Design Text)
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
School of Engineering and Information and Communication Technology KIT305/607 Mobile Application Development Week 7: Usability (think-alouds) Dr. Rainer.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
Observing Users (finishing up)
SIE 515 Design Evaluation Lecture 7.
System.
Fundamentals of Information Systems, Sixth Edition
Unified Modeling Language
Systems Analysis and Design
“In the midst of chaos, there is also opportunity” - Sun Tzu
Professor John Canny Fall 2001 Sept 11, 2001
task analysis focus on HTA
Observing Users (finishing up)
Task Analysis Analyzing and describing how people do their jobs/work
Human Computer Interaction Universitas Gunadarma
Presentation transcript:

Fall 2002CS/PSY Task Analysis Analyzing and describing how people do their jobs/work  -> Go to their environment Examine users’ tasks to better understand what they need from interface and how they will use it

Fall 2002CS/PSY Components Three key components to include in discussing how people work  Activities  Artifacts  Relations Don’t just focus on computer system artifacts and interactions Study related processes and objects in the environment that people may use and involve  Example: office env---papers, whiteboards, etc.

Fall 2002CS/PSY Task Analysis Focus Focus on observable behaviors  What are the practices, methods, steps, objects, …, used? Observe users, what they do, less so how they do it Not on internal cognitive state of user

Fall 2002CS/PSY Input & Output Gather data:  Documentation  Interviews  Observation  Surveys/questionnaires  Automatic data recording/tracking Represent Data:  Lists, outlines, matrices  Narratives  Hierarchies & Networks  Flow charts

Fall 2002CS/PSY Data to be Gathered Information about users Description of environment  Where the tasks will be performed Major goals of the job  What will result in a successful end state? User preferences & needs  Before they even start: coffee, pen, notebook, log sheets…

Fall 2002CS/PSY Data to be Gathered … Tasks & Subtasks:  Physical  Cognitive  Communication Conditions under which these tasks are done Results/outcomes of tasks Requirements to perform task:  Information  Communication with others  Equipment Must include Should include Could include Exclude

Fall 2002CS/PSY Data Gathering Tools: Docs Documentation  Often contains description of how the tasks should be done (rather than how they are currently being done)  Standards  Manuals  Histories  Best Practices Domain Expert Description  Expert describes how process should work, how tasks should be done  “Knowledge-based” discovery

Fall 2002CS/PSY DGT: Interviews Interviews:  Structured Efficient Require training  Unstructured Inefficient No training  Semi-structured Good balance Often appropriate

Fall 2002CS/PSY Semi-structured Interviews Predetermine data of interest Plan for effective question types How do you perform task x? Why do you perform task x? Under what conditions do you perform task x? What do you do before you perfom…? What information do you need to…? Who do you need to communicate with to…? What do you use to…? What happens after you…? What is the result or consequence of…? What is the result or consequence of NOT…?  See: Gordon & Gill, 1992; Graesser, Lang, & Elofson, 1987

Fall 2002CS/PSY DGT: Observation Observation  In situ, watch users do what they do  Record with videotape To watch later, or again  Take lots of notes, sketches  May require coding the video later  Focus on specific task-relevant behaviors in notes, but later convert to abstract subtasks

Fall 2002CS/PSY DGT: Questions Questions & Answers  Questionnaires Exploratory vs. confirmatory Open-ended vs. categorical (exhaustive) What do you need to perform..? (list) Which of the following is most important to perform…? (select) If you ask it, use it. If you won’t/can’t use it, don’t ask it.

Fall 2002CS/PSY DGT: Think-aloud Questions & Answers, cont’d…  Think-aloud protocol Person talks about what they are doing, while they are doing it (or just before or after) Observer can ask probe questions Why did you just do that?  Note: Probe questions affect performance, as does thinking aloud.

Fall 2002CS/PSY DGT: Logging Automatic tracking  Keystroke/mouse click monitoring  Timers  Logs  Physical location/movement trackers Cell phones Aware Home

Fall 2002CS/PSY Representing Data: Outlines 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  Example, next slide

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 … Task Outline

Fall 2002CS/PSY RD: Narratives Narratives  Describe tasks in sentences  Often expanded version of list or outline  More effective for communicating general idea of task  Not effective for details  Not effective for branching tasks  Not effective for parallel tasks

Fall 2002CS/PSY RD: Hierarchies Hierarchical Task Analysis (HTA)  Graphical notation & decomposition of tasks  Tasks as sets of actions  Tasks organized into plans Clusters of subtasks with a preferred order and prerequisite conditions

HTA

Fall 2002CS/PSY Example Task Clusters Fixed sequence Optional tasks Waiting events Cycles Time-sharing Discretionary

Fall 2002CS/PSY RD: Networks Network / Entity-Relationship Diagrams  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”

Fall 2002CS/PSY Methodology Often list attributes, actions of objects Object: pen simple Attribute: color: red writing: on/off Object: Mary actor Actions: M1: make a sketch M2: organize meeting

Fall 2002CS/PSY RD: Flow Charts Flow Chart of Task Steps  Combines Entity-relationship (network) with sequential flow, branching, parallel tasks.  Includes actions, decisions, logic, by all elements of the system  Abstracted  Mature, well-known, good tools

Fall 2002CS/PSY Flow Chart Start Continue? Document Input Display Manual Operation End Y N

Fall 2002CS/PSY Summary of Task Analysis Determine the data you need Gather it using various appropriate methods and techniques Represent the tasks and subtasks, plus other related information Use this data to improve design Note: Be efficient!