Answer Questions 1, 2 , and 3. Please use the tables provided to answer questions 2 and 3

Assignment information Consider the following scenario: New Horizons Sailboat Charters (NHSC) is a business that owns and leases (charters) sailboats and specializes in boats that can be used for multiday or weekly charters. Each sailboat is fully equipped at the time it is leased. Some equipment are attached to the boat, such as radios, compasses, depth indicators and other instrumentation, stoves, and refrigerators. Other equipment, such as sails, lines, anchors, life preservers, and equipment in the cabin (dishes, silverware, cooking utensils, bedding, and so on), is not physically attached to the boat. NHSC provides consumable supplies, such as charts, navigation books, tide and current tables, soap, dish towels, toilet paper, and similar items. The consumable supplies are treated as equipment by NHSC for tracking and accounting purposes. Sailboats need maintenance. NHSC keeps accurate records of all maintenance activities and costs. Here are some additional requirements about the data to be stored in this database: - For a charter, the return date may not be known at the start of the charter. - For the maintenance, cost is optional and only applies if maintenance involves outside contractors. - For customers, email is optional. - For equipment, make and model are optional since not all equipment have a make or model. - NHSC wants to keep records of all past charters, even those involving a boat or equipment that is no longer rented. - If a charter needs to be deleted, data about equipment rented for that charter can also be deleted. - For the maintenance data, NHSC does not want to keep the log of maintenance if the boat is no longer in use and needs to be removed from the database. A data model of a proposed database to support an information system for NHSC is shown below. Questions 1. Convert this conceptual model to a database design (using the E-R diagram notations). Your design should include a specification of tables and attributes as well as primary, alternate and foreign keys. Identify the SQL Server data type for each attribute. 2. List all relationships in your model using the table below. Summary of design relationships 3. Specify how you will enforce minimum cardinality. Document your minimum cardinality enforcement using referential integrity actions for required parents, if any, using the form below. Fill a separate form for each M-O relationships in your design (make sure to replace the general labels PARENT and CHILD with the names of the parent and child tables for the relationship being documented). Actions for required parent in PARENT-CHILD