7. Suppose that you are designing a database for a life insurance company. Every agent of the insurance company has a name, agent number (which uniquely identifies the agent), and phone number. An insurance policy has a policy number (which uniquely identifies the policy), a premium amount (this is the monthly payment due), an agent who sells the policy, and a payout amount. A person may buy an insurance policy; people who buy a policy are called customers. We need to record the name, social security number, birthdate, and beneficiaries of each customer. A customer is only allowed to have one policy at a time. A customer may have up to 12 beneficiaries (these are the people who will receive the payout of the policy). We need to know the first name of each beneficiary, but this is not enough to identify a beneficiary. In order to identify a beneficary, we need to know both their first name and the social security number of the customer whose policy they are on. Create an ER diagram for the database, including all appropriate entity types, relationship types, and attributes. Specify a key for each entity type, and all appropriate cardinality constraints; and identify any derived attributes, descriptive attributes, roles, and weak entity types. Avoid multi-valued attributes whenever possible. Explain any assumptions you make, and identify any constraints which cannot be captured with the ER diagram