Task Analysis.

Slides:



Advertisements
Similar presentations
Use-Cases.
Advertisements

Use Case Diagrams Damian Gordon.
Use Case & Use Case Diagram
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
MIS 325 PSCJ. 2  Business processes can be quite complex  Process model: any abstract representation of a process  Process-modeling tools provide a.
Task Analysis EDU 553 – Principles of Instructional Design Dr. Steve Broskoske.
Task Analysis Summer Introduction In the last chapter we looked through the UCSD process. We identified TA as an important part of the system.
IAT 334 Interface Design Task Analysis
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
Lecture 8 Electronic Commerce Modelling Techniques
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
Interaction Diagrams Activity Diagram State Machine Diagram
Conversation Form l One path through a use case that emphasizes interactions between an actor and the system l Can show optional and repeated actions l.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
Requirements and Task Analysis
Documenting Requirements using Use Case Diagrams
Task Analysis Analyzing and representing the activities of your users.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Preece Chapter 7.7 & Mc Cracken Chapter 3
Analyzing and representing the activities of your users
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 and Task Analysis. Please attend!! Duke Hutchings: “Window interfaces for multiple monitor systems”: next Monday 2/6, 9:30-11, room 154 student.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
Identifying Needs and Establishing Requirements
Requirements, cont. …and a word on Ethics. Project Part 1: Requirements Gather data using one or more techniques Learn about environment, users, tasks,
1 Chapter 2 Revision: Documentation DFD System FC.
Fall 2002CS/PSY Task Analysis Analyzing and describing how people do their jobs/work  -> Go to their environment Examine users’ tasks to better.
Requirements II: Task Analysis. Objectives By the end of the class, you will be able to… Write detailed task descriptions to inform design. Create scenarios.
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
OBJECT ORIENTED METHODOLOGIES Week04. Agenda… © Jerry Kotuba SYST39409-Object Oriented Methodologies 2  This week  Quiz 1  Take up ICE-01  Check “Grade.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
Data Analysis, Interpretation, & Presentation: Lies, Damn Lies, and Statistics CS561.
Chapter 6 A Use-Case-Driven Process. 2 Definitions The choice of models and the choice of techniques used to express them have a significant impact on.
Objectives By the end of the class, you will be able to… Describe typical users by using “personas” Write detailed task descriptions to inform design.
Software Design Deriving a solution which satisfies software requirements.
Identifying needs and establishing requirements
Process Models: Data Flow Diagrams Chapter 2. Process Modeling Objective: Understand the concept of business processes Understand and create Data Flow.
Observing Users (finishing up) CS352. Announcements, Activity Notice upcoming due dates (web page) Discussion: –Did your observations have enough detail.
Object Oriented Methodologies
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
Task Analysis …and we’ll really get to Ethics this time.
Understanding Task Analysis
Task Analysis CSCI 4800/6800 Feb 27, Goals of task analysis Elicit descriptions of what people do Represent those descriptions Predict difficulties,
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.
1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section
This material has been developed by Georgia Tech HCI faculty, and continues to evolve. Contributors include Gregory Abowd, Jim Foley, Diane Gromala, Elizabeth.
Identifying Needs and Establishing Requirements Presenters: Veronica Gasca Jennifer Rhough.
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.
The Hashemite University Computer Engineering Department
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.
Use Case Diagrams. Introduction In the previous Lecture, you saw a brief review of the nine UML diagrams. Now that you have the clear, you'll start to.
GATHERING DATA Supplementary Note. What are requirements? A requirement is a statement about an intended product that specifies what it should do or how.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Observing Users (finishing up)
Paul Ammann & Jeff Offutt
ATM OO Design and Implementation Case Study
Chapter 5 Task analysis.
Paul Ammann & Jeff Offutt
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Observing Users (finishing up)
Task Analysis Analyzing and describing how people do their jobs/work
Human Computer Interaction Universitas Gunadarma
Presentation transcript:

Task Analysis

Agenda Questions? Task Analysis Practice Project part 1 reminder

Persona assignment Rachel is 24, newly married to the love of her life Morgan, 26. Rachel teaches 2nd grade at the near by Elementary School while Morgan works at the local water treatment plant. They both work 5 days a week, Rachel from the hours of 7:00AM - 4:00PM and Morgan from 6:00AM - 2:30PM. Since both of their work schedules vary significantly, they own two cars, driving to and from work separately. Planning meals can be difficult for the couple. It is hard for Morgan to call Rachel and see what is for dinner, for she cannot answer her cell phone during teaching and vice a versa for Morgan while he is at the plant. Morgan likes to have dinner ready for Rachel when she walks into the door from work, but Rachel is the one who does the grocery shopping and who tends to know what is on hand to cook. Morgan occasionally stops by the local supermarket to pick up what he has a taste for at dinner on his way home from work, but then is told at home by Rachel that there is food already at the house and there is no need to spend more money at the supermarket. Rachel uses the new technology from Food Networking that shows what is available for her to cook and then displays it to Morgan in the morning, showing him what could be made for dinner that evening. Morgan can now prepare meals for Rachel, avoiding the frequent stops to the supermarket on his way home from work and using what is already at the house, eliminating waste.

Describing requirements activities Narratives Personas Scenarios Task Analysis & other task descriptions Use Cases Workflow ER diagrams

Scenario Example Register for classes What kinds of activities could we write a scenario about? Let’s write one together

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

Use Case Diagram

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 emails all the meeting participants informing them of them appointment

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

Task Decomposition Break tasks down into subtasks Continue for as many levels as needed …how many are needed? Not just for computer tasks, but any sort of activity Easily supports sequential tasks Can support parallel tasks & branching Difficult to represent exceptions, errors

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 …

Hierarchical Task Analysis (HTA) Graphical notation & decomposition of tasks Goals – what the user wants to achieve Tasks – do these to achieve the goals Subtasks – lower-level tasks Tasks organized into plans Clusters of subtasks with a preferred order and prerequisite conditions

Task Model - Borrow Book Sequences added as annotations Goal Tasks to complete goal Subtasks to carry out one task From Interaction Design, Preece Rogers and Sharp

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

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

Example Register for classes

Other task representations Flow charts Ordering of task steps, can be complex Includes decisions logic and information Many tools to support Workflow Flow of documents through people and activities Entity Relationship Diagrams Show objects and their relationships About relations, not procedures

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

Workflow Example 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

From Interaction Design, Preece Rogers and Sharp

Entity Relationship Diagrams Object Oriented Models Objects/people with links to related objects Stress relationship between objects and actions Links describe functionally and in terms of strength About relations, not procedures Complements HTA & flow charts

Object Model: ATM Objects Relations Actions on objects Etc Account, ATM machine, ATM card, customer Relations Customer has one or more accounts ATM machine accesses account Actions on objects Account: deposit($), withdraw($), balance ATM machine: authenticate, dispense($), print receipt Etc

Beyond Requirements Task analysis throughout life cycle: Describe and document design ideas Help design menu, dialog structure Help create documentation and help Task descriptions can be given at any necessary abstraction level

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!

Next assignment: Scenario Similar to persona, but focus is on a task Next next assignment: task analysis Do an HTA for a task/activity for your project Activity is how it currently exists, NOT what it would be like with you new system 3 levels deep should be sufficient

Exercise: Movie Ticket Kiosk What data gathering techniques would you use? Who would you interact with? Who are the stakeholders? What are typical user characteristics? What is physical/social/technical environment? 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?

Project Part 1 reminder Due Feb. 12 (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