Use the following business rules to identify and write all attributes, relationships, and cardinalities between the entities shown on the next page. Do not add any additional entities to the diagram. Decide which attributes should be primary keys and foreign keys for each entity and put those in the diagram. Remember to include relationship verbs for all relationships. Deliverable for this question: Please write the answers directly on the diagram on the next page. Take a picture of the diagram when you have finished and add the picture to the Word document created for Question 1. Do not turn in a separate file for your answer to each question. Application scenario: The application is for a research engineering company that needs to keep track of employees and equipment when they are assigned to a project. The database will be owned by the research engineering company. If you need to make assumptions about business rules other than the ones provided below, be sure to write those assumptions on your answer. An employee is uniquely identified by an EmployeeID. For each employee, the database should keep track of the FirstName, LastName, PhoneNumber, and EmailAddress. A project is uniquely identified by a ProjectID. For each project, the database should keep track of the ProjectMission and StartDate. A piece of equipment is uniquely identified by a SerialNumber. The database should keep track of the cost of the piece of equipment. An EquipmentType is uniquely identified by an EquipmentTypeID (as shown on the skeleton diagram). The database should keep track of the TypeDescription for each EquipmentType. Each piece of equipment is related to one and only one row in the EquipmentType entity, but a given row in the EquipmentType entity might be related to multiple pieces of equipment. The assignment entity is used to store the AssignDate and the ReleaseDate for the assignment of an employee to a project with a piece of equipment. The AssignmentID is the primary key. The assignment entity should be viewed as an intersection entity. An employee may be assigned to many different projects and pieces of equipment; A project may have many different employees and pieces of equipment assigned to it, and a piece of equipment may be assigned to many employees and projects. The assignment entity is used to store all the assignments.