STUDENT

EVALUATION
SYSTEM
TEAM MEMBERS
1.)ABHINAV VISHWA
2.)KARAN RAWAT
3.)PRAKHAR JAIN
4.)MOHIT KUMAR LAL
5.)SAURABH PANDEY
 E-R DIAGRAM OF OUR DATABASE
STUDENT
NAME CREDITS
NAME PHONE CGPA ID

PHOTO

ST
TEAC
FACULTY SUBJECT UD STUDENT
HES
IES

SUBJECT
DEPAR
TMENT PASSWOR
ID
D NAME
FACULT TYPE COURSE
Y
ID
PASSWORD
SCHEMA OF OUR DATABASE
TABLE FOR ENTITY 1
FACULTY

NAME FACULTY-ID PASSWORD PHONE DEPARTMEN

T
SCHEMA OF OUR DATABASE
TABLE FOR ENTITY 2
SUBJECT

NAME TYPE CREDITS SUBJECT-ID

SCHEMA OF OUR DATABASE
TABLE FOR ENTITY 3
STUDENT

NAME COURSE STUDENT- PASSWOR CGPA PHOTO

ID D
SCHEMA OF OUR DATABASE
TABLE FOR RELATION 1
TEACHES

FACULTY-ID SUBJECT-ID
SCHEMA OF OUR DATABASE
TABLE OR RELATION 2
STUDIES

STUDENT- SUBJECT- MARKS GRADE ASSIGN_1 ASSIGN_2

ID ID
PRIMARY KEYS IN THE SCHEMA
TABLE FACULTY :
FACULTY-ID

TABLE SUBJECT :
SUBJECT-ID

TABLE STUDENT :
STUDENT-ID
PRIMARY KEYS IN THE SCHEMA
RELATION TABLE TEACHES :
SUBJECT-ID
FACULTY-ID

RELATION TABLE STUDIES :

SUBJECT-ID
STUDENT-ID
FOREIGN KEYS IN THE SCHEMA
TEACHES :
SUBJECT-ID REFERENCES SUBJECT
FACULTY-ID REFERENCES FACULTY

STUDIES :
STUDENT-ID REFERENCES STUDENT
SUBJECT-ID REFERENCES SUBJECT
CONSTRAINTS IN SCHEMA
TABLE STUDIES :
CONSTRAINT
“check(assign_one in('submitted','not_submitted')),
check(assign_two in('submitted','not_submitted'))”
CHECKS FOR A ASSIGNMENT IF IT IS SUBMITTED
OR NOT SUBMITTED BY THE STUDENT BY
ASSIGNING VALUE ASSIGN_ONE OR ASSIGN_TWO
EITHER “SUBMITTED” OR “NOT SUBMITTED”.
NORMALIZATION
FACULTY
NAME FACULTY-ID PASSWORD PHONE DEPARTMEN
T

Mr. A . J . FAC_ONE 12356 9023458932 CHEMICAL

Singh ENG.

Ms. A. Singh FAC_TWO 7895 9078653421 MATHS

HOW IS IT NORMALIZED?
1 NF :
NAME, FACULTY-ID, PASSWORD, PHONE ,
DEPARTMENT ARE ATOMIC ATTRIBUTES AND
SQL QUERIES USED TO EXTRACT THEM JUSTIFIES
THEIR UNDIVISIBILITY. HENCE, THE TABLE IS IN
1 NF .
HOW IS IT NORMALIZED?
2 NF :
PRIMARY KEY IN THE TABLE FACULTY IS ONE, i.e. ,
FACULTY-ID . HENCE THERE CANNOT BE ANY
PARTIAL FUNCTIONAL DEPENDENCIES OF NON-
PRIMARY KEYS ON THE PRIMARY KEY . THIS
JUSTIFIES THE FACULTY TABLE IN 2nd NF.
HOW IS IT NORMALIZED?
3 NF :
THE NON-PRIMARY KEYS FACULTY-ID, PASSWORD ,
PHONE AND DEPARTMENT DEPENDS EXCLUSIVELY
ON PRIMARY-KEY FACULTY-ID AND THERE IS NO
TRANSITIVE DEPENDENCY OF NON-PRIMARY KEYS
ON FACULTY-ID .HENCE, FACULTY TABLE IS IN 3rd
NF .
NORMALIZATION
SUBJECT

NAME TYPE CREDITS SUBJECT-ID

DBMS COMPULSORY 3 330

ROBOTICS ELECTIVE 3 530

HOW IS IT NORMALIZED?
1 NF :
NAME, TYPE, CREDITS , SUBJECT-ID ARE ATOMIC
ATTRIBUTES AND SQL QUERIES USED TO
EXTRACT THEM JUSTIFIES THEIR
UNDIVISIBILITY. HENCE, THE TABLE IS IN
1 NF .
HOW IS IT NORMALIZED?
2 NF :
PRIMARY KEY IN THE TABLE FACULTY IS ONE, i.e. ,
SUBJECT-ID . HENCE THERE CANNOT BE ANY
PARTIAL FUNCTIONAL DEPENDENCIES OF NON-
PRIMARY KEYS ON THE PRIMARY KEY . THIS
JUSTIFIES THE FACULTY TABLE IN 2nd NF.
HOW IS IT NORMALIZED?
3 NF :
THE NON-PRIMARY KEYS NAME, TYPE , CREDITS
SUBJECT-ID DEPENDS EXCLUSIVELY ON PRIMARY
KEY FACULTY-ID AND THERE IS NO TRANSITIVE
DEPENDENCY OF NON-PRIMARY KEYS ON
FACULTY-ID .HENCE, FACULTY TABLE IS IN 3rd
NF .
NORMALISATION
STUDENT

NAME COURSE STUDENT- PASSWOR CGPA PHOTO

ID D

MAYUR IT 402 8956 8.54 Localhost/phot

SHARMA os/mayur.png

ANAND ECE 693 0982 9.01 Localhost/phot

MEHRA os/anand.png
HOW IS IT NORMALIZED?
1 NF :
NAME, COURSE, STUDENT-ID , PASSWORD, CGPA
AND PHOTO ARE ATOMIC ATTRIBUTES AND SQL
QUERIES USED TO EXTRACT THEM JUSTIFIES
THEIR UNDIVISIBILITY. HENCE, THE TABLE IS IN
1 NF .
HOW IS IT NORMALIZED?
2 NF :
PRIMARY KEY IN THE TABLE FACULTY IS ONE, i.e. ,
STUDENT-ID . HENCE THERE CANNOT BE ANY
PARTIAL FUNCTIONAL DEPENDENCIES OF NON-
PRIMARY KEYS ON THE PRIMARY KEY . THIS
JUSTIFIES THE FACULTY TABLE IN 2nd NF.
HOW IS IT NORMALIZED?
3 NF :
THE NON-PRIMARY KEYS NAME, COURSE,
PASSWORD, STUDENT-ID, CGPA AND PHOTO
DEPENDS EXCLUSIVELY ON PRIMARY KEY
FACULTY-ID AND THERE IS NO TRANSITIVE
DEPENDENCY OF NON-PRIMARY KEYS ON
FACULTY-ID .HENCE, FACULTY TABLE IS IN 3rd
NF .
NORMALISATION
TEACHES

FACULTY-ID SUBJECT-ID

FAC_ONE 330

FAC_TWO 530
HOW IS IT NORMALIZED?
1 NF :
FACULTY-ID AND SUBJECT-ID ARE ATOMIC
ATTRIBUTES AND SQL QUERIES USED TO
EXTRACT THEM JUSTIFIES THEIR NDIVISIBILITY.
HENCE, THE TABLE IS IN 1 NF .
HOW IS IT NORMALIZED?
2 NF :
PRIMARY KEY IN THE TABLE FACULTY ARE TWO,
i.e. FACULTY-ID AND SUBJECT-ID . THERE ARE NO
NON-PRIMARY KEYS IN THE RELATION TABLE.
THERE CAN’T BE ANY PARTIAL DEPENDENCY OF
NON-PRIMARY KEYS. THIS JUSTIFIES THE
TEACHES TABLE IN 2nd NF.
HOW IS IT NORMALIZED?
3 NF :
AS NO NON-PRIMARY KEYS ARE THERE IN THE
TEACHES TABLE. THERE CAN NOT BE ANY
TRANSITIVE DEPENDENCY OF NON-PRIMARY
KEYS. HENCE, TEACHES TABLE IS JUSTIFIED TO
BE IN 3rd NF .
NORMALISATION
STUDIES

STUDENT- SUBJECT- MARKS GRADE ASSIGN_1 ASSIGN_2

ID ID

402 330 91 A+ SUBMITTED NOT

SUBMITTED

693 530 78 B+ SUBMITTED NOT

SUBMITTED
HOW IS IT NORMALIZED?
1 NF :
STUDENT-ID, SUBJECT-ID, MARKS, GRADES,
ASSIGN_1, ASSIGN_2 ARE ATOMIC ATTRIBUTES
AND SQL QUERIES USED TO EXTRACT THEM
JUSTIFIES THEIR NDIVISIBILITY. HENCE, THE
TABLE IS IN 1 NF .
HOW IS IT NORMALIZED?
2 NF :
PRIMARY KEY IN THE TABLE FACULTY ARE TWO, i.e.
STUDENT-ID AND SUBJECT-ID . MARKS, GRADE,
ASSIGN_1 AND ASSIGN_2 ALL ARE
CHARACTERISTICS OF A SUBJECT OF A PARTICULAR
STUDENT. BOTH THE PRIMARY KEYS ARE
TOGETHER DETERMINING ALL THE NON-PRIMARY
KEYS OF STUDIES TABLE. THERE CAN’T BE ANY
PARTIAL DEPENDENCY OF NON-PRIMARY KEYS.
THIS JUSTIFIES THE STUDIES TABLE IN 2nd NF.
HOW IS IT NORMALIZED?
3 NF :
ALL THE NON-PRIMARY KEYS MARKS, GRADE,
ASSIGN_1, AND ASSIGN_2 ARE DIRECTLY DEPENDENT
UPON THE PRIMARY KEYS STUDENT-ID AND
SUBJECT-ID AND NO NON-PRIMARY ATTRIBUTE IS
DEPENDENT UPON ANOTHER NON-PRIMARY
ATTRIBUTE, THERE CAN NOT BE ANY TRANSITIVE
DEPENDENCY OF NON-PRIMARY ATTRIBUTES.
HENCE, STUDIES TABLE IS JUSTIFIED TO
BE IN 3rd NF .
BIBLIOGAPHY
(FOR THE DBMS PROJECT)
1.) Database System Concepts
-Abraham Silberschatz
-Henry F. Korth
-S. Sudarshan
2.) Wikipedia
3.) w3schools