CIS 515: Strategic Planning for Database Systems : Database Modeling and Normalization

Study of strategic database planning, modeling, and normalization.

Michael Davis
Contributor
4.3
34
10 months ago
Preview (4 of 12 Pages)
100%
Log in to unlock

Page 1

CIS 515: Strategic Planning for Database Systems : Database Modeling and Normalization - Page 1 preview image

Loading page ...

DATABASE MODELING AND NORMALIZATION1Database Modeling and NormalizationName:Prof:CIS 515: Strategic Planning for Database SystemsDate:Explain the process of developing an effective Entity Relationship Model (ERM) for apersonnel database, including key components such as entities, relationships, attributes, andconstraints. Discuss the iterative steps required for its development, the potential risks associatedwith not following these steps, and the importance of time-variant data for policy enforcementand training management. Additionally, explain the normalization process to ensure the databaseis in 3NF, and illustrate the five entities necessary for sustaining the personnel database solution.Your response should be approximately 1200-1500 words.

Page 2

CIS 515: Strategic Planning for Database Systems : Database Modeling and Normalization - Page 2 preview image

Loading page ...

Page 3

CIS 515: Strategic Planning for Database Systems : Database Modeling and Normalization - Page 3 preview image

Loading page ...

DATABASE MODELING AND NORMALIZATION2Steps in the development of an effective Entity Relationship Model (ERM) Diagram andthe possible iterative steps / factorsAn entity relationship model or ERM isatype ofgraphical diagram whererelationshipsbetween entities in a database are being shown.Below here is an example diagram of ERM:As ERM is an iterative process it needs replication of processes and procedures. Thereare three main components in ERM and they are:EntityInERMdatabase designing entity can be many things. It can be somebody, canbe some place, an object or event, or even can be a concept where data is collected or saved. Asanexample, ifa personaccepts some data informationfor a business,thenentities would includeconsumersand also their address, and orders.In databaseentity islabelled with a singular nounand characterized by a rectangle.RelationshipRelationshipsymbolizeslinkbetween entities and/orentity types.Simplywe can say itis the interactionamongthe entities.For an example,aconsumer places an order,thenthe word "places"highlightsthe relationship between theinstance of a customer and theorder thatthe personplaced.Usually relationships are beingrepresented by a diamond shapeorjust by a simpleline connecting the entities.

Page 4

CIS 515: Strategic Planning for Database Systems : Database Modeling and Normalization - Page 4 preview image

Loading page ...

DATABASE MODELING AND NORMALIZATION3Attribute (s)An attribute is a property of an entity that is of interest to the business.For an example, “aperson”entitycan be described by name, dateof birth, SSN, address, genderetc.These description works asattributesfor the entity andeachattributes haveaspecificvalue.Attributesare classified by followingdimensions:Simple/atomicvs. compositeSingle-valuedvs. multi-valued (or set-valued)Storedvs. derivedConstraints (Cardinality)Constraint of ERM are mainly a representationof a relationpresentingnumber of instances of one entity related to number of instances of another entity.Simply it isthebondbetween the entities in terms of numbers.For example, a salesperson mayhavezero customers or mayhave one ormorecustomers. Another example could beone ordershould contain at least oneproduct.Among different type of cardinalitynotation, crow's foot notation is a common one. Inthisnotation, a single bar indicatesone,a doublebar indicates one and only one,a circleindicates zero, and a crow's foot indicates many.Draw Rough ERDIn this step entities are written inrectangles andrelationshipsareondiamond orline segmentsand connecttheentities.
Preview Mode

This document has 12 pages. Sign in to access the full document!