Smart House Use cases

From wiki.gpii
Jump to: navigation, search

This page is about the smart house activity in the Cloud4all project (November 2011 – October 2015) and is now outdated.

Use Case 1

1. Title: Auto-personalisation of home appliances and devices in a foreign environment

2. Development team: ASTEA

3. Short description (context of use): People who need AT support usually have it set up at home. However, applying the same configuration at a foreign place is time-consuming and wearisome. This use case shows how the Cloud4all infrastructure allows easy application of personal settings in various home environments (in parents’ house, at a friend's house, in a hotel, etc.)

4. Context elicitation: Home appliances and devices

5. Restrictions: Appliances and devices should support a remote configuration interface in order to benefit from the Cloud4all auto-personalisation mechanisms.

6. Primary actor(s): All users

7. Secondary actor(s): Professionals support users with configuring their devices

8. Priority Level (Essential, Secondary, Supportive): Essential

9. Background info/reason on selection and on assigning the priority level: When a user is in a foreign environment, it is very important that their specific needs are met. Not doing so might pose a risk to the health of the individual or lead to severe discomfort.

10. Application Scenarios (to be used as a basis for Pilot testing, could be one or more depending if all your implementation features can be addressed in one solid scenario or not):

10.1. Application Scenario 1

Short Description: Helen is a 25-year old student who completely lost her sight due to an accident. She lives alone and is worried about the safety of her home, so she has a security system installed. Helen is heavily dependent on non-visual feedback from any devices she is using. The security system requires a numeric code to be entered to be turned on or off. It has a feature for pronouncing the number corresponding to the button pressed. The A/C system is controlled by a remote control that vibrates in different patterns as air conditioning is turned on/off or the temperature is changed. Helen often visits her parents’ home, where she needs the same settings to feel comfortable. They want these settings to be applied only when she visits them, so they have installed an RFID card reader at the entrance.

Interaction steps:
Step 1: The user identifies himself or herself with an RFID chip.
Step 2: The system authenticates the user and gets their preferences from the cloud-based server.
Step 3: The matchmaker determines the best settings for this person and all devices in the house that allow personalisation.
Step 4: All devices in the house that allow it receive the personalisation settings and apply them.
Step 5: Tactile feedback is applied to all devices that support it.
Step 6: Audible indicators are enabled on all devices that support them.
Step 7: The user enters the house and turns off the security systems. Numbers on buttons pressed are pronounced.
Step 8: The user turns on the heating. The remote control vibrates once to indicate that.
Step 9: The user logs out of the system by touching the RFID chip to the reader again. All settings are restored to their previous state.

System output: Once the user is identified the system applies the user preferences to all devices that support personalisation. Settings are transferred either wirelessly to each device or through a cable that connects them to the RFID reader. Audio indicators are turned on for the security system and tactile feedback is enabled on the A/C system remote control.
Critical success parameters: Devices should support audio indicators and tactile feedback. Devices should provide remote configuration interface over WiFi or cable.
Pre-conditions: None

10.2 Application Scenario 2

Short Description: Ivan Petrov is 23-year old Bulgarian struggling with the Down Syndrome. He is sent to Germany for experimental treatment procedures. During his stay there he is accommodated in a modern hotel near the clinic. Ivan doesn't understand German and he has difficulties with his mobility and motor skills. The hotel is equipped with some of the latest technology advancements in order to accept patients with similar conditions. The multimedia system (TV, radio, stereo), phone, etc. have the ability to personalize their button mapping and language in order to help patients during their stay. Ivan uses similar home appliances in his home back in Bulgaria, so he has his personal settings on his mobile phone and can transfer them to the devices in the hotel room using NFC.

Interaction steps:
Step 1: The user identifies himself using the NFC on his personal mobile phone.
Step 2: The system sends to the cloud-based server a list with available home appliances that are compatible with the services.
Step 3: Matching of user specific settings and available customizable devices is done on the server.
Step 4: The result with specific customized settings is sent to the devices in the hotel room.
Step 5: Changed settings are applied to the devices in the room. The buttons of the multimedia system are remapped for ease of use (some are disabled and the most used are assigned to the most accesible). The same is done for the HVAC.
Step 6: Devices for which the user has no specific customizations are restored to their default state (in case they were previously changed for other hotel visitors and not changed back).
Step 7: At the end of his stay at the hotel the user uses the NFC of his personal mobile phone again to log out (reset his personal settings).

Critical success parameters: Devices should support button remapping and different languages. Devices should provide a remote configuration interface over WiFi or cable.
Pre-conditions: None

11. Services related to your implementation: Acommodating facilities (hotels, rehab centers, nursing homes); Private homes;
12. Innovation:
13. UML Diagram: (later)
14. Connected UCs: SP3-1, SP3-2, SP3-5, SP3-6, SP3-14, SP3-16, SP3-20, SP3-21
15. Mapping to user requirements: (later)
16. List of registry-based preferences: (later)
17. Where in the project
17.1. Relevant Cloud4all WP this will take place: WP305
17.2. Relevant Cloud4all Activity this will take place: A305.3
18. References & Additional comments (if any): -

Use Case 2

1. Title: Multiple profiles for auto-personalisation of home appliances and devices

2. Development team: ASTEA

3. Short description (context of use): People who need AT (or specific settings) usually live in a place together with someone else. In some cases the preferences for appliances and devices set by one person might not be appropriate for the other. The goal of this use case is to show how Cloud4All will handle the need for multiple profiles in one environment.

4. Context: Home appliances and devices

5. Restrictions: Appliances and devices should support a remote configuration interface in order to benefit from the Cloud4all auto-personalisation mechanisms.

6. Primary actor(s): All users

7. Secondary actor(s):

8. Priority Level (Essential, Secondary, Supportive): Secondary

9. Background info/reason on selection and on assigning the priority level: The preferences of the users with particular needs are often treated with priority by the members of their families or their co-inhabitants.

10. Application Scenarios (to be used as a basis for Pilot testing, could be one or more depending if all your implementation features can be addressed in one solid scenario or not):

Use Case 2: 10.1. Application Scenario 1

Short Description: Adam is a 30-year old cook who has astigmatism (vision is blurred) and deuteranomaly (partial colour blindness). In his kitchen all electronic displays are adjusted to have a high contrast between the text and the background. He works together with 10 co-workers in a restaurant. In order to be more effective at that, he applies his settings to the kitchen appliances he will use. In order not to slow down his co-workers, after finishing his work with the current appliances he restores the default settings.


Interaction steps:
Step 1: The user identifies himself to the device, using the NFC on his personal mobile phone.
Step 2: The system sends to the cloud-based server a list with available settings that are compatible with the services.
Step 3: Matching of user specific settings to the current appliance is done on the server.
Step 4: The result with specific customized settings is sent to the appliance in the kitchen.
Step 5: User settings that are supported by the current appliance are applied.
Step 6: Before leaving, the user uses the NFC of his personal mobile phone to log out, which results in restoring the previous settings of the appliance.

System output: Once the user is identified the system output is the following: the settings of the device are automatically modified. Settings are transferred either wirelessly or through a cable that connects it to the server. The font of the menu is bigger. The custom colour theme is applied to the display of the appliance.
Critical success parameters: Appliance should support font size and colour customization for its display. Appliances should provide a remote configuration interface over WiFi or cable.
Pre-conditions:-

Use Case 2: 10.2 Application Scenario 2

Short Description: Albena is a 40-year old user with a hearing impairment. She wears a hearing aid although it doesn’t restore her hearing completely. She needs a higher volume when using the home multimedia system (TV, DVD player, home theatre etc.) or for calls on the phone. She also prefers other types of interaction to avoid relying only on sound. The members of her family have normal hearing, and it is not possible to configure the volume settings or the non-sound indicators once and for all, as there is no specific setting that would be acceptable for all members. When she is alone at home, Albena configures the home phone with her preferred settings by identifying into the system (using her USB identifier, NFC ring or another way). Once she logs in, the phone settings automatically change - the volume during call changes to her preferred level, and visual indicators for incoming calls turn on. When she wants to use the multimedia system (watching TV or using the home theatre), she logs into the system in the same way. Once she is identified, the volume of the system changes to her preferred level and subtitles are turned on.
Edge case: as the maximum volume level of the systems is harmful for her family, a priority of user preferences is set: when another member of the family identifies with the multimedia system (while Albena is still logged in), the volume sets to the normal level, but the subtitles and other visual indicators remain.

Interaction steps:
Step 1: The user approaches the home phone system and identifies herself with her USB drive, NFC ring or RFID chip.
Step 2: The system identifies the user and sends user ID and device information to a Cloud-server or to a locally located component.
Step 3: The home phone system receives the personalisation settings and applies them.
Step 4: The volume level during calls is set to the maximum and visual indicators for incoming calls if supported are enabled.
Step 5: The user approaches the home theatre system and identifies herself.
Step 6: The system identifies the user and sends user ID and device information to a Cloud-server or to a locally located component.
Step 7: The system receives personalisation settings and applies them.
Step 8: The volume level changes to the maximum and subtitles if available are enabled.
Step 9: The user starts watching a movie on the home theatre system.
Step 10: Another member of the family approaches the home theatre system and identifies him/herself.

Comment: The compromise settings (normal volume combined with captions) are not only relevant when somebody else wants to 
watch TV but also when somebody else is in the same room (or even in a nearby room) and simply wants to read, study or work: 
in this situation, the maximum volume is always disturbing for other family members.

Step 11: The system identifies the new user and sends his/her information and the device information to a Cloud-server or to a locally located component.
Step 12: The matchmaker system determines the priorities of the users for some settings.
Step 13: The system receives the updated personalization settings and applies them.
Step 14: The volume changes to the normal level, but the subtitles remain.
Step 15: Both users continue watching the movie.

System output: Once the user is identified the system output is the following: the settings of the device are automatically modified. Settings are transferred to each device either through wireless connection or through a cable. Volume levels are maximized, visual indicators are turned on, subtitles are turned on.
Critical success parameters: Devices should support visual indicators. Devices should provide a remote configuration interface over WiFi or cable.

10.3 Application Scenario 3:
Short Description: Adam is a 30 year-old cook who has astigmatism (vision is blurred) and deuteranomaly (partial colour blindness). He lives with his wife and 2 kids, and has set the TV in the house with custom settings that allow him to see more clearly: the subtitles are bigger, the menus use high contrast colours and the buttons on it are larger than usual. When Adam is not around, his family prefers the default settings. In order to satisfy them, he always restores the default settings after finishing using the TV.

Interaction steps:
Step 1: The user identifies himself to the TV with NFC on his phone or RFID chip.
Step 2: The system connects to the cloud-based server and sends the available adjustable settings and user authentication to it.
Step 3: The cloud-based service returns the new settings.
Step 4: The settings are applied.
Step 5: Before leaving the user logs out of the system via NFC on his phone or RFID chip.
Step 6: After logging out, the TV settings are restored to their default values.

System output: Once the user is identified the system output is the following: the settings of the device are automatically modified. The font of the subtitles is bigger. The custom colour theme is applied to the menu. The layout, the font size and the buttons size of the menu is changed.
Critical success parameters: Devices should support custom colour themes, font size adjustments and custom layout. Devices should provide a remote configuration interface over WiFi or cable.

11. Services related to your implementation: Restaurants; Private homes;
12. Innovation:
13. UML Diagram: (later)
14. Connected UCs: SP3-1, SP3-2, SP3-5, SP3-6, SP3-14, SP3-16, SP3-19, SP3-21
15. Mapping to user requirements: (later)
16. List of registry-based preferences: (later)
17. Where in the project
17.1. Relevant Cloud4all WP this will take place: WP305
17.2. Relevant Cloud4all Activity this will take place: A305.3
18. References & Additional comments (if any): -

Final Version

Final version (as submitted to the EC) of D101.2 "Use Cases":

See also Use Cases and Implementations.