Software Requirements

Specification
For

Dynamic web application for online examination

system
Version-0

Prepared by -

Sohel Mujawar (1526244)

Dhiraj Patil (1526252)

Shubham Salunkhe (1526255)

Abhiraj Saste (1526257)

Aniket Velhankar (1526259)

Harshal Wagh (1526260)

Date created-
Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions...................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective.........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces.............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1.............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6

 
1. INTRODUCTION

1.1 PURPOSE

The purpose of this document is to build an online system to conduct exams and manage the
student and staff activities.

1.2 DOCUMENT CONVENTIONS

The content of this document is written in Times New Roman with font size 12. The main
titles of the body are written in Times New Roman with font size 14.The margins are set as
follows: left and right is 0.9” while top and bottom is 1”.The line spacing is selected 12 point.

1.3 INTENDED AUDIENCE AND READING SUGGESTIONS

This project is a prototype for the online examination system and it is restricted to
educational institutions. This has been implemented under the guidance of college professors.
This project is useful for the students as well as to the teachers.

1.4 PROJECT SCOPE

The ‘online examination system’ is the project that focuses on providing the support for
giving the examinations, accessing information about courses, syllabus, and various notices
in an online manner.

The project can be accessed globally through the website which will be useful for all the
students from schools, universities and various other educational institutions. Also candidates
from non-educational institutions can have the project beneficial for attempting various
exams such as licensing exams, GK tests, aptitude tests, quizzes and so on online. We’ll have
a database server supporting records of student’s performance, thus the students as well as
teachers and parents can access this record for planning purposes.

The project focuses on automated generation of result as soon as the exam ends. The
questions are of multiple choice types. Above all, we hope to provide a comfortable user
experience.

1.5 REFERENCES

 https://krazytech.com/projects
 Fundamentals of database systems by ramez elmarsi and shamkant b.navathe
2. OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

The database for online examination system stores the following information.

 Student:
This includes the student’s name, roll number, date of birth, email id, place of birth,
address, contact number, attendance, and grades.
 Teacher:
This includes the name of the teacher, teacher id, contact number, email id, subject id
and subject name.
 Exam:
This includes the test id, paper id, subject name, marks, question id and choice
Number, test duration,syllabus.
 Administrator:
This includes the name of the administrator, admin id, email id, contact number and
the department.
 Database administrator:
This includes the name and id of the head of the database administrator, email id, and
contact number.

2.2 PRODUCT FEATURES

2.3 USER CLASS and CHARACTERISTICS

These characteristics are of the users of the web application that will be using the online
examination system for giving exams online, or performing an activity such as checking
syllabus or time table or any other activity concerned with the application.
The actors that interact with the application and the database include Developer, Tester,
Student, Teacher, Administrator, etc.

The student performs the following activity:

 Student-
 The primary responsibility of the student is to attempt the exams.
 The student can share his/her notes on various topics.
 He/she can conduct discussion on various topics.
 Queries can be asked directly to the respective faculty.

The teacher performs the following functions:

 Teacher:
 The staffs set the question papers.
 It can conduct discussion on various topics.
 Syllabus can be provided online.
 It can keep a watch on student’s performance.
 The administrator performs the following functions:

 Administrator:
 To collaborate various sections for examination.
 To provide notices such as examination dates.
 Conduct meetings with the staff.

The database administrator performs the following functions:

 Database administrator:
 To ensure the consistency of the database.
 To manage frequent updates.
 To ensure accurate results.
 Maintain database integrity.

The developer performs the following functions:

 Developer:
 Develop the software according to suitable model.
 Ensure correct functionality of code.
 Maintain the functionality according to the requirements.
 Solve the bugs and errors.

The Tester performs the following functions:

 Tester:
 Find out the bugs from the code.
 Think of exceptional cases and handle them.
 Report the developer about the bugs.

The controller performs the following functions:

 Controller:
 Provide the online help and support.
 Solve the problem of any administrator or individual related to the
organization.
 Keep the control of every task in the organization.
 Available at the ‘contact us’ desk of the software.

2.4 OPERATING ENVIRONMENT

Operating environment for the online examination system is as listed below.

 Distributed database.
 Client/Server system.
 Operating system: Windows, Android, iOS.
 Database: MYSQL.
  Platform: ASP.net.

2.5 DESIGN and IMPLEMENTATION CONSTRAINTS

1. SQL commands for inserting entries into the database, updating the status of each entry,
making views of tables.
2. Database will be implemented using a centralized database management system
Thus the application will be provide information everywhere in the world.

2.6 USER DOCUMENTATION

A user manual is required as part of the project deliverables. Complete documentation

regarding design, implementation, testing and on-going maintenance of the device will be
developed by the end of the project.

2.7 ASSUMPTION DEPENDENCIES:

Let us assume that this is the online examination system and it is used in the following
application:

3. SYSTEM FEATURES

DESCRIPTION and PRIORITY

The online examination system maintains information on tests, students, administrator and
various notices. Of course, this project has a high priority because it is very difficult to travel
across institutions to give examinations without prior reservations.

CLIENT/SERVER SYSTEM:

The term client/server refers primarily to an architecture or logical division of

responsibilities, the client is the application (also known as the front-end), and the server is
the DBMS (also known as the back-end).

A client/server system is a distributed system in which,

 Some sites are client sites and others are server sites.
 All the data resides at the server sites.
 All applications execute at the client sites.

4. EXTERNAL INTERFACE REQUIREMENTS

4.1 USER INTERFACES

 Front-end software: asp.net version

 Back-end software: SQL

4.2 HARDWARE INTERFACES

 Any computer device with Windows, Android, Linux or iOS.

 A browser which supports CGI, HTML & Javascript.

4.3 SOFTWARE INTERFACES

Following are the software used for the online examination system.
Software used Description
Operating System The project is platform independent. It can
run on any device and support any operating
system.
Database We have used the MySQL database as other
databases such as ORACLE are heavy and
large to host them on the server. The MySQL
database will store all the data from the
website.
ASP.net We have chosen ASP.net to implement our
project. ASP.net has various built in
functionalities that must be done manually in
PHP OR JSP. It is comparatively used for
small data but the efficiency and speed is
gradually increased.
JavaScript Javascript makes the webpage dynamic and
user friendly. It is compatible with ASP.net.

4.4 COMMUNICATION INTERFACES

This project supports all types of web browsers. We are using simple electronic forms for the
filling information, attempting tests, etc.

5. OTHER NONFUNCTIONAL REQUIREMENTS

5.1 PERFORMANCE REQUIREMENTS

These are some of the use cases for our website.

1.Administrator - database:
2. Database – Database:
3.Student – Database:

4. Teacher-database:
A) E-R DIAGRAM

The E-R Diagram constitutes a technique for representing the logical structure of a database
in a pictorial manner. This analysis is then used to organize data as a relation, normalizing
relation and finally obtaining a relation database.

 ENTITIES: Which specify distinct real-world items in an application.

 PROPERTIES/ATTRIBUTES: Which specify properties of an entity and
relationships.
 RELATIONSHIPS: Which connect entities and represent meaningful dependencies
between them.
 
The diagram shows the ER diagram of airline database

B) NORMALIZATION:
The basic objective of normalization is to reduce redundancy which means that information is
to be stored only once. Storing information several times leads to wastage of storage space
and increase in the total size of the data stored.
If a database is not properly designed it can give rise to modification anomalies. Modification
anomalies arise when data is added to, changed or deleted from a database table. Similarly, in
traditional databases as well as improperly designed relational databases, data redundancy
can be a problem. These can be eliminated by normalizing a database.
Normalization is the process of breaking down a table into smaller tables. So that each table
deals with a single theme. There are three different kinds of modifications of anomalies and
formulated the first, second and third normal forms (3NF) is considered sufficient for most
practical purposes. It should be considered only after a thorough analysis and complete
understanding of its implications.

5.2 SAFETY REQUIREMENTS

If there is extensive damage to a wide portion of the database due to catastrophic failure, such
as a disk crash, the recovery method restores a past copy of the database that was backed up
to archival storage (typically tape) and reconstructs a more current state by reapplying or
redoing the operations of committed transactions from the backed up log, up to the time of
failure.

5.3 SECURITY REQUIREMENTS

Security systems need database storage just like many other applications. However, the
special requirements of the security market mean that vendors must choose their database
partner carefully.
5.4 SOFTWARE QUALITY ATTRIBUTES

 AVAILABILITY: The test paper should be available on the specified date and

specified time as many students must have enrolled for it.
 CORRECTNESS: The test should be taken in proper time duration and schedule and
the results should be accurate.
 MAINTAINABILITY: The software is maintained by the controllers and engineers
so as to maintain its quality.
 USABILITY: The test schedule should satisfy the maximum number of student
needs
 MOBILITY: The software must provide same performance and functionality
whenever accessed from any part of the world.