Download Software Requirements Specification for Attendance Management System and more Summaries Software Engineering in PDF only on Docsity!
Software Requirements
Specification
for
Smart Attendance Management
System
Prepared by
Group Name: ATTENDANCE MANAGEMENT SYSTEM
Baijnath Mahto BTECH/10014/20 btech10014.20@bitmesra.ac.in
Kumar Aditya BTECH/10015/20 btech10015.20@bitmesra.ac.in
Harshavardhan sinha BTECH/10016/20 btech10016.20@bitmesra.ac.in
Instructor: K. Sridhar Patnaik
Course: Software Engineering Lab (IT306)
Lab Section: A
Date: 16
th (^) September 2022
Software Requirements Specification for Page ii
- 1 INTRODUCTION...................................................................................................................................................... Contents
- 1.1 DOCUMENT PURPOSE............................................................................................................................................
- 1.2 PRODUCT SCOPE...................................................................................................................................................
- 1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW.............................................................................................
- 1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS.................................................................................................
- 1.5 REFERENCES AND ACKNOWLEDGMENTS..............................................................................................................
- 2 OVERALL DESCRIPTION.....................................................................................................................................
- 2.1 PRODUCT OVERVIEW............................................................................................................................................
- 2.2 PRODUCT FUNCTIONALITY...................................................................................................................................
- 2.3 USER CHARACTERISTICS......................................................................................................................................
- 2.4 CONSTRAINTS: -....................................................................................................................................................
- 2.5 ASSUMPTIONS AND DEPENDENCIES: -.................................................................................................................
- 3 SPECIFIC REQUIREMENTS.................................................................................................................................
- 3.1 EXTERNAL INTERFACE REQUIREMENTS...............................................................................................................
- 3.2 FUNCTIONAL REQUIREMENTS...............................................................................................................................
- 3.3 USE CASE MODEL................................................................................................................................................
- 4 OTHER NON-FUNCTIONAL REQUIREMENTS.............................................................................................
- 4.1 PERFORMANCE REQUIREMENTS..........................................................................................................................
- 4.2 SAFETY AND SECURITY REQUIREMENTS............................................................................................................
- 4.3 SOFTWARE QUALITY ATTRIBUTES.....................................................................................................................
1.4 Definitions, Acronyms and Abbreviations
Abbreviations:-
GPS: Global Positioning System. SRS: Software Requirements Specification. GAIL: Gas Authority of India Ltd. DB: Database. RAM: Read only Memory.
1.5 References and Acknowledgments
- IEEE SRS DOCUMENT - https://docs.google.com/document/d/1IcNg8N_GNAF14Hv-UuEe6l2G7qkpEzv3/ edit?usp=sharing&ouid=103722181419596063687&rtpof=true&sd=true
- Problem Statement - https://docs.google.com/document/d/1V8wCJQlWk7A35IIIsE4PNpFQ_3o1BLgQ/ edit?usp=sharing&ouid=103722181419596063687&rtpof=true&sd=true Term Definition Face Recognition Facial recognition is a category of biometric security. Other forms of biometric software include voice recognition, fingerprint recognition, and eye retina or iris recognition. Geo fencing Geo-fencing (geofencing) is a feature in a software program that uses the global positioning system (GPS) or radio frequency identification (RFID) to define geographical boundaries. Blockchain blockchain is the foundation for immutable ledgers, or records of transactions that cannot be altered, deleted, or destroyed. Database A database is an organized collection of structured information, or data, typically stored electronically in a computer system. User a person who uses or operates something. Admin A person who has specific controls to a forum/website/etc. that allows them to control the forum/website/etc Software Requirements Specification A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document. Stakeholder Any person with an interest in the project who is not a developer.
- What Is Facial Recognition Attendance System and Its Benefits - https://www.lystloc.com/blog/what-is- facial-recognition-attendance-system-and-its-top-benefits-in-the-workplace/
- Guide on Building A Face Attendance System - https://analyticsindiamag.com/a-complete-guide-on- building-a-face-attendance-system/
- Blockchain App Development - https://appinventiv.com/blog/blockchain-app-development-guide/
- Geofence Implementation - https://www.excellarate.com/blogs/basics-geofence-implementation/
- View attendance report of employees. Attendance can be filtered by date or employee. Following functionalities can be performed by the employee: -
- Login
- Mark his/her time-in and time-out by scanning their face
- View attendance report of self
2.4 Constraints: -
As the system is using face recognition feature to identify each employee of the organization, it must be able to identify each of them individually. According to this, system must be capable to mark their presence for the day and it should convey the same message to the employee as well.
- According to the data protection act the data of the employee should not be shared for financial purposes.
- The employee should be present within 100 meters of the office premises.
- Response time should not be 5 seconds.
- It should successfully recognize the specific employees with or without wearing spectacles, cap, or industrial helmet
2.5 Assumptions and Dependencies: -
- Network should be available
- Employee should be registered in the system to mark the attendance
- Databases of the employee should be present in the system for proper functioning of the face recognition system.
- The mobile should have GPS inbuilt.
3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces: - The user interface of this system should be simple and clear for the ease of use of employees. The color scheme should be appropriate to provide familiarity with the company and there should be no contrast issues. The different functions in the app should be easily accessible through the side menu or search bar. 3.1.2 Hardware Interfaces: -
- Working camera with clear image.
- Memory: 500MB RAM
- Snapdragon 420 processor or equivalent and higher.
- GPS 3.1.3 Software Interfaces: -
- Android app
- Employee side browser support
- Server-side Django + SQLITE Database Support .
3.2 Functional Requirements
System must capture faces System must store faces in a DB attached to the employee’s ID System must recognize the employee to enable attendance marking. System must be able to fetch the location
3.3.1 Use Case
Topic: Fetch details
Description:
To get about employees like Photograph (headshot), Name, Designation, Employee
Number, Gender, Office Address, etc.
Actors: Admin, Employee
Preconditions :
1. Website must be in active state.
2. Employee must be registered.
Post conditions :
- Details Page displays the various details of the employee. Flow of Events:
- Employee Clicks on Fetch Details.
- Site receives the request and identifies the login id.
- Then the site requests to fetch details of the employee from database.
- The database then searches the employee id and fetches the details.
- Site displays the related information to the employee. Alternative Flow: If the Employee details isn’t available: -
- No details found message displayed.
- Enter the missing details first message displayed.
Exception :
1. No Network available.
Requirement :
1. The details of the employee must be present in the database.
3.3.2 Use Case #
Topic: Authentication
Description:
To verify that the same person is trying to add attendance and is present in the office
premises.
Actors: Admin
Preconditions :
1. Website must be in active state.
2. The camera of the device and GPS of the device should work.
3. The Face Data should be present in the Database.
Post conditions :
- The attendance of the person should be marked. Flow of Events:
- The app asks for GPS and camera access.
- The app fetches the location and verifies that it is under the preferred location.
- Then the app clicks the image of the person and tries to verify it from the database.
- After verification, it leads to attendance marked page. Alternative Flow: If the Location isn’t inside office: -
- Location invalid page opens
- Please move to 100 meters near the office premises If the Face isn’t verified: -
- Face not recognized page opens.
- Click another picture with eyes open and in sufficient light, message displays.
Exception :
1. No GPS and camera available.
Requirement :
1. The face data of the employees should be stored in database.
This system may face many threats. Sometimes, it comes from a community insider. This could be someone who discloses the data form the database where it located, in the registration office. Another type of deception is false identification, such as a fake ID, when employees present in the registration office. The system will reduce this kind of misuse because the face identification is more secure than others. Nobody can make up a face not related to them. However, admin in the registration office should check on the identification carefully before initiating any processes in the system. These records will be the official record for all employees since they begin job. Level of access Subject: People level:
- Users (Employee).
- Admin (control the system). Computer level:
- Hardware (camera and GPS)
- Software (the system)
4.3 Software Quality Attributes
- Maintainability: Software should be written in such a way so that it can evolve to meet the changing needs of customers. This is a critical attribute because software change is an inevitable requirement of a changing business environment.
- Dependability and security: Software dependability includes a range of characteristics including reliability, security, and safety. Dependable software should not cause physical or economic damage in the event of system failure. Malicious users should not be able to access or damage the system.
- Efficiency: Software should not make wasteful use of system resources such as memory and processor cycles. Efficiency therefore includes responsiveness, processing time, memory utilisation, etc.
- Acceptability: Software must be acceptable to the type of users for which it is designed. This means that it must be understandable, usable and compatible with other systems that they use.
- Simplicity, Reuse Possibilities and Robust Code.
