Featured Post

A Study to Determine the Prevalence of Pressure Ulcers in Spinal Cord Injury Patients and Underlying Factors (in a Governme :: Nursing Research Project

I have done an exploration venture in satisfaction of the Bachelors of Science in nursing at Rufaida College of nursing, Hamdard University,...

Saturday, May 2, 2020

Telemedicine Database Management System †MyAssignmenthelp.com

Question: Discuss about the Telemedicine Database Management System. Answer: Introduction: At the time of designing the ERD, it has been assumed that one owner can claim many policies. However, a property can be insurance only once. The system needs to store the details of the bills. The coverage of the insurance is same for both types of insurances. The specialization is introduced in the ERD diagram to show the types of policies and properties. Each of the policies are associated with different properties. Such as, the Home Building policy is associated with home and the Home Contents policy is associated with contents of home. The coverage is related to policy in the form of many to many relationship. The many-to-many relationship is not possible to implement in real life. Therefore, the many-to-many relationship is divided into one-to-many and many-to-one. The business rules of the designed ERD are as following. Customer related to property in one to many relationship. One customer may have many properties. Home_Building_Policy has one-to-one relationship with home. Home_Conetcts_Policy has one-to-one relationship with contents. Policy has one-to-many relationship with Policy_Coverage Policy_Coverage has many-to-one relationship with Coverage Bill has many-to-one relationship with policy Logical Design: Customer(Cust_ID, Name, Address, Phone, Email, Age) Owner_Property(ID, Owner) Foreign key (Owner) references Customer(Cust_ID) Home(Number, HBP_ID, Address, Registration_ID, Size, GPD) Foreign key (HBP_ID) references Home_Buliding_Policy(HBP_ID) Home(ID, HCP_ID, Type, Original_Cost, Purchase_Dtae, Gurantee_Last_Date) Foreign key (HCP_ID) references Home_Contents_Policy(HCP_ID) Policy(ID, Policy_Number, Policy_Effective_Date, Payment_Option, Total_Amount, Achieve, Additional_Info, Created_Date) Bibliography: Hababeh, I., Khalil, I. and Khreishah, A., 2015. Designing high performance web-based computing services to promote telemedicine database management system. IEEE transactions on services computing, 8(1), pp.47-64. Nidzwetzki, J.K. and Gting, R.H., 2016. DISTRIBUTED SECONDO: An extensible highly available and scalable database management system. FernUniversitt, Fakultt fr Mathematik und Informatik.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.