Consider an hotel management system. The client accesses the system through the internet, and can book an hotel room, by choosing both check-in and check-out dates. The dates availability are verified and the reservation is confirmed and stored, if the selected dates are available. When booking a room in that hotel, the client needs to provide his/hers personal details.
Software engineers created a use case describing the previous scenario (presented on the right side of the screen). However, after a management meeting, a new scenario appeared:
At check-out, the system calculates the amount to be payed by the client. The payment can be made by using a debit or a credit card. When using a credit card, the client has to pay an extra fee.
Please change the use case describing this scenario (on the right), by using the following template:
Name: use case name
Brief description: executive summary
Actors: actors participating in the use case
Primary: actor initiating the use case
Secondary: actor(s) participating in the use case, but not starting it
Pre-conditions: prerequisites for a successful execution of the use case
Main flow: atomic steps of the use case
Post-conditions: system state, after a successful execution of the use case
Alternative flows: deviations from the main flow