To browse Academia. Skip to main content. You're using an out-of-date version of Internet Explorer. Log In Sign Up. Rok Piletic. Ankit Shukla.
Options: The result of the new DB will also be a change in process of insurance company from office work to online service in Waterford. Cost and Timescale: The only cost we have is time of a students used to performed outputs of this project. For the whole project there is estimated hours for Tim of five students. Risk Analysis: Risk Identification: Time management, time scheduling and not sufficient time to do the output, loss of data or outputs, not enough information to build the right DB, not meeting the goals of the project therefore bad grading, delegating the tasks to the right person in the Tim.
Risk Prevention: Make a good time scheduling, make a good research and preparation on the tasks ahead, save data in different locations not to get lost or stolen, use more computers if one will get broken down.
Car insurance database er diagram
Risk Management: If there are risks that we could not foresaw or we did not take a precaution to prevent it to happen, we will take a meeting und discuss it inside the group what action to take to eliminate it and if they were even bigger things than that we could handle we will discuss it with module facilitator.
Risk Monitoring: During the project we will have a written report with all the details of the work to be done, responsibilities and deadlines so that we could meet the submission deadlines. Part B - Submit the model and report to the appropriate folder on Moodle by 5pm on Friday 14th of November, Schedule Gantt chart : Table 1: Gantt chart Human Resource Requirements: Project team Its estimated 8 weeks with current tem of 5 people to be needed to do the project.
Maybe there will be needed one to two support staff when building the DB. Support Staff additional people needed when building the DB. Additional Staff No additional staff needed. Project Control: Monitoring mechanisms Project progress will be monitored trough meeting reports and outputs done till next meeting. Section 5: Case: Aviva Car Insurance AVIVA is a global service company in 17 countries that has around 43 million customers with insurance, savings and investment products.
Section 6: Data Base Modelling Data modeling is an activity that makes physical world become digital stored in data base, as seen in Figure 1, how the process from reall world becomse Data base model. Figure 1: Process of data base building The output we get from this activity is the data model as static information structure in terms of data entities and their relationship using architectural style.
The data model in principal describes the structure of data entities and their relationships. Like in our case — Vehicle insurance, entities will include Customers, Insurance policy, Employees. Customer has several attributes, as costumer number, address, status and number of insurance policy. With architectural view we first draft very little detail Silverston, By each additional step in the process we gain more data and more details.
To differ this different stages organizations use qualifiers. The model focuses on the entities and their relationships and properties that are imbedded in the problem. Best use for communication with stakeholders. Is a step from conceptual data model to a data management technology relation databases and is subject of normalization.
This is a model with implementation of data entities. With optimizations that have partitioning or merging entities, duplicating data, creating identification keys and indexes.
Entity Relationship Diagram Example: Car Insurance
All models conceptual, logical and physical are seen in Figure 2, for better idea how models look like, though physical data model in general is not considered architectural Merson, Figure 2: Graphical presentation of Conceptual model Fig. As a group we decided on various rules that need to be implemented in order for the model to be consistent and precise.
Table 2 below illustrates these rules. These assumptions will help shape our model to allow consistency within our design. Table 3 presents the assumptions used in this model. Table 4: Entity types used in car insurance data base system CDM model.
These assumptions and explanations are illustrated in Table 5 below. First we had to make some changes and improvements to the conceptual data model which are explained and presented in last part of this report.
Then we identify all the attributes in old and new entities and assigned them the primary PK and foreign keys FK and made relationships with them in Erwin to make a full LDM. We identified each variable and the data types that this LDM could be used to design the database in Access or Oracle data base management systems.
This is any distinguishable object that presents part of data base. It can be related to any object in real world such as: a car, a customer persona policy, a company, etc. Properties of entities can have values: - Name - Description of the meaning and significance - Weather entity is dependent or non-dependent - List of attributes Car entity: year, manufacturer, model, mileage, owner, licence, book of maintenance with properties data type, size, is it required or not.
Relations Relationship - Designates logical association between entities, with cardinality of the participant entities: one-to-one, one-to-many, or many-to-many relationships. Relationships can be identifying or non-identifying identifying A-B; existence of B depends on existence of A. Fo e a ple department entity is a generalization of different types of departments; at the same time vehicle insurance department or travel insurance department is specialization of department entity.
Aggregation - is an abstraction that turns relationship between entities into an aggregate entity, rarely used. Example: customer-insurance advisor -date can be an aggregate entity called Appointment.
A Entity Relationship Diagram showing car-insurance company. You can edit this Entity Relationship Diagram using Creately diagramming tool and include in. The entity-relationship diagram of Car Insurance Management System shows all the visual instrument of database tables and the relations. Construct an E-R diagram for a car insurance company whose customers own one or more cars each. Each car has associated with it zero to any number of.
Constraints The database normalization technique is used to impose restrictions on data model that is based no dependencies between entities and their attributes. Normalization is used with the goal objective to avoid duplication of information in order to safe guard the consistency integrity of the data.
Data types When we assign attributes to entities with primary keys and foreign keys do the normalization, we identify each attribute with data type for each data management system — Access and Oracle as seen in example Table 6, below. For better overview we presents the table number to the corresponding entity type, followed by the business rule of what we wish the entity type to capture, posted below in Table 7.
Therefore physical data model is used to implement into different technical software and hardware environments that is due to current state of technology and is changing as technologies change.
It means that physical model design done five or ten years ago is outdated today Speelpenninget al. If the correct entity model is being build will conform to the rules of normalization. Each rule has corresponding data model interpretation, which can be used to validate placement of attributes in ER model, see Figure 6 Speelpenninget al. Therefore you have to keep track of them and find how to implement them in correct way, see Figure 7.
Car-Insurance Company ( Entity Relationship Diagram)
This change also means change of terminology Speelpenninget al. You must be aware that there is no absolute truth here. These types define generic domain of values that each column can contain, see Figure 9. Choosing a large fixed length for a column to only store a few bytes per row, makes a large table.
Maximum size is bytes. Maximum size isand minimum is 1.
Question: Construct an ER diagram for car insurance company that has a set of customers Mumbai University > Information Technology > Sem 3 > Database. premium_payment payment_no due_date amount received_on payment accident report_id date place participated. Figure E-R diagram for a car insurance. This diagram describes the entity relationship for a Car- Insurance Company. The Customers own one or More cars each. Each car has 0 or more accidents.
This is the most commonly-used data type and you should use it if you are not sure which one to use. This data type is used for data on which calculation or sorting should be possible. Avoid its use for numbers like a phone number, where the value does not have any meaning.
Typical use: amount of money, quantities, generated unique key values. A date data type also contains time components.
You should use it only when you know the full date including day, month, and year. The time component is often set to midnight in normal use of dates. Typical use: any date where the full date is known. Obsolete since Oracle8. Was used for ASCII text files where you do not need to search using the wildcard or substring functionality. Use CLOB data type instead. Was used for large object types where the database should not try to interpret the data.E - R Model Library Management System DBMS lec - 4
Use BLOB data type instead. Typical use: images or video clips. View All Premium Projects. Project Category. The entity-relationship diagram of Activity Management System shows all the visual instrument of database tables and the relations between Users, Timeslots, Activity, Particiapants etc.
It used The entity-relationship diagram of Library Information System shows all the visual instrument of database tables and the relations between Book Maintenance, Membership Management, Student, Member etc The entity-relationship diagram of Examination Management System shows all the visual instrument of database tables and the relations between Examinations, Courses, Students, Faculties etc.
The entity-relationship diagram of Patient Management System shows all the visual instrument of database tables and the relations between Doctor, Diease, Patient, Medicine etc.
Construct an E-R diagram for a car-insurance company whose customers own one Consider a database used to record the marks that students get in different . Terminology mapping – ER Model to Physical design. 8 Table 2: Design rules for CDM model of car insurance database. FREE Online ER Diagram example: 'Car Insurance'. Learn about database design with ERD. Draw Free ERD with online ERD software. Sign up to create a free.
It used structure data and The entity-relationship diagram of Garment Inventory System shows all the visual instrument of database tables and the relations between Inventory, Garments, Brands, Customers etc. It used structure data