SMART ATTENDANCE SYSTEM

1. System
1.1. Introduction
The proposed project “Smart Prayer Attendance System” has been developed to overcome
the problems faced in the practicing of manual system. This software is built to eliminate
and in some cases reduce the hardships faced by the existing system. Moreover this system
is designed for particular need of the schools or colleges to carry out its operations in a
smooth and effective manner.

1.2. Existing System Study

1.2.1. Smart Door Unlocking System
a. Introduction

Smart door locking system is designed to prevent unauthorized access, trespassing and
intrusion. Banks, corporate offices, financial organization, jewellery shops, and government
organization are some of the common targets where unauthorized access, trespassing and
intrusion take place. Normally the aim behind such activities is stealing money, jewels or
any important documents for individual gain. The purpose of Android Based Smart door
locking system is to provide a smart solution to overcome these challenges and provide a
feasible solution. This system works on pre-decided password concept. It increases the
security level to prevent an unauthorized unlocking done by attacker. In case the user
forgets the passwords, system gives the flexibility to the user to change or reset the
password. This automatic password based lock system gives user more secured way of
locking-unlocking the system.

b. Common Features
 Less Human Effort
 Fast And Convenient
 Mobile Application

c. Distinct Features
 Authorized Access
 Easy To Handle and Operate
 User Friendly Interface

d. Limitations
 Electronic Devices
 Requires More Manual Work

e. Features adopted for Proposed System

 Authorized Access
 Fast And Convenient
 User Friendly Interface

1.2.2. Student Attendance System

1|Page
201703100110024,201703100110027,201703100110057,201703100110062
 SMART ATTENDANCE SYSTEM

1.2.3. Employee Attendance System

1.2.4. Comparative Study
1.2.4.1. Distinct features
1.2.4.2. Common features
1.2.4.3. Limitations
1.2.4.4. Features adopted for proposed system

2. Proposed System
2.1. Definition
This project is developed for taking the prayer attendance of students during prayer hours
using Biometrics(Face Recognition, Fingerprints if face is not recognized) technology.

2.2. Objectives
The purpose of this document is to describe the functionality and specifications of the
design of a web application for Managing students attendance in prayer session. The
expected audiences of this document are the developers and the admin of the web
application. Now with the help of this system the admin has the information on his finger
tips and can easily prepare a good record based on their requirements.

Finally, we can say that this system will not only automate the process but save the valuable
time of the HOD’s, Counsellors, Faculty’s or the admin, which can be well utilized buy their
institute. This will be an additional advantage and management of power based on their
free time from their normal duty.

2.3. Scope
The scope of the project is the system on which the software is installed ,i.e. the project is
developed as a desktop application and it will work for a particular institute. But later on
the project can be modified to operate it online.

2.4. Requirements
2.4.1. Non Functional
 SQL Database
 Windows OS will execute the system
 Attendance should be kept manually if face is not recognized
 Student’s attendance is being taken during prayer hours only

2.4.2. Functional
 The user does not need to tackle with any problems regarding the GUI as it aims
to be a simple but functional one
 Report Generation

2.4.3. Distinct

2|Page
201703100110024,201703100110027,201703100110057,201703100110062
 SMART ATTENDANCE SYSTEM

 FACE Recognition Based Attendance

 Attendance taken using biometrics technology(Fingerprints are also allowed

2.5. Software Process Model

2.6. Acronyms, and Abbreviations
2.7. Proposed technologies
3. System Design
3.1. Use-Cases
3.1.1. Actors and roles
3.1.2. Scenario description of each Use-Case
3.1.3. Use-Case Diagrams
3.2. Activity Diagrams
3.3. Sequence/Data Flow Diagrams/Class Diagram
3.4. Data Dictionary with Constraints
3.5. System Architectural Diagram
3.6. User Interface Design
3.6.1. UI Specification with technical justification
3.6.2. Validations
3.6.3. Navigations
3.6.4. Screenshots
3.7. Reports
3.7.1. Inputs and Outputs
3.7.2. Layouts
3.7.3. Report Usage

4. System Enhancement
5. Learning during project wok
6. References
6.1. Books
6.2. Web References
6.3. Additional reference

3|Page
201703100110024,201703100110027,201703100110057,201703100110062