system analysis and design

Draw a Collaboration diagram for the Written Use Case description of a Hotel Room Reservation process, as provided below:

Use Case Title: Hotel Room Reservation Primary Actor: Customer Level: Kite (high, general) Stakeholders: Customer, Reservation Clerk Preconditions: Customer pays with credit card Minimal Guarantee: Customer able to request a room Success Guarantee: Customer will secure a reservation for a room

Main Success scenario:

1) Customer requests a room reservation for a specific date.

2) Hotel clerk checks room availability on specified date.

3) Clerk confirms room availability on specific date.

4) Customer requests relevant discount (AAA, corporate rate, etc.).

5) Clerk checks availability of discounts on date requested.

6) Best available room rate is found.

7) Total amount due, including taxes, is calculated.

8) Clerk informs customer of amount due (displays the total costs).

9) Customer confirms reservation of the room and Clerk books the room.

10) Availability of the room on the specified date is adjusted.

11) Charge of a one-day's rate on customer's card is applied as a deposit.

12) Clerk issues (displays) a reservation confirmation number to the customer.

Extensions:

3a) Rooms not available on specified date - customer tries another hotel.

12a) Credit card will not accept charge - reservation cancelled.

Hint:

Use only the Main Success scenario to draw the diagram. The Customer Actor interacts with the system through a ReservationClerk boundary object. Also, consider one Control object for this Use case (e.g. Hotel Control), and two entity objects (HotelRooms, containing data for room availability, and CustomerCreditCard, containing customer credit data). Consider all calculations to be performed by the Control class on itself, as well as finding best room rate(discount).