The aim is to provide synchronised work environment for all types of elderly users (mobile distance and office desktop workers, teleworkers and generally flexi-workers) and hide all complex technological aspects from the elderly user and provide a “plug and play” connectivity with the working environment.
The user would like to flexi work (either from his/her home which we expect to be the most typical case or when he/she is on the move) using soft skills applications such as email, web browser, office automation and/or other “profession dependant” applications. The “OASIS - Connecting Bridge” will facilitate his/her connection with the company server hiding all the complexity that existing connecting tools might have
System output
The user is connected to his/her company IT infrastructure and is able to perform a number of IT related tasks in the same way as his/her office
1) Number of successful connections to the IT infrastructure of the company 2) Remote working hours
Environmental restrictions
Interaction level
Step 1 – the user wants to be connected to the IT infrastructure of his/her company by pushing a specific button (real or virtual hw/sw embedded) of his/her working device (Home PC, Laptop, PDA, etc)
Step 2 – the “OASIS - Connecting Bridge” taking into consideration all different parameters such as working device, company IT infrastructure security settings, working environment and telecom network existing in the environment, etc connects the user working device with his/her company IT infrastructure end emulates his/her working environment in the office
Step 3- the user is able to perform a number of IT related tasks in the same way as his/her office
static parameters: company IT infrastructure security settings
semi-dynamic parameters: working device and telecom network, etc.
Quality of service indicators
- Minimum questions asked for succeeding the connection
- Uninterrupted connection
Potential input needed from other UCs (what input and which UCs?)
- Login credentials
Important accessibility attributes (per UG)
Desktop accessibility attributes (already set by other applications)
Background info/ reason on selection and on assigning the priority level
References
Comments
The bridge should be such that does not impose to the user to install any software or device. Web-based interfaces (i.e. Web 2.0) constitute the first choice for the task (to be further analysed however in the relevant WP).
Figure 95: SP3-33 Connecting bridge
SP3-34 Work Assistant application
Context of use (aim)
The aim is to generate easily understandable workflows, to guide the user in the everyday working requirements
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Secondary actor(s)
Home automation service providers
Telematic service providers
Connected UCs
Priority Level
Secondary
Scenario(s)
The user would like to flexi work (either from his/her home which we expect to be the most typical case or when he/she is on the move). The “OASIS – Work Assistant” application will facilitate the user to generate easily understandable workflows, to guide the user in the everyday working requirements.
System output
Easily understandable workflows
Relevant OASIS WP
WP3.5
Services involved
Smart workplaces
Devices & restrictions
11a. User Interaction devices & restrictions
PC mainly (and PDA)
11b. Sensor devices & restrictions
N/A
Critical success parameters
Services
Success parameters
Smart workplaces
Accuracy of the tasks provided in the workflows and appropriate timing
Environmental restrictions
Interaction level
Step 1 – the user calls the “OASIS – Work Assistant” application
Step 2 – the application provides the user easily understandable workflows that guide the user in his/her everyday working requirements, tracking also his/her accomplishments.
Personalisation/ adaptation level
Yes:
semi-dynamic parameters: links with other applications to monitor the status of the user taskς.
Quality of service indicators
- Understandable and useful workflows
- Task accomplishment monitoring
Potential input needed from other UCs (what input and which UCs?)
Depending on the applications that worked by the user.
Important accessibility attributes (per UG)
Workflows and HMI adaptable to UG.
This should be linked to the health monitoring as well, to avoid stress levels, etc. and to maybe also have messages that recommend the user chills out when stress levels are too high.
Background info/ reason on selection and on assigning the priority level
References
Comments
This workflow approach would bring the user from application to application, but in a rather transparent manner.
In fact, the user would “initiate” the daily workflow, starting e.g. with a note saying that s/he needs to check his/her “virtual online” appointments, and after having done that, to login to e.g. Skype, etc.
Not clear whether this is an approach using notes, but also applications may be pushed to the user.
Figure 96: SP3-34 Work assistant
SP3-35 Advanced authentication mechanism
Context of use (aim)
The aim is to facilitate the user to be connected with his/her company IT environment. In this use case emphasis is on service security, and user authentication issues using biometric authentication technologies.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Secondary actor(s)
Home automation service providers
Telematic service providers
Connected UCs
Priority Level
Supportive
Scenario(s)
A biometric authentication mechanism fully integrated into an ambient intelligent environment will allow elderly users to login without having to remember complex usernames and passwords. Biometrics information could be stored a priori in a smart card so as to be used statically in desktop applications or directly (e.g. by fingerprint sensors which can easily be integrated into small devices or by face recognition with small integrated cameras in PDAs and mobile phones) while on the move. Also the smart seat of A3.5.1 could be used for this task for physiological signals and/or seating profile based authentication. Special agents in advance will orchestrate the authentication process and decide which method is appropriate according to active application and user needs.
System output
Secure connectivity to the company IT infrastructure
Relevant OASIS WP
WP3.5
Services involved
Smart workplaces
Devices & restrictions
11a. User Interaction devices & restrictions
PC (and PDA)
11b. Sensor devices & restrictions
N/A
Critical success parameters
Services
Success parameters
Smart workplaces
Secure and uninterrupted connectivity
Environmental restrictions
Interaction level
Step 1 – Biometrics information is stored a priori in a smart card
Step 2 – The user provides seamlessly the biometrics information either putting the card in a specialized device or provide his/her fingerprint sensors in a small device
Step 3 – The user is authenticated and has a secure connection with his/her company IT environment
Personalisation/ adaptation level
Yes:
static parameters: User biometrics information
Quality of service indicators
- Easily stored biometric information
- Easily connected biometric scanning devices
Potential input needed from other UCs (what input and which UCs?)
- Biometrics information stored a priori in an appropriate place (e.g. smart card, etc.).
Important accessibility attributes (per UG)
Authentication must fit with user profile and disability associated with it (a tremor in hand can make proper fingerprint authentication cumbersome).
Background info/ reason on selection and on assigning the priority level
The user can perform his/her tasks without this module. However this module provides an advanced authentication and security mechanism which facilitates the user authentication and secures the connection if this is required in certain professions.
This Use Case highlights the importance of mobile work for the elderly. It facilitates access to user’s data while freely moving from each device to another. Data synchronization is handled automatically by the system without user interference.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Connected UCs
Priority Level
Essential
Scenario(s)
The user can perform changes on one device and review them from another. Data synchronization between the devices is performed automatically and transparently by the system itself. For example, a user can add a new appointment in his/her PDA calendar, which will be automatically shown at his/her PC calendar as well (via web services).
System output
The system upon start-up must transparently synchronize data between devices, offering user the capability to access data from all his devices.
Relevant OASIS WP
3.5 (A3.5.2, A3.5.3)
Services involved
Smart workplaces
Devices & restrictions
11a. User Interaction devices & restrictions
OASIS Devices : PC, PDA and Mobile Phone
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Smart workplaces
Applications’ ability to synchronize data from different devices.
User friendliness of the application.
Interoperability in terms of connected devices.
Environmental restrictions
Interaction level
Step 1: The user after having interacted with one device (e.g. PC), boots the OASIS Framework on another to continue his work (e.g. PDA).
Step 2: The user launches any of the smart workplaces applications.
Step 3: The system synchronizes application’s data between different devices and provides the user with an up-to-date view.
Personalisation/ adaptation level
No
Quality of service indicators
Reliability demands: 100% reliability (i.e. the system provides the correct info to the user).
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
The User Interface of smart workplaces applications must be properly designed for elderly users.
Background info/ reason on selection and on assigning the priority level
Mobile Work is valuable to elderly as it offers the ability to work without location restrictions. However, data synchronization could become a complex task for them to perform. Automatic data synchronization though, relieves them from worrying about this issue resulting in increased productivity.
References
Comments
Whenever possible, data exchange should be based upon web services and not physical connections (i.e. by Bluetooth)
Figure 98: SP3-36 Background data synchronisation
SP3-37 On-the-fly Synchronization
Context of use (aim)
This Use Case highlights the importance of mobile work for the elderly. It facilitates migration of current application status while freely moving from each device to another. Data and application synchronization are handled automatically by the system without user interference.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Connected UCs
Priority Level
Essential
Scenario(s)
The user can perform changes on one device and review them from another. Data and application synchronization between the devices are performed automatically and transparently by the system itself. For example, a user can start editing a new appointment in his PDA calendar and then continue his work from his PC without interfering with the migration process.
System output
The system upon start-up must transparently synchronize data and application between devices, offering user the capability to immediately continue his work.
Relevant OASIS WP
3.5 (A3.5.2, A3.5.3)
Services involved
Smart workplaces
Devices & restrictions
11a. User Interaction devices & restrictions
OASIS Devices : PC, PDA and Mobile Phone
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Smart workplaces
Applications’ ability to synchronize data from different devices.
Application’s ability to migrate current status across different devices.
User friendliness of the application.
Interoperability in terms of connected devices.
Environmental restrictions
Interaction level
Step 1: The user while interacting with one device (e.g. PDA), boots the OASIS System on another device to continue his work from there (e.g. PC).
Step 2: The system launches automatically the appropriate (currently active) smart workplaces application.
Step 3: The system synchronizes data between different devices and restores the application’s status (User Interface + Data) from the “source” to the “target” device.
Personalisation/ adaptation level
Yes:
√ dynamic parameters: user attributes
√ environmental parameters/context of use: device capabilities
Quality of service indicators
Reliability demands: 100% reliability (i.e. the system provides the correct info to the user).
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
The User Interface of smart workplaces applications must be properly designed for elderly users and for different devices.
Background info/ reason on selection and on assigning the priority level
Mobile Work is valuable to elderly as it offers the ability to work without location restrictions. However, data synchronization could become a complex task for them to perform. Automatic data synchronization combined with User Interface adaptation though, relieves them from worrying about these issues resulting in increased productivity.
References
Comments
Figure 99: SP3-37 On-the-fly synchronisation
SP3-38 Remote Control
Context of use (aim)
This Use Case highlights the importance of remote control of OASIS applications for the elderly. It facilitates user’s interaction with the system while freely moving in the environment.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Connected UCs
Priority Level
Supportive
Scenario(s)
The user can use one of the OASIS mobile devices in order to interact with the OASIS system running in his PC. For example, a user can connect an external display to his PC and use his PDA in order to remotely use an OASIS application.
System output
The system upon start-up (in the mobile environment) connects with the Remote Control Server in the PC and henceforth propagates all user actions to the server for further manipulation.
Relevant OASIS WP
3.5
Services involved
Leisure and social activities support
Smart workplaces
Devices & restrictions
11a. User Interaction devices & restrictions
OASIS Mobile Devices : PDA, mobile phone
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Leisure and social activities support
Applications’ ability to be controlled remotely via specific events.
User friendliness of the application.
Interoperability in terms of connected devices.
Smart workplaces
Environmental restrictions
Interaction level
Step 1: The user while interacting with one device (e.g. PC), boots the OASIS Framework on another device to use it as a remote control (e.g. PDA).
Step 2: The user launches remote control application.
Step 3: The system upon successful connection establishment is ready to be used as a remote input device.
Step 4: The user interacts with the local interface.
Step 5: The client-side component propagates every user action to the server, where the server-side component is responsible for translating and executing these commands.
Personalisation/ adaptation level
Yes:
dynamic parameters: user attributes
environmental parameters/context of use: device capabilities
Quality of service indicators
Reliability demands: 100% reliability (i.e. the system translates the remote user action correctly).
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
The User Interface of the remote control application must be properly designed for elderly users and mobile devices.
Background info/ reason on selection and on assigning the priority level
Remote Control is valuable to elderly as it offers the ability to work without location restrictions.
Remote control can be used anywhere in the home. It can also be used by more than user at the same time, thus promoting social collaboration.
