1

PROJECT DOMAIN DESCRIPTION:

Student attendance management system deals with the maintenance of the student’s
attendance details. It is generates the attendance of the student on basis of presence in class. It is
maintained on the daily basis of their attendance. the staffs will be provided with the separate
username & password to make the student’s status.
The staffs handling the particular subjects responsible to make the attendance for all students.

The Domains present in this database are separated in means of students details, staff
details, time table details.

The student relation contains domains like Roll no, Name, DOB, Mobile number,
Department, Year, Address, etc….

The Staff relation contains domains like Staff code, Staff name, Subject, Password. The
Staff code and Password are use for login purpose.

The Time table relation has domains like Day and the Subjects for 1-7 periods .

DATABASE MANAGEMENT SYSTEM

2

ER MODELLING USING ER DIAGRAMS :

ER model

DATABASE MANAGEMENT SYSTEM

3

FUNCTIONAL DEPEDANCY :
a.{Roll no}{Name, Dept, Year, DOB, Mno, CStatus, Address, Eid}

b.{Staff name}{Subject Code, Password}

c.{Subject code}{Subject name}

d.{Day}{I, II, III, IV, V, VI, VII}

e.{Roll no, Period}{Present/Absent}

DATABASE MANAGEMENT SYSTEM

4

NORMALIZATION AND IDENTIFICATION OF KEYS :

Relation : Student (BCNF)

PK

Roll No Name Dept Year Address DOB M.no Eid CStatus

Relation : Staff (BCNF)

PK FK

Staff Name Subject Code Password

Relation : Attendance (BCNF)

PK PK

Roll no Date S Code Present/Absent

Relation : Subject (BCNF)

PK

S Code S Name

DATABASE MANAGEMENT SYSTEM

5

DETAILED SCHEMA OF RELATIONS :

Relation : Student

FIELDS DATATYPE CONSTRAINTS DESCRIPTION

Rollno Varchar(15) Primarykey Student rollnumber

Name Varchar(20) NotNull Student name

Dept Varchar(30) NotNull Department name

Year Number NotNull Batch year

DOB Varchar(20) NotNull Student date of birth

ADDRESS Varchar(20) NotNull Student permanent

address

MNO Varchar(20) NotNull Student mobile

number

EID Varchar(30) NotNull Student E-mail id

CSTATUS Varchar(20) NotNull Student status for

dayscholler/Hosteller

Student Details Table

Relation : Subject

FIELDS DATA TYPE CONSTRAINTS DESCRIPTION

S Code Varchar(10) Primary key Individual code for

Subjects
S Name Varchar(30) Not Null Name of the Subject

Subject Detail Table

DATABASE MANAGEMENT SYSTEM

6

RELATION : STAFF

FIELDS DATATYPE CONSTRAINTS DESCRIPTION

Scode varchar(20) Foreign Key Define Separate

subject code id

Sname Varchar(20) Primary Key Staffs name

Password Varchar(20) NotNull Staff login password

Staff Detail Table

RELATION : ATTENDANCE

FIELDS DATA TYPE CONSTRAINTS DESCRIPTION

Present/Absent Char P or A Whether student is

present or Absent
S Code Varchar(20) Foreign key Code for the Subject

Rollno Varchar(15) Foreign Key Attendance

Student Roll no

Date Date Primary Key Date for attendance

Attendance Detail Table

DATABASE MANAGEMENT SYSTEM

7

FREQUENTLY APPLIED QUERIES ON THE RELATION :

a. To Display the attendance status of a student for individual subject on a particular date .

Select Rollno, Present/Absent from Attendance where Subject code = (select Subject code
from Subject where and Sname="Subject name”) and Rollno = “Rollno” and Date = “Date”;

b. To Display the attendance status of a student for all subjects on a particular date .

Select Rollno, S Code, Present/Absent from Attendance where Rollno = “Rollno” and Date
= “Date”;

c. Display the attendance of all Students on a day for a individual subject.

Select Rollno, Present/Absent from Attendance where Date = “Date” and SCode = (Select
SCode from Subject where Sname = “Subject Name”;

d. Display total number of period attended by a student for individual subject.

Select count(*) as ThoursPresent from attendance where Rollno = “ roll number” and
SCode = (Select SCode from Subject where Sname = “Subject Name” and Present/Absent = “P”;

DATABASE MANAGEMENT SYSTEM

8

CONCURRENCY CONTROL MECHANISM :

In the proposed system concurrency control mechanisms are implemented to achieve the
following objectives

a. Two users can read any random records in parallel.

b. While one user is updating a record, no other user is permitted to read or write the
record until the first user commits his changes. This prevents dirty read.

DATABASE MANAGEMENT SYSTEM