User and Task Analysis Howell Istance Department of Computer Science De Montfort University.

Slides:



Advertisements
Similar presentations
Structured Design The Structured Design Approach (also called Layered Approach) focuses on the conceptual and physical level. As discussed earlier: Conceptual.
Advertisements

HFSD ISDE 2005 Users and User Characteristics. HFSD ISDE 2005 Contents Users - Designing for diversity Characteristics of users.
Database Systems: Design, Implementation, and Management Tenth Edition
Tutorial 8: Developing an Excel Application
Task Analysis Material from Authors of Human Computer Interaction Alan Dix, et al.
© De Montfort University, Characteristics of Good Dialogues Howell Istance Department of Computer Science De Montfort University.
Programming Logic and Design Fourth Edition, Introductory
Classification of Users. 4 What assumptions can be made about target users’ groups in terms of: –expected frequency of use of system –knowledge of task.
1 Users, tasks and environment Howell Istance School of Computing (chapter 3.1 – 3.5 : McCracken and Wolfe )
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
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.
Copyright © 2005, Pearson Education, Inc. Chapter 8 Command and Natural Languages.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
File Systems and Databases
System Design and Analysis
ID sept 03 John T Burns© Copyright De Montfort University 2003 All Rights Reserved Users and User Characteristics.
© De Montfort University, Design Process Howell Istance Department of Computer Science De Montfort University.
Principles and Methods
Preece Chapter 7.7 & Mc Cracken Chapter 3
User interface design Designing effective interfaces for software systems Objectives To suggest some general design principles for user interface design.
Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.
© De Montfort University, Users and User Characteristics Howell Istance Department of Computer Science De Montfort University.
Course Instructor: Aisha Azeem
Requirements Gathering and Task analysis. Requirements gathering and task analysis 4 Requirements gathering is a central part of systems development understanding.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Input/Output Design User Interface Design
User Interface Theory & Design
Revision Lesson : DESIGNING COMPUTER-BASED INFORMATION SYSTEMS.
Introduction to Systems Analysis and Design Trisha Cummings.
Chapter 5 Models and theories 1. Cognitive modeling If we can build a model of how a user works, then we can predict how s/he will interact with the interface.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
1 Shawlands Academy Higher Computing Software Development Unit.
Chapter 8: Systems analysis and design
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
11.10 Human Computer Interface www. ICT-Teacher.com.
ISDE 2011 Users and User Characteristics. ISDE 2011 Contents Users - Designing for diversity Characteristics of users.
UI Style and Usability, User Experience Niteen Borge.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
SE: CHAPTER 7 Writing The Program
Human Factors Issues Chapter 9. Human Factors = ergonomics WWII based – military significance… … a necessary part of medical device design…
I Power Higher Computing Software Development The Software Development Process.
Software Architecture
User Interface Theory & Design Lecture 6a 1.  User interface is everything the end user comes into contact with while using the system  To the user,
Editors And Debugging Systems Other System Software Text Editors Interactive Debugging Systems UNIT 5 S.Sharmili Priyadarsini.
IFS310: Module 12 User Interface Design - Navigation/Communication between the system and users.
E.g.: MS-DOS interface. DIR C: /W /A:D will list all the directories in the root directory of drive C in wide list format. Disadvantage is that commands.
Individual Differences in Human-Computer Interaction HMI Yun Hwan Kang.
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.
The Software Development Process
Chapter Three The UNIX Editors.
Human Factors Issues Chapter 8. What is Human Factors? Application of the scientific knowledge of human capabilities and limitations to the design of.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Chapter 13 Finalizing Design Specifications
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
TRAINING PACKAGE The User Action Framework Reliability Study July 1999.
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.
Human Resource Management Lecture 2 MGT Last Lecture Title and Course Code Introduction Text Book Chapters (Course Topics) What is HRM (managing.
Database Design, Application Development, and Administration, 6 th Edition Copyright © 2015 by Michael V. Mannino. All rights reserved. Chapter 5 Understanding.
DBS201: Data Modeling. Agenda Data Modeling Types of Models Entity Relationship Model.
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
Chapter 6 : User interface design
Chapter 16: User Interface Design
Object oriented system development life cycle
Design AH Computing.
Human Factors Issues Chapter 8 Paul King.
Tools of Software Development
Introduction to Systems Analysis and Design
MBI 630: Week 11 Interface Design
Presentation transcript:

User and Task Analysis Howell Istance Department of Computer Science De Montfort University

SOFT Interactive Systems Objectives...

SOFT Interactive Systems User Centered Design Process

SOFT Interactive Systems System Related User Characteristics n What characteristics can you expect of the users of your interface? u frequency of use u discretion to use the system u knowledge of the task which the system will support u knowledge of computers u experience of other similar systems u general abilities, e.g. literacy, vision u attitude towards computers (and your system) u existing skills (keyboard, mouse)

SOFT Interactive Systems Three-Dimensional Framework n Three Dimensional Framework for User Classification Knowledge of Computers Knowledge of Task Frequency of Use (low)(high)

SOFT Interactive Systems Design implications n Provide for high degree of sophistication in interface: u range of functions provided, u flexibility to combine functions to provide new commands, u possibilities to customise interface to own needs. n Lower requirement for user support than with other user types. n Can utilise programming languages and extensible command languages (e.g. macros and scripts). Computer professionals

SOFT Interactive Systems Highly variable group in terms of knowledge and experience Design implications n Important to support the user ‘guessing’ or experimenting with how operations can be carried out at the interface. Consistency and a close match to the user’s task model is important. n Frequency of use determines how much the user can be expected to learn short cuts and accelerators. n User support provided by the interface is important. Professionals without programming experience

SOFT Interactive Systems Design implications n Can anticipate significant learning of routine operations to take place, so can make use of abbreviations and codes for data input. n Can expect strong user skills to be developed, such as keyboard skills. n Error messages must be clear and provide specific guidance for recovery. n Cannot expect users to develop deeper knowledge or understanding of the computer system without specific training. Skilled clerks

SOFT Interactive Systems Design implications n Every type of user error must be trapped. This type of user will not be able to infer what is happening or the cause of an error condition. n Require explicit on-screen prompts for each step of the dialogue. n High degree of user support and a low degree of sophistication is required in the interface. ? Naïve users

SOFT Interactive Systems Task Analysis n provides an essential basis for u early stages of interface design u evaluation of design at early and late stages u structuring training in system use u structuring and design of documentation

SOFT Interactive Systems Levels of Task Analysis n 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

SOFT Interactive Systems General Analysis level n who are the users u classify the users into one or more groups u define characteristics of the group n what are the main task components of the users present job u what proportion of time is spent in different tasks u what causes variations in this n where are the tasks carried out n what equipment (other than the computer system) are used n what communication is there between the user and other people

SOFT Interactive Systems Detailed analysis of tasks in present job n what is the hierarchical structure of main tasks, and subtasks within these main tasks n how do users see the structure of their job in terms of tasks n for each task identified u what information is required u what actions arise or result from decisions u what feedback is provided on effect of actions u what affects successful performance u what are the possible errors and what factors cause these

SOFT Interactive Systems Detailed analysis of tasks in present job n what are the good features of the existing system which should be retained in the subsequent redesign n what are the bad features of the existing system that should be designed out n what skills are required for each task n how are the required skills trained initially and how are these retained

SOFT Interactive Systems Actions and Objects n Low level (down the hierarchy) task descriptions can be formulated as actions performed on task-related objects u e.g... change start time of appointment u object: appointment u attribute: start time u action: change/edit n a dictionary of objects, attributes and associated actions can be constructed through process of u rationalisation u generification

SOFT Interactive Systems Building an object dictionary n interviews with users provide textual descriptions of tasks n these can be analysed by identifying u nouns (candidate objects) u verbs (candidate actions) n process of generification to identify what are essentially descriptions of the same thing n process of hierarchy building to identify objects as members of related classes

SOFT Interactive Systems Objectives of task analysis to support interface design n identify a hierarchy of user goals, tasks and subtasks together with a plan describing how and when these are done n represent lowest level task as a set of procedures (using something like pseudocode) u include statements of information requirements and exception conditions n identify set of actions and associated objects

SOFT Interactive Systems Hierarchical task analysis (HTA) Originally devised to define training requirements in process industry - method needs additionally u descriptions of information requirements for lowest level sub- operations u dictionary of objects and associated actions Representation u tree diagram or tabular format Advantages of HTA u simple, informal notation u but still requires considerable skills on part of analyst.

SOFT Interactive Systems Example of HTA Delete block of text in a word processor 1.Delete block of text Goal

SOFT Interactive Systems Example of HTA Delete block of text in a word processor 1.Delete block of text Goal 2) Select 'cut' from Edit menu 1) Select block of text or 2) Select cut icon from toolbar or 2) Press 'delete' key then Tasks

SOFT Interactive Systems HTA representation 1.Delete block of text 1. Select text block 2. Press ‘delete’ 3. Select cut from edit menu 4. Select cut icon from toolbar

SOFT Interactive Systems HTA representation 1.Delete block of text 1. Select text block 2. Press ‘delete’ 3. Select cut from edit menu 4. Select cut icon from toolbar Plan 1: 1-2 or 1-3 or 1-4

SOFT Interactive Systems HTA representation 1.Delete block of text 1. Select text block 2. Press ‘delete’ 3. Select cut from edit menu 4. Select cut icon from toolbar Plan 1: 1-2 or 1-3 or 1-4 1) Anchor the start of the block 2) adjust the extent of the block 3) Anchor end of the block then Subtasks

SOFT Interactive Systems HTA representation of tasks and subtasks 1.Delete block of text 1. Select text block 2. Press ‘delete’ 3. Select cut from edit menu 4. Select cut icon from toolbar 1.Define start of text selection 2. Adjust length of text selection 3. Define end of text selection Plan 1: 1-2 or 1-3 or 1-4 Plan:

SOFT Interactive Systems HTA representation of tasks and subtasks 1.Delete block of text 1. Select text block 2. Press ‘delete’ 3. Select cut from edit menu 4. Select cut icon from toolbar 1.Define start of text selection 2. Adjust length of text selection 3. Define end of text selection Plan 1: 1-2 or 1-3 or 1-4 Plan: Procedure 1) position text insertion in front of first character of block 2)...

SOFT Interactive Systems How far to decompose tasks? 1.Delete block of text 1. Select text block 2. Press ‘delete’ 3. Select cut from edit menu 4. Select cut icon from toolbar 1.Define start of text selection 2. Adjust length of text selection 3. Define end of text selection Plan 1: 1-2 or 1-3 or 1-4 Plan:

SOFT Interactive Systems How far to decompose tasks? 1.Delete block of text 1. Select text block 2. Press ‘delete’ 3. Select cut from edit menu 4. Select cut icon from toolbar 1.Define start of text selection 2. Adjust length of text selection 3. Define end of text selection Plan 1: 1-2 or 1-3 or 1-4 Plan: as far as is useful for the analysis

SOFT Interactive Systems Means of collecting task analysis data n interviews with potential users n observations of users performing tasks by trained observers n activity sampling n activity logging (by observer) n activity logging (by user) - 'diary of activities'