7/29/2019 Ims Usecase

1/12

Name Create Account

Brief Description The Create Account use case allows the User to create a login and become aRegistered User.

Actor(s) Guest

Flow of Events

Basic Flow

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

1. The User enters the required User Accountinformation values and requests that the system saves theentered values.

2. The system validates the entered User Accountinformation.

3. The values for the User Accountinformation are stored in the Users account. The system notifies theUser that the account has been created.

4. The use case ends

Alternate Flows

Title Description

User Cancels Request At any time, the User may choose to cancel the account creation. At whichpoint, the processing is discontinued, the user account remains unchanged,and the user is notified that the account management request has beencancelled.

User Enters Invalid UserAccount Information

If during Create Account, the system determines that the User entered invalidUser Accountinformation, the following occurs:

1. The system describes which entered data was invalid and presentsthe User with suggestions for entering valid data.

2. The system prompts the User to re-enter the invalid information.

3. The User re-enters the information and the system re-validates it.

4. If valid information is entered, the User Account Information is stored.

5. If invalid information is entered, the Entered Information is Invalidalternative flow is executed again. This continues until the Userenters valid information, or chooses Cancel (see the User CancelsAccount Management Request alternative flow).

Invalid User Accountinformation:

- Missing information items

- Username already exists in the system

- User Accountinformation entered does not comply to its definition inthe glossary or in the system form flow.

- Not well formed e-mail address

- Wrong words in any part of the User Accountinformation

Pre-Conditions

Title Description

None

Post-Conditions

Title Description

Success The User entered data is stored in the user account. Confirmation is generatedof success creation of account through message dialog box information thatwill appear on screen.

The user account was notcreated

The User entered invalid data or chose to cancel the account creation request.In either case, no account will be created.

Extension Points

None

7/29/2019 Ims Usecase

2/12

Name Log In

Brief Description A user of the System logs in to the System

Actor(s) User / Cashier /Administrator

Flow of Events

Basic Flow

This use case starts when the User accesses the log in feature of the system.

1. The system prompts the User for his/her username and password.

2. The User enters his/her username and password.

3. The system validates the entered information, making sure that the entered username and passwordare valid for one user account in the system, and that the required password is entered for the enteredusername.

4. The User is signed in. The system displays a message indicating that the user is signed in.

5. The use case ends.

Alternate Flows

Title Description

New User If the User does not have an account, the System will give the User theopportunity to create an account. See the Create Account use case. Oncethe account is created, the User is considered log in.

User Forgot UserName/Password

If the User forgot his/her user name or password, the System will prompt theuser to answer his/her security question provided in the Create Account stage.Provided that it is answered correctly, the user name and password areemailed to the email address provided when the account was created.

User Fails Authentication If the User entered an invalid username and/or password, the following occurs:

1. The system describes the reasons why the User failed authenticationthrough message dialog box.

2. The system presents the User with suggestions for changes necessaryto allow the User to pass authentication.

3. The system prompts the User to re-enter the valid information.4. The Basic Flow continues where the User enters new information.

Pre-Conditions

Title Description

None

Post-Conditions

Title Description

Success The User is authenticated and the system displays all features available for therole the user is associated with as defined in his/her user account.

User not signed in 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.Extension Points

None

7/29/2019 Ims Usecase

3/12

Name Log In

Brief Description A user of the System logs in to the System

Actor(s) User / Cashier /Administrator

Flow of Events

Basic Flow

This use case starts when the User accesses the log in feature of the system.

5. The system prompts the User for his/her username and password.

6. The User enters his/her username and password.

7. The system validates the entered information, making sure that the entered username and passwordare valid for one user account in the system, and that the required password is entered for the enteredusername.

8. The User is signed in. The system displays a message indicating that the user is signed in.

6. The use case ends.

Alternate Flows

Title Description

New User If the User does not have an account, the System will give the User theopportunity to create an account. See the Create Account use case. Oncethe account is created, the User is considered log in.

User Forgot UserName/Password

If the User forgot his/her user name or password, the System will prompt theuser to answer his/her security question provided in the Create Account stage.Provided that it is answered correctly, the user name and password areemailed to the email address provided when the account was created.

User Fails Authentication If the User entered an invalid username and/or password, the following occurs:

5. The system describes the reasons why the User failed authenticationthrough message dialog box.

6. The system presents the User with suggestions for changes necessaryto allow the User to pass authentication.

7. The system prompts the User to re-enter the valid information.8. The Basic Flow continues where the User enters new information.

Pre-Conditions

Title Description

None

Post-Conditions

Title Description

Success The User is authenticated and the system displays all features available for therole the user is associated with as defined in his/her user account.

User not signed in 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.Extension Points

None

7/29/2019 Ims Usecase

4/12

Use Case Name: Search an item of products and materials

Actor(s): Cashier

Description: This use case describes the process on how the actor search an item ofproducts and materials

Typical Course of Events: Actor Action

Step 1: This use case begin whenactor search for an item of productsand materials

Step4: this use case ends when thecustomer verified his record

System Response

Step2: The system will retrieve therecord

Alternate Courses

Pre-condition:

Post-condition:

Use Case Name: Update reservation

Actor(s): receptionist

Description: This use case describes how the process of updating the reservation

7/29/2019 Ims Usecase

5/12

Typical Course of Events: Actor Action

Step 1: This use case begin whenactor retrieve the reservation

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

System Response

Step2: The system will retrieve therecord

Alternate Courses

Pre-condition:Post-condition:

7/29/2019 Ims Usecase

6/12

Use Case Name: List of available room

Actor(s): receptionist

Description: This use case describes the process retrieving the list of available room

Typical Course of Events: Actor Action

Step 1: This use case starts whenthe actor retrieve the available room

Step4: this use case ends whenactor view the list of available room

System Response

Step2: The system will retrieve therecord

Alternate Courses

Pre-condition:Post-condition:

7/29/2019 Ims Usecase

7/12

Use Case Name: List of room

Actor(s): receptionist

Description: This use case describes the process retrieving the list of room

Typical Course of Events: Actor Action

Step 1: This use case starts whenthe actor retrieve the list of room

Step4: this use case ends whenactor view the list of room

System Response

Step2: The system will retrieve therecord

Alternate Courses

Pre-condition:

Post-condition:

7/29/2019 Ims Usecase

8/12

Use Case Name: Add customer reservation

Actor(s): receptionist

Description: This use case describes the process of customer reservation

Typical Course of Events: Actor Action

Step 1: This use case starts whenthe actor ask the customersreservation info such as expecteddate of check in name and numberof days

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

System Response

Step2: The system will save therecords

Step 3: the system will verify thereservation

Alternate Courses

Pre-condition:Post-condition:

7/29/2019 Ims Usecase

9/12

Use Case Name: Add customer record

Actor(s): receptionist

Description: This use case describes the adding of customers record

Typical Course of Events: Actor Action

Step 1: This use case begins actoradd the the customers reservationsuch as address, name, date checkin. Date check out, number of days

Step 3: this usecase ends when thecustomer verify the record

System Response

Step2: The system will save thegiven information

Alternate Courses

Pre-condition:Post-condition:

7/29/2019 Ims Usecase

10/12

Use Case Name: Create new account for receptionist

Actor(s): administrator

Description: This use case describes the process of how to create new account

Typical Course of Events: Actor Action

Step 1: This use case begins whenthe actor create an account forreceptionist such as name, type anduser number

Step 3: this usecase ends when theactor verified the account

System Response

Step2: The system will save theaccount

Step 3: the system will verify theaccount

Alternate Courses

Pre-condition:Post-condition:

7/29/2019 Ims Usecase

11/12

Use Case Name: Add reserve room

Actor(s): receptionist

Description: This use case describes the process of adding reserve room

Typical Course of Events: Actor Action

Step 1: This use case starts whenthe actor add reserve room

Step 3: the customer will verify theroom reservation

System Response

Step2: The system will verify theroom

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

Alternate Courses

Pre-condition:Post-condition:

7/29/2019 Ims Usecase

12/12

Use Case Name: View available rooms

Actor(s): customer

Description: This use case describes the process viewing available room

Typical Course of Events: Actor Action

Step 1: This use case starts whenthe actor ask for available room

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

System Response

Step2: The system will retrieve thelist of available room

Step 3: the system will display theavailable room

Alternate Courses

Pre-condition:Post-condition: