4. Tasks and Happypaths

Question 1

Happy path

Answer 1

Shows each screen/window/page that the user gets for solving ONE task. You describe what the user does and how the system reacts. You put arrows between screens and mark the spaces where the user does something. Show only the flow when everything goes well

Question 2

How many happy paths per task?

Answer 2

One

Question 3

Dropdown

Answer 3

1. One of many 2. Options hidden 3. Usually a large selection

Question 4

Check box

Answer 4

1. One or more of many 2. Options visible 3. Usually a small selection

Question 5

Radio button

Answer 5

1. Not a button 2. One of many 3. Options visible 4. Usually a small selection

Question 6

Sliders

Answer 6

Sometimes selections are granular

Question 7

Toggle

Answer 7

1. On/off 2. Sometimes a single check box

Question 8

Buttons

Answer 8

1. Call to action 2. OK/Cancel was the paradigm for a long time 3. Descriptive calls to action

Question 9

What are the 5 design principles?

Answer 9

1. Visibility 2. Feedback 3. Constraints 4. Consistency 5. Affordance

Question 10

Visibility

Answer 10

A control should be visible so users know it is available. A user should be able to initiate an action and see what they can do. WYSIWYG

Question 11

Feedback

Answer 11

Sending information back to the user about what has been done and what has been accomplished. Feedback includes; audio, tactile, verbal, visual and combination of these. There should be feedback for every action

Question 12

Constraints

Answer 12

Restricting the possible actions that can be performed. Helps prevent user from selecting incorrect options. Example; graying out fields

Question 13

Consistency

Answer 13

Designing interfaces to have similar operations and use similar elements for similar tasks. Consistent interfaces are easier to learn and use. Example; Consistent colour, layout, fonts,… Internal consistency refers to designing operations to behave the same within an application and external consistency to designing operations, interfaces, etc, to be the same across applications and devices

Question 14

Affordance

Answer 14

Refers to an attribute of an object that allows people to know how to use it. Example; a mouse button invites pushing, scrollbars invite moving up and down

Question 15

What is alternative flow?

Answer 15

When the user does not do as planned during a happy path