Scribd
Upload
150 views30 pages

University Management System

Uploaded by

Anuj Mishra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
150 views30 pages

University Management System

Uploaded by

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

C. V.

RAMAN GLOBAL
UNIVERSITY
BHUBANESWAR, ODISHA
DATABASE ENIGINEERING CASE STUDY ON UNIVERSITY MANAGEMENT
SYSTEM
SUBMITTED BY -: (GROUP – 3)

NAME REGD.NO BRANCH


SUBHAM TARASIA 2201020743 CSIT
ARCHITA MISHRA 2201020776 CSIT
ANUJA MISHRA 2201020790 CSIT
B. SUMIT KUMAR 2201020793 CSIT

UNDER THE SUPERVISION OF DR. PRASANT KUMAR DASH


DEPARTMENT OF CSE
DATE OF SUBMISSION – ’06/05/2024’
CONTENTS
 INTRODUCTION
 RELATIONS TO CASE STUDY
 SCHEMA DIAGRAM
 RELATIONAL SCHEMA
 ER DIAGRAM
 TABLE CREATION
 CONSTRAINTS
 TABLE INSERTION
 TABLE UPDATION
 LIST OF QUERIES
INTRODUCTION
 A University Management System is a comprehensive software solution designed to streamline administrative tasks in higher
education institutions. It typically includes modules for admissions, enrollment, academic records, scheduling, student information,
financial management, and more. These systems automate processes, enhance communication between departments, faculty, and
students, and provide valuable data for decision-making. By centralizing information and workflows, they improve efficiency,
reduce errors, and enhance overall productivity.
 University management systems are chosen for several reasons:
 Streamlined Administration: They simplify complex administrative tasks such as admissions, enrollment, course scheduling, and grading,
making processes more efficient and reducing manual workload.
 Improved Communication: These systems facilitate better communication between faculty, students, and administrative staff through
centralized platforms, emails, notifications, and discussion forums.
 Data Management: They provide a centralized database for storing and managing academic records, financial data, and student information,
ensuring data accuracy, security, and accessibility.
 Challenges faced in university management systems include:
 Data Security: Protecting sensitive student and institutional data from cyber threats, data breaches, and unauthorized access is a significant
concern. Maintaining compliance with data protection regulations adds complexity.
 Integration: Integrating with existing systems and databases, especially legacy systems, can be challenging, leading to data inconsistencies
and compatibility issues.
 Cost: Implementing and maintaining a university management system can be costly, including initial investment, licensing fees,
customization, training, and ongoing support.
Relations to case study

 Relations that we have considered in our University Management System -:


1) Student
2) Hostel
3) Department
4) Course
5) Fees
6) Subject
7) Instructor
8) Exam
9) Library
10) Book
 Description about our considered tables -:

 Student - A university must have vast no. of students . So it could contain fields like-Student name ,student id, student email,
student phone number and student address.

 Hostel – All the students of the university must accommodate with the hostel facilities. So it could contain fields like- hostel id,
hostel name, and the no. of seats in available in the corresponding hostel.

 Department – A university have different departments. So it could contain fields like- department id, department name,
department HOD etc.

 Course – A university also provides different courses for the students. So it could contain fields like- course id, course name and
course duration.

 Fees – Students must have to pay yearly fees for their studies. So it could contain fields like s
 Subject – There are different subjects taught in the university. So it could contain fields like- subject id, subject name, subject
duration, subject credit and department id referred to the Department table.

 Instructor – For different subjects, different instructors have been assigned. So it could contain fields like- instructor id,
instructor name, instructor email and instructor specialization.

 Exam- Students must appear periodic examinations for the self assessment of their academic abilities, So it could contain fields
like- exam name , exam duration and exam dates , which include the exam start date and exam end date.

 Library – The university also gives library facilities, which offers a quite place to study. So it could contain fields like- the book
id along with the book name,no. of books contained and the library open timing and close timing.

 Book – Different categories of books are available in the library. So it could contain fields like- the book id, book name and the
author of the corresponding book.s
SCHEMA DIAGRAM
RELATIONAL SCHEMA

 Here are the Relational Schemas of our corresponding tables -:

1) Student ( Student_id , Student_name , Student_email , Student_phone_no , city , state , landmark )


2) Hostel ( no_of_seats , hostel_id , hostel_name )
3) Department ( department_id , department_name , department_hod )
4) Course ( course_id , course_name , course_duration )
5) Fees ( payment_id, student_id, payment_due)
6) Subject ( subject_id , subject_name , department_id , subject_duration , subject_credit )
7) Instructor ( instructor_id , instructor_name , instructor_email , instructor_specialization)
8) Exam ( exam_name , duration , start_date , end_date )
9) Library ( library_book_id , library_book_name , no_of_books , open_time , close_time )
10) Book ( book_id , book_name , author )
ER Diagram
TABLE CREATION
Constraints

 Add constraint in ‘Student’ table -:


Syntax - ALTER TABLE Student
ADD CONSTRAINT unique_email UNIQUE (Student_email);
 Add constraint in ‘Hostel’ table -:
Syntax - ALTER TABLE Hostel
ADD CONSTRAINT positive_seats CHECK (no_of_seats > 0);
 Add constraint in ‘Department’ table -:
Syntax - ALTER TABLE Department
ADD CONSTRAINT not_null_hod CHECK (department_hod IS NOT NULL);
 Add constraint in ‘Course’ table -:
Syntax - ALTER TABLE Course
ADD CONSTRAINT positive_duration CHECK (course_duration > 0);
 Add constraint in ‘Fees’ table -:
Syntax - ALTER TABLE Fees
ADD CONSTRAINT positive_amount CHECK (amount > 0);
 Add constraint in ‘Subject’ table -:
Syntax - ALTER TABLE Subject
ADD CONSTRAINT positive_subject_duration CHECK (subject_duration > 0);
 Add constraint in ‘Instructor’ table -:
Syntax - ALTER TABLE Instructor
ADD CONSTRAINT unique_instructor_email UNIQUE (instructor_email);
 Add constraint in ‘Exam’ table -:
Syntax - ALTER TABLE Exam
ADD CONSTRAINT positive_exam_duration CHECK (duration > 0);
 Add constraint in ‘Library’ table -:
Syntax - ALTER TABLE Library
ADD CONSTRAINT positive_books CHECK (no_of_books > 0);
 Add constraint in ‘Book’ table -:
Syntax - ALTER TABLE Book
ADD CONSTRAINT not_null_book_name CHECK (book_name IS NOT NULL);
Table Insertion
TABLE UPDATION
List Of Queries

 Updation in ‘Student’ table


 Updation in ‘Hostel’ table
 Updation in ‘Department’ table
 Updation in ‘Course’ table
 Updation in ‘Fees’ table
 Updation in ‘Subject’ table
 Updation in ‘Instructor’ table
 Updation in ‘Exam’ table
 Updation in ‘Library’ table
 Updation in ‘Book’ table

You might also like