Software Requirements

Specification
for

Teacher Attendance System

Prepared by Aksa Kalsoom, Sadia Farooq and Laila Abid

Supervisor: Sir Imran Khalil

University Of Engineering And Technology

30th Nov 2014

ii

Table of Contents
Table of Contents .......................................................................................................................... ii
1. Introduction .............................................................................................................................. i
1.1
1.2
1.3
1.4
1.5

Purpose.............................................................................................................................................. i
Document Conventions ..................................................................................................................... i
Intended Audience and Reading Suggestions ................................................................................... i
Product Scope ................................................................................................................................... i
References ......................................................................................................................................... i

2. Overall Description ................................................................................................................. ii

2.1
2.2
2.3
2.4
2.5
2.6
2.7

Product Perspective.......................................................................................................................... ii
Product Functions ............................................................................................................................ ii
User Classes and Characteristics ..................................................................................................... ii
Operating Environment .................................................................................................................... 3
Design and Implementation Constraints .......................................................................................... 3
User Documentation ........................................................................................................................ 3
Assumptions and Dependencies ..................................................................................................... iii

3. External Interface Requirements ...........................................................................................4

3.1
3.2
3.3
3.4

User Interfaces ................................................................................................................................. 4

Hardware Interfaces ......................................................................................................................... 4
Software Interfaces .......................................................................................................................... 4
Communications Interfaces ............................................................................................................. 4

4. System Model ...........................................................................................................................5

4.1 The Functional Model of Teacher Attendance System .................................................................... 5
4.2 The System Design Object Model ................................................................................................. 10

4.3 Activity Diagram for Staff Biometric Attendance System.11

5. Specific Requirements ...........................................................................................................11
5.1 Functional Requirements ............................................................................................................... 11
5.2 Non Functional Requirements ....................................................................................................... 12

Appendix A: Glossary..................................................................................................................13
Appendix B: Analysis Models .....................................................................................................13
Appendix C: To Be Determined List ..........................................................................................13

1. Introduction
1.1 Purpose
The purpose of this SRS document is to provide a detailed overview of our software
product, its parameters and goals. This document describes the project target , its user interface,
hardware and software requirements. It defines how this software will work. The following .it
defines the functional and nonfunctional requirement. This Software Requirements Specification
document only covers the main system and does not describe the implementation of the database
in which the main system interacts.

1.2 Document Conventions

As of the latest version of this Software Requirements Specification, there are no document
conventions

1.3 Intended Audience and Reading Suggestions

The intended audience is the software engineering class, who will be implementing and testing
the Attendance Tracking System. Also, the document is to be utilized by the software
engineering professor to evaluate the softwares design and features.

1.4 Project Scope

The Teacher Attendance System will allow the administrator to maintain the record of
attendance of teacher. Also the system will permit the adminstrattor to maintain all the esential
details regarding to a particular teacher. Furthermore the program provides different modes to
edit the attendance ,view statistics and take notes on elements pertaining to attendance. The goal
is to provide an easy and portable solution to attendance record maintenance and attendance
statistics.

1.5 References
I.
II.
III.

Cappelli, R., Lumini, A., Maio, D. and Maltoni, D. (2007). Fingerprint Image Reconstruction from
Standard Templates, IEEE Transactions, vol. 29, pp.1489-1503.
Cappelli, R., Maio, D., Maltoni, D., Wayman, J., L. and Jain, A. K. (2006). Performance evaluation
of fingerprint verification systems, IEEE Trans. Pattern Anal., 28(1), pp. 3-18.
Chirillo, J. and Scott, B. (2007). Implementing Biometric Security. Indianapolis: John Wiley
Publishing Inc., ISBN: 0 7654 25026.

ii

2. Overall Description
2.1 Product Perspective
The Attendance Management System is intended to replace the manual model of attendance
record keeping by means of paper records. The paper records are replaced with a single
interaction between the teacher and the Attendance Management System. Professors will be able
to view details regarding attendance of individual students on their PC and quickly maintain
attendance records. The system will be developed in such a way to provide easy addition of
enhanced features, which may be desired in subsequent versions.

2.2 Product Functions

The main feature of the Attendance Managemant System is that it keeps a record of all essentials
details of each individual teacher.At the end of a specified period this system create a defaulties
list as well as the non-defaulties list. Finally, another feature of Attendance Management System
is its flexibility and ease of use.

2.3 User Classes and Characteristics

There are number of faculty members at the university and it is estimated that almost all faculty
members will utilize the Attendance Management System.The admin should be allowed to take,
edit, and view attendance records at any desirable time. All professors have Internet access
through their PC s . This provides the backbone of the Attendance Management System.

iii

2.4 Operating Environment

The Attendance Management System shall function on the PC provided by the

department. This entails the system to operate on the Windows CE platform.
The Attendance Management System shall interface between Windows CE designated to
store the attendance records. The Web Server and Database Software have not been
established at this point.
The Attendance Management System will record all the essentials details of each
particular staff member.
Pentium 3.0 GHz or higher RAM must be 1 Gb or more and Hard Drive10 GB or more

2.5 Design and Implementation Constraints

The time allotted for this project will be limited to the end of June 2015.
The language for the project will be VB.Net and the development environment will be
the embedded Visual Basic 6.0 environment.

2.6 User Documentation

The system will provide an online user manual in HTML that describes the functionality
and options available to the user.
The system will provide a hard copy of the user manual, which is identical to the manual.

2.7 Assumptions and Dependencies

DE-1: Teacher data being used for setup and Teacher recognition is dependent on information in
adatabase administered outside of the capabilities of the Attendance ManagementSystem.
All non-academic staff of the institution has a unique employee ID for registration.
The authentication system is fed with the data to identify the admin.
There is a salary dispatch system in the organization.
Each staff belongs to a particular Department or Unit
The captured attendance is stored on the database server and can be retrieved.
Administrator can track attendance records of any non-academic staff.

3. External Interface Requirements

3.1 User Interfaces

The Attendance Management System shall provide details of teacher in the department.

iv

These details can be clicked with a mouse in order to view a particular teachers
sattendance record.
All modifications to the database will be done through a keyboard.
Application will be accessed through a Browser Interface. The interface would be viewed
best using 1024 x768 and 800 x 600 pixels resolution setting.

3.2 Hardware Interfaces

A. Hardware requirement for the client computer

RAM 1 GB, 2 GB or more recommended for fast access of the application

Hard Disk: 5 GB free space to install the Client side application.
Input device: Keyboard, fingerprint reader.
Output device: Computer Monitor.

B. Hardware requirement for the server.

RAM 2GB recommended 6GB or more for big systems this is recommended because
image processing work need more memory.
Hard Disk: minimum of 15 GB recommended 40GB or more to store the biometric
data,we need bigger storage space for storing the image file properly.
Input device: Keyboard and fingerprint reader.
Output device: computer monitor.

3.3 Software Interfaces

MySQL

For Database

VB.Net

Programming language

Adobe Photoshop, Illustrator

For graphic design

Visual Basic 6.0

For making the layout

Crystal Report/ MS Excel

For making Reports

3.4 Communications Interfaces

The security of a user must be consistent through the use of passwords.

The Attendance Management System will communicate to the database through Internet.

4. System Models
System model helps the analysts to understand the functionality of the system and models are
used to communicate with the system. The system model is composed of three individual
models:-The functional model: represented by use case and Scenario.

4.1 The Functional Model of Teacher Attendance System

UML Use Case diagram for staff biometric attendance system is shown in Figure 1.1. In this
figure, the various participants in the system are also detailed.
Actors: Database administrator, non-academic staffs
Non-academic staff: mark attendance, In-time, out-times, apply for leave, and get salary.

Administrator: Keep track of attendance, generate monthly attendance summary, and reports to
the faculty

Software Requirements Specification for <Project>

vi

4.1.1 Use case and actor descriptions

Login Use case
Use case name
Actor(s)
Description
Precondition
Post condition

Login
Administrator, End User
The username and password to login for Administrator and User
Administrator and User must be authorized
Login is successfully
Basic course of Actions
Administrator and User want to Login
Fill the user name and password on the space provide
Administrator login as Admin and User login as standard user
Click Login button
Use case ends

Alternate of courses of Action

Alternative course A: 2. If the Administrator and user is not fill correctly, the login fails
Alternate Course A : 5: use case ends
Capture Fingerprint Use case
Use case name
Actor(s)
Description
Precondition
Post condition

Capture fingerprint
Administrator, End user ( fingerprint scanner)
The capture fingerprints process provides a predefined capture
sequence
The administrator and user has chosen the capture biometrics
feature of device application
The fingerprint capturing process is completed
Basic course of Actions
Fingerprint reader displays platen and active capture area of current presenter
finger tips
Administrator and User places requested print on scanner platen
Scanner captures the print image after it determines that the print image is
acceptable
The Application displays the fingerprint captured to the administrator and user
Repeat steps 1 to 3 until all required print images are captured
Use case ends

Software Requirements Specification for <Project>

vii

Alternate of courses of Action

Alternative course A: 3. If the scanner fails, application indicates the failure of the scanner
and the option to capture print is inactive
Alternate Course A : 6. Use case ends
Character Identification Use case
Use case name
Actor(s)
Description
Precondition
Post condition

Character identification
Administrator
The Administrator chooses character identification option,
selects an image and then character to identify
The image must exist and be processed in order for the
characters to be extracted
New information will be stored in the database
Basic course of Actions
Administrator logs into the system
Verification of log in information is correct
Administrator clicks on character identification option
A grid view is made available and returns an image that have already been
entered into the system
Administrator selects an image from a grid view or adds a new image to the
selection
A new page is displayed with all of the characters that have made appearances
in the selected image
Administrator selects an image for a list of photos
Administrator fills in known information pertaining to selected character
Data is inserted into the database
Administrator can either view the characters image gallery, view who the
current character interacted with, go on to another page or logout
Logs the user out or redirects to another page

Alternate of courses of Action

Alternative course A: 2. If the Administrator fails verification at the log in, error message will
display, Administrator will not be able access the system and then he/she will be prompted to
try again
Alternative course A: 8. If the Administrator fills in unknown information, error message will
displayed and he/she prompted to fill the correct again

Software Requirements Specification for <Project>

viii

Display Information Use case

Use case name
Actor(s)
Description
Precondition
Post condition

Display information
End User
The device application will display all available information by
using the biometric image captured.
Device application successfully launched
Information displayed
Basic course of Actions

The Device application resets the alert indication (i.e. all information displayed
chronologically)
The device application displays to the user the information that match entries
in the Database
Use case ends
Alternate of courses of Action
Alternative course A: 2. If captured image does not match any entries in the database, access
the details of the information
Alternate Course A : 3. Use case ends
Review (Update) Analyses Use case
Use case name
Actor(s)
Description
Precondition
Post condition

Review analyses
Administrator
The Administrator is able to look frame analyses or documents
by other user or their own
Frames must already be analyzed and documents must be
submitted in order for them to be reviewed later
Users can only make changes to their own frame analyses or
documents submitted
Basic course of Actions
Administrator logs into the system
Verification login information is correct
Administrator clicks on review link

Software Requirements Specification for <Project>

ix

A grid view is made available returns review that have already been entered
into the system
Administrator selects review from a grid view
A new page displays with a drop down list of reviews from a particular photo
and documents submitted
Administrator selects a review from a drop down list or a document from a
grid view
Administrator views this information
Verification user is able make changes, redirects to the home page, logs the
user out.
Administrator can make changes, return to main menu or exit by logging out
Alternate of courses of Action
Alternative course A: 2. If the Administrator fails verification at the login, an error message
will displayed, user will not be able to access the system and the user will be prompted to try
again
Alternate Course A : 9. If Administrator fails verification to make changes, an error message
will display and the user will be unable to make any changes, go to step 10
Alert Notice Use case
Use case name
Actor(s)
Description
Precondition
Post condition

Alert notice
End User
The system will continuously monitor the return responses and
indicate when there is a positive match response received
The system application must be launched with an active
connection
Matched transaction is indicated
Basic course of Actions
Checks if there is a new match response
If there is a new match the system application presents to the user
Use case ends

Software Requirements Specification for <Project>

4.2 The System Design Object Model

The object model represented in UML with class diagrams, describe the structure of the
proposed system of staff biometric attendance system, in terms of objects, attribute, associations,
and operations. The class diagram for the proposed system describes the system in terms of
classes, attributes, operations, and their associations.In UML, classes and objects are depicted by
boxes composed of three compartments. The top compartment displays the name of the class or
object. The centre compartment displays its attributes, and the bottom compartment displays its
operation.

11

4.3 Activity Diagram for Staff Biometric Attendance System

The activity diagram describes the behaviour of the proposed system in terms of activities.
Activities are modelling elements that represent the execution of a set of operations. The execution
of an activity can be triggered by the completion of other activities, by the availability of objects, or
by external events. The activity diagram for staff biometric attendance system depicts activities
related to management of staff attendance.

5 Specific Requirements
5.1 Functional Requirements
In this section, we are included the set of functional requirments. Each functional requirement are
carried out with brief explanation.

5.1.1 Registration of a teacher

In a database , the admin will register each of the teacher name and their unique finger print.
Later on , this information will use for the proper indentification.

5.1.2 Teacher indentification

Our system will be uniquely identify each of the teacher in the department.
When teacher enters and leave the department , identification is done.

5.1.3 Storage identification

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

12

When the identification period is done, a text file is created which consist of records of
the teacher name date , in out time, finger print, all personal and professional
information.

5.1.4 Time stamping of identification

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

5.1.5 Indetification data downloaded into the Microsoft Excel

The system will be able to download the indetification data into the Microsoft Excel
readable text file.
In an Excel spreadsheet, the data should be formatted.

5.2 Non Functional Requirements

5.2.1 Performance Requirements

The software will support when multiple concurrent access user terminals.
The software will handle the textual and finger 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 sec.

5.2.2 Data Migration Requirements

There must be a simple way to teacher data from one system to migrate to a new system.

5.2.3 Security Requirements

No one should be allowed to tamper with the data from others. Only admin can view and login
into the system.

5.2.4 Maintainability
The system shall be distributed with independent modules or classes for database interface for the
databases. This independency brings to easy testability, maintainability, flexibility and easy to use.
In general, after the system has been produced, change or improvement may be needed. This could
happen because design faults are identified after the system has been failed tested or because
functions need to be added.

12

5.2.5 Accuracy
Human face and fingerprint recognition system need an accurate and correct data from the system
that he/she uses for the preparation of reports as well as to make relevant decisions.

5.2.6 Backup
There should avoid damaging the record. A simple backup function for the whole teacher
attendance data.

Appendix A: Glossary
SRS: Software Requirement Specification
RAM: Random Access Memory
OS: operating system
DB: Databases
SQL: Structured Query Language

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

Appendix C: To Be Determined List