Scribd
Upload
29 views6 pages

SE (Lab # 01) 1

Uploaded by

Usman Faizyab Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
29 views6 pages

SE (Lab # 01) 1

Uploaded by

Usman Faizyab Khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

SOFTWARE REQUIREMENT

SPECIFICATION (SRS)

EduTrack

Version 1.0

October 17, 2024


Chapter 1

Introduction

This document provides a detailed specification of the software requirements


for the EduTrack system, a student management system. The purpose of
this section is to provide an overview, define the document’s purpose, and
outline the scope and intended audience for the EduTrack system.

1.1 Document Purpose


The purpose of this Software Requirements Specification (SRS) document is
to outline the functional and non-functional requirements of the EduTrack
system. This document serves as a guide for the development team to under-
stand the features and capabilities of the system. It covers all aspects of the
system, from user roles and interactions to system performance and security.
This SRS focuses on the initial version of EduTrack, which will be used by a
single department at the university.

1.2 Product Scope


EduTrack is a mobile-based student management system designed to stream-
line academic administration within a single department at a university. Its
primary functions include real-time attendance tracking, class schedule man-
agement, and quiz notifications, along with features for generating atten-
dance reports. The system allows teachers and class advisors to easily man-
age and communicate with students, reducing the manual effort involved in
day-to-day academic tasks.
The main benefits of EduTrack include increased efficiency in managing
attendance, improved communication between teachers and students, and

1
timely updates on class schedules and quizzes. By automating these pro-
cesses, the system helps reduce human error and ensures students stay in-
formed. EduTrack’s goal is to make academic management simpler, more
accurate, and more organized, benefiting both students and faculty.

1.3 Intended Audience and Document Overview


The EduTrack Software Requirements Specification (SRS) is intended for
several key audiences, each with distinct needs and interests regarding the
system. These include:

• Project Managers: They will use the SRS to understand the overall
scope and objectives of the EduTrack system, including its require-
ments and deliverables. This helps in planning, scheduling, and re-
source allocation.

• Developers: The SRS provides detailed functional and non-functional


requirements necessary for the design and implementation of the sys-
tem. Developers will use this information to ensure that the software
meets the specified criteria and functions correctly.

• Clients (Department Administrators and Professors): For the


university department, the SRS outlines the system’s capabilities and
features, providing an understanding of how EduTrack will address
their needs and improve academic management.

2
Chapter 2

Overall Description

2.1 Product Perspective


The EduTrack system is a new, standalone mobile app created for a university
department. It is not an update or replacement for any existing system but a
fresh solution designed to improve academic administration. The app helps
manage attendance, class schedules, and quiz notifications, tasks that are
usually done manually or using various separate systems.
Below is a general diagram illustrating the major components of the Edu-
Track system, its interactions with the environment, and its context of use:

Figure 2.1: Context Diagram of EduTrack

3
2.2 Functional Requirements
The EduTrack system offers a range of features designed to streamline aca-
demic administration and enhance communication. The major functions of
the system include:

• Attendance Tracking: Teachers can take attendance in real-time,


with records automatically stored and updated.

• Class Schedule Management: Class advisors can manage and up-


date class schedules, including adding compensatory classes. Students
are notified of schedule changes automatically.

• Quiz Information Management: Teachers can enter quiz details,


including dates, topics, and marks, which students can access to view
and keep track of their quiz information.

• Marks Management: Teachers input quiz marks into the system,


and students can view their results.

• Report Generation: Attendance reports are automatically generated


for class advisors for administrative purposes.

• Student Notifications: Students receive real-time notifications about


quizzes, attendance, and schedule changes.

• User Authentication and Role Management: Secure login for


students, teachers, and class advisors, with role-based access to system
functions.

2.3 Non Functional Requirements


The non-functional requirements for the EduTrack system outline the ex-
pected performance, usability, and other quality aspects that will ensure the
system operates efficiently and meets user expectations. course project.

• Performance:

– The system should handle up to 100 users simultaneously.


– Responses for most operations, such as attendance updates, should
take less than 2 seconds.

4
• Usability:

– The mobile app should have a simple, user-friendly interface.


– Users should easily access key features (attendance, schedule, quizzes)
within 3 taps.

• Reliability:

– The system should be available at least 95% of the time during


university hours.
– Backup mechanisms should ensure minimal data loss in case of
failure.

• Security:

– Basic encryption should protect student and teacher data.


– Only authorized users can access or modify specific data, such as
attendance and quizzes.

• Scalability:

– The system should support adding new departments or users with-


out major changes.

• Maintainability:

– The system should be easy to update, with clear documentation


for future improvements.

• Portability:

– The mobile app should work on both Android and iOS devices.

You might also like