1 / 16

SYS366

SYS366. Week 6 - Lecture 1 Business Use Cases: How to Identify Them & How to document them. Today. Identifying Business Use Cases Documenting Business Use Cases. Business Use Cases.

billiek
Download Presentation

SYS366

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. SYS366 Week 6 - Lecture 1 Business Use Cases: How to Identify Them & How to document them

  2. Today • Identifying Business Use Cases • Documenting Business Use Cases

  3. Business Use Cases • “An abstract form of use case that is independent of the concrete possibilities and requirements for its (IT-related) implementation.”* • *Developing Software with UML: Object-Oriented Analysis and Design in Practice, Bernard Oestereich, p. 72.

  4. Business Use Cases • How to identify a Business Use Case? • Look for processes the company uses to satisfy the requests of the business actors • Processes could be an event that the business needs to respond to or it could be an event where the business needs to generate some kind of response back • Can include manual as well as automated processes

  5. Business Use Cases • Where does a Use case start? • “At the start there is always a commercial trigger, a commercial event • Customer would like to conclude a contract • Customer would like some information • Marketing department would like a statistical evaluation of reservations”* • *Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernard Oestereich, p. 74.

  6. Business Use Cases • Where does a Use case end? • “At the end a result has been produced that has “commercial value” • A vehicle registration • A letter to the customer • A business management evaluation”* • *Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernard Oestereich, p. 74.

  7. Business Use Cases • How to identify the Actors? • Look for who is placing requirements on the system. • Anybody who is directly or indirectly involved affected by the system. • Directly: someone who will have direct contact with the system • Indirectly: someone who does not have direct contact with the system but who is involved in the business that is supported by the system

  8. Business Use Cases • Example of Actors: • Users of the system • Other departments (Marketing, Sales) • Clients or Management • Customers • System Administrators, Service Personnel, Training Personnel, Support Personnel • System Developers, System Maintenance Personnel • Buyers of the system

  9. Business Use Cases • Narrative: A car rental company wants a new Information System to handle vehicle reservations, rentals, and billing. The new system will provide all functions directly related to handling customers. These include customer information, reservations, vehicle rental, and customer billing. Internal Accounting, Product Planning, Vehicle Transfer are not part of the system.

  10. Vehicle Rental • Use Case diagram

  11. Today • Identifying Business Use Cases • Documenting Business Use Cases

  12. Documenting Business Use Cases • To document a business use case, include the following: • Name • Short description • Actor(s) • Trigger • Result(s)

  13. Documenting Business Use Cases • A template is to be used to document a Business Use Case. • Format of the template: Business Use Case Name: The name this business use case has been given. Short Description: A brief description of what this business use case does. Actors: The names of the person or persons who use or are affected by this business use case. Trigger: What causes this business use case to start Results:What is the output of this business use case

  14. Documenting Business Use Cases • Example: Reserve Vehicle Business Use Case. * Business Use Case Name: Reserve Vehicle Short Description: A customer reserves a vehicle for a defined period. Actors: Customer, Call Centre Employee Trigger: A Customer would like to reserve a vehicle. Results: Vehicle Reservation, reservation confirmation. • *Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernard Oestereich, p. 73.

  15. Documenting Business Use Cases • Example: Complete Vehicle Rental Contract Business Use Case. * Business Use Case Name: Complete Vehicle Rental Contract Short Description: A reserved vehicle is handed over to a customer for his/her use. Actors: Customer, Rental agent, Vehicle Transfer Staff Trigger: A Customer would like to pick up a reserved vehicle. Results: Rental contract was completed, vehicle keys were handed over. • *Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernard Oestereich, p. 73.

  16. Prep for WP2 • Use Case Descriptions for your Business Use Cases

More Related