25
Use Case: Create Customer Account Sequence Diagram Main Flow: 1. Customer enters first name. 2. Customer enters last name. 3. Customer enters email address. 4. Customer enter phone. 5. Customer enters password. 6. Customer reenters password. 7. Customer enters street address. 8. Customer enters city. 9. Customer enters state. 10. Customer enters zip code. 11. Customer selects remember me. 12. Customer selects sign up for notifications 13. Customer clicks submit.

justinbareis.files.wordpress.com€¦  · Web viewCustomer clicks add to cart. Use Case: Update Order Sequence Diagram. Main Flow: Customer has the choice to update the following:

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Use Case: Create Customer Account Sequence Diagram

Main Flow:

1. Customer enters first name.

2. Customer enters last name.

3. Customer enters email address.

4. Customer enter phone.

5. Customer enters password.

6. Customer reenters password.

7. Customer enters street address.

8. Customer enters city.

9. Customer enters state.

10. Customer enters zip code.

11. Customer selects remember me.

12. Customer selects sign up for notifications

13. Customer clicks submit.

Use Case: Update Customer Account Sequence Diagram

Main Flow:

Customer has the choice to update the following:

1. Customer enters first name.

2. Customer enters last name.

3. Customer enters email address.

4. Customer enter phone.

5. Customer enters password.

6. Customer reenters password.

7. Customer enters street address.

8. Customer enters city.

9. Customer enters state.

10. Customer enters zip code.

11. Customer selects remember me.

12. Customer selects sign up for notifications

13. Customer clicks submit.

Use Case: Delete Customer Account Sequence Diagram

Main Flow:

1. Customer selects delete account.

2. Customer clicks submit.

Use Case: Create Customer Receipt Sequence Diagram

Main Flow:

1. Karoline enters first name.

2. Karoline enters last name.

3. Karoline enters street address.

4. Karoline enters city.

5. Karoline enters state.

6. Karoline enters zip code.

7. Karoline selects delivery type.

8. Karoline selects method of payment.

9. Karoline selects estimated ready date.

10. Karoline selects estimated ready time.

11. Karoline selects the product.

12. Karoline enters the price.

13. Karoline enters the total.

14. Karoline clicks submit.

Use Case: Update Customer Receipt Sequence Diagram

Main Flow:

Customer has the choice to update the following:

1. Karoline enters first name.

2. Karoline enters last name.

3. Karoline enters street address.

4. Karoline enters city.

5. Karoline enters state.

6. Karoline enters zip code.

7. Karoline selects delivery type.

8. Karoline selects method of payment.

9. Karoline selects estimated ready date.

10. Karoline selects estimated ready time.

11. Karoline selects the product.

12. Karoline enters the price.

13. Karoline enters the total.

14. Karoline clicks submit.

Use Case: Delete Customer Receipt Sequence Diagram

Main Flow:

1. Karoline selects delete receipt.

2. Karoline clicks submit.

Use Case: Create Order Sequence Diagram

Main Flow:

1. Customer enters first name.

2. Customer enters last name.

3. Customer enters email address.

4. Customer enters phone number.

5. Customer selects method of delivery.

6. Customer selects type of event.

7. Customer selects event date.

8. Customer selects number of people needed to serve.

9. Customer selects the type of product.

10. Customer selects cake/cupcake flavor.

11. Customer selects filling/topping.

12. Customer enters budget

13. Customer enters message to be written on the product.

14. Customer enters additional information needed.

15. Customer attaches image.

16. Customer clicks add to cart.

Use Case: Update Order Sequence Diagram

Main Flow:

Customer has the choice to update the following:

1. Customer enters first name.

2. Customer enters last name.

3. Customer enters email address.

4. Customer enters phone number.

5. Customer selects method of delivery.

6. Customer selects type of event.

7. Customer selects event date.

8. Customer selects number of people needed to serve.

9. Customer selects the type of product.

10. Customer selects cake/cupcake flavor.

11. Customer selects filling/topping.

12. Customer enters budget

13. Customer enters message to be written on the product.

14. Customer enters additional information needed.

15. Customer attaches image.

16. Customer clicks add to cart.

Use Case: Delete Order Sequence Diagram

Main Flow:

1. Karoline selects delete order.

2. Karoline clicks submit.

Use Case: Create Login Sequence Diagram

Main Flow:

1. Karoline/Customer enters username.

2. Karoline/Customer enters password.

3. Karoline/Customer selects Remember Me.

4. Karoline clicks submit.

Use Case: Update Login Sequence Diagram

Main Flow:

Karoline has the choice to update the following:

1. Karoline enters username.

2. Karoline enters password.

3. Karoline selects Remember Me.

4. Karoline clicks submit.

Use Case: Delete Login Sequence Diagram

Main Flow:

1. Karoline selects delete receipt.

2. Karoline clicks submit.

Use Case: Shopping Cart Sequence Diagram

1. Customer creates a cake through the create a cake process.

2. Customer adds the cakes that they wish to order a virtual shopping cart

3. Customer has option to add or remove items from shopping cart

4. Once satisfied, the customer moves system along to delivery

Use Case: Notification Sequence Diagram

Main Flow

1. System administrator enters customer email address

2. System administrator enters subject

3. System administrator enters message

4. System administrator clicks submit

5. Email is sent to customer

Use Case: Date Sequence Diagram

Main Flow

1. System administrator enters date

2. System administrator enters start time

3. System administrator enters end time

4. System administrator enters unavailable

5. System administrator clicks export to calendar

6. Unavailable date is added to calendar

Use Case: Expense Sequence Diagram

Main Flow

1. System administrator enters date

2. System administrator chooses expenses type

3. System administrator enters expense name

4. System administrator enters cost

5. System administrator clicks submit

6. Expense is created

Use Case: Payment Sequence Diagram

Use Case: Delivery Sequence Diagram

Main Flow

1. System administrator clicks “create delivery”

2. System administrator enters customer’s first name

3. System administrator enters customer’s last name

4. System administrator enters order number

5. System administrator chooses date of delivery

6. System administrator enters customer location

7. System administrator enters delivery charge

8. System administrator enters notes about order

9. System administrator clicks submit

10. Delivery is created

Use Case: Social Media Outreach Sequence Diagram

Use Case: Report Sequence Diagram

Use Case: Revenue Report Sequence Diagram

Use Case: Inventory Sequence Diagram

Main Flow:

1. Karoline selects item code.

2. Karoline selects item name.

3. Karoline selects item category.

4. Karoline selects item quantity.

5. Karoline enters price

6. Karoline clicks submit.