Use cases template

From Web of Things Interest Group

It's a template format for collecting of WoT use cases.

Template of WoT Use Case

[Name of Use case]

use case description (Required)

  • descriptions of use case ....
  • What is the user motivation for the use case
  • Target Use :
  • Category: What application domains are related (e.g. referring to the taxonomy)

Assumptions (Required)

  • descriptions of Assumptions ....

Usage scenario (Required)

  • descriptions of Usage scenarios ...
  • How does the user motivation translate to a technical Description

Technical requirements / topics (Required)

  • descriptions of Technical requirements / topics
  • What interaction pattern with or btw things can be observed

Additional data (Optional)

  • descriptions of Additional data

Justification (Required)

  • descriptions of Justification
  • Which aspects are not considered

Comments (Optional)

  • remarkable comments

UC submitter / supporter (Optional)

  • who is submitter / supporter

Examples

(1) Light Control

Use case description (Required)

  • Control home room lighting and entire home lighting with browser on user devices from within the home or from outside the home.
  • Features include turning lights on, off, dimming, and ganging a group of lights as a single control entity. Control can be immediate or scheduled to occur in the future once or at a scheduled interval either onetime or on some recurrence schedule.
  • Target Use: Home
  • Category: Home Automation

Assumptions (Required)

  • Home lighting is abled to be controlled over a network interface by browser.

Usage scenario (Required)

  • Jonathan has purchased network enabled lighting and has replaced all of his lights with his new purchases in his home.
  • Jonathan open the web browser onto his smartphone that will enable him to control his home lighting.
  • Jonathan launches his new home lighting control web app while in his home and his UI is populated with all the lighting devices that are available for him to control.
  • Jonathan is out with friends and its getting dark and for security purposes he wants to turn on some targeted lights in his home so it looks like he was present.
  • Jonathan pulls out his already authenticated smartphone to his home lighting and launches the lighting control web application. His UI displays his home lighting and the status of each light in his home.

Technical requirements / topics (Required)

  • Service discovery of lighting devices
  • Notification to controlling web application when lighting state has change.
  • Authentication of controlling web application/device with home light devices
  • Control and status of lighting devices.
  • Grouping of lighting devices for control and status

Additional data (Optional)

  • None

Justification (Required)

  • This enables a homeowner for convenience, security, and energy savings to control the home lighting when in the home, remote from the home, or prescheduled basis.
  • There are proprietary solutions in the marketplace and network controllable lighting is currently available in the consumer marketplace.
  • The market need is immediate verses in the future since products are available now!

Comments (Optional)

  • None

UC submitter / supporter (Optional)

  • Jonathan Jeon (ETRI)


(2) Smart Washing Machine

use case description (Required)

  • Joan has a heavy load of washing to do. She decides to run it over night to take advantage of the lower power prices. She loads the clothes into the washing machine and selects the economy operation mode. She has previously set her preferences with her home automation agent that is accessible on the Web from her phone, tablet, TV or laptop.
  • Target Use : smart home
  • Category: smart home / home automation / deferred operation
  • Related Category: smart cities / smart grid / signaling with smart power devices

Assumptions (Required)

  • TBD

Usage scenario (Required)

  • The physical user controls on the washing machine are deliberately simple, and designed to work in conjunction with the web based home automation agent.
  • This agent has access to Joan’s electricity supplier and as is able to track the price charged by her supplier on her electricity plan as it changes according to demand across the city.
  • The agent runs in the cloud, but is able to communicate through the firewall with devices in Joan’s home via her home hub.
  • This was set up automatically when she first plugged the machine in. The washing machine has a very limited embedded controller.
  • It suffices to run the desired washing and drying cycle, and has sensors that monitor its operation and enable components that are wearing out to be detected before they fail. Joan has agreed to share this data with the manufacturer as part of the warranty agreement.
  • In return, she gets proactive scheduling of service visits at her convenience.

Technical requirements / topics (Required)

  • Thing registers: thing registers with service in the cloud
  • Configure data subscription: specific data field (e.g. for maintenance) is forwarded (e.g. to manufacturer)
  • Thing integration in web based agent

Additional data (Optional)

  • none

Justification (Required)

  • these aspects are not considered
    • Life cycle of devices, services and applications
    • Discovery of devices
    • Installation process
    • Dealing with faults
    • Replacing devices
    • Taking devices out of operation

Comments (Optional)

  • none

UC submitter / supporter (Optional)

  • Dave Raggett (W3C), Joerg Heuer(Siemens)


(3) Shutter Control

use case description (Required)

  • Jo has motor driven shutters in front of the windows. He wants that the shutter control adapts to the lighting and presence in the house. So he combines the shutter control with other sensor services such as web based information on day light. If he is not present the shutter is closed in the evening and opened in the morning. If he is present he explicit controls it with a switch sensor. In this case closing the shutter result in switching on a minimum lighting. Finally one switch is configured by Jo as emergency opening of the shutters.
  • Target Use : smart home
  • Category: smart home / home automation / shutter control

Assumptions (Required)

  • TBD

Usage scenario (Required)

  • The resources of the shutter controller can be discovered by the web browser.
  • The resources can be mashed up with web based information such as daylight information.
  • This mashup can be activated by a resource of the presence sensor.

Technical requirements / topics (Required)

  • Thing discovery: find things in the local network
  • Thing resource browsing: to create a mashup the resource of the thing can be browsed
  • Mashup of Thing resources: thing resources can be mashed up (this might need some further clarification)

Additional data (Optional)

  • none

Justification (Required)

  • These aspects are not considered
    • Life cycle of devices, services and applications
    • Installation process
    • Dealing with faults
    • Replacing devices

Comments (Optional)

  • remarkable comments

UC submitter / supporter (Optional)

  • Joerg Heuer(Siemens)
Retrieved from "https://www.w3.org/WoT/IG/wiki/index.php?title=Use_cases_template&oldid=151"