Crafting the Compelling User Experience

Transkript

1 Crafting the Compelling User Experience Design I : Abstract Design Crafting the Compelling User Experience: Abstract Design Phase Slide number 1

2 2YHUYLHZ RI 8&' 3KDVHV Slide number 2

3 'HVLJQ $EVWUDFW 'HVLJQ 3URFHVV Slide number 3

4 )URP 'LVFRYHU\ 3KDVH User class diagram Users current task models Users goals User experience use cases Slide number 4

5 8VHUV 2EMHFW 0RGHO ƒ Purpose of modelling users objects: To ensure that the fundamental objects of the system are objects that users perceive and expect to deal with to complete a task rather than system objects, objects from a programming model. ƒ Definition of user objects: Those concepts or things (concrete or abstract) that users perceive and interact with in order to accomplish their tasks. ƒ Special note on user s mental model vs users object model: A user s mental model belongs to an individual whereas the users object model is the object model that our system will portray to the user (there should be a strong correlation so that various individual mental models can map to the system s users object model) ƒ UCD activities: ƒ Review diagrams from Discovery phase, in particular utilize the task models to find the nouns that appear in the task flow Slide number 5

6 +RZGR,FUHDWHWKH XVHUV REMHFW PRGHO" ƒ 1. Identify the objects - review nouns that are found in the task models ƒ 2. Sort the objects utilizing a simple table (optional can do directly into modelling if desired) ƒ 3. Define each object with 1 clause (no jargon) in ways users would understand them ƒ 4. Put objects in model (including definitions, attributes and operations) and define relationships between objects Concrete People Forms Users Abstract Real things you can touch or walk away with Hotel Room Credit card Key Those who are managed by the system or have things saved for them Guest Existing paperwork or other system Reservation Folio Those who operate the system or directly interact with the system Guest Reservation clerk Front Desk clerk Night auditor Anything else Authorization Stay Dates Slide number 6

7 +RZGR,FUHDWHWKH XVHUV REMHFW PRGHO" Object Attributes Operations Relationship (composed of) Definition: The part of the building where the guest stays. Quick overview: ƒ 1: In Rose, create a new class diagram in the Design Phase section ƒ 2: Add objects (for each object in your object table) ƒ 3: Add definitions, attributes and operations to each object ƒ 4: Define relationships between objects Slide number 7

8 +RZGR,FUHDWHWKH XVHUV REMHFW PRGHO" FRQWLQXHG«ƒ5: Define multiplicity between objects Multiplicity ƒ6: Continue adding objects (The actor stereotype is used to represent people that the system need to know about) Actor Slide number 8

9 +RZGR,FUHDWHWKH XVHUV REMHFW PRGHO" FRQWLQXHG«Generic relationship defined In user terms Slide number 9

10 +RZGR,FUHDWHWKH XVHUV REMHFW PRGHO" FRQWLQXHG«Association Object For many-to-many relationships add an object to represent the relationship ƒ An existing form is often the right object for this Definition: A description of the customers needs that the hotel commits to fulfil (an agreement) Slide number 10

11 8VHUV REMHFW PRGHO Slide number 11

12 'HVLJQ $EVWUDFW 'HVLJQ 3URFHVV Slide number 12

13 'HVLJQHU V 7DVN 0RGHO 3URSRVHG WDVN PRGHO ƒ Purpose of modelling task flow the system will enable: To describe the breakdown between user tasks and system tasks so that the user experience architecture begins to be formed. ƒ Definition of designer s task model: A high level description of the enabling structure (generally a sequence of activities and decision points) that the system intends to enable the users to perform. ƒ UCD activities: ƒ Design activity is to reference the user s current task flows (and pay particular attention to the points of pain) and define what will be the task flow the system will actually enabled Slide number 13

14 +RZ GR, FUHDWH WKH GHVLJQHU V WDVN PRGHO" Users current task model ƒ1: Review users current task model ƒ2: Identify activities or interactions (such as when lines cross the swim lanes or activities between decision points) that indicate an interaction between the user and the system Interaction between clerk and system! Have to figure out what objects are involved in this activity and what happens after data is returned by the system this activity will inform the designer s task model and the abstract views Slide number 14

15 'HVLJQHU V 7DVN 0RGHO 7DVN 2YHUYLHZ These steps define how the check availability step will work (at a high level) ƒ 3: Add activities in the order tasks will be completed in the new system ƒ Do not have to match existing practice, but be aware of the learning required by the users ƒ ƒ Treat system as a black box Only reveal essential details ƒ Show where process occurs and decisions are made Slide number 15

16 'HVLJQHU V 7DVN 0RGHO 7DVN 2YHUYLHZ ƒ 4: Add states to indicate when the system will be displaying a state to the user until a state-change event occurs State Slide number 16

17 7KH $EVWUDFW 'HVLJQ 3URFHVV Slide number 17

18 $EVWUDFW 9LHZV ƒ Purpose of modelling abstract views: To describe what parts of a user object are needed in order to perform a task. ƒ Definition of abstract view: A device independent description of what the user will experience (user touch point) that enables users to accomplish their task. Users do NOT interact with objects directly they work THROUGH views of objects. ƒ UCD activities: ƒ Utilizing the users object model and the designer s task model, abstractly define the views on objects that are required to support the task. Slide number 18

19 +RZ GR, GHILQH DEVWUDFW YLHZV" ƒ 1: Review most frequent or most commonly used tasks first ƒ 2: Start by figuring out what objects are involved in that activity and define a view of that object that has the necessary information What object(s) is involved in this activity? Slide number 19

20 +RZ GR, GHILQH DEVWUDFW YLHZV" Abstract view for make a reservation Abstract view Object ƒ 3: Hotel object is involved in the task so add the hotel object to a new diagram ƒ 4: Create a view on that object that contains the information required to perform the task ƒ 5: Identify which attributes and operations from the parent object the view will be using (Note: some attributes and operations will be unique to the view as this particular view isn t stored in the system) Slide number 20

21 +RZ GR, GHILQH DEVWUDFW YLHZV" ƒ Return to task model and find another activity that requires a view Look at sequence of activities that result in a new state Slide number 21

22 +RZ GR, GHILQH DEVWUDFW YLHZV" Abstract view for Create a reservation Denotes view composition For this view, 3 views of objects are composed. The ease of use of the user experience will come from that reuse of objects that are found in the users object model Slide number 22

23 ([HUFLVH ƒ Exercise: Create the views needed to check in a guest ƒ Time: 15 minutes and then take a break ƒ While doing: ƒ Discussion: Informal discussions due to time and size of workshop Slide number 23

24 ([HUFLVH &KHFNLQ GHVLJQHU WDVN PRGHO Slide number 24

25 ([HUFLVH FKHFNLQ DEVWUDFW YLHZ Slide number 25

26 7KH $EVWUDFW 'HVLJQ 3URFHVV Slide number 26

27 'HWDLOHG 7DVN )ORZV ƒ Purpose of modelling detailed task flows: To describe the exact sequence of events to ensure that the view definitions are complete (views have to contain the operations shown in the task flow). ƒ Definition of detailed task flows: A diagram that shows that sequence of actions performed by the user and what the system does in response to these actions (responses the user would perceive). ƒ UCD activities: ƒ Utilizing the the designer s task model, and the abstract views, define the sequence of events from the users perspective (not the system events) Slide number 27

28 7DVN )ORZ LQ 'HWDLO This should be an operation in the view being used ƒ To read these diagrams Read down a column to determine the order of activities performed by the entity (an actor, object or view) Slide number 28

29 7KH $EVWUDFW 'HVLJQ 3URFHVV Slide number 29

30 2EMHFW 6WDWHV ƒ Purpose of modelling object states (can model view states too): To describe the way in which objects change as a consequence of users interaction with the object (through views). ƒ Definition of an object state: A condition or situation during the life of an object during which it satisfies some condition, performs some activity, or waits for some event. ƒ UCD activities: ƒ Review the detailed task flows and determine the states the object is going through as operations are performed with the object. Slide number 30

31 2EMHFW 6WDWHV Transition ƒ Use state diagrams (Harel Diagrams) to show normal processes for an object or a view Start State ƒ Transition names should correspond to operations ƒ Convert to state tables to examine all combinations of states and transitions End State Slide number 31

32 6WDWH 7DEOH Rows: States, Columns: Operations Open Inputs Process [valid data] Process [invalid data] Reenter input Check-in Close out [Initial] To receiving input Receiving input To receiving input To confirmed To invalid Confirmed To [final] Invalid To receiving input To [final] Slide number 32

33 6WDWH 7DEOH Rows: States, Columns: Operations Open Inputs Process [valid data] Process [invalid data] Reenter input Check-in Close out [Initial] To receiving input Not available to the user Receiving input Confirmed Open is an internal action so not available to the user To receiving input To confirmed To invalid Must be invalid Not allowed - no changes are allowed once a reservation is confirmed Not allowed To [final] Not allowed Not allowed Invalid Not allowed To receiving input Not allowed To [final] Slide number 33

34 &RPSOHWLQJ $EVWUDFW 'HVLJQ Have Use Cases Task Synthesis Find User Objects Design Outline Tasks Design Abstract Views Map Object and View States Create Det ailed Task Diagrams ƒ Exit abstract design when you have ƒ ƒ ƒ Processed all the use cases Found or created no new objects in last pass Validated the model with users ƒ Typically done using low fidelity prototypes Slide number 34

35 ([HUFLVH ƒ Exercise: Create the state chart from the state table for a hotel room. Consider how to complete the empty cells. ƒ Time: 15 minutes and then take a break ƒ While doing: ƒ Discussion: Informal discussions due to time and size of workshop Slide number 35

36 ([HUFLVH 6WDWH 0RGHOV Free Occupied Needs Cleaning Check In Check Out Clean Slide number 36

37 ([HUFLVH 6WDWH 0RGHOV Free Occupied Needs Cleaning Check In To occupied (start Folio) Not allowed Should not happen Check Out Not allowed To need cleaning (complete Folio) Not allowed Clean Should not happen (already cleaned) To Occupied (guest request) To Free Slide number 37