SBD: Analyzing Requirements Chris North cs3724: HCI.

Slides:



Advertisements
Similar presentations
Chapter 14: Usability testing and field studies
Advertisements

Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
CS305: HCI in SW Development Evaluation (Return to…)
Laura Pejsa Goff Pejsa & Associates MESI 2014
IS214 Recap. IS214 Understanding Users and Their Work –User and task analysis –Ethnographic methods –Site visits: observation, interviews –Contextual.
Saul Greenberg User Centered Design Why User Centered Design is important Approaches to User Centered Design.
Methodology Overview Dr. Saul Greenberg John Kelleher.
James Tam User Centered Design Why User Centered Design is important Approaches to User Centered Design.
1 User Centered Design and Evaluation. 2 Overview Why involve users at all? What is a user-centered approach? Evaluation strategies Examples from “Snap-Together.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #18.
Task Analysis Homework Section 5. Task Analysis HW Grades Overall, very good  Examples from excellent task analyses Some confusion:  Difference between.
Midterm Exam Review IS 485, Professor Matt Thatcher.
IS 425 Enterprise Information I LECTURE 4 Autumn  2004 Norma Sutcliffe.
Recap of IS214. Placing this course in context Creating information technology that helps people accomplish their goals, make the experience effective,
Design Process …and the project.
Contextual Inquiry Material Source: Professor John Landay, UCB.
1 User Centered Design and Evaluation. 2 Overview My evaluation experience Why involve users at all? What is a user-centered approach? Evaluation strategies.
HEC Lausanne > HCI > March 2005 Scenario-Based Design of Interactive Software Université de Lausanne Ecole des Hautes Etudes Commerciales (HEC) Introduction.
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
CS 3724: Introduction to Human Computer Interaction Chris North Jason Lee Szu-Chia Lu.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
SBD: Activity Design Chris North CS 3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
Information Design and Visualization
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Formative Evaluation cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
Usability testing. Goals & questions focus on how well users perform tasks with the product. – typical users – doing typical tasks. Comparison of products.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Scenario-Based Usability Engineering Chris North cs3724: HCI.
SBD: Interaction Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
Level 2 Prepared by: RHR First Prepared on: Nov 23, 2006 Last Modified on: Quality checked by: MOH Copyright 2004 Asia Pacific Institute of Information.
Usability Testing Chris North cs3724: HCI. Presentations karen molye, steve kovalak Vote: UI Hall of Fame/Shame?
Human-Computer Interaction & Usability Unit HCI & Usability Unit ICT&S Center, University of Salzburg.
Requirements Analysis Goal: understand users’ current activities well enough to reason about technology- based enhancements.
SBD: Analyzing Requirements Chris North CS 3724: HCI.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
Requirements Analysis Goal: understand users’ current activities well enough to reason about technology- based enhancements.
Introduction to Usability Engineering Learning about your users (cont.): The field interview 1.
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
SBD: Information Design
SBD: Activity Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
Review Chris North cs3724: HCI. Midterm Topics Scenario-based design: (ch 1-4) SBD background –metrics, tradeoffs, scenarios Requirements analysis –Field.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Chapter 10 Qualitative Field Research Key Terms. Naturalism Approach to field research based on the assumption that an objective social reality exists.
Chapter 10 Qualitative Field Research Key Terms. Naturalism Approach to field research based on the assumption that an objective social reality exists.
User Interface Evaluation Introduction Lecture #15.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Contextual Inquiry & Intro to Ethnography Introduction to HCI & Contextual.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
CS 3724: Introduction to Human Computer Interaction Chris North Regis Kopper.
Learning about your users (cont.).: The field interview CS 352 Usability Engineering Summer 2010.
CS 3724 Usability Engineering Section 2 CRN MW 2:30-3: McB.
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
CS 3724 Introduction to Human Computer Interaction Section 1 CRN TuTh 5:00-6: McB.
Cognitive Models Agenda Who Am I? Cognitive Models
CIS 376 Bruce R. Maxim UM-Dearborn
HCI in the software process
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Informatics 121 Software Design I
Introduction to Human Computer Interaction
SBD: Analyzing Requirements
SBD: Analyzing Requirements
Model based design.
HCI in the software process
Formative Evaluation cs3724: HCI.
Learning about your users (cont.): The field interview
Interface Design and Usability
Presentation transcript:

SBD: Analyzing Requirements Chris North cs3724: HCI

Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders, field studies Usability specifications Activity scenarios Interaction scenarios iterative analysis of usability claims and re-design metaphors, information technology, HCI theory, guidelines formative evaluation DESIGN ANALYZE PROTOTYPE & EVALUATE

Analyzing Requirements Goal: understand users’ current activities well enough to reason about technology-based enhancements

Analyzing Requirements 1.Root concept 2.Field studies (ethnography) Contextual inquiry (ask during) Participatory analysis (ask after) Explicit vs tacit knowledge 3.Summaries 4.Problem scenarios Story of current activity 5.Claims analysis +/- impacts

Categories People hypotheticals Activities HTA subgoals Artifacts usage Social context relationships

Summaries: stakeholder, task, and artifact analyses, general themes Root concept: vision, rationale, assumptions, stakeholders Problem scenarios: illustrate and put into context the tasks and themes discovered in the field studies Claims analysis: find and incorporate features of practice that have key implications for use Field studies: workplace observations, recordings, interviews, artifacts SBD and Requirements Analysis

Grocery Shopping

HW 1 HTA Kroger’s checkout

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2025 SlidePlayer.com. Inc. All rights reserved.