Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

software specification requirement on Face Recognition Attendence System, Papers of Software Project Management

Complete description on face recognition attendance system

Typology: Papers

2020/2021
On special offer
30 Points
Discount

Limited-time offer


Uploaded on 12/10/2021

mustafa.k
mustafa.k 🇮🇳

5

(6)

4 documents

1 / 12

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
Software Requirements Specification for Face
Recognition Attendance System
A Software Engineering Case Study Report
on
Face Recognition Attendance System
Prepared
by
Mustafa Bohra
Mustansir Daulat
Pratik Kadam
Raj Kunwar Singh
Under the guidance of
Ms. Swati.V. Jadhav
Bansilal Ramnath Agarwal Charitable Trust's
Vishwakarma Institute of Technology
666, Upper Indiranagar, Bibwewadi,
Pune, Maharashtra, INDIA - 411 037
pf3
pf4
pf5
pf8
pf9
pfa
Discount

On special offer

Partial preview of the text

Download software specification requirement on Face Recognition Attendence System and more Papers Software Project Management in PDF only on Docsity!

Software Requirements Specification for Face Recognition Attendance System

A Software Engineering Case Study Report

on

“ Face Recognition Attendance System ”

Prepared

by

Mustafa Bohra

Mustansir Daulat

Pratik Kadam

Raj Kunwar Singh

Under the guidance of

Ms. Swati.V. Jadhav

Bansilal Ramnath Agarwal Charitable Trust's

Vishwakarma Institute of Technology

666, Upper Indiranagar, Bibwewadi, Pune, Maharashtra, INDIA - 411 037

Software Requirements Specification for Face

Recognition Attendance System

    1. Introduction................................................................................................................................ Table of Contents
    • 1.1 Purpose.............................................................................................................................................
    • 1.2 Document Conventions.....................................................................................................................
    • 1.3 Intended Audience and Reading Suggestions...................................................................................
    • 1.4 Product Scope...................................................................................................................................
    • 1.5 References.........................................................................................................................................
    1. Overall Description....................................................................................................................
    • 2.1 Product Perspective...........................................................................................................................
    • 2.2 Product Functions.............................................................................................................................
    • 2.3 User Classes and Characteristics.......................................................................................................
    • 2.4 Operating Environment.....................................................................................................................
    • 2.5 Design and Implementation Constraints...........................................................................................
    • 2.6 User Documentation.........................................................................................................................
    • 2.7 Assumptions and Dependencies........................................................................................................
    1. External Interface Requirements.............................................................................................
    • 3.1 User Interfaces..................................................................................................................................
    • 3.2 Hardware Interfaces..........................................................................................................................
    • 3.3 Software Interfaces...........................................................................................................................
    • 3.4 Communications Interfaces...............................................................................................................
    1. System Features.........................................................................................................................
    1. Other Nonfunctional Requirements.........................................................................................
    • 5.2 Performance Requirements...............................................................................................................
    • 5.3 Safety Requirements........................................................................................................................
    • 5.4 Security Requirements......................................................................................................................
    • 5.5 Software Quality Attributes..............................................................................................................
    • 5.6 Business Rules.................................................................................................................................

2. Overall Description

2.1 Product Perspective

In University or school , Professors manually take attendance in every class each day. They spend time to do that during class time and almost 10 minute last in taking. The Automatic Attendance System will help them do this process in an easy way. The main scope of this project is to make attendance process more organized in every class. This project will help Professors take the attendance automatically without spending some time during the class. They will also know the current grade in their reports. It makes it easier to have a clear picture of every student’s attendance throughout the academic year. The system is about to modify an existing system to develop the project, which contains classes managed by Professors. It has management tools for courses. These tools play a significant role in the educational models these days, which are to organize the educational level using technology to achieve the educational goals easily. Professors have the control panel for every class they have. The control panels allow them to create and develop the course’s page that all students can see. They may have a Home Page, Syllabus, Discussion, Grade, Assignments, People, Files, and more. All of these components are available and controlled by the faculty member to make any changes. Definitions: Users: This means students who will get the most benefits of the system. Faculty: Also, who has the top priority to get benefit for the system and they are the target actors of the system. The Registration Office: This is for the system management, and it will be presented by the employees.

2.2 Product Functions

There are two kinds of process models for this system. There is the overview process model and the conditional process model. Starting with the first one. The first step of this process is to have a camera for face detection of staff or a student. That will do the following steps:

  1. Students Register there picture to the admin
  2. Every face has a special code number for every recode. This code number takes the other step, which is matching.
  3. The system checks on the face and sends to the server and the student database.
  4. This database file, the system checks this face for the identification. Also, the database sends it to the registration office data file to check if this code exists or not. If the code number for the face is in both databases, the code number will continue for other steps. And if the code is not there, it will give you a false result. Then, it will send you to the registration office for the identification and look for your record to modify it if there is any issue. Then, students will try again.
  1. Checkpoint, which will check if the student data is enrolled in the particular class or not. If yes, the process will continue, and if not, the system will send you to the registration office to check. There is also another process for this project that if a student missed a class, the system would make a decision. The aim of this process is to contain every student’s status and make sure the attendance for all students has already been taken. After ten minutes of the class time, the system will run automatically to check on the attendance page. If all students attended in that class, the system will send a report to them and stop. However, if there are students who missed the class, the system would start some process. The system will check for who is missing the class and make a list of them. Every student of this list will receive a message that asks them for the reason of the missing the class. Furthermore, if the Confidential student has an acceptable reason that he/she provides to faculty, the system will automatically report them, and the system will be done

2.3 User Classes and Characteristics

There are three types of user classes in this community:

  1. Students
  2. Faculty
  3. Registration Office

2.4 Operating Environment

This project will go through steps: The first step is to have the automatic attendance device in every classroom in the school. These devices will be connected to the computer and its system. Students have to put their photo on file in the registration office on their first day to save their photo record in the database. This system has some requirements to be accomplished. It needs hardware and software. Hardware requirements:

  1. Camera for Face Capture
  2. Cables for the device The current system work is already in existence. However, we need some system requirements:
  3. Create new databases and indexes for students and class list by using mysql
  4. Make connection to the current database
  5. Design interfaces for the users
  6. Design an attendance page
  7. Programing using JavaScript, PHP , Python and HTML

2.5 Design and Implementation Constraints

2.6 User Documentation

Technically speaking, a useful user document should have all documentation and essentials that are required and related to the entire product cycle. The user documentation is a part of the overall product delivered to the customer; end-to-end.

information, faculty information, class’s information, and other related information. All of these data are stored in the database and end with the device screen and web pages.

3.3 Software Interfaces

The system will use:

  1. High –definition Camera for scanning a Face
  2. Web pages for the forms HTML, PHP
  3. Server
  4. Programing using JavaScript , Python
  5. Database uses with mysql  Google Chrome.  Safari  Microsoft Edge.  Brave  DuckDuckGo

3.4 Communications Interfaces

 Camera and system should be connected via wire or internet.

4. System Features 4.1 Adding a New student Function: Sign up a new student to the system. Requirements: To add a new user to the system, all of them should have registered in the admission office before they can register in their classes. On the orientation day, all students must add their photo for only one time to save the photo in the registration office to sign up 4.2 Adding a New Faculty Function: Sign up a new student to the system. Requirements: To add a new user to the system, all of them should have registered in the admission office before they can register in their classes. On the orientation day, all students must add their photo for only one time to save the photo in the registration office to sign up 4.2 Use the system to attend to classes Function: Attend to classes Automated Face detection system detect the face of the student in the classroom and create excel sheet who all are present and who is missed the class 4.3 Report students Function: The user will look at their reports for the current status. Requirements: When the students have enrolled in the class, they are now able to check on their current attendance situation through the web page in the system, they will be shown a page that gives them the whole attendance status in the semester. 4.4 Faculty receive a report Function: Faculty receives a current report every class.

Requirements: The system will send a message after ten minutes of the class time to the faculty. Faculty will have the all students’ attendance reports in the particular class. Faculty can modify some of the attendance grades if he/she needs. 4.6 Faculty check the report and the attendance control panel page Function: Users can provide feedback about search terms. Requirements: Faculty has to check on the report and give the final submission. Faculty has full control of modifying any grades and looking at students who have excuses to modify their grades. Faculty receive messages from the system about students who missed classes.

5. Other Nonfunctional Requirements  Maintenance: Proper maintenance of every camera for proper detection  Reliability: Pretty much accurate all the time so no mistake in taking attendance

5.1 Appearance

 The user interface should be interactive.

 The app should be easy-to-navigate.

5.2 Performance Requirements

 Concurrency:

Uploads allowed from a particular student/faculty shall be done at the same instance to ensure an acceptable speed.

 Continuous Availability and Reliability:

The connection to the servers should be robust to ensure proper working at every-time.

5.3 Safety Requirements

 The servers should be properly maintained to for their proper working.  The camera lenses should be clean for proper detection of the faces.

5.4 Security Requirements

 Login details like Passwords , should not be stored as plain texts. Passwords should be encrypted. Cryptography tools like Hashing and salting algorithms should be used.  The decryption algorithms should be in reach of only the concerned administrative staff.

5.5 Software Quality Attributes

 System must contain this properties or feature like availability, interoperability, correctness, reliability, learnability, robustness, maintainability, readability, extensibility, testability,

Appendix B: Models

6.1 Use Case Diagram –

Fig 1 – Use Case Diagram

6.2 Class Diagram

Fig 2 – Class Diagram