UML Class Diagrams
For this project, you will prepare a class diagram plus another UML diagram of your own choosing based on the Problem Statement below. The diagrams you submit must represent the overall architectue of your IT system solution and key attributes that address the Problem Statement requirements. The following is the Problem Statement :
The Try 'n Save Inc. is a discount pet food store that caters to bargain-hunting pet owners. The management of Try 'n Save wishes to implement an enterprise resource planning (ERP) system that links the local stores, regional warehouses, participating suppliers, and headquarters. Management requires that each sale at a store's cash registers (i.e., the point-of-sale (POS) transaction) be tracked by the store's inventory system and the inventory system at the store's regional warehouse. The regional warehouses will exchange inventory and sales data with each other, with their suppliers, and with headquarters. Some suppliers will service all warehouses, while others will service only one regional warehouse.
The ERP system component at the local Try 'n Save store will automatically determine when to submit a store order (SO) to the regional warehouse to replenish the store's inventory for the product in problem. The regional warehouse automatically will determine when to submit a Resupply Order (RO) to the supplier, versus handling the SO with on-hand supply. Regional warehouses alternatively may submit a Transfer Order (TO) to a peer regional warehouse if a peer regional warehouse has more than a 90-day supply of the item(s) requested by the SO. In addition to processing the order, the recipient will acknowledge all types of orders. The response time between an order and its acknowledgement will be one (1) minute or less 90 percent of the time.
The suppliers of Try 'n Save will be encouraged to automatically process Try 'n Save's ERP system ROs. During the period suppliers transition to fully automated links, the ERP system will tolerate a mix of automated and non-automated links to suppliers. Assume that the link to the non-automated suppliers will be by means of faxed transmission of ROs over commercial telephone lines. There will be no acknowledgement of faxed ROs.
The headquarters component of the ERP system will maintain a corporate-wide view of sales and inventory levels. Monthly and quarterly management reports will be generated that will summarize the following for the respective time period:
• sales by store 
• sales by region 
• total sales 
• inventory by store 
• inventory by region 
• and total inventory 
Ad hoc report capability will also be supported by the ERP system.
In addition, the headquarters ERP system component will provide "data-mining" features to determine trends in the corporate-wide data by region, by time-of-year, by holiday, and by other pet demographic parameters to be defined by management.