1 / 8

Use Case Discussion

Use Case Discussion. Authors:. Date: 2011-01-20. 11-11-0191-00-01ai. Abstract. Materials to facilitate the discussions of Use Cases as a methodology to derive requirements. . Actor(s) Device sets Goal Scenario(s). Basic Use Case Methodology.

teddy
Download Presentation

Use Case Discussion

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Use Case Discussion Authors: Date:2011-01-20 11-11-0191-00-01ai Tom Siep, CSR

  2. Abstract Materials to facilitate the discussions of Use Cases as a methodology to derive requirements. Tom Siep, CSR

  3. Actor(s) Device sets Goal Scenario(s) Basic Use Case Methodology Tom Siep, CSR

  4. Unique characteristics of operator, if any, of: • Initiator device • Target device operator, if any. • If more than one person, important factors: • Describe the relationship between the two people. • Level of trust • Previous history Basic Use Case MethodologyActor(s) Tom Siep, CSR

  5. 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 • User Interface capability • Bandwidth Basic Use Case MethodologyDevice sets Tom Siep, CSR

  6. Concise description of what the actor wants to accomplish • Time • User Inerface • device constraints Basic Use Case MethodologyGoal Tom Siep, CSR

  7. January 2011 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 Basic Use Case MethodologyScenario(s) Tom Siep, CSR

  8. Actor(s): Traveler near a Wi-Fi hotspot • Device sets: Mobile Phone Internet Access Point  Home Controller  Actuators; Sensor Home Controller  Internet Access Point Mobile Phone • 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. Example: Home Automation and Control Tom Siep, CSR

More Related