Padmabhooshan Vasantraodada Patil Institute of Technology,

Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

Student Result Management System

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions Acronyms and Abbreviations
1.4 References
2. Overall Description
2.1 Product perspective
2.2 Product functions
2.3 User characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
3. External Interface Requirements
3.1 User interfaces
3.2 Hardware interfaces
3.3 Software interfaces
3.4 Communication interfaces
4. System Features
4.1 Subject Information maintenance
4.2 Marks Information maintenance
4.3 User Account information maintenance
4.4 Functional requirements
4.5 Logical DB requirements
5. Other Nonfunctional Requirements
5.1 Performance
5.2 Reliability
5.3 Availability
5.4 Security
5.5 Maintainability
5.6 Protability

1
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

Student Result Management System

Students Name & Roll No.

3001. Pranav Popat Shinde
3002. Sneha Popat Manepatil
3003. Sadaf Najir Kalawant
3004. Usha Ramchandra Kudale Subject In-charge

2
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

Table of Contents

1.Introduction .................................................................................................................... 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations 4
1.4 References 5
2.The Overall Description .................................................................................................. 6
2.1 Product Perspective 6
2.2 Product Functions 6
2.3 User Characteristics 6
2.4 Constraints 7
2.5 Assumptions and Dependencies 7
3. External interface Requirements .................................................................................. 8
3.1 User Interfaces 8
3.2 Hardware Interfaces 9
3.3 Software Interfaces 9
3.4 Communications Interfaces 9
4. System Features………………………………………………………………………...10
4.1 Subject Information maintenance 13
4.2 Marks Information maintenance 13
4.3 User Account information maintenance 13
4.4 Functional requirements 14
4.5 Logical DB requirements 14
5. Other Non-Functional Requirements…………………………………………………15
5.1 Performance 15
5.2 Reliability 15
5.3 Availability 15
5.4 Security 15
5.5 Maintainability 16
5.6 Portability 16

3
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

1. Introduction

The student management system can handle all the details about a student. The details
include college details, course details, student personal details, academic details etc., the
student management system is an automated version of manual student management system.

1.1 Purpose

This SRS Document contains the complete software requirements for the Online Student
Information Management System (OS I MS) and describes the design decisions, architectural
design and the detailed design needed to implement the system. It provides the visibility in the
design and provides information needed for software support. New reliable and fast
school/college management software with the great customers support. It'll help you with your
daily school/college management routines..

1.2 Scope

Online Student Information Management System is developing for general purpose and used
to replace old paper work system and PUMS. OSIMS is to build upon the existing information
system PUMS in order to efficiently provide student information to teachers and school/college
administration. This increase in efficiency of result making, provide result to parents, give
feedback to student, finally, publication and email student result. It provides a mechanism to
edit the student information form which makes the system flexible.

1.3 Definitions, Acronyms, and Abbreviations.

OSIMS Online Student Information Management System

PUMS Project Units Management System
SRS Software Requirement Specification

OS Operating System
URS User Requirement Specification
TCP/IP Transmission Control Protocol/Internet Protocol
ASP.NET Active Server Pages Network Enabled Technologies

4
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

1.4 References

(a)https://www.scribd.com/doc/48111565/Software-Requirements-Specification-for-online-
student-management-system.

(b) ‘Software Engineering’ by K.K. Aggarwal & Yogesh Singh, New Age Publishing House,

2nd Ed.

© IEEE Recommended Practice for Software Requirements Specifications – IEEE Std

830-1998.

(d) IEEE Standard for Software Test Documentation – IEEE Std. 829-1998.

5
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

2. The Overall Description

The student management system allows authorized members to access the records of
academically registered students. It can be used in various educational institutes across the
globe and simplifies working of institutes.

2.1 Product Perspective

The proposed system shall be developed using client/server architecture and be compatible
with Microsoft Windows Operating System. The front end of the system will be developed
using Visual Basic 6.0 and backend will be developed using MS SQL Server 2000.

2.2 Product Functions

The OSIMS will allow access only to authorized users with specific roles (System
administrator, Faculty and Student). Depending upon the user’s role, he/she will be able to
access only specific modules of the system.

A summary of major functions that the URS will perform

· A login facility for enabling only authorized access to the system.

· System administrator will be able to add, modify or delete programme, school/college,

scheme, paper and login information.

· Students will be able to add/modify his/her details and register for papers to be studied in
the current semester.

· System administrator/Faculty will be able to generate reports.

2.3 User Characteristics

Qualification: At least matriculation and comfortable with English.

Experience: Should be well versed/informed about the registration process of the university.

Technical Experience: Elementary knowledge of computers

6
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

2.4 Constraints

There will only be one administrator. The delete operation is available only to the
administrator. To reduce the complexity of the system, there is no check on delete operation.
Hence, administrator should be very careful before deletion of any record and he/she will be
responsible for data consistency

2.5 Assumptions and Dependencies

- The login Id and password must be created by system administrator and communicated to the
concerned user confidentially to avoid unauthorized access to the system.

- It is assumed that a student registering for the subsequent semester has been promoted to that
semester by the university as per rules and has paid desired university fee. · Registration
process will be open only for specific duration.

7
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

3. External Interface Requirements

3.1 User Interface

The OSIMS will have following user-friendly and menu driven interfaces

a) Login: to allow the entry of only authorized users through valid login Id and password.

b) School/college Details: to maintain school/college details

c) Programme Details: to maintain programme details.

d) Scheme Details : to maintain scheme details of a programme.

e) Paper Details: to maintain paper details of a scheme for a particular programme

g) Faculty Details : to maintain the faculty details.

The following screens will be provided:

1) 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 10charRole:
Will have the following Values: Administrator, Data entry Operator , student , teacher

2) Subject info Parameter Screen: This screen will be accessible only to the Administrator. It
will allow the user to enter the semester number for which the user wants to access the
subject information.

3) Student info Parameter Screen: This screen will be accessible only to the Administrator. It
will allow the user to enter the Batch Year for which the user wants to access the student
information.

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

8
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

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

3.2 Hardware Interface

a) Screen resolution of at least 640 x 480 or above.

b) Support for printer (dot matrix, deskjet, laserjet)

c) Computer systems will be in the networked environment as it is a multi-user system.

3.3 Software Interface

a) MS-Windows Operating System

b) Microsoft Visual Basic 6.0 for designing front-end

c) MS SQL Server 2000 for backend

d) PLATEFORM : JAVA LANGUAGE

e) INTEGRATED DEVELOPMENT ENVIRONMENT(IDE):ECLIPSE

3.4 Communication Interface Requirements

Connections to the system will be over TCP/IP connection

9
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

4. System Features

Use Case Diagram –

10
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

Data Flow Diagram -

11
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

Class Diagram –

12
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

4.1 Subject Information maintenance

The system will maintain information about various subjects being offered during different
semesters of the course. The following information will be maintained for each subject: Subject
code, Subject type, Semester.
The system will allow creation , modification ,deletion of new, existing subjects and also have
the ability to list all the available subjects for a particular semester.
Validity Checks:
1)Only user with the data entry operator will be able to access the Subject Information
Maintenance module.
2)No two semester will have the same subject.
3)The subject code will be unique for each subject .
4)Subject code, Subject name, semester cannot be blank

4.2 Marks Information maintenance

The system will maintain information about the marks obtained by various students of
different enrollment year in different semesters. The following information would be
maintained :
Student Enrollment Number, Semester, Subject code, internal marks, External Marks, Total
marks. The system will allow creation/modification/deletion of marks information and also
have the ability to list all the available marks information for all students for a particular
subject in the given semester.
Validity check:
• Only the user with role of teacher will be authorized to access the Marks Information
maintenance module.
• Marks cannot be less than 0.
• Total marks will be calculated as :Internal Marks in that subject + External Marks in
that subject .

4.3 User Account Information maintenance

A system will maintain information about various users who will be able to access the
system. The following information would be a maintained: User name, user ID,
password<Role.
VALIDITY CHECK:
i. Only user with role Administrator will be authorized to access the User Accounts
Information Maintenance module.
ii. User Name, User Id, Password, Role cannot be left blank

13
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

4.4 Functional Requirement

4.4.1 Log in Module (LM)

User (admin, student and teachers) shall be able to load the Login Module in the internet
browser. The LM shall support the user to log into the system. The login panel shall contain
fields to contain a user name and a field for password. The password field shall be masked
with symbols when the user types. It shall also contain a button labelled as Login. When the
user clicks on Login button the username and password will be verified by database
administrator and then only the user will able to use the system functions.

4.4.2 Registered Users Module (RUM)

After successful login, user shall be able to continue navigating through the website and view
school/college detailed information. After successful login, user (admin, student and
teachers) shall be able to update and maintain their profile, such as changing password and
personal details.

4.4.3 Normal Users Module (NUM)

Users who visit SMS but have not registered, are able to navigate through the system. Users
shall be able to view currently held events & upcoming institute schedule. Users shall be able
to view school/college timings and their faculties information. Users are able to register
themselves as registered users, by clicking on the register now button.

4.4.4 Administrator Module (AM)

After successful login, system shall display administrative functions. Administrative
functions shown shall be add and update. When administrator clicks on the add button,
system shall display a section where administrator can add new student details, remove
unused student details and many more. When administrator clicks on update button, system
shall display a section where administrator can update student details and schedule of lecture
which are currently stored in the database. When administrator adds, updates or delete and
entry, the AM module will send the request to the Server Module which will do the necessary
changes to the DB.
3.2.9 Server Module (SM) SM shall be between the various modules and the DB. SM shall
receive all requests and format the pages accordingly to be displayed. SM shall validate and
execute all requests from the other modules

4.5 Logical DB Requirement

The following information will be placed in DB:
1)Subject info: Subject Name, Code, Semester
2)Student Info: Student Enrolment Number, Student name, Enrollment year.
3)Marks info: Student Enrollment , Semester, internal marks in each subject, external marks
in each subject
4)User Account Info: User Name, User Id, password, role

14
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

5. Other Nonfunctional Requirements

Non-functional requirements may exist for the following attributes. Often these requirements
must be achieved at a system wide level rather than at a unit level. State the requirements in
the following sections in measurable terms (e.g., 95% of transaction shall be processed in less
than a second, system downtime may not exceed 1 minute per day, etc.).

5.1 Performance
The system and the server must be capable of handling the real-time error functionality
occurs by the defined users. In addition, the system must be safety critical. All failures
reported by the server side must be handled instantaneously to allow for user and system
safety. Easy tracking of records and updating can be done.

5.2 Reliability
The system is safety critical. If it moves out of normal operation mode, the requirement to
drop or down the server and fix it as soon as possible and open it again. This emergency
behaviour shall not occur without reason. The system are reliable to users anytime, anywhere,
just need a PC and Internet Connection. Also the system work in multiple web browsers like
(Chrome, Mozilla, Opera, and Internet Explorer).

5.3 Availability

When in normal operating conditions, request by a user for system shall be handled within 1
second. Immediate feedback of the systems activities shall be communicated to the user.

5.4 Security
There shall be a strong security mechanism should be place in the server side of the system to
keep unwanted users to hack or damage the system. However, all users of the system give
and store the details of privacy related to personal information and many other. The system
have accounts for its users and only authorized users can access the system with username
and password. The passwords are encrypted using a ASP.NET function.

5.5 Maintainability
There shall be design documents describing maintenance of the software and database used to
save the user details as well as the daily updated and modification done in system. There shall
be an access on the control system by the admin to be maintained it properly at the front end
as well as at back end. The system have a friendly user interface and the system very
interactive.

15
 Padmabhooshan Vasantraodada Patil Institute of Technology,
Sangli (Budhgaon)
(Approved by AICTE, New Delhi, Recognized by Government of Maharashtra, Affiliated to DBATU Lonere)

Department of Computer Science & Engineering

5.6 Portability

There is portability requirement as far as our system is concern because it is an online as well
as offline (local server based) system so we can access it from anywhere through the internet
connection. And we have to maintain the copy of stored data into our database.

16