OBJECT-ORIENTED SOFTWARE ENGINEERING (SE202)

LAB MANUAL

Subject Code: SE202

Subject Name: Object-Oriented Software Engineering
Branch: Software Engineering
Year: 2nd Year (4th Semester)

Submitted by:
SHREYANSH PALWALIA (2K22/SE/167)
UMESH PATIL (2K22/SE/186)

Submitted to:
Ms. Ruchika Malhotra
Head of Department
Department of Software Engineering

Department of Software Engineering

Delhi Technological University

Shahbad Daulatpur, Main Bawana Road, Delhi-110042
 INDEX

SNO. EXPERIMENT DATE SIGNATURE

1. Problem Statement
2. Initial Requirement
Documentation
3. Software
Requirement
Specification
4. Test case Matrix
 PROBLEM STATEMENT
The goal of the Attendance Tracking Management System is to capture time and
attendance data for accurate payroll processing and an insight into workforce
productivity for an organization. An employee electronically marks his in time and
out time everyday in order for proper calculation of attendance data. This data should
be further processed to provide overtime management and absence management.

The key issues related to the existing system are-

 Manual Processes: The existing manual methods for tracking attendance require
significant time and effort from administrators and teachers. Manually recording
attendance is prone to errors and can lead to inaccuracies in attendance records.
 Lack of Real-Time Updates: Paper-based or spreadsheet-based systems do not
provide real-time updates on attendance status. This leads to delays in identifying
absenteeism or tardiness, making it difficult for administrators to take timely
action.
 Inefficient Reporting: Generating attendance reports using manual methods is
labor-intensive and time-consuming. Administrators often face challenges in
consolidating attendance data and producing accurate reports for analysis or
compliance purposes.
 Difficulty in Monitoring: Without a centralized system for attendance tracking,
monitoring attendance across multiple classes or locations becomes challenging.
This can result in inconsistencies in attendance recording and difficulty in
enforcing attendance policies uniformly.
 Limited Accessibility: Paper-based systems restrict access to attendance records,
making it difficult for stakeholders such as teachers, students, and parents to
access real-time attendance information.

The objectives of attendance tracking management system are-

 Automate Attendance Recording: Develop a system that automates the process of

recording attendance, reducing the reliance on manual data entry and minimizing
errors.
 Real-Time Updates: Implement features that provide real-time updates on
attendance status, allowing administrators and teachers to promptly identify
absenteeism or tardiness.
 Efficient Reporting: Create functionalities for generating comprehensive and
customizable attendance reports effortlessly. These reports should facilitate data
analysis and support decision-making processes.
 Centralized Monitoring: Establish a centralized platform for monitoring
attendance across multiple classes, departments, or locations. Ensure consistency
in attendance recording and enforcement of attendance policies.
 INTIAL REQUIREMENT DOCUMENT

Title of the project Attendance Tracking Management System

Stakeholders involved in capturing requirements Student, Administrative staff, Teachers,Head
of Department
Techniques used for capturing requirements Interviewing and Use case
Name of the person along with the designation
Date 5th February,2024
Version 1.0
Consolidated list of initial requirements:

1) User Authentication: Secure login system for administrators, teachers, and students.
2) Role-Based Access Control: Different levels of access for administrators, teachers, and
students.
3) Attendance Recording: Ability to record attendance for individual classes or sessions.
4) Multiple Attendance Methods: Support for various attendance tracking methods (e.g., manual
entry, barcode scanning, biometric recognition).
5) Real-Time Updates: Instantaneous updating of attendance records.
6) Attendance Reports: Generate comprehensive reports on attendance data for administrators
and teachers.
7) Customizable Reporting: Ability to customize reports based on different parameters (e.g., date
range, class, student).
8) Automatic Notifications: Automated alerts for absentees or latecomers to teachers and
administrators.
9) Integration with Student Information System (SIS): Sync attendance data with the existing
student information system
10) Data Security: Ensure the security and privacy of attendance records.
11) Data Backup and Recovery: Regular backups and a recovery plan for attendance data.
12) Attendance Policies: Ability to configure attendance policies (e.g., minimum attendance
requirements, late policies).
13) Mobile Accessibility: Access to the system via mobile devices for both teachers and
administrators.
14) Customizable Interface: Interface customization options for different user preferences.
15) Scalability: Ability to scale the system to accommodate a growing number of users and
data.
16) Integration with Timetable: Integration with the school or institution timetable for easier
tracking.
17) Leave Management: Capability to manage and track leave requests for students and
teachers.
18) Audit Trail: Maintain an audit trail for all attendance-related activities for accountability.
19) Cross-Platform Compatibility: Compatibility with different operating systems and web
browsers.
20) Training and Support: Provision of training materials and ongoing support for users.
 SOFTWARE REQUIREMENTS SPECIFICATION
ATTENDANCE TRACKING MANAGEMENT SYSTEM

TABLE OF CONTENT

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, acronyms, and abbreviations
1.4 References
1.5 Overview

2. Overall description
2.1 Product perspective
2.1.1 System interfaces
2.1.2 User interfaces
2.1.3 Hardware interfaces
2.1.4 Software interfaces
2.1.5 Communication interfaces
2.1.6 Memory constraints
2.1.7 Operations
2.1.8 Site adaptation requirements
2.2 Product functions
2.3 User characteristics
2.4 Constraints
2.5 Assumptions and dependencies
2.6 Apportioning of requirements

3. Specific requirements
3.1 External interfaces
3.2 Functions
3.3 Performance requirements
3.4 Logical database requirements
3.5 Design constraints
3.5.1 Standards compliance
3.6 Software system attributes
3.6.1 Reliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
3.7 Organizing the specific requirements
3.7.1 System mode
3.7.2 User class
3.7.3 Objects
3.7.4 Features
3.7.5 Stimulus
3.7.6 Response
 3.7.7 Functional Hierarchy
3.8 Additional comments

4. Supporting information
1. PURPOSE

1.1 PURPOSE

The attendance tracking system makes easier for users to manage attendance records
efficiently, providing functionalities for logging attendance, generating reports, and
notifying relevant parties about attendance-related matters. It enables administrators,
teachers, and students to access and utilize attendance data for various purposes, such
as monitoring attendance trends, managing leave requests, and sending notifications.

1.2 SCOPE

The purpose of the Attendance Tracking Management System is to perform the

following functions:

1. User Authentication and Management:

- Generate login details for administrators, teachers, and students.
- Allow users to log in to the system securely.

2. Attendance Management:
- Administrators can mark attendance for classes.
- Teachers can mark attendance for their classes.
- Students can view their attendance records.

3. Attendance Reporting:
- Generate detailed reports based on attendance data for specific time frames,
departments, or individuals.

4. Notification System:
- Automatically send notifications to students and parents/guardians regarding
attendance-related matters such as absences, tardiness, or low attendance rates.

5. Monitoring and Analysis:

- Monitor attendance trends over time, track overall rates, identify classes or
students with recurring attendance issues, and implement interventions as necessary.

6. Leave Management:
- Students can submit leave requests for anticipated absences.
- Teachers and administrators can review and approve/reject these requests.

1.3 DEFINTIONS, ACRONYMS and ABBREVATIONS

SRS: Attendance Tracking System Requirement Specification.

ADMIN: The user role responsible for managing the Attendance Tracking System,
including user accounts, permissions, and system configurations.
ATMS: Attendance Tracking System, the software used to monitor and manage
attendance records.
1.4 REFERENCES

● Object-Oriented Software Engineering by Yogesh Singh & Ruchika Malhotra, PHI

Learning Private Limited.
● IEEE Recommended Practice for Software Requirements Specifications— IEEE
Std 830-1998.
● IEEE Standard for Software Test Documentation—IEEE Std. 829-1998.

1.5 OVERVIEW

This document is prepared to explain all detailed information about the overall system
description, functional, non-functional, and specific requirements, data, and
behavioural model description of the system. This document basically consists of
three parts: the first part includes an introduction and an overall description of the
application. The second part contains specific requirements, data, and behavioural
model descriptions of the system, which are sections 3, 4, and 5 in the document. The
last part gives planning, a conclusion, and supporting information about the system.

2. OVERALL DESCRIPTION

The Attendance Tracking Management System is a comprehensive web-based

application designed to simplify the process of tracking and managing attendance for
educational institutions or organizations

2.1 PROUDCT PERSPECTIVE

The Attendance Tracking Management System allows authorized users to effectively

manage attendance records for various entities such as students, teachers, and
administrators. It provides functionalities for logging attendance, generating reports,
managing user accounts, and sending notifications. The system aims to streamline the
process of tracking attendance, ensuring accuracy and efficiency.

The system operates as a centralized platform for recording attendance data, providing
users with easy access to relevant information. Through the system interface,
administrators can manage user accounts, including adding, deleting, updating, and
viewing user information. Teachers can mark attendance for their classes, while
students can submit leave requests for anticipated absences.

Online access to the system has made attendance management more convenient and
efficient than traditional methods. It allows for real-time tracking of attendance,
reducing manual effort and minimizing errors. The system also provides features for
generating detailed reports on attendance trends over time, enabling users to identify
patterns and take necessary actions.
2.1.1 SYSTEM INTERFACES

Authentication System:
- Responsible for user login and authentication.
 - Ensures that only authorized users can access the system.

Database System:
- Stores attendance data, user information, and system configurations.
- Provides a structured storage environment for efficient data retrieval and
manipulation.

Reporting Module:
- Generates attendance reports based on user-defined parameters.
- Allows users to analyze attendance trends and make data-driven decisions.

Notification System:
- Sends automated alerts and notifications to users regarding attendance-related
matters.
- Keeps users informed about leave approvals, attendance trends, and other
important updates.

2.1.2 USER INTERFACES

● Login: Permit only authorized users to access the system by providing valid login
credentials (username and password).
● Registration: Enable users to create an account within the Attendance Tracking
Management System.
● Mark Attendance: Enable authorized users (teachers or administrators) to mark
attendance for students or employees.
● View Attendance Records: Provide users with the ability to view attendance records
for specific classes, students, or time periods.
● Manage User Data: Allow administrators to add, delete, update, and view user
information within the system.
● Generate Attendance Reports: Provide functionality for generating detailed reports
based on attendance data for specific time frames, departments, or individuals.
● Send Attendance Notifications: Enable automated notifications to be sent to
students and their parents/guardians regarding attendance-related matters such as
absences, tardiness, or low attendance rates.
● Monitor Attendance Trends: Allow administrators to monitor attendance trends
over time, including tracking overall attendance rates, identifying classes or students
with recurring attendance issues, and implementing interventions as necessary.
● Manage Leave Requests: Enable students to submit leave requests through the
system for anticipated absences, which can be reviewed and approved/rejected by
teachers or administrators.
● User Interfaces: Provide intuitive interfaces for all aforementioned functionalities to
ensure ease of use and efficient navigation within the system.

2.1.3 HARDWARE INTERFACES

Screen resolution: At least 640x480 or above for optimal display of system interface
and data.
Support for printers: Compatibility with various printer types including dot matrix,
Deskjet, and laserjet printers for printing attendance reports and notifications.
Networked environment: Computer systems should be able to connect to a network as
the system is designed to be used in a multi-user environment, allowing for seamless
communication and data sharing among users.

2.1.4 SOFTWARE INTERFACES

● MS-Windows Operating System (NT/XP/Vista).

● Microsoft Visual Studio Code
● MS SQL Server 2005 for back-end.

2.1.5 COMMUNICATIONS INTERFACES

The Attendance Tracking Management System will utilize LAN, web-enabled

services, or stand-alone systems. Communication within the system occurs via local
area network (LAN) for internal interactions and through web-enabled services for
external communication with users accessing the system remotely..

2.1.6 MEMORY CONSTRAINTS

RAM: At least 512 MB

Hard Disk Space: At least 500 MB

2.1.7 OPERATIONS

Attendance Tracking Management System:

- Data processing support.
- Backup and recovery of employee, customer, and train schedule details.

Leave Management:
- Data processing support.
- Backup and recovery of employee details, leave requests, and approval statuses.

User Data Management:

- Data processing support.
- Backup and recovery of user information.

Attendance Reporting:
- Data processing support.
- Backup and recovery of attendance data and report settings.

2.1.8 SITE ADAPTION REQUIREMENTS

The terminal at the client site will have to support the hardware and software
interfaces
specified in sections 2.1.3 and 2.1.4, respectively.

2.2 PRODUCT FUNCTIONS

1. Login Facility:
- Enable authorized access to the system for users with specific roles.

2. User Management:
- System administrator can add, modify, delete, or view details of users (e.g.,
administrators, teachers, students).

3. Attendance Management:
- System administrator/teachers can mark attendance for classes.
- Users can view attendance records for specific time frames, classes, or individuals.
- System generates notifications for attendance-related matters (e.g., absences,
tardiness).

4. Leave Management:
- Students can submit leave requests for anticipated absences.
- Administrators can review and approve/reject leave requests.

5. Report Generation:
- Users can generate detailed reports based on attendance data (e.g., attendance rates,
trends).

6. Notification System:
- Automatic notifications sent to students/parents regarding attendance status and
leave request approvals/rejections.

7. Role-based Access Control:

- Access to system modules based on user roles (e.g., administrator, teacher,
student).

2.3 USER CHARACTERISTICS

● Qualification: At least matriculation and comfortable with English.

● Experience: Should be well versed/informed about the processes of booking tickets
on the online portal.
● Technical experience: Elementary knowledge of computers.

2.4 CONSTRAINTS

1. Attendance Tracking Management System:

- The software does not maintain records of periodicals.
- There will be only one administrator.
- The delete operation is available to the administrator without any checks, so the
administrator must exercise caution before deletion and is responsible for data
consistency.
- Users are not allowed to update the primary key.

2. User Data Management:

- The software does not maintain records of periodicals.
- There will be only one administrator.
 - The delete operation is available to the administrator without any checks, so the
administrator must exercise caution before deletion and is responsible for data
consistency.
- Users are not allowed to update the primary key.

3. Attendance Notification System:

- The software does not maintain records of periodicals.
- There will be only one administrator.
- The delete operation is available to the administrator without any checks, so the
administrator must exercise caution before deletion and is responsible for data
consistency.
- Users are not allowed to update the primary key.

4. Attendance Trend Monitoring:

- The software does not maintain records of periodicals.
- There will be only one administrator.
- The delete operation is available to the administrator without any checks, so the
administrator must exercise caution before deletion and is responsible for data
consistency.
- Users are not allowed to update the primary key.

5. Leave Request Management:

- The software does not maintain records of periodicals.
- There will be only one administrator.
- The delete operation is available to the administrator without any checks, so the
administrator must exercise caution before deletion and is responsible for data
consistency.
- Users are not allowed to update the primary key.

2.5 ASSUMPTIONS AND DEPENDENCIES

● There will be only one admin.

● The login ID and password must be created by the Administrator and
communicated to the concerned user confidentially to avoid unauthorized access to
the system.

2.6 APPORTIONING OF REQUIREMENTS

NONE

3. SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACES

LOGIN PAGE
Select the user

Mark attendance
Maintain details

Add Teacher
Delete Teacher

Delete Student
3.2 FUNCTIONS

LOG IN

1. INTRODUCTION-Users log in to the system using their unique credentials

(username and password).

2.ACTORS- Administrator,Teacher, Student

3.PRE CONDITIONS-
a)The user must have valid credentials (username and password) to log in.
b)The system must be operational and accessible.
c)The user must have permission to access the system.
4. POST CONDITIONS-
a) Upon successful authentication, the user gains access to the system.
b) If authentication fails, the user is prompted to re-enter their credentials or
recover/reset their password.
5. BASIC FLOW-
a) The user navigates to the login page of the Attendance Tracking Management
System.
b) The system presents fields for the user to enter their username and password.
c) The user enters their username and password.
d) The system validates the provided credentials.
e) If the credentials are valid, the system grants access to the user and redirects them
to the system's dashboard.
f) If the credentials are invalid, the system displays an error message indicating the
failure of authentication.
6. ALTERNATE FLOW-
a)If the user forgets their password:
b)The user clicks on the "Forgot Password" link.
c)The system prompts the user to enter their email address.
d)The system sends a password reset link to the provided email address.
e)The user checks their email and follows the instructions in the password reset email
to create a new password.
7. SPECIAL REQUIREMENTS- None
VIEW ATTENDANCE RECORD

1.INTRODUCTION-Authorized users can view attendance records for specific

classes, students, or time periods. They can access both current and historical
attendance data..

2.ACTORS- Administrator,Teacher
3.PRE CONDITIONS-
a)The user must be logged in as an administrator or a teacher.
b)The attendance records must exist in the system.
4.POST CONDITIONS-
a)The user is able to view the attendance records as per their access level.
5.BASIC FLOW-
a) The user logs into the Attendance Tracking Management System.
b) The user navigates to the "View Attendance Records" section.
c) The system presents a list of options for viewing attendance records, such as by
date, by class, or by individual student.
d) The user selects the desired option.
e) The system retrieves the attendance records according to the selected option and
displays them to the user.
f) The user can further filter or sort the displayed records if necessary.
g) The user reviews the attendance records.

6.ALTERNATE FLOW-
a)If there are no attendance records available for the selected criteria, the system
displays a message indicating no records found.
7.SPECIAL REQUIREMENTS- None
MARK ATTENDANCE

1.INTRODUCTION-Teachers have the ability to mark attendance for their classes.

They can mark students as present, absent, or late using the system interface.
Additionally, teachers may have the option to mark attendance using biometric
scanners or RFID technology.
2.ACTORS- Administrator,Teacher
3.PRE CONDITIONS-
a) User must be authenticated and have appropriate access rights.
b) The system must be operational and accessible.

4.POST CONDITIONS-
a) The attendance of the user(s) marked is recorded accurately in the system.
b) Any notifications or alerts related to attendance (e.g., late arrivals, absences) are
triggered accordingly.
c) Data integrity is maintained, ensuring that the attendance records are updated in
the database.

5.BASIC FLOW-
a) The user accesses the attendance tracking management system.
b) The user selects the option to mark attendance.
c) The system presents a list of users or groups whose attendance needs to be
marked.
d) The user selects the user(s) or group(s) for whom attendance needs to be marked.
e) The system prompts the user to confirm the attendance marking.
f) The user confirms the attendance marking.
g) The system records the attendance of the selected user(s) or group(s) and updates
the database.
h) Any relevant notifications or alerts are triggered based on the attendance marked

6.ALTERNATE FLOW-
a)If the user attempts to mark attendance for a user/group not present in the system,
the system notifies the user and prompts them to recheck the selection.
7.SPECIAL REQUIREMENTS- None
MAINTAIN ATTENDANCE RECORD

INTRODUCTION- This use case focuses on managing user data within the
Attendance Tracking Management System. Administrators can add, delete, update,
and view user information.
ACTORS- Administrator
PRE CONDITIONS-

The administrator must be logged into the system with the necessary permissions.

The system must be operational and accessible.

POST CONDITIONS-

User data is maintained accurately within the system.

BASIC FLOW-

1.The administrator navigates to the user management section.

The system presents options for managing users, such as "Add User," "Delete User,"
"Update User," and "View User."

The administrator selects the desired option.

1.Add User: The administrator enters the required user information (e.g., name,
username, password, role) and submits it. The system validates the information and
creates a new user account.

2.Delete User: The administrator selects the user to be deleted and confirms the
deletion. The system deletes the user account and associated attendance records
(based on system configuration).

3.Update User: The administrator selects the user to be updated, makes the necessary
changes to the user information, and submits the updates. The system validates the
information and updates the user record.

4.View User: The administrator selects the user to view their details, including
attendance history (based on system configuration).
ALTERNATE FLOW-

1.If the administrator attempts to add a user with an existing username, the system
should notify them of the conflict.

2.If the administrator attempts to delete a user without confirmation, the system might
prompt for confirmation to prevent accidental deletion.

3.If the user information being updated is invalid, the system should notify the
administrator and prevent the update.
SPECIAL REQUIREMENTS- None
GENERATE REPORTS

1.INTRODUCTION- It allows authorized users to create detailed reports based on

attendance data for specific time frames, departments, or individuals.

2.ACTORS- Administrator
3.PRE CONDITIONS-
a)The user must be authenticated and have appropriate permissions to access the
report generation functionality.
b)Attendance data must be available and up-to-date in the system.
4.POST CONDITIONS-
A comprehensive attendance report is generated based on the specified parameters
and made available to the user for viewing, downloading, or further processing.
5.BASIC FLOW-
a)The user navigates to the report generation section within the Attendance Tracking
Management System.
b)The user selects the parameters for the report, such as the time frame,
department(s), employee(s), or specific criteria.
c)The system validates the selected parameters and ensures that the necessary data is
available.
d)The system generates the report based on the specified parameters.
e)The generated report is presented to the user through the system interface.
f)The user can choose to view the report online, download it in a preferred format
(e.g., PDF, CSV), or perform further actions such as sharing or printing.
6.ALTERNATE FLOW-
a)If the selected parameters do not match any available data or if there are errors in
the input, the system displays an error message and prompts the user to correct the
selection.
7.SPECIAL REQUIREMENTS- None
NOTIFY PARENTS and STUDENTS

1.INTRODUCTION- The system can automatically send notifications to students

and their parents/guardians regarding attendance-related matters such as absences,
tardiness, or low attendance rates. Notifications can be sent via email, SMS, or
through a dedicated mobile application.
2.ACTORS-System
3.PRE CONDITIONS-
a)The Attendance Tracking Management System is operational.
b)Attendance data for students is recorded and stored in the system.
c)Contact information for parents and students is accurately registered in the system.
4.POST CONDITIONS-
Parents and students receive notifications regarding their attendance status.
5.BASIC FLOW-
a)The Attendance Administrator logs into the system.
b)The Administrator selects the option to send attendance notifications.
c)The system retrieves attendance data for the specified time frame.
d)For each student with unexcused absences or tardiness, the system retrieves the
contact information of the respective parent(s).
e)The system generates automated notifications containing attendance status for each
student.
f)Notifications are sent via email, SMS, or other registered communication channels
to the parents and students.
g)The system records the notification delivery status.

6.ALTERNATE FLOW-
a)If the system encounters an error while retrieving attendance data, the Administrator
is notified, and the process is halted until the issue is resolved.
7.SPECIAL REQUIREMENTS- None
MONITOR ATTENDANCE TRENDS

1.INTRODUCTION- Administrators can use the system to monitor attendance

trends over time. This includes tracking overall attendance rates, identifying classes or
students with recurring attendance issues, and implementing interventions as
necessary.
2.ACTORS-System
3.PRE CONDITIONS-
a)The Attendance Tracking Management System is operational and accessible.
b)Users have appropriate permissions to access attendance data.
c)Sufficient historical attendance data is available for analysis.
4.POST CONDITIONS-
a)Attendance trends are analyzed and presented to the user
5.BASIC FLOW-
Data Selection:
User specifies the parameters for the attendance trend analysis, such as date range,
employee groups, or specific departments.
Data Retrieval:
The system retrieves relevant attendance data based on the user's selection criteria
from the database.
Analysis:
The system processes the retrieved data to identify patterns, trends, and anomalies in
attendance.
Presentation:
The system generates graphical representations or reports summarizing the attendance
trends.
The user reviews the presented data to gain insights into attendance patterns.
Action:
Based on the insights gained, the user may take necessary actions such as adjusting
schedules, addressing attendance issues, or recognizing exemplary attendance.

6.ALTERNATE FLOW-
a)If the system encounters errors while retrieving or analyzing the data, it prompts the
user with appropriate error messages and offers options to retry or modify the input
parameters.
7.SPECIAL REQUIREMENTS- None
MANAGE LEAVE REQUESTS

1.INTRODUCTION- Students can submit leave requests through the system for
anticipated absences due to reasons such as illness, personal emergencies, or official
events. Teachers and administrators can review and approve/reject these requests
accordingly.
2.ACTORS-Students
3.PRE CONDITIONS-
a)User must be authenticated and have appropriate permissions to manage leave
requests.
b)The system must be operational and accessible.
4.POST CONDITIONS-
a)The leave request status is updated (approved or denied).
b)Notifications are sent to relevant parties regarding the status of the leave request.
5.BASIC FLOW-
a)The authorized user accesses the system and navigates to the leave management
section.
b)The user selects the option to manage leave requests.
c)The system presents a list of pending leave requests.
d)The user selects a specific leave request to review.
e)The user reviews the details of the leave request including dates, reason, and any
attached documentation.
f)The user decides whether to approve or deny the leave request.
g)If approved, the system updates the leave request status accordingly and sends a
notification to the employee.
h)If denied, the system updates the leave request status accordingly and sends a
notification to the employee with the reason for denial.
i)The user may choose to add comments or notes regarding the decision.
j)The system logs the action taken by the user for auditing purposes.

6.ALTERNATE FLOW-
a)If the user does not have appropriate permissions to manage leave requests, the
system displays an error message and the use case terminates.
b)If additional information is required for decision-making, the user requests
clarification from the employee who submitted the leave request.
c)If approved, but conflicts arise with other scheduled events or staffing, the system
prompts the user to resolve conflicts before finalizing the approval.
d)If denied, but the employee insists on leave, the user may escalate the request to a
higher authority for further review.
7.SPECIAL REQUIREMENTS- None
3.3 PERFORMANCE REQUIREMENTS

● Should run on a 500 MHz, 512 MB RAM machine.

● Responses should be within 2 seconds.

3.4 LOGICAL DATABASE REQUIREMENTS

NONE

3.5 DESIGN CONSTRAINTS

● Usability : The application will be user-friendly and easy to operate and the
functions
will be easily understandable.
● Reliability : The applications will be available to the students throughout the
registration period and have a high degree of fault tolerance.
● Security : The application will be password protected. Users will have to enter the
correct login ID and password to access the application.● Maintainability : The
application will be designed in a maintainable manner. It will be
easy to incorporate new requirements in the individual modules.
● Portability : The application will be easily portable on any windows-based system
that
has SQL Server installed.

3.5.1 STANDARD COMPLIANCE

The system should comply with relevant industry standards for data security, privacy,
and accessibility. It should also adhere to programming best practices and follow a
modular, scalable architecture.

3.6 SOFTWARE SYSTEM REQUIREMENTS

3.6.1 RELIABILITY
The system should be highly reliable, ensuring minimal downtime and accurate attendance tracking
under various conditions. It should handle errors gracefully and provide mechanisms for data integrity
and recovery.

3.6.2 AVAILABILITY

The system should be available 24/7 to accommodate users across different time
zones. It should have redundant components and failover mechanisms to ensure
uninterrupted service.

3.6.3 SECURITY

The system should prioritize data security and access control. It should implement
encryption for sensitive data transmission and storage. Role-based access control
mechanisms should be in place to ensure that users only have access to the features
and data relevant to their roles. Additionally, the system should regularly undergo
security assessments and audits to identify and mitigate potential vulnerabilities.

3.6.4 MAINTIANABILITY

The system should be designed with maintainability in mind, allowing for easy
updates, enhancements, and bug fixes. Modular code architecture and documentation
should be provided to facilitate understanding and modification by developers.
Version control should be utilized to track changes and manage codebase evolution
effectively.

3.6.5 PORTABILITY

The system should be designed to be portable across different environments and

platforms. It should be compatible with various operating systems and web browsers
to ensure accessibility for all users. Additionally, mobile responsiveness and
compatibility should be ensured to enable access from smartphones and tablets.

3.7 ORGANIZING THE SPECIFIC REQUIREMENTS

3.7.1 SYSTEM MODE

The system operates in an online mode, allowing users to access it via web browsers
or dedicated applications.

3.7.2 USER CLASS

- Administrator: Manages system settings, user accounts, and overall system

functionality.
- Teacher: Marks attendance, manages class-related tasks, and views attendance
reports.
- Student: Submits leave requests and views personal attendance records.

3.7.3 OBJECTS

- User accounts: Store information about administrators, teachers, and students,

including credentials and permissions.
- Attendance records: Store data about student attendance, including dates, class
periods, and attendance status.
- Leave requests: Store information about leave requests submitted by students,
including dates, reasons, and status.

3.7.4 FEATURE

- Authentication: Users must log in with valid credentials to access the system.
- Attendance marking: Teachers mark attendance for classes, with options for present,
absent, or late statuses.
- Leave request management: Students submit leave requests, which administrators or
teachers review and approve/reject.
- Report generation: Administrators can generate attendance reports based on
specified parameters.

3.7.5 STIMULUS

- User interaction: Users interact with the system through graphical user interfaces,
inputting data and receiving feedback.
- System events: System events include user logins, attendance marking, leave request
submissions, and report generation.

3.7.6 RESPONSE

- System response: The system processes user requests, validates input data, updates
database records, and generates notifications.

3.7.7 FUNCTIONAL HIERARCHY

- The system hierarchy includes authentication, attendance tracking, leave request

management, report generation, and notification handling modules.

3.8 ADDITIONAL COMMENTS

- The system efficiently tracks attendance, promoting transparency.

- Users must be authenticated for data security.
- System availability is crucial for uninterrupted tracking.
- Permissions ensure only authorized access.
- Accurate records aid decision-making.
- Structured flow enhances user experience.
- Error handling ensures system resilience.
- Strong password policies enhance security.

4. SUPPORTING INFORMATION
USE CASE DIAGRAM
CLASS DIAGRAM
 SEQUENCE DIAGRAM

LOG IN- BASIC FLOW

LOG IN- ALTERNATE FLOW
MARK ATTENDANCE-BASIC FLOW
MARK ATTENDANCE- ALTERNATE FLOW
VIEW ATTENDANCE RECORD- BASIC FLOW
VIEW ATTENDANCE RECORD- ALTERNATE FLOW
GENERATE REPORT- BASIC FLOW
 ACTIVITY DIAGRAM
View attendance
Mark attendance
 STATECHART DIAGRAM
For LOGIN-
MARK ATTENDANCE-
 DERIVING TEST CASES FROM USE CASE

Login
Scenario Name &
Test Case ID Description Username Password Expected Outcome Pass/Fail
Basic Flow: Login
with valid
TC1 credentials Valid input Valid input Redirected to User Dashboard Pass
Alternate Flow:
Login with invalid Invalid
TC2 username input Valid input Error message: "Invalid Username" Pass
Alternate Flow:
Login with invalid Invalid
TC3 password Valid input input Error message: "Invalid Password" Pass
Alternate Flow:
Login with empty Empty Error message: "Username cannot be
TC4 username input Valid input empty" Pass
Alternate Flow:
Login with empty Error message: "Password cannot be
TC5 password Valid input Empty input empty" Pass
Alternate Flow: Incorrect
Login attempt input(multip
TC6 exceeding limit Valid input le attempts) Account locked message Pass
Alternate Flow: Newly
Login after created
TC7 password reset Valid input input Redirected to User Dashboard Pass
Alternate Flow: Valid
Login with case- input(incorr Error message: "Invalid Username
TC8 sensitive mismatch ect case) Valid input or Password" Pass
 View attendance Record
Scenario Name & Selection
Test Case ID Description User Role Criteria Expected Outcome Pass/Fail
Basic Flow: View User sees a list of
attendance by Admin/ Select a attendance records for
TC1 class Teacher class the selected class. Pass
Basic Flow: View User sees a list of
attendance by Admin/ Select a attendance records for
TC2 date range Teacher date range the chosen date range. Pass
Basic Flow: View Search by User sees the
attendance by Admin/ student attendance history for
TC3 student Teacher name/ID the specific student. Pass
Select a
Alternate Flow: No class with System displays "No
records found Admin/ no records found"
TC4 (class) Teacher attendance message. Pass
Select a
Alternate Flow: No date range System displays "No
records found Admin/ with no records found"
TC5 (date range) Teacher attendance message. Pass
Search for
Alternate Flow: No a student System displays "No
records found Admin/ with no records found"
TC6 (student) Teacher attendance message. Pass
Alternate Flow:
Insufficient access Attempt to System displays an error
(Teacher - all view all message indicating
TC7 classes) Teacher classes insufficient access. Pass
Attempt to
Alternate Flow: view
Insufficient access another System displays an error
(Teacher - other teacher's message indicating
TC8 teacher's class) Teacher class insufficient access. Pass
 Mark Attendance
Test Case Scenario Name Pre Expected
ID & Description Actor Conditions Steps Outcome Pass/Fail Remarks
1. Access
attendance
marking Attendance
option. 2. marked as
Select a "Present" for
class the selected
teacher is students.
assigned System may
to. 3. display
User Select success
logged in students message and
(Teacher of who are trigger
Basic Flow: a class), present. 4. notifications
Mark Attendance Confirm (e.g., late
attendance - system attendance arrival
TC1 Present Teacher operational marking. notifications). Pass -
1. Access
attendance
marking
option. 2.
Select a
class the
teacher is
assigned Attendance
to. 3. marked as
User Select "Absent" for
logged in students selected
(Teacher of who are students.
Basic Flow: a class), absent. 4. System may
Mark Attendance Confirm trigger
attendance - system attendance notifications
TC2 Absent Teacher operational marking. for absences. Pass -
1. Access
attendance
marking
option. 2.
Select a
class the
teacher is
assigned Attendance
to. 3. marked as
User Select "Late" for
logged in students selected
(Teacher of who are students.
Basic Flow: a class), late. 4. System may
Mark Attendance Confirm display late
attendance - system attendance arrival
TC3 Late Teacher operational marking. notifications. Pass -
1. Access
User attendance
logged in marking System
Alternate Flow: (Teacher of option. 2. displays an
Mark a class), Select a error message
attendance for Attendance class. 3. indicating
non-existent system Enter a "User not
TC4 user Teacher operational name or ID found". Pass -
 that does
not
correspond
to a
student.
1. Access
attendance
marking
option. 2.
Select a
class. 3.
Select
students. 4.
User Choose to Attendance
logged in cancel marking is not
(Teacher of attendance recorded.
Alternate Flow: a class), marking System may
User cancels Attendance before display a
attendance system confirmati confirmation
TC5 marking Teacher operational on. message. Pass -
1. Access
attendance
marking
option
User (with
logged in biometric
(Teacher of option). 2. Attendance is
a class), Select a marked based
Additional Attendance class. 3. on successful
Flow: Mark system Use the biometric
attendance operational, biometric scans. System
using Biometric Biometric scanner to may display Functionality depends
Scanner (if scanner authenticat success on specific hardware
TC6 supported) Teacher connected e students. message. Pass/Fail integration.
1. Access
attendance
marking
User option
logged in (with RFID
(Teacher of option). 2.
a class), Select a Attendance is
Attendance class. 3. marked based
Additional system Students on valid RFID
Flow: Mark operational, use their scans. System
attendance RFID RFID tags may display Functionality depends
using RFID (if reader for success on specific hardware
TC7 supported) Teacher connected attendance. message. Pass/Fail integration.
System
displays an
error message
indicating
unavailability
User or asks to try
logged in 1. Access again later.
Error Handling: (Teacher of attendance Attendance
System a class), marking data is not
unavailable Attendance option. 2. lost (may be
during system has Attempt to buffered for
attendance connectivit mark later Simulates system
TC8 marking Teacher y issues attendance. submission). Pass downtime scenario.
 Actual test case

Scenario Name &

Test Case ID Description Username Password Expected Outcome Pass/Fail
Basic Flow:
Login with valid
TC1 credentials Abc123d55 Valid input Redirected to User Dashboard Pass
Alternate Flow:
Login with invalid
TC2 username a12b Valid input Error message: "Invalid Username" Pass
Alternate Flow:
Login with invalid Invalid
TC3 password Abc123d543 input Error message: "Invalid Password" Pass
Alternate Flow:
Login with empty Error message: "Username cannot be
TC4 username * Valid input empty" Pass
Alternate Flow:
Login with empty Empty Error message: "Password cannot be
TC5 password Shrr4589 input empty" Pass
Incorrect
Alternate Flow: input
Login attempt (multiple
TC6 exceeding limit Shi45r89 attempts) Account locked message Pass
Alternate Flow: Newly
Login after created
TC7 password reset Uumh5892 input Redirected to User Dashboard Pass
Alternate Flow:
Login with case- Error message: "Invalid Username
TC8 sensitive mismatch AB804tuE Valid input or Password" Pass