Student attendence management

PROJECT

ON

STUDENT ATTENDENCE MANAGEMENT SYSTEM BY USING FINGER PRINT

Presented

BY:

Basit Bashir (18)

Asif Raza (23)

Abdur Rehman (42)

Farrukh Liaquat (9)

A project presented and submitted to the

MAM HINA ANWAR

IN

University of Education

Township Campus

Lahore.

Department of Division of Science

&

Technology

DECLARATION

We hereby declare that this project is our original work, which this applies to the best of our knowledge.

DEDICATION

This project is dedicated to the Almighty God for giving us the grace, courage and strength to complete it.

ABSTRACT

Project of attendance management system by using finger print is definitely based on the computer.

This project is used to determiner eligibility criteria of the student in order to meet the requirement of the examination.

In order to overcome the drawback of manual attending taking system, this project is developed . which reduced the time consumption and error problem.

Java is used as the programming language because of object oriented , presence of tools of debugging etc.

Java used as a front-end and MySQL used as the backend.

ACKNOWLEDGEMENTWith deep gratitude to Almighty God, who supported our project to successfully complete.

Finally, our utmost thanks and deep gratitude goes to our teacher in helping in our project.

Content:

TITLE

DECLARATION

DEDICATION

ABSTRACT

ACKNOWLEDGMENT

TABLE OF CONTENTS

TABLE OF COTENTS:

1. Introduction1.1 purpose of the project1.2 scope of the project1.3 Acronyms, Abbreviations, Definitions1.4 context of system 1.5 System functions1.6 user characteristics 1.7 General constraints1.8 Assumptions and Dependencies

2. Requirements2.1 user Requirements

2.1.1 Functional requirements

2.2 Non-functional requirements

3 Project management

project planning

3. System requirements3.1 Functional requirements3.2 Non-functional requirements

4. Sequence Diagram5. Activity Diagram6. Risk analysis

6.1 external interface requirements6.1.1 user interfaces6.1.2 hardware interfaces6.1.3 software interfaces

6.1.4 communication interfaces Requirements

7. Design constraints8. Other Requirements9. Use Case Diagram

10. System implementation11. project costing

12. Project plan

13. Quality plan14. Validation and test plan15. Configuration management plan16. Maintenance plan17. Staff development plan18. appendices19. index

Problem statement: Student attendance management system are designed which are based on the fingerprint

recognitions. Out of much identification, it is faster and manages the records of attendance for

institutes like UNIVERSITY OF EDUCATION.

Motivation and Challenges: In order to maintain the records of students for university of education with accuracy, we

will design a better attendance management system. And it is considered to be important key behind motivating this project.

In this way, this system will remove a problems of roll calling and will save the times of teachers as well as the students.

Today, fingerprint recognition is very advanced technology. We can improve fingerprint identification system by decreasing the matching time. For it, we will divide the database to one tenth.

Using Biometrics: Biometrics system uniquely identified the human so in student attendance management

system, the use of biometric is to be considered as a secure approach. Biometric system are of the following types like fingerprint recognition, voice

recognition, palm recognition and face recognition. Here we will use the fingerprint recognition. Because of its features i.e. security

What is fingerprint? On the surface of the fingertips, it is the shape of valleys and ridges.

Why we use fingerprints? Out of all biometric identification method, the fingerprints identification method are

used because it is fastest, secure , unique for every person and does not change in one’s lifetime.

As an implementation point of view, it is cheap. It is used in both civilians and forensic applications. It is mostly used because it has the greatest market shares. And energy consumption is

less as compared to other system.

Purpose of project:

The purpose of this document is to offer a detailed explanation of attendance management system by using fingerprint.

In order to provide a complete and necessary descriptions of the requirements for the attendance management system , this documents will completely explain all the functional and non-functional requirements , design decisions, design constraints , architectural design and the detailed design needed to implement the system.

Attendance management system with the purpose of developing the tradition of taking attendance path to computerized.

Other purpose is developing this type of software is to generate reports automatically within a short times. Reports automatically generation may be done in the middle of the session or at the last of session.

This system which we are going to design also helpful in protect the proxy which is almost occurs daily in the class attendance.

Scope of the project or System:

Student attendance management system by using fingerprint is developed or designed in order to replace the manual paper work.

Because of computerized system, its have the lot of benefits that is:

Free trouble to use. fast approach to enter attendance Efficient reports best user Interface highly reliable, approximate result from user

It is also helpful for parents in knowing the status of their children.

Specially, this attendance management system is designed to allow the head of proctors to manage and control by taking the students fingerprint for collecting their daily attendance.

Basically project or system scope is a system on which we installed the software . In other words, we can say that it is developed as a desktop application and it will

perform all of the activities of attendance taking for a particular institute like university of education.

Acronyms, Abbreviations, Definitions:

IEEE The Institute of Electrical and Electronics Engineers, Inc.

SRS Software Requirements Specification

UE University of education

SAMS

Student Attendance Management System

OS operating system (windows)

DBMS database management system

UI user interface

e.g for example

i.e such as or that is

id identification

info information

Context of project or System:

As a context point of view, we seen that this project or system provides some type of interaction

or relationship between the proctors and students.

Basically this project or system is used for the institutes like University of education.

This project or system used the fingerprint device of the proctor’s computer.

When the project or system used the fingerprint device of proctor’s computer, then this project

or system would be responsible for taking attendance.

After taking attendance, it will store into the embedded database.

It just requires that the students only put their fingers on the fingerprint device.

Project or System functions:

There is many advantage or benefits of this project.

First of all, it saved the times as compared to manual system.

o Because In manual system, the teacher or proctors take the attendance by calling the

students names or Roll no.

Cost is less as compared to manual cost.

It keeps the sleep time for the safety of students waiting proctors to give attendance.

It is helpful for the proctors to prepare their reports and process their data easily.

User characteristics:

Proctors or professor are system users.

For the system or project use, the proctors should have a desktop computer.

To deal with it, proctors should have the basic skills about it.

Other responsibilities or characteristic of users (proctor or professor or teacher) , is to the train

the students about the proper working of device.

For any misuse of the device, the proctor will be irresponsible.

Every day at night, the system can be used

General Constraints:

Fingerprint machine are connected with the proctor’s desktop computer.

So that’ why the response time of the system is depend on it.

There are some constraints or simply we can say that the system cannot respond or performs its

task when one of the following is occurred.

i. If the fingerprint machine which are connected to proctors desktop computer has a

problem.

ii. On the desktop computer of proctors, if the program does not performs its functionality

or corrupted.

iii. If the light has gone.

iv. If the server which are used for this product cannot work.

Others constrains may be of following:

Unauthorized users, the system will not be accessible.

The all data of attendance will be transmitted to the central database in encrypted form.

Assumptions and Dependencies:

We must have the alternatives any source, when the light is gone or main source of power is off.

There must be a backup and the proctors can easily restore it, if the system or system program

is corrupted.

If Finger print machine which are connected to our main desktop computer of the proctor is

failed, then there should be reserved finger machine in the store.

Other is followings:

To desktop computer, each professor or proctor have the access.

For each professor in the department of division of science and technology university of

education the table with login and password has been set up.

For general users, the initial login and password will be encrypted.

In order to upload the data to the central database, the time frame is the day that grades are

due to the university and one week before the start of new semester.

Once a student’s is dropped, the information associated with the student cannot be removed or

modified.

In order to implement the system, this SRS will use by the development team.

In order to connect USB peripheral device such as Fingerprint sensor , we use the USB slot.

The system will run over the existing campus network.

It is developed as a client- server application.

In client-server application, data access services are only provided by the server.

Functional Requirements:

Requirements or Scenarios for users:

In this section, we are included the set of functional requirements. Each functional requirement are

carried out with brief explanation.

a. Registration of a Student

in a database , the instructor will register each of the students name and their unique

finger print.

Later on , this information will use for the proper identification

b. Student identification

Our system will be uniquely identify each of students in the class.

When the students enters and leave the classroom, identification is done.

For a identification of students, there will require a real or specific time according to

university of education schedule.

c. Storage identified students

This system will be able to store all student information into database.

When the identification period is done, a text file is created which consist of records

of the students ‘name ‘date and timestamps for the class.

d. Display student’s name after identification and sounds.

The system is able to display the access granted message with the student’s name

when their logon was successful.

On the successes and failures of the identification, audible sound will be played.

e. Time stamping of identification.

An arrival time, exit time and date to be involved in every time he check in to make sure the student is in attendance for the entire class period.

f. identification data downloaded into the Microsoft Excel

The system will be able to download the identification data into the Microsoft Excel readable text file.

In an Excel spreadsheet, the data should be formatted.

first of all, we will include the requirement which is helpful in using the system.

For it purpose, we adopted the two steps one by one .

1. Taking attendance

2. Report generation

These both steps consist of multiple steps:

Such that:

1. Taking attendance:

Fingerprint attendance management system provides the main function of

attendance taking.

It priority is high.

It implemented by using the automated mode.

By using the automatic mode, the system will mark the attendance of students by

checking student’s fingerprint within the fingerprint device.

Fingerprint machine consist of the fingerprint sensor.

the user or students will press fingerprint sensor on the fingerprint machine in

automatic mode, then

After pressing it, the fingerprint devices will take fingerprint of the student.

Taking fingerprint will search in the database and checked either it is available or

not

If the searching fingerprint is matched in the database, then corresponding or

given id number is displayed.

On a desktop computer, a compatible fingerprint device interface and driver must be

installed for the working of the automatic mode.

Functional requirements include the two types of condition.

1. Pre-condition

2. Post-condition

Pre-condition:

All electric devices which play a important role in fingerprint student attendance management, it must be ON.

Post condition:within the latest student status, whether it is absent or present , always student attendance list is updated and all of this information is saved in the database.

Report Generation:

Student status report will be generated by the system.

NON-FUNTIONAL REQUIREMENTS:

Performance Requirements:

The software will support when multiple concurrent access user terminals.

The software will handle the textual and fingerprint information.

With the client (users) and servers running on the same machine, then the response time will be

maximum of 2 sec.

But mostly 95% transactions are proceed within the less than 5 seconds

2. Deployment.

On window or standalone operating system, the system or project should be deployable.

3. Security

No one should be allowed to tamper with data from others; Enhanced Security Sensitive data.

4. Backup

There should avoid damaging the record. A simple backup function for the whole student attendance data.

5. Data migrationThere must be a simple way to student data from one system to migrate to a new system.

Project Planning:

In planning section we set our goals and objectives of the project and also it provide an agreement between following properties. Project Sponsor, Project Manager, Project Team, Steering Committee and other person associated affected by the project

The details of the project plan vary depending on the type of project and organisation.However, most plans should include the following sections:

1. Introduction2. Project organisation3. Risk analysis4. Hardware and software resource requirements5. Work breakdown6. Project schedule

7. Monitoring and reporting mechanisms

Project organisation we describe development team people involved and their roles in the team.

System requirements:

Functional requirements Non functional requirements

For both functional and non-functional we use the some keywords i.e:

M D

O

M :

stand for mandatory requirements system something must do

D:

Stand for desirable requirements System something preferably should do

O:

Stand for Optional requirements System something may do

Functional Requirement explanation:

1. For the administrator registration process manage-without the enrollment of fingerprint new user add (by using password ):

i. With password, new user can enroll by the administrator directly.

Priority:

Its priority is M.

ii. With including password , staff information can insert by the administrator.

Priority:

Its priority is M.

iii. Staff detail including record and profile can view by the administrator.

Priority:

It’s priority is D.

iv. . the detail of staff data can edit by the administrator.

Priority:


2. Login:

i. On the system , staff and administrator can login .

3. Print report about attendance:

i. Report of staff about attendance can print by the administrator.

Priority:


ii. Daily, monthly activities report of attendance can print by the staff.

Priority:

It’s priority is D.4. Report management:

i. Report of staffs about attendance can be viewed by the administrator.

Priority:

It’s priority is M.

ii. report can be submitted by the administrator.

Priority:


iii. folder of report can be viewed by the administrator.

Priority:


iv. administrator can key in data into the form.

Priority:

Priority is M.

v. report about attendance can be viewed by the staff.

Priority:


vi. data of staff can be updated by the administrator.

Priority :


vii. in order to save the report in storage file , administrator can forward it.

Priority:


5. Storage of data management (only for the administrator):

i. data about staff can be searched by the administer.

Priority:

It’s prority is D.

ii. staff can be removed by the administrator.

Priority:

It’s priority is O.

iii. data duplication can be removed by the administer.

Priority:


` iv. If staff change their department or faculty or in any case they resign, then removal of the staff can do by the administrator.

Priority :


iv. because of some solid reasons , data transaction for the user which are selected from the range of some specific data is may delete by the administrator.

Priority:

It’s Priority is O.

v. detail about staff data can view by the administrator.

Priority:

It’s Priority is D.

vi. report of staff can view by the administrator.

Priority:


vii. The data which are deleted , the administrator can retrieve it with the help of sheet of attendance.

Priority:

Its Priority is O.

6. Data manage:

i. data about the attendance of staff can export the administrator from the database to excel format.

Priority:


ii. data about the attendance of staff can export by the staff from database to Excel format.

Priority :


Non Functional Requirements;

Requirement description:

1. Issues of usability :

i. For each time, 30 seconds is require for the both administrator and staff to be login on the system.

Priority:

It’s priorityis M.

ii. 24 hours system should able to run.

Priority:

It’s priorityis D.

iii. per staff within 3 minute , administrator should be able for their registration.

Priority:


iv. Especially For staff profile and record, system should not redundancy.

Priority :


2. Issues of security: i. As according to needed, the working of login system should be proper.

Priority:


ii. Staff and administrator have the password and ID . and both have authorization to open the storage file. Unknown or other people can not be open.

Priority:


3. Issues of Storage: i. As according to need, we can save any data.

Priority:


ii. For storage purpose, capacity of memory is not be lessen than the 50 Gigabytes.

Priority:


iii. Saving of any data either it is file or documents should be do within one minute or less than 1 minute.

Priority:


iv. Each time according to need we can view the storage document or file though simultaneously it is open.

Priority :


4. Issues about color: i. Text color black

Priority:


ii. Color is blue or white for the background.

Priority:


5. Issues about text: i. Time New Roman is used for each text.

Priority:

It’s priority is M.ii. It must be bold .iii. Font size is 12 for title.iv. And 14 font size is use for heading.

Priority :


Sequence diagram:

Activity diagram:

Risk analysis:

Risk:

Risk are those uncertain future events which occurrence probability for the

loss.

In every project, the main purpose is to identify the risk and its

management.

There will be following possible risk which can be related to the project:

1. There can be occurred crashing problem in server of the database. We are

replicated in distributed database is its each part and on the server it will

stored.

From another server , we can access the data, if the one server is crashed.

2. The weakness of the procedures security system , implementation , internal

control and design that could be exercised and result in a security.

3. For the lect student cannot mark their atttendence he forget their tag.

4. Both student attendance can be marked by the one students.

Specific requirements: External interface Requirements:

User interfaces:

First of all, User interface is providing the Login Screen.

Login screen is may be for the administrator, student Dean and proctors.

SCREEN FOR LOGIN:

Login screen is a screen that will be displayed first.

This screen will allow different users to access different screens.

On the base of their role, different users access different screen.

There will be various fields for it but mostly product associate with three types of field.

i. Username

ii. Password

iii. Role

These various field will be for the administrators, proctors, and Student Dean.

Hardware Interfaces:

In order to viewing the proper and complete screen, there is required of screen resolution of

order of at least 800*600.

Students fingerprint which are taken on the fingerprint machine are also required the screen

resolution of 800*600.

In order to generate the report with the help of printer required the same resolution as above

mentioned.

Software interfaces:

For the software interfaces, any window based operating system Microsoft SQL Server 2008 as the DBMS for database.

Communication Interfaces:

Power and communication port are viewed.

In order to connect the power, Electrical outlets are used.

For the network connection with the computer, Ethernet port is used.

Network connections with computer, Ethernet Serial port jack is used through RS232.

With extension sound box, we are connected Audio jack.

1. Design constraints

This section will design limitations that apply to the system being developed and will be adhered to give .. during the development phase of the project

Programming language:

The server program that is written in Java using the Standard Edition (SE v1.5) development kit on the computer.

Databases:

Microsoft SQL Server 2008 are used as the database management system of the system. The database is stored on the server.

Development tool:

The Eclipse 3.2 IDE and the Net Beans IDE 6.0 should be used as the primary development tools to build. On the server and the client programs

operating temperature and humidity:

The system should be functional in both indoor and outdoor environments, even though the system will be used mainly in the interior classrooms at optimum temperature (20 ~ 25 ° C) and humidity (30 ~ 40%)

standards:

The server program must run under Windows XP, Windows Vista, Linux and Mac OSX operating systems. The server requires that the Java 1.5 (or higher) Runtime Environment installed on your computer. The computer hardware specifications must meet the minimum requirements of 2.3 GHz CPU speed, 2.0GB of RAM, and at least 10 GB of hard disk space for database storage. The invigilator program must be able to function on all computers running the Java Runtime Environment installed.

Legal restrictions:

The only authority the installation of the system must approve the student dean of educational services (or an equivalent distribution).

Economic:

There is a cost of about $ 350 per class for the computer, and a cost of about $ 100 per machine fingerprint for each block (terminal). The system will be released as open source software, so there is no profit.

Sustainability:

The system is expected to live for at least 10 years or until a new version is released to replace it.

Other requirements:

Database Requirements : The system includes three databases: student, class, and instructor The student database contains student information, such as name, address and

identification number containing student. The class database contains information about classes class title, department code, and of

course include number of students. The class databases are grouped by department code and course name.

The instructor database contains information about instructors, including teaching

include name, address, password, and class.

Use case diagram:

SYSTEM IMPLEMENTATION:STEP 1 : Start the process .

STEP 2 : The student places the thumb on the scanner .

STEP 3: The thumb scanner generates code that corresponds to the thumb impression .

STEP 4: This code is linked to the code already stored in the database.

STEP 5 : If there is a match , the student ID and student name retrieved from the table students and current time is marked accordingly to the entry or exit of the students .

STEP 6 : If a match is not found, " No record of the students ' message is displayed .

STEP 7 : The total number of days present within the month is calculated.

STEP 8 : Therefore, there are no leaves taken is noted by the students .

STEP 9 : If the casual leave and sick leave taken by him more than the permitted leave then it is considered unnecessary furlough .

STEP 10 : To a new student , the administrator needs to login using the login ID and password contain .

STEP 11 : It records the data of the student as students - ID, student - , date of birth, date - of -join , and mobile -no , sex and address .

STEP 12 : Stop the execution.

Project Cost:

Price: Rs/- 30,000

Quality Plan:

In this section we check our system is working well or not .Does it face any kind of situation and fulfil the user expectation? Factors of Poor Fingerprint Quality are:

Technological

High Throughput/ Reduced Capture Time Unclean Scanner Platen

Operational

Humidity / Temperature Seasonal Change Ambient Light

Environmental

Uncooperative subject Nervous Subject

Behavioural

Dry fingers due to natural aging process Worn ridge structure due to occupation Finer ridge structure specific to a demographic group

Physiological

Application Graphical User Interface (GUI) Ease of Scanner Use / Interaction

Evaluation & its types:

As we already know evaluation is inevitable so it may be:

1. technology evaluation2. scenario evaluation

3. Operational evaluation.

Technology evaluation:

In Technology evaluation the evolution based on technology innovative. Technology evaluation in which we have to introduce new technology in our biometric project.

Scenario evaluation: The goal of scenario testing is to determine the overall system performance in a prototype or simulated application. Testing is carried out on a complete system in an environment that models a real-world target application of interest

Operational evaluation: The goal of operational testing is to determine the performance of a complete biometric system in a specific application environment with a specific target population. Depending upon data storage capabilities of the tested device, offline testing might not be possible

TESTING PLAN:

Test Case No: 1

Description: Validation of the administrator.

Expected Result: If incorrect password got an error message "Login incorrect" is displayed.

Test Case No: 2

Description: Validation of the administrator.

Expected Result: If the correct username and password given "LOGIN CORRECT" message is displayed and the control is transferred to Administrator form.

Test Case no: 3

Description: Capturing thumb impression.

Expected Result: If there is no matching record for the current thumb impression message "None of these students" is displayed.

Test Case no: 4

Description: Capturing thumb impression.

Expected Result: If matching record for the current thumb impression than attendance is marked for those students.

Test Case no: 5

Description: The Register.

Expected Result: "Registered" message appears.