### BERT, Group 50

### Use Case UC4: Cancel Room Bookings

### Revision History: current version v2, v1

### Primary Actor: Employee

#### Stakeholders and interests:

- Employee: Wants to be able to be able to cancel an existing room booking. Wants the booking to be removed from persistent storage.

Preconditions:

1. The employee has been successfully logged in to the Room Booking Subsystem.
2. Employee has indicated to system that Cancel Booking is required.
3. The room booking information is available for interrogation and modification.

Success Guarantee (Post conditions):

1. A Room booking entry is removed from persistent storage.

Main Success Scenario (or Basic Flow):

1. Employee enters in his/her employee identification code.
2. System find all bookings held by the employee.
3. System presents all bookings held by the employee to the employee.
4. Employee chooses which booking is to be deleted.
5. System presents a cancellation confirmation message to the employee.
6. Employee submits cancellation request to system.
7. System removes the booking from persistent storage.
8. System presents employees current list of bookings (minus the cancelled booking).
9. Employee exits Use Case.

Actor repeats steps 4 until indicates done.

Extensions (or Alternative Flows):

1a.System does not recognise employee identification as a valid value

1. System signals error.
2. Employee re-enters identification information.

2a. Retrieval error.

1. System signals error.
2. Employee re-enters identification number or Exit Use Case.
3. Use Case continues from Main Success Scenario step 3.

7a. Cancellation Error

1. System signals error that it cannot cancel room booking.
2. Employee restarts Use Case from Main Success Scenario step 1 or exits current Use Case.

Special Requirements:

-

Technology and Data Variations List:

n/a

#### Frequency of Occurrence:

Occurrence on an ad-hoc basis.

#### Open Issues:

-