Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.

Slides:



Advertisements
Similar presentations
Latika Nirula & Earl Woodruff OISE/University of Toronto
Advertisements

Chapter 11 Designing the User Interface
Mobile learning with a mobile game Design and motivational effects.
Thoughts on Systematic Exploratory Testing of Important Products James Bach, Satisfice, Inc.
How to Enhance Personal Productivity By Janet Hadley
Experiential Learning Cycle
1/10 POSDATA Team EVR:MAKING USE Hou, Kyu Cho, Eun Young Jeung, Min Ho Jung,Hee Joon.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
HOW DO PROFESSIONAL DEVELOPERS COMPREHEND TO SOFTWARE Report submitted by Tobias Roehm, Rebecca Tiarks, Rainer Koschke, Walid Maalej.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
From requirements to design
Design Activities in Usability Engineering laura leventhal and julie barnes.
OF INFORMATION AND KNOWLEDGE MITE INTERACTIVE REPRESENTATIONS 6323.
Day 9 Navigation Heuristic evaluation. Objectives  Look at some simple rules on navigation  Introduction to Heuristic Evaluation.
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Chapter 13: Designing the User Interface
User Centered Design Lecture # 5 Gabriel Spitz.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
Lean Supply Chain Action Learning Program September 2007.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
Human Interface Engineering1 Main Title, 60 pt., U/L case LS=.8 lines Introduction to Human Interface Engineering NTU Seminar Amy Ma HIE Global Director.
Chapter 2: Understanding and conceptualizing interaction Question 1.
Chapter 4 Requirements Engineering
SBD: Activity Design Chris North CS 3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
Evaluation of digital collections' user interfaces Radovan Vrana Faculty of Humanities and Social Sciences Zagreb, Croatia
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
 Knowledge Acquisition  Machine Learning. The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
User Documentation Stored information about how to use a system –Reference manuals, tutorials, online help –Many systems show up with a diverse set of.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
111 Notion of a Project Notes from OOSE Slides – a different textbook used in the past Read/review carefully and understand.
What is Usability? Usability Is a measure of how easy it is to use something: –How easy will the use of the software be for a typical user to understand,
MULTIMEDIA DEFINITION OF MULTIMEDIA
Heuristic evaluation Functionality: Visual Design: Efficiency:
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Artificial intelligence systems form a broad and diverse set of.
Chapter 2.2 Game Design. CS Overview This introduction covers: –Terms –Concepts –Approach All from a workaday viewpoint.
Jacobsen, D. M. EDER Computer Based Learning II Jan 17 – 2 nd Seminar Web Portfolio Course Project Discussion / Collaboration / Lab 40% 60%
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Writing Software Documentation A Task-Oriented Approach Thomas T. Barker Chapter 5: Analyzing Your Users Summary Cornelius Farrell Emily Werschay February.
Requirements Analysis Goal: understand users’ current activities well enough to reason about technology- based enhancements.
Teaching Reading Comprehension
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Requirements Analysis Goal: understand users’ current activities well enough to reason about technology- based enhancements.
Human Computer Interaction
Project Sharing  Team discussions (15 minutes) –Share results of your work on the Project Scope Proposal –Discuss your choice of methods and results –Prepare.
Facilitate Group Learning
Developing a Framework In Support of a Community of Practice in ABI Jason Newberry, Research Director Tanya Darisi, Senior Researcher
SBD: Activity Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
Amplifying access and inclusion through audience participation Jessica Bradford, Interpretation Manager Science Museum.
Pertemuan 16 Materi : Buku Wajib & Sumber Materi :
Writing to Teach - Tutorials Chapter 2. Writing to Teach - Tutorials The purpose of a tutorial is to accommodate information to the needs of the user.
Professional Ethics and Responsibilities
SBD: Analyzing Requirements Chris North cs3724: HCI.
Information Design Goal: identify methods for representing and arranging the objects and actions possible in a system in a way that facilitates perception.
1 Usability Analysis n Why Analyze n Types of Usability Analysis n Human Subjects Research n Project 3: Heuristic Evaluation.
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
Mind Mapping Software: Uses and Benefits for Education.
User Documentation Stored information about how to use a system
Impact-Oriented Project Planning
Design Thinking.
Grade 6 Outdoor School Program Curriculum Map
ROLE OF «electronic virtual enhanced research-engaged student teams» WEB PORTAL IN SOLUTION OF PROBLEM OF COLLABORATION INTERNATIONAL TEAMS INSIDE ONE.
Beyond User Participation: A Model of Learning and Negotiation During Systems Development The Workshop on "Redefining the Organizational Roles of Information.
Presentation transcript:

Activity Design Goal: work from problems and opportunities of problem domain to envision new activities

An HCIC Example Goal: design a universal remote control Measure use of remote controls and functionalities Mathematically determine which remote and which function might be next Automatically perform it with a touch of a button

From Requirements to Design Requirements analysis sets the scene Design transforms people’s activities –New technology, new tasks, new experiences –And the cycle continues...

SYSTEM FUNCTIONALITY USER INTERFACE The Two Faces of HCI Design

product data browsing searching ordering payment customer data SYSTEM FUNCTIONALITY USER INTERFACE icons links menus layout navigation labels fields security feedback The Two Faces of HCI Design

Activity Design Emphasizes broad scope of what is being designed Establishes and maintains usage context Also referred to as conceptual design or task-level design

Why System Functionality First? Designers can focus on what a system will do Postpone the “how” question until later Hard to analyze UI needs without knowing what a system will do UI difficulties can destroy a system’s usability

Envisioning New Activities Three activity design concerns to keep in mind: Effectiveness: Designing tasks that meet real needs Comprehension: Designing concepts and services that your users can predict, understand Satisfaction: Designing tasks that are motivating and lead to feelings of accomplishment, satisfaction

Designing for Effectiveness Innovation is good, but how much is too much? –Build on what is already working well –Engage stakeholders in cooperative design What parts of a task to support via technology? –Leverage other aspects of the work context, both people and things (distributed cognition) Balance tendency toward general solutions with the needs of specific tasks –Predict and support exceptions, provide special cases for common or critical tasks

Designing for Comprehension Cannot directly observe comprehension –Must rely on users’ behaviors, reactions, comments –Make inferences about their mental models Metaphors play a crucial role in this –Designers explore metaphors to get new ideas –Users evoke metaphors to understand new concepts Try to leverage users’ existing knowledge –Anticipate and support analogical reasoning –But look for ways to “break” current understandings

Designer’s Model User’s Mental Model Cashier Systematic, logical, comprehensive Ad hoc, informal, incomplete The Web Cart

Designing for Satisfaction Automate tedious tasks, but try not to remove sources of reward or accomplishment –Carefully examine sources of reward, maintain or enhance opportunities for feelings of achievement –Use the computer to make tasks more personal, more stimulating, more “fun” Balance the needs of individuals with those of the groups they work with –The people who do the most “work” when using a system may not be those who get the most “benefit”

Problem scenarios: work from current practice to build new Activity design scenarios: transform current activities to use new design ideas Claims analysis: identify, illustrate, and document design features with key implications Activity design space: brainstorm implications of metaphors and technology Problem claims: look for design ideas that address negatives, but keep positives HCI knowledge about activity design SBD and Activity Design

Exploring Metaphors and Technology Metaphors for online shopping... Technology for online shopping...

Apply a Computational Metaphor Taking a software object’s point of view –Use anthropomorphism to extend the task Envision “scenario within a scenario” –Ask: what would I do, if I were a shopping list trying to be helpful to this shopper? May discover new services, other objects –But need to reflect on implications of each idea –Claims analysis helps you do this

Working With Claims in Design Maintain or enhance as many positive impacts (upsides) as you can While removing or minimizing negative impacts (downsides) whenever possible As new ideas/scenarios are envisioned, consider also the new claims that they raise

From the Science Fair Case Study Giving all students the same physical display board... + constrains and simplifies project lay-out + limits visual complexity for viewers - but exhibits may have widely varying needs - but regularity and simplicity may be boring to view How to maintain or enhance the benefits for planning and viewing but address the project- specific needs, or issues of variety and creativity in display?

New Activities Lead to New Claims We envisioned an exhibit template that would help in planning, but made it editable so that motivated (e.g. experienced) students could be as creative as desired Providing an exhibit template that is editable... + offers default planning and lay-out of exhibit parts + leverages students’ familiarity with science projects + enables expert participants to be creative - but students may trust the template too much - but inexperienced students may become confused

Photo taken from a garden shop problem scenario: shopper wanders by, sees the pots, is reminded of needs

From a Garden Shop Scenario... A wall of shelves for displaying products... + simplifies comparison of physical features + provides implicit availability/popularity indications + directs shoppers to related products - but some shelves will be difficult to reach - but browsing is constrained by physical layout How to maintain or enhance product comparisons and other analysis tasks, while addressing awkwardness and physical constraints?

Refining an Activity Design Ongoing claims analysis of activity scenarios –Capture key ideas, begin to build design rationale –Document problems to address during UI design Participatory design –Brainstorming sessions with stakeholders –Share rough ideas, get them to elaborate (metaphors can be very useful here as well) Consistency and coherence –Reuse actors and objects to increase coherence –Complement with ongoing “what if?” reasoning to expand and test the overall design

Friday Activity: Participatory Design Consider the role that your client seems to be taking in your project How can you maintain control over your project How can you encourage your client to participate in helpful ways