0% found this document useful (0 votes)
63 views24 pages

7.text Entry Devices - Positioning - Pointing and Drawing - Display Devices - Devices For Virtual Realit

This document discusses various interaction design techniques used in the discovery phase of design including storyboarding, use case modeling, and stakeholder profiles. It describes storyboarding as using pictures to describe workflows. Use case modeling represents interactions between users and a system using actors and use cases. Stakeholder profiles define the target user through context of use, cognitive and physical abilities. The discovery phase documentation includes a mission statement, requirements document, and project management document.

Uploaded by

Aban Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
63 views24 pages

7.text Entry Devices - Positioning - Pointing and Drawing - Display Devices - Devices For Virtual Realit

This document discusses various interaction design techniques used in the discovery phase of design including storyboarding, use case modeling, and stakeholder profiles. It describes storyboarding as using pictures to describe workflows. Use case modeling represents interactions between users and a system using actors and use cases. Stakeholder profiles define the target user through context of use, cognitive and physical abilities. The discovery phase documentation includes a mission statement, requirements document, and project management document.

Uploaded by

Aban Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

Interaction Design

DISCOVERY
Interpretation - Storyboarding
2

 Storyboarding involves using a series of pictures that


describes a particular process or work flow
 Can be used to study existing workflows or generate
requirements
 Can facilitate the process of task decomposition
 Used to brainstorm alternative ways of completing tasks
3
Interpretation – Use Cases
4

 Use case modeling represents a structured approach


for describing workflows and processes
 Use cases depict the interaction between the users and the
system
 Jacobson et al (1992)
 Incorporated into the Unified Modeling Language
(UML) standard
Interpretation – Use Cases
5

 The two main components of use case modeling are


the actors and the use cases
 An actor:
 Is always external to the system

 Interacts directly with the system

 Represents a role played by people or things, not specific people or


specific things
Interpretation – Use Cases
6

 According to Rumbaugh, a use case is “a specification of


sequences of actions, including variant sequences and error
sequences, that a system, subsystem, or class can perform
by interacting with outside actors”
 Use cases:
 Are always started by an actor
 Are always written from an actor’s point of view
Interpretation – Use Cases
7
Interpretation – Use Cases
8

 The use case diagram


shows the system
boundary, the use
cases internal to the
system, and the actors
external to the system,
e.g. [Fig.4.6, Arlow &
Neustadt 2005]
Interpretation – Use Cases
9
Interpretation – Use Cases
10
Interpretation – Use Cases
11

 There are diverse flows (paths) through a use case


 Main flow: The main path through the use case is the one that
is completed without any diversions from error conditions or
other accidental circumstances

 Alternative flows: Alternative paths describe the exception-


handling capabilities of the system. They capture, for example:
 Premature termination of a process
 Possible error conditions
 Unusual exercising of a use case
Interpretation – Use Cases
12

 Scenarios: Each unique path through the use case is


called a scenario
Interpretation - Primary Stakeholder Profiles
13

 Primary Stakeholder Profiles are used to define the


target user

 The constructs covered include:


 Context of use

 Cognitive ability

 Physical ability

 Individual profile
Interpretation - Primary Stakeholder Profiles
14
Interpretation - Primary Stakeholder Profiles
15

 Context of use for a common office desktop system


Interpretation - Primary Stakeholder Profiles
16

 The cognitive abilities of the target users affect the


design

 The cognitive abilities of the target users may be


specific (e.g., an educational game for a specific
grade level) or more general (e.g., a web site for a
broader audience)
Interpretation - Primary Stakeholder Profiles
17

Domain expertise may not correlate with computer literacy


Interpretation - Primary Stakeholder Profiles
18

 The human condition includes wide ranges of physical


abilities
 Visual
 Auditory
 Haptic
Interpretation - Primary Stakeholder Profiles
19

 There are situations when personal user information is


required
Documentation
20

 Documentation as outcome of the Discovery phase


consists of
 Mission statement (project concept)
 Requirements document
 Project management document
Documentation
21

 Mission Statement
 Project goals
 What needs will the new system address?
 How will it address these needs?
 What is the utility of the proposed system?
 Project scope
 What does the proposed design include or exclude?
 What are the external constraints such as time and finances?
 How will you decide when it satisfies the design proposal?
Documentation
22

 Requirements Document
 Detailed requirements, on several levels of priorities
(recommended, 3 levels)
 Functional
 Non-functional

 Inputs/outputs
Documentation
23

 Project Management Document


 Definition of the tasks involved in the project

 People assigned to tasks

 Risk assessment

 Evaluation criteria and methods

 Implementation timeline

 Training

 Maintenance

 Future needs
Video Selection
24

 HCI videos
[Sketch furniture by Front] [High-speed robot hand]
[MIT’s Nexi robot] [Honda Asimo] [Corning - glass]
[Augmented reality by Hitlab] - Nitish
[MS surface patient consultation] - Andrew
[Augmented maps] - Rakib
[Microsoft Kinect] - Warren and Parth
[BumpTop] - Nitish

You might also like