Use Case: 60 day advance reservation #2

New Issue

2022-02-21T13:46:05-05:00

yan-wah commented

2022-02-21 13:46:05 -05:00

(Migrated from github.com)

What is the feature/ request?

The requested feature is a reservation system where guests are able to make an advance reservation and pay the full cost of their stay within 30 days. The following are requirements of the prepaid system:

Prepaid rate is 85% of base rate
Reservations must be 60 days in advance or more
Valid payment collection window is 30 days from the date a guest filed a reservation
Reservation is cancelled if payment is not collected
Reservations that are payed cannot be cancelled
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
45 days before the scheduled stay, notifications must be sent to the registrant's email for payment collection (within 15 days)
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
Valid email is obtained

Scenario

Customer refers to guest in these scenarios

Payment is specified during registration

Customer visits registration system.
Customer selects 60 day advance reservation.
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.
Customer receives a receipt of their transaction.*

Customer chooses to wait to pay

Customer visits registration system.
Customer selects 60 day advance reservation option.
Customer inputs personal information first name and last name.
Customer does not input 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.
Customer receives a receipt of their transaction.*
Wait 15 days
Employee manually sends a notification to pay for the room.
Customer provides payment information.
Customer receives a receipt of their transaction.*

Customer request reservation change
See the reservation change scenario, after the initial details are collected, #1 . The two handle reservation changes the same way.

* 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 make an advance reservation and pay the full cost of their stay within 30 days. The following are requirements of the prepaid system: - Prepaid rate is 85% of base rate - Reservations must be 60 days in advance or more - Valid payment collection window is 30 days from the date a guest filed a reservation - Reservation is cancelled if payment is not collected - Reservations that are payed cannot be cancelled - 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 - 45 days before the scheduled stay, notifications must be sent to the registrant's email for payment collection (within 15 days) - 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 - Valid email is obtained # Scenario *Customer refers to guest in these scenarios* **Payment is specified during registration** 1. Customer visits registration system. 2. Customer selects 60 day advance reservation. 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. 6. Customer submits information. 7. Customer receives a receipt of their transaction.* **Customer chooses to wait to pay** 1. Customer visits registration system. 2. Customer selects 60 day advance reservation option. 3. Customer inputs personal information first name and last name. 4. Customer does not input 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. 6. Customer submits information. 7. Customer receives a receipt of their transaction.* 8. *Wait 15 days* 9. Employee manually sends a notification to pay for the room. 10. Customer provides payment information. 11. Customer receives a receipt of their transaction.* **Customer request reservation change** See the reservation change scenario, after the initial details are collected, #1 . The two handle reservation changes the same way. \* *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:23:17 -05:00

(Migrated from github.com)

Diagram

https://user-images.githubusercontent.com/48105815/155854724-77f39779-1b3a-40a9-af7e-fdbe36294714.png

# Diagram https://user-images.githubusercontent.com/48105815/155854724-77f39779-1b3a-40a9-af7e-fdbe36294714.png

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: yanwah/ophelias-oasis#2