There is a database design assignment that divided into three parts.
I hope your experts can help me to finish it. I've already done the Part A. So you need to do the following works based on my Part A.
You can also revise/improve my part A in order to do better for Part B & C. But never change the Part A too much.
I need revised part A & finished part B in 3 days. As for the whole assignment, you can give it back to me in a week time.
Introduction:
The assignment involves the conceptual and logical design of a database to support an online insurancecompany.
The data model can be based on an existing system or a fictional system, but in the latter case, we suggest that you base it primarily on a real system to ensure that you include all the necessary information. In your submission, include details about which website you used as a source for your ideas. The data model details shouldbe as complex as your group can reasonably manage and model correctly. Generally, individuals will tend to have smaller, less complex data models than groups, which should be dealing with more entities and relationships.
Please ensure that you adhere to the generally accepted principles of privacy and confidentiality of data. In particular, if you are basing your assignment on an actual system to which you have access, do not use details such as names, contact details etc of real customers or other people in your case study. You should change this data so that it cannot be linked to a real person or company.
Assignment Requirements:
The submission includes the following deliverables:
Part A:
1) Database design case study:
Give a short description of the insurance application/website for which you will be designing the database, outline the basic functions that your database needs to support, and identify the data requirements. Please include some sample documentation (forms, statements, webpage etc.).
Your case study description should be similar to the New Oriental Hospital case study given for your data modelling tutorials (See Tutorials 1 and 2),but will probably be shorter, with 3 or 4 forms. You will only need 6-8 entities in total when doing the conceptual data modelling, so bear this in mind when deciding the scope of your case study).
Part B:
2) Conceptual data modelling:
Produce the final ERD reflecting the data requirements given in the case study (using the Crow’s foot or textbook notation). Justify your design decisions by documenting all your assumptions for your conceptual data model. Your conceptual data model will be marked according to your ability to identify appropriate entities, attributes, relationships and cardinalities, and to structure a data model using these elements.
Part C:
3) Logical design / Schema conversion:
Convert your ERD (conceptual schema) into a set of relational tables. Use the following format to list each table, where the primary keys are underlined and the foreign keys are marked with asterisk(s):
TableName (Identifier, non-key attributes) or
TableName (Identifier, non-key attributes, ForeignKey*)
ForeignKey references OtherTable
Your relational model will be marked according to your correct application of the appropriate conversion rules.
4) Logical design / Normalisation:
a) Identify and list the functional dependencies (FDs) (based on the business rules and formsof your case study)
Please use the following format for your functional dependencies:
X → Y
i.e. determinantAttribute(s) → dependentAttribute(s)
b) Use these FDs to determine the highest normal form for each table/relation defined in deliverable 3. Justify your decisions. If there are tables which are not fully normalised (i.e. not in BCNF), perform normalisation for the tables until all the tables are in BCNF. You must document in detail each part of the normalisation process.
Please use the following format for your final set of relations, where the primary keys are underlined and the foreign keys are marked with asterisk(s):
RelationName (Identifier, non-key attributes) or
RelationName(Identifier, non-key attributes, ForeignKey*)
ForeignKey references OtherRelation
Note: Your assignments will be marked according to your demonstration of knowledge, i.e. you must demonstrate that you understand each of the processes of database design, such as conceptual data modelling, logical design of a database and normalisation,. You need to justify your design decisions, so do not simply show your final answers. Show your working and reasoning as much as possible.
5) Reflection on your design and lessons learnt
Write a reflection on your design and lessons learnt from this assignment. You need to roughly rank your design out of 10 and give the reasons you have assigned this ranking. Also, you need to point out specifically what you can improve.
What is a Reflection?
Adapted from: https://www.gwc.maricopa.edu/class/e-portfolio/reflecwhat.html
Reflection, or thinking about our experiences, is the key to learning. Reflection allows us to analyse our experiences, make changes based on our mistakes, keep doing what is successful, and build upon or modify past knowledge based on new knowledge. Reflection also allows us to make connections between subjects or between school, work and home. By doing this, we begin to see how all parts of our lives are connected and to understand that we are a part of the web of life.
The reflective part of this assignment is to help you to reflect on the assignment this semester, assess what you have learned and explain what connections you see or can make between classes and between other subjects, work and home. To help yourself in doing this you may wish to consider the following questions:
• What did you already know about the content or skills that were presented in this class?
• What did you learn about the content or skills that were presented in this class?
• How did doing the assignment change your understanding of the content and skills used in this subject?
• What connections have you made between this class and other subjects you’ve taken or with experiences at work or home?
Attachment:- Database design.rar