Use Cases and Implementations
This page is the home page for our work defining Use Cases -- leading to early trials and implementations.
The form of a use case would be
- the problem / issue / situation
- how GPII might help in addressing it
- Scenario examples
- What needs to be in place for this to be possible
- minimum that couild be used with Wizard of Oz to study the topic
- minimum for full trial implementations without Wizard of Oz
- What is in place
- Timeline for the rest
- Any plans for this area
The purpose is to help hasten the day when each of these scenarios can occur by highlighting their need to GPII planners, developers, and implementers so that the necessary components will be in place.
The use cases below may first appear as trials, "slices" of a full implementation of C4A/GPII, rendered on a small scale, with a limited set of features for the purposes of learning how C4A/GPII must work and how users and other stakeholders respond to the service. For each example there should be a partnering organization and mainstream and/or AT partners.
- On-demand real-time captioning service (STTR/CART) at a university or other educational institution, where a small number of users could call upon the service of captioners who each know something about the subject of the different class (if only the common terminology), using skills-based routing. This would improve the quality of the service to the students, and also respond to the university's need to make educational STTR/CART more affordable and manageable.
- Library Pack - allows library to easily install a package on its computers that enables C4A/GPII
- works with built-in features, installed AT and/or AT on network/Web
- compatible with the library's network security and special library software (catalogue, etc.)
- Target organization: single library or small metropolitan library system
- AAC service that is ubiquitous and location-aware. The AAC system, on a specific mobile device or available on any computer the user encounters, would provide customized selection interface, etc. as common to AAC, but would additionally customize the active vocabulary based on the user's location.
- Point-of-sale terminals or ATMs. Interface options could include low vision display, screen reading, and touch screen navigation assistance (such as larger targets for either low vision or dexterity impaired users). Target organization: bank, merchant, or transit system.
- Media content customization. Users can get access to specific materials in their preferred formats (low vision interface, TTS, simplified language). Target organizations: museums (explanations of the exhibits), OER community, textbook publishers, educational institutions.
- Transit assistance service for people with cognitive and/or visual disabilities. This location-aware service would help with scheduling rides, making decisions between transit options, alerting or warning the user, identifying the correct vehicle at crowded stations, communicating with vehicle drivers, mid-course assistance for transfers or response to delays, emergency assistance, notification to users about upcoming stop, notifications to caregivers or those expecting the user's arrival, etc. Target organization: transit operators and administrators.
- Video services organizer. This service would make set-top box functionality accessible to users, and would assist with recording and playback of broadcast, saved, or online videos, including rendering them accessibly. Target organization: video services companies (cable, satellite, etc.)
Note that for awareness purposes, some of these trials could be combined at a single location, such as a small city or university. This would give users (and the public) a taste of a fully implemented C4A/GPII -- going from classroom to bank to library, via shuttle, with my personalized interface following me.
Final version (as submitted to the EC) of D101.2 "Use Cases":