Velammal College of Engineering and Technology, Madurai – 625 009.

(An Autonomous Institution)

Department of Computer Science and Engineering

Academic Year: 2023 - 2024 (EVEN Semester)
B.E CSE - II YEAR - IV SEMESTER

21CS210 – Database Management Systems Laboratory

Mini Project
Student Database Management Systems

SUBMITTED BY,
Team member1: Roll No: ……. , Name: ……………
Team member2: Roll No: ……. , Name: ……………

Mark Splitup
S.No. Criteria Maximum Marks Marks Obtained
1. Application Complexity 05
2. Database Design 20
3. Proper Documentation 10
4. Frontend Design 05
5. Presentation 05
6. On time submission 05
Total 50

Course Skilled Course In-charge

Mrs. Arunasakthi Dr. A.M.Rajeswari
Mrs. R.Niranjana Associate Professor, CSE
 Student Database Management Systems

Assistant Professor, CSE

Team member name1, Team member name2 Page 2 of 10

 Student Database Management Systems

TABLE OF CONTENT

S.No. Title Page No.

1. Introduction

2. Application User

3. Functional Overview

4. Detailed Functional Requirement

5. Software and Hardware Requirement

6. Performance Requirement

7. Validation Criteria

8. Entities and Relationships

9. Entities and Relationship Diagram

10. Functional Dependencies and Normalization

11. Data Dictionaries

12. Database Creation and listing using MySQL

13. Establishing database connectivity through PHP

14. Conclusion

15. References

Team member name1, Team member name2 Page 3 of 10

 Student Database Management Systems

1. Introduction
This project aims to computerize the operations of the student database of an institution. Features
include managing attendance and the continuous assessment test marks of the students.

2. Application Users
The users of the system are the teaching staff, students and their parents. Teaching staff can
update the mark and attendance details of the students for the subjects they are handling. All the
users can view the details of the students like test marks, attendance and assignment mark details
of the students.

3. Functions Overview
The following functionality will be supported by the student database management system.
 Attendance updating and view.
 Marks updating and view.

4. Detailed Functional Requirements

4.1 Attendance updating and view.
Teaching staff records the attendance detail of the students for the subjects handled by them. In
case of default, attendance can be updated by the teaching staff by considering the allowable on
duty leave. Based on the attendance percentage, the students are allowed to take the semester
examinations. All the users can view the details of the attendance.
Attendance reports like monthly report, cumulative report and overall report are generated.

4.2 Marks updating and view.

Teaching staff records the mark details scored by the students in their subjects. The marks
include continuous assessment tests and assignments. All the users can view the details of the
attendance and marks scored by the student in the tests and the assignments.
Report like the marks for individual test, assignments marks for individual subjects, overall
marks scored by the students for every test, and overall internal marks obtained by the students,
their results and their Grade (CGPA) in every subject are generated.

5 Software and Hardware Requirements

Front end Tool : Netbeans 6.2
ServerSide programming : Java Servlet

Team member name1, Team member name2 Page 4 of 10

 Student Database Management Systems

Backend DataBase : PostgreSQL 9.2

6 Performance Requirements
Capacity Requirements : 5 users (student/parent/staff)
Sample Data Base Size : 10 to 20 tuples
Response time : 1micro seconds
Through put : Average transaction per minute may be 3

7 Validation Criteria
We will load the database with sample data of 15 Students, 10 Staff, 15 Subjects, 3 Tests and 3
Assignment for testing. We will test the system by finding the grade for the student.

8 Entities and Relationships

8.1 Entities
i. Department v. Attendance
ii. Student vi. Test
iii. Staff vii. Assignment
iv. Subject

8.2 Relationships
i. Sub_handle
ii. Sub_optes

9 ER Diagram

Team member name1, Team member name2 Page 5 of 10

 Student Database Management Systems

10 Functional Dependencies and Normalization

The initial relational schema from the ER diagram.

10.1 Schema
1. Department1 (dept_id, dname, block)
2. Student1 ( stud_id, sname, semester )
3. Staff ( staff_id, sname, category)
4. Subject ( sub_code, title, credit, semester )
5. Attendance (stud_id, sub_code, period, date )
6. Test (stud_id, sub_code, test_no, marks )
7. Assignment (stud_id, sub_code, ass_no, marks )
8. Sub_handle (staff_id, sub_code )
9. Sub_optes (stud_id, sub_code,)

10.2 Functional Dependencies

S.No Relation Name Set of FD BCNF Checking
1. Department1 1. dept_id → dname In FDs 3 and 4 the candidate key
is not superkey hence FDs 1 and 2
2. dept_id → block
will be considered for the relation
3. dname → block to be in BCNF , since dept_id is

Team member name1, Team member name2 Page 6 of 10

 Student Database Management Systems

the superkey and always they

4. block → dname
holds.
Among which in the FD 3 the
1. stud_id → sname candidate key is not superkey
hence FDs 1 and 2 will be
2. Student1 2. stud_id → semester
considered for the relation to be in
3. sname → semester BCNF , since s_id is the superkey
and always FDs 1and 2 holds.
In the FD 3 the candidate key
1. staff_id → sname sname is not superkey hence FDs
1 and 2 will be considered for the
3. Staff 2. staff_id → category
relation to be in BCNF , since
3. sname → category staff_id is the superkey and
always FDs 1and 2 holds.

1. Sub_code → title In FDs 3 and 4 the candidate key

is not superkey hence FDs 1 and 2
2. Sub_code → credit will be considered for the relation
4. Subject
3. title → semester to be in BCNF , since Sub_code is
the superkey and always they
4. title → credit holds.
1. stud_id, sub_code → period
2. sub_code → credit In FDs 1,2, 3 and 4 the candidate
key is not superkey hence FD 5
3. title → semester alone will be considered for the
5. Attendance
4. title → credit relation to be in BCNF , since
stud_id, sub_code, date is the
5. stud_id, sub_code, date superkey and always they holds.
→ period
In the FD 1 and 2 the candidate
1. stud_id, sub_code → marks key sname is not superkey hence
2. test_no → marks FDs 3 will be considered for the
6. Test
relation to be in BCNF , since
3. stud_id, sub_code, test_no
stud_id, sub_code, test_no is the
→ marks
superkey and always FDs it holds.
In the FD 1 and 2 the candidate
1. stud_id, sub_code → marks key sname is not superkey hence
2. ass_no → marks FDs 3 will be considered for the
7. Assignment
relation to be in BCNF , since
3. stud_id, sub_code, ass_no →
stud_id, sub_code, ass_no is the
marks
superkey and always FDs it holds.

1. staff_id →→ sub_code This relation will have

8. Sub_handle multivalued dependency which
2. sub_code →→ staff_id can’t be avoided.

1. staff_id →→ sub_code This relation will have

3. Sub_optes multivalued dependency which
2. sub_code →→ staff_id can’t be avoided.

Team member name1, Team member name2 Page 7 of 10

 Student Database Management Systems

11 Data Dictionary
Department relation:

Attribute Data Type Constraints Remarks

Dept_id Varchar(5) Primary key 3 department is considered
Dname Varchar(10) Not null Name of Department
Block Varchar(1) Not null Location of Department
Staff relation:
Attribute Data Type Constraints Remarks
Staff_id Varchar(5) Primary key Staff id
Sname Varchar(15) Not null Name of staff

Varchar(10) Type of staff

Category Not null
(Teaching, supporting)
Dept_id Varchar(5) Foreign key references department1 Refer Department id

Student relation:
Attribute Data Type Constraints Remarks
stud_id Varchar(5) Primary key Student roll number
sname Varchar(15) Not null Name of student
Current semester , the student may also be
semester Varchar(3) - in repeat course due to lack of attendance,
hence this field can also be null.

Varchar(5) Foreign key references

Dept_id Refer Department id
department1

Subject relation:
Attribute Data Type Constraints Remarks
sub_code Varchar(5) Primary key Code for each subject
title Varchar(15) Not null Name of subject

credit integer Not null Credit for each subject

semester Varchar(3) Not null subject belongs to a sem

Dept_id Varchar(5) Foreign key references department1 Refer Department id

Sub_Handle relation:

Team member name1, Team member name2 Page 8 of 10

 Student Database Management Systems

Attribute Data Type Constraints Remarks

Staff_id Varchar(5) Foreign key References Staff
sub_code Varchar(5) Foreign key References Subject

Sub_Opt relation:
Attribute Data Type Constraints Remarks
stud_id Varchar(5) Foreign key References Student
sub_code Varchar(5) Foreign key References Subject

Attendance relation:
Attribute Data Type Constraints Remarks
stud_id Varchar(5) Foreign key References Student
sub_code Varchar(5) Foreign key References Subject
period integer Not null 7 periods per day

date Date Not null Date of the period

Test_Marks relation:
Attribute Data Type Constraints Remarks
stud_id Varchar(5) Foreign key References Student
sub_code Varchar(5) Foreign key References Subject
Test_no integer - Three test for each semester

marks integer - Mark scored in each test

Assignments relation:
Attribute Data Type Constraints Remarks
stud_id Varchar(5) Foreign key References Student
sub_code Varchar(5) Foreign key References Subject

integer Two assignments for each

assign_no -
semester
marks integer - Mark scored in each assignment

12 Database Creation
- Create all the tables: Show the creation using ‘DESC’ command
- Insert the records (atleast 5 records) for all the tables: Show all the table contents using
‘SELECT *’ command.

Team member name1, Team member name2 Page 9 of 10

 Student Database Management Systems

13 Database connectivity:
- Identify functionalities for your application.
- Establish database connectivity and perform INSERT / DELETE / UPDATE / SELECT
operation through PHP / PYTHON / JAVA /etc., design the user interface (GUI – choice
is yours) for your application requirement.
- Print any one form of report generation like Ticket generation, Bill generation, etc.,
from your application (give screen shots of the report).
- Give screen shots for
1. GUI (Graphical User Interface) / Frontend Designing
2. Functionalities - Coding
3. Backend Designing
4. Reports Generations.

*************************

Team member name1, Team member name2 Page 10 of 10