UML Use Case Diagram Exercise Create a UML Use Case diagram from the following (bulletized) business requirements. Tips: (1) Whenever you can say that Item B is always a type of Item A, or Item B is always a kind of Item A, that indicates that you have a generalization relationship such that Item B is the specialization and Item A is the generalization; (2) Includes relationships are identified when one Use Case always uses another Use Case; (3) Extend relationships are identified when one Use Case sometimes (but not always) uses another Use Case under some special conditions. The following requirements are for a product purchase system:

The administrator runs inventory reports. Every time when inventory reports are run, inventory data is loaded from disk.

The administrator updates the inventory stock. Every time when inventory stock is updated, inventory data is loaded from disk. Also, every time when inventory stock is updated, inventory data is saved to a disk.

A (general) make-a-sale (hint: meant to be a verb-noun phrase) can be of two specialized kinds: (1) make-a phone order sale; and (2) make-a walk-in sale.

A sales clerk records the make-a-walk-in sales.

A telephone operator, a specialized kind of a sales clerk, handles and records all make-a phone orders.

Whenever there is a make-a-sale, the inventory stock is updated.

A sale may need to verify a credit card if the purchase is a credit card purchase.

A sale may need to verify a check if the purchase is a check purchase.