Scribd
Upload
114 views7 pages

SRS On Student Management

This document outlines requirements for a student management system. It describes the purpose of managing student data and fee details online. The system will have administrator and user modules. The administrator can view, edit, and manage student data and generate reports. Users can view personal details and fee information. Non-functional requirements include the system needing to perform all specified functions, securely store encrypted passwords in the database, and be maintainable and portable across platforms.

Uploaded by

Harpreet Singh Bagga
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
114 views7 pages

SRS On Student Management

This document outlines requirements for a student management system. It describes the purpose of managing student data and fee details online. The system will have administrator and user modules. The administrator can view, edit, and manage student data and generate reports. Users can view personal details and fee information. Non-functional requirements include the system needing to perform all specified functions, securely store encrypted passwords in the database, and be maintainable and portable across platforms.

Uploaded by

Harpreet Singh Bagga
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

SOFTWARE ENGINEERING File BACHELOR OF

TECHNOLOGY (Computer Science Engineering)

SUBMITTED BY:- SUBMITTED TO:-

Harpreet Singh Dr. Rini Saxena


1915169 ABC

INTRODUCTION

1 CSE 5TH CD
1.1 Purpose

Our product is a student management system that gives all the services that must be
provided to a student over the internet to find fee details provided by that
administrator of the college.

This product contains each and every data regarding student, payment etc., personal
details which can be updated by the student and viewed by the administrator. It
provides detailed information about the fee details and the location (place) of college.
Our product is a subpart of the university management system.

1.2 Project Scope

Our Student Management System product usage makes work done at the faster way
the software is applicable to view the fee details provided by the administrator of the
organization and student can edit his personal details which can be viewed by the
administrator.

1.3 References

https://krazytech.com/projects/sample-software-requirements-specificationsrs-report-airline-
database

https://1000projects.org/software-requirements-specification-student-management-
system.html
https://www.academia.edu/36903518/SOFTWARE_REQUIREMENTS_SPECIFICATION_S
RS_FOR_Student_and_Unit_Management_System_SUMS_Registration_Module

2. OVERALL DESCRIPTION
2.1 Product Perspective

Student Management System is capable of managing each and every data regarding
student, payments etc. Student Management System helps us in managing in an
extremely efficient way. This Student Management System works in an efficient
manner.

We have two modules in this project. One is the admin and the other is the user.
Admin can maintain the fee details of students and can generate the reports and

2 CSE 5TH CD
export the details to excel. User module can edit their personal details and can view
the fee details.

2.2 Product Features

● Reduces the manual workload.


● Complete details of the student can be stored and retrieved.
● Admin can see all the student’s payment details and also export to
excel sheets.
● The student can view all his details, payment details and the location of
the college.

2.3 Product Functions :

There are two different users who will be using this product: Administrator
who can view and edit the details of any students. Students who can view
their details as well as they can edit their details. The features that are
available to the Administrator are: An Administrator can login into the system
and perform any of the available operations. Can enable/disable student.
Can edit student information to the database. Can make a search for a
specific student. Can access all the details of the student. The features that
are available to the student are: Student can login into the system and can
perform any of the available options. Can view his/her personal details. Can
edit his/her personal details Can upload his/her resume. Can upload his/her
image

#Software requirements:

• Microsoft .Net framework 3.5

• Microsoft Visual Studio 2008

• Microsoft ASP.Net 3.5

• Microsoft C#.Net language

• Microsoft SQL Server 2005

• ADO.NET

3 CSE 5TH CD
• HTML

#Hardware Requirements:

Processor: Intel Pentium 4 or more

Ram: 1 GB or more

Hard disk: 40 GB hard disk recommended for the primary partition.

3. FUNCTIONAL REQUIREMENTS OF STUDENT


MANAGEMENT SYSTEM.
● Register new students.
● Record the attendance of students.
● Record the internal marks of students.
● Record the feed details of students.
● Register a new teacher/employee.
● Register a new user for the system.
● Record the salary details of employees.
● Record the course details and subject information.
● Record the scholarship details and information.
● Generate various reports for all transactions in the system.

4. USER CASE DIAGRAM.

This user case diagram is a graphic depiction of the interactions among the
elements of the Student Management System. It represents the methodology
used in system analysis to identify, clarify and organize system requirements
of the student management system. The main actors of student management
system is this user case diagram are: Super Adim, System user, Faculties,
Student who perform the different type of use cases such as manage student,
manage fees, manage logins, manage profiles, manage courses, manage
exams, manage users and full student management system operations. Major
elements of the user case diagram are shown in the picture below.

The relationships between and among the actors and the use cases of the
Student Management System:

4 CSE 5TH CD
● Super Admin Entity: Use cases of Super Admin are to manage student,
manage fees, manage logins, manage profiles, manage courses,
manage exams, manage users and full student management system
operations.
● System User Entity: use cases of system User are to manage student,
manage fees, manage logins, manage profiles, manage courses,
manage exams.
● Faculties Entity: use cases of faculties are add courses, add exams,
publish result, view result.
● Student Entity: use cases of student are view results, view fees, make
fees payments.

5. NONFUNCTIONAL REQUIREMENTS

5.1 Performance Requirements

The proposed system that we are going to develop will be used as the Chief
performance system for providing help to the organization in managing the

5 CSE 5TH CD
whole database of the students studying in the organisation. Therefore, it is
expected that the database would perform functionally all the requirements
that are specified.

5.2 Safety Requirements

If there is extensive damage to a wide portion of the database due to


catastrophic failure, such as a disk crash, the recovery method restores a past
copy of the database that was backed up to archival storage (typically tape)
and reconstructs a more current state by reapplying or redoing the operations
of committed transactions from the backed up log, up to the time of failure.

5.3 Security Requirements

Security systems need database storage just like many other applications.
However, the special requirements of the security market mean that vendors
must choose their database partner carefully.

6. SPECIFIC REQUIREMENTS

6.1 Design constraints


The system needs to design based on the existing code and database using J2SE
5.0, J2EE 1.4 and Struts 1.2.x.

6.2 Software system attributes

6.2.1 Security
The system needs to log the client's registration information of registration such as IP
address and time for security purposes.
Passwords should be encrypted and stored in the database.

6 CSE 5TH CD
6.2.2 Maintainability
The system is developed using Struts, all action is detailed in struts-config.xml and
web.xml that are easy to modify and make update.

6.2.3 Portability
The web application is coding in J2EE and Struts, therefore, it should be transferable
between different OS and Java containers.

7 CSE 5TH CD

You might also like