Software Requirements Specification

Software Requirements
Specification
Student Portal
12.02.2015
Swami Pushkar
Himanshu Sachdeva
Deepak Singh
Varun Sharma

(CSE/12/340)
(CSE/12/320)
(CSE/12/312)
(CSE/12/346)

(Approved by AICTE, Ministry of HRD, Govt of India & DTE, Govt of Haryana
and Affiliated to DCRUST, Murthal)

Page i

Software Requirements Specification

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ........................................................................................................................... iv
1. Introduction ..............................................................................................................................1
1.1
1.2
1.3
1.4
1.5

Purpose ........................................................................................................................................ 1
Document Conventions ............................................................................................................... 1
Intended Audience and Reading Suggestions ............................................................................. 1
Project Scope ............................................................................................................................... 1
References ................................................................................................................................... 1

2. Overall Description ..................................................................................................................2

2.1
2.2
2.3
2.4
2.5
2.6
2.7

Product Perspective ..................................................................................................................... 2

Product Features .......................................................................................................................... 2
User Classes and Characteristics ................................................................................................. 2
Operating Environment ............................................................................................................... 2
Design and Implementation Constraints ..................................................................................... 3
User Documentation .................................................................................................................... 3
Assumptions and Dependencies .................................................................................................. 3

3. System Features........................................................................................................................4
3.1
Login............................................................................................................................................ 4
3.1.1 Description and Priority .......................................................................................................... 4
3.1.2 Stimulus/Response Sequences ................................................................................................ 4
3.1.3 Functional Requirements ........................................................................................................ 4
3.2
Registration ................................................................................................................................. 4
3.2.1 Description and Priority .......................................................................................................... 4
3.2.2 Stimulus/Response Sequences ................................................................................................ 4
3.2.3 Functional Requirement .......................................................................................................... 4
3.3
Time Table .................................................................................................................................. 4
3.3.1 Description and Priority .......................................................................................................... 4
3.3.2 Stimulus/Response Sequences ................................................................................................ 5
3.3.3 Functional Requirement .......................................................................................................... 5
3.4
Notes/Book .................................................................................................................................. 5
3.4.1 Description and Priority .......................................................................................................... 5
3.4.2 Stimulus/Response Sequences ................................................................................................ 5
3.4.3 Functional Requirement .......................................................................................................... 5
3.5
Attendance ................................................................................................................................... 5
3.5.1 Description and Priority .......................................................................................................... 5
3.5.2 Stimulus/Response Sequences ................................................................................................ 5
3.5.3 Functional Requirement .......................................................................................................... 5
3.6
Aptitude Test ............................................................................................................................... 6
3.6.1 Description and Priority .......................................................................................................... 6
3.6.2 Stimulus/Response Sequences ................................................................................................ 6
3.6.3 Functional Requirement .......................................................................................................... 6
3.7
Forum .......................................................................................................................................... 6
3.7.1 Description and Priority .......................................................................................................... 6
3.7.2 Functional Requirement .......................................................................................................... 6
3.8
Fees .............................................................................................................................................. 6
3.8.1 Description and Priority .......................................................................................................... 6
3.8.2 Functional Requirement .......................................................................................................... 6

4. External Interface Requirements ...........................................................................................7

4.1
4.2
4.3
4.4

User Interfaces ............................................................................................................................. 7

Hardware Interfaces .................................................................................................................... 7
Software Interfaces ...................................................................................................................... 7
Communications Interfaces ......................................................................................................... 7

Page ii

Software Requirements Specification

5. Other Nonfunctional Requirements .......................................................................................8

5.1
5.2
5.3
5.4

Performance Requirements ......................................................................................................... 8

Safety Requirements .................................................................................................................... 8
Security Requirements ................................................................................................................ 8
Software Quality Attributes ........................................................................................................ 8

6. Other Requirements ..............................................................................................................10

Appendix A: Glossary..................................................................................................................10
Appendix B: Analysis Models .....................................................................................................10
Appendix C: Issues List ...............................................................................................................10

Page iii

Software Requirements Specification

Revision History
Name

Date

Reason For Changes

Version

Page iv

Software Requirements Specification

1. Introduction
1.1 Purpose
The purpose of this report is to specify the software requirements of the project Student Portal.
The project Student Portal is being developed for the need of organization and student. This is
one of the best efforts by us to prove that how online system can be helpful in such organization.
This system however is a snapshot of the whole scenario for the booming service industry.

1.2 Document Conventions

All the titles are in bold and font size 16 and all the other contents have font Times New Roman and
font size 12.

1.3 Intended Audience and Reading Suggestions

The target audiences of this document are design team, development team, testing team and all the members
who are directly and/or indirectly responsible for delivery of this project.

1.4 Project Scope

The objective is to create a website which can help students to view academic record online and to
reduce paper work as it is also easy to access online.

1.5 References

https://en.wikipedia.org/wiki/Software_requirements_specification
https://www.assembla.com/wiki/show/csci4200-group3/External_interface_requirements

Software Requirements Specification

2. Overall Description
2.1 Product Perspective
Student Portal is a web application that maintains student academic record.

2.2 Product Features

Student Portal is applicable to this fast growing world where there is a need to communicate by
sharing information. Today we need all relative information easily and that too in minimal time.
This project has different modules like new User login, Downloading Files, Attendance
management, Fees, Aptitude test, Syllabus, Forum etc.

2.3 User Classes and Characteristics

We divide the users in to three categories:
Student Login
First is Students, which have limited facilities in approximate all modules. Students will
not have write permission in different fields such as Attendance info, Library info,
Result etc. Student can only update some personal information.

Teacher Login
Second is Teachers, who have to upload some set of information such as Result, Notes,
Books and Attendance for all the students.

Admin Login
Last user is admin, who manages the student and teacher user. Admin may upload some
data such as yearly fees, may add a new user and much more.

2.4 Operating Environment

This application will be available as a website. The full description of the environment in which this
product will be developed is as follows:
Platform
Operating System
Scripting Language
Layout
Server
Back-End Tool
Technology

Windows
Windows 7 and above
JavaScript
HTML
Apache Tomcat 6.0
MySQL
J2EE (JSP and Servlet)

Software Requirements Specification

2.5 Design and Implementation Constraints

N.A.

2.6 User Documentation

N.A.

2.7 Assumptions and Dependencies

Below are the assumptions for this project:

People will have a proper internet connection so as to connect to the website

People will be able to find the website easily with the knowledge of the proper URL
People will be provided a good GUI so that the user knows where to click accordingly
People will contact customer service if they have a question or problem
An interactive GUI will serve the purpose of people coming back in order to use the
website

We assume that our product shall provide sufficient space on servers to maintain the database to
clients

Software Requirements Specification

3. System Features
3.1

Login

3.1.1 Description and Priority

Login is one of the integral module. Three types of user can login- administrator, teacher and
student. It checks for a valid candidate when the user enters his user id and password.
3.1.2 Stimulus/Response Sequences
After entering user id and password there will be a submit button which will have event on button
click.
3.1.3 Functional Requirements
It is divided into following functions:

Login Checker

3.2 Registration
3.2.1 Description and Priority
Registration module mainly provides a form to the user to fill the necessary details for the first time
they log on to the portal and then submit it to get registered.
3.2.2 Stimulus/Response Sequences
After entering full details, there will be a submit button which will have event on button click.
There will also be a Reset button to fill details again.
3.2.3 Functional Requirement
It is divided into following functions:
Unique Id Checker
Mailing System

3.3

Time Table

3.3.1 Description and Priority

Teacher uploads time table.

Software Requirements Specification

3.3.2 Stimulus/Response Sequences

It is displayed on the student portal when a Student may log in.
3.3.3 Functional Requirement
It is divided into following functions:
Downloader

3.4 Notes/Book
3.4.1 Description and Priority
Teachers may upload some reference books and notes that may serve a great purpose.
3.4.2 Stimulus/Response Sequences
It is in a file format (such as .pdf, .doc) which can be downloaded.
3.4.3 Functional Requirement
It is divided into following functions:
Downloader

3.5 Attendance
3.5.1 Description and Priority
Teachers upload Attendance for each student weekly which is displayed on the student portal.
3.5.2 Stimulus/Response Sequences
If the attendance of a student goes below 75% then the system automatically generates and sends a
mail to the registered email id of the parent/guardian of student.
3.5.3 Functional Requirement

Display

Software Requirements Specification

3.6 Aptitude Test

3.6.1 Description and Priority
This module provides students the ability to assess their aptitude and technical skills
3.6.2 Stimulus/Response Sequences
The results of the test will be displayed immediately after they finish the test. Result may also be
mailed.
3.6.3 Functional Requirement
It is divided into following functions:
Id Checker
Mailing System
Result Checker

3.7 Forum
3.7.1 Description and Priority
In this module, user can upload any query, doubt or question and other users can provide
solution/answer for the specified query.
3.7.2 Functional Requirement
It is divided into following functions:
Id Checker
Mailing System
Answer Checker
Downloader

3.8 Fees
3.8.1 Description and Priority
This module displays the fee structure as well as submitted fees along with the cheque number, DD
number etc.
3.8.2 Functional Requirement

Display
6

Software Requirements Specification

4. External Interface Requirements

4.1 User Interfaces

The User Interface of the product will be designed in HTML

Screen resolution will be optimized for 1024*768 pixels

4.2 Hardware Interfaces

An internet connection to allow the browser software interfaces to connect to the internet to access
the files of the website.

4.3 Software Interfaces

Name:

Google Chrome, Mozilla Firefox, Internet Explorer, Apple Safari, Opera or other web
browsers
Purpose: To allow remote access of the website and downloading of files via the internet.

4.4 Communications Interfaces

Internet Protocol (IP) shall be used by the software interfaces to connect to the internet.

Software Requirements Specification

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The system should be able to handle the sudden burden of multiple logins and queries
without deviating much in response time.
24x7 availability of the system with suitable updating at regular intervals of time.
Users feedbacks should be analyzed and updated (add/delete features) accordingly.
The reply to all the queries of the users should be correct adequate and appropriate.
To maintain the integrity of the data and in order to ensure the security of the database, every
user is validated (using a password and login id)

5.2 Safety Requirements

The system should be able to recover in adequate and less time after any type of crash.
Proper safety of data will be required.
The system should be secure to threats like hacking and viruses to the highest degree
possible.

5.3 Security Requirements

Following are the security requirements that need to be performed the processing of secure
system:

Physical Security
N.A.

Database Security
-

SQL Server authentication: In this case, SQL Server requires that a user specifies a
name and password at the time when connection is attempted.

Windows authentication: With built in Windows authentication and per-application

configuration, we can be assured that your applications are secure.

5.4 Software Quality Attributes

The main quality attributes of this product will be:
Availability: - Our product will have more time to be functional and working. If the system
will be affected by any type of errors, malicious attacks and system loads then it
will be able to recover in less time.

Software Requirements Specification

Maintainability: - Maintainability is the ability of the system to undergo changes with a

degree of ease. These changes could impact components, services, features,

and interfaces when adding or changing the functionality, fixing errors, and
meeting new business requirements. Our product will have good maintainability as
it is divided into modules, therefore we can easily make any changes to this smaller
parts.

Reusability: - Reusability defines the capability for components and subsystems to be

suitable for use in other applications and in other scenarios. As our product has
different smaller modules, it will be easy to reuse them anywhere else.
Usability: -

This product will have good user interface clear and easy to use. Pages will
include buttons and radio buttons, and the screen layout will also be suitable.

Modifiability: - This product will have nice modifiability because different functionalities
will be divided into modules making them easy to modify.

Software Requirements Specification

6. Other Requirements
This project need to be hosted on a domain to serve multiple user requests.

Appendix A: Glossary
SRS: - Software Requirement Specification
IE: - Internet Explorer
GUI: - Graphical User Interface
SQL: - Structured Query Language

Appendix B: Analysis Models

N.A.

Appendix C: Issues List

N.A.

10