Car Insurance Entity Relationship Diagram
SC3306 Unit 1 Assignment
By XXXX XXXXX
University of the People
January 31, 2017
Introduction
The following analysis document provides an entity relationship (E-R) diagrams in support of a car-insurance company requirements as detailed in the assignment statement.
Assignment Statement
In Unit 1, we are introduced to database systems. For your written assignment: 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 recorded accidents. Your response must be complete and in your own words with conclusion and title page.
Analysis Considerations
I have chosen to stick closely to the three entity requirements as outlined in the Assignment Statement since this course is about how to do an E-R diagram rather than a mandate to build a perfect car insurance system. Initially entities, attributes, constraints, and comments are captured in a series
…show more content…
The first E-R diagram follows the standard notation in the course material. The second shows the same material (although with more detail) using the crows foot notation. When assessing use the notation closest to the solution set when evaluating this assignment.
Break down of Entities, Attributes, types, and constraints.
Customer In a more refined model customer should be linked to a Policy entity. A separate driver entity could also be created. customer_id integer Not null PK, unique, generated customer_ssn numeric(9,0) Not null CK, unique, could use a char(9) instead. customer_dr_num char(13) Not null CK, unique, validate through state departments customer _name Not shown on fig 2 customer_first_name char(25) Not null customer_mdl_intial char(1) null customer_last_name char(25) Not null customer_address Not shown on fig 2 customer_addr1 char(32) Not null customer_addr2 char(32) null customer_city char(32) Not null Validate city by
The ERD represents conceptualization by end users of what the database has to offer. As a database designer, it is important for you to use the ERD tool so the components, attributes, entities and relationships are clearly visible. The ERD tool will held database designers make sure they are capturing all required data and that all tables needed are built around that data.
2. using the data requirements and the business rules provided, develop a conceptual model (ERD), including attribute data types and required field lengths; and
A. Lab # : BSBA BIS245A-1 B. Lab 1 of 7 : Introduction to MS Visio and MS Access C. Lab Overview--Scenario/Summary TCOs: 1. Given a business situation in which managers require information from a database, determine, analyze and classify that information so that reports can be designed to meet the requirements. 2. Given a situation containing entities, business rules, and data requirements, create the conceptual model of the database using a database modeling tool. Scenario: You have been asked to create two conceptual database models using MS Visio Database Model Diagram Template. The purpose of this lab is to have you gain familiarity with the various modeling tools needed to create a conceptual model (entity relationship diagram) of a
A. What is the recommendation for water intake for a person of your sex and age? The recommended DRI of water intake for someone my age is 3,700g of water a day, which converts to 3.7 liters a day. During my three day analysis I consumed 865.02 grams of water.
For the first normal form stage to be reached, there are a few requirements that must be met. First, the database attributes will be checked to make sure that all the key attributes have been included within the entities. Second, each cell will contain only one value and not a group of values. A cell is the intersection between the columns and rows. Third, all of the key attributes that have been defined should be dependent on the primary key. The Riordan Manufacturing database entities contains all of the necessary attributes for each entity and each of these attributes are dependent on the primary key and each cell only contains one value. The Riordan Manufacturing database is in first normal form.
III. Mass Transportation- Encourage usage of mass transportation to improve air quality and traffic congestion.
Based on some of the responses of Unit 1 complete questions I would like to remind the class that it is very important to listen to the Attend section and read your online assigned textbook chapters in the READ section each week before completing your assignments.
Just to be clear, do you want us to discuss three different types of programs/sections (covered in Unit 3: Succeeding as an Online Learner) that are available, at our disposal, to help users acclimate to the online learning environment? Thank you for your attention to this matter.
In this figure, there are two sources of information for business: 1). Information from IW, which has passed through the ETL process before it goes to the end users. 2.) Information from independent data sources, which is processed by different standards. This is counter to the strategic goal of eliminating duplication of analysis, reporting and ad hoc analysis. This environment consumes more time for business users to understand end-user data, and more money for the firm which is wasted on different and possibly conflicting results.
Databases are the center of many technology and non-technology focused businesses. They are used in retail, healthcare, education and government. Databases are essentially in entering, storing, managing and referencing data, and can be simple in nature, or extremely complex. In order for a database to be implemented correctly, planning is required. Planning takes place from the moment of idea inception, and continues throughout multiple stages of the planning process (typically during the analysis and design phases). An Entity-relationship diagram, or ERD, is a visual layout or plan for a database. An ERD is defined as “a graphical model that shows the logical model of the data for an organization (Dischiave, n.d.).” ERDs should follow the industry standard best practices in order to be most effective and useful overall. ERDs that do not follow certain best practices, which are outlined in this paper, could cause delays, inconsistencies, or lasting problems when designing and implementing a database. ERDs should follow set business rules, follow appropriate, effective and consistent naming conventions, should clearly outline unary, binary and ternary relationships, should include attributes, entities and relationships and should be clear and easy to follow (Hoffer, 2012). The article entitled
For expecting parents, who have low income, preparing for their expected child can be very difficult. These difficult preparations have an impact on the child’s life before it is born. Parents who have low income, may not be able to afford the education they need to learn in raising a newborn child. This includes, not knowing what to feed a baby at certain ages, what to do when a baby is feeling sick, how to tell if a baby is sick, etc. Low-income parents also struggle to prepare for their newborn baby in regards to the essentials. Although the price of diapers, medicine, outfits, etc. may not seem expensive on the shelf of the store. The price is extreme when considering how much overtime needs to be bought.
The Entity Relationship diagram for the information provided in the spread sheet is shown below.
* Requirements Modeling * Input * Process * Output * Either of the following two (2) or combined, whichever are applicable:Data and Process Modeling Context Diagram Data Flow Diagram Object ModelingUse Case DiagramClass DiagramSequence DiagramActivity Diagram * Design * Output and User-Interface Design * Forms * Reports * Data Design * Entity Relationship Diagram * Data Dictionary * System Architecture * Network Model * Network Topology * Security * Development * Software Specification * Hardware Specification * Deployment Diagram * Test Plan * Testing * System Testing * Implementation Plan * Project Implementation Checklist *
This document is an entity-relationship diagram, or “ERD,” for a system to manage electronic resources. An ERD is a model that identifies the concepts or entities that exist in a system and the relationships between those entities. An ERD is often used as a way to visualize a relational database: each entity represents a database table, and the relationship lines represent the keys in one table that point to specific records in related tables. ERDs may also be more abstract, not necessarily capturing every table needed within a database, but serving to diagram the major concepts
Below is the data design diagram, which illustrates the relationship between the customer and the transaction flow of