1 / 15

Task 1.1: Building Scenarios

Task 1.1: Building Scenarios. Agenda. Introduction Scenarios Conclusions. Introduction. Scenarios show uses of context-driven mobile services in AmI Based on ISTAG scenarios for AmI in 2010 Goals (guide for CoDAMoS project): Detect technical requirements to make AmI happen

iniko
Télécharger la présentation

Task 1.1: Building Scenarios

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. Task 1.1: Building Scenarios

  2. Agenda Introduction Scenarios Conclusions

  3. Introduction • Scenarios show uses of context-driven mobile services in AmI • Based on ISTAG scenarios for AmI in 2010 • Goals (guide for CoDAMoS project): • Detect technical requirements to make AmI happen • Define the challenges • Discover pitfalls

  4. Scenarios • Near term vs technology demanding scenarios • First two scenarios in cooperation with User Commission members  Success • Meanwhile all 7 scenarios in cooperation with User Commission members • CoDAMoS website (http://www.cs.kuleuven.ac.be/cwis/research/distrinet/projects/CoDAMoS/)  User Commission section: • Deliverable 1.1.2 • Scenarios section

  5. Scenarios: Overview • Short scenario overview • Notice: • WP7 (Integration of results) and WP8 (valorization) connected to all scenarios

  6. Scenario 1 • Instant Messaging: Alcatel • Context-Sensitive IM: adaptation to environment (TV with avatars) • Location of user and device is transparent for IM service • Multi-Modal user interfaces (speech and audio) • User profiles + automatic agenda synchronization

  7. Scenario 2 • Advanced Online Communities: Androme N.V. • Online communities that go much further than normal website driven communities (e.g. forum) • Requesting on-site information and help from community members that are in the vicinity (transparent)  Location context • Transparent payment handling • Device independency: GSM, PDA,….

  8. Scenario 3 • AGV Maintenance System: Egemin • Context-sensitive planning of maintenances on AGV systems  announcement of upcoming defects and maintenance • Calendar service and planning service for agenda synchronization with engineers • Use of extra services underway

  9. Scenario 4 • The Right Time for a Virtual Business Meeting: Siemens N.V. • Efficient, location transparent and device independent meetings  Unified Communication System • Targeting persons and not devices: Device independent • Presence information of users detected by analyzing behaviour • Location • Mood: sad, happy,… • Availability: meeting (available for urgent calls) • …

  10. Scenario 5 • Integrated Traffic Information: VRT • Using AmI to “push” important traffic information to individual users based on: • Presets • Communication and processing platforms (PDA, GSM, PC,…) • Knowledge of the whereabouts of the traveler (GPS or other indirect means)

  11. Scenario 6 • The Museum Visit: Gallo-Roman Museum of Tongeren • Surroundings visitors determine information shown to the user • Museum artifacts • Available means of communication • Other users in same group • Interface adapts to user profile • E.g. younger vs older people

  12. Scenario 7 • Mobility through AmI: Hogeschool Limburg (JaDiMO HOBU project) • Enhance mobility experience by automatic creation of mobility communities (e.g. for a particular region) • Within a group  Query for: • Transportation resources • Traffic jams • Bus/train schedules • … • Context-based planning of transportation, routes and rewards (for people offering rides)

  13. Conclusions (1) • Context information is very important: • Environment: • planning of transportation dependant on the weather • Location: • contacting community members based on location • looking up traffic jams based on location • Platform: • adaptation of UI based on platform information • migrating code to platforms with more computation power • User: • user preferences for selecting drivers • presence information

  14. Conclusions (2): coverage

  15. Conclusions (3) • User Commission members (can) cooperate in the development/implementation of the scenarios • Different Work Packages are involved for realizing scenarios • Use scenarios to guide and evaluate WPs development • AmI makes life easier, more efficient and more fun

More Related