Auto part website system.

I need a short paragraph about:

-The scenarios of user interface design in general.

-Describing those scenarios specifically. ( how the programming works)

Context diagram Sales order confirmation Maintains supplier data, maintains inv. Data, request reports Customer Manager Customer data; sales orders Maintain Cust. Data, Sales Order Processing, Maintain supp. Data, Purchase reorder process, maintain inv. Data, display reports Summary reports Scenario 1 - Maintain Customer data. Customer: created, updated, and deleted. 1. New customer creates customer account 2. System auto assigns a unique customer ID to each new customer 3. Current customer updates customer account 4. Customer deletes account Scenario 2 - Sales order. Customer places a sales order and the storage of sales orders. 1. Customer searches for desired part(s) 2. Customer selects part 3. Customer specifies order quantity 4. Customer confirms order 5. Systems stores sales order information 6. System sends confirmation email to customer Scenario 3 - Supplier data. The manager inserts, updates, deletes supplier data 1. Manager creates supplier account 2. System auto assigns a unique supplier ID to each new supplier 3. Manager updates current supplier account 4. Manager deletes supplier account Scenario 4 - Purchase Reorder. The manager places purchase re-orders and the storage of said purchase re-orders to a supplier. 1. Manager searches for desired part(s) 2. Manager selects part 3. Manager specifies order quantity 4. Manager confirms order 5. Systems stores purchase re-order information Scenario 5 - Inventory Data. The manager inserts, updates, deletes Inventory data 1. Manager creates new part record 2. System auto assigns a unique part ID to each new part 3. Manager updates part record 4. Manager deletes part record Scenario 6 - Display Summary Reports. The manager requests desired reports from the system. 1. Manager requests desired report from the system 2. Requested report is exported into excel spreadsheet for report manipulation Context diagram Sales order confirmation Maintains supplier data, maintains inv. Data, request reports Customer Manager Customer data; sales orders Maintain Cust. Data, Sales Order Processing, Maintain supp. Data, Purchase reorder process, maintain inv. Data, display reports Summary reports Scenario 1 - Maintain Customer data. Customer: created, updated, and deleted. 1. New customer creates customer account 2. System auto assigns a unique customer ID to each new customer 3. Current customer updates customer account 4. Customer deletes account Scenario 2 - Sales order. Customer places a sales order and the storage of sales orders. 1. Customer searches for desired part(s) 2. Customer selects part 3. Customer specifies order quantity 4. Customer confirms order 5. Systems stores sales order information 6. System sends confirmation email to customer Scenario 3 - Supplier data. The manager inserts, updates, deletes supplier data 1. Manager creates supplier account 2. System auto assigns a unique supplier ID to each new supplier 3. Manager updates current supplier account 4. Manager deletes supplier account Scenario 4 - Purchase Reorder. The manager places purchase re-orders and the storage of said purchase re-orders to a supplier. 1. Manager searches for desired part(s) 2. Manager selects part 3. Manager specifies order quantity 4. Manager confirms order 5. Systems stores purchase re-order information Scenario 5 - Inventory Data. The manager inserts, updates, deletes Inventory data 1. Manager creates new part record 2. System auto assigns a unique part ID to each new part 3. Manager updates part record 4. Manager deletes part record Scenario 6 - Display Summary Reports. The manager requests desired reports from the system. 1. Manager requests desired report from the system 2. Requested report is exported into excel spreadsheet for report manipulation