Use Case Description

Use Case Name:   Make an Order

ID:  2      

Importance Level: High

Primary Actor:      Customer

Use Case Type:    Detail

Stakeholders and Interests:            Customer – wants to place order for a specific gear

                                                          Process Gear – wants to keep track of orders

 

Brief Description:                 Adds orders to the database.

Trigger:     A customer places an order.

Type:        External               

Relationships:

                Association:         Customer, Delivery Schedule, Parts, Parts Process Operations, Job Process

                                           Outsource

                Include:                  Credit Limit Verification

                Extend:                 Add a New Customer, Create a New Part          

                Generalization:     

Normal Flow of Events:

1.        If customer is not an existing customer, execute add a new customer use case.

2.        If the gear is a new part, execute create a new part use case.

3.        Order information (quantity, part number, order number, customer number, purchase order number, price) is entered into the database.

4.        The credit limit verification use case is executed.

5.        If credit is approved, a delivery schedule is determined using part numbers, quantities, and shipping dates.

6.        The order acknowledgement is printed and sent to the customer.

7.        Retrieve all operations for this part.

8.        Add these operations to the job process.

9.        Determine vendor for outsourced operations.

SubFlows:

        S-1:

1.         

        S-2:

1.         

Alternate/Exceptional Flows: