Entity Relationship Diagram

This document discusses the creation of an Entity Relationship Diagram (ERD) for a case study. It includes the business rules for the database, the entities, attributes, relationships, and cardinality described by the rules.

Running head: ENTITY RELATIONSHIP DIAGRAM
Entity Relationship Diagram
Name of the Student:
Name of the University:
Author Note

1
ENTITY RELATIONSHIP DIAGRAM
Task 1: Write all possible business rules for the above case study.
The business rules for the database which is to be developed for the organization are
provided below:
 The database should be able to store the names of all the department in the
organization.
 The departments in the organization are to be identified by the department id which
would provide the other details of the department related to it.
 The system should also be able to store the details of the employees in the system.
The employees would be identified by their unique id that would be providing all the
details of the employees.
 There are three types of employees for the organization. The three type of employees
in the organization are salaried employees, hourly employees, or contract employees.
The database should not be storing any other type of employees in the system.
 The database should be able to store the details of the salesperson in the system. The
salesperson are the employees who are already present in the system. All the
salesperson in the system are employees whereas all the employees in the system are
not salesperson.
 The database should be able store the details of the sales that are taking place in the
system. The database should also store the details of the commissions for each of the
salesperson in the organization. The details of the commissions are stored in the
commission table identified by the unique commission id.
 The database also stores the information about the contacts in the contacts table of the
system. The details are identified by the unique contact id for each employee.

2
ENTITY RELATIONSHIP DIAGRAM
 There are a number of employees for a single department however a single employee
belongs to a single department only. Hence the mapping in the database are done
accordingly.
Task 2: Create an ERD (using a specialization hierarchy if appropriate)
that represents the entities, attributes, the relationships between entities,
and the cardinality and optionality of each relationship that are described
by this business rule.
Figure 1: Entity Relationship Diagram of the Granite Sales Company
Source: (Created by Author)

3
ENTITY RELATIONSHIP DIAGRAM
Bibliography
Cagiltay, N. E., Ozcelik, E., & Ozcelik, N. S. (2015). The effect of competition on learning in
games. Computers & Education, 87, 35-41.
Al-Btoush, A. A. S. (2015). Extracting Entity Relationship Diagram (ERD) from English
Sentences. International Journal of Database Theory and Application, 8(2), 35-244.
Elmasri, R., & Navathe, S. (2016). Fundamentals of database systems. London: Pearson.
Mohammed, M. A., kareem Muhammed, D. A., & Abdullah, J. M. (2014). Practical
Approaches of Transforming ER Diagram into Tables.
Katayama, S., & Matsunawa, A. (2018, September). Solidification microstructure of laser
welded stainless steels. In International Congress on Applications of Lasers & Electro-Optics
(Vol. 1984, No. 2, p. 60). Laser Institute of America.
Arora, Siddharth, V. Venkataraman, A. Zhan, S. Donohue, K. M. Biglan, E. R. Dorsey, and
M. A. Little. "Detecting and monitoring the symptoms of Parkinson's disease using
smartphones: a pilot study." Parkinsonism & related disorders 21, no. 6 (2015): 650-653.