DATABASE MODELING AND NORMALIZATION
Assignment 4: Database Modeling and Normalization
The Public Government of Sugar Hill in Georgia (PGSH) has requested an optimized
data repository for its current system which will enable the management staff to perform
essential human resources (HR) duties along with the capability to produce ad hoc reporting
features for various departments. They look forward to holding data that will allow them to
perform core HR functions such as hiring, promotions, policy enforcement, benefits
management, and training. Best Database Consulting (BDBC) has been awarded the contract to
implement this new personnel system for PGSH. As part of the agreement we will be listing the
process of the implementation in the following areas: (1) an efficient Entity Relationship Model
(ERM) Diagram, (2) risks of not following with the designing steps for the ERM Diagram, (3)
entities, (4) time-variant data, (5) Diagrams, (6) normalization and (7) dependencies.
An Effective Entity Relationship Model Diagram
A conceptual data model which defines the domain regarding entities, attributes and
relationships are called an entity-relationship (ER). On an entity-relationship diagram (ERD)
entities are represented as rectangles, attributes as ellipses and relationships between entities as
diamonds (Chen, 1976). To have an efficient ERD, there are definitive steps that need to be
addressed and is key that they are covered in a specific order. Although they are not set in stone,
once identified the design flow needs to be followed. The steps that BDBC will follow to
determine PGSH’s ERD will be the following:
Identify the entity types and assign a noun to each one.
Identify relationships amongst the entities and assign a verb to identify them.
Recognize the cardinality and optionality of the relationships.