Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Month Year Tom Siep, CSRSlide 1 Use Case Discussion Date: 2011-01-20 Authors: 11-11-0191-00-00ai.

Similar presentations


Presentation on theme: "Doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Month Year Tom Siep, CSRSlide 1 Use Case Discussion Date: 2011-01-20 Authors: 11-11-0191-00-00ai."— Presentation transcript:

1 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Month Year Tom Siep, CSRSlide 1 Use Case Discussion Date: 2011-01-20 Authors: 11-11-0191-00-00ai

2 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Month Year Tom Siep, CSRSlide 2 Abstract Materials to facilitate the discussions of Use Cases as a methodology to derive requirements.

3 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Basic Use Case Methodology Actor(s) Device sets Goal Scenario(s) Month Year Tom Siep, CSRSlide 3

4 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Basic Use Case Methodology Actor(s) Unique characteristics of operator, if any –Of initiator device –Of target device operator, if any. If more than one person –describe the relationship between the two people. –level of trust –previous history Month Year Tom Siep, CSRSlide 4

5 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Basic Use Case Methodology Device sets Communicating devices in the use case. Traditional use case descriptions cite one device –Our models require that we describe the characteristics of both or all, in the case of multiple interacting devices. Characteristics may include –Size –power consumption –hours/days between charging –UI capability –Bandwidth Month Year Tom Siep, CSRSlide 5

6 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Basic Use Case Methodology Goal Concise description of what the actor wants to accomplish –Time –UI –device constraints Month Year Tom Siep, CSRSlide 6

7 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Basic Use Case Methodology Scenario(s) Text description of user interaction with in a particular situation. There may be more than one scenario for each use case when the actor/devices/goal is the same, but the setting or other variable is significantly different. In our particular case time to complete transaction is important Month Year Tom Siep, CSRSlide 7

8 doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Example: Home Automation and Control Actor(s): Traveler near a Wi-Fi hotspot Device sets: Mobile Phone  Internet Access Point  Home Controller  Actuators; Sensor  Home Controller  Mobile Phone  Internet Access Point Goal: Ability to interact with home system from another device remotely and confirm action was taken Scenario(s): –User wants to access a controller that schedules activities based on energy costs / availability. Ability to monitor the temperature and ventilation available, together with external temperature, solar inputs and wind speeds to efficiently heat / cool a building to provide an efficient use of energy. This includes automatic control of windows / blinds / shutters to control ventilation / control of solar gain. Non-time critical, several minutes response time is adequate. –Appliance determines that room is much too hot and sends alarm to remote user with current user, who determines critical situation exists and calls emergency response authorities. Time critical, sub-second notification required. January 2011 Tom Siep, CSRSlide 8


Download ppt "Doc.: IEEE 802.11-yy/xxxxr0 Submission 11/0191r0 Month Year Tom Siep, CSRSlide 1 Use Case Discussion Date: 2011-01-20 Authors: 11-11-0191-00-00ai."

Similar presentations


Ads by Google