P roject L ogical Model
Employee Management system
Submitted To:
Sir . Faisal Hafeez
Submitted By:
Kashif Iqbal
Muneeb Hamza
Roll No:
Ul-bsitm-a-23-83
Ul-BSITM-A-23-!3
Subject:
Database Administrator and Management
Employee Management System :
Designing the Logical Data
Model Objective: Convert the conceptual data model into a logical data
model suitable for implementation in a relational database.
Normalization:
Apply normalization techniques to ensure the data
model is free from redundancy and anomalies. Data Types: Define
appropriate data types for attributes (e.g., INT, VARCHAR, DATE).
Keys:
Identify primary and foreign keys for each entity.
Constraints:
Add constraints (e.g., NOT NULL, UNIQUE) to ensure
data integrity. Logical Data Model Design The logical data model is
derived from the conceptual ER diagram and provides a structured
relational schema. It expands on the conceptual model by refining the
attributes, defining primary and foreign keys, applying normalization up
to 3NF, and assigning appropriate data types and constraints. Each entity
and relationship from the conceptual ERD is mapped to a relational table
with clearly defined attributes, keys, and relationships.
Below is a breakdown of each table in the logical model:
Table:
EMPLOYEE
o Emp_ID (INT) [Primary Key, NOT NULL]
o Name (VARCHAR(100)) [NOT NULL]
o Gender (VARCHAR(10)) [NOT NULL]
o DOB (DATE) [NOT NULL]
o DOJ (DATE) [NOT NULL]
o Address (VARCHAR(255) [NOT NULL]
o Dept_ID (INT) [Foreign Key]
Table:
DEPARTMENT
o Dept_ID (INT) [Primary Key, NOT NULL]
o Name (VARCHAR(100)) [NOT NULL]
o Location (VARCHAR(100)) [NOT NULL]
o Manager_ID (INT) [Foreign Key]
Table:
PROJECT
o Project_ID (INT) [Primary Key, NOT NULL]
o Name (VARCHAR(100)) [NOT NULL]
o Location (VARCHAR(100)) [NOT NULL]
o Dept_ID (INT) [Foreign Key]
Table:
DEPENDENT
o Dependent_ID (INT) [Primary Key, NOT NULL]
o Emp_ID (INT) [Foreign Key]
o Name (VARCHAR(100)) [NOT NULL]
o Gender (VARCHAR(10)) [NOT NULL]
o Relationship (VARCHAR(50)) [NOT NULL]
Table:
WORKS_ON
oEmp_ID (INT) [Foreign Key]
oProject_ID (INT) [Foreign Key] - Hours (INT) [NOT
NULL]
Conclusion The Logical Data Model of the Employee Management
System is now in 3rd Normal Form (3NF) and ready for implementation
in a relational database. All entities, attributes, and relationships have
been properly structured and constraints are enforced to ensure data
consistency and integrity. Please refer to the conceptual ER diagram for
the visual representation of the model.
▁▂▄▅▆▇█THANKS█▇▆▅▄▂▁