Create an ERD using the crows foot notation discussed in the PowerPoint videos for this module. Be sure each entity is a box with the name of the entity at the top of the box, the primary key attribute or attributes are in the middle of the box, and the non-primary key attributes and foreign keys are in the bottom of the box. Lines should separate each part of the entity box. Each entity must have a primary key defined. A primary key may consist of one or more attributes. The final ERD submitted for grading should not include any M:N relationships, and all attributes should be placed within an entity. Each relationship should have at least one relationship verb or verb phrase. Please include all required foreign keys and denote the foreign key(s) with the notation (FK) on the ERD. In addition to creating an ERD, also make data tables showing how the data in the Excel workbook would be stored in your tables. You do not have to create these tables on SQL Server just create tables in a Word document or Excel workbook. Use these tables to help you validate your database design. Each table should store the data without redundancy. For example, there should be one row per customer in your newly designed database. Include these data tables with your ERD as part of the deliverable for this assignment. a. Application scenario: Design a database for a landscaping company to help keep track of their contracts. Sample data is provided in the Excel workbook called LandscapeContractData. On the worksheet, each row represents a unique contract. Each contract has a unique contract number, a date that the contract was signed, and a contract amount. Each contract is also of a given type. A contract can only be of one type. A contract type is a set of standardized types that should be stored in the database. Each contract is with only one customer. A contract must have a customer and a contract type. A customer has an identifier (CustomerID), a CustomerName, a phone number, a city, and a state. A customer may be stored in the database even if the customer does not currently have a contract. A contract type may be stored in the database even if the contract type is not currently related to a contract.