Scribd
Upload
24 views9 pages

Ums Dbms Project

Uploaded by

gcstock50
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
24 views9 pages

Ums Dbms Project

Uploaded by

gcstock50
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Name Mahad yousaf(7451) , Ali hashim(7227)

Project Dbms
PROJECT :

UNIVERSITY MANAGEMENT SYSTEM

Creating a University Management System involves handling data about entities like
Students, Faculty, Courses, Departments, and more. Here's a detailed plan with an ERD,
relational model, and normalization:

A University Management System (UMS) is a software application designed to


manage the operations of a university. It facilitates effective communication and
administration between students, faculty, and administrative staff. This case study
highlights the requirements, design, and implementation of a UMS for a university.
Case Study: University Management System

Stakeholders
1. Students: Register for courses, view grades, and access schedules.
2. Faculty: Manage courses, track student performance, and submit grades.
3. Administrators: Oversee operations, generate reports, and manage data
integrity.
4. IT Staff: Maintain the system and ensure its security and availability.
_____________________________________________________
Entity-Relationship Diagram (ERD)
Entities and Attributes:
 Student:
o Student_ID (PK)
o Name
o Email
o Phone
o Address
o Department_ID (FK)
 Faculty:
o Faculty_ID (PK)
o Name
o Email
o Phone
o Department_ID (FK)
 Course:
o Course_ID (PK)
o Course_Name
o Credits
o Department_ID (FK)
 Department:
o Department_ID (PK)
o Department_Name
 Enrollment:
o Enrollment_ID (PK)
o Student_ID (FK)
o Course_ID (FK)
o Grade
 Teaching:
o Teaching_ID (PK)
o Faculty_ID (FK)
o Course_ID (FK)
o Semester

Creating a University Management System involves handling data


about entities like Students, Faculty, Courses, Departments, and more.
Here's a detailed plan with an ERD, relational model, and
normalization:

1. Entity-Relationship Diagram (ERD)


Entities and Attributes:
 Student:
o Student_ID (PK)
o Name
o Email
o Phone
o Address
o Department_ID (FK)
 Faculty:
o Faculty_ID (PK)
o Name
o Email
o Phone
o Department_ID (FK)
 Course:
o Course_ID (PK)
o Course_Name
o Credits
o Department_ID (FK)
 Department:
o Department_ID (PK)
o Department_Name
 Enrollment:
o Enrollment_ID (PK)
o Student_ID (FK)
o Course_ID (FK)
o Grade
 Teaching:
o Teaching_ID (PK)
o Faculty_ID (FK)
o Course_ID (FK)
o Semester

ERD Structure:
We'll have relationships such as:
 "Belongs to" between Student and Department.
 "Belongs to" between Faculty and Department.
 "Offers" between Department and Course.
 "Enrolls in" between Student and Course (via Enrollment).
 "Teaches" between Faculty and Course (via Teaching).
ENTITY RELATIONSHIP DIAGRAM ( ERD )
NORMALIZATION

Step-by-Step Normalization
Unnormalized Form (UNF):
Initially, data is unorganized and might contain repeating groups or arrays.
Example Table:
STUDENT_I Student_Nam Department_Nam Course_I Course_Nam
D
Grade
e e D e
S001 Alice Computer Science C101 Databases A
S001 Alice Computer Science C102 Java B+
S002 Bob Mathematics C103 Algebra A-

First Normal Form (1NF):


1. Remove repeating groups:
o Each attribute must contain atomic values.
o Create a separate row for each instance of repeating groups.
Normalized Table:
Department_Nam
Student_ID Student_Name Course_ID Course_Name Grade
e
S001 Alice Computer Science C101 Databases A
S001 Alice Computer Science C102 Java B+
S002 Bob Mathematics C103 Algebra A-

Second Normal Form (2NF):


1. Remove partial dependencies:
o All non-key attributes should depend on the entire primary key.
o For composite primary keys, separate tables to ensure attributes are
only dependent on the relevant part of the key.
In this example:
 Composite Primary Key: Student_ID, Course_ID.
 Student_Name and Department_Name depend only on Student_ID.
Break into two tables:
Student Table:
Student_ID Student_Name Department_Name
S001 Alice Computer Science
S002 Bob Mathematics
Course Enrollment Table:
Student_ID Course_ID Course_Name Grade
S001 C101 Databases A
S001 C102 Java B+
S002 C103 Algebra A-

Third Normal Form (3NF):


1. Remove transitive dependencies:
o Non-key attributes should not depend on other non-key attributes.
o If Department_Name is dependent on Department_ID, separate it into
a Department table.
Break into additional tables:
Student Table:
Student_ID Student_Name Department_ID
S001 Alice D01
S002 Bob D02
Department Table:
Department_ID Department_Name
D01 Computer Science
D02 Mathematics
Course Enrollment Table:
Student_ID Course_ID Grade
S001 C101 A
S001 C102 B+
S002 C103 A-
Course Table:
Course_ID Course_Name Department_ID
C101 Databases D01
C102 Java D01
C103 Algebra D02

Final Normalized Tables


1. Student Table:
o Attributes: Student_ID (PK), Student_Name, Department_ID (FK).
2. Department Table:
o Attributes: Department_ID (PK), Department_Name.
3. Course Table:
o Attributes: Course_ID (PK), Course_Name, Department_ID (FK).
4. Course Enrollment Table:
o Attributes: Student_ID (FK), Course_ID (FK), Grade.
5. Faculty Table (Optional for faculty details):
o Attributes: Faculty_ID (PK), Name, Department_ID (FK).
6. Teaching Table (Optional for faculty-course assignments):
o Attributes: Teaching_ID (PK), Faculty_ID (FK), Course_ID (FK),
Semester.

You might also like