Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

ISO 9001:2000 Documentation Requirements
Educational Research: Competencies for Analysis and Application, 9 th edition. Gay, Mills, & Airasian © 2009 Pearson Education, Inc. All rights reserved.
User and Task Analysis Howell Istance Department of Computer Science De Montfort University.
System Design and Analysis
Usability & Usability Engineering. Usability What is usability Easy to use? User Friendly?
Task Analysis Analyzing and representing the activities of your users.
Computers: Tools for an Information Age
Usability 2004 J T Burns1 Usability & Usability Engineering.
Preece Chapter 7.7 & Mc Cracken Chapter 3
3 Chapter Needs Assessment.
Chapter 2 Accountants as Business Analysts
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
TC176/IAF ISO 9001:2000 Auditing Practices Group.
Quality Improvement Prepeared By Dr: Manal Moussa.
Requirements Gathering and Task analysis. Requirements gathering and task analysis 4 Requirements gathering is a central part of systems development understanding.
McGraw-Hill/Irwin© 2006 The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 3 Needs Assessment
Usability 2009 J T Burns1 Usability & Usability Engineering.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Introduction to Systems Analysis and Design Trisha Cummings.
Copyright 2010, The World Bank Group. All Rights Reserved. Training and Procedural Manuals Section B 1.
S/W Project Management
Instructional Design Brian Newberry. Instructional Design Instructional Design is a systematic process for the creation of educational resources.
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Chapter 8: Systems analysis and design
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Business Analysis and Essential Competencies
Requirements Engineering
Chapter 5 Job Analysis.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Chapter 4 Finding out about tasks and work. Terminology GOAL: End result or objective TASK: An activity that a person has to do to accomplish a goal ACTION:
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
System Analysis-Gathering Requirements.  System analysis is the process of gathering info about existing system, which may be computerized or not, while.
1 Introduction to Software Engineering Lecture 1.
Vocabulary 1 Research Process. 1. Problem definition: the purpose of the study should be taken into account; the relevant background info; what info is.
Understanding Task Analysis
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.
Task Analysis Overview, utility Types of task analysis Sources and use.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Systems Development Life Cycle
User and Task Analysis © Ed Green Penn State University Penn State University All Rights Reserved All Rights Reserved 12/5/2015User and Task Analysis 1.
Copyright 2010, The World Bank Group. All Rights Reserved. Testing and Documentation Part II.
(c) 2007 McGraw-Hill Higher Education. All rights reserved. Accountability and Teacher Evaluation Chapter 14.
Chapter 15: Analytical evaluation. Aims: Describe inspection methods. Show how heuristic evaluation can be adapted to evaluate different products. Explain.
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.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Work Plan Development Section A 1.
Human Resource Management JOB ANALYSIS
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
TC176/IAF ISO 9001:2000 Auditing Practices Group.
WORKSHOP ON ACCREDITATION OF BODIES CERTIFYING MEDICAL DEVICES INT MARKET TOPIC 9 CH 8 ISO MEASUREMENT, ANALYSIS AND IMPROVEMENT INTERNAL AUDITS.
Job Analysis Rashmi Farkiya. Contents INTRODUCTION NEED FOR JOB ANALYSIS. APPROACHES TO JOB ANALYSIS COMPONENTS OF JOB ANALYSIS. PROCESS OF JOB ANALYSIS.
Chapter 9 Database Planning, Design, and Administration Transparencies © Pearson Education Limited 1995, 2005.
Getting Ready for the NOCTI test April 30, Study checklist #1 Analyze Programming Problems and Flowchart Solutions Study Checklist.
Chapter 7: Designing solutions to problems OCR Computing for A Level © Hodder Education 2009.
Classroom Assessment A Practical Guide for Educators by Craig A
User-centred system design process
JOB, ROLE, COMPETENCY AND SKILLS ANALYSIS
Object oriented system development life cycle
Gaurav Dubey & Frank Ritter
Lecture 09:Software Testing
Introduction to Systems Analysis and Design
Research Design Shamindra Nath Sanyal 12/4/2018 SNS.
Evaluation.
HCI Evaluation Techniques
Chapter 5 Architectural Design.
Presentation transcript:

task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7

task analysis 2 © Copyright De Montfort University 1998 All Rights Reserved User interfaces are designed for.. a new system to replace an existing manual system e.g. library information system an existing computer system being redesigned –functionality remains the same –functionality is extended or changed in some way. a completely new system with no manual equivalent (generally rare) There is usually some situation with existing users and usage that can be studied and analysed.

task analysis 3 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis provides an essential basis for –early stages of interface design –evaluation of design at early and late stages –structuring training in system use –structuring and design of documentation

task analysis 4 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Techniques HTA – This and other related techniques focus on what actually happens, rather than what should happen –Eg Obtaining a balance from an ATM Cognitive task analysis. This technique aims to describe some of the cognitive characteristics of users tasks. –Eg The time to recognise interpret and respond to an on-screen instruction

task analysis 5 © Copyright De Montfort University 1998 All Rights Reserved Levels of Task Analysis relate to existing situation or new system. General Analysis of User Characteristics Detailed Analysis of tasks in present job(s) Subset of tasks to be included in new system Analysis of Actions and Objects in new system

task analysis 6 © Copyright De Montfort University 1998 All Rights Reserved General Analysis level who are the users –classify the users into one or more groups –define characteristics of the group what are the main task components of the users’ present job –what proportion of time is spent in different tasks –what causes variations in this where are the tasks carried out what equipment (other than the computer system) are used what communication is there between the user and other people

task analysis 7 © Copyright De Montfort University 1998 All Rights Reserved Detailed analysis of tasks in present job what is the hierarchical structure of main tasks, and subtasks within these main tasks how do users see the structure of their job in terms of tasks for each task identified –what information is required –what actions arise or result from decisions –what feedback is provided on effect of actions –what affects successful performance –what are the possible errors and what factors cause these

task analysis 8 © Copyright De Montfort University 1998 All Rights Reserved Detailed analysis of tasks in present job what are the good features of the existing system which should be retained in the subsequent redesign what are the bad features of the existing system that should be designed out what skills are required for each task how are the required skills trained initially and how are these retained

task analysis 9 © Copyright De Montfort University 1998 All Rights Reserved Objectives of task analysis to support interface design identify a hierarchy of user goals, tasks and subtasks together with a plan describing how and when these are done represent lowest level task as a set of procedures –include statements of information requirements and exception conditions identify set of actions and associated objects

task analysis 10 © Copyright De Montfort University 1998 All Rights Reserved Requirements for a task analysis method a structure to represent goals, subtasks, procedures, objects and actions a means of collecting data from experts in the task domain a means of representing the analysis to –check validity of the analysis back with experts –communicate with others in design team guidance for mapping the analysis to the design

task analysis 11 © Copyright De Montfort University 1998 All Rights Reserved Hierarchical task analysis (HTA) Structural components goal - statement of a desired state to be achieved –e.g. obtain a bank account balance operation - things done in order to achieve goals –e.g. produce a paper copy showing current balance sub-operations- subordinate operations to attain main operation plan - specifies when the conditions when each sub- operation will be carried out

task analysis 12 © Copyright De Montfort University 1998 All Rights Reserved Hierarchical task analysis (HTA) Originally devised to define training requirements in process industry - method needs additionally –descriptions of information requirements for lowest level sub-operations –dictionary of objects and associated actions Representation –tree diagram or tabular format Advantages of HTA –simple, informal notation –but still requires considerable skills on part of analyst.

task analysis 13 © Copyright De Montfort University 1998 All Rights Reserved Relating the model to interface requirements Errors in performance can result from: some information –not available when required –available but not sufficiently accurate –available and accurate, but not correctly perceived user’s knowledge of task goal incomplete insufficient or delayed feedback user’s ability to formulate correct decision is inadequate delay in being able to communicate decision to rest of system

task analysis 14 © Copyright De Montfort University 1998 All Rights Reserved Implications for interface design when a task has to be performed ensure that the necessary information is available –so for each task supported by the interface, what information is required? user decisions need to be communicated quickly to the system –so for each task, how will the user input decisions? feedback on task performance should be available –so for each task, how will feedback information be presented and what form should this take?

task analysis 15 © Copyright De Montfort University 1998 All Rights Reserved Means of collecting task analysis data interviews with potential users observations of users performing tasks by trained observers activity sampling activity logging (by observer) activity logging (by user) - 'diary of activities‘

task analysis 16 © Copyright De Montfort University 1998 All Rights Reserved Further Reading