SOFTWARE ENGINEERING LAB 2

CREATING A SRS

STUDENT ATTENDANCE MONITORING SYSTEM

Table of Contents

1. Introduction............................................................................................................ 1
1.1 Purpose 1
1.2 Scope 1
1.3 References 1
1.4 Overview 1
2. The Overall Description .........................................................................................1
2.1 Product Perspective 1
2.2 Product Functions 1
2.3 User Characteristics 1
2.4 Constraints 2
2.5 Assumptions and Dependencies 2
3. External interface Requirements .......................................................................... 2
3.1 User Interfaces 2
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 3
4. System Features ……………………………………………………………………….4
5. Other Non-Functional Requirements………………………………………………….6
5.1 Performance Requirements 6
5.1.1 Static Requirements 6
5.1.2 Dynamic Requirements 6
5.2 Software System Attributes 6
5.2.1 Reliability 6
5.2.2 Availability 7
5.2.3 Security 7
5.2.4 Maintainability 7
5.3 Business Rules 7
6. Other Requirements ..............................................................................................8
Appendix A: Glossary 9
1. Introduction

1.1 Purpose
The purpose of developing attendance management system is to computerized the tradition
way of taking attendance. Another purpose for developing this software is to generate the report
automatically at the end of the session or in the between of the session.This document detailed
functional and non-functional requirements for attendance maintenance system.

1.2 Scope
This system allows the teacher to maintain attendance record of the classes to which it is
teaching. With the help of this system Teacher should be in a position to send e-mail to the
students who remain absent for the class. The system provides a cumulative report at every
month end for the corresponding class.

1.3 References
The references for the above software are as follows:-
i. www.google.com
ii. www.wikipedia.com
iii. IEEE. Software Requirements Specification Std. 830-1993.
iv. Prohance Attendance App
URL: https://www.prohance.net/attendance-and-timesheet
v. www.academia.edu

1.4 Overview
This system provides an easy solution to the teacher to keep track of student attendance and
statistics.

2. The Overall Description

2.1 Product Perspective

The Attendance Management System is intended to replace the manual model of attendance
record keeping by means of roll call and paper records. The roll call and paper records are
replaced with a single interaction between the professor 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.

2.2 Product Functions

The main feature of the Attendance Management System is that it keeps a record of all
essentials details of each individual student. At the end of a specified period this system creates
a defaulters list as well as the non-defaulters list. Attendance Percentage of each student in
every subject would be displayed in this list.

2.3 User Characteristics

Professors :- A professor is a faculty member of a university. There are n number of faculty
members at the university and it is estimated that almost all faculty members will utilize the
Attendance Management System. Professors will have multiple classes and interaction with the
system will occur at multiple times throughout the day from multiple professors. The professor
should be allowed to take, edit, and view attendance records at any desirable time. All
professors have Internet access through their PC’ s.

2.4 Constraints
1: The time allotted for this project will be limited to the end of this semester.
2: The language for the project will be Visual C++ and the development environment will
be the embedded Visual C++ 3.0 environment.
3: All the HTML code for the user manual will conform to the HTML 4.0 standard.
4: Programming is done in JAVA, SQL, HTML.

2.5 Assumptions and Dependencies

AS-1: The database mentioned within this Software Requirements Specification document is
previously administered with the correct information needed by the Attendance
Management System.
AS-2: For attendance policies, since professors do not usually tabulate tardiness, it is assumed
a student is either present or absent. The system also assumes that detail regarding each
student would be made correctly.
DE-1: Class data being used for setup and student recognition is dependent on information in a
database administered outside of the capabilities of the Attendance Management System.
DE-2: Statistics on student attendance is dependent on a professor’ s consistent utilization of
the system for each class period

3. External interface Requirements

3.1 User Interfaces

UI-1: The Attendance Management System shall provide details of students in the class to aid in
taking roll.
UI-2: These details can be clicked with a mouse in order to view a particular student’s
attendance record.
UI-3: All modifications to the database will be done through a keyboard.
UI-4: Application will be accessed through a Browser Interface. The interface would be viewed
 best using 1024 x768 and 800 x 600 pixels resolution setting.
UI-5: The program will provide a page that produces current statistics on class attendance.

3.2 Hardware Interfaces

Server Side:
H1: Operating System: Windows 7/xp/vista, Windows ME
H2: Processor: Pentium 3.0 GHz or higher
H3: RAM: 512Mb or more
H4: Hard Drive: 128 Mb or more

Client side:
H5: Operating System: Windows 7 or above, MAC or UNIX.
H6: Processor: Pentium III or 2.0 GHz or higher.
H7: RAM: 512 Mb or more

3.3 Software Interfaces

SI-1: Attendance Management System

SI-1.1: This software will transmit the attendance of a class to a database on a machine
via Internet.
SI-1.2: The user will be allowed to modify attendance records at any time.
SI-1.3: If the user forgets to transmit the information, the system will automatically send it
for them at the end of the class.

SI-2: Database
The Attendance Management System will communicate with the database to perform the
following options.
SI-2.1: To allow a user to enter attendance.
SI-2.2: To allow a user to modify attendance.
SI-2.3: To allow a user to query a system to gain statistics concerning individual and
Class attendance.

3.4 Communications Interfaces

CI-1: The security of a user must be consistent through the use of passwords.
CI-2: The Attendance Management System will communicate to the database through Internet.

4. System Features

The attendance system has been built to eliminate the time and effort wasted in taking
attendance in schools and colleges. It also greatly reduces the amount of paper resources
needed in attendance data management.
Functional Requirements

4.1. Adding a New student:

Function: Sign up a new student to the system.
Priority: Top (Required for first release)
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 scan their thumbs in the input device for only one time to save the
fingerprint data in the registration office to sign up.

4.2 Use the system to attend to classes

Function: Attend to classes

Priority: Top (Required for every class attended)
Requirements: When students have a class, they must scan their thumbs in the
fingerprint input device. If the scan matches, students can enter the class, and they will
be checked on the Canvas page. If the scan does not match, the student must check
with the registration office to figure out the checking device.

4.3 Report students

Function: The user will look at their reports for the current status.
Priority: Top (Required for first release)
Requirements: When the students have enrolled in the class, they are now able to
check on their current attendance situation through the Canvas 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.

Priority: Top(Required for first release)
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.5 Students missed classes

Function: Students receive a message for missing class and have to submit a form.
Priority: High (Required for second release)
Requirements: When a student misses a class, he/she will receive a message via email
and Canvas page. Students must long in to the Canvas page and go to the attendance
page to write the reason for missing the class. Students have to submit the form to wait
for the response of the faculty’s decision.

4.6 Students missed two classes and more

Function: Students receive a warning message for missing class for the second time.
Priority: High (Required for second release)
Requirements: When students miss more than one class, students will receive a warning
message for missing two classes or more. The warning message should be for the
 missed classes for the whole semester and their status in a danger level.

4.7 Faculty check the report and the attendance control panel page

Function: Users can provide feedback about search terms.

Priority: Medium (Second release if possible, mandatory for third release)
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. For students who submit the note for the missed class, faculty members could look
at the note and give a decision on the student’s grades.

5. Other Non-Functional Requirements

5.1 Performance Requirements

Easy tracking of records and updating can be done.all the requirements relating to
performance characteristics of the system are specified in the section below.There are 2
types of requirements.

A. Static Requirements:
These characteristics do not impose any constraints on the execution characteristics of
the system.They are:

a. No. of terminals:
The software makes use of the underlying database that will reside at the
server,while the front end will be available online to the administrative and
departmental courses as well as students and teachers.

b. No. of Users:
The number of users may vary, as this software finds applications in almost all
departments.

B. Dynamic Requirements:
These specify constraints on the execution characteristics of the system.They typically
include response time and throughout of the system. Since these factors are not
applicable to the proposed software,it will suffice if the response time is high and the
transactions are carried out precisely and quickly.

5.2 Software System Attributes

5.2.1 Reliability
Due to wireless connectivity, reliability cannot be guaranteed. However, overall reliability
of the system and roll number information shall be achieved through the process of
database manipulation.
5.2.2 Availability
The system should be available during college hours.

5.2.3 Security
SE-1: An instructor shall permitted to view and edit absence information in the database
for only his/her classes.
SE-2: In order to take roll or edit database information, the instructor shall be required to
enter a password. This password shall be stored on the instructor’ s PC after initial
entry in order that it must only be entered once.
SE-3: Passwords shall be stored in an instructor database and verified upon each
session of roll or database modification.
SE-4: An instructor shall be allowed to change his/her password only by supplying
his/her existing password. The updated password shall be stored in the instructor
database and on the instructor’s PC.

5.2.4 Maintainability
There should be a facility to add or delete or update teachers and students for each
Semester.

5.3 Business Rules

5.3.1 Attendance Recording

The system must provide a feature for faculty members to record student attendance for
each class session.

5.3.2 Attendance Marking

Attendance can be marked as Present, Absent, Late, or Excused.

5.3.3 Attendance Tracking

The system should maintain a comprehensive record of attendance for each student for
every class session throughout the academic term.

5.3.4 Access Control

Only authorized faculty members should have access to mark attendance.

5.3.5 Student Identification

The system should accurately identify each student to ensure attendance is marked for
the correct individuals.

5.3.6 Attendance Reports

The system should generate attendance reports for individual students as well as entire
classes, displaying attendance percentages, dates of absences, and any remarks.

5.3.7 Notification System

Automated notifications should be sent to students and/or guardians in case of frequent
absences or irregular attendance patterns.
5.3.8 Attendance Policies
The system should support customization of attendance policies, including minimum
attendance requirements for courses and consequences for excessive absences.

5.3.9 Integration
The system should be capable of integrating with other academic systems, such as
grading and scheduling software, to streamline administrative processes.

5.3.10 Data Security

Attendance data should be securely stored and accessible only to authorized personnel,
in compliance with relevant data protection regulations.

5.3.11 Attendance Corrections

Faculty members should have the ability to make corrections to attendance records in case
of errors or omissions.

5.3.12 Audit Trail

The system should maintain an audit trail of all attendance-related activities, including who
marked attendance, when it was marked, and any modifications made.

5.3.13 Real-time Updates

Attendance records should be updated in real-time to reflect changes as they occur,
ensuring accuracy and reliability.

5.3.14 Student Participation

The system should encourage student participation in the attendance tracking process,
allowing students to view their own attendance records and report any discrepancies.

5.3.15 Accessibility
The system should be accessible via multiple devices, including desktop computers,
tablets, and smartphones, to accommodate the diverse needs of users.

6. Other Requirements

6.1 Automated Reminders

The system shall send automated reminders to faculty and students for upcoming
classes or events to improve attendance punctuality.

6.2. Geolocation Tracking

The system shall implement geolocation tracking to verify the physical presence of
students during class sessions, especially for remote or hybrid learning
environments.

6.3. Attendance Gamification

The system shall introduce gamification elements, such as rewards or badges, to
incentivize regular attendance and increase student engagement.
6.4. Parental Access
The system shall provide parents or guardians with limited access to view their child’s at
child's attendance records and receive attendance-related notifications.

Appendix A: Glossary

This subsection contains definitions of all the terms, acronyms, and abbreviations used in the
document. Terms and concepts from the application domain are defined.

● SRS: Software Requirement Specification

● RAM: Random Access Memory
● OS: operating system
● DB: Databases
● PHP: Personal Home Page
● SQL: Structured Query Language