Software Requirements Specification

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview

2. General Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
2.4 General Characteristics

3. Specific Requirements
3.1 Functional Requirements
3.2 Performance Requirements
3.3 Non-Functional Requirements
3.4 Design Constraints
1. Introduction

1.1 Purpose

Basic Description of Problem

The purpose of the project is to provide online facility to Institutes to conduct online exams
and to Students to give online exams. Institutes can enter and edit the questions along with
the students list. Also they can view the result. Students can login and give their respective
exams and view their score then and there. Others can view sample papers to get look and
feel of the online examination system.

1.2 Scope

Scope of this project is very broad compared to manually taken exams. They are:-
 This app can be used in educational institutions as well as in corporate world.
 Can be used anywhere any time as it is a web based application (user location doesn’t
matter.
 No restriction that examiner has to be present when the candidate takes the test.
 No manual work of preparing and storing the result information.
 Less time consumption, as the result is calculated immediately after the test and
displayed to the student/candidate.
 For students/candidates, it saves time of going to far away centers to give exams.

1.5 Overview

 This system provide an easy solution to the student to give exam online.

2. General Description

2.1 Product Perspective

(i) User interfaces

The application will have a user friendly and menu based interface.

Following screens will be provided:

(ii) A login screen for entering the username, password will be provided. Access to different
screens will be based upon the user.

(iii) There is a screen for displaying information regarding entries to be made by institutes.

(iv) There is a screen for displaying information regarding filling of exam details by
institutes.
(v) There is a screen for displaying information regarding entering student list for the
particular exam.

(vi) There is a screen for displaying information menu regarding what options the institutes
will select while filling entries (entering questions, student list, deleting questions, entering
exam details).

(vii) There is a screen for displaying exam details to the students when they are taking exams.

(viii) There is a screen for taking exam for the students.

(ix) There is a screen for displaying of results of students after taking the exam.

2.2 Product Functions

The functions are divided according to the user types such as:-
 Administrator:- The function of the administrator is to add/edit exams in the test
module.
 Candidate:- The function of the student is to update his/her profile and give various
exams.

2.3 User Characteristics

 Candidate module: The candidate will logon to the software and take his
examination. He can also check his previous examinations marks and his
details. The candidate will get result immediately after the completion of the
examination.
 Examiner module: The database is prepared & loaded into the software.
Selection for examination can be done language wise by the examiner. The
results will be displayed immediately after completion of the examination.
 Administrator module: The administrator collects all the results after
successful completion of the examination and sends to the head quarters as
and when required.

Based on the above categorizations, in order to meet user's needs the following precautions
should be taken:

 Time can be saved by scheduling the exams, if it is available a question bank to store
questions for different subjects.
 A system can be given a mark by checking the students answers, and give the result as
soon as students finish his exam.
 A facility to generate a result chart as pre required without manual interface.
  The system should have records of students and faculty that can be access to the
system which can be used only for the authorized person.
 The system should be more secure for management user records and more reliable to
work at any conditions.

2.4 General Constraints

The following constraints will limit the developer's options for designing the system:

 An extra security as SSL must be used to secure the marks details and other examination information.

3. Specific Requirements

3.1 Functional Requirements

This section gives a functional requirement that applicable to the On-Line Exam
system.
There are three sub modules in this phase.
 Candidate module.
 Examiner module.
 Administrator module.

The functionality of each module is as follows:

 Candidate module: The candidate will logon to the software and take his
examination. He can also check his previous examinations marks and his
details. The candidate will get result immediately after the completion of the
examination.
 Examiner module: The database is prepared & loaded into the software.
Selection for examination can be done language wise by the examiner. The
results will be displayed immediately after completion of the examination.
 Administrator module: The administrator collects all the results after
successful completion of the examination and sends to the head quarters as
and when required.

The features that are available to the Administrator are:

 The administrator has the full fledged rights over the OES.
 Can create/delete an account.
  Can view the accounts.
 Can change the password.
 Can hide any kind of features from the both of users.
 Insert/delete/edit the information of available on OES.
 Can access all the accounts of the faculty members/students.

The features available to the Students are:

 Can view the different categories of Test available in their account.
 Can change password.
 Can view their marks.
 Can view the various reading material.
 Can view and modify its profile but can modify it to some limited range.

The features available to the Examiner are:

 Can view the different categories of Test conducted by users.
 Can change password.
 Can view their marks.
 Can view and modify Results.

3.2 Performance Requirements:

This subsection specifies numerical requirements placed on the software or on the human
interaction with the software, as a whole. Numerical requirements will include:
 300 terminals will be supported at a time

 Only text information will be supported (HTTP)

 All the transactions will be processed within seconds.

3.3 Non-functional Requirements

3.3.1) Performance Requirements

Some Performance requirements identified is listed below:
 The database shall be able to accommodate a minimum of 10,000 records
of students.
  The software shall support use of multiple users at a time.
 There are no other specific performance requirements that will affect
development.

3.3.2) 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.

3.3.3) Security Requirements

Some of the factors that are identified to protect the software from accidental or
malicious access, use, modification, destruction, or disclosure are described
below. Keep specific log or history data sets
 Assign certain functions to different modules
 Restrict communications between some areas of the program
 Check data integrity for critical variables
 Later version of the software will incorporate encryption techniques in the
user/license authentication process.
Communication needs to be restricted when the application is validating the user or license.
(i.e., using https).
 DFD:

Admin
Student Registration Exam schedule
Online exam
system

Success registration

Level 0
Get info

Update login _mst

Get info STUDENT_MST

Student Student
registration
and login
process

Get_info

2.0 admin
Admin activity
Update info to master

Make a receipt and reports

Print Report
report and
receipt Report_info
Getting details

Level 1