Biometric fingerprint student attendance systemSoftware requirement specifications

UNDER THE GUIDANCE OF Submitted by

Er. Mananpreet Kaur Neha Chhabra (5665)

CSE Department Rajni(5675)

Robin(5680)

Tavleen Kaur(5697)

Computer Science & Engineering Department

Table of Contents

1. Introduction………………………………………………………….1-2

1.1 Purpose

1.2 Scope

1.3 Glossary :Definitions,Acronyms and Abbreviations

1.4 References

2. The Overall Description……………………………………………...3-7

2.1 System Environment

2.1.1 Hardware Interfaces

2.1.2 Software Interfaces

2.2 Functional Requirements

2.3 User Characteristics

2.4 Non-Functional Requirements

3. Requirements Specification………………………………………….....8

3.1 External Interface Requirements

4. Behavioural Description…………………………..……………………9

4.1 System States

1. INTRODUCTION

1.1. Purpose

The purpose of this document is to present a detailed description of the Attendance

Management System Using Fingerprint. This document will fully describe all the functional

and nonfunctional requirements, design constraints, and other factors necessary to provide a

complete and comprehensive description of the requirements for the Attendance Management

System Using Fingerprint. It will also describe the external behavior of the Attendance

Management System using fingerprint.

 

1.2. Scope of project

 

This software system will be the attendance Management System for lcet, Ludhiana . This

system will be designed to facilitate the attendance system of students by providing tools

to assist in automating the manual attendance system. More specifically, this system is

designed to allow the head of departments to manage and control by taking the

students fingerprint for collecting their daily attendance. A variety of reports can be produced

to give the information for student Dean’s for its needs in the following format:

•Attendance Report

•Leave Report

•Absence Report

•Exception Report

 

1.3. Definitions, Acronyms and Abbreviations

SRS- Software Requirements Specifications

IEEE-Institute of Electrical and Electronics Engineers

DBMS- Database Management System

SQL- Structural query language.

USB- Universal Serial Bus.

2. The Overall Description

Describes the general factors that are required for the development of the software. This

section does not state specific requirements. Instead it provides a background for

requirement that makes them easier to understand.

2.1 FUNCTIONAL REQUIREMENTS

The functional requirements document (FRD) is a formal statement of an application’s functional requirements. It serves the same purpose as a contract. The developers agree to provide the capabilities specified. The client agrees to find the product satisfactory if it provides the capabilities specified in the FRD. Functional Requirement defines the function of software or its component. A function is described as a set of inputs, the behaviour, and outputs. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioural requirements describing all the cases where the system uses the functional requirements are captured in use case. The plan for implementing functional requirements is detailed in the system design.

In some cases a requirements analyst generates use cases after gathering and validating a set of functional requirements. The hierarchy of functional requirements is: user/stakeholder request → feature → use case → business rule. Each use case illustrates behavioural scenarios through one or more functional requirements. Often, though, an analyst will begin by eliciting a set of use cases, from which the analyst can derive the functional requirements that must be Implemented to allow a user to perform each use case.

Quality is meeting requirements. For that reason, the FRD is the central document in system development. It is used for the following:

Uses

Designing and developing tile application system.

Evaluating the product in all subsequent phases of the life cycle.

Determining the success of the project

The FRD has the following characteristics:

Characteristics of FRD It demonstrates that the application provides value to the State in terms of the

business objectives and business processes in the 5-year plan

It contains a complete set of requirements for the application. It leaves no room for anyone to assume anything not stated in the FRD.

It is solution independent. The FRD is a statement of what the application is to do—not of how it works. The FRD does not commit the developers to a design. For that reason, any reference to the use of a specific technology is entirely inappropriate in an FRD.

A requirement is a condition that the application must meet for the customer to find the application satisfactory. A requirement has the following characteristics:

Requirement Characteristics

It provides a benefit to the organization

It describes the capabilities the application must provide in business terms.

It does not describe how the application provides that capability

It does not describe such design considerations as computer hardware, operating system, and database design

It is stated in unambiguous words. Its meaning is clear and understandable

It is verifiable

FUNCTIONAL REQUIREMENTS OF BIOMETRIC STUDENT

R.2: LOGIN MANAGEMENT

Description The user is requested to enter the login id and password so as to access the database to check the student’s attendance. This login is done at managerial levels i.e. only head of department and other staff members can review the database.

Input Login_Id and Password.

Output Main form opens.

LOGIN MANAGEMENT

R.2.1 FAILED TO LOGIN

FAILED TO LOGINDescription

If attempt to access the database is failed the user has filled the wrong information either password or id or both of them , in other words an attempt to access the information which is not valid to the user , the database will inform the user about it.

Input Enter login_Id and password.

Output Invalid information. Please try again.

R.3 Main Form

R.3.1:MANAGE PERSONAL DETAILS

MANAGE PERSONAL DETAILSDescription

The student’s information about his/her name, ph_no,address, Age, Sex etc is filled and then student is provided a roll no which

1.1

acts as Student_id which is unique to a particular student then a department is decided in which the student is interested to take admission in.

Input Enter Student_id.

Output Student details stored successfully.

R.3.1.1: ENROLLMENT SCAN

ENROLLMENT SCANDescription

The user’s fingerprints are scanned and associated with that user’s identity in the system. This is normally a supervised process to allow for preventing false identity creation and propagation. In colleges and universities, enrolment would be done at the time a student takes admission in the particular institute and only needs to be done once.

Input Fingerprint scan and image of the student.Output Successfully saved the student biometric data of the student.

R.3.1.2: UPDATE STUDENT DETAILS

Update Student detailsDescription

When a student wants to change the information about personal details he surely can do it, so any attempt to update the information ,the database allows it to do so , thus nothing is permanent or static except fingerprint scan of a student it can’t be changed once stored in the database.

Input Student_id.

Output Details updated and successfully saved in the database

R.3.1.2.1: RESET STUDENT DETAILS

RESET STUDENT DETAILS

Description

If all of the details need to be updated this option can be used, it will simply clear all the personal details of the student.By doing so you will get a chance to enter the details again

Input Student_id.

Output Student information cleared from the database.

R.3.1.3: DELETE STUDENT INFORMATION

DELETE STUDENT INFORMATIONDescription

Delete record of student who has left the institute or who is passed out.

Input Student_id

Output Record deleted.

R.4: ATTENDANCE REPORT

Description: It shows the attendance of every student in each of the subjects or courses provided in the department in which he/she is opted for.

R.4.1: ATTENDANCE REPORT OF PARTICULAR STUDENT

ATTENDANCE REPORT OF PARTICULAR STUDENTDescription

It shows the attendance of every student in each of the subjects or courses provided in the department in which he/she is opted for.

Input Enter Student_id.

Output Attendance of the student is displayed in each of the course.

R.4.1.1: ATTENDANCE REPORT OF ALL STUDENTS OF CLASS

ATTENDANCE REPORT OF ALL STUDENTS OF CLASSInput Class_id

Output Complete attendance report of a class containing all the students

R.4.2 ATTENDANCE REPORT OF A COURSE

ATTENDANCE REPORT OF A COURSEInput Corse_code

Output A report is displayed showing status of the course containing all students eligible and non eligible to exams.

R.5: DISPLAY REPORT FOR ELIGIBILITY CRITERIA

DISPLAY REPORT FOR ELIGIBILITY CRITERIADescription

As Reports are generated for each course and the total number of students for each attendance is listed and their corresponding status. If their attendance is less than say 60% or any standard you may set then a report will be displayed showing whether they are qualified for a exam or not.

Input Enter Status of eligibility.

Output Corresponding to the eligibility, report is displayed.

2.2. Non-Functional Requirements

This section contains all the software requirements at a level of detail, which enable designers

to design a system to satisfy those requirements, and testers to test that the system satisfies

those requirements.

2.2.1 System Environment

2.2.1.1 Hardware Interfaces

The software application would be compatible on

Processor: - Dual Core or above

RAM: - 512MB or above.

Hard disk: -80 GB or above.

Monitor: - 14” VGA

Mouse, keyboard with 101 keys

2.2.1.2 Software Interfaces

Following are the software requirements needed for the project:-

Operating system : Windows xp, window 7 or above

IDE : Netbeans IDE7.2.1 for java and Mysql query browser

Front end : Java

Back end : My-sql

Server : SQL server

Development kit : jdk-6

Browsers : Internet Explorer, Mozilla Firefox, Google Chrome, Safari.

N.1 External Interfaces

The Biometrics will use the standard input/output devices for a personal computer. This

includes the following:

EXTERNAL INTERFACES The Biometrics will use the standard input/output devices for a personal computer.

Keyboard One of the primary input devices used with a computer, the keyboard looks very similar to the keyboards of electric typewriters, with some additional keys. Keyboards allow a computer user to input letters,

numbers, and other symbols into a computer .

Monitor. A monitor or display is an electronic visual display for computers. The monitor comprises the display device, circuitry and an enclosure. The display device in modern monitors is typically a thin film transistor liquid crystal display (TFT-LCD) thin panel, while older monitors use a cathode ray tube (CRT) about as deep as the screen size.

Printer. It is used to produce a hard copy of the processed data

Scanner It is used to scan the fingerprint

N.2 User Interfaces

USER INTERFACES A Screen is displayed which is used to help the user to interact with the software

Login Screen This is the first screen displayed. It will allow users to access different screens based on their role. Various fields will be: Username, Password, Role (Administrator, Student, Teacher).

N.3 Software Interfaces

SOFTWARE INTERFACE  Any windows-based Operating system Microsoft SQL Server 2008 as the DBMS-for database.

N.4 Communications Interfaces

View of Power and Comm. Port

Electrical outlet using for connecting the power.

Ethernet port: Using for network connection with the computer through Ethernet

Serial port jack Using for network connection with the computer through RS232

USB slot: Connect USB peripheral device (for example the U flash disk, fingerprint sensor

and so on).

N.5 PLATFORM: NETBEANS 7.1.1

INTRODUCTION TO NETBEANS 7.1.1:

Net Beans IDE is a modular, standards-based integrated development environment (IDE),

written in the Java programming language. The NetBeans project consists of a full-featured

open source IDE written in the Java programming language and a rich client application

platform, which can be used as a generic framework to build any kind of application.

User Interface Elements Of NetBeans IDE

When you create a new window application project in NetBeans IDE 6.9.1 a window similar

to the one shown below:

The Solution Explorer Window

The Solution Explorer window list the solution name, the project name, and all the forms and

modules that are used n the project. You can open a particular file existing in project by

double-clicking the file in the solution explorer window. The following figure depicts the

solution explorer window.

The Solution Explorer Window

The Properties Window

The properties window display the properties that are associated with an object.

For example:

On selecting Form from the window form designer window, the properties window lists all

the properties associated with forms, such as size and text. The following figure shows the

properties window displaying the properties of a form:

The properties window

Toolbox:

The toolbox displays a number of tabs. Each tab contains several items, as shown in the

following:

The Toolbox Window

The Output Window:

The output window displays messages for the status of status of various features provided in

Net Beans IDE 7.1.1.

2.4 Behavioural Description

B.1 System State

This section contains the descriptions about all the state of the system i.e. thumb scanner and the events and actions of those states.

The various states that system undergoes are:-

Starting state

Enrolment scans :The user’s fingerprints are scanned and associated with that user’s identity in the system. This is normally a supervised process to allow for preventing —false identity creation and propagation. In an enterprise scenario, enrolment would be done at the time a person becomes employed and only needs to be done once.

Logic State

Template creation and storage: A biometric template is created from biometric features derived from the scanned fingerprint. The enrolment template becomes the fingerprint biometric record for the user. In some solutions, the fingerprint scan itself may also be stored.

Ending State

Live scan: Each time a person requests access to the system, a live scan of the fingerprint is made and a live template is derived from that scan. The scanner may also perform a liveness

measurement, which can distinguish between an artificial copy of the fingerprint and a “live” finger and thus validate the authenticity of the fingerprint.

Automated matching: The live template is compared to a specific enrolment template and a matching score is generated. Scores greater than a threshold are considered a match.

Fingerprint Biometrics Process Flow