COMPUTER SCIENCE

Use case: LogOnUser

Use case ID: UC1

Preconditions:

1. The User is logged on to the system

Primary scenario:

1. The use case begins when the User logs in

2. The system recognizes the User.

3. The system logs the User on the site right away.

Secondary scenarios:

The User do not logs in due to system failure.

Postconditions:

1. The User is logged on the system.

Secondary scenario:UserAuthenticationFails

Preconditions:

1. The User has not been recognized by the system.

Secondary scenario:

1 The scenario begins when the User selects “Log On’’.


2 While the User is not authenticated and the number of authentication attempts is less than or equal to three

2.1 The system asks the User for their user name and password.

2.2 The User enters their user name and password.


2.3 The user name and/or password is wrong.

3 The system logs a security violation. 4 The system freezes the User account.

Postconditions:

1 The User is not logged on. 
2 The system has logged a security violation.


3 The User’s account has been frozen pending investigation of the security violation.

Use case: LogOnCustomer

Use case ID: UC2

Actors:Customer

Preconditions:

1. The Customer is logged on to the system

Primary scenario:

1. The use case begins when the Customer clicks “LogOn”.

2. While the Customer is not authenticated and the number of authentication attempts is less than or equal to three

2.2 The system asks the Customer for their user name and password.

2.3 The Customer enters their user name and password.

2.4 The user name and password are correct.

3. The system authenticates the Customer.

Postconditions:

1. The Customeris not logged on.

Secondary scenario:CustomerAuthenticationFails

1. The scenario begins when the Customer selects “LogOn”.

2. While the Customer is not authenticated and the number of authentication attempts is less than or equal to three.

2.1 The system asks the User for their user name and password.

2.3 The user name and/or password is wrong.

3. The system freezes the User account.

Preconditions:

1. The User is not logged on.

2. The system has logged a security violation.

3. The User’s account has been frozen pending investigation of the security violation

Use case: CancelingAnOrder

Use case ID: UC3

Actors: Customer

Customer Care Assistant

Preconditions:

1. The Customer is logged on to the system.


2. The system is displaying full details of an open order.

Flow of event:

1. The use case begins when the Customer selects “Cancel Order”.

2. The system asks the Customer for confirmation.


3. The Customer confirms the cancellation.


4. The system marks the order as cancelled.

5. The system records the time and date that the order was cancelled.


6. The system tells the inventory actor to release the inventory items reserved for this order.

Postconditions:

1. The order is cancelled.

Use case:ArrangeDelivery

Use case ID: UC4

Actors:

Customer care assistant.

Logic department manager.

Preconditions:

1. The customer proceeded the order.

Postconditions:

1. The use case begins when the Customer selects “Checkout”.

2. The system asks the Dispatcher actor to display the Customer order

3. The system presents the final order to the Customer. The order includes the order information and the price. The order also includes the shipping information, and shipping address and credit card.

4. The system asks the Customer to accept or decline the order.

5. The Customer accepts the order.

6. The system arranges delivery.

Postconditions:

1. The customer has accepted the order.

2. The ordered has been processed by the customer care assistant.

Use case: TrackingOrder

Use case ID: UC5

Actors:

Customer

Preconditions:

1. The order has been forwarded to the Dispatcher.

2. The Dispatcher is logged on to the system.

3. The order status is “pending”.

4. The order has been processed by the Dispatch Department.

Flow of events:

1. The use case begins when the Dispatcher selects “Close Order”.

2. The system asks the Dispatcher to enter an order number, the date on which the order was shipped, the shipping company and tracking number if available.

3. The Dispatcher enters the requested information.

4. The system finds the order and changes the status of the order to “closed”.

5. The system adds to the order the date on which the order was shipped, the shipping company and tracking number (if available).

Postconditions:

1. The order status has been changed to “closed”.

2. The order has been updated to include the date on which the order was shipped, the shipping company and tracking number (if available).

Use case: CreateNewCustomer

Use case ID: UC6

Customer

Preconditions:

1. The Customer is not logged on to the system.


Flow of event:

1. The use case begins when the Customer selects “New Customer”.


2. The system asks the Customer to enter a user name and password.


3. The Customer enters the requested information.


4. The system checks to see if the user name is available and the password is valid.

5. While the username is not available or the password is invalid

6. The Customer enters the requested information.

7. 
While mandatory information is missing

8. The system confirms that the customer information has been accepted.

9. The system assigns a unique customer identifier to the customer.

Postconditions:

1. The system has saved the Customer details.


Use case: ViewOrder

Use case ID: UC7

Actors:

Customer

Preconditions:

1. A set of order has been identified for viewing.

Flow of events:

1. The system displays a page containing the first 5orders. This page includes summary details for each order including its price

2. While the Customer is browsing

2.1 If there are more order to display

2.1.1 The Customer may select “Next” to view the next page of orders

2.2 If the Customer is not on the first page of orders

2.2.1 The Customer may select “Previous” to view the previous page of orders

2.3 If the Customer selects anorder

2.3.1 The system displays full details of the order including its price

2.3.2 The Customer may select “Back” to continue browsing

Postconditions: None

Use case: WritingCustomerExperienceComments

Use case ID: UC8

Actors:

Customer Service

Customer

Preconditions:

1. The Customer is logged on to the system.

2. A Feedback have been raised by the Customers.

3. A set of claims has been identified for viewing.

Flow of events:

1. The system displays a page containing a maximum of 10 claims. This page includes the following summary information for each claim: order number, the reason of the claim, and the claim state.

2. The Customer support can solve the claims.

Postconditions:

1. A claims have been solved or under process.

2. Include ( Raiseclaim)