1 / 19

BTS330

BTS330. Understanding User Requirements. Requirements. Steps: Define vision/scope Identify users/stakeholders Identify use cases Understand what interaction is happening with the system Identify business rules. Use Case Modeling. Actor

marly
Download Presentation

BTS330

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. BTS330 Understanding User Requirements

  2. Requirements • Steps: • Define vision/scope • Identify users/stakeholders • Identify use cases • Understand what interaction is happening with the system • Identify business rules

  3. Use Case Modeling • Actor • Represent anything outside the system that uses the system to do something • From your stakeholder list, identify those ‘stakeholders’ that will actually use the system  those are the actors

  4. Use Case Modeling • Actor • Give them a name – use a name that describes the role that the actor plays in relation to the system • i.e. Fitness Instructor, member, manager • Really a role that a person (or system, or device) plays when using the system • Give the actor a brief description

  5. Use Case Modeling • Fitness Instructor • Instructs fitness classes • Member • Uses the club’s facilities and services • manager • Is responsible for overseeing the operation of the club and managing the employees

  6. Use Case Modeling • Actor Tip: • Every system requires an actor to start the system and to shut it down  the actor is anything outside the system that exchanges information with the system • Every system requires some sort of maintenance to be done • i.e. backup – actor is ‘system clock’

  7. Use Case Modeling • Actor • A person, software system, department, role, device…etc…. outside of the system that interacts with the system Actor System Actor Actor

  8. Use Case Modeling • Use cases: • Express the behaviour of the system that produce a measurable result of value to an actor • Describe the things actors want the system to do • i.e. query the status of an order • How do the users use the system? • Each major system ‘usage’ is a use case • i.e. Process A Membership, Manage Fitness Classes, Maintain Employee

  9. Use Case Modeling • Use case: • A sequence of interactions between a system and an external actor • Accomplishes a ‘useful’ goal; something of value to the user

  10. Use Case Modeling • Actors communicate with the system to: • Start a use case • Ask for some data stored in the system which the use case presents to the actor • Change data stored in the system by means of a dialog with the system (request some data, change it and save it)

  11. Use Case Modeling • Use cases communicate with the actor to: • Report that something special has happened in the system that the actor should be aware of • Ask an actor for help in making a decision needed to achieve a goal • Delegate responsibility to an actor

  12. Use Case Modeling • Identifying use cases • For each actor list the interaction they must have with the system • The interaction should be a ‘goal’ that the actor wants to accomplish by using the system • Name the interaction  use a verb to name the interaction • i.e. Schedule A Class, Process A Membership

  13. Use Case Modeling • Use cases are usually completed in a short period of time • If parts of the use case are widely separated in time and performed by different actors, then those parts are probably better as separate use cases

  14. Use Case Modeling • Identifying use cases tips: • What functions will the actor want from the system? • Does the system store information? What actors will create, read, update, or delete that information? • Does the system need to notify an actor about changes in its internal state? • Are there any external events that the system must know about? What actor informs the system about those events?

  15. Use Case Modeling • Identifying use cases • Every system starts from a vision • Vision can tell us the key features required of the system, possible constraints and who the stakeholders might be

  16. In-class Exercise • Jim’s Gym • For Jim’s Gym who needs to acquire an automated computer system to run his new business, the Gym Management System is an information system that will provide a single point of access to manage his gym. The system will provide the capability to manage all aspects of Jim’s business such as managing members and fitness staff, schedule employees and fitness classes as well as a gift shop. There will also be services such as massage therapy and private and semi-private instruction with a fitness instructor offered. Unlike the competition, our product will allow members to manage their experience at Jim’s gym through an interactive web interface where customers can sign up for classes and services that the gym will be offering.

  17. In-Class Exercise • From the vision statement: • Stakeholders: • Jim • Fitness instructors • Use Cases: • Manage Members • Manage Staff • Schedule Employees • Schedule Classes • Gift Shop • Massage Therapy • Private, semi-private instruction • Sign up for classes

  18. In-Class Exercise • Which of these will an actor need to interact with the system? • Which of these will require further analysis to determine who the actors need to be and what interaction they need to have with the system? • Manage Members • Manage Staff • Schedule Employees • Schedule Classes • Gift Shop • Massage Therapy • Private, semi-private instruction • Sign up for classes

  19. In-Class Exercise • For your business, start with your vision statement • Identify who the stakeholders are • Identify the use cases by listing the interaction the actor needs to have with the system (you might be able to identify some of the interaction from your vision statement)

More Related