Cloud Computing: Data Modeling & ER Diagram for Granite Sales Company

Verified

Added on  2023/04/20

|4
|540
|403
Practical Assignment
AI Summary
This assignment provides a data modeling solution for Granite Sales Company, focusing on designing an Entity Relationship (ER) diagram to represent the company's employee and department data. The solution outlines key business rules, such as the relationships between employees and departments, employee categories (salaried, hourly, and contract), and how employee compensation is structured. The ER diagram visually represents the entities (Employee, Department, SalaryCommission, EmpRoaster, Contract_Details) and their relationships, ensuring that the database accurately reflects the company's operational structure. The assignment emphasizes the importance of business rules in database design and their role in creating a reliable and efficient information model. Desklib offers a variety of resources, including similar assignments and past papers, to support students in their studies.
Document Page
Assessment 2 – Data Modelling
Granite Sales Company
Submitted By
Course
Professor
Date
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Introduction
Granite Sales Company maintains all records on staff as well as the divisions that they work in.
For every division, the name of the department, their mail box number, and office telephone
extension must be stored. Many employees can work in a department whereas one employee
can work in one department only. Employees can be categorized in three categories - salaried,
hourly and contract employees. Employees can be uniquely identified by unique employee
number. In case of hourly employees, target weekly hours will also be stored. Salaried
employee can have some commission profit which must also be saved into the database. In
case of contract employees, their contract rate with contract start date and end date will be
saved into the system. Being database administrator, my job is to prepare well defined entity
relationship diagram and then implement it correctly in Granite Sales Company.
Business Rules
Distinguishing and archiving business rules while developing and implementing database are
very important for planning a database in the organization. Business rules can enable the
developer for developing various relationship guidelines and requirements and for developing
correct information model. They additionally enable us to comprehend business processes, and
the quality, role as well as scope of the information. These guidelines are considered as a
specialized tool among clients and developer, and can help to standardize the organization's
perspective in terms of information. It is essential to recall that few of the business rules can't
be shown. Business Rules give the most ideal order of entities, properties, relations, and
Document Page
constraints. (Database management, 2018). Business rules that need to be considered while
developing database for Granite Sales Company are as following:
One employee can be assigned to one department only whereas one department can have
many employees assigned.
One employee can be of category – salaried, contractual or hourly. Therefore, employee table
will be linked to SalaryCommission, EmpRoaster and Contract_Details.
The billing rate of contractual employee will calculated according to start date and end date.
The category like employee is salaried, contractual or hourly employee will be saved in
EmpCategory attribute of employee table.
Also, profit of salaried employee will be calculated according to base salary and number of
hours he has worked.
One employee can have many contracts as after completion of contract, organization can
restart his contract. Therefore, there will be one to many relationship in Employee and
Contract_details entities.
An employee can have many details of roaster as he can have many shifts in one week. There, it
will also possess one to many relationship in employee and EmpRoaster entities.
Also, an employee can earn many profits according to his work. Hence, it will also have one to
many relationship.
Entity Relationship Diagram
Document Page
References
Business Rules. Database management 2018. Retrieved from -
http://databasemanagement.wikia.com/wiki/Business_Rules
chevron_up_icon
1 out of 4
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]