Software Requirements

Specification

Project: 20231CSE0142

Author: vineeth soudri

[email protected]

Company: presidency university

Publication date: 2024-09-27

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Product perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.1 System interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.2 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.3 Hardware interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3.4 Software interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.5 Communications interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.6 Memory constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.7 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.8 Site adaptation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.9 Interfaces with services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Product functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 User characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.6 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.7 Assumptions and dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.8 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.9 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 External interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Usability requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4 Performance requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.5 Logical database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.6 Design constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.7 Standards compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.8 Software system attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4 Supporting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1 Introduction
[SRS-1] The College Management System (CMS) is a software solution designed to automate college administrative tasks
like student enrollment, course management, attendance tracking, and performance evaluation. This Software Requirements
Specification (SRS) document provides a detailed overview of the system’s objectives, functionalities, and requirements to
ensure efficient and secure management of college operations. The CMS will offer role-based access for administrators,
faculty, and students while integrating seamlessly with existing systems such as the library management system.

Type: Section

1.1 Purpose
[SRS-2] The purpose of this Software Requirements Specification (SRS) document is to provide a comprehensive overview
of the College Management System (CMS). This document outlines the system’s functionalities, intended users, and
interfaces, aiming to streamline college operations such as student registration, course management, attendance tracking, and
grading.

Type: Section

1.2 Scope
[SRS-3] The CMS is designed to manage various administrative operations of the college, including:

1.Student Management

2.Faculty Management

3.Course Registration

4.Attendance Tracking

5.Grading

The system will be accessible via a web interface for administrators, faculty, and students, providing role-based access.

Type: Section

1.3 Product perspective

[SRS-4] The CMS will function as a standalone web application integrated with the existing Student Database and Library
Management System, ensuring seamless access to critical information.

Type: Section

1.3.1 System interfaces

[SRS-5] 1.Interaction with the Student Database to retrieve and update student records.

2.Integration with the Library Management System for tracking student book loans.

Type: Section

1.3.2 User interfaces

[SRS-6] 1 .Login Page

2.Dashboard for summaries and key information

3.Student Management Page for managing student records

Type: Section

Software Requirements Specification 1

[SRS-7] Server specifications:

1. Intel i5 or above
2. 8GB RAM
3. 512GB disk space

Type: Section

1.3.4 Software interfaces

[SRS-8] Operating Systems: Linux(ubuntu or Arch) or Windows version 8 or above

1.Database: MySQL 8.0 or PostgreSQL 12.0

Type: Section

1.3.5 Communications interfaces

[SRS-9] Communication will be via REST APIs over HTTP/HTTPS for data retrieval and updates.

Type: Section

1.3.6 Memory constraints

[SRS-10] The system should maintain memory usage below 4GB during peak hours.

Type: Section

1.3.7 Operations

[SRS-11] Daily backups and recovery processes will be implemented to ensure data integrity.

Type: Section

1.3.8 Site adaptation requirements

[SRS-12] Configurable settings for multiple campuses with distinct databases.

Type: Section

1.3.9 Interfaces with services

[SRS-13] Integration with the college's email service for notifications and alerts.

Type: Section

1.4 Product functions

[SRS-14] The system will provide functionalities such as:

1.User Management

2.Student Management

3.Course Management

4.Attendance Tracking

5.Grading

Software Requirements Specification 2

1.5 User characteristics
[SRS-15]

1. Administrator: Full access to system functionalities.

2. Faculty: Manage courses and student grades.
3. 2.Student: Access to grades, attendance, and schedules.

Type: Section

1.6 Limitations
[SRS-16]

1. The initial version will not support integration with third-party learning management systems.

Type: Section

1.7 Assumptions and dependencies

[SRS-17]

1. Users must have a valid college email address.

2. The system relies on an active internet connection for data access.

Type: Section

1.8 Definitions
[SRS-18]

CMS: College Management System

Student ID: Unique identifier for each student

Type: Section

1.9 Acronyms and abbreviations

[SRS-19] GUI: Graphical User Interface

DBMS: Database Management System

URL: Uniform Resource Locator (web address)

HTML: HyperText Markup Language

Type: Section

2 Requirements
Type: Section

2.1 External interfaces

[SRS-21] The CMS will connect to external systems such as the Student Database and Library Management System.

Type: Section

2.2 Functions

Software Requirements Specification 3

 1. FR-1: The system shall allow users to log in using their email and password.
2. FR-2: The system shall allow administrators to add or remove students.
3. FR-3: The system shall enable faculty to update student attendance records.

Type: Section

2.3 Usability requirements

[SRS-23] The system should provide an intuitive interface with easy navigation and consistent layout across all pages.

Type: Section

2.4 Performance requirements

[SRS-24] The system should support up to 500 concurrent users with a response time of under 2 seconds for most operations.

Type: Section

2.5 Logical database requirements

[SRS-25] The CMS will use a relational database structured with tables for Students, Courses, Faculty, and Attendance, each
with unique keys.

Type: Section

2.6 Design constraints

[SRS-26] The system will adhere to a three-tier architecture, separating the user interface, business logic, and database layers.

Type: Section

2.7 Standards compliance

[SRS-27] The system will comply with the IEEE 830 standard for Software Requirements Specification.

Type: Section

2.8 Software system attributes

[SRS-28]

1. Reliability: The system will maintain 99.9% uptime.

2. Security: User data will be encrypted using AES-256.
3. Maintainability: The code will follow industry-standard conventions for ease of maintenance.

Type: Section

3 Verification
[SRS-29] Verification will include automated tests to confirm functional requirements and manual tests for usability and
performance.

Type: Section

4 Supporting information
[SRS-30] Include diagrams such as use case diagrams and flowcharts that detail system interactions.

Type: Section

Software Requirements Specification 4

[SRS-31]

1. IEEE 830 standard for Software Requirements Specification.

2. Documentation on RESTful APIs.

Type: Section

Software Requirements Specification 5