Title: Update Personal Information

Actor: User (Admin, Customer, Provider)

Scenario:

1. User can update his/her personal information.

2. Admin can also update own and other personal information.
3. User have to log into the system.
4. Users need to navigate the profile info page.

Exception:

1. Too much user at a same time can cause server traffic.

2. User Input error.
3. No database connection.

Precondition:

1. Users have devices that support internet service.

2. Users have internet connection.
3. Users are familiar with web browsing and can interact with website.
4. Users must be logged in to the web application.
5. Users must be on the page.

Post condition:

1. Successful: User can update personal information.

2. Unsuccessful: Due to server problem user can see an error message and system will ask
for try again.
3. Exception: Stay in the same page if possible.
Title: Registration Confirmation
Actor: Admin

Scenario:

1. User have to get access to all registration request list.

2. Then after verification user have to give access to new registered person through their id.
3. User has to be logged into the system.

Exception:

1. Too much user at a same time can cause server traffic.

2. User Input error.
3. No database connection.

Precondition:

1. Users have devices that support internet service.

2. Users have internet connection.
3. Users are familiar with web browsing and can interact with website.
4. Users must be logged in to the web application.
5. Users must be on the page.

Post condition:

1. Successful: User can give access to new user successfully.

2. Unsuccessful: Due to server. User can see an error message and system will ask for try
again.
3. Exception: Stay in the same page if possible.
Title: Payment
Actor: Admin, Customer, Provider

Scenario:

1. Provider and admin can view all order request according to customers need.
2. User can accept order request.
3. Then they can contact with their clients for completing payment.

Exception:

1. Too many server request is not controllable for the server.

2. Too much user at a same time can cause server traffic.
3. No database connection.

Precondition:

1. Provider and seller have to register to the system

2. Admin has to log into their account to receive the request.
3. Admin has to accept the request, able to contact to the provider.

Post condition:

1. Successful: Provider can get the order request and provide it successfully.
2. Unsuccessful: Admin can’t get the request for server problem. User can see an error
message and ask for try again.
3. Exception: Stay in the same page if possible.