Android Based Advanced Attendance Vigilance System Using Wireless Network With Fusion of Bio Metric Fingerprint Authentication

Android based advanced attendance vigilance system using wireless network with the
fusion of biometric fingerprint authentication
CHAPTER 1
INTRODUCTION
1.1. Project Description

In the recent years, biometric fingerprint authentication has become very popular to
identify an individual. It is highly secured. Different organizations use it to identify their
employees. To identify the employee, the fingerprint sensors are generally set up in front
of the entrance or exit door. In recent years, mobile phones have become one of the
popular gadgets and people can’t think of their lives without mobile phones for a minute.
So, we have developed a fusion of wireless network and fingerprint authentication system
as a mobile application. To ensure the physical presence of the employee, we need the
workplace to be connected to a router. An employee can be able to give his attendance
only if he is connected to that specific router. This ensures the physical presence of an
employee. A counter will be there in the system which will calculate the time of being
present in the workplace as long as someone is connected to the router. When an
employee leaves, the device will get disconnected and as soon as it comes into the range
of the router (Working place) it will be reconnected again and resume the counting
process where it left. The whole system is a fusion of fingerprint authentication system
and wireless router where the attendance will be started counting only after an employee
is in the router range and gets logged in through fingerprint authentication at the same
time. The log in process is session based so that an employee cannot leave the place
without the device (Smart ID) as he does not know when the device gets signed out and
needs a quick log in to resume the process. The system can supersede the traditional
attendance system through fingerprint technology as it has many advantages such as high
accuracy; optimize time complexity and router system. The system would be ideal for
implementation in different organizations for identification and authentication.
University B D T College of Engineering Page 1

1.2. Scope of the project

User authentication is one of the major factors of our system. To make sure the user is
authentic, we use their fingerprint. Bio-metric fingerprint uniquely represents a person.
Fingerprint authentication will ensure the physical presence of an employee inside the
working place. At first, the employee needs to install the required APK files of the system
to their android phones. Then an employee needs to register himself in our system with
his fingerprint and additional information such as name, employee id, phone number,
email id and address. The whole registration process will be done in front of the
administrative supervisor of the organization to maintain the accuracy. Thereafter, an
employee’s mobile phone is registered in this system through its MAC address. The
android application will fetch the MAC address from the device and send it to the server.
The counter in the system server gets initialized before starting of a working hour and it
will continue the counting process till the working hour ends. To ensure the presence, an
employee needs to give his fingerprint through his mobile phone’s fingerprint sensor
which will be allowed only after he is in the range of the router. After getting connected
to the router, the counter in the system server will get initialized and it will start counting
the amount of time the device is connected to the router. By accessing the router,
authority of the organization will see the devices connected to the router which implies
the presence of those respective employees. This is a session based log in system. If an
employee is working in an organization for 8 hours, his mobile phone will be randomly
logged out from the system 3/4 times in a day.
1.3. Problem statement

Different organizations use fingerprint authentication to identify their employees. It
diminishes the proxy giving attitude of the employees. To identify the employee, the
fingerprint sensors are generally set up in front of the entrance or exit door. Sometimes,
some employee misuses the advantage of this fingerprint sensor. An employee uses his
own fingerprint to open the door for someone else to leave. So, the fingerprint sensor
can’t ensure the presence of an employee in the workplace.

1.4. Objectives of the project

The basic aim of this project is to design an effective and secure technique for personal
authentication using biometric fingerprint with fusion of wireless network.
 To develop a smart attendance system where an android device will be used as a

smart ID card.
 To develop a mobile application in Java to ensure the attendance of an individual
employee using bio-metric fingerprint authentication.
 To develop an organization to a Wi-Fi zone so that the connection or
disconnection of the android device to the router determines the presence or
absence of the employee.
 To use counters to count the total amount of time the employee spends in the
organization.

CHAPTER 2
LITERATURE SYSTEM
2.1. Existing System
Existing system is focused on the attendance system using biometric fingerprint

authentication. It is a micro-controller based prototype which used fingerprint sensor to
take the fingerprint to identify the employee. In this system security is very less.
2.1.1. Disadvantages of the Existing System

 Centralized system-As the database is located, stored and maintained in a single
location it losses over the day-to-day activities of the organization.
 Uses Fingerprint but it is not tracking the employee whether he is in campus or
not.
 The existing system is a Micro control based system and consumes more time to
compare fingerprint if the number of employees are large.
 The existing system does not ensure the presence of employee after giving
attendance thus it is less efficient.

2.2. Proposed System

In the new proposed system, along with the identification of the employee, the entire
working place will be a Wi-Fi zone. So, the connection or disconnection of the android
device (Smart ID card) to the router will determine whether an employee is present in the
working place or not. A counter will be there into the system to count the total amount of
time an employee spends in the working place.
2.2.1. Advantages of the Proposed System

 Since the data is present in every system the proposed system is a distributed
system.
 Employee is processing the attendance in their mobile, their mobile only act as
smart ID.
 This system tracks the employee’s presence in the campus using Wi-Fi.
 Only the authenticated employee can login to the system using fingerprint
authentication. Hence it is more secure.

CHAPTER 3
SOFTWARE REQUIREMENT SPECIFICATIONS
3.1. Functional Requirements
3.1.1. Admin Web Applications

 Admin has to login using id and password.
 After login admin has to add employee details with employee fingerprint.
 Admin can check employee attendance report monthly.
3.1.2. Android Application

 After that for user login user has to connect organization Wi-Fi and give his/her id
and fingerprint, if it is matching, then login time will add into the database.
 Then to logout employee has to click the logout button, it will add logout time to
database.
3.2. Non-Functional Requirements
Non-functional requires a description and, where possible, target values of associated

non-functional requirements. Non-functional requirements detail constraints, targets or
control mechanisms for the new system. They describe how, how well or to what standard
a function should be provided. For example, levels of required service such as response
times; security and access requirements; technical constraints; required interfacing with
users' and other systems; and project constraints such as implementation on the
organization’s hardware/software platform. Service level requirements are measures of
the quality of service required, and is crucial to capacity planning and physical design.

Identify realistic, measurable target values for each service level. These include
service hours, service availability, responsiveness, throughput and reliability. Security
includes defining priority and frequency of backup of data, recovery, fallback and
contingency planning and access restrictions. Access restrictions should deal with what
data needs protected; what data should be restricted to a particular user role; and level of
restriction required, example: - physical, password, view only. Non-functional
requirements may cover the system as a whole or relate to specific functional
requirements.
Accessibility: The accessibility factor to the system depends on the availability of a

broad band connection. The access to our system is possible in places where the internet
is available.
Availability : The system has to be available anywhere and anytime whenever the user
requires the use of the system. Here we consider the issue of the service level agreement
with various domains in order to embed our system with theirs.
Deployment: The deployment is carried out in various stages such as Android

deployment, Database deployment, and deployment of the source code.
Documentation: The documentation is carried out for every stage in order to summarize
and record the result of every stage since the time the system development was started.
Efficiency: The efficiency of the system is now related in terms of the number of users
able to login. We have not provided the factor of simultaneous login because our system
is built under the cost constraint and this can be further extended and developed.
Failure management: At times of system failure the users may be puzzled about what is
the problem that is taking place in the system. So we have created various exceptions in
order to provide notifications to the users to help them assist and guide them in rectifying
the errors.
Security: We are developing our system with the view of making the password
authentication in various websites and domain. So sufficient security is provided in our
system in order to make it safe for the users usability by target user community.

Communication Interfaces: The application requires an internet connection to perform

browsing and downloading files from the internet.
Safety requirements: Application ensures that it does not download malicious and
infected links from web sites.
Security requirements: Provides automatic file checking capability to ensure the

security of mobile platform and the application.
Software quality attributes: The source code of the application is going to be open as
this is going to be open source software. It will be free for further modifications and
improvements.
3.3. Software and Hardware Requirements
3.3.1. Software Requirements
 Operating system : Windows XP Professional / Windows7

 Coding Language : Java (Jdk 1.7)
 Database : My-SQL 5.0
 Database GUI : SQLYog
 Eclipse tool : Eclipse Indigo
 Android : ADT bundle
 Smart Phone
3.3.2. Hardware Requirements
 System : Pentium IV 2.4 GHz.

 Hard Disk : 500 GB.
 Ram : 4 GB
 Any desktop / Laptop system with above configuration or higher level

CHAPTER 4
SYSTEM DESIGN
4.1. Development Methodology
4.1.1. User Interface

The layouts of the UI design are taken care of by Extensible Markup Language (XML)
which is a markup language that defines a set of rules for encoding documents in a format
that is both human-readable and machine-readable. Android platform is used to develop
the whole development system in Android Studio. Java is used for the development
purpose which is the official language of Android development and is well supported by
Android Studio.
4.1.2. Database
MySQL database is the most widely used open source server to store employee’s
information and the timing of arrival and departure. After registration of the employees
into the system, their identity is tracked by a unique key in MySQL server and is
considered as MAC ADDRESS. In MySQL server, several rows have been allocated for
different employees where they have information like name, employee ID, device’s MAC
ADDRESS (Principle key), Fingerprint sample etc.
4.1.3. MAC Address Access

The MAC Addresses of the devices are kept in the same MySQL server where attendance
procedure is authorized depending upon whether it is matched with the MAC ADDRESS
of the employee on the same server. Information about the amount of time a device is
connected to the router is retrieved from the WNetWatcher software and sent to the server
for further process.

4.1.4. Server
PHP is ued as server side scripting language to connect the MySQL database server to the
Android Studio.
4.1.5. Session Based Log In

Session-based log in is handled using random number generator in Java which is kept
random for the development purpose of the system.
Figure 4.1. Flow chart of session based login

4.1.6. Android Based Mobile Application

Android-based built-in security features like Android Application Sandbox (which
isolates the app data and code execution from other apps), application framework
(Cryptography and permissions) are used so that it can significantly reduce the frequency
and impact of application security issues. The development of the app is designed in such
a way with the default system and file permissions so that it can take difficult decisions
about security such as User-granted permissions to restrict access to system features and
user data.
Figure 4.2. Block diagram of the technical part of the system

4.2. Architectural Design
Figure 4.3. System Architecture

Figure 4.4. Flow chart of the System Architecture
4.3. Database
4.3.1. Tables
m_admin
Field Type Null Key Extra
admin_id bigint(200) NO PRI auto_increment
admin_name varchar(200) YES
admin_password varchar(200) YES
Table 4.1. The Admin table

m_employee

emp_id bigint(200) NO PRI auto_increment
emp_no varchar(200) YES
emp_name varchar(200) YES
emp_gender varchar(200) YES
emp_dob varchar(200) YES
emp_designation varchar(200) YES
emp_department varchar(200) YES
emp_email_id varchar(200) YES
emp_cell_No varchar(20) YES
emp_FP_image varchar(200) YES
emp_FP_image_feature varchar(200) YES
emp_FP_image_enc varchar(200) YES
emp_status varchar(200) YES
Table 4.2. The Employee table
m_attendance

att_code bigint(200) NO PRI auto_increment
emp_no varchar(200) YES
emp_login_date varchar(200) YES
emp_login_TimeStamp varchar(200) YES
emp_logout_TimeStamp varchar(200) YES
emp_login_status varchar(200) YES
emp_logout_status varchar(200) YES
Table 4.3. The Employee Attendance table

CHAPTER 5
UML DIAGRAMS
5.1. Dataflow Diagram

A data flow diagram (DFD) is a graphical representation of the ―flow‖ of data through an
information system. A data flow diagram can also be used for the visualization of data
processing (structured design). It is common practice for a designer to draw a context-
level DFD first which shows the interaction between the system and outside entities.
DFD's show the flow of data from external entities into the system, how the data moves
from one process to another, as well as its logical storage.
There are four symbols
i. Squares representing external entities, which are sources and destinations of data.
ii. Rounded rectangles representing processes, which take data as input, do some
operation and output the data.
iii. Arrows representing the data flows, which can either, be electronic data or
physical Items.
iv. Cylinder representing the database.
Figure 5.1. Context Analysis Diagram

Figure 5.2. Data Flow Diagram for Android App during Connecting with WI-FI
Figure 5.3. Data Flow Diagram for Android App during Disconnection from WI-FI

5.2. Sequence Diagram
Figure 5.4. Sequence diagram of the system

5.3. Use Case Diagram
Figure 5.5. Use-Case diagram for Admin
Figure 5.6. Use-Case diagram for Employee

5.4. Class Diagram
Figure 5.7. Class diagram for Admin

Figure 5.8. Class diagram for Employee

CHAPTER 6
IMPLEMENTATION
6.1. Coding
//mysql connection
package com.DAO;
public interface Global
{
public static final String JDBC_DRIVER = "com.mysql.jdbc.Driver";
public static final String JDBC_HOST_URL_WITH_DBNAME =
"jdbc:mysql://localhost:3306/db_biometric_attendance";
public static final String DATABASE_USERNAME = "root";
public static final String DATABASE_PASSWORD = "admin";
public static final String STATUS = "valid";
public static final String TRUE = "yes";
}
//global.java-Connection to the Wi-Fi network

package com.HttpClient;
public class Global

{
//static String ipaddress = MainActivity.ipAddress.trim();
//public static final String URL =

"http://"+"192.168.1.56"+":8080/BioMetricAttenDance_WebApp/Android/";
public static final String URL =

"http://192.168.43.216:8080/BioMetricAttenDance_WebApp/Android/";
public static String wifiNamee = "NOT AVAILABLE"; //Company Wi-Fi Name
//public static final String URL =

"http://192.168.1.8:8080/BioMetricAttenDance_WebApp/";
}

//home.java
package com.example.biometricattendance;
import java.io.BufferedReader;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.util.ArrayList;
import java.util.List;
import org.apache.http.HttpEntity;
import org.apache.http.HttpResponse;
import org.apache.http.NameValuePair;
import org.apache.http.client.HttpClient;
import org.apache.http.client.entity.UrlEncodedFormEntity;
import org.apache.http.client.methods.HttpPost;
import org.apache.http.impl.client.DefaultHttpClient;
import org.apache.http.message.BasicNameValuePair;
import com.HttpClient.CustomHttpClient;
import com.HttpClient.Global;
import com.database.DataBaseAdapter;
import android.widget.Toast;

public class Home extends Activity
private SharedPreferences pref;
private String empId;
private ProgressDialog progressDialog;
int n = 0;
String connectedWiFiName = "";
private DataBaseAdapter mDataBaseAdapter;
private TextView et_gender;
private TextView et_dob;
private TextView et_designation;
private TextView et_depertment;
private TextView etEmpName;
private TextView et_email;
private TextView et_phone;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_home);

if (android.os.Build.VERSION.SDK_INT > 9)
StrictMode.ThreadPolicy policy =
new StrictMode.ThreadPolicy.Builder().permitAll().build();
StrictMode.setThreadPolicy(policy);
progressDialog = new ProgressDialog(this);
Log.d("abhishek", "Its came Inside Home Activity");
mDataBaseAdapter = new DataBaseAdapter(this);
mDataBaseAdapter.open();
empId = mDataBaseAdapter.getEmployeeId();
etEmpName = (TextView)findViewById(R.id.et_empName);
et_gender = (TextView)findViewById(R.id.et_gender);
et_dob = (TextView)findViewById(R.id.et_dob);
et_designation = (TextView)findViewById(R.id.et_designation);
et_depertment = (TextView)findViewById(R.id.et_depertment);
et_email = (TextView)findViewById(R.id.et_email);
et_phone = (TextView)findViewById(R.id.et_phone);
ArrayList<NameValuePair> empIdList = new

ArrayList<NameValuePair>();
empIdList.add(new BasicNameValuePair("empId", empId));

try
String response =
CustomHttpClient.executeHttpPost(Global.URL+"GetEmloyee.jsp
", empIdList)
System.out.println("response
is>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>"+res
ponse.trim());
//Toast.makeText(getApplicationContext(), "response
is>>>>>>>>>>> " +response , Toast.LENGTH_LONG).show();
String resp[] = response.split(">")
//Toast.makeText(getApplicationContext(), "response resp[]

is>>>>>>>>>>> " +resp[1] , Toast.LENGTH_LONG).show();
String ss[] = resp[1].split("~");
etEmpName.setText(ss[0].trim());
et_gender.setText(ss[1]);
et_dob.setText(ss[2]);
et_designation.setText(ss[3]);
et_depertment.setText(ss[4]);
et_email.setText(ss[5]);
et_phone.setText(ss[6]);

catch (Exception e)
// TODO: handle exception
e.printStackTrace();
@Override
public boolean onCreateOptionsMenu(Menu menu)
// Inflate the menu; this adds items to the action bar if it is present.
getMenuInflater().inflate(R.menu.home, menu);
return true;
@Override
public boolean onOptionsItemSelected(MenuItem item)
// Handle action bar item clicks here. The action bar will
// automatically handle clicks on the Home/Up button, so long
// as you specify a parent activity in AndroidManifest.xml.
int id = item.getItemId();

if (id == R.id.menu_logout)
logout();
return super.onOptionsItemSelected(item);
public void logout()
String WiFiName = getConnectedWiFiName();
if(WiFiName.trim().equalsIgnoreCase(Global.wifiNamee.trim()))
Global.wifiNamee = "NOT AVAILABLE"; //Company Wi-Fi

Name
new Home.ExecuteTask().execute(empId);
else
Toast.makeText(getApplicationContext(), "You Are Not In office

Wi-Fi!!!", Toast.LENGTH_LONG).show();

CHAPTER 7
SOFTWARE TESTING
Testing performs a very critical role for quality assurance and for ensuring the reliability
of the software. The success of testing for errors in programs depends critically on the test
cases.
7.1. Testing Phase
The completion of the system is achieved only after it has been thoroughly tested. Though
this gives a feel that project is completed there cannot be any project without going
through this stage. Hence in this stage it is decided whether this project can undergo real
time environment execution without any breakdowns, therefore the package can be
rejected even at this stage.
A primary purpose of testing is to detect software failures so that defects may be

discovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a
product functions properly under all conditions but can only establish that it does not
function properly under specific conditions. The scope of software testing often includes
examination of code as well as execution of that code in various environments and
conditions as well as examining the aspects of code: does it do what it is supposed to do
and do what it needs to do. In the current culture of software development, a testing
organization may be separate from the development team. There are various roles for
testing team members. Information derived from software testing may be used to correct
the process by which software is developed.

7.2. Unit Testing
During this implementation of the system each module of the system was tested
separately to uncover errors within its boundaries. User interface is used as a guide in the
process
In computer programming, unit testing is a method by which individual units of source

code are tested to determine if they are fit for use. A unit is the smallest testable part of an
application. In procedural programming a unit may be an individual function or
procedure. In object-oriented programming a unit is usually a method. Unit tests are
created by programmers or occasionally by white box testers during the development
process.
Ideally, each test case is independent from the others: substitutes like method stubs, mock
objects, fakes and test harnesses can be used to assist testing a module in isolation. Unit
tests are typically written and run by software developers to ensure that code meets its
design and behaves as intended. Its implementation can vary from being very manual
(pencil and paper) to being formalized as part of build automation.
7.3. System Testing
Testing is a set of activities that can be planned in advance and conducted systematically.
The proposed system is tested in parallel with the software that consists of its own phases
of its analysis, implementation, testing and maintenance. Following are the tests
conducted on the system.
System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the system's compliance with its specified requirements. System
testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.

7.4. Module Testing
A module is composed of various programs related to that module. Module testing is

done to check the module functionality and interaction between units within a module. It
checks the functionality of each program with relation to other programs within the same
module. It then tests the overall functionality of each module.
This module introduces the technique of functional (black box) unit testing to verify the
correctness of classes. It shows how to design unit test cases based on a class
specification within a contract programming approach. The laboratory exercises then
guide students through creating and running tester classes in Java from a test case design,
utilizing the Joint unit test framework. It also contains a worked example on how to unit
test GUI and event handling classes.
Testing is an essential part of any software development process, but it is often poorly
understood. In this module, we take a simple approach and look at two key approaches to
testing. Unit testing is done at the class level, and is designed with the aid of method pre-
and post-conditions. System testing is done at the program level, and is designed based on
documented use cases. We look at how your approach to object-oriented design is
influenced by the need to design and execute tests, and close with some other issues in
testing.
7.5. Integration Testing
Integration testing is a systematic technique for constructing the program structure while
conducting tests to uncover errors associated with interfacing. The object is to take unit
tester module and build a program structure that has been dictated by the design.
The purpose of integration testing is to verify functional, performance, and reliability

requirements placed on major design items. These "design items", i.e. assemblages (or
groups of units), are exercised through their interfaces using Black box testing, success
and error cases being simulated via appropriate parameter and data inputs. Simulated
usage of shared data areas and inter-process communication is tested and individual
subsystems are exercised through their input interface.

Test cases are constructed to test that all components within assemblages interact
correctly, for example across procedure calls or process activations, and this is done after
testing individual modules, i.e. unit testing. The overall idea is a "building block"
approach, in which verified assemblages are added to a verified base which is then used
to support the integration testing of further assemblages.
7.6. Acceptance Testing
This software has been tested with realistic data given by the client and produced results.
Then the client satisfying all the requirements specified by them has also developed the
software within the time limitations specified. A demonstration has been given to the
client and the end user giving all the operational features.
Acceptance testing generally involves running a suite of tests on the completed system.
Each individual test, known as a case, exercises a particular operating condition of the
user's environment or feature of the system, and will result in a pass or fail, or Boolean,
outcome. There is generally no degree of success or failure. The test environment is
usually designed to be identical, or as close as possible, to the anticipated user's
environment, including extremes of such. These test cases must each be accompanied by
test case input data or a formal description of the operational activities (or both) to be
performed—intended to thoroughly exercise the specific case—and a formal description
of the expected results.
7.7. Test Cases
After developing the system, an evaluation for measuring the accuracy and correctness of
the system is performed. It is measured how the new system is much better than the
traditional ones. The evaluation process of the system is performed in two steps.
At first, example of 5 different organizations where the employees gave attendance in the
traditional way where fingerprint sensors have been set in the entrance and exit doors.
Some employees gave the attendance in front of the door. After 1 hour some of the
employees go outside from their working place to do their personal job. When enquired,
some employees said that they went to the bank for some transaction. A few of them told

that they went to the hospital. It has been also observed that one employee uses his own
fingerprint to open the door for others to leave the place. This violates the attendance
system.
In the second scenario, all the employees of 5 different organizations were registered
with their fingerprint and additional information. A router was installed in those working
places respectively. When an employee is in the working place, he is automatically
connected to the router as he is in range, and later on, he logged in through fingerprint
authentication to initialize the attendance process for the day. As the procedure follows
unique fingerprint authentication, there is no scope for the proxy. They had to remain in
working place as they did not know when the account gets logged out itself and they need
to log in immediately, as it is a session based login system. As a result, only 2 employees
in an organization went outside the working place during work time but they had taken
permission from their senior. The summary of the evaluation result is given in Table.
Organization Number of Total time Employee uses others Take permission

(n=5) Employees taken(min) fingerprint to escape from senior to go
outside
1 52 10 Yes, 4 employees 2 Employees
4 47 8 No 2 Employees
5 54 10 Yes, 2 employees No
Table 9.1. Method 1- which uses only fingerprint authentication
Organization Number of Total time Employee uses others Take permission

(n=5) Employees taken(min) fingerprint to escape from senior to go
outside
4 47 8 No 2 Employees
5 54 10 Yes, 2 employees No
Table 9.2. Method 2 – Fusion of fingerprint authentication and connection to Wi-Fi

CHAPTER 8
GRAPHICAL USER INTERFACE
8.1. Snapshots
Figure 8.1. Admin login page
Figure 8.2. Add Employee page

Figure 8.3. View Employee page
Figure 8.4. Change fingerprint of employee

Figure 8.5. View employee page
Figure 8.6. Mobile device login

Figure 8.7. Fingerprint upload
Figure 8.8. Fingerprint authentication

Figure 8.9. Authenticated profile of employee

CHAPTER 9
FUTURE WORK
The system is error-free and accurate, but still, there is accuracy that needs to be
developed. To add head counting, a camera can be used in this system. Every
organization should contain CCTV cameras. The sequential CCTV footage of the
working place can be obtained. There will be differences in the images as people move
and their positions are not fixed. By continuously subtracting the image from one another,
calculations can be performed in the working place while the attendance procedure is
going on. Then cross-check this number to the number of mobile phones connected to the
router network. This will add more accuracy to this system and if the number does not
match, the system server will receive an alert.
The system is currently developed for the android platform but the focus is to develop it
on iOS platform as well in near future. Besides, in any organization there are employees
who have to perform field work on different occasions. As proposed system consists of
router, it is not eligible for the employees who are responsible for field work. So
including GPS tracker to ensure the presence of the employees in their respective fields is
also one of our future aspects.

CHAPTER 10
CONCLUSION
The proposed vigilance system has been developed using the present technology. This
system automates the process of attendance monitoring, thus saves a lot of time. It is also
cost-effective system because it relies only on a smartphone. As this completely
automates the attendance system, it leaves no room for any kind of error. This system will
surely increase employee’s efficiency at work and also help in the progress of any
organization.

APPENDIX [A]
REFERENCES
[1] T. Agarwal, Biometric Sensors Types and Its Working, 2014.
Online Available: https://www.elprocus.com/differenttypes-biometric-sensors
[2] S. Blog, Advantages of a Biometric Attendance System, 2016.
Online Available: https://blog.synerion.com/biometricattendance-Advantages
[3] M. A. k. T. G. R. J.Chandramohan, R.Nagarajan, ―Attendance monitoring system of
students based on biometric and gps tracking system,‖ International Journal of Advanced
Engineering, Management and Science (IJAEMS), vol. 3, no. 3, 2017.
[4] J. C. D. Cruz, A. C. Paglinawan, M. I. R. Bonifacio, A. J. D. Flores, and E. V. B.
Hurna, ―Biometrics based attendance checking using principal component analysis,‖ in
Humanitarian Technology Conference (R10-HTC), 2015 IEEE Region 10.
[5] D. K. Sarker, N. I. Hossain, and I. A. Jamil, ―Design and implementation of smart
attendance management system using multiple step authentication,‖ in Computational
Intelligence (IWCI), International Workshop on. IEEE, 2016.
[6] A. T. Onaolamipo, ―Development of a computerized biometric control examination
screening and attendance monitoring system with fees management,‖ Development, vol.
4, no. 6, pp. 76–81, 2014.
[7] P. Wadhwa, ―Attendance system using android integrated biometric fingerprint
recognition,‖ International Research Journal of Engineering and Technology (IRJET),
vol. 4, no. 6, 2017.
[8] A. A. Kumbhar, K. S. Wanjara, D. H. Trivedi, A. U. Khairatkar, and D. Sharma,
―Automated attendance monitoring system using android platform,‖ International
Journal of Current Engineering and Technology, vol. 4, no. 2, pp. 1096–1099, 2014.
[9] V. J. A. Sharma, ―Location based attendance tracking using mobile devices,‖
International Journal of Computer Sciences and Engineering.
[10] S. Sultana, A. Enayet, and I. J. Mouri, ―A smart, location based time and attendance
tracking system using android application,‖
International Journal of Computer Science, Engineering and Information Technology
(IJCSEIT), vol. 5, no. 1, pp. 1–5, 2015.

Android Based Advanced Attendance Vigilance System Using Wireless Network With Fusion of Bio Metric Fingerprint Authentication

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Android Based Advanced Attendance Vigilance System Using Wireless Network With Fusion of Bio Metric Fingerprint Authentication

Uploaded by

Copyright:

Available Formats

Android based advanced attendance vigilance system using wireless network with the

fusion of biometric fingerprint authentication

1.1. Project Description

University B D T College of Engineering Page 1

1.2. Scope of the project

1.3. Problem statement

University B D T College of Engineering Page 2

1.4. Objectives of the project

 To develop a smart attendance system where an android device will be used as a

University B D T College of Engineering Page 3

2.1. Existing System

Existing system is focused on the attendance system using biometric fingerprint

2.1.1. Disadvantages of the Existing System

University B D T College of Engineering Page 4

2.2. Proposed System

2.2.1. Advantages of the Proposed System

University B D T College of Engineering Page 5

SOFTWARE REQUIREMENT SPECIFICATIONS

3.1. Functional Requirements

3.1.1. Admin Web Applications

3.1.2. Android Application

3.2. Non-Functional Requirements

Non-functional requires a description and, where possible, target values of associated

University B D T College of Engineering Page 6

Accessibility: The accessibility factor to the system depends on the availability of a

Deployment: The deployment is carried out in various stages such as Android

University B D T College of Engineering Page 7

Communication Interfaces: The application requires an internet connection to perform

Security requirements: Provides automatic file checking capability to ensure the

3.3. Software and Hardware Requirements

3.3.1. Software Requirements

 Operating system : Windows XP Professional / Windows7

3.3.2. Hardware Requirements

 System : Pentium IV 2.4 GHz.

University B D T College of Engineering Page 8

4.1. Development Methodology

4.1.1. User Interface

4.1.3. MAC Address Access

University B D T College of Engineering Page 9

4.1.5. Session Based Log In

Figure 4.1. Flow chart of session based login

University B D T College of Engineering Page 10

4.1.6. Android Based Mobile Application

Figure 4.2. Block diagram of the technical part of the system

University B D T College of Engineering Page 11

4.2. Architectural Design

Figure 4.3. System Architecture

University B D T College of Engineering Page 12

Figure 4.4. Flow chart of the System Architecture

admin_id bigint(200) NO PRI auto_increment

admin_name varchar(200) YES

admin_password varchar(200) YES

Table 4.1. The Admin table

University B D T College of Engineering Page 13

Field Type Null Key Extra

Field Type Null Key Extra

University B D T College of Engineering Page 14

5.1. Dataflow Diagram

Figure 5.1. Context Analysis Diagram

University B D T College of Engineering Page 15

University B D T College of Engineering Page 16

5.2. Sequence Diagram

Figure 5.4. Sequence diagram of the system