Observing Users (finishing up) CS352. Announcements, Activity Notice upcoming due dates (web page) Discussion: –Did your observations have enough detail.

Slides:



Advertisements
Similar presentations
Microsoft® Access® 2010 Training
Advertisements

The Design Process Where do consumer products begin?
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
Information System Engineering
IAT 334 Interface Design Task Analysis
Chapter 6 Review Questions
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
WEEK 4 Material Lecture 4a (Wed.). Use Cases/Actors o What is a use case ? l A sequence of actions performed by a system that yields an observable result.
Task Analysis.
Task Analysis Analyzing and representing the activities of your users.
Analyzing and representing the activities of your users
DARS Web for Advisor Academic and Enrollment Services, Transfer Articulation & Degree Audit Office (TADA)
Requirements Gathering & Task Analysis – Part 5 of 5
Working with SharePoint Document Libraries. What are document libraries? Document libraries are collections of files that you can share with team members.
An Introduction to Content Management. By the end of the session you will be able to... Explain what a content management system is Apply the principles.
Requirements, cont. …and a word on Ethics. Project Part 1: Requirements Gather data using one or more techniques Learn about environment, users, tasks,
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
Systems Analysis and Design in a Changing World, Fifth Edition
Data Gathering CS361.
Project Analysis Course ( ) Week 2 Activities.
Your User Name is the first portion of your Carleton Connect account eg. mroger4 if the was n.ca
Chapter 8: Systems analysis and design
LBTO IssueTrak User’s Manual Norm Cushing version 1.3 August 8th, 2007.
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.
Chapter 4 User Experience Model. User experience model (Ux) Visual specification of the user interface Visual specification of the user interface Both.
1 © 2005 course technology University Of Palestine Chapter 6 Storyboarding the User’s Experience.
1 Direct Manipulation Proposal 17 Direct Manipulation is when physical actions are used instead of commands. E.g. In a word document when the user inputs.
Introduction to Sequence Diagrams
12 Systems Analysis and Design in a Changing World, Fifth Edition.
Data Analysis, Interpretation, & Presentation: Lies, Damn Lies, and Statistics CS561.
1 ITEC 3010 “Systems Analysis and Design, I” LECTURE 10: Use Case Realizations [Prof. Peter Khaiter]
Advanced English Writing
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
1 © 2005 course technology University Of Palestine Chapter 6 (cont.) Storyboarding the User’s Experience.
Reading, Multiple Choice and Graphic Text.  Information paragraph- presents ideas and information on a topic  News report- presents information in the.
Faculty of Computer & Information
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
S9k Production Floor System Ingredient Inventory Production Inventory Production Dashboard.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
Task Analysis …and we’ll really get to Ethics this time.
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
 Relate Use Cases to  MVC and Application Architecture  CRC  Recap distinctions : Language, Process, Tool  Detail a Use Case  Elements of a Use Case.
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
Capturing and Exploring Requirements with Use Cases and UML Models
Verification & Validation. Batch processing In a batch processing system, documents such as sales orders are collected into batches of typically 50 documents.
The Writing Process Language Arts.
McGraw-Hill/Irwin The Interactive Computing Series © 2002 The McGraw-Hill Companies, Inc. All rights reserved. Microsoft Excel 2002 Working with Data Lists.
2/6/03C-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Requirements and Use Cases.
M1G Introduction to Programming 2 3. Creating Classes: Room and Item.
1 SEQUENCE DIAGRAM EXAMPLE The domain model, showing the navigability of the associations, and the Reserve video (staff scenario) use-case description.
UML - Development Process 1 Software Development Process Using UML.
Use Case Model Use case description.
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.
Observing Users (finishing up)
Paul Ammann & Jeff Offutt
Paul Ammann & Jeff Offutt
Week 12: Activity & Sequence Diagrams
Observing Users (finishing up)
Task Analysis Analyzing and describing how people do their jobs/work
Human Computer Interaction Universitas Gunadarma
Presentation transcript:

Observing Users (finishing up) CS352

Announcements, Activity Notice upcoming due dates (web page) Discussion: –Did your observations have enough detail to make us feel “there”? –If we had been following the inventory guidelines –for Proj. Part 4, what data would we have recorded from the in-class demo?Proj. Part 4 2

Input Input: –Surveys/questionnaires –Interviews –Observation –Documentation –Automatic data recording/tracking

Output Output: making sense of the input: –List of problems (e.g., Steve Krug min 6-7:30) When is this what you need? –Task Outlines –Scenarios & Use Cases After we show these, again ask: when is this what you need? –Diagrams and Flow charts When is this what you need? –Visualizations with counts of Phenomena After we show these, again ask: when are these what you need?

Task Outline 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 v 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 Outlines –Use expanding/collapsing outline tool –Add detail progressively –Can add linked outlines for specific subtasks But: –Good for sequential tasks –Does not support parallel tasks well –Does not support branching well

Scenarios Describe tasks in sentences Effective for communicating general idea of task. Not effective for tasks with much branching, or parallel tasks Scenarios: “informal narrative description” –Focus on tasks / activities, not system (technology) use –~ One path thru a use-case, but from user/task perspective. –“Say I want to find a book by G. Jeffries. I don’t remember the title, but I know it was... I go to the catalog and enter my... I don’t understand why I have to do this, since... However, once..., I am given a choice of... or..., but not... I chose the... because... but now... When I see this, I realize that in fact I made a mistake on..., so I... Finally I see the entry I want. –(See book, p. 506, for the full version.)

Use Cases –Focus on user-system interaction, not tasks. –Less effective than scenarios for the user emotions and reasoning. eg: 1. System displays options for User chooses the option to find out System prompts user for User enters Alternative courses: 3. If the option entered is invalid: 3.1 System displays error message. 3.2 System returns to step If the... (See book p. 511 (?) for the full version.)

Diagrams, Flow Charts. To show sequence, space, relationships…

Other Visualizations Eg: count phenomena over time

Visualizations (cont.) Eg: Co-occurrence of phenomena

Visualizations (cont.) Eg: Across time to show interesting change. Time Gaps opened (light) and closed (dark) over time.

Summary Inputs: Data from interviews, observations, etc. –Lot of raw test and/or recordings. Outputs: Ways to make sense of it. –Task outline (understand task) –Scenario (understand one user’s way of doing things) –Use case (understand several users’ ways) –Diagram/flow charts (relationships, paths, sequences) –Visualization (Understand frequencies, patterns and relationships)