1. Lecture 4 Business Use Cases: How to document them 1 SYS366

2. Business Use Cases 2 “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.

3. Business Use Cases 3 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

4. Business Use Cases 4 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.

5. Business Use Cases 5 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.

6. Business Use Cases 6 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

7. Business Use Cases 7 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

8. Business Use Cases 8 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.

9. Documenting Business Use Cases 9 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

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

11. Documenting Business Use Cases 11 Example: Reserve Vehicle Business Use Case. * Business Use Case Name: Reserve Vehicle Short Description: This use case enables a call centre employee to reserve a vehicle for a defined period at a customer’s request. 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.

12. Documenting Business Use Cases 12 Example: Create Vehicle Rental Contract Business Use Case. * Business Use Case Name: Create Vehicle Rental Contract Short Description: This use case enables the actor, a rental agent, to create a contract for a vehicle which had been reserved. Actors: Customer, Rental agent Trigger:A Customer would like to pick up a reserved vehicle. Results:Rental contract was completed. * Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernard Oestereich, p. 73.