1

Database Modeling and Normalization

Ramesh Amadoru

Strayer University

CIS515: (Strategic Planning for Database Systems)

Prof. Rong Shi

This study source was downloaded by 100000781515250 from CourseHero.com on 08-05-2021 05:35:36 GMT -05:00

https://www.coursehero.com/file/95094364/Week-Five-Assignment-Database-Modeling-and-Normalizationdocx/
1. Determine the steps in the development of an effective entity relationship model (ERM)

diagram and determine the possible iterative steps and factors that one must consider

in this process, with consideration of the HR core functions and responsibilities of the

client.

Introduction

The visual representation of the various entities as well as how they are representing the

relationships with each other will illustrate through the Entity Relationship Diagram (ERD). The

Entity Relationship Diagram (ERD) is also knowing as Entity Relationship Modals (ERM).

Although Data Modeling has a long history which runs towards 1970’s, it was so unfortunate

that, there was no standard ways of modelling business processes or databases since the solutions

which was proposed and discussed were not widely adapted. Peter Chen has introduced which is

widely adapted Entity Relationship Model as well as diagramming presentation for database

design in his paper call “The Entity Relationship Model-Toward a Unified View of Data”.

The entities of the ER schemas will become tables, attributes and they are finally

converted to database schema and due to this reason, the ER diagrams are widely used to design

the relational databases and troubleshooting the defect which occurs in relational databases. The

Software engineering sector is also heavily relying on Entity Relationship Models while planning

their software projects since this can identify deferent system elements and its relationships.

The entity, attribute, and relationship are the most common elements in ER diagram and

there can be further classified based of the main element sets such as week entity, multi value

and derived attributes, week relationships, recursive relationship, as well as Cardinality and
ordinality notations which are used in Entity Relationship diagrams (ERD). (Ultimate Entity

Relationship Diagram Tutorial (ER Diagrams))

The purpose behind this report is to build an Entity Relationship Diagram (ERM) against

the core Human Resources or HR functions as well as ad hoc reporting related to the client such

as Recruitment, Promotions, Policy Enforcement, Benefits Management, Compliance Training.

Also, the process of development related to the Entity Relationship Diagram (ERM) is a

combination of Iterative and step by step process which includes three Iterations.

Iteration One:

The following steps will be processed under the Iteration one and there can be listed as

below and the Entity Relationship Diagram (ERD) must be developed against each iteration until

the Entity Relationship Diagram (ERD) is fully developed.

a. Identifying the entities and mapping those entities with real world objects such as

“Employee, Payroll, Policy” which comes from description of the HR functions.

b. Identifying the relationships that are coming from the HR functions that will

associate with identified “Employee” entity.

c. Developing a draft based Entity Relationship Diagram (ERD) using the identified

entities and relationships as well as the connections must be presented among the

entities of the draft.

Iteration Two:

In the Iteration Two the following steps will be proceeded and they can be listed as
 a. Identifying the details related to the Cardinalities’ which refers to the process

and finding number of occurrences that is related to the entity and its

relationships.

b. Identifying and define the Primary Key’s related to the entities.

c. The Entity Relationship Diagram (ERD) must be updated based on the identified

Primary and Foreign keys which is in the draft mode as well as the relationships

that are precent with many to many relationships needed to be broken into

multiple one to many relationships. Also, the “Foreign keys” must be identified

within the Cardinalities’.

Iteration Three:

a. The attributes which can be in the entities as well as the possible relationships

need to be identified.

b. The fully illustrated Entity Relationship Diagram (ERD) must be developed.

c. Thoroughly recognized whether the Entity Relationship Diagram (ERD) and the

HR functionalities which are in description are binding with each other. (Iterative

Process for Generating ER Diagram from Unrestricted Requirements)

2. Analyze the risks that can occur if any of the developmental or iterative steps

of creating an ERM diagram are not performed.

The Entity Relationship Diagram (ERD) are mainly suitable for the systems that have

fully structured data. If for any reason the system has unstructured or semi-structured data sets

the implementation of proposed ERD model becomes critical. This occurs when there are

situations that has lack support of data integration. Also, integrating the Entity Relationship

Diagram (ERD) with the existing database of the organization is going to be complicated since

the data architecture is different from the Entity Relationship Diagram (ERD). Also,
 5

understanding of proper relationships which is going to be more decision makeable since Entity

Relationship Diagram (ERD) is capable of only visualizing the relational structure that going to

be applied. (What is an Entity Relationship Diagram (ERD)? - All You Need to Know)

3. Select and rank at least five entities that would be required for the development of

the data repositories.

The data repositories which are identified from the overview of the requirement and ranked

as below.

1. Employee

2. Payroll

3. Policy

4. Job

5. Training

4. Specify the components that would be required to hold time-variant data for

policy enforcement and training management.

The associated entities that are with policies and training courses which needs to be

ensured that they incorporate with “Date” or “Time” attributes will be associated with policy

changes and training outcomes. The “POLICY” table which have a relationship with the

“POLICYHISTORY” table that contains the date where the specific policy was enforced.

Also, when it come to the “TRAININGCOURSE” table that is associated with

“TRAININGHISTORY” table which contains both foreign key attributes come from

“EMPLOYEE” table. Identifying the employee who is the part of both

“TRAINSTARTDATE” as well as “TRAINENDDATE” attributes are holding the course date

This study source was downloaded by 100000781515250 from CourseHero.com on 08-05-2021 05:35:37 GMT -05:00

https://www.coursehero.com/file/95094364/Week-Five-Assignment-Database-Modeling-and-Normalizationdocx/
 information. By doing so we can ensure the accuracy of the time sensitive data which is

present within the modal. (Lucidchart)

5. Diagram a possible 1:M solution that will hold salary history data, job history,

and training history for each employee through the use of graphical tools.

(What is Entity Relationship Diagram (ERD)?)

using the selected five entities of the personnel database solution. Document each step of

the process and justify your assumptions in the process.

When considering the “Normalization of the entities related to this scenario, we can

determine whether there are any partial dependencies are presented to make tables in First

Normal Form (1NF) state by looking at the attributes. Each table is now in First Normal

Form (1NF) state since the repeating groups are eliminated through filing the required data

within the table set.

The identification of “Primary” and “Foreign” keys of each entity set has been performed

against the tables shown in “One to Many” relationship diagram in this document as well as

there are no partial dependencies among the entity set which is use in the diagram.

The “Employee” entity set is directly falling under the Second Normal Form (2NF) state

since it has only one attribute that can be considered as “Primary” key. Also, the

“Composite” key which was used in the “Training History” entity has addressed the issue of

partial dependencies within the entity set. The partial dependencies that can be in “Job

History”, “Training Course”, and “Job” entity sets has been addressed through the

“Composite Primary” key utilization.

Identifying the “Transitive” dependencies and removal needed to be done to convert the

entity sets which are in this user case and the “Employee” entity set is already in Third

Normal Form (3NF) state since the attributes such as “First name”, “Last Name” are no

longer dependent on the other entities. Also, the “TRAINENDDATE”, “JOBENDDATE”,

“COURSEDESE”, and “SALARY” attributes has no dependencies since the “Primary” key
 of this is already a “Composite” key and there are no other attributes are present in “Training

History”, “Job History”, “Training Course”, and “Job” entity sets. (Normalization)

7. Diagram at least five possible entities that will be required to sustain a

personnel solution. The diagram should include the following:

a. Dependency diagrams.

b. Multivalued dependencies.

(Normalization)
 Sources

1. Ultimate Entity Relationship Diagram Tutorial (ER

Diagrams). https://creately.com/blog/diagrams/er-diagrams-

tutorial/

2. Iterative Process for Generating ER Diagram from Unrestricted Requirements

https://www.scitepress.org/papers/2018/67787/67787.pdf

3. What is an Entity Relationship Diagram (ERD)? - All You Need to

Know https://www.edrawsoft.com/what-is-entity-relationship-diagram-

erd.html

4. Lucidchart

https://www.lucidchart.com/pages/er-diagrams

5. What is Entity Relationship Diagram (ERD)?

https://www.visual-paradigm.com/guide/data-modeling/what-is-entity-

relationship-diagram/

6. Normalization

https://condor.depaul.edu/gandrus/240IT/accesspages/normalization3.htm