Pofile initialisation and management

1. Pofile initialisation and management Teleconference 13.11.12

2. Agenda • General Aspects on profile initialisation and management • High impact variables • Use context profile initialization/ management • Process/ screen flow for initialization and management • Next steps for ID102.1 and 1st annual review

3. General aspects on profile initialisation and management • Review of the results of the user workshop in Berlin • Main requirements identified • Based on requirements first concept on profile initialisation and management • Second user workshop on Friday 16th of November to validate concept • LoFi tests at Fraunhofer Laboratory

4. Requirements Profile Initialisation • Users are willing to spend a lot of time on profile initialisation, if they have an added value afterwards, e.g high accessiblity, high usability. • Users would use a personal device (e.g. personal computer, smartphone, tablet PC) for profile initialisation that is already adjusted to the user needs/ already equipped with the needed AT. • There should be two modes for profile initialisation – an expert mode for advanced users and a simple mode for users with cognitive difficulties and low computer literacy. • Profile initialisation could be handled comparable to an application store: different alternatives for preference settings are offered and can be accepted or rejected

5. Requirements • Users would prefer a step by step approach for profile initialisation (e.g. dialogue wizard), where user interface parameters can be adjusted to the user’s needs by selecting an option out of an defined number of proposed options or by adjusting the value for an interface parameter (simple and advanced mode). • users want to take over the device settings of the device used for initialization as default profile. • If the user wants neither the wizard or to take over the device settings, the profile should be left blank until the user changes the setting of a parameter • Users would prefer to set a ‘rough’ profile first and to adjust the preference setting afterwards in more detail.

6. Requirements Profile Management • Clearly structured. • Maximum of three levels within the menu hierarchy. • WYSIWYG – when changing a preference setting a preview of the change should be given. • Clear label of menu items and clear categorisation of variables within the menu • A filter function should be provided to switch between a view of the main preferences and all preferences. • Browser based. • Users would like to manage profiles and to change preference settings of public devices via remote, using a personal device (e.g. preferences settings for a ticket machine are assessed via a persona smartphone using near-field-communication).

7. Concept • Profile initialisation Profile initialisation Device settings asdefaultprofile Wizard high impactpreferences Blank profile • Usecase • The deviceis not setupfortheuser • Caregiverisinitialisingtheprofile • User does not knowhis/ her needsandpreferences • Usecase • The deviceisisalreadyadaptedtotheuserneeds • Use Case • User wantstoadjust a specific variable (not partofthe high impact variables) • User wantstoskiptheinitialisationprocess • Outcome • Profile with high impact variables = global profile • all other variables are blank • Outcome • Profile filled in withsettingsofthedeviceusedforinitialisation • High impactsaswellas all other variables oftheprofilehave a preferencesettingvalue • Outcome • Blank profile • Blank variables arehandledbythematchmaker (e.g. usedefaultofthedevice)

8. General concept • reduce all adaptable interface variables to a defined number of variables that are presented to the user as preference settings for profile initialisation • They are fundamental to make an interface accessible/ perceivable. These variables/ preferences will be presented within the Discovery Aid Wizard and will be provided in the filtered view of the profile management editor. • First set of high impact variables was generated on expert decision using the document „Unified Table D101“ (first with focus on elderly users) • This set will be validated within a requirement analysis with users • High impact variables

9. Concept Profile management Cloud manage General settings • Profile management • Privacy settings • Advancedfunctionalities (recommendations, sharingamongpeers) • Profile selection (device, platform, global • Search for end deviceswithinreach • Preference settings (high impactand all)

10. Profiles Profiles • Global profile • Withoutdevicespecificconditionalpreferences • Will beusedbythematchmakerforaccessingnewdevices • Profileswithinmanagementtoolrefersto a userviewofdevice/platformspecificpreferencesettings (independentofthereprasentation in theregistry/ ontology) • Device specificprofilecanbegeneratedby • accessing a newdevice (matchmaker will derivepreferencesettingsfornewdevice) • Search for a devicewithinareaandsetpreferencesordefinewhichdevicepreferencesettingsshouldbeusedforthenewdevice (advanced) • Device/ platformspecificprofile • Withdevicespecificconditionalpreferences • Will beusedbythematchmakerforaccessingsimilardevices/ platforms • New profile • Search fordevice • Definenewprofile (advanced)

11. User workshop and LoFi tests User workshop • Requirementanalysiswithfocus on • validationof „high impacts“ • Clustering ofuserinterface variables (cardsorting) LoFiusertests • Comparitiveevaluationof different papermockupswithfocus on • Overall usability • Menu structure

12. ID 102.1 Next steps: • Input fromtheworkshopandresultsoftheusertestingto ID102.1 untilWednesdaynextweek (21stof November) • Pendingissuestobediscussedwitharchitectureteamandmatchmakerteam (towhen?) • Whatshouldbereadyfor Madrid • Whatshouldbereadyforthefirstannualreview?