Pilot 2 - Work Overview

From wiki.gpii
Revision as of 16:44, 6 November 2013 by Bsheytanov (talk | contribs) (Pilot Scenario:: Updating status of Astea's tasks)
Jump to: navigation, search

Contents

Relevant documents:


PILOT 2 PANIC LIST/PLAN

Pilot Scenario:

STEP 1 - User uses platform A (either Windows or Linux) and the PMT (launched via a desktop shortcut) to create a new GPII account and insert preferences

STEP 2 - User saves and applies their preferences, which saves the preferences (to the preferences server), and system automatically applies them to the system, generates a token and shows the user what their new token is

STEP 3 -  Facilitator puts the token on USB or NFC/RFID

STEP 4 - Facilitator using a desktop icon takes a snapshot of the settings for purposes of logging of the solutions we are testing: Orca, NVDA, Supernova, Maavis, built in Windows and Linux a11y features

STEP 4 - User closes the PMT which brings up the PCP. User modifies settings and immediately sees the changes on the system. User then saves the changes.

STEP 5B - User manually modifies settings in the ATs. 6. Facilitator takes a snapshot of the settings for purposes of logging - in case of manually modified settings in step 5b, the snapshotted settings are uploaded to the prefs server

STEP 7. Facilitator selects a matchmaker using a desktop icon.

STEP 8. User logs out of Platform A

STEP 9. User logs into platform B (Windows, Linux, Android, Simple phone, Windows tablet)

STEP 10. Facilitator takes a snapshot of the settings for the purposes of logging of the solutions we are testing: platform A solutions, Android built in a11y features, Mobile Accesibility (android), Java phones built in features and conf call app, smarthouse, eCtouch , eC mobile, Sociable, Google Chrome

STEP 11. User manually tweaks settings in the application(s)

STEP 12. Facilitator takes another snapshot of the settings (using the logging tool or manually, depending on the SP3 application)

STEP 13a. User logs out of the system Continuing scenario for Non-sighted users:

STEP 14b. User logs into platform A with multiple screen readers installed - Supernova and NVDA

STEP 15c.The system displays a message that the facilitator reads to the user.

STEP 13b. User logs into a platform X which is (simulated) lockdown mode with only browser available

GENERAL

Demos at the pilots:

1. Context Awareness Support

2. Advanced PMT wireframes


SP3 Implementations:

SuperNova:

Smarthouse

Linux:

Windows:

Sociable:

Google Chrome:

Android:

Maavis:

Mobile Accessibility:

Java Mobile:

NVDA:

WebAnywhere:

eCTouch and eCMobile:

Other:

Next Steps: Clarify with Claudia what the system can do in terms of the pilots. Find out if there is anyone else building other scenarios. Get estimates from Antranig, Boyan, Jess Create JIRAs for SP3 apps, based on: https://docs.google.com/document/d/1sU6e5Su5DUn928ZhBEfXQOsmaYjrEFP5FqHgXG6yQc8/edit#heading=h.g9ses598hi5c Consider Out of Scope

Applications that don't give us an API to make the modifications directly.