1 / 21

Creating ubicomp systems

Creating ubicomp systems. Elements of research. Problem Goal Hypotheses Approach. Why build ubicomp systems?. Problem Address problem or societal need Goal Prototype Hypotheses Test hypotheses Approach User studies (mobile users, public) Datasets Test limits of technologies.

allene
Download Presentation

Creating ubicomp systems

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. Creating ubicomp systems

  2. Elements of research • Problem • Goal • Hypotheses • Approach

  3. Why build ubicomp systems? • Problem • Address problem or societal need • Goal • Prototype • Hypotheses • Test hypotheses • Approach • User studies (mobile users, public) • Datasets • Test limits of technologies

  4. What kind of system? • The real thing • Prototype: • Low fidelity prototype • Video (e.g. Tap input as an embedded interaction method for mobile devices) • Rapid prototype • Wizard of Oz (e.g. The effects of speech interface accuracy on driving performance) • Almost the real thing (e.g. Lucid Touch)

  5. Lucid Touch • http://www.youtube.com/watch?v=RsNFZAEssPQ

  6. Elements of a good system

  7. On the subject of Rome…

  8. Elements of a good system • Semantic Rubicon: • What can the system know about the world and user? • What does the user know about the system? • Interactions of the two?

  9. The system side • Seamful design • What to show the user? • Pessimistic: only what is known to be correct • Optimistic: everything as though it was all correct • Cautious: present uncertainty • Opportunistic: exploit uncertainty

  10. The user side • When to involve the user? • Frequency and inconvenience • Speech recognition accuracy low/high • Severity of consequences • “Lights and siren!” • Reliability of system decisions • Are you sure you should bother me? • Acceptability of automating tasks • Parking, driving

  11. Example: Search Vox • T. Paek, B. Thiesson, Y. Ju & B. Lee. Search Vox: Leveraging multimodal refinement and partial knowledge for mobile voice search.Proceedings of User Interface Software and Technology (UIST), 2008 • Video • Tim Paek, Microsoft Research

  12. “It is always runtime” • Need careful startup? That’s a problem. • Sporadically available elements? Handle gracefully. • What if individual elements fail/are disconnected? • How do you handle data when a source is disconnected and when reconnected? • Reconnection example: epidemic propagation • Identify version mismatches.

  13. Debugging • Log files • Heartbeat • Status displays (e.g. LED, sound) • Diagnostic interfaces • Remote access • Externalize state or communications (e.g. publish/subscribe)

  14. Debugging: P54 examples • Log files • Standard • Heartbeat • Observe interactions with infrastructure • Status displays (e.g. LED, sound) • User interface

  15. Debugging: P54 examples • Diagnostic interfaces • Sniffer • Remote access • Security requirements prevent live access • File exchange servers • Jacob LeBlanc, Thomas E. Hurton, W. Thomas Miller, III, Andrew L. Kun, “Design and Evaluation of a Vehicle Data Distribution and Collection System,” Pervasive 2007

  16. Debugging: P54 examples • Externalize state or communications (e.g. publish/subscribe) • P54 server could be used for this purpose: e.g. recover tag bank

  17. Debugging: P54 examples • Externalize state or communications (e.g. publish/subscribe) • P54 server could be used for this purpose: e.g. recover tag bank

More Related