Building Models Part 1: Models good for defining system and user requirements –Affinity diagrams –Flow model –Cultural model –Sequence model –Physical.

Slides:



Advertisements
Similar presentations
what is it and why do we use it?
Advertisements

Chapter 9 User-centered approaches to interaction design By: Sarah Obenhaus Ray Evans Nate Lynch.
Methods: Deciding What to Design In-Young Ko iko.AT. icu.ac.kr Information and Communications University (ICU) iko.AT. icu.ac.kr Fall 2005 ICE0575 Lecture.
Listening Strategies for ELA Regents By: Mr. Newton Explanation: The following animated* flow chart is used to teach the students the appropriate steps.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Consolidation Reading: CD Ch.s 8, 9, & 10 Modeling & Interpretation.
CAEL Prior Learning Assessment Process Mapping – Session 2 Facilitator – Eric Heller
April 14, 2009 Jim Butler Julia Heany.  A process is a series of steps or actions performed to achieve a specific purpose.  A process can describe the.
1 Lecture 3: Contextual Design Methodology Brad Myers / / : Introduction to Human Computer Interaction for Technology Executives Fall,
Interaktionsdesign Session 4 Analysemetoder. Work Models Describe work from the point of view of the one person interviewed The Flow model The Sequence.
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2002] February 8, 2007.
Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,
Understanding and Representing Users A.J. Brush cse490ra January 22, 2003.
Copyright W. Howden1 Lecture 2: Elaboration Tasks and Domain Modeling.
Contextual Design. Purpose for us An example A term often used, with varying levels of precision.
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2005] February 5, 2009.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
1 Contextual Interview Shahnewaz A. Jolly CPSC 681: Research Methods in Human Computer Interaction Instructor: Dr. Saul Greenberg Date: November 4, 2009.
Design process. Design briefs Investigating Designing Producing Analysing and evaluating Design process wall charts.
Z556 Systems Analysis & Design Session 7 ILS Z556 1.
Mar 28 ~ Announcements~ Engineering professor, Dr. Jay Pembridge, looking for transcription and coding for a research project on teaching expertise. $10/hr,
Designing User Experience (UX) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.Creative Commons.
The Design Discipline.
CENTER FOR NONPROFIT EXCELLENCE EVALUATION WORKSHOP SERIES Session IV: Analyzing and Reporting Your Data Presenters: Patty Emord.
Client Logo LEAN ENTERPRISE Implementation Workshop.
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY User Studies Basic principles, methods, and examples Sari.
Requirements 101 CS3300 Fall 2015.
Z556 Systems Analysis & Design Session 5 ILS Z556 1.
High-Level Design With Sequence Diagrams COMP314 (based on original slides by Mark Hall)
Affinity Diagrams ITM 734 Fall 2006 Corritore. 2 Affinity diagrams Brings issues and insights about customers/users together  Fastest and best way Affinity.
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
Create a Work Breakdown Structure (WBS) n Develop the project goal yourself n Take a cursory pass at defining the objectives –the preliminary plan n Have.
Subject to Consultation Insert Slide Title Here Insert Name and Date Here.
S556 SYSTEMS ANALYSIS & DESIGN Week 9. Team Process Presentation on April 4 SLSI S556 2  15 minutes  Present your teamwork process, not the findings.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Modeling Work and the Interpretation Session ITM 734 Fall 2006 Corritore.
Drawing System Sequence Diagrams
Requirements Elicitation. Structured Interview: Purpose is to ask and answer questions concerning the problem being modeled Observation: Observe activities.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
S556 Systems Analysis & Design Week 10: November 11, 2008.
Task Analysis Overview, utility Types of task analysis Sources and use.
S556 SYSTEMS ANALYSIS & DESIGN Week 6. Using Language to Focus Thought (cf., Wood, 1997) SLIS S556 2  The language gives you a way to see:  a framework.
CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10.
This material has been developed by Georgia Tech HCI faculty, and continues to evolve. Contributors include Gregory Abowd, Jim Foley, Diane Gromala, Elizabeth.
Big Six Information–Seeking Problem–Solving Process.
1 ISE Human Factors in the System Life Cycle The human factors engineering process  Research  Model  Define requirements  Design  Evaluation.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Design from Data Reading: CD Ch. 11, 12,
Fashion MARKETING TID1131. Types of research Quantitative research Information relating to numbers – quantity. Method - surveys Qualitative research To.
In the news. Taxonomy Organizing Information Observation The Organization Project Scope Start the project Stakeholder Interviews Gather goals Focus groups.
Communication Diagrams Lecture 8. Introduction  Interaction Diagrams are used to model system dynamics  How do objects change state?  How do objects.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design: Reading: CD Ch.s 14, 15, &16 Monday Midterm CS 321 Human-Computer.
Requirements Elicitation Hans Van Vliet, Software Engineering: Principles and Practices, 3rd edition, Wiley (Chapter 3) 1.
Trends & Concepts in the Software Industry II Synthesis.
Designing User Experience (UX) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.Creative Commons.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
Observation Direct observation in the field –Structuring frameworks –Degree of participation (insider or outsider) –Ethnography Direct observation in controlled.
WHAT IS A Context Diagram?
Welcome to M301 P2 Software Systems & their Development
Z556 Systems Analysis & Design
Unified Modeling Language
Designing User Experience (UX)
CHAPTER 4 PROPOSAL.
CHAPTER 4 PROPOSAL.
Topics Technologies for Meaning Making Create a Mind Map
User Studies Basic principles, methods, and examples
Object-Oriented Software Engineering
A Fundamental Challenge
Presentation transcript:

Building Models Part 1: Models good for defining system and user requirements –Affinity diagrams –Flow model –Cultural model –Sequence model –Physical model –Artifact model –Source: H. Beyer and K. Holtzblatt (1999), Contextual Design : A Customer-Centered Approach to Systems Designs. San Francisco, CA: Morgan Kaufmann. Note: for more details on the following example, you should visit the InContext website at and follow the CDTools link to “Resources” and then “Shopping Data Browser” (on the right under “Example Data.”)

Affinity Diagram Use the Post-It notes to record insights and quotes from your observations and interviews. –One phrase or quote per note. –Write big enough for all to see. Post the notes on the wall. “Walk the wall” and rearrange the notes into like categories. When everyone is agreed on the categories, give each category a meaningful name and summarize the findings. Use the affinity diagram to generate design ideas, identify requirements, and inform other models.

Affinity Diagram

Flow Model Draw the primary user of the system in the center of the page. Use Post-It notes to add other users, people, “roles,” and physical objects as needed to define flows of work and information. Use annotated lines and arrows to indicate flows of information or work. Indicate opportunities for “breakdowns” in communications or work flow. Use the model to add to or refine requirements, define key interactions, and identify communication modes and methods.

Flow Model

Flow Model Detail

Cultural Model Draw a circle representing the primary user in center. Draw overlapping and concentric circles representing other entities that affect the primary user. Draw arrows indicating influences, constraints, and expectations. Identify individual and pervasive values that affect how the user will approach the task. Use the model to define subtleties that should affect system design.

Cultural Model

Sequence Model Define specific steps the user goes through to accomplish the task. Identify strategies and decision points. Identify breakdowns that make the task difficult to complete. Where appropriate, identify options and alternative strategies. Use the model to further define requirements, identify design opportunities, and begin to define potential interaction methods.

Sequence Model

Physical Model Diagram in detail the physical space in which the task is performed. Identify both “official” and “unofficial” designation of locations. Identify paths taken through the space during task performance. Define how users use the space to accomplish the task. Identify breakdowns where the physical space inhibits task performance. Use the model to develop system design requirements and opportunities.

Physical Model

Artifact Model Draw or diagram the artifacts used to accomplish the task. Specify the user’s intent in using the artifact. If necessary, identify variants of the artifacts. Identify potential breakdowns where the artifact inhibits task performance. Use the model to define user requirements and identify potential design directions.

Artifact Model

Building Models Part 2: Models good for defining interaction –HTA –GOMS –OFM

Example: HTA of ____________

Example: OFM of _____________