INTRODUCTION

Online Examination itself represents the examination through the internet.

This project will help the university/ Institution to evaluate the question has
multiple options with one correct answer. This project contains two types of
question viz. subjective and objective. Students have to write the descriptive
answer for the subjective question will be randomly generated. It would be
evaluated automatically i.e. by the system.

This project helps the management to conducting online examination and

save recourse. The university/Institution can conduct the online examination and
announce the status or result in a few data. The examination department is
responsible for the marinating of question paper and it would be completely secure.
Online examinations, sometimes referred as e-examinations, are the examinations
conducted through the internet or in an intranet (if within the Organization) for a
remote candidate(s). Most of the examinations issue results as the candidate finish
the examination, when there is an answer processing module also included within
the system. These examinations are conducted as open-book t y p e examinations.
Candidate is given a limited time to answer the questions and after the time expiry
the answer paper is disabled automatically and answers is sent to the examiner. The
examiner will evaluate answers, either through automated process or manually and
the results will be sent to the candidate through email or made available in the web
site

********************

19
 System Analysis

Requirements analysis is a software engineering task that bridges the

gap between system level requirements engineering and software design.
Requirements engineering activities result in the specification of softwares
operational characteristics (function, data and behavior), indicate softwares
interface with other system elements, and establish constraints that software must
meet. The most commonly used requirements technique is to conduct a meeting or
interview. The first meeting between a software engineer (the analyst) and the
customer can be likened to the awkwardness of a first date between two
adolescents. Neither person knows what to say or ask; both are worried that they
do say will be misinterpreted; both are thinking about where it might lead (both
likely have radically different expectations here); both want to get the thing over
with, but at the same time, both want it to be a success.

Gause and Weinberg suggest that the analyst start by asking CONTEXT-
FREE QUESTIONS. That is, a set of questions that will lead to a basic
understanding of the problem, the people who want a solution, the nature of the
solution that is desired, and the effectiveness of the first encounter itself.

The goal of the requirements gathering activity is to collect all relevant

information from the customer regarding the product to be developed with a view
to clearly understanding the customer requirements and weeding out the
incompleteness and inconsistencies in these requirements. The requirements
analysis activity is begun by collecting all relevant data regarding the product to be

19
developed from the users of the product and from the customer through interviews
and discussions.

Design Pattern

This software based on concept of the Model View Controller (MVC) design
pattern. View renders the data from the Model in response to the request made to
the model by controlled events made by user interaction.
Model View Controller is a design approach to separate the application object
model from GUI, originally invented around 80s. Then later on it has become a
widely accepted common design pattern. The main objective behind this pattern is
to decouple the view of the data (presentation layer) from the actual data
processing so that the same model can be used for various views. This is achieved
by using three different types of objects that interact with each other in loosely
coupled manner with their discreet set of tasks.

These three objects are known as Model, View and Controller :-

VIEW:

View is the graphical data presentation (outputting) irrespective of the real data
processing. View is the responsible for look and feel, some custom formatting,
sorting etc. View is completely isolated from actual complex data operations. For
example, Online product catalog view is completely separated from database
connection, query, tables etc. It simply gets final row-data from the model and puts
some cosmetics and formatting before displaying it in browser. View provides
interface to interact with the system. The beauty of MVC approach is that it
supports any kind of view, which is challenging in todays distributed and multi-

19
platformenvironment. A MVC model can have multiple views, which are
controlled by controller. View interface can be of WEB-FORMS, HTML,
XML/XSLT, XTML, and WML or can be Windows forms etc.

MODEL:

Model is responsible for actual data processing, like database connection, querying
database, implementing business rules etc. It feeds data to the view without
worrying about the actual formatting and look and feel. Data provided by Model is
display-neutral so it can be interfaced with as many views without code
redundancy; this eases your code maintenance and reduces bugs and allows code
-reuse at good extent. Model responds to the request made by controllers and
notifies the registered views to update their display with new data.

19
CONTROLLER:

Controller is responsible for Notice of action. Controller responds to the mouse or

keyboard input to command model and view to change. Controllers are associated
with views. User interaction triggers the events to change the model, which in turn
calls some methods of model to update its state to notify other registered views to
refresh their display.

19
Benefits:

Following are the few of the benefits of MVC design pattern.

Since MVC handles the multiple views using the same enterprise model it is
easier to maintain, test and upgrade the multiple system.
It will be easier to add new clients just by adding their views and controllers.

Since the Model is completely decoupled from view it allows lot of

flexibilities to design and implement the model considering reusability and
modularity. This model also can be extended for further distributed
application.

It is possible to have development process in parallel for model, view and

controller.

********************

Methodology Used

A software life cycle is the series of identifiable stages that a Software

product undergoes during its lifetime. The first stage in the life Cycle of any

software product is usually the feasibility study stage. The Subsequent stages are:

requirement analysis and specification, design, coding, testing and maintenance.

19
Each of these stages is called a life cycle Phase. A life cycle model represents all
the activities required to make a software product transit through its life cycle
phases. It also captures the order in which these activities are to be undertaken. The
most strict life cycle model used is the Classical Life Cycle Model. However, in
any practical software development work, it is not possible to strictly follow the
classical waterfall model from every phase to its preceding phases.

M E T H O D O LO GY AD O PT E D

Structured system analysis techniques had been adopted for the analysis of
the algorithm and software development.
Structured system design techniques had been adopted for the design of the
algorithm and software development.
Prototyping model for initial implementation had been used for early testing
and module development.
Prototyping model had been used for the development of the Graphical User
Interface.

Incremental Model had been used for the development of the software.
Structured development life cycle had been used for this project.
PERT chart is the primary Tool used for system planning.
Project cost had been estimated as a function of comparing the cost of
similar available products, effort estimation on the project, resources
acquired for the project and COCOMO Model as the theoretical reference.

19
 Test plan was created to form the strategy of testing. This includes the
decision of testing techniques, decision of testing tools, and decision of
milestones when the testing will commence.
DFD

0-Level

Student exam
result

Admin
add question Online Exam

1 level

Student table

Enter the Get list

19
username
Of pwd
&

Password
 login
Student

Get

Verify user
name
&Pwd
Result
Display
Online
exam give

exam

1 level
Admin table

request Enter the login Get list

admin username
Of pwd
&

Password
check

19
 Verify user
name
&Pwd

Question &
add
answer database
question
& answer

DATA BASE DESIGN

19
19
19
19
SCREEN_SHOT

19
19
19
19
19
19
19
19
HOW CAN WE GET EMPLOYMENT THROUGH ONLINE SYSTEM

Today most of the exam is conducting online. So there is a great scope to

give a interface of online exam to those student who is preparing for
competitive exam.

For this , we have to open a center with minimum 5 computer and to buy a
online test like MP Police , Patwari , MP-PSC , IAS , IPS , IFS , NET , SET ,
CAT etc. , a student can know their preparation to give it.

*************

19