DESIGN REPORT

ON

Attendance system using RFID

Submitted by
BibinJerard

4S011IS010

PrakyathRai

4S011IS039

ShafiAzeem Abdul Gani

4S011IS048

In partial fulfillment of requirement for the award of the degree

Of

BACHELOR OF ENGINEERING
IN
INFORMATION SCIENCE & ENGINEERING
Under the guidance of: Mrs.RenukaTantry
(Assistant professor,ISE Department)

DEPARTMENT OF INFORMATION SCIENCE &ENGINEERING

ST JOSEPH ENGINEERING COLLEGE

DESIGN REPORT
ON

ATTENDANCE SYSTEM USING RFID

Submitted BY:

BibinJerard

4SO11IS010

bibin1993@gmail.com9611143982____________
(Signature)

PrakyathRai

4SO11IS039

prakyathrai28@gmail.com8970440795 ____________
(Signature)

ShafiAzeem A G

4SO11IS048 shafeeazeemag@gmail.com8971896292____________
(Signature)

Under the Guidance of:

Mrs. RenukaTantry
(Assistant professor ISE department)

________________Signature with date

ATTENDANCE SYSTEM USING RFID

1. Abstract design
a. Architectural design
Here we are proposing a system which automatically takes and registers the attendance of a
student. This system uses RFID technology to register the attendance and store in the central
computer.
Instructor authentication needed
INSTRUCTOR
Adds student details
STUDENT

Student enter classroom with RFID tag

RFID TERMINAL

RFID reader reads the RFID tag

APPLICATION LAYER

Checks whether the USN number matches the student details

DATABASE SERVER

Attendance will be marked and is added to the database

b. Use case diagram

Use case diagram is used to identify the primary elements and processes that form the
system. The primary elements are called as actors and the processes are called as
use cases. Use case diagram is a graph of actors, a set of use cases enclosed by
system boundary, communication association between the actors and use cases. The
use case diagrams describes how a system interacts with the outside actors, each use
case represents a piece of functionality that a system provides to its user. The figure
below represents the use case diagram for the RFID attendance system.

instructor

HOD/ Dean
Enable RFID Tag

Register attendance

Approve Warning

Student

Admin &staff
Login Web Interface

Update Schedule

In this use case diagram, there are 4 actors as shown in the figure above,they are admin, head of the
department staff and the student

Use Case
Admin login
Registration of new student
Modify from allocated RFID
Search Student Detail
Search by RFID number
Search by Department
Filter by Date
Display all

Description
The Admin has to enter his credentials every time to
work on system.
The admin has to do one time registration into system.
The admin modify the detail of student by the allocated
RFID.
The Admin will search the student detail like student
In_time, Out_time etc.
The Admin can search unique RFID number.
The Admin can search by Department in which the
student studies.
The Admin can see total student detail on that specific
date.
The Admin see the detail of all student in that College.

2. Functional design
a. Modular design diagram
Modular design is an approach that subdivides the system into
modules that can be independently created and then used in different
system to drive multiple functionalities. Some complex system can be
broken down into simple subsystem which works together when
combined.
The modular design for RFID attendance system contains following
module:

Administrative mode:
Registering student.
Registering staff and lecturers.
Viewing and editing database and
sending information.

User mode :
Contains student and staff.
Students can only view their
attendance status.
Staff can view as well as edit the data.

RFID Attendance Registration

ADMIN MODE

Database
maintenance

Registration
of students

View database and

send information

Registration
of lecturers

b. Data flow diagram

0-level DFD:

USER MODE

Student RFID tag

Registration

Student

View attendance
status

Lecturers

Lecturers RFID
tag Registration

Modify student
Attendance

User/administrat

Syste
m

Output

1-level DFD:
Login
process
Report
generatio
n

Attendanc
e entry

Teacher
entry
Student
entry

2-level DFD:
2.1:
Administrator
Login
proces
s

After login

Data stored

Student

After login

Student
entry

Teacher
entry

data entry

data entry

Login

Data stored

Teacher

Administrator

2.2:
user
Login
process
After login
Login
Report
generati
on
data entry

Attendance
Attendance

After login
Attendanc
e entry

Report

User

Data entry

Login
Data entry

Attendance

Instructor

Student

RFID terminal

Application server

Database server

1: Instructor Authentication Needed()

2: User ID and Password()

3: check user ID and password()

4:get instructor table()

5: send instructor table()

6: Checking()
7: Success()
9: get lists of student & their RFID number()
8: system ready()
10:send list of student & RFID number()

11: Passing through RFID reader()

12: detect RFID number()

13: checking for match ()

14: Result of registration ()

15: Turn off the terminal ()

16: Send the list of numbers detected ()

18: Add absentees to database()

17: Send email notifying absent student()

Control flow design

a. Activity diagram
An activity diagram shows the overall workflow behavior of a system.
They describe the business and operational step by step workflows in a
system. Activity diagrams can show activities that are conditional and
parallel.
Fig 1.1 shows the activity diagram for the administrator. The
administrator has to register the student and staff details in the
database and generate report when required. The administrator is also
responsible for maintenance of the system and database.
Fig 1.2 shows the activity diagram for the users of the system. The user
uses the RFID tags to enter the class room/the users include the
students and the staff. Student can view his attendance by logging in
and the lecturers have the ability to view and edit.

reg of students
Reg of
teachers

Generate
reports
Maintain
database
Fig 1.1

User entry with

Check

Register in

Exit user

if not proper

Generate
report
Add to

Fig 1.2

3. Access layer design

a. ER model

Teacher ID

Subject

Month

T.name

Student id
Status

Teacher

Sem
Attendanc
e

Teaches
Belongs

Subject
Studied

S.code

S,name

Teacher id

Student

Student id

Sem

name
Course

4. Presentation layer design:

a. User Interface Flow Design
START

Enter
student

Checked IN?

no

No
sound

yes
Beep sound

UPDATE DATATBASE
EVENT LOG

STOP

Check in flow chart

STOP

START

EXIT
STUDENT

CHECKED OUT

no

Beep
Sound

yes
No sound

UPDATE DATATBASE
EVENT LOG

STOP
STOP

START

ENTER
TEACHER

CHECKED IN?

no

NOSOUND

yes
BEEP
SOUND
UPDATE DATATBASE
EVENT LOG AND
START TIMER

STOP

STOP

START

EXIT
TEACHER

CHECKED OUT

no

Beep
Sound

yes
No sound

UPDATE DATATBASE
EVENT LOG

STOP

STOP

Check out flow chart

START

SET
ALARM

UPDATE DATATBASE
EVENT LOG

FIND ID

FIND ID

yes
Sound
Alarm
STOP

b. ER model

no