39
User Interaction Design User Interaction Design Representing User Representing User Interactions Interactions

User Interaction Design Representing User Interactions

Embed Size (px)

Citation preview

Page 1: User Interaction Design Representing User Interactions

User Interaction DesignUser Interaction DesignUser Interaction DesignUser Interaction DesignRepresenting User Representing User

InteractionsInteractions

Page 2: User Interaction Design Representing User Interactions

Design & Representation

• Design– Creative, mental, problem-solving process

• Representation– Physical process of capturing or recording

a design

Page 3: User Interaction Design Representing User Interactions

Design Representations

• Means by which interaction designs are communicated and documented.

• Design representations are communicated between:– Designer and developer (maybe others)– Not the User (in most cases)

Page 4: User Interaction Design Representing User Interactions

Design Representations

• Constructional Representations– Interactions described from the

system’s view point.• State Transition diagrams• Event-based mechanisms• Object Oriented mechanisms

Page 5: User Interaction Design Representing User Interactions

Design Representations

• Behavioral Representations– User Centered and Task/Goal Oriented.

– Task Analysis, user modeling, function analysis are all behavioral activities

– Example Methods• Command Language Grammar• Keystroke Level Model• Task Action Grammar• GOMS (Goals, Operators, Methods &

Selection)• User Action Notation (UAN)

Page 6: User Interaction Design Representing User Interactions

User Interaction Design

• Each Behavioral design must be translated into a Constructional Design– Result is the User Interaction Design

• User Interaction Design is created by the designer and given to the developer.

Page 7: User Interaction Design Representing User Interactions

User Action Notation

• User and Task Oriented Notation that describes physical behavior of the user and interface as task are being performed.

Page 8: User Interaction Design Representing User Interactions

User Action Notation

• Interfaces are represented as quasi-hierarchical structures of asynchronous tasks.

• User actions cause state changes in the interface.

Page 9: User Interaction Design Representing User Interactions

User Action Notation

• UAN consists of – Task Descriptions– Scenarios– Discussion Notes– State Transition Diagrams

• Uses special Notation to describe tasks

Page 10: User Interaction Design Representing User Interactions

UAN: Selecting A File

1. Move the cursor to the file icon.

2. Press and immediately release the left mouse button.

Page 11: User Interaction Design Representing User Interactions

UAN: Selecting A File

1. ~[file icon]

2. Mv^

Page 12: User Interaction Design Representing User Interactions

User Action Notation

Advantage of UAN

1. Takes less space on paper.2. If you know, it saves time.

Page 13: User Interaction Design Representing User Interactions

User Action Notation

Problems with UAN

1. New language for the developer.2. Cryptic notation.3. If you don’t know it, it takes more

time.4. No standard notation.

Page 14: User Interaction Design Representing User Interactions

User Action Notation Modified

• UAN consists of – Task Descriptions– Scenarios– Discussion Notes– State Transition Diagrams

• Eliminate special Notation

Page 15: User Interaction Design Representing User Interactions

Task Descriptions

• Identify all of the tasks the system or product must support.

• Occurs in Feasibility and Analysis Stage of Software Development.

Page 16: User Interaction Design Representing User Interactions

Scenarios

• Create User Scenarios that support each task from the Task Descriptions.

• Occurs in Analysis and Design Stage of Software Development.

Page 17: User Interaction Design Representing User Interactions

Discussion Notes

• Any special observations, requirements or hypothesis that designer has are noted.

• Occurs in everywhere in Software Development.

Page 18: User Interaction Design Representing User Interactions

State Transition Diagrams

• Finite State Machines– Graph of the system that identifies user

interactions.

• Occurs in Design before Development.

• Includes graphs and screen images.

Page 19: User Interaction Design Representing User Interactions

State Transition Diagrams

• Graphs with Nodes and Edges.

• Nodes– Represent interface states.– Image of interface should be included.

• Edges– Appear between nodes.– Represent changes in interface state.

Page 20: User Interaction Design Representing User Interactions

State Transition Diagrams

• Each interface has a State Transition Diagram.

• The system is a collection of interfaces, therefore, it is also a collection of State Transition Diagrams

• Can become very complex very quick.

Page 21: User Interaction Design Representing User Interactions

State Transition Diagrams

• Each interface has a State Transition Diagram.

• The system is a collection of interfaces, therefore, it is also a collection of State Transition Diagrams

• Can become very complex very quick.

Page 22: User Interaction Design Representing User Interactions

User Interaction DesignUser Interaction DesignUser Interaction DesignUser Interaction DesignExample Example

Login InterfaceLogin Interface

Page 23: User Interaction Design Representing User Interactions

User Login Interface

Page 24: User Interaction Design Representing User Interactions
Page 25: User Interaction Design Representing User Interactions

Start

Password

LoginPassword

Login

End

Submit

Top path

Bottom path

Page 26: User Interaction Design Representing User Interactions

Top Path

Start

PasswordLogin

End

Submit

Page 27: User Interaction Design Representing User Interactions

User enters login name.

Page 28: User Interaction Design Representing User Interactions

User enters password.

Page 29: User Interaction Design Representing User Interactions

User presses submit.

Page 30: User Interaction Design Representing User Interactions

Bottom Path

Start

LoginPassword

End

Submit

Page 31: User Interaction Design Representing User Interactions

User enters password.

Page 32: User Interaction Design Representing User Interactions

User enters login name.

Page 33: User Interaction Design Representing User Interactions

User presses submit.

Page 34: User Interaction Design Representing User Interactions

Start

Password

LoginPassword

Login

End

Submit

Top path

Bottom path

Page 35: User Interaction Design Representing User Interactions

Review of Review of Computational TheoryComputational Theory

Relationship toRelationship toWeb DesignWeb Design

Review of Review of Computational TheoryComputational Theory

Relationship toRelationship toWeb DesignWeb Design

Page 36: User Interaction Design Representing User Interactions

Automatic Door/FA

Frontpad

Rearpad

closed open

Front

Neither

Front,Rear,Both

Rear,Both,Neither

Chuck Allison, UVSC, http://uvsc.freshsources.com/html/cns_3240.html

Page 37: User Interaction Design Representing User Interactions

Successful Path

A successful path through a transition graph is a series of edges forming a path beginning at some start state (there may be several) and ending at a final state.

1- 2 3 4+abb a

aa

b

Free Rideabbab…

abbaa…

abbababba

A Lambda transition occurs when you get a free transition that was not initiated by user or system action/interaction. Move on a whim (w/o consuming input).

Chuck Allison modified by Seals

Page 38: User Interaction Design Representing User Interactions

Example(p. 84)

a,b

ab

bbbb

bbbb

bbb

a

a a a

a

b

b

- +

Cohen Ch6-Chuck Allison, http://uvsc.freshsources.com/html/cns_3240.html

Page 39: User Interaction Design Representing User Interactions

User Interaction Design

1. Task Descriptions

2. Scenarios

3. Discussion Notes

4. State Transition Diagrams