ONLINE EXAMINATION

SYSTEM
GUIDE SUBMITTED
BY
Himanshu kaushal

Ms Gurbrinder kaur
 SYNOPSIS
1. General description of the system under study

 Existing System is used in schools, colleges,

competitive exams, etc. In this the records of the
students are managed manually. Students have to
reach at the center to appear the exam. Sometimes due
to other problems they may not reach at stipulated
time.
 User Requirements
 Problems faced by existing system:
 Students find difficult to carry the books.
 They get bore of reading large books.
 Students get hesitated or feel shy of asking doubts to the
teacher/sir.
 Faculties have to manage all the data on paper which is risky.
 Establish the need of the new system
 The basic needs of the new system are as follows:
 Provides facility to conduct online examination worldwide.
 It saves time.
 It allows number of students to give the exam at a time and
displays the results as the test gets over.
 It also thereby helps in saving resources- both human and
natural.
 User can register, log in and give the test with his specific id, and
can see the results as well.
Objectives of the project
 Online Exams System fulfills the requirements of the
institutes to conduct the exams online. They do not
have to go to any software developer to make a separate
site for being able to conduct exams online. They just
have to register on the site and enter the exam details
and the lists of the students which can appear in the
exam. Students can give exam without the need of
going to any physical destination. They can view the
result at the same time. Thus the purpose of the site is
to provide a system that saves the efforts and time of
both the institutes and the students.
 METHODOLOGY
 The Waterfall Model was first Process Model to be introduced. It is also
referred to as a linear-sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each phase must be completed
before the next phase can begin and there is no overlapping in the phases.
Waterfall model is the earliest SDLC approach that was used for software
development.
 The waterfall Model illustrates the software development process in a linear
sequential flow; hence it is also referred to as a linear-sequential life cycle
model. This means that any phase in the development process begins only if
the previous phase is complete. In waterfall model phases do not overlap.
 Waterfall model design: Waterfall approach was first SDLC Model to be
used widely in Software Engineering to ensure success of the project. In
"The Waterfall" approach, the whole process of software development is
divided into separate phases. In Waterfall model, typically, the outcome of
one phase acts as the input for the next phase
 PROBLEM DIFINITION
Waterfall model design: Waterfall approach was
first SDLC Model to be used widely in Software
Engineering to ensure success of the project. In "The
Waterfall" approach, the whole process of software
development is divided into separate phases. In
Waterfall model, typically, the outcome of one phase
acts as the input for the next phase sequentially.
Following is a diagrammatic representation of
different phases of waterfall model.
 SYSTEM REQUIREMENT
SPECIFICATION
 Purpose: A software requirements specification (SRS) is a
comprehensive description of the intended purpose and
environment for software under development. The SRS fully
describes what the software will do and how it will be
expected to perform. An SRS minimizes the time and effort
required by developers to achieve desired goals and also
minimizes the development cost. A good SRS defines how an
application will interact with system hardware, other
programs and human users in a wide variety of real-world
situations.
 System Requirement Specification: This section provides
software requirements to a level of detail sufficient to enable
designers to design the system and testers to test the system.
 (a) Institute Registration Screen: Various fields available on this screen will be:
 Login Name
 Email Id
 Password
 (b) Institute Login Screen: Fields available on this screen are:
 Login Name
 Password
 (c) Entering Questions: Various Fields are:
 Questions
 Options
 Correct Answer
 (d) Exam Details Screen: Various Fields are:
 Exam Name
 No. Of Questions
 Time Limit
 +ve, -ve Marks
 Passing Marks
 (e) Student List Screen: Various Fields are:
 Student ID
 Student Name
 (f ) Student Login Screen: Various Fields are:
 Student ID
 Student Name
 Institute ID
 (g) Student Taking Exam Screen: Various Fields are:
 Display Of Question With Options
 Control Buttons To switch questions
 (h) Result Displaying Screen: Various Fields are:
 No. Of Correct Questions
 No. Of Incorrect Questions
 No. Of Unattempted Questions.
 Total Marks.
 Result(Pass/Fail)
 2.2 Overall description
 2.21 Product Perspective:
 The application will have a user friendly and menu based
interface. Following screens will be provided.
 A login screen for entering the username, password will be
provided. Access to different screens will be based upon the user.
 There is a screen for displaying information regarding entries to
be made by institutes.
 There is a screen for displaying information regarding entering
student list for the particular exam.
 There is a screen for displaying information menu regarding
what options the institutes will select while filling entries.
 There is a screen for displaying exam details to the students
when they are taking exams.
 There is a screen for taking exam for the students.
 There is a screen for displaying of results of students after taking
the exam.
 Product features
 The website will allow access only to authorized users
with specific roles (Administrator- maintains the
website, Institutes-Register to conduct the exams,
Students-Give the exams online)
 A summary of the major functions that the website
will perform:
Provide facility to institutes to register to conduct a
online test.
Institutes can enter the number of questions, +ve, -ve
marks, questions and answers and the list of eligible
students.
Students can login and give the tests.
 Functional requirements:
 Number of Modules: After careful analysis the system has been
identified to have the following modules:
 Home – Home page of Online Examination site.
 Login – Student can login to start test.
 Register – From this page new student can register for test.
 Student Page – Previously saved test results can be viewed here and
other links like Edit Profile, Logout, and Change Password.
 Edit Profile – Student can edit registration information like personal
details, address, contact no, display name.
 Change Password – Currently logged user can change his password
from this link.
 Logout – User logged out from this site.
 Test – System randomly select questions from question bank and
display one by one to the student.
 Results – After completing the examination student can view results.
 Question Bank - Admin user can manage question bank from web
interface.

Non-functional requirements
Hardware requirements:
 Computer (CPU)
 Intel Pentium4 or higher
 Memory
 At least 2 GB
 Hard Disk
 40 GB
 Display
 Super VGA (800 600) or higher-resolution monitor with
256 colors
 Input Device
 Keyboard , Mouse
 Software requirements:
Front End
HTML, CSS
Back End
SQL, PHP, JavaScript
Operating System
Windows 7
 Security: Every user who wants to use our content management system
application and the website has to register himself to our system else he/she
can’t access the system. Only user having a valid or authorized user name
and password can access the system. We also providing security feature by
limiting the access of user to the system by categorizing them into different
user type, each user type have their own access level to the system that is
End User can’t do what Administrator are allow to do.
 Efficiency: We are providing a better and efficient way of interaction
to user. A user can now interact or communicate with our new system by
our newly developed Content Management System, by using this facility
user can easily understand what is required by system or he will also feel
friendlier while interacting with system. Our system is also helpful for those
people who are not part of the trust but if they are working as a new
member or a third party they can easily understand the system.
 Usability: Our Content Management System is quite easy to use as it
has been made for the users who aren’t much educated, we are providing
simple and user friendly interfaces through which users can interact with
our system. In case of our system users aren’t required to have a sound
knowledge unlike other system, a user with basic knowledge of the trust can
interact with the proposed system easily.
 SYSTEM DESIGN

 Physical design
 Systems design implies a systematic approach to the design of a system. It may take a bottom-up or top-
down approach, but either way the process is systematic wherein it takes into account all related
variables of the system that needs to be created—from the architecture, to the required hardware and
software, right down to the data and how it travels and transforms throughout its travel through the
system. Systems design then overlaps with systems analysis, systems engineering and systems
architecture.
 The physical design relates to the actual input and output processes of the system. This is laid down in
terms of how data is input into a system, how it is verified how it is processed, and how it is displayed as
output. In Physical design, following requirements about the system are decided:
 (a) Input requirement,
 (b) Output requirements,
 (c) Storage requirements,
 (d) Processing Requirements
 Use Case Diagram: Use case diagrams are considered for high level requirement analysis of a system. So
when the requirements of a system are analyzed the functionalities are captured in use cases. So we can
say that uses cases are nothing but the system functionalities written in an organized manner. Now the
second things which are relevant to the use cases are the actors. Actors can be defined as something that
interacts with the system. The actors can be human user, some internal applications or may be some
external applications. So in a brief when we are planning to draw a use case diagram we should have the
following items identified.
USE CASE DIAGRAM
 DATA FLOW DIAGRAM
 Data Flow Diagram: Data Flow Diagrams (DFD)helps us in
identifying existing business processes. It is a technique we
benefit from particularly before we go through business process
re-engineering. At its simplest, a data flow diagram looks at how
data flows through a system. It concerns things like where the
data will come from and go to as well as where it will be stored.
But you won't find information about the processing timing.

 (a) Level 0 DFD shows an overview of the system where the
input entities includes Admin and Student providing
their respective inputs to obtain details and to authorize output.
O LEVEL DFD
1 LEVEL DFD
2 LEVEL DFD
 Entity Relationship (ER) diagrams are drawn when designing a database system,
After the systems specification, an ER diagram is drawn showing the conceptual
design of the database, this diagram shows the type of information that is to be
stored in the system and how these information associate with each other.
 Entity: An entity may be defined as a thing which is recognized as being capable of
an independent existence and which can be uniquely identified. By composite
information.
 Attributes: Attributes define the properties of a data object and take on one of three
different characteristics.
 Relationship: A relationship captures how two or more entities are related to one
another.
 Cardinality: The data model must be capable of representing the number of
occurrences of objects in a given relationship. The cardinality of an object-
relationship pair is:

 One-to-One (1:1): An occurrence of object ‘A’ can relate to one and only one
occurrence of object ‘B’ and an occurrence of ‘B’ can relate to only one occurrence of
‘A’.
 Many-to-Many (M: N):An occurrence of object ‘A’ can relate to one or more
occurrences of ‘B’, while an occurrence of ‘B’ can relate to or more occurrences of ‘A’.
 One-to-Many (1: N): One occurrence of object ‘A’ can relate to one or many
occurrences of object ‘B’ but an occurrence of ‘B’ can relate to only one occurrence of
‘A’.
E-R DIAGRAM
FRONT PAGE
LOGIN PAGE
LOGIN PAGE FOR ADMIN
PAGE FOR ADDING QUESTIONS IN A
DATABASE