$1.$Create the initial ER diagram. Base your design on the following business rules: A store may place many orders. $($Note the use of may which is reflected in the ORDER optionality.$)$ An order must be placed by a store. $($Note that STORE is mandatory to ORDER. In this ERD, the order environment apparently reflects a wholesale environment.$)$ An order contains at least one order line. $($Note that ORDER$\_$LINE is mandatory to ORDER, and vice$-$versa.$)$ Each order line is contained in one and only one order. $($Discussion: Although a given item such as a hammer may be found in many orders, a specific hammer sold to a specific store is found in only one order.$)$ Each order line has a specific product written in it$.$ A product may be written in many orders. $($Discussion: Many stores can order one or more specific products, but a product that is not in demand may never be sold to a store and will, therefore, not show up in any order line $--$ note that ORDER$\_$LINE is optional to PRODUCT.Also, note that each order line may indicate more than one of a specific item. For example, the item may be hammer and the number sold may be $1$ or $2,$ or $500.$ The ORDER$\_$LINE entity would have at least the following attributes: ORDER$\_$NUM, ORDLINE$\_$NUM, PROD$\_$CODE, ORDLINE$\_$PRICE, ORDLINE$\_$QUANTITY. The ORDER$\_$LINE composite PK would be ORDER$\_$NUM $+$ ORDLINE$\_$NUM. You might add the derived attribute ORDLINE$\_$AMOUNT, which would be the result of multiplying ORDLINE$\_$PRICE and ORDLINE$\_$QUANTITY.$)$ A store may employ many employees. $($Discussion: A new store may not yet have any employees, yet the database may already include the new store information location, type, and so on$.$ If you made the EMPLOYEE entity mandatory to STORE, you would have to create an employee for that store before you had even hired one.$)$ Each employee is employed by one $($and only one$)$ store. An employee may have one or more dependents. $($Discussion: You cannot require an employee to have dependents, so DEPENDENT is optional to EMPLOYEE. Note the use of the word may in the relationship.$)$ A dependent must be related to an employee. $($Discussion: It makes no sense to keep track of dependents of people who are not even employees. Therefore, EMPLOYEE is mandatory to DEPENDENT.