University of Barishal

Assignment

COURSE TITLE : Software Engineering

TOPIC : Software Requirement Specifications for

Attendance Management System
COURSE CODE : CSE-2102

SUBMITTED TO : Md Erfan
Assistant Professor
Dept. of Computer Science & Engineering
University of Barishal

SUBMITTED BY : Deepanwita Roy

Roll: 20CSE024
Dept. of Computer Science & Engineering
University of Barishal

SESSION : 2019-2020

SEMESTER : SEMESTER-05

DATE : 16-11-2023
Software Requirements Specification for Student Attendance system
Senario:

In the proposed Student Attendance Management System with an authentication system, users
(students, faculty, and administrators) would have secure access to the platform. Each user would have
unique login credentials, enhancing the system's security and ensuring that only authorized individuals
can interact with sensitive attendance and student information. The authentication process would
involve verifying the user's identity through a username and password combination. Admins would have
exclusive access to system-wide settings and student information, while faculty members would be able
to manage attendance for their assigned courses. Students, in turn, could view their own attendance
records and submit leave requests. The authentication layer not only safeguards the integrity of the data
but also provides a personalized and role-based experience, ensuring that users can access and interact
with the system based on their designated roles and responsibilities within the university's attendance
management framework.

Use case diagram elements:

The use case diagram consists of six graphics elements that represent whole system:

 Systems  Actors  Use cases  Association  Dependencies  generalization

Normal Requirements:
 User Authentication: Basic login, with the option for multi-factor authentication.
 Attendance Tracking: Manual or basic check-in/check-out, with options for automated tracking.
 Reporting: Basic attendance reports for individuals or groups.
 Integration: Integration with existing HR or school management systems.
 Notifications: Basic alerts for absentees or latecomers.
Expected Requirements:
 Real-time Updates: Real-time tracking and updates on attendance status.
 Mobile Accessibility: Mobile-friendly interface and app for on-the-go access.
 Leave Management: Integration with leave management system.
 Flexible Configurations: Customizable settings for different attendance policies.
 Scalability: Ability to scale with organizational growth.
Excited Requirements:
 Geolocation Tracking: GPS-based tracking for field employees or students.
 Biometric Authentication: Advanced biometric methods like facial recognition.
 Gamification: Gamified elements to encourage attendance.
 Automated Compliance:Automation of compliance with labor laws.
 Employee/Stuent Engagement: Features for feedback and recognition.
 Advanced Analytics: Predictive analytics for workforce planning.
Use case diagram

Fig: Use-case diagram for Software Requirements Specification for Student Attendance system

Use-Case:

1.Validate use id and password

Use-Case Validate use id and password

Primary Actor Attendence System
Goal in Context To Validate use id and password
Preconditions System is well configured and it operates well
Trigger User decides to login
Scenario User opens web system]
Type valid user id and password
Login

Exceptions If password and user id is valid, user can login

Otherwise not
Priority Essential,mush be implemented
When available First Increment
Frequency of use Regularly
Channel to actor Via web application interface
Secondary actor None
Channel to none
Secondary actor
Open issues

generate a detailed attendance report based on specified criteria in the Attendance System.

Use-Case generate a detailed attendance report based on specified criteria in the

Attendance System.
Primary Actor Attendance System Administrator
Goal in Context To generate a detailed attendance report based on specified criteria in the
Attendance System.
Preconditions The Membership Management System is operational.
The user has the necessary permissions to view member details.
Trigger The user, with appropriate authorization, decides to create a report.
Scenario Administrator logs into the Attendance System.
Administrator navigates to the "Generate Attendance Report" section.
Administrator defines the criteria for the report, specifying the date range,
individuals, and any other relevant filters.
Administrator selects the type of attendance report to be generated (e.g., daily,
weekly, monthly).
System processes the request and compiles attendance data based on the
specified criteria.
Administrator reviews the generated attendance report on the system interface,
showing details such as attendance percentages, late arrivals, and absences.
Administrator has the option to download, print, or share the attendance report as
needed
Exceptions If the user lacks the necessary permissions, the system denies access to the
member details.
If the selected member does not exist in the system, the user is notified.
Priority Essential, must be implemented
When available First Increment
Frequency of use REgularly
Channel to actor Via web application interface
Secondary actor None
Channel to none
Secondary actor
Open issues

Activity Diagram
Fig: Admin Activity Diagram
 Fig: Student Activity Diagram

Fig: Student LOGIN Activity Diagram

Swimlane Diagram:

Fig: Swimlane diagram for Software Requirements Specification for Student Attendance system

Requirement Specification

Functional Requirements

FR-01 Members Information

Description This module helps admin to register Student and Teachers. Admin is able
to maintain all the information of Student and Teachers.
Stakeholder s Admin

FR-02 Update Members Details

Description This module helps admin to update Teachers and Students’ information.
Admin and Teachers can update the details of the students and we store
these details in database.
Stakeholder s Admin, Teacher

FR-03 Unregistered Members

Description Description Admin can delete the details of the Student and Teacher. And
Teachers can delete Students details in database and Admin also deletes
these details in database..
Stakeholder s Admin, Teacher

FR-04 Search Member

Description Desc Admin and Teachers can search the details of the students and the
system displays the specific member.
Stakeholder s Admin, Teacher

FR-05 View Member Details

Description Admin as well as members can view the entire details of the students or
members who are registered.
Stakeholder s Admin, Teacher

FR-06 Check Attendance

Description Students can check only their own attendance records
Stakeholder s Admin, Teacher

FR-07 Generate Report

Description Teachers and student can download their generated report in pdf format
Stakeholder s Admin, Teacher

Safety Requirements

System would be protected by a password.

Security Requirements

 SE-1: An instructor shall permit 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.
Class Diagram

Fig: Class diagram for Software Requirements Specification for Student Attendance system