Use Case Name View and update customer details

Scenario Customer are able to view their account and update the details.
Triggering Event Customer need to view or update their details.
Brief Description Customer that had created their account they need to check their
account in order not to miss any details or information about
themselves if there is anything that require the customer to change
information they can update it immediately.
Actors Customers.
Related Use Cases Create customer account.
Stakeholders
Preconditions Customer need to create their account first.
Post Conditions Customer require to click confirmation button.
Flow Of Activities Actor System
1. Customer click on 1.1 System will display the details
account button. of information in one page.
2. Customer click on edit 1.2 At the end of the page system
button. will provide a confirmation
3. Customer fill in the button and edit button.
form and make change 2.1 System will display a form to
to the wrong details. customer.
4. Customer click on 2.2 System will provide two button
update button. at the end of the page which is
an update button which is a
confirmation for update and a
cancel button.
4.1 Customer information will be
stored into database.
4.2 The system will update all of
the information to the view
account page.

Exception Conditions

Special Requirements/ Business The customer have to follow all of the information format.
Rules
Assumption Customer tend to have a typing error and keep changing a few
information like password, username, phone number and address.
Use Case Name View catalog.

Scenario View list of item trough catalog provided.

Triggering Event Customer want to find wedding dress, accessories or shoes for their
wedding day.
Brief Description Customer view catalog that show the details of wedding dress,
accessories and shoes.
Actors Customers.
Related Use Cases None.
Stakeholders
Preconditions Catalog must be available and being maintained.
Post Conditions Customer must click on the specific item to view full description of
the item.
Flow Of Activities Actor System
1. Customer view the 1.1. System will display list of the
home page or pages most popular item in a catalog
based on categories. form
2. Customer click on the 1.3 Each item will have a view
view item button. button and add to cart button.
2.1 System will display item
picture, item price and item
description.
2.2 System will provide an add to
cart button.
Exception Conditions

Special Requirements/ Business

Rules
Assumption
Use Case Name Booking item.

Scenario Booking online item for rent.

Triggering Event Customer want to booking item for their wedding.
Brief Description Customer want to book the items that had being added to their cart.
Actors Customers
Related Use Cases Create account and catalog
Stakeholders Marketing, operating, general manager.
Preconditions Item must be available and customer have create an account.
Post Conditions Customer have to make payment.
Flow Of Activities Actor System
1. Customer view item 1.1 System will display all of the
from catalog. boutique item to the online
2. Customer click on the catalog.
provided add to cart 1.2 System will display the
button. availability of the item in the
3. Customer insert the item description.
size, renting date and 2.1 System will prompt user to
number of item. insert a few details like
4. Customer need to click customer size, renting date
on confirm button. and number of item.
5. Customer click on check 3.1 System will prompt customer
out button to click on confirmation
button.
5.1 All of the customer desire
item will be stored into the
database.
5.2 System will display selected
item in the customer cart
page.
5.3 System will provide a check
out button for customer to
proceed with booking the
items.
5.4

Exception Conditions

Special Requirements/ Business

Rules
Assumption
Use Case Name

Scenario
Triggering Event
Brief Description
Actors
Related Use Cases
Stakeholders
Preconditions
Post Conditions
Flow Of Activities

Exception Conditions
Special Requirements/ Business
Rules
Assumption