From Scenarios to Paper Prototypes Chapter 6 of About Face Defining requirements Defining the interaction framework.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

ITEC 1001 Tutorial 1 Using Common Features of Microsoft Office 2003.
User problems, scenarios and storyboards
Human Computer Interface
Copyright 1999 all rights reserved The HCI Design Process n User Interfaces are not just built by sitting down and drawing up designs for them n Just like.
1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text.
XP Exploring the Basics of Microsoft Windows XP1 Exploring the Basics of Windows XP.
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
Usability presented by the OSU Libraries’ u-team.
Paper Prototyping A tool for iterative design Wai Yong Low.
User Personas Assignment IS 485, Professor Matt Thatcher.
Use Case Analysis Chapter 6.
1 of 5 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
1 of 6 Parts of Your Notebook Below is a graphic overview of the different parts of a OneNote 2007 notebook. Microsoft ® OneNote ® 2007 notebooks are digital.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Principles and Methods
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews 2. Workshops 3. Brainstorming.
What is a prototype? A prototype is a small scale model of your larger product. Can be a physical object, or a simple software program. Many physical.
XP Using Common Features of Microsoft Office Tutorial 1.
Chapter 13: Designing the User Interface
Spring /6.831 User Interface Design and Implementation1 Lecture 8: Generating Designs.
User Interface Design Chapter 11. Objectives  Understand several fundamental user interface (UI) design principles.  Understand the process of UI design.
Operating Systems Chapter 4.
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
CS378 - Mobile Computing App Project Overview. App Project Teams of 2 or 3 students Develop an Android application of your choosing subject to instructor.
1CS480: Graphical User Interfaces. Dario Salvucci, Drexel University. Lecture 5: Scenarios.
Guidelines and Prototypes CS774 Human Computer Interaction Spring 2004.
Software engineering lec4 Requirements. Developing requirements Start thinking about particular problem Understand the problem  Domain analysis Gather.
Designing a Graphical User Interface (GUI) Krisana Chinnasarn, Ph.D. January 2007.
1 Human-Computer Interaction  Design process  Task and User Characteristics  Guidelines  Evaluation.
Overview Prototyping and construction Conceptual design
New Teachers’ Induction January 20, 2011 Office of Curriculum and Instruction.
Research on the Interaction Between Human and Machines University of Houston-Clear Lake Tasha Y. David.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Microsoft ® Office Outlook ® 2003 Training See and share multiple calendars CGI presents:
Chapter 6: NavigationCopyright © 2004 by Prentice Hall 6. Navigation Design Site-level navigation: making it easy for the user to get around the site Page-level.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
User Interface Structure Design Chapter 11. Key Definitions The user interface defines how the system will interact with external entities The system.
CS540 Software Design Lecture 5 1 Lecture 5: High Level Requirements Specification Anita S. Malik Adapted from Schach (2004) Chapter.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Cooper Interaction Design Process: Requirements Definition & Framework Overview Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Running A Paper Prototyping Session CS 321 Human-Computer Interaction.
Engineering\CADD Systems Office CADD Manager's Series Customizing the Interface.
Prototyping. REVIEW : Why a prototype? Helps with: –Screen layouts and information display –Work flow, task design –Technical issues –Difficult, controversial,
Requirements specification Why is this the first major stage of software development? –Need to understand what customer wants first Goal of requirements.
LECTURE 18 16/11/15. MAKING THE INTERFACE CONSISTENT Consistency is one way to develop and reinforce the users conceptual model of applications and give.
1 Lecture 5: Interactive Tools: Prototypers (HyperCard, Director, Visual Basic), Interface Builders Brad Myers Advanced User Interface Software.
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.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Design, prototyping and construction(Chapter 11).
Leading the Way. Coaches realize The whole is never the sum of the parts – it is greater or lesser, depending on how well the individuals work together.
Presented by the GMU Win-Win Team March 17, 2004 Status Report.
Computer/Human Interaction Fall 2015 Northeastern University1 Name of Interface Tagline if you have one Team member names and schools/years Team member.
DOCUMENTATION REF: Essentials of IT (Hamilton et al) Chapter 1.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Use Case Analysis Chapter 6.
Recall The Team Skills Analyzing the Problem (with 5 steps)
Prototyping.
Interaction Styles.
Software engineering USER INTERFACE DESIGN.
Recall The Team Skills Analyzing the Problem (with 5 steps)
Introduction to Computers
Microsoft Windows 7 Basics
User ScenarIOS.
Microsoft Windows 7 Basics
Microsoft Windows 7 Basics
Your Project Title (It is YOUR project, not the team's project, not CAM2) Your Name Date.
Presentation transcript:

From Scenarios to Paper Prototypes Chapter 6 of About Face Defining requirements Defining the interaction framework

Defining requirements Steps: Problem and Vision statements Brainstorming Identifying persona expectations  Scenarios  Identifying needs

Persona based Scenarios “a concise description of a persona using a software-based product to achieve a goal“ [Cooper, Inmates are Running the Asylum, pg. 179] Derived from information gathered during User Modeling (interviews etc)

Context Scenarios Focus on Context Scenarios Textual description Broad outlines of how someone interacts with your application Not a description of interaction details like dialogs. Focus on goals, don’t worry yet about how things will be accomplished

Questions addressed by Context Scenarios (Cooper, pg 80) What is the setting in which the product will be used? Will it be used for extended amounts of time? Is the persona frequently interrupted? Are there multiple users on a single workstation/device? What other products is it used with? How much complexity is permissible, based on persona skill and frequency of use?  What primary activities does the persona need to accomplish to meet her goals? What is the expected end result of using the product?

Identifying needs List what needs to be in the application to satisfy the context scenario Data needs: objects and information Functional needs: operations need to be performed on objects “Call (action) a person (object) directly from an appointment (context)” Similar to tasks, but also includes the objects

Defining the interaction framework Note –This diverges from Cooper’s steps. Determine Form Factor and Input methods: Tablet using pen Construct Key Path Scenarios Paper prototype Determine functional and data elements

Construct Key Path Scenarios Spell out the gritty details at the task level for the primary actions and pathways through the system E.g. For viewing and composing mail Start with a list of tasks Interaction best shown through paper prototypes (Cooper calls it storyboarding)

Paper Prototypes Prototypes using paper that represent of the user’s interaction with the application Advantages: Easy and fast to create Hand drawn nature focuses on structure of interaction rather than on visual features (icon design etc) Encourages users to suggest change

Paper Prototypes You do a paper prototype for a particular set of key path scenarios Complete high-level menu structure and interactions All the dialogs, menus, etc to complete the key path scenario(s) Include “real” data in the prototype so users have context

Functional & Data Elements Look back at the needs you identified and think about how those needs will be supported in the interface Panes, frames, other containers Individual on-screen buttons, menus, controls needs Groups of on-screen controls

Questions to consider Which elements need a large amount of real estate and which do not? Which elements are used together? In what sequence will a set of related elements be used?

Building the paper prototypes One piece of paper or card stock is the screen Put everything that might need to move on a post-it (pull down menus, buttons,..) Windows: pieces of paper, decorate windows with title bar Pull-down menus, name goes on window, contents on a post-it. Draw buttons, check boxes on windows

Paper prototype examples

Interviewing with a paper prototype Don’t do a demo. Give user a task to accomplish with prototype (e.g. grade this assignment) Critical that this user actually does the work your application is for Ask the user to talk out loud as they do things, explaining what they are doing. Be flexible – the user is never wrong, adjust the prototype to meet their expectations

Team responsibilities One person facilitates the interview, talking with the user and acting as “super help”. One person acts as the “computer” making the prototype work as it should Have another person assist the “computer” if there is lots of data to configure on the spot (write on post-its) Everyone else takes notes

Online references User Interface Engineering Five Paper prototyping tips Using Paper prototypes Online Computer Library Center Nice step by step article of how they do paper prototyping