Use the information below and create a sequence diagram for the use case.
Name: Buy Parts
Actor: Customer/Store Associate
Description: This use case describes the process used to buy parts at the auto parts dealer.
Successful Completion: 1. Customer requests auto part
2. Store Associate checks on availability of part
3. Part is available and customer pays cost
4. Customer receives part and stock is adjusted
Alternative: 1. Customer requests auto part
2. Store Associate checks on availability of part
3. Part is not available, and customer selects to order part or no part
4. Customer receives part and stock is adjusted (if alternate part ordered) or customer leaves with no part
Pre-Condition: Customer wants to purchase part
Post-Condition: None
Assumptions: None
Customer -> Store Associate: 1. Customer requests auto part
Store Associate -> Inventory System: 2. Store Associate checks on availability of part
Inventory System --> Store Associate: 3. Part is available
Store Associate -> Customer: 3. Customer pays cost
Customer -> Store Associate: 4. Customer receives part
Inventory System -> Inventory System: 4. Stock is adjusted
Alternative:
Customer -> Store Associate: 1. Customer requests auto part
Store Associate -> Inventory System: 2. Store Associate checks on availability of part
Inventory System -> Inventory System: 3. Part is not available
Store Associate -> Customer: 3. Customer selects to order part or no part
Inventory System -> Inventory System: 4. Customer orders alternate part or no part
Customer -> Store Associate: 4. Customer receives part or leaves with no part
Inventory System -> Inventory System: 4. Stock is adjusted if alternate part ordered