Srs of Student Result Management System Compress
Srs of Student Result Management System Compress
Srs of Student Result Management System Compress
Srs-of-student-result-management-system compress
Prepared by:
Name:p.v.saibalaji
Reg.No.Y20AIT477
BapatlaEngineeringCollege
lOMoARcPSD|20791547
Report-I
Table of Contents
1. INTRODUCTION.....................................................................................................................................................1
1.1 PURPOSE...............................................................................................................................................................1
1.2 SCOPE....................................................................................................................................................................1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................................................................1
1.4 REFERENCES.........................................................................................................................................................1
1.5 OVERVIEW
2. GENERAL DESCRIPTION....................................................................................................................................2
2.1 PRODUCT PERSPECTIVE........................................................................................................................................2
2.2 PRODUCT FUNCTIONS...........................................................................................................................................2
2.3 USER CHARACTERISTICS......................................................................................................................................2 2.4
GENERAL CONSTRAINTS.......................................................................................................................................2 2.5
ASSUMPTIONS AND DEPENDENCIES......................................................................................................................3
3. SPECIFIC REQUIREMENTS................................................................................................................................2
3.1 EXTERNAL INTERFACE REQUIREMENTS...............................................................................................................3
3.1.1 User Interfaces.............................................................................................................................................3
3.1.2 Hardware Interfaces....................................................................................................................................4
3.1.3 Software Interfaces......................................................................................................................................4
lOMoARcPSD|20791547
1.1 Purpose
This specification document describes the capabilities that will be provided by the
software application STUDENT RESULT MANAGEMENT SYSTEM .It also states the
various constraints by which the system will abide. The intended audience for this
document are the development team, testing team and end users of the product.
1.2 Scope
The application will manage the information about various students enrolled in this
course in different years, the subjects offered during different semesters of the course, the
marks obtained by the various students in various subjects in different semesters. The
application will greatly simplify and speed up the result preparation and management
process.
1.5 Overview
Student’s information is stored in mysql the authority is given to Administrator; he gives
the permission to instructor to enter the department data and student information. The
security is providing by giving password to each instructor..
2. General Description
This section of the SRS should describe the general factors that affect 'the product and its
requirements. It should be made clear that this section does not state specific
requirements; it only makes those requirements easier to understand.
4) Generation of Reports
3. Specific Requirements
This section contains the software requirements to a level of detail sufficient to enable
designers to design the system and testers to test that system.
Login screen: This will be the first screen that will be displayed. It allows user to access
different screens based upon the user role. Various fields available on this screen will be
User id: alphanumeric of length up to 10char.
Password: alphanumeric of length up to 10char
Role: Will have the following
Values: Administrator, Data entry Operator , student , teacher
4) Student Information Screen: This screen will be accessible only to the Administrator.
It will allow the user to modify the information about new/existing student for
particular batch year. Various fields available on these screen are:
Student Enrollment No: of the format B.E/YYYY where YYYY represents the batch year
Student Name: only alphabetic letters and length up to 40 chars.
Batch Year: of the format YYYY
5) Marks Entry Parameter Screen: This screen will be accessible only to the Teacher. It
will allow the user to enter the Batch Year, the semester number and the subject for
which the user wants to access the marks information.
6) Marks entry screen: Screen: This screen will be accessible only to the Teacher. It will
allow the user to add/modify/delete information about the marks obtained in the
SoftwareRequirements Specification
lOMoARcPSD|20791547
selected subject by different students. It includes Student enrollment no, student name,
internal marks, external marks, total marks.
1 .Safety Requirements
The database may get crashed at any certain time due to virus or operating system
failure. Therefore, it is required to take the database backup
2. Security Requirements
We are going to develop a secured database for the university .Depending upon the
category of user the access rights are decided. It means if the user is an administrator then
he can be able to modify the data, delete, append etc. All other users other than staff only
have the rights to retrieve the information about database.
3. Hardware Constraints
The system requires a database in order to store persistent data. The database should
have backup capabilities
DB Requirement
4. Analysis Models
4.1 Flow Chart Context
diagram-
SoftwareRequirements Specification
lOMoARcPSD|20791547
LEVEL-1 DFD
LEVEL -2 DFD
SoftwareRequirements Specification
lOMoARcPSD|20791547
SoftwareRequirements Specification
lOMoARcPSD|20791547
ER DIAGRAM