Database Management System for Properties -myassignmenthelp.com

Question: Discuss about theDatabase Management System for Properties and Customers. Answer: Entity relationship Diagram Business rules and Assumption Business Rules The following set of business rules are used for the development of the ER diagram of CQ Insurance. Maintaining a policy set for the CQ insurance for recording the details of the customer and their property details Maintaining the details of the customers and using different tables for properties and customers Details of the enrollment and the policy used as reference during the insurance claim. Assumptions For the development of the entity relationship diagram the following assumptions are made such as: A customer can have one or more property that are eligible for insurance For claiming insurance the customer should enroll into a policy One or more policy can be handles by an insurance agent Logical Design For the creation of the logical design the entity relationship diagram is mapped such that all the relations are kept in third normal form. The relations are provided below: Customer (Customer_ID [PK], Name, Address, Email) Properties (Property_ID [PK], Location, Details, Customer_ID [FK]) Home Item (Item_ID [PK], Description, Market_Value, Property_ID [FK]) Policy (Policy_number [PK], Details, Start_Date, End_Date, Duration) Policy_Enrollment (Policy_ID [PK], Customer_ID [FK], Policy_Number [FK], Item_ID [FK], Property_ID [FK], Policy_Date) Insurance_Agent (Agent_ID [PK], Agent_Name, Email, Contact_Information, Salary) Claims (Claim_ID [PK], Policy_ID [FK], Customer_ID [FK], Agent_ID [FK], Claim_Date) Bibliography Al-Masree, H.K., 2015. Extracting Entity Relationship Diagram (ERD) from relational database schema.International Journal of Database Theory and Application,8(3), pp.15-26. Yoshizumi, T., Kirishima, T., Goto, T., Tsuchida, K. and Yaku, T., 2016, July. A graph grammar for entity relationship diagrams. InIndustrial Informatics (INDIN), 2016 IEEE 14th International Conference on(pp. 810-815). IEEE.