Of course, let's tackle the first milestone, which entails requirements analysis.
Analysis of Requirements
1. *Identify * Important Stakeholders and End-Users:
- Peter Selleck (the owner), the reservation staff, and visitors may be considered key stakeholders for
the AHS reservation system.
- The end users who will interface with the system are mostly the reservation personnel.
Determine functional requirements and record use cases.
The first use case is to create a new reservation.
- Actors: Users that work in reservations
This use case illustrates the procedure for making a new reservation for a visitor.
- Key Actions:
1. A staff member accesses the computer.
2. A staff person enters visitor information.
3. A staff employee inputs the arrival and departure dates.
4. A member of staff details the number of rooms, adults, kids, newborns, and any discount codes.
5. The reservation is saved by the system, and a confirmation is given.
*Use Case 2*: Update an Existing Reservation
This use case illustrates the procedure for modifying an existing reservation. - Actors: Reservation
staff (user).
- Key Actions:
1. A staff member accesses the computer.
2. A member of the staff looks up the visitor's previous reservation.
3. A staff member makes the necessary changes to the reservation, such as adding or removing
rooms or altering the dates.
4. After updating the reservation, the system saves it and issues a confirmation.
c. "Use Case 3: Cancellation of Reservation"
- Actors: Users that work in reservations
This use case illustrates the procedure for cancelling a reservation.
- Key Actions:
1. A staff member accesses the computer.
2. A member of the staff looks up the visitor's previous reservation.
3. An employee starts the cancelling procedure.
4. The system updates the reservation status and confirms the cancellation.
d. **Use Case 4: Creation of a Guest Account**
- Actors: New guest and reservation staff (user).
This use case illustrates the procedure for setting up a guest account for a brand-new visitor.
- Key Actions:
1. A staff member accesses the computer.
2. A staff person checks to see if the visitor is new.
3. If the visitor is a new one, the staff member takes down their contact and payment information.
4. A fresh visitor account is made by the system.
f. **Use Case 5: Update to Guest Account**
- Actors: Returning visitor, reservation staff (user).
This use case illustrates the procedure for updating a guest's information when they return.
- Key Actions:
1. A staff member accesses the computer.
2. A member of staff looks up the returning visitor's account.
3. An employee updates any pertinent information about a guest.
4. The revised data is saved by the system.
3. Include the following presumptions that were developed during the requirements analysis phase:
- Every reservation is done over the phone.
- A total of 18 rooms can be accommodated by the system.
- Employees have access to and control over reservations.
- For new visitors, credit card information is necessary.
- The system will offer confirmations for both reservations and cancellations.
These use cases and assumptions can serve as a foundation for the system's functional requirements.
With this information, you may create a strong foundation for the design and development of the
system in the subsequent milestone.
