The requested feature is a reservation system where guests are able to pay at the end of their stay. The following are requirements of the prepaid system:
Payment is collected at the end of the stay
Reservations can be made whenever
They are charged for the first day if there are "no shows" or cancel less than 3 days before the start of their stay
Changes are permitted (subject to availability)
Receipt must be generated
Who will use this system (primary actor)?
Guests
Preconditions
Nightly rate is configured
Available rooms must be checked
Credit card number/ payment information is provided
Scenario
Customer refers to guest in these scenarios
Customer is not a no-show/ cancellation
Customer visits registration system.
Customer selects conventional 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.
Customer receives a receipt of their transaction.*
Customer arrives on-time and stays for their reservation duration.
Customer is charged after their stay.
Customer is not a no-show
Customer visits registration system.
Customer selects conventional 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.
Customer receives a receipt of their transaction.*
Customer does not arrive on their reservation start date.
Customer is charged on the start of their start date.
Customer is not a cancellation
Customer visits registration system.
Customer selects conventional 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.
Customer receives a receipt of their transaction.*
Customer cancels within 3 days of their stay.
Customer is charged at the time of cancellation.
* Might not need this per the original specification, needs revision/ review.
** Optional
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 at the end of their stay. The following are requirements of the prepaid system:
- Payment is collected at the end of the stay
- Reservations can be made whenever
- They are charged for the first day if there are "no shows" or cancel less than 3 days before the start of their stay
- Changes are permitted (subject to availability)
- Receipt must be generated
# Who will use this system (primary actor)?
Guests
# Preconditions
- Nightly rate is configured
- Available rooms must be checked
- Credit card number/ payment information is provided
# Scenario
*Customer refers to guest in these scenarios*
**Customer is not a no-show/ cancellation**
1. Customer visits registration system.
2. Customer selects conventional 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. Customer receives a receipt of their transaction.*
6. Customer arrives on-time and stays for their reservation duration.
7. Customer is charged after their stay.
**Customer is not a no-show**
1. Customer visits registration system.
2. Customer selects conventional 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. Customer receives a receipt of their transaction.*
6. Customer does not arrive on their reservation start date.
7. Customer is charged on the start of their start date.
**Customer is not a cancellation**
1. Customer visits registration system.
2. Customer selects conventional 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. Customer receives a receipt of their transaction.*
6. Customer cancels within 3 days of their stay.
7. Customer is charged at the time of cancellation.
\* *Might not need this per the original specification, needs revision/ review.*
\** *Optional*
# 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?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What is the feature/ request?
The requested feature is a reservation system where guests are able to pay at the end of their stay. The following are requirements of the prepaid system:
Who will use this system (primary actor)?
Guests
Preconditions
Scenario
Customer refers to guest in these scenarios
Customer is not a no-show/ cancellation
Customer is not a no-show
Customer is not a cancellation
* Might not need this per the original specification, needs revision/ review.
** Optional
Exceptions/ Restrictions
Concerns
Diagram
https://user-images.githubusercontent.com/48105815/155854442-d5d8dfca-9adf-4c7f-a947-215e528569bc.png