Software Requirements Specification

For

Exam Registration System

1 Introduction
Examinations used to test the understandability of the Student and his
ability to recollect it, using it in apt situation, reasoning and Analytics. Now a days,
Instead of conducting examinations in papers, mostly everything is done online.
Starting from question paper setting and till the report of statistical score is
submitted online.
1.1 Purpose

This Software Requirements Specification provides a complete

description of all the functions and constraints of the Exam Registration
System. This document includes database management to maintain details
about the students, faculty members and staffs.

1.2 Scope

The website allows secure access for users with specific privileges.
Course materials cater to various courses, and examiners utilize the
platform for exam creation and result viewing. Administrators manage
admissions, results, and user registration. Security measures prevent exam
risks and malpractices. Published results cover past and upcoming exams.
The user-friendly interface requires only basic computer knowledge.

1.3 Definitions, Acronyms and Abbreviations

ACRONYMS ABBREVIATION DEFINITION

HTML Hypertext markup language Used to design static web
pages
EJB Enterprises java beans Programming platform to
develop and run java app.
DB2 Database Delivers flexible and cost
effective database platform
To build business
application.
HTTP Hyper Text Markup Language Used to design web pages

1.4 References

Page 1
 The document in this file is adopted from the IEEE guide to Software
requirement specifications (SRS).

1.5 Overview

The remainder of this document deals with the general requirements, in

section 2, and the specific requirements, in section 3. Section 2 deals with
requirements from the perspective of the end users of the product. Section 2
includes a few examples, requirements related to what the product must do for the
user, and data that the user must send to and receive from the product. Section 3,
on the other hand, deals with specific requirements and constraints of the project.
In section 3, it will provide information about external hardware and skills a user
must possess, various constraints on product based on users' needs, and the
interconnectivity of our product with its surrounding environment and users.

2.0 Overall Description

The online exam registration system streamlines registration, examinations,

and result publication, enhancing examination efficiency.
It alleviates examiner workload by scheduling exams based on covered
modules and allocating time tables according to chapters and subjects.
It accommodates various users such as Administrators, examiners, and
students for seamless access and operation.

2.1 Use-Case Model Survey

The Exam Registration Use Case Model facilitates student enrollment, examiner
exam creation, and administrator oversight. Students register and enroll in courses,
while examiners create and schedule exams. Administrators manage the system and
oversee the entire process. User authentication ensures security. Alternate flows
handle errors or full courses. Pre-conditions include system operation and valid
credentials. Post-conditions involve successful course enrollment, exam creation,
scheduling, and result publication.

2.1.1 Introduction

A use case is a methodology used in system analysis to identify, clarify and

organize system requirements. A use case (or set of use cases) has these characteristics:

 Organizes functional requirements

 Models the goals of system/actor (user) interactions
 Records paths (called scenarios) from trigger events to goals
 Describes one main flow of events (also called a basic course of action), and
possibly other ones, called exceptional flows of events (also called alternate
courses of action)
 Is multi-level, so that one use case can use the functionality of another one.

Page 2
 2.1.2 Survey Description
Student Registration:
 Actors Involved: Student, Administrator
 Description: Students register for the system to access exam
registration functionalities.
Course Enrollment:
 Actors Involved: Student, Administrator
 Description: Students enroll in courses they wish to take exams for.
Exam Creation:
 Actors Involved: Examiner, Administrator
 Description: Examiners create and modify exams, including adding
questions and setting parameters.
Exam Scheduling:
 Actors Involved: Examiner, Administrator
 Description: Examiners and administrators set the schedule for
exams, including dates and times.
Result Publication:
 Actors Involved: Examiner, Administrator
 Description: Once exams are graded, results are published for
students to view.
User Authentication:
 Actors Involved: Student, Examiner, Administrator
 Description: Users are authenticated before accessing exam
registration functionalities to ensure security.

2.1.3 Use-Case Model Hierarchy

Description:
The package allows users to login or register a user account - either as a
Student,examiner,Administartor in the system.

Use Cases:
Authenticate, Registration ,Take Test, Feed Question for a exam;
Use Case :
Primary Actor : Student, System
Pre-Condition: Student enrolled in that course
Post-Condition: Store details in database
Main Scenario

Page 3
 1.Questions are selected randomly and given to the student
2.Student submit the answers
3.System evaluates the answers
4.System displays result of the student
Database manager:
The database manager updates the question,answers and maintains the
student and the professor information.

Functional Requriement Non-Functional Requriement

Student Registration: Students must be able
to create accounts by providing necessary
information, which is then validated and
stored securely in the database.
Exam Creation: Examiners need to create
and configure exams by inputting exam
details, examiner details, and setting
parameters such as question types and
grading criteria.
Exam Scheduling: The system should
enable administrators to schedule exams
based on predefined criteria such as student
availability and course schedules.
Functional Requirement and
Result Publication: Exam results must be
published for students and administrators to
access, providing insights into performance
and grading.
Security: The system must ensure the
confidentiality and integrity of student and
examiner data through robust authentication
mechanisms and encryption protocols.
Performance: The system should handle
simultaneous registration and exam creation
requests efficiently, maintaining
responsiveness and scalability.
Usability: The user interface must be
intuitive and user-friendly, requiring minimal
training for users to navigate through
registration and exam creation processes.

Page 4
2.1.4 Diagrams of the use case model

1.3 Assumptions and Dependencies

 Registration are already created and information’s available for use.
 Roles and responsibilities are already established.
 Administrator is already created.
3. Requirements

It is possible in the future that a few additional features be implemented into

this system.
 Management system: This will allow the system to manage
effectively the other resources in the easiest way.
 Training facility: This will allow effectively train the staffs and
improve the quality of education in the institution.
3.1 Use-Case Specifications
The use case for online course registration system is register for exams,
select courses to register, maintain professor information, and maintain student
information.
3.2 Functionality
Inputs:

Page 5
 The Exam Registration System inputs student, course, exam, examiner, and
administrator data, alongside system configurations. Student information is
validated and stored, courses are enrolled, exams are created, and schedules are
arranged. Outputs include enrollment confirmations, exam schedules, results, and
system updates for users' access.
Processing:
1. Student Registration validates and stores student details in the database.
2. Course Enrollment checks course availability and enrolls students in chosen
courses.
3. Exam Creation configures exams by adding questions and parameters.
4. Exam Scheduling arranges exams based on predefined criteria like student
availability.
5. Result Publication shares exam results for student and administrator access.

Outputs:

 Student Enrollment Confirmation

 Exam Confirmation
 Exam Schedule
 Exam Resultseg

3.3 Usability
Some of the usability requirements identified for this system are listed
below:
 A logical interface is essential to an easy to use system, speeding up
common tasks.
 Error prevention is integral to the system and is provided in a number
of formats from sanity checks to limiting free-text input.

3.4 Reliability
Exam registration system is reliable because web site can never be prone to
any failures and are efficiently managed by database administrator and it saves cost.

Availability:
All cached data will be rebuilt during every startup. There is no recovery of
user data if it is lost. Default values of system data will be assigned when necessary.
Some of the attributes identified for the reliability is listed below:
 All data storage for user variables will be committed to the database at the time of entry.
 Data corruption is prevented by applying the possible backup procedures and
techniques

Page 6
 Portability:
Some of the attributes of software that relate to the ease of porting the
software to other host machines and/or operating systems. This may include:
 Java is used to develop the product. So it is easiest to port the software in any
environment.

3.5 Performance
Online library management system provided a good performance as the
whole process of becoming a member and issue of books takes place within few
seconds.

3.5.1 Response Time

In case of providing username and password to the user, the user signs up
an account. Administrator immediately sends a verification mail with a
conformation link. Once the user clicks onto this verification link, and he/she can
verification within few minutes.

3.5.2 Capacity
Any number of users can register the courses at a time.

3.6 Interfaces

User Interfaces:
Its interfaces depends person to person, if person is student then its interface
is different, if person is head of department then it is different and so on.

Hardware Interfaces:
Hardware interface will be keyboard, mouse, monitor and printer.

Software Interfaces: All data handling is done by DBMS so we require SQL along
with windows

Communication Interface:
 Client on Internet will be using HTTP/HTTPS Protocol.
 Client on intranet will be using TCP/IP protocol

Page 7