Implementation of Master Data Model for HR Database - Desklib

This article discusses the implementation of Master Data Model for HR Database in Desklib. It explains the relevance of each table and key data points. The article also highlights the importance of consistency in data integrity and no loss of data during the transfer process.

1. The master data model has been be implemented in this project. The database is based on the
process of merging the initial data base or the Master data base with the new Human Resource
data base into a single one. This needs to be completed with the implication of zero loss in the
data of the two data base. Apart from this there needs to be the consistency of the data
integrity in the system so that no connection is lost in the data. There should also be the
consideration of no loss in the data during the process of transferring of the data.
2. The entity relationship diagram shows the relation between the six tables which are to be used
for the completion of the project. The details of the employees and the customers are to be
stored in separate tables. The details of the orderdetails would be used for the connection of
the order table and the product table for each customer. The supplier is responsible for the
delivery of each of the products from the product table. All details are stored in the table for
future reference.
3. The key data points for the table are
 Employee: Stores the details of the employees working for the company. The employees are
responsible for the collection of different orders from the customers.
 Product: this table stores the details of the products which are available for sale by the
company.
 Order: this entity is responsible for the storage of the order which has been placed by the
customer
 OrderDetails: this entity is responsible for the storing of the relationship between the orders
and the product. This entity consists of the associative keys with the orderID and the
productID.
 Customer: this entity stores the details of the customers who are using the service
 Supplier: this entity is responsible for the storing of information related to the suppliers who
are responsible for the delivery of the products.
4. The values that are stored in each of the entities of the database are as follows:
 Employee stores employeeID, firstName, lastName, address, phone
 Product stores productID, productName, unitPrice, supplierID
 Order stores orderID, orderDate, totalValue, employeeID, customerID
 OrderDetails stores orderID, productID, quantity
 Customer stores customerID, firstName, lastName, address, phone
 Supplier stores supplierID, companyName, address, phone
5. Relevance of the use of each of the tables are discussed below:
 The employees are responsible for the collection of the orders from the customers
 Each product is linked to a supplier who is responsible for the products delivery.
 Order details consists of the orderID and the productID which is to be delivered
 Customers book an order from the company
 The supplier reviews the order and delivers the product.
 All details are stored in the database for reference.