1 / 24

Refining and Communicating Tangible Interaction

Refining and Communicating Tangible Interaction. Critiquing the Design Review. Design strengths: Design weaknesses: Ideas for improvement: What aspects are missing in this design: Boundary cases Expected but not specified Unexpected but possible

lawsonr
Download Presentation

Refining and Communicating Tangible Interaction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Refining and Communicating Tangible Interaction Comp150 TUI Spring 2006

  2. Critiquing the Design Review • Design strengths: • Design weaknesses: • Ideas for improvement: • What aspects are missing in this design: • Boundary cases • Expected but not specified • Unexpected but possible • What interactions are possible at a given a context? • How does the set of possible interactions changes with the context? • What interactions are possible to be carried out concurrently? • (bring examples) • Is there enough information to address the : • SW design • HW design • Physical design • (bring examples) Comp150 TUI Spring 2006

  3. Refining the Design of Tangible Interaction • Task Analysis: • List the tasks users expect to accomplish using this system. • Conceptual modeling: • Identify a set of objects required for accomplishing these tasks. For each object list its attributes. • Identify the relations between objects • Describe what actions can be performed upon each object. • Representation: • Decide which objects are represented physically/digitally: • Map conceptual actions to physical actions, identify constraints. • Map relationships between concepts to physical relations. • Construct TAC palette • Syntactic modeling: • Build a high-level state diagram: what tasks can be accomplished within each state, consider how the system changes states, consider temporal relation between tasks. • Use a task diagram to describe the actions and interaction objects necessary for carrying out each of the tasks. Consider temporal relations between actions. Comp150 TUI Spring 2006

  4. The Design Space of TUIs Designers’ Outpost [Klemmer et al.2001] ComTouch [Jacob et al. 2001] Senseboard [Jacob et al. 2001] Media Blocks [Ullmer et al. 2003] Navigation Blocks [Camarata et al. 2002] Tangible Query Interfaces [Ullmer et al. 2003] Comp150 TUI Spring 2006

  5. Communication Why to Model? • Highlight system properties: observability, predicatability, modes etc. • Expose design issues • Compare alternative designs. • Communicate design to SW engineers • Communicate design to ‘customers’ • Design documentation • Generate code from technology independent spec. • Integrate novel technologies Analysis Implementation Comp150 TUI Spring 2006

  6. A Framework for modeling TUIsToken and Constraints (TAC) Paradigm • Tokens: Physical objects that represent digital information • Constraints: Physical objects that constraint the manipulation of tokens by: • Suggesting how to manipulate a token • Physically constraining • Providing a frame of reference • TAC: A relationship between a token and a set of constraints which encapsulates a set of manipulation actions Comp150 TUI Spring 2006

  7. 1 2 3 association dialogue interaction Describing a TUI using TUIVIS TAC Palette Dialogue diagram Task diagram Comp150 TUI Spring 2006

  8. Graphical Representation of Tokens and Constraints Tokens Constraints Comp150 TUI Spring 2006

  9. Combining Tokens and Constraints into TACs Comp150 TUI Spring 2006

  10. The TAC Palette Comp150 TUI Spring 2006

  11. The TAC Palette Comp150 TUI Spring 2006

  12. move orien.t time wind mater.ial dist. Describing the Tangible Dialogue • High level states • Transitions Comp150 TUI Spring 2006

  13. Constructing the Dialogue Diagram • What is the initial state of the system? • What tasks are users willing to accomplish while interacting with the URP interface? • Start from the start state and repeat until you can’t find new states: • What event change the set of tasks users can perform in this state? • Create a new state, describe the new set of tasks. Comp150 TUI Spring 2006

  14. addBuilding /shadow(F) move orien. move orien. addBuilding /shadow(T) addBuilding /shadow(T) wind mater. wind mater. removeBuilding /shadow(F) removeBuilding numOfBuilding=2 /shadow(F) time dist. time removeBuilding numOfBuilding>2 /shadow(F) Dialogue Diagram Comp150 TUI Spring 2006

  15. Task DiagramURP - distance measuring Comp150 TUI Spring 2006

  16. Constructing a Task Diagram • What is the physical state of the system prior to the first action aimed at accomplishing this task? • What are the actions users perform toward accomplishing this task? • What physical interaction objects are needed for each action? • What is the physical state of the system after an action was performed? • What is the internal state of the system after an action was performed? • When does the system physical state goes back to its state prior to the execution of the first action? Comp150 TUI Spring 2006

  17. Task DiagramURP - distance measuring Comp150 TUI Spring 2006

  18. 1 2 3 association dialogue interaction Summary TAC Palette Dialogue diagram Task diagram Comp150 TUI Spring 2006

  19. Project 1, Part 2Analyzing TUIs • What to submit: • A TAC Palette • A dialogue diagram • At least two task diagrams • Discussion of the following topics: • Observability and predictability: • Does the physical state of the system indicate to the user the internal state of the system? Is there information in the internal state that is not presented in the physical state? • Does the physical state of the system contain enough information to enable the user to determine what tasks are available for him to perform? Assuming multiple users interact with the system at the same time. Does the physical state of the system indicate to users what tasks they can or cannot perform in parallel? If possible bring an example of two tasks that different users cannot perform in parallel. • Modes • Certain actions are meaningful only in certain contexts. Bring an example of a user action that is meaningless in one context and has a meaning in another. • Physical Syntax • Does the physical state of the system indicate to users which actions are legal/illegal? Comp150 TUI Spring 2006

  20. Next week • Introduction to technologies • Reading • Start working in teams on a technology demo Comp150 TUI Spring 2006

  21. Designer’s Outpost [Klemmer 2001](An Interactive Surface) Back Comp150 TUI Spring 2006

  22. Tangible Query Interfaces [Ullmer 2003](A Token+Constraints System) Back Comp150 TUI Spring 2006

  23. ComTouch [Chang 2003](A Haptic Interface) Back Comp150 TUI Spring 2006

  24. Web Stickers (Paper Based) Comp150 TUI Spring 2006

More Related