Professional Documents
Culture Documents
Dbms Complete Projectasx
Dbms Complete Projectasx
A
MICO-PROJECT
“Design Normalized Database and ER diagram
for College”
SUBMITTED
SUCCESSFULLY FOR
SUBJECT
Database Management System
-: GUIDED BY :-
Prof. S . V . B A H A L E
Computer Engineering Department
GOVERNMENT POLYTECHNIC COLLEGE MURTIZAPUR
2020-2021
Government Polytechnic,Murtizapur
Project on
“Design Normalized Database for College”
Group Members:
-: INDEX :-
Sr.No Topic
1 Introduction
2 Features
3 Prime Features
5 Normalization
6 ER Diagram
7 Reference and
Conclusion
INTRODUCTION
6. Library Management
7. User management
8. Hostel management
9. Security Management
2. Forms
3. Reports
LOGIN:-
Login module is used to check whether the user is an
authorized person to use the systemor not.
For this the user should give the correct user name andpassword.
2. Student
3. Faculty
4.Parents
2. Maintaining system
Student:-
They have login facility to access all the information related to
their courses,marks,fee details.With the help of a userid and
password they can ensure all the relevant information.They are
assigned with an id that has all the data stored for a particular
facility.
Employee:-
They are of two types:-
1. Teaching staff
2. Non-teaching
4. Student ID Form
7. Employee ID Form
REPORTS:-
All the above mentioned data are stored in the back end andcan
be retrieved as reports with filtering options.
The Following are the reports can be taken from this system:-
1. Student Report
2. Employee Report
Entity Attributes
As we define different entities, we find that we are diggingdeeper
and deeper into details.
1. Enrolment
*ID
AcademicYear
Term: Spring/Summer/Fall
SectionID
StudentID
DateEnrolled
MidtermGrade
FinalGrade
2. Student
*ID
First Name
Last Name
College ID
Email
3. Instructor
*ID
College ID
First Name
Last Name
Rank: I=Instructor, P=Professor C=Dept. Chair
Type: F=Full Time, A=Adjunct
Department ID
4. Department
*ID
Name
5. Course
*ID
Name
Description
Type: Online/Lecture/HybridTerm:
Spring/Summer/Fall
6. Section
*ID
Name
Course ID
Schedule ID
Instructor ID
Room
We spent some time analysing "College" database and
discovered a number of useful relationships between thetables.
In practice, these relationships are established bycreation of
• Primary keys are marked by the key icons next to each ID column in every
table.
• Connecting lines show relationships between the tables. The lines have
∞ symbols next to theforeign key columns. The other side is marked
by digit "1", indicating relation to primary key in another table.
• Recall that during the database modelling stage we referred to each table
as entiy. Hence the name of the above diagram - EntiyRelationship
• The meaning of 1 and ∞ (∞ is like digit "8" on its side, indicating "infinity")
is that primary/foreign key pairs form one-to-manyrelationships. Each primary
key column can contain only oneuniquevalueidentifying one row in the table.
On the other hand, there can be manynon-uniquevaluesstored in the foreign
key column of another table. Those are the pointers back to the table
rows containing the primary key.
• Connecting columns should have values that match or compare easily,
representing the same or similar data in each of the tables participating
in the join. For example, the Department.ID column matches the
Instructor.DepartmentID column:
The following SELECT query prints instructor names and their departments:
SELECT_Example
SELECT
Instructor.FirstName,
Instructor.LastName,
Department.Name
FROM
Instructor, Department
WHERE
Instructor.DepartmentID = Department.ID
NORMALIZATION
Database normalization is the process of organizing the fields
and tables of a relational database to minimize redundancy and
dependency. Normalization usually involves dividing largetables
into smaller (and less redundant) tables and defining
relationships between them. The objective is to isolate data so
that additions, deletions, and modifications of a field can be
made in just one table and then propagated through the rest of
the database using the defined relationships.
Normalization helps eliminate redundancies and
inconsistencies in table data. It is the process of reducing
tables to a set of columns where all the non-key columns
depend on the primary key column. If this is not the case, the
data can become inconsistent during updates.
This section briefly reviews the rules for first, second, third, and
fourth normal form:-
Does it mean that the student record must keep a list of everysection
where the student is currently enrolled? Maybe. But
REFERENCES:-
1. http://www.c-
jump.com/bcc/common/Talk/SQL/SQL_20_DBdesign/SQL_20_DBdesign. html
2. http://forums.devshed.com/database-management-
46/database-design-for- college-dept-64712.html
3. www.slideshare.net
CONCLUSION:-
This case study incorporate all activities required to access college database.It
provides all necessary information to the management as well as the student withthe
use of this system. The user can simply sit in front of the system and login using id
and password to monitor each and every query related to college without any physical
movement of file.Database can service the student faculty requests best in time.
The system provides quickly and valuable information.The modules have beenintegrated
for effective use for future forecasting and for the current need.
A self-driven module in the proposed system will accomplish the automated taskssuch
as:-email alerts, sms alerts and notification to the administrator etc.