0% found this document useful (0 votes)
9 views14 pages

College Management System

The document outlines a College Management System that includes various roles such as admin, instructors, and students, detailing their interactions with departments and courses. It specifies requirements for managing user accounts, course enrollment, and person details, while ensuring data integrity through normalization principles. The system's design includes unique identifiers for departments, courses, instructors, and students, with a focus on maintaining third normal form in its database structure.

Uploaded by

THE UNIQUE WEY
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views14 pages

College Management System

The document outlines a College Management System that includes various roles such as admin, instructors, and students, detailing their interactions with departments and courses. It specifies requirements for managing user accounts, course enrollment, and person details, while ensuring data integrity through normalization principles. The system's design includes unique identifiers for departments, courses, instructors, and students, with a focus on maintaining third normal form in its database structure.

Uploaded by

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

College Management System

Group Members

BT21CSE194 BT21CSE195
GYANBARDHAN M AZEEM KHAN

BT21CSE198 BT21CSE202
HIMANSHU SINGH YASH PATIDAR
Problem
Statement
A college contains many departments. Each
department can offer any number of courses.
Many instructors can work in a department, but
an instructor can work only in one department.
For each department, there is a head, and an
instructor can be head of only one department.
Each instructor can take any number of courses,
and a course can be taken by only one instructor.
A student can enroll for any number of courses
and each course can have any number of
students. Requirements other than the above can
be added.
Requirement Analysis

1 Admin 2 College
The admin has overall control and can Departments
perform all administrative tasks, including The college consists of multiple
editing, deleting, and updating information departments, each with a unique
across the entire system. This role is department number and name.
responsible for managing user accounts,
overseeing departments, instructors,
courses, students, and person details.

3 Instructors and 4 Students and


Courses Courses
Instructors work in a single department and Students can enroll in multiple courses, and
can offer multiple courses within their each course can have multiple students.
department.

5 Person Details
Each person has a first name, last name, date of birth, and gender.
Assumptions

Every department has a unique Department Number and Department Name.


Every course has a globally unique Course ID and Course Name.

A person in general (instructor or student) has a First Name, Middle Name


(optional), Last Name (optional), Date of Birth, and Gender.
A person may have one or more Phone Numbers.
Every instructor, in addition, has a unique Instructor ID and Pay Scale.
Every student, in addition, has a unique Student ID.
Both instructors and students have a saved Password Hash required for login.
Every course has a count of the Hours per Week it is taken by its instructor.
Every course associated with a student has a record of the Attendance and
Marks obtained by the student in that course.
ER Diagram
Relational Schema Diagram
Normalization
FIRST NORMAL FORM
In all tables, every attribute is
atomic and takes only one value
from its domain. Hence all are in
their First Normal Form (1NF).

SECOND NORMAL FORM


Third Normal Form
DEPARTMENT: PERSON:
DeptNo →DeptNo PersonID →PersonID
DeptNo → DeptName PersonID → FirstName
DeptNo → Head PersonID → MiddleName
DeptName → Head PersonID → LastName
We can remove the transitive dependency PersonID → DOB
DeptNo →DeptName → Head. PersonID → Gender
There are no transitive dependencies; relation is in
Hence, new FDs are: its Third Normal Form (3NF).
DeptNo → DeptNo
DeptNo →DeptName PHONE:
DeptNo → Head PersonID →PersonID
PersonID → PhNo
There are no transitive dependencies; relation is in
its Third Normal Form (3NF).
Third Normal Form
INSTRUCTOR: STUDENT:
InstructorID →InstructorID StudentID →StudentID
InstructorID → PassHash StudentID → PassHash
InstructorID → PersonID StudentID → PersonID
InstructorID → PayScale There are no transitive dependencies; relation is in
InstructorID → DeptNo its Third Normal Form (3NF).
There are no transitive dependencies; relation is in
its Third Normal Form (3NF). UNDERTAKES:
(StudentID, CourseID)→StudentID, CourseID
COURSE: (StudentID, CourseID)→ Attendance
CourseID →CourseID (StudentID, CourseID)→ Marks
CourseID → CourseName There are no transitive dependencies; relation is in
CourseID → DeptNo its Third Normal Form (3NF).
CourseID → InstructorID
CourseID → HrPerWeek
There are no transitive dependencies; relation is in
its Third Normal Form (3NF).

You might also like