Use case: Prepaid reservation system #1

New Issue

2022-02-21T13:32:10-05:00

yan-wah commented

2022-02-21 13:32:10 -05:00

(Migrated from github.com)

What is the feature/ request?

The requested feature is a reservation system where guests are able to pay the full cost of their stay at the time of reservation. The following are requirements of the prepaid system:

Prepaid rate is 75% of base rate
Reservations must be 90 days in advance or more
No refund if prepaid is cancelled
Prepaid reservations can be changed at an additional cost of 110% of current base rate for changed reservation
No refund is paid if the changed reservation cost is less than the original reservation cost
Receipt must be generated

Who will use this system (primary actor)?

Guests
Employees (Secondary actor)

Preconditions

Nightly rate is configured
Available rooms must be checked
Reservation is made 90 days before stay or longer

Scenario

Customer refers to guest in these scenarios

Customer prepays their stay

Customer visits registration system.
Customer selects prepaid reservation option.
Customer inputs personal information first name and last name.
Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date.
Customer inputs contact information such as email address, and phone number.
Customer submits information.
Payment is collected.
Customer receives a receipt of their transaction.*

Customer cancels their stay

Customer visits registration system.
Customer selects prepaid reservation option.
Customer inputs personal information first name and last name.
Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date.
Customer inputs contact information such as email address, and phone number.
Customer submits information.
Payment is collected.
Customer receives a receipt of their transaction.*
Customer cancels.

Customer requests reservation change for a higher price (assuming availability)

Customer visits registration system.
Customer selects prepaid reservation option.
Customer inputs personal information first name and last name.
Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date.
Customer inputs contact information such as email address, and phone number.
Customer submits information.
Payment is collected.
Customer receives a receipt of their transaction.*
Customer requests change.
Employee checks if there is availability to change.
Employee makes change.
Customer pays the 110% of the difference in cost.
Payment is collected.
Customer receives a receipt of their transaction.*

Customer requests reservation change for a lower price (assuming availability)

Customer visits registration system.
Customer selects prepaid reservation option.
Customer inputs personal information first name and last name.
Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date.
Customer inputs contact information such as email address, and phone number.
Customer submits information.
Payment is collected.
Customer receives a receipt of their transaction.*
Customer requests change.
Employee checks if there is availability to change.
Employee makes change.

* Might not need this per the original specification, needs revision/ review.

Exceptions/ Restrictions

Guests may not reserve specific rooms.
Rooms are available (occupancy is not maxed)

Concerns

What measures exist to prevent fraudulent use?
What happens if someone reserves under different reservation systems?

# What is the feature/ request? The requested feature is a reservation system where guests are able to pay the full cost of their stay at the time of reservation. The following are requirements of the prepaid system: - Prepaid rate is 75% of base rate - Reservations must be 90 days in advance or more - No refund if prepaid is cancelled - Prepaid reservations can be changed at an additional cost of 110% of current base rate for changed reservation - No refund is paid if the changed reservation cost is less than the original reservation cost - Receipt must be generated # Who will use this system (primary actor)? - Guests - Employees (Secondary actor) # Preconditions - Nightly rate is configured - Available rooms must be checked - Reservation is made 90 days before stay or longer # Scenario *Customer refers to guest in these scenarios* **Customer prepays their stay** 1. Customer visits registration system. 2. Customer selects prepaid reservation option. 3. Customer inputs personal information first name and last name. 4. Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date. 5. Customer inputs contact information such as email address, and phone number. 4. Customer submits information. 5. Payment is collected. 6. Customer receives a receipt of their transaction.* **Customer cancels their stay** 1. Customer visits registration system. 2. Customer selects prepaid reservation option. 3. Customer inputs personal information first name and last name. 4. Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date. 5. Customer inputs contact information such as email address, and phone number. 4. Customer submits information. 5. Payment is collected. 6. Customer receives a receipt of their transaction.* 7. Customer cancels. **Customer requests reservation change for a higher price (assuming availability)** 1. Customer visits registration system. 2. Customer selects prepaid reservation option. 3. Customer inputs personal information first name and last name. 4. Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date. 5. Customer inputs contact information such as email address, and phone number. 4. Customer submits information. 5. Payment is collected. 6. Customer receives a receipt of their transaction.* 7. Customer requests change. 7. Employee checks if there is availability to change. 8. Employee makes change. 8. Customer pays the 110% of the difference in cost. 9. Payment is collected. 10. Customer receives a receipt of their transaction.* **Customer requests reservation change for a lower price (assuming availability)** 1. Customer visits registration system. 2. Customer selects prepaid reservation option. 3. Customer inputs personal information first name and last name. 4. Customer inputs payment information consisting of credit card number, CCV/ CVC, and credit card expiration date. 5. Customer inputs contact information such as email address, and phone number. 4. Customer submits information. 5. Payment is collected. 6. Customer receives a receipt of their transaction.* 7. Customer requests change. 7. Employee checks if there is availability to change. 8. Employee makes change. \* *Might not need this per the original specification, needs revision/ review.* # Exceptions/ Restrictions - Guests may not reserve specific rooms. - Rooms are available (occupancy is not maxed) # Concerns - What measures exist to prevent fraudulent use? - What happens if someone reserves under different reservation systems?

PrograMeiji commented

2022-02-26 13:27:29 -05:00

(Migrated from github.com)

Diagram

https://user-images.githubusercontent.com/48105815/155854826-38bb70e2-881a-4703-9ad0-1d9602d074e4.png

# Diagram https://user-images.githubusercontent.com/48105815/155854826-38bb70e2-881a-4703-9ad0-1d9602d074e4.png

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: yanwah/ophelias-oasis#1