DESIGN_REPORT complete.docx

DESIGN REPORT

ON

Attendance system using RFIDSubmitted 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 [email protected]____________(Signature)

PrakyathRai 4SO11IS039 [email protected] ____________(Signature)

ShafiAzeem A G 4SO11IS048 [email protected]____________(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

Adds student details

Student enter classroom with RFID tag

RFID reader reads the RFID tag

Checks whether the USN number matches the student details

Attendance will be marked and is added to the database

INSTRUCTOR

STUDENT

RFID TERMINAL

APPLICATION LAYER

DATABASE SERVER

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

Student Admin &staff

Enable RFID Tag

Register attendance

Approve Warning

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 DescriptionAdmin login The Admin has to enter his credentials every time to

work on system.Registration of new student The admin has to do one time registration into system.Modify from allocated RFID The admin modify the detail of student by the

allocated RFID.Search Student Detail The Admin will search the student detail like student

In_time, Out_time etc.Search by RFID number The Admin can search unique RFID number.Search by Department The Admin can search by Department in which the

student studies.Filter by Date The Admin can see total student detail on that specific

date.Display all 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.

b. Data flow diagram

RFID Attendance Registration

ADMIN MODE

Database maintenance

USER MODE

Registration of lecturers

Student Lecturers

Registration of students

View database and send information

Modify student Attendance

Student RFID tag Registration

View attendance status

Lecturers RFID tag Registration

0-level DFD:

1-level DFD:

2-level DFD:

User/administrator

OutputSystem

Login process

Teacher entry

Student entry

Attendance entry

Report generation

2.1:

After login After login Login

Data stored Data stored

Student data entry data entry Teacher

2.2:

After login After login Login Login

Data entry

data entry

Attendance Report Data entry AttendanceAttendance

Student entry

Login process

Teacher entry

Administrator

Administrator

user

Report generation

Attendance entry

Login process

User

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()

Instructor Student RFID terminal Application server Database server

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 diagramAn 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

Fig 1.1

if not proper

Generate reports

Maintain database

Reg of teachers

Add to database

Generate report

Exit user

Register in database

Check

User entry with tag

Fig 1.2

3. Access layer designa. ER model

Teacher

Student

Subject

Attendance

Teaches

Studied

Belongs

Teacher ID

S.code

Sem

T.name Month

Status

Teacher id

Subject

Student id

name

S,name

SemStudent id

Course

4. Presentation layer design:

a. User Interface Flow Design

no

yes

Check in flow chart

START

Enter student

No sound

Beep sound

UPDATE DATATBASE EVENT LOG

Checked IN?

STOPSTOP

no

yes

START

EXIT STUDENT

Beep Sound

No sound

UPDATE DATATBASE EVENT LOG

CHECKED OUT

STOPSTOP

no

yes

START

ENTER TEACHER

NOSOUND

BEEP SOUND

UPDATE DATATBASE EVENT LOG AND START TIMER

CHECKED IN?

STOP STOP

no

yes

START

EXIT TEACHER

Beep Sound

No sound

STOP

STOPUPDATE DATATBASE EVENT LOG

CHECKED OUT

Check out flow chart

START

SET ALARM

no

yes

b. ER model

Sound Alarm

FIND ID

STOP

UPDATE DATATBASE EVENT LOG

FIND ID