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: the name should be the goal as a short active verb phrase
Context of use: a longer statement of the goal, if needed, its normal occurrence condition
Scope: design scope, what system is being considered black-box under design
Level: one of: strategic, user goal, sub-function
Primary actor: a role name for the primary actor, or description
Stakeholders & interests: list of stakeholders and key interests in the use case
Pre-condition: what we expect is already the state of the world
Success end condition: the state of the world upon successful completion
Failed end protection: the state of the world if goal abandoned
Trigger: what starts the use case, may be time event
Main success scenario: lists the steps of the scenario from trigger to goal deliver
Variations: the variations that will cause eventual bifurcation in the scenario