Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 10

NAME = ZEEL RABADIYA ENNO=190303105198

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 Project Scope..................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective.........................................................................................................................2
2.2 Product Features.............................................................................................................................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. System Features.......................................................................................................................3
3.1 System Feature 1.............................................................................................................................3
3.2 System Feature 2 (and so on)..........................................................................................................4
4. External Interface Requirements...........................................................................................4
4.1 User Interfaces................................................................................................................................4
4.2 Hardware Interfaces........................................................................................................................4
4.3 Software Interfaces.........................................................................................................................4
4.4 Communications Interfaces.............................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................5
5.1 Performance Requirements.............................................................................................................5
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................6
Appendix C: Issues List.................................................................................................................6
NAME = ZEEL RABADIYA ENNO=190303105198

INTRODUCTION
Online Quiz Examination System is Multiple Choice Questions Based
Examination system. It provides an easy to use environment for both test
conductors and students appearing for Examination. The main objective
of online Quiz Examination is to provide all the features that an
examinatioin System must have,with the “interfaces that don’t scare its
users!”

1. Purpose: 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.

2. Scope: The website to conduct online examination is “Online


Examination”. This website provides facility to institutes to conduct
online exams by providing a unique id to each institute. The
institute provides questions along with positive and negative marks.
Institute also enters the list of eligible students. All the information
entered can be later edited by the institute.

3. Document Conventions: The following are the list of conventions


and acronyms used in this document and the project as well:
 Administrator: A login id representing a user with user
administration privileges to the software
 User: A general id assigned to user
 Client: intended users for the software

4. References:
This web application has been prepared on the basis of discussion
with Team members and also taken information from following
books & website1
 www.google.com
 www.wikipedia.org
NAME = ZEEL RABADIYA ENNO=190303105198

Overall Description
 In Online examination system institute can register to conduct an online
test and view the records later. Students can give the test and their
respective records, which include their marks for each test given by
them, will be maintained separately. No student can take a particular
exam more than once.

1. Product Perspective:
The Online Examination System is a package to be used by Examiners
to improve the efficiency of the process of taking the examination. The
Online Examination System to be developed benefits greatly the
members and the people taking examination.
The Various Stages in the site as follows: -
 Login
 System Overview
 Test
 Result
Login: This window offers the user two choices for logging into the system
according to the present privileges - Candidate login and Administrator login.
The candidate login will take the user to the user profile. The Administrator
Login will take the user to the administrator profile.
System Overview: This window can only be accessed by the administrator. It
allows the administrator to add and edit exams.
Test: This window contains all the exams candidate can give. All these exams
are organized according to the categories they fall in. The test window will be
different for students and corporate employees.
Result: This window displays the result of exams the candidate has just
appeared. This data will be saved and displayed in the user profile. If the score
is in top 10, the result will also be displayed in the rankings area of result
window
NAME = ZEEL RABADIYA ENNO=190303105198

2. Product Features

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.

3. User Classes and Characteristics

The various users of this app are classified into two types: -
- Administrator
- Candidate: - Student
This app requires the user to have characteristics such as the user should be
able to communicate and write in English and should have previous experience
of giving an online exam.

4. Operating Environment

This app is internet based so it will run in any operating system with internet
access through a web browser

5. Design and Implementation Constraints

The candidate is allowed to give the exams any number of times, until specified
otherwise by the administrator while building the test. While giving the exam
NAME = ZEEL RABADIYA ENNO=190303105198

the candidate is given only a set amount of time and the remaining time should
be displayed, after which the exam should close and display the result.

6. Assumptions and Dependencies

Assumptions and dependencies:


-It is assumed that the user has basic knowledge of the system (i.e., he/she is
not a first-time user) as any action by the user is considered valid during an
examination.
- It is assumed that the data entered by the user while registering is true.
- It is assumed that the candidate does not cheat during the exam as there are
no supervisors around to monitor.
NAME = ZEEL RABADIYA ENNO=190303105198

SYSTEM FEATURES
1. Functional Requirements
Functional requirements are nothing but the services provided by the system to
its end users.
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 student will logon to the software and view his marks
with the grade awarded. He can also check his previous semester marks and his
details.

Examiner module: The database is prepared & loaded into the software.
Selection for semester can be done language wise by the examiner.

Administrator module: The administrator collects all the marks and results
after successful analysis and sends to the headquarters as and when required
NAME = ZEEL RABADIYA ENNO=190303105198

External Interface Requirements

1. User Interface

•Registration Screen: Various fields available on this screen will be:


-Login Name
-Email Id
-Password
•Login Screen: Fields available on this screen are:
-Login Name
-Password

2. Hardware Interfaces

Screen resolution of at least 800X600 is required for proper and complete


viewing of screens. Higher resolution will be accepted.

3. Software Interfaces

-Any windows-based operating system.

-Mongo dB Server Database


-Php and JavaScript

4. communications Interfaces

NONE
NAME = ZEEL RABADIYA ENNO=190303105198

Nonfunctional Requirements

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

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. 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
NAME = ZEEL RABADIYA ENNO=190303105198

 Communication needs to be restricted when the


application is validating the user or license. (i.e., using https).

4. Software Quality Attributes

The Quality of the System is maintained in such a way so that it


can be very user friendly to all the users.

The software quality attributes are assumed as under:

1)Accurate and hence reliable.

2) Secured.

3) Fast speed.

4) Compatibility.

1. Administrator has a

privilege to create, modify and


NAME = ZEEL RABADIYA ENNO=190303105198

delete the marks,percentage


and other
2. 1.1. Document
Conventions
3. The following are the list of
conventions and acronyms
used in this
4. document and the project as
well:
5. Administrator: A login id
representing a user with user
administration
6. privileges to the software
7. User: A general login id

assigned to users
Client: Intended users for the
8. 

softwareDocument Conventions:

You might also like