Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity.

Slides:



Advertisements
Similar presentations
Beginning Action Research Learning Cedar Rapids Community Schools February, 2005 Dr. Susan Leddick.
Advertisements

Connecting Classrooms to Systems of School-wide PBS
Applying Grounded Theory Methods to Library and User Assessment
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.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Consolidation Reading: CD Ch.s 8, 9, & 10 Modeling & Interpretation.
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
Bullseye Bullseye was rolled out to our user base on Friday, January 30. I wanted to take this opportunity to give everyone an update on a.
Observing users Chapter 12. Observation ● Why? Get information on.. – Context, technology, interaction ● Where? – Controlled environments – In the field.
Agile Project Management with Scrum
Information System Engineering
How do I summarize and make sense of all these words?
+ Yearbook Class Introduction Rules and Syllabus Give each student their binder which includes: Syllabus Turn in signature sheet Rubric Guide.
Studio Design in HCI Spring 2004 Bill Hart-Davidson Session 8: object-oriented modeling, basic concepts; artifact and physical work models; guidelines.
WRA 453 Grant & Proposal Writing Fall 2004 Bill Hart-Davidson Session 4: Interview Questions for Grant Writer Shadowing Project.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 3: Team & Project intros; Activity Analysis; Phase 1 presentation and Memo guidelines;
Studio Design in HCI Fall 2005 Bill Hart-Davidson Session 10: class diagrams; prototype examples; review guidelines for phase 2 presentation & forecast.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.
Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor Richard.
12 C H A P T E R Systems Investigation and Analysis and Analysis.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!
Observing users. The aims Discuss the benefits & challenges of different types of observation. Describe how to observe as an on-looker, a participant,
Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” - may be of use to you in the future “blackbox”
Contextual Design. Purpose for us An example A term often used, with varying levels of precision.
Course Instructor: Aisha Azeem
Lean Training Standard Work. Agenda What is it? What’s it for? How does it work? When do you use it? What’s an example?
Texas Assessment Management System Basics 2011 TSNAP Fall Academy for New District Testing Coordinators.
Academy of management - August 15, 2011 Symposium: Learning to Coordinate: The Dynamic Interplay between Relationships and Structures Who’s actually relating?
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
Creating databases for web applications SQL. Systems design. ER diagrams. Data flow diagrams. Storyboards. Homework: Plan database and applications for.
Systems Analysis and Design in a Changing World, 6th Edition
Introduction to Sequence Diagrams
Welcome to PC360: Managing Projects. Please set cell phones and pagers to silent Refrain from side discussions. We all want to hear what you have to say!
Requirements Engineering Requirements Elicitation Process Lecture-8.
User Inspired Design 2013 Jack Whalen Yiying Wu
6 th Annual Focus Users’ Conference 6 th Annual Focus Users’ Conference Communication Tools Presented by: Lauren Velazquez Presented by: Lauren Velazquez.
Welcome to AR355: Processing Interfund Transactions.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: An Aside: The Quickest Tour through the UML that you will ever get.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design & Putting it Together Reading: ABF: Ch. 9 CD Ch.s 14, 15, 16,
Modeling Work and the Interpretation Session ITM 734 Fall 2006 Corritore.
IFS310: Module 3 1/25/2007 Fact Finding Techniques.
Systems Analysis and Design in a Changing World, 6th Edition
Conversation Analysis Introduction to Conversation Analysis 2e Anthony J. Liddicoat, March 2011.
1 © 2009 University of Wisconsin-Extension, Cooperative Extension, Program Development and Evaluation How do I summarize and make sense of all these words?
Inspiration Software, Inc. By Suzanne Sherman. Visual Learning Inspiration Software is based on the premise that visual learning helps students to improve.
2.4 Key Management Roles KEY CONCEPT
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10.
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
Strength-Based Feedback and Goal-Setting Sessions.
Advanced Technical Writing 2006 Session #13. Today In Class ► The third analytic perspective: workflows & production models ► Thinking about “metadata”
Copyright © 2013 Curt Hill Creating the To-Be Architecture Using the crystal ball.
AR350: Maintaining Customers Welcome to AR350: Maintaining Customers.
Understanding User's Work Ethnography The systematic study and documentation of human activity without imposing a prior interpretation on it via immersion.
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
Portfolios for TAs. PI34 “Students must complete a portfolio of evidence for the teaching standards” to be certified Review.
Use Case Model Use case description.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Start the slide show by clicking on the "Slide Show" option in the below menu or – hit the F5 Key.
VTPBiS Coordinators as Coaches Learning and Networking Meeting 1 May, 2016.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
Observing lessons MONDAY 21 ST SEPTEMBER AM. Menu TimeasActivity 9:30Starter 9:45Classroom observation – why and how 10:45Break 11:15Task 2: Different.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
Introduction to Web Authoring Bill Hart-Davidson AIM: billhd30 Session 21
Investigating System Requirements
Architecture Concept Documents
Week 10: Object Modeling (1)Use Case Model
CS 321 Human-Computer Interaction
Nanotechnology & Society
Presentation transcript:

Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity diagrams; Preview: object-oriented modeling

Today in Class Be ready to share… –Your Research Plan –Your Sequence diagram We’ll talk about affinity diagrams as a way to analyze data from your CD interviews We’ll talk about consolidated sequence diagrams Key OO modeling concepts

Tell us about your Research Plan The research focus - what does your team need to know? The interviews/observations you will do broken down by roles The approach you will take in each of these How you will deal with the challenges your project poses

Affinity Diagrams & Consolidated Work Models Affinity diagrams and consolidated work models are tools for making inductive reasoning from multiple data sources systematic by: 1.Creating concrete representations of work practices 2.Granting “ownership” of the representation and subsequent designs to the whole team 3.Emphasizing patterns vs. anecdotes

What is an Affinity Diagram? Simply put, it is a issue- categorized, prioritized list of the insights that come from interpretation sessions. n

Affinity Diagram: Structure sum. points sum. points sum. points sum. groups point Built from the bottom up, categories emerge from the specifics of your observations. NOT a “sorting” task.

Example… weekly reports focus on production goals and customer quality metrics all users routinely print And file customer s customer contact records are important, but informal

Innovating w/ the Affinity As patterns emerge, the team’s job is to link these with design goals…bringing your expertise IT systems to bear on the data sum1 Customer-relationship management point sum2 point

The Affinity tells users’ stories We do it routinely… Customer-relationship management is vital to our business file Call back sheets But inconsistently…

The Affinity gives you a way to check design direction w/ users “We have noticed that maintaining relationships with customers is important to you. You spend a great deal of time during the day doing this sort of work: creating or updating records, responding to , logging and returning calls. You also evaluate your staff using metrics that relate to this work, and yet much of it is done ad- hoc and informally…what we would like to do for you is…

Consolidated Work Models Like Affinity Diagrams, consolidated work models tell stories of how work happens in ways that 1.Allow the whole team to see and understand work practices 2.Highlight design issues and opportunities

Consolidating = move from individual  organizational patterns Flow models: move from understanding individual workers’ practice to patterns of work by “role” Sequence models: move from understanding instances of work to the structure of the work, including reasons for differences observed

Consolidated sequence diagrams: UML/swimlane studentteacher Assign paper peer Draft paper Draft paper Exchange & Review papers Check reviews Note all user roles involved in a task are represented ; artifacts are in blue; trigger in red Cont.

Sequence consolidation: grading Instructor skims whole report quickly, no more than 2-3 seconds per page Instructor returns to P1, begins reading Instructor flips through document, lingers on heading on p. 3 Returns to p.1, reads abstract Flips through all pages again quickly Returns to P1, begins reading

Nominating the action: “triage” Instructor skims whole report quickly, no more than 2-3 seconds per page Instructor returns to P1, begins reading The fact that the instructor encountered no serious problems in this instance made the purpose of this action hard to detect

Consolidation reminders When you give a generic name to a role, an action, an influencer (in the cultural model), a tool (in the artifact or physical model), or a space (in the physical model)…verify it with users! These generic names will be very important in our next phase of the design, OO modeling, as they will frequently become the shorthand for system features including user environments (metaphors, screens), data objects & states, actions, and of course, user roles.

OO modeling Object-oriented modeling provides a way to coordinate the design work with development work by using similar terms to express the priorities of each group. We speak, in OO modeling, in terms of User Roles that do specific Actions through the use of Objects.

Views A view is the way a given object appears to a user. Views can focus the attention on a single object, or provide a way to see, understand, and interact with many objects at once.

2 Views of the Buddy Object in AIM Buddy name, status in “buddy list” Buddy details in “buddy info”

Object/View Instances Objects spawn “instances” of themselves that users interact with. This allows the same basic object to carry context-specific details. Views also have instances, which tend to be “sessions,” reflecting the time, place, and task conditions.

Object States Most objects a user interacts with have a lifecycle, a series of “states” it can go through. At any given time, an object is occupying some state and may be poised to move to another (usually as the result of something the user does).

Next time… Artifact and Physical Models –Exercise 2, build a consolidated Artifact or physical model Representing design concepts w/ OO modeling techniques Guidelines for Phase 2 presentations