A Project Report

On

Online Examination System

(Department of Computer Science & Engineering)

Submitted by:
1. Anik Barua
2. Tarequl Islam
3. Mohiuddin Munna
Submitted to:

Assistant Professor, Tanjim Mahmud

Submitted Date: 15 February, 2020

 1

ACKNOWLEDGEMENT

The satisfaction that accompanies the successful

completion of any task would be incomplete without
the mention of people whose ceaseless cooperation
made it possible, whose constant guidance and
encouragement crown all efforts with success. We
are grateful to our project guide Mr. Tanjim
Mahmud for the guidance, inspiration and
constructive suggestions that helpful us in the
preparation of this project.

Anik Barua
Tarequl Islam
Mohiuddin Munna
 2

ABSTRACT

Online Examination System is web based

application for students, organizations, coaching
institutes which can be customized as per the
requirements and technical evaluation. Online Quiz
Examination System not only replace paperwork but
also releases the workload of faculty. It fulfills the
requirements of the institutes to conduct the online
exams. Students can give exam without the need of
going to any physical destination. They can view the
result at the same time. So that the purpose of the
site is to provide a system that saves the efforts and
time of faculty. The user with minimum knowledge
about computer can be able to operate the system
easily. The system also produces brief result
required by the management.
 CONTENTS 3
ACKNOWLEDGEMENT…………………………………... 01
ABSTRACT ………………………………………………… 02
Chapter 1. Introduction………………………………………………...04
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . ……..04
1.2 Why Online Examination System…………………...05
1.3 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . …...05
1.4 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . …...06
1.5 Disadvantage of existing System . . . . . . . . . . . …...07
1.6 Objective of proposed system . . . . . . . . . . . . . . ……07
Chapter 2: Process model…………………………………(08-11)
Chapter 3: Software Requirement Specification…………….....12
3.1 Proposed. . . . . . . . . . . . . . . . . . . . . . . . . ………….. …12
3.2 Proposed System………………………………………13
3.3 Characteristic of the Proposed System………………..14
3.4 Specific Requirement . . . . . . . . . . . . . . . . . . . .
……...15
3.5 User Requirement . . . . . . . . . . . . . . . . . . . . . . .
……...16
3.6 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
……..16
3.7 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . ………17
Chapter 4: Design ………………………………………………………..… 18
Chapter 5: Testing and Validation……………………………….….. 19
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .... (19-
20)
5.2 Testing . . . . . . . . . . . . . . . . . . ……………. . … (20-
22)
5.3 Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . …….23
5.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . …….
23
Chapter 6: Implementation…………………………………….24
6.1 Exam Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . ….24
6.2 Student Aspect. . . . . . . . . . . . . . . . . . . . . . . …… …..25
6.3 Administrator Aspect. . . . . . . . . . . . . . . . . . . . …….25
 6.4 Sample Code…………………………………… (26-30)
6.5 Snap shots of Online Examination System......... (31-45)
6.6 Conclusion…………………………………………...46

Chapter: 1

INTRODUCTION

1.1 Introduction:
Online examination is conducting a test online to measure
the knowledge of the participants on a given topic. In the
olden days everybody had to gather in a classroom at the
same time to take an exam. It is a web based online
examination solution for students, organizations, coaching
institutes which can be customized as per the
requirements.
 5

1.2 Why Online Examination System:

 Stored Repository of exams

 General problem with time for students
 Auto grading
 Flexible
 Time Saver
 Security

1.3 Scope:

 It is cost effective and popular means of mass-

evaluation system. The faculty prepares the tests
and questions for each exam.
 The candidates can login through the client
computers with their roll number given to them
and can take the exam.
  The questions are shuffled in a random order so
that possibilities for getting questions in the same
order for the students who are beside, is very less.

1.4 Existing system:

The Existing system of conducting

examination process is manual. Existing system
is a large man power process and is difficult
to implement it at different platform. It has so
many problems. So we introduce an OLES
system, which is fully computerized. Existing
system is a large man power process and is
difficult to implement.
 7

1.5 Disadvantages of existing system:

 The existing systems are very time consuming.

 It is difficult to analyze the exam
manually.
 Results are not precise as calculation and
evaluations are done annually.
 Result processing after summation of exam
takes more time as it is done manually.

1.6 Objective of proposed system:

 Economic feasibility
 Time Flexibility
 Technical feasibility
 User-friendly interface
 Eco-Friendly System
 8
Chapter: 2
Process model
We will do this project by waterfall process model.
Waterfall model is a software model that can be adapted
to produce the software. The main thing is that if software
team adapt the waterfall model for the production of
software than a proper detailed planning and proper
accurate work is needed in every phase of the waterfall
model.

Waterfall model:
 9

1. Requirement gathering and analysis:

In this phase, all the detailed requirements are gathered
from the customer who wants to develop the software.
After getting the requirements, system analyst analyses
the requirements that whether requirement can be fulfilled
or not. If customer requirements can be fulfilled than
whether these requirements are fulfilled within budget or
out of the budget. After this software team moves to the
design phase.
2. Design:
Before starting the design, software team completely
gathered all the detailed requirement from the customer
and requirement analysis is also completed. In the design
phase, software team designs the software. Different
diagrams are also drawn in this phase for software. Some
of these are used the class diagram, activity diagram, data
flow diagram, state transition diagram etc.
When a team is completely satisfied with the proposed
design, then move to the next phase.

10

3. Implementation:
Before starting implementation, software team completely
design the system and now ready to develop the system.
Programs are written and all the designed is converted
into computer programs, collectively called software.
When the team is completely satisfied with the developed
software, then move to the next phase.
4. Testing:
Before starting testing, software team
completely developed all the software. Now its time to
test the software by using different software testing
techniques. Most common are white box, black box, and
gray box testing techniques.
When the team is completely satisfied with the testing and
pass the software for implementation, then move to the
next phase.

11

5. Deployment:
Before starting deployment, software team completely
tested all the software. Now it’s time to install or deploy
the software in its working environment.

6. Maintenance:
When software is deployed, there can be many bugs,
faults or new updating needed. Maintenance includes
debugging and new feature addition.

12

Chapter: 3

Software Requirement Specification

3.1 Proposed:
The main objective of the Online Examination
System is that it helps educational institutions and
corporate world to conduct exams to any
number of candidates at a time, in an automated
manner. It reduces the time consumption and
workload that exist in the current system of
examination. It also helps in storing the record of
each examination and the results are also stored in
the system. This makes the searching of the records
easier than the existing system.

13

3.2 Proposed System:

 14

3.3 Characteristic of the Proposed System:

The online test created for taking online test has following
features:

 In comparison to the present system the proposed

system will be less time consuming and is more
efficient.
  Analysis will be very easy in proposed system as it is
automated.

 Result will be very precise and accurate and will be

declared in very short span of time because
calculation and evaluations are done by the simulator
itself.

 The proposed system is very secure as no chances of

leakage of question paper as it is dependent on the
administrator only.

 The logs of appeared candidates and their marks are

stored and can be backup for future use.

15
3.4 Specific requirements:
2.2.1 Software requirement:
 Operating System: Windows XP and
others.
 Front End: HTML, CSS, JavaScript.
 Back End: PHP, MySQL.
 Software Requirement: XAMPP
SERVER.
  Browser: Mozilla Firefox, Google
Chrome and Others.

2.2.2 Hardware requirement Client Side:

 Browser: Any browser.

 Processor: Pentium 2.0 and above.
 RAM: 500 MB and above.

2.2.3 Server Side:

 Processor: Pentium and above.

 RAM: 512 MB and above.
 Hard disk space: 4 GB.

16

3.5 User Requirements:

Every user should be:

 Comfortably work with computer.
 He must also have basic
knowledge of English.
3.6 Constraints:

 Graphical user interface is only in English.

 Enrolment ID and password is used for
identification of user and there is no facility
for guest.
 Only registered users will be authorized to
use the services.
 Limited to HTTP or HTTPS.
 This system is working for single
server.

17

3.7 Conclusion:
In this phase, we understand the software
requirement specifications for the system .We
arrange all the required components to develop
the project in this phase itself so that we will
have a clear idea regarding the requirements
before designing the project. Thus we will
 proceed to the design phase followed by the
implementation phase of the project.

18

Chapter: 4

Design

4.1 E-R Diagram:

 19

Chapter: 5

Testing and Validation

5.1 Introduction:
Software testing is a critical element of software
quality assurance and represents the ultimate review of
specification, design and coding. In fact, testing is the one
step in the software engineering process that could be
viewed as destructive rather than constructive.

A strategy for software testing integrates software test

case design methods into a well-planned series of
steps that result in the successful construction of
software.

Testing is the set of activities that can be planned in

advance and conducted systematically. The underlying
motivation of program testing is to affirm software
quality with methods that can economically and
effectively apply to both strategic to both large and small-
scale systems.
20

The following are the Testing Objectives:

 Testing is a process of executing a program with
the intent of finding an error.
 A good test has a high probability of finding an
as yet undiscovered error.
 A successful test is one that uncovers an as yet
undiscovered error.

5.2 Testing:
The objective is to design tests that
systematically uncover different classes of errors
and do so with a minimum amount of time and
effort. Testing cannot show the absence of defects, it
can only show that software defects are present.
 21

5.2.1 Integration Testing:

Modules integrated by moving down the
program design hierarchy. Can use depth first or breadth
first top down integration verifies major control and
decision points early in design process. Top-level
structure tested most. Depth first implementation allows a
complete function to be implemented, tested and
demonstrated. And does depth first implementation of
critical functions early. Top down integration forced (to
some extent) by some development tools in programs
with graphical user interfaces. Begin construction and
testing with atomic modules (lowest level
modules).Bottom up integration testing as its name
implies begins construction and testing with atomic
modules. Because modules are integrated from the bottom
up, processing required for modules subordinate to a
given level is always available and the need for
stubs is eliminated.

5.2.2 Validation Testing:

 Validation testing is aims to demonstrate that the
software functions in a manner that can be reasonably
expected by the customer. This tests conformance the
software to the Software Requirements Specification.
22

5.2.3 Alpha and Beta Testing:

Alpha testing:
It’s an acceptance testing conducted by the
developed environment.
Beta Testing:

It’s an acceptance testing conducted by the

multiple customers in the customer environment.

5.2.4 System Testing:

Software is only one component of a system.
Software will be incorporated with other system
components and system integration and validation
test performance.
 23

5.3 Validation:
Validation aims to demonstrate that the software
functions in a manner that can be reasonably expected
by the user. An experiment has done for checking
the consistency for the user requirements regarding
the username and password which should be validated
through the server and the username and password
should be matched.

5.4 Conclusion:
In this way we also completed the testing phase of
the project and ensured that the system is ready to go live.
Thus we developed a system that provides a paperless
examination.
 24

Chapter: 6

Implementation

6.1 Exam Module:

Examination process:

 Login to the online examination system.

 Attend Test
 Submit

The form of questions in test page:

 Multiple choice questions

  The questions are selected at random

25

6.2 Student Aspect:

 Requesting registration.
 Logging into the system.
 Edit user information.
 Selecting the test.
 Appearing for the examination.
 Printing the result at the end of the examination.
 Reviewing the given responses

6.3 Administrator Aspect:

 Taking backup of the database.

 Editing/Deleting/Creating the database.
 Changing the password.
 Logging into the system.
  Accepting registrations of candidates.
 Creating a test.
 Posting questions in the above test.
 Posting multiple options to respective question.
 Marking correct answer within the given options.
26
6.4 Sample Code:

1. index.php

<?php include 'inc/header.php'; ?>

<?php
Session::checkLogin();
?>

<div class="main">
<h1>Online Exam System - User Login</h1>
<div class="segment" style="margin-right:30px;">
<img src="img/rmstu.png"/>
</div>
<div class="segment">
<form action="" method="post">
<table class="tbl" style="padding-left: 60px; padding-top: 65px">
<tr>
<td>E-mail:</td>
<td><input name="email" id="email" type="text"
required="" placeholder="Enter Email"></td>
</tr>
<tr>
 <td>Password:</td>
<td><input name="password" id="password"
type="password" required="" placeholder="Enter Password"></td>
</tr>
<tr>
<td></td>
27

<td class="button_class"><input type="submit"

id="loginSubmit" value="Login">
</td>
</tr>
</table>
</form>

<br/>
<p style="font-size: 16px; text-align: center;">Are You a New User?
<a style="text-decoration: none" href="register.php">Register</a>
Here</p>
<br/>
<p style="font-size: 14px; text-align: center;"><span
class="empty" style="display: none">Fields Must Not be Empty!
</span></p>
<p style="font-size: 14px; text-align: center;"><span class="error"
style="display: none">Email or Password Not Matched!</span></p>
<p style="font-size: 14px; text-align: center;"><span
class="disable" style="display: none">User ID Disabled From Admin!
</span></p>

</div>

</div>
<?php include 'inc/footer.php'; ?>
 28
2. Database.php
<?php
$filepath = realpath(dirname(__FILE__));
include_once ($filepath.'/../config/config.php');
Class Database{
public $host = DB_HOST;
public $user = DB_USER;
public $pass = DB_PASS;
public $dbname = DB_NAME;

public $link;
public $error;

public function __construct(){

$this->connectDB();
}

private function connectDB(){

$this->link = new mysqli($this->host, $this->user, $this->pass, $this->dbname);
if(!$this->link){
$this->error ="Connection fail".$this->link->connect_error;
return false;
}
}

// Select or Read data

public function select($query){
$result = $this->link->query($query) or die($this->link->error.__LINE__);
if($result->num_rows > 0){
return $result;
} else {
return false;

}
29
}

// Insert data
public function insert($query){
$insert_row = $this->link->query($query) or die($this->link->error.__LINE__);
if($insert_row){
return $insert_row;
} else {
return false;
}
}

// Update data
public function update($query){
$update_row = $this->link->query($query) or die($this->link->error.__LINE__);
if($update_row){
return $update_row;
} else {
return false;
}
}

//Delete data
public function delete($query){
$delete_row = $this->link->query($query) or die($this->link->error.__LINE__);
if($delete_row){
return $delete_row;
} else {
 return false;
}
}

30

3. Config.php

<?php
define("DB_HOST", "localhost");
define("DB_USER", "root");
define("DB_PASS", "");
define("DB_NAME", "db_exam");
?>
 31

6.5 Snap Shots:

a. Administration Interface:

1. Admin Login Page: This is admin login page is

made For Security purpose that only Admin can Access &
modify to the Project.
 32

2. Admin Page:
 33

3. Manage User Page:

 34

4. Add Question Page:

 35

5. Question List Page:

 36

6. Viva Request Page:

 37

b. User Interface:

1. User Login Page: This is User login Form is made

For Security purpose that only Authenticated User only
Access in to the Project.
 38

2. User Registration Page:

 39

3. User Profile Page:

 40

4. Exam Page:
 41

6. Test Page:
 42

7. Question Page:
 43

8. Question Page:
 44

9. View Answer Page:

 45

10. Viva Page:

46
6.6 Conclusion:
Online Examination System (OLES) is a web application.
The key concept is to minimize the amount of paper and
convert all forms of documentation to digital form. It can
observe that the information required can be obtained
with ease and accuracy in the computerized system. The
user with minimum knowledge about computer can be
able operate the system easily. The system also produces
brief result required by the management.

47
THANK YOU