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.

Slides:



Advertisements
Similar presentations
Requirements gathering
Advertisements

Context Diagram Yong Choi BPA CSUB.
Use Case & Use Case Diagram
Task Analysis Material from Authors of Human Computer Interaction Alan Dix, et al.
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Task Analysis Summer Introduction In the last chapter we looked through the UCSD process. We identified TA as an important part of the system.
Chapter 14: Usability testing and field studies. 2 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept.
User and Task Analysis Howell Istance Department of Computer Science De Montfort University.
COMP106 Assignment 2 – A new interface design Proposal 6.
Programming System development life cycle Life cycle of a program
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
System Design and Analysis
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
Task Analysis Analyzing and representing the activities of your users.
Monash University, SIMS, Semester One, DATA GATHERING FOR INFORMATION SYSTEMS DEVELOPMENT CSE Information Systems 1 CSE Information Systems.
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Preece Chapter 7.7 & Mc Cracken Chapter 3
Object-Orientated Design Unit 3: Objects and Classes Jin Sa.
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
About the Presentations The presentations cover the objectives found in the opening of each chapter. All chapter objectives are listed in the beginning.
Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.
Chapter 3 Planning Your Solution
Systems Analysis I Data Flow Diagrams
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 6 - Use cases and activity diagrams Dr.
Systems Life Cycle A summary of what needs to be done.
The Software Development Cycle Defining and understanding the problem.
Introduction to Systems Analysis and Design Trisha Cummings.
Lecture Outline 11 The Development of Information Systems Chapter 8 page 390+
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Managing the development and purchase of information systems (Part 1)
Chapter 8: Systems analysis and design
1 © 2005 course technology University Of Palestine Chapter 6 Storyboarding the User’s Experience.
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
ITEC224 Database Programming
© 2001 Business & Information Systems 2/e1 Chapter 13 Developing and Managing Information Systems.
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 5 Requirements Gary Marsden ( ) July 2002.
ECE 264 Object-Oriented Software Development Instructor: Dr. Honggang Wang Fall 2012 Lecture 3: Requirements Specification, C++ Basics.
Feasibility Study.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
Chapter 5 Flowcharting Copyright © 2010 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.
Systems Analysis and Design in a Changing World, 6th Edition
User Interfaces 4 BTECH: IT WIKI PAGE:
Understanding Task Analysis
Systems Development Life Cycle
Requirements specification Why is this the first major stage of software development? –Need to understand what customer wants first Goal of requirements.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
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.
CHAPTER 3 – JOB ANALYSIS. KEY CONCEPTS AND SKILLS ➲ Define job analysis ➲ Reasons for conducting job analysis ➲ Types of information required for job.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Program Design. Simple Program Design, Fourth Edition Chapter 1 2 Objectives In this chapter you will be able to: Describe the steps in the program development.
Strategies & Knowledge for Independent Learning Group Work SKIL SKIL cards are sets of cards that explain how to use different learning strategies. They.
Progression in KS3/4 Algorithms MONDAY 30 TH NOVEMBER SUE SENTANCE.
1 After the scenarios are formulated Find all the use cases in the scenario Describe each of these use cases in more detail Participating actors Describe.
CHAPTER 6 OBJECT ANALYSIS.
CSE 110: Programming Language I Matin Saad Abdullah UB 404.
Analysis. This involves investigating what is required from the new system and what facilities are available. It would probably include:
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.
CMPE 280 Web UI Design and Development August 29 Class Meeting
User-centred system design process
Chapter 5 Task analysis.
Systems Analysis and Design
Systems Development and Documentation Techniques
The Development of Information Systems Chapter 8 page 348+
Essentials of Systems Analysis and Design Fourth Edition
Use Case Modeling - techniques for detailing use cases
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Using Use Case Diagrams
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Presentation transcript:

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 Distinguish between different types of task analysis Carry out an HTA on an existing system Explain and show how the results of an HTA can be used to improve the usability of a proposed interactive system

5.2 Task analysis Result –Description of tasks that users do when they interact with a system Aim –Find out what the old system enables users to do Focus –Goals and actions (procedures and methods) that users carry out –What users know about their work and tasks –Psychological processes such as perception and memory –Objects and entities on which users act –Relationship between objects and attributes TA should inform, not constrain development of new system TA very useful for “walk-up-and-use” systems –Don’t want to train users –System should be as natural as possible

5.3 What is task analysis? Means of analysing and describing the jobs people do –Provides both method and notation Focus on –peoples’ goals and the actions they carry out –things people know (skills and abilities) –the things they act on

5.4 Purposes of task analysis Purpose –Help designers to understand existing systems, tasks and skills required in people’s existing jobs. Advantage –Contributes to better understanding of users’ requirements Evaluation of existing system –Assists in design of new system –Triggers insights of how to do the task better Notation –Simple and descriptive –Should cover both tasks and the users

5.5 Approaches to TA Not all tasks structures are hierarchical  HTA not always applicable Several approaches –HTA –Procedural –Knowledge-based (KB) –Entity-relationship (ER) Procedural TA –All activities are executed step-by-step, linear and sequential –Directional flow with a start and end –Preceding task must be completed before commencing with next one –Represented in flowchart diagram

5.5.1 Inputs to and outputs of TA Inputs –Problem statement –Observation of existing systems –Analysis of users Outputs –HTA or other document, e.g. matrix –Problem statement –Observations of existing system Good and bad points –Analysis and profile of the user population Issues –Who are the users? –How diverse is the user population? –How to provide universal access? –Why don’t people use the system? –Observe goals as well as tasks

5.5.2 Data collection Ask people –Assume that they have adequate insight –May not always tell the truth Observe users working –Users might be nervous, not acting naturally –Users might be conscious not to make mistakes –Users might show only subset of tasks that they know well Talk to users informally, in focus groups or interviews Read available documentation or training material Do the task yourself Familiarise yourself with existing systems Analyse real tasks, i.e. don’t set up tasks superficially Develop abstractions of real tasks Conduct experiments Ethnographic methods, social probes, surveys Contextual enquiries

5.6 Hierarchical Task Analysis One of the most common forms of TA Involves –Identifying goals that user wants to achieve –Decomposing goals into tasks –Further decomposing into subtasks –Repeat; stop at the level of actions

5.6.1 HTA example 1: Withdraw cash from ATM 0 Withdraw cash 1 Check machine will work 1.1 Look at status indicator 1.2Look for card logo 2 Insert card 3Enter PIN number 4Select Language 5Initiate withdrawal transaction 5.1Select withdraw cash 5.2Specify account 5.3 Enter amount 6Complete transaction 6.1Take card 6.2 Take cash 6.3 Take statement

5.6.2 Adding plans Hierarchical diagram / text specifies which subtasks are part of a task Does not specify how the subtasks are carried out Plans are used to describe –how sub-tasks are combined –order of subtasks –conditional or optional subtasks –optimum way of using sub-tasks –any repetition required or involved HTA not complete without complete set of plans to guide implementation of sub-tasks ATM example –Next slide

Plan 0: do 1; if possible do 2; repeat 3 until PIN correctly entered; do 4; do 5; do 6. Plan 1: do 1.1, 1.2 in any order Plan 5: do 5.1; do 5.2; do 5.3. Plan 6:wait until card available; do 6.1; wait until cash available; do 6.2; wait until statement available; do Withdraw cash 1Check machine will work 1.1 Look at status indicator 1.2Look for card logo 2Insert card 3Enter PIN number 4Select Language 5Initiate withdrawal transaction 5.1Select withdraw cash 5.2 Specify account 5.3 Enter amount 6 Complete transaction 6.1Take card 6.2Take cash 6.3Take statement HTA example: Plans added

E2: Example 2 The manual task of filing documents in a filing cabinet... –You have an unsorted stack of documents –Your filing cabinet contains folders that are ordered somehow –How do you get all the documents into the correct folder?

E2/T0: Filing cabinet 0. Store documents in filing cabinet 1.File lots of documents 2.File one or two documents Plan 0:Do 1 or 2

E2/T2: Filing one or two things Simply find the appropriate folder and put the documents in... 2.File one or two documents 2.1.Open cabinet 2.2.File each document 2.3.Close cabinet Plan 2:Do 2.1., (2.2. repeatedly) then 2.3.

E2/T2.2: Filing each document 2.2.File each document Find appropriate file Open file Place document in file Close file Plan 2.2:Do 2.2.1, , , then

E2/T1: Filing lots of documents Strategy Sort the documents into order first then split the sorted documents up into ‘categories’ (ie all the documents whose author begins with ‘A’) then work through the filing cabinet, putting each category into the right file 1.File lots of documents 1.1.Choose criteria on which documents are sorted 1.2.Sort all documents to be filed into order 1.3.Split documents up into categories 1.4.Open cabinet 1.5.Place each category of document into file 1.6.Close cabinet Plan 1: Do 1.1., 1.2., 1.3., 1.4., (1.5. repeatedly) then 1.6.

E2/T1.1: Choosing sorting criteria 1.1.Choose criteria on which documents are sorted Choose alphabetical by title of document Choose alphabetical by author of document Choose date order Plan 1.1:Do any one of , , or

E2/T1.5: Placing categories in files 1.5.Place each category of document into file Open file Place each document in file Close file Plan 1.5: Do , ( repeatedly) then

HTA: E2 0. Store documents in filing cabinet 1.File lots of documents 1.1.Choose criteria on which documents are sorted 1.2.Sort all documents to be filed into order 1.3.Split documents up into categories 1.4.Open cabinet 1.5.Place each category of document into file 1.6.Close cabinet 2.File one or two documents 2.1. Open cabinet 2.2. File each document Find appropriate file Open file Place document in file Close file 2.3. Close cabinet Plan 0: Do 1 or 2 Plan 1: Do 1.1., 1.2., 1.3., 1.4., (1.5. repeatedly) then 1.6. Plan 2: Do 2.1., (2.2. repeatedly) then 2.3. Plan 2.2: Do 2.2.1, , , then

E2: Things to note... Note … –The overall task is numbered 0 –The tasks are all described by verbs –Each task that is decomposed must have a plan to go with it –Plan X must only refer to sub-tasks to X Think about … –Imagine that you are designing an electronic filing system –What does this HTA tell you about filing systems? –Which bits of the manual task would you keep, and which would you do away with or redesign? –Why?

E3. Example Jill creates a stack of new catalogues in a corner of her kitchen. When she is preparing dinner, she can flip through a catalogue to see what’s new or on sale or what strikes her interest. In the evening she may pick out five or six catalogues to look at while the family is watching TV. She may even take a few to bed, or to the bath. Generally she simply browses through pictures, reading descriptions only when the pictures look interesting. When she finds something interesting she may dog-ear the page, draw a circle round it or mark the page with a sticky note. She keeps catalogues with marked pictures around until she wants to make a purchase.

E3/T0: Example 0.Using catalogues 1.Browse items 2.Mark items Plan 0: do 1 then 2 if item found

E3/T1: Example 0.Using catalogues 1.Browse items 1.1.Browse by what’s new 1.2.Browse by sales 1.3.Browse by items that interest 1.4.Browse by catalogues Browse in kitchen Browse while watching TV Browse in bed 1.4.4Browse in bath 2.Mark items Plan 1: do 1.1 or 1.2 or 1.3 or 1.4

E3/T2: Example 0.Using catalogues 1.Browse items 2.Mark items 2.1.Circle item 2.2.Mark page Dog-ear page Sticky on page Plan 2: do 2.1 or 2.2

E3/T2: Example 0.Using catalogues 1.Browse items 2.Mark items 2.1.Circle item 2.2.Mark page Dog-ear page Sticky on page Plan 2.2: do or 2.2.2

5.6.5 Key features interactive system based on HTA Flexibility Interactivity Portability (Location and hardware) Flexible browsing capability Suitable functionality These are passed as requirements to the design cycle

Summary Task analysis gives designers a means of describing how people do their jobs Serves different purposes in design and development