### BERT, Group 50

### Use Case UC2: View Room Bookings

### Revision History: current version v2, v1

### Primary Actor: Employee

#### Stakeholders and interests:

- Employee: Wants to be able to view the current status of room bookings for a given date or date/time period. Alternatively, the employee wants to view what rooms are not yet booked for a given date or date/time period (ie. a room's availability). In either case, an employee wants the option to also find out about a room's configuration. After viewing the room booking information, the employee wants to easily access a room booking option, if he/she so desires.

Preconditions:

1. The employee has been successfully logged in to the Room Booking Subsystem
2. The room booking information is available for interrogation.

Success Guarantee (Post conditions):

1. Room booking information is displayed as per the employee's input criteria.

Main Success Scenario (or Basic Flow):

1. Employee indicates the date of the room booking they want to see.
2. Employee indicates the room number they want to see.
3. Employee indicates they want to view room bookings by current bookings.
4. Employee requests System to display the bookings.
5. System finds the the bookings based on the Employee's criteria.
6. System presents the room booking information to the Employee.
7. System provides employee with the option to make a room booking.
8. Employee takes the option to make a room booking or Exit system.
9. System directs the flow to Use Case UC3: Make Room Booking or terminates current Use Case.

Actor repeats steps 1-4 until indicates done.

Extensions (or Alternative Flows):

1a.System does not recognise date as valid value

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

2a. System does not recognise the room number as a valid value.

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

3a. Employee wants to view the room booking system via the room(s) availability.

1. Employee indicates they want to view via a room(s) available time slots.
2. Use Case continues from Main Success Scenario step 4.

5a. Retrieval error.

1. System indicates that the requested information cannot be retrieved.
2. Use Case continues from Main Success Scenario step 1, or employee exits Use Case.

9a. Redirection Error

1. System signals error that it cannot redirect Employee to Use Case UC3: Make Room Booking.
2. Employee exits current Use Case.

Special Requirements:

-

Technology and Data Variations List:

n/a

#### Frequency of Occurrence:

Occurrence on an ad-hoc basis.

#### Open Issues:

-