Scribd
Upload
17 views7 pages

1.1 Purpose

This document outlines the Software Requirements Specification (SRS) for the Student Information System (SIS), designed to manage student data including enrollment, course registration, and grades management. The SIS will provide functionalities such as student registration, course enrollment, attendance tracking, and reporting, while excluding financial transactions and external system integrations. The system will be web-based, user-friendly, and must meet various performance, security, and usability requirements.

Uploaded by

Balaji Sri Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views7 pages

1.1 Purpose

This document outlines the Software Requirements Specification (SRS) for the Student Information System (SIS), designed to manage student data including enrollment, course registration, and grades management. The SIS will provide functionalities such as student registration, course enrollment, attendance tracking, and reporting, while excluding financial transactions and external system integrations. The system will be web-based, user-friendly, and must meet various performance, security, and usability requirements.

Uploaded by

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

EX.

NO:2 – DOCUMENTARY SOFTWARE REQUIREMENTS


SPECIFICATION (SRS) FOR IDENTIFIED SYSTEM-
GT . ASHOKBHARATHI - 8763
1. Introduction

1. INTRODUCTION
1.1 PURPOSE

 This document outlines the software requirements for the Student


Information System (SIS). The purpose of the SIS is to manage
various aspects of student data including enrollment, course
registration, grade management, and reporting for students and staff
members. This system will improve the efficiency of managing
student information and enhance the overall academic process.

1.2 SCOPE

 The SIS will handle functionalities such as:


o Student Registration and Management: Creating, updating,
and viewing student records.
o Course Enrollment: Students can register for courses, and
faculty can manage the enrollment.
o Grades Management: Faculty can enter and update grades,
and students can view their grades.
o Timetable Management: Admins can configure and manage
the academic timetable.
o Attendance Tracking: Teachers and administrators can
monitor student attendance.
o Reports: Admins can generate various reports, such as student
performance, course registrations, and attendance statistics.
 Exclusions:
o The system will not handle financial transactions such as
tuition payments or student fees.
o Integration with external systems (e.g., learning management
systems, e-learning platforms) is out of scope for the initial
version.

1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

 SIS: Student Information System


 Admin: Administrator responsible for managing the system and users
 Student: An individual who is enrolled in courses at the institution
 Faculty: Teaching staff who can manage courses, grades, and
attendance
 Registrar: Administrative staff responsible for managing course
registrations and student records

1.4 REFERENCES

 "Student Information Systems and their Management," Journal of


Educational Technology, 2021.
 ISO/IEC 9126 – Software Engineering — Product Quality.
 University Data Standards – Institutional Requirements Document.

2. OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

 The SIS will be a web-based application accessible by students,


faculty, and administrative staff. The system will consist of a user-
friendly interface for students and faculty, and a robust backend for
administrators. It will interact with the institution's database to store
and manage student records, course registrations, grades, and other
essential data.

2.2 PRODUCT FUNCTIONS

 Student Registration and Profile Management: Students can


register themselves, update personal information, and view academic
records.
 Course Registration: Students can search for courses and enroll in
them, while faculty can manage course details and student
registrations.
 Grade Management: Faculty can input grades and academic
performance details, and students can view their grades.
 Timetable Management: Administrators can create and manage
course schedules and assign them to classrooms and instructors.
 Attendance Tracking: Faculty can track student attendance, marking
absences and making attendance reports available for students and
admins.
 Reports: Admins can generate reports related to student performance,
course enrollments, attendance statistics, etc.

2.3 USER CHARACTERISTICS

 Students: Students will need basic computer skills to interact with


the system (e.g., logging in, viewing grades, enrolling in courses).
 Faculty/Professors: Faculty members will need to be able to input
grades, track attendance, and manage courses effectively. They
should be familiar with academic processes and data entry.
 Admins/Registrars: Admins will require a more advanced
understanding of the system to manage user accounts, configure
courses, and generate reports.
2.4 CONSTRAINTS

 The system must be compatible with modern browsers (Chrome,


Firefox, Safari) and operate in the institution’s IT environment.
 The application must integrate with existing database systems used by
the institution (e.g., student records database).
 There may be restrictions on the number of concurrent users the
system must support, based on institution needs.

3. SPECIFIC REQUIREMENTS

3.1 FUNCTIONAL REQUIREMENTS

1. User Registration and Profile Management


o The system must allow students to create, update, and view
their profiles (e.g., name, email, courses, grades).
o Students must be able to view their enrolled courses and
academic progress.
o Admins should have the ability to update or delete student
profiles.

2. Course Enrollment and Management


o Students should be able to search for and register for available
courses based on prerequisites, schedules, and availability.
o Faculty and admins should be able to create and manage
course offerings, including assigning faculty, setting schedules,
and capping enrollments.

3. Grade Management
o Faculty must be able to input, update, and view grades for their
courses.
o Students should be able to access their grades for each course
they are enrolled in.
o Admins must be able to generate and export reports based on
student grades.

4. Attendance Management
o Faculty should be able to mark attendance for each class
session.
o The system should track student absences and generate reports
based on attendance records.

5. Timetable Management
o Admins must be able to create and manage the academic
timetable, assigning faculty and classrooms to courses.
o Students should be able to view their timetable and check
course schedules.

6. Reporting and Analytics


o Admins should be able to generate various reports, such as
student performance, course enrollment statistics, and
attendance.
o Reports should be exportable in formats like PDF, CSV, and
Excel.

3.2 NON-FUNCTIONAL REQUIREMENTS

1. Performance
o The system should be capable of handling up to 10,000
concurrent users without performance degradation.
o System responses (e.g., page load, searching) should be
completed in under 3 seconds.

2. Security
o All sensitive data (e.g., student personal information, grades)
should be encrypted in transit and at rest.
o User authentication must include secure login mechanisms,
including password management and, if necessary, two-factor
authentication.
o Admins must have role-based access control to ensure that
only authorized users can modify sensitive data.

3. Usability
o The system interface must be user-friendly and accessible to
both students and faculty with minimal training.
o Mobile compatibility is required for students to access course
materials, grades, and timetables on the go.

4. Scalability
o The system must be scalable to accommodate growing
numbers of students and courses as the institution expands.
o The system should be modular so that additional features (e.g.,
financial management, advanced analytics) can be added later.

5. Availability
o The system must be available 24/7 with 99.9% uptime,
excluding scheduled maintenance.

6. Backup and Recovery


o The system must have automatic backup procedures in place to
protect student data.
o The system should support disaster recovery mechanisms in
case of a data breach or system failure.

3.3 INTERFACE REQUIREMENTS

1. User Interface
o The system will have a web-based interface with a dashboard
for students, faculty, and admins.
o Students will have access to their grades, course schedule, and
personal information.
o Faculty will have access to their courses, student records, and
grade management tools.

2. System Interfaces
o The SIS must integrate with the institution’s existing database
for student and course information.
o The system should integrate with email systems for
notifications about course schedules, grades, and attendance.

3. External Interfaces
o The SIS should be able to interface with external systems (if
applicable), such as the Learning Management System (LMS)
or external assessment platforms.

You might also like