Software Requirements

Specification
for

Computer Science Department

Portal
Version 1.0 approved

Prepared by :
Ravinder Kumar
Pankaj Dhiman
Prashant Singh
Nirmal Kumar

Aravali College of Engineering and Management

26th October 2019
Table of Contents
Table of Contents ..........................................................................................................................ii
Revision History ............................................................................................................................ii
1. Introduction ...............................................................................................................................1
1.1 Purpose ............................................................................................................................................ 1
1.2 Document Conventions ................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions ................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ....................................................................................................................................... 1
2. Overall Description ...................................................................................................................2
2.1 Product Perspective ......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment ................................................................................................................... 3
2.5 Design and Implementation Constraints ......................................................................................... 3
2.6 User Documentation ........................................................................................................................3
2.7 Assumptions and Dependencies ......................................................................................................3
3. External Interface Requirements ............................................................................................4
3.1 User Interfaces .................................................................................................................................4
3.2 Hardware Interfaces ........................................................................................................................ 4
3.3 Software Interfaces ......................................................................................................................... 5
3.4 Communications Interfaces ............................................................................................................ 5
4. System Features ........................................................................................................................5
5. Other Nonfunctional Requirements .......................................................................................6
5.1 Performance Requirements ............................................................................................................. 6
5.2 Safety Requirements ....................................................................................................................... 6
5.3 Security Requirements .................................................................................................................... 6
5.4 Software Quality Attributes ............................................................................................................ 7
5.5 Business Rules ................................................................................................................................ 7
6. Other Requirements .................................................................................................................7
Appendix B: Analysis Models ......................................................................................................8
Appendix C: To Be Determined List ...........................................................................................8
1. Introduction

1.1 Purpose
The main goal and objective of this attendance system of face detection and recognition is to present
face recognition in real time environment, to see and mark the attendance of their students and
employees on a daily basis to keep track of their presence. The system will mark and record the
attendance in any environment. This system is automated and user can capture video and accordingly
attendance will be marked, improving the accuracy to great extent and finally the attendance report
will be generated.

1.2 Document Conventions

 Entire document should be justified.
 Convention for Main title
Font face: Times New Roman
Font style: Bold
Font Size: 14
 Convention for Sub title
Font face: Times New Roman
Font style: Bold
Font Size: 12
 Convention for body
Font face: Times New Roman
Font Size: 12

1.3 Intended Audience and Reading Suggestions

The intended audience for this is everyone either developer , newbies, nerds, project managers,
marketing staff, users, testers, and documentation writers. The SRS contains the detailed
specification of the various technicalities of this Chatbot, the way of the functioning of the bot
and more on every bit of the project. The required sequence for referring to this SRS is the same
way as it proceeds for each and every reader irrespective of any prerequisites.

1.4 Product Scope

Face Recognition is basically a attendance management system or we can simply say a software
that typically runs on the fundamentals python, that is used as an attendance system.
The project is specifically dedicated towards so that the application serves as an attendance
system/conversational agent for college.

1.5 References
 https://www.python.org/
 https://opencv.org/
 https://www.tutorialspoint.com

 https://www.geeksforgeeks.org/python-gui-tkinter/
2. Overall Description

2.1 Product Perspective

The proposed Face Recognition System will take care of the requirements of the college by managing
the attendance of students. The system will automatically be able to address all the needs of an
efficient management portal for providing the faculty all the information/functionality so that faculty
will get the most out of the application.

2.2 Product Functions

 To detect faces real time.

 To recognize the detected faces by the use of a suitable algorithm.
 Linking the information captured by the feed to the database for accuracy of results. To update
the class attendance register after a successful match.

2.3 User Classes and Characteristics

Currently the system provides only one kind of user service and that is only the user mode. The admin
will be acting as a controller and he/she will be having all the privileges of the administrator.

2.4 Operating Environment

The product will be operating in windows environment. The Technical Blog System is a website
and shall operate in all famous browsers, for a model we are taking Microsoft Internet Explorer,
Google Chrome, and Mozilla Firefox. Also it will be compatible with the IE 6.0. Most of the
features will be compatible with the Mozilla Firefox & Opera 7.0 or higher version. The only
requirement to use this online product would be the internet connection.

The hardware configuration include Hard Disk: 512 GB, at least 4GB RAM Monitor: 15” Color
monitor, Keyboard: 122 keys. The basic input devices required are keyboard, mouse and output
devices are monitor, printer etc.
2.5 Design and Implementation Constraints
Each member will be having a id which can be used for the entering the blog and issuing articles,
etc. Whenever any blogger wishes to contribute to a topic, the blogger will first be authenticated so
that no discrepancy of the login status of the user can occur.

2.6 User Documentation

Along with the product, the report and synopsis of the project will be delivered that will highlight all
the details of the project is implemented and about the various intricacies. The user documentation
formats are the ones that are usually followed in every documentation.

2.7 Assumptions and Dependencies

The assumptions are:

 The coding should be error free.
 The system should be user-friendly so that it is easy to use for the users.
 The system should have more storage capacity and provide fast access to the database.
 The system should provide effective search facility for the admin.
 Users must have their correct usernames and passwords to enter into their online accounts and
do actions.

The dependencies are:-

 The specific hardware and software due to which the product will be run.
 On the basis of listing requirements and specification the project will be developed and run.
 The end users (admin) should have proper understanding of the product.
 The system should have the general report stored.
 The information of all the users must be stored in a database that is accessible by the admin
System.

3. External Interface Requirements
3.1 User Interfaces

The software provides good graphical interface for the user and helps the user to take the
attendance easily on the system, performing the required task such as manage attendance, mark
attendance on excel sheet.

 The user interface must be customizable by the administrator.

 All the modules provided with the software must fit into this graphical user interface and
accomplish to the standard defined.
 The design should be simple and all the different interfaces should follow a standard template.
 The user interface should be able to interact with the user management module.

3.2 Hardware Interfaces

Hardware Configuration:-
 Processor:Intel i3 CPU
 Hard Disk: 512GB
 RAM:4GB

3.3 Software Interfaces

Software Configuration:-
This software package is developed using Python, OpenCV, TensorFlow, Microsoft Excel, openCV
libraries and Tkinter for front end which are supported by the 3rd party licences. Firebase is used as
the back end to store the database.
Operating System: Windows 10, Windows 8,8.1, Windows 7, Windows XP
Language: Python

3.4 Communications Interfaces

The interface for attendance is currently used locally through a local application with the help of
which the interface opens so that the user can interact with the attendance portal.
4. System Features
The users of the system should be provided the surety that their sessions is secure. This is possible
by providing:-

 The faculty’s have their separate id to mark the attendance of student by using face recognition
and the attendance marked on the excel sheet.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
The capability of the computer depends on the performance of the software. The software can take
any number of inputs provided the database size is larger enough. This would depend on the
available of memory space.

5.2 Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup so that the database is not lost. Proper
UPS/inverter facility should be there in case of power supply failure.

5.3 Security Requirements

 System will use secured database
 System should have different types of users and every user has access constraints.
 Proper user authentication should be provided.
 No one should be able to hack users’ password.
 There should be separate accounts for admin and members such that none of the members can
access the database and only admin has the rights to update the database.

5.4 Software Quality Attributes

 Maintainability: There will be no maintained requirement for the software. The database is
provided by the end user and therefore is maintained by this user.
 Portability: The system is developed for secured purpose, so it is can’t beportable.
 
 Availability: This system will available only until the system on which it is install,is
running.
 Scalability: Applicable.


5.5 Business Rules

A business rule is anything that captures and implements business policies and practices. A rule can
enforce business policy, make a decision, or infer new data from existing data. This includes the rules
and regulations that the system users should abide by. This includes the cost of the project and the
discount offers provided. The users should avoid illegal rules and protocols. Neither admin nor
member should cross the rules and regulations.

Appendix A: Analysis Models

In our project “face Recognition attendance management system”, we have made use of the
following analysis model which is the various DFD diagrams at various levels. These are :

1. Level 0 DFD

2. Level 1 DFD
3. Level 2 DFD
Appendix B: To Be Determined List
This To Be Determined (TBD) list serves to collect all currently outstanding decisions, choices, and
unresolved requirements, including questions the development team may need to ask of the project
“Face Recognition System”.

Presently there are no remaining TBDs. All TBDs have been tracked to their closure.