Name Brief Description Actor(s) Flow of Events Basic Flow

Create Account The Create Account use case allows the User to create a login and become a Registered User. Guest

This use case starts when the User accesses the system feature that enables him/her to create an account by entering information that is maintained in the Users account.

1. 2. 3.
4.

The User enters the required User Account information values and requests that the system saves the entered values. The system validates the entered User Account information. The values for the User Account information are stored in the Users account. The system notifies the User that the account has been created. The use case ends

Alternate Flows Title User Cancels Request Description At any time, the User may choose to cancel the account creation. At which point, the processing is discontinued, the user account remains unchanged, and the user is notified that the account management request has been cancelled. If during Create Account, the system determines that the User entered invalid User Account information, the following occurs: 1. 2. 3. 4. 5. The system describes which entered data was invalid and presents the User with suggestions for entering valid data. The system prompts the User to re-enter the invalid information. The User re-enters the information and the system re-validates it. If valid information is entered, the User Account Information is stored. If invalid information is entered, the Entered Information is Invalid alternative flow is executed again. This continues until the User enters valid information, or chooses Cancel (see the User Cancels Account Management Request alternative flow). Missing information items Username already exists in the system User Account information entered does not comply to its definition in the glossary or in the system form flow. Not well formed e-mail address Wrong words in any part of the User Account information

User Enters Invalid User Account Information

Invalid User Account information: -

Pre-Conditions Title None Post-Conditions Title Success

Description

Description The User entered data is stored in the user account. Confirmation is generated of success creation of account through message dialog box information that will appear on screen. The User entered invalid data or chose to cancel the account creation request. In either case, no account will be created.

The user account was not created Extension Points None

Name Brief Description Actor(s) Flow of Events Basic Flow

Log In A user of the System logs in to the System User / Cashier /Administrator

This use case starts when the User accesses the log in feature of the system. 1. 2. 3. The system prompts the User for his/her username and password. The User enters his/her username and password. The system validates the entered information, making sure that the entered username and password are valid for one user account in the system, and that the required password is entered for the entered username. The User is signed in. The system displays a message indicating that the user is signed in. The use case ends.

4. 5.

Alternate Flows Title New User Description If the User does not have an account, the System will give the User the opportunity to create an account. See the Create Account use case. Once the account is created, the User is considered log in. If the User forgot his/her user name or password, the System will prompt the user to answer his/her security question provided in the Create Account stage. Provided that it is answered correctly, the user name and password are emailed to the email address provided when the account was created. If the User entered an invalid username and/or password, the following occurs: 1. 2. 3. 4. Pre-Conditions Title None Post-Conditions Title Success User not signed in Description The User is authenticated and the system displays all features available for the role the user is associated with as defined in his/her user account. This can occur because the User repeatedly entered invalid sign in information. The User has been notified of the reason why he/she was not signed in. The User is not authenticated and remains in the Anonymous User role. Description The system describes the reasons why the User failed authentication through message dialog box. The system presents the User with suggestions for changes necessary to allow the User to pass authentication. The system prompts the User to re-enter the valid information. The Basic Flow continues where the User enters new information.

User Forgot User Name/Password User Fails Authentication

Extension Points None

Name Brief Description Actor(s) Flow of Events Basic Flow

Log In A user of the System logs in to the System User / Cashier /Administrator

This use case starts when the User accesses the log in feature of the system. 5. 6. 7. The system prompts the User for his/her username and password. The User enters his/her username and password. The system validates the entered information, making sure that the entered username and password are valid for one user account in the system, and that the required password is entered for the entered username. The User is signed in. The system displays a message indicating that the user is signed in. The use case ends.

8. 6.

Alternate Flows Title New User Description If the User does not have an account, the System will give the User the opportunity to create an account. See the Create Account use case. Once the account is created, the User is considered log in. If the User forgot his/her user name or password, the System will prompt the user to answer his/her security question provided in the Create Account stage. Provided that it is answered correctly, the user name and password are emailed to the email address provided when the account was created. If the User entered an invalid username and/or password, the following occurs: 5. 6. 7. 8. Pre-Conditions Title None Post-Conditions Title Success User not signed in Description The User is authenticated and the system displays all features available for the role the user is associated with as defined in his/her user account. This can occur because the User repeatedly entered invalid sign in information. The User has been notified of the reason why he/she was not signed in. The User is not authenticated and remains in the Anonymous User role. Description The system describes the reasons why the User failed authentication through message dialog box. The system presents the User with suggestions for changes necessary to allow the User to pass authentication. The system prompts the User to re-enter the valid information. The Basic Flow continues where the User enters new information.

User Forgot User Name/Password User Fails Authentication

Extension Points None

Use Case Name: Actor(s): Description:

Search an item of products and materials Cashier This use case describes the process on how the actor search an item of products and materials Actor Action Step 1: This use case begin when actor search for an item of products and materials System Response Step 2: The system will retrieve the record

Typical Course of Events:

Step 4: this use case ends when the customer verified his record

Alternate Courses Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

Update reservation receptionist This use case describes how the process of updating the reservation

Typical Course of Events:

Actor Action Step 1: This use case begin when actor retrieve the reservation

System Response Step 2: The system will retrieve the record

Step 3: this use case ends when the actor update the reservation

Alternate Courses Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

List of available room receptionist This use case describes the process retrieving the list of available room

Typical Course of Events:

Actor Action Step 1: This use case starts when the actor retrieve the available room

System Response Step 2: The system will retrieve the record

Step 4: this use case ends when actor view the list of available room

Alternate Courses Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

List of room receptionist This use case describes the process retrieving the list of room

Typical Course of Events:

Actor Action Step 1: This use case starts when the actor retrieve the list of room

System Response Step 2: The system will retrieve the record

Step 4: this use case ends when actor view the list of room

Alternate Courses Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

Add customer reservation receptionist This use case describes the process of customer reservation

Typical Course of Events:

Actor Action Step 1: This use case starts when the actor ask the customers reservation info such as expected date of check in name and number of days

System Response Step 2: The system will save the records Step 3: the system will verify the reservation

Step 4: this use case ends when the customer verified the reservation

Alternate Courses Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

Add customer record receptionist This use case describes the adding of customers record

Typical Course of Events:

Actor Action Step 1: This use case begins actor add the the customers reservation such as address, name, date check in. Date check out, number of days

System Response Step 2: The system will save the given information

Step 3: this usecase ends when the customer verify the record

Alternate Courses

Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

Create new account for receptionist administrator This use case describes the process of how to create new account

Typical Course of Events:

Actor Action Step 1: This use case begins when the actor create an account for receptionist such as name, type and user number

System Response Step 2: The system will save the account Step 3: the system will verify the account

Step 3: this usecase ends when the actor verified the account

Alternate Courses Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

Add reserve room receptionist This use case describes the process of adding reserve room

Typical Course of Events:

Actor Action Step 1: This use case starts when the actor add reserve room

System Response Step 2: The system will verify the room

Step 3: the customer will verify the room reservation

Step 4: this use case ends when the system save the room reservation

Alternate Courses Pre-condition: Post-condition:

Use Case Name: Actor(s): Description:

View available rooms customer This use case describes the process viewing available room

Typical Course of Events:

Actor Action Step 1: This use case starts when the actor ask for available room

System Response Step 2: The system will retrieve the list of available room Step 3: the system will display the available room

Step 4: this use case ends when the actor view the available room

Alternate Courses Pre-condition: Post-condition: