ass ENTITY RELATIONSHIPS EXERCISE Please read the below requirement and create an ER diagram for the below Requirement End users visit the Hallmarks partner website to purchase gifts items. Customers may or may not place orders at any one time. Each order is assigned a unique order code and an order may have multiple items. The Item type will be an important attribute. One order can have multiple transactions since customers may add items, change the quantity of items or even return items after purchase, if they so desire. The payment amount is the total amount of the order and the payment type is the type of payment that the customer uses (eg Credit card, check, cash etc). Relevant customer information includes name, address and telephone number Please represent the above requirement as an ER diagram with UML notation. We will develop and add this to out Database and write SQL queries on this Remember The steps to creating an ERD are as follows. ldentify the entities - Entities are easy to recognize as they are represented by nouns Identify attributes - these are qualities/values associated with entities ldentify the relationships between the entities - relationships are identified by verbs Link entities to attributes and link entities together via their relationships NORMALIZATION EXERCISE PLEASE NORMALIZE THIS TABLE IN 3NF (AT A MINIMUM 2NF) Employee No Employee Name Department Employee City Employee Rating Amit Divya ama OBIEE,ETL NYC COGNOS Administrator NYC AVERAGE AVERAGE STAR 2 TX The process may look complicated. However, if you follow the rules completely, and donot miss out any steps, then you should arrive at the correct solution. If you omit a rule there is a high probability that you will end up with too few tables or incorrect keys The following normal forms were discussed in this section: 1. First normal form: A table is in the first normal form if it contains no repeating columns 2. Second normal form: A table is in the second normal form if it is in the first normal form and contains only columns that are dependent on the whole (primary) key 3. Third normal form: A table is in the third normal form if it is in the second normal form and all the non-key columns are dependent only on the primary key. If the value of a non-key column is dependent on the value of another non-key column we have a situation known as transitive dependency. This can be resolved by removing the columns dependent on non-key tems to another table