0 - Project Report
0 - Project Report
PROJECT REPORT
On
“ONLINE EXAM”
Of
SESSION: 2018-20
( Department of CS)
1
PREFACE
In its broadest sense project report is necessary to make the students of business school familiar
with the industrial environment prevailing in the world. To be competitive and work aggressive,
students need to know the policies, procedures and the trends going on in the present industrial
world.
2
S
This is to certify that Mr. ARVIND PATHAK , S/o Kaushal Kishore Pathak
, Roll No. 1817314901 student of MCA IV Semester (Batch 2018-20) of
this institution has done project report titled “Online exam”.
The project has been prepared and submitted by the above named in
fulfillment of the Master of Computer Application degree Programme
(MCA) as per the requirement of Abdul kalam Technical University,
Lucknow.
Date :
3
ACKNOWLEDGEMENT
I, sincerely wish to thank Dr. Ram Kishore Agrawal, Honorable chairman, Rajiv Academy for
Technology and Management, Mathura. We are obliged to the advice, encouragement tips and
timely suggestion provided by our program coordinator Mr. kanta Prasad Sharma .It is a
matter of great privilege to express our sincere thanks, gratitude and indebtedness to our guide
Mr. Sharad Singh and Miss Monika Singh for their valuable guidance and supervision
throughout the development of the project. It was really great to work with them. Their
guidance and impassionate support all around is really thankful. The time spent with them for
the development of the project was full of potential as well as knowledge. Their prospects of
motivation, discipline, timely discussions and tips along with the moral support as well as
confidence extended us certainly to make a great deal of learning. We want to express our
special thanks to our entire batch mates for fruitful discussions. We are also great full to all
others who helped us directly or indirectly in our work. We dedicate our project work to our
parents who have influenced us in more ways than they know.
4
DECLARATION
I, ARVIND PATHAK hereby declare that this project work report entitled “ONLINE
EXAM” submitted by me for the fulfillment of the degree of Master of Computer Application
from AKTU, Lucknow is a record of original work carried out by myself under the guidance of
Mr. Sharad Singh (Lect. of CS Dept.) and Miss Monika Singh of RATM, Mathura.
ARVIND PATHAK
1817314901
5
CERTIFICATE OF GUIDANCE
It is certified that ARVIND PATHAK have submitted the “ONLINE EXAM” as a project
report to the department of computer science for partial fulfillment of award of degree of
M.C.A from AKTU, Lucknow.
(Project Guide)
6
TABLE OF CONTENTS:
PREFACE
ABSTRACT
ACKNOWLEDGMENT
DECLARATION
CERTIFICATE
CETRTIFICATE OF GUIDANCE
7
TABLE OF CONTENTS:
CHAPTER : 1
Design constraints
Acceptance Criteria
CHAPTER : 2
SYSTEM ANALYSIS……….
Feasibility Study
Introduction
Software Requirement
Hardware Requirement
CHAPTER : 3
INTRODUCTION TO SQL
8
CHAPTER : 4
System Analysis
Methodology Adopted
Design Pattern
CHAPTER:5
Architecture
Login Module
Admin Module
User Module
ER-Diagram
DFD’s
CHAPTER : 6
STRUCTURAL CHART………
SIGNUP table
CATEGORY table
QUESTIION table
CHAPTER ; 7
SCREEN LAYOUTS…….
HOME
9
PROFILE SHOWING
CATEGORY SELECTION
QUIZ
RESULT
ADMIN
QUESTION ADDING
CATEGORY ADDING
CODING…..
Login
Admin Status
User Status
Quiz Status
CHAPTER : 8
TESTING…..
Testing Method
Test Case- 1
Test Case- 2
Test Case- 3
CHAPTER : 9
SYSTEM IMPLEMENTATION ….
10
SYSTEM MAINTENANCE….
FUTURE SCOPE
CHAPTER ; 10
BIBLIOGRAPHY…
11
CHAPTER : 1
INTODUCTION
TO
ONLINE EXAM
OF THE PROJECT
User-friendly system
User-friendly systems are not only needed for the creator, but also for participants.
“Intuitive” is key. One of the best examples is the software of the iPhone. It has a lot of
options, but is still something you can figure out without needing a manual. Of course, an
online examination system is different, but still has some similarities. Once an online
examination system is not user-friendly, creators and participants will move on to another
system. This is obviously something you don't want to happen.
Responsive design
A responsive design is an approach where the web designer wants to reach an optimal
web experience for a wide range of devices. A responsive site scales with the size of the
screen without sacrificing the text readability or usability of the user interface.
12
Offering several types of questions
Multiple choice, fill in the blanks and free text. These are the options you can use with our
online examination system. Having more than one options is necessary to check several
types of knowledge. Not all examination can be checked with multiple choice questions.
Do you want your exam for anyone or for a predefined group of users? The online exam can be
made for people who are invited to the exam and have to log in with a username and password.
If your exam is free for anyone, you can insert a link for making the exam.
Having to check all answers is very time-consuming. So, having the answers checked
automatically and instantly will eventually pay off. It’s less work for the creator of the exam
and participants don’t have to wait too long for getting the results of their exams. Catching two
birds with one stone .
Having the results and statistics is nice to get a whole overview of the performances.
Which users score best? On what kind of questions did users score low at? It’s all possible with
our tool. And know what’s even better? Administrators can export the results and statistics to an
Excel file.
13
. Introduction:
14
DESIGN CONTSSTRAIN
SOFTWARE CONSTRAINTS :-
HARDWARE CONSTRAINTS :-
15
Internet Connection Broadband (high-speed) Internet connection with a speed of 4 Mbps or
higher
Keyboard and a Microsoft Mouse or some other compatible pointing device
ACCEPTANCE CRITERIA
Before finally implementing the software at the user s site, the developer must
demonstrate that the system works on the source data and other information. The
developer will have to show through Test Cases that all the conditions and
requirements are satisfied.
16
CHAPTER : 2
SYSTEM-ANALYSIS
FEASIBLITY STUDY
Feasible study is a primary study which investigates the information need of user .The
resources requirements, cost and benefits of the instant-chat that is our proposed system.
It means to carry out the detailed study of the existing system, find out the problem related to
technical, chatting and economical field like cost by concerning the user of the study proposal
of the proposed system is accepted by user and admin.
17
Essence of proposed system are :-
The development of this project involves using .NET technologies, like windows form,
class files and user control.
Insertion of windows forms.
Adding and creating a classes file.
Developing and adding a user control.
This needs a detailed study of the proposed system, which is carried out by the following
technique :-
• Questionnaires
• Observations
This would help to have an in depth study of the existing system and understand the strength
and weakness and the requirement of the new proposed system.
Economic Feasibility -
Economic analysis is the most frequently used method for evaluating the effectiveness of a
candidate system. The process of identifying financial benefits. More commonly known as
cost/benefit analysis, the procedure is to determine the benefit. This is an ongoing effort that
improves in accuracy at each phase of the system life cycle.
Now is decided what can be done, what each will cost and what benefits can be expected to be
derived from each.
18
Technical Feasibility -
Technical feasibility centers on the existing system (hardware, software, etc.) and to what
extent it can support the proposed addition. This involves financial consideration to
accommodate technical enhancements. If the budget is a serious constraint, then the project is
judged not feasible. To select best tool among all.
Operational Feasibility –
People are inherently resistant to change, and computers have been known to facilitate change.
An estimate should be made of how strong a reaction the user
19
• Start preliminary investigation-The system analyst of each project team starts
preliminary investigation through different fact finding technique.
• Prepare the current system flowchart-After preliminary investigation; the analyst
prepare the system flowchart of the current system. The flowchart describes the general
working of the system in graphical way.
• Determine objective of the proposed system- The major objectives of the proposed
system are listed by each analyst and are discussed in the current system.
• Describe the deficiencies of the proposed system- On studying the current system
flowchart , the analysts identify and describes the deficiencies in the current system.
• Prepare the proposed system flowchart- After determining the major objectives of the
proposed system, the analysts prepare their system flowchart. System flowcharts of the
proposed system are compared with the current system.
• Determining the technical feasibility- The existing computer system(h/w or s/w)of the
concerned department is identified and their technical specification are noted down. The
analyst decides whether the existing systems are sufficient for the technical requirement
of the proposed system or not.
• Determine the operational feasibility-After determining the economic feasibility, the
analyst identify the responsible users of the system and hence determine the operational
feasibility of the project.
• Presentation of the feasibility analysis- During the feasibility study, the analysts also
keep on the feasibility report. At the end of the feasibility analysis, the feasibility
analysis report is given to the management along the oral presentation.
Feasibility analysis report is formal document for management use and is prepared for
system analyst during or after feasibility study. This report generally contains the following
sections.
• Covering letter- It is formally presents the report with brief description of the
project problem along with recommendations to be considered.
20
• Table of content- It lists the\section of feasibility study report along with their page
number.
• Overview- It present the overview of the project problem along with the purpose
and scope of the project.
• Description of the existing system- A brief description of the existing system along
with the purpose and scope of the project.
• System requirement- The system requirements, which are either derived from the
existing system or from the discussion with the users, are presented in this section.
• Development plan- It present a detailed plan with the starting and completion dates
for different phase of SDLC.
• Technical Feasibility finding- It present the finding of technical feasibility along
with recommendations.
• Costs and Benefits- The savings and benefits are highlighted to justify the
economic feasibility of this project.
• Operational Feasibility Finding- It present the finding of operational feasibility
along with the human resource requirements to implement the system.
21
SOFTWARE REQUIREMENT SPECIFICATION:
3.1 INTRODUCTION
The s/w requirement specification is produced at the culmination of the analysis task. The
function and performance allocated to s/w as part of the system engineering are redefined by
establishing a complete information description, a detailed functional description, are
representation by system behaviors, an indication of performance requirements and design
constraints, appropriate validation criteria, and other information pertinent to requirements. The
various sub levels classification of the specification is given below:
The introduction of the s/w requirement specification states the goals and objectives of the s/w,
describing it in the context of the computer-based system. Actually, the introduction may be
nothing more than the s/w scope of the planning document.
22
The information description provides a detailed description of the problem that the s/w must
solve. Information content, flow, and structure are documented. H/w, S/w, and human
interfaces are described for external system elements and internal s/w functions.
A description of each function required to solve the problem is presented in the Functional
Description. A processing narrative is provided for each function, design constraints are started
and justified, performance characteristics are stated, and one or more diagrams are included
graphically represent the overall structure of the s/w and interplay among s/w functions and
other system elements.
Validation Criteria is probably the most important and, ironically, the most often neglected
section of the Software Requirements Specifications. Yet, specification of validation criteria
acts as an implicit review of all other requirements.
• The project must contain a login form which will check wrong entries from the user.
• The project must also contain a registration form for the new entry and also validate
every input.
• The admin module must provide entire control on the system.
• Any valid employee can work on this system on the basis of provide rolls
• Proper authentication must be provided
• Must be secure because it provides the money transaction
The project starts with a login form. Only the valid users can run the project. All the users are
divided act. their roles and their corresponding details are stored in login table of the database.
The table keeps the record of the username and password of different accounts.
Database Backup facility is also there which is only for admin purpose.
23
Software Requirements:
• OS : Windows XP/Window 7.
• Technologies : C#
Hardware Requirements:
• RAM : 2 GB Min.
CHAPTER : 3
INTRODUCTION TO SQL-
What Is SQL?
SQL is a special-purpose language used to define, access, and manipulate data. SQL is
nonprocedural, meaning that it describes the necessary components (i.e., tables) and desired
results without dictating exactly how those results should be computed. Every SQL
implementation sits atop a database engine, whose job it is to interpret SQL statements and
determine how the various data structures in the database should be accessed to accurately and
efficiently produce the desired outcome.
INSERT
24
Adds data to a database.
UPDATE
Modifies data in a database.
DELETE
Removes data from a database.
MERGE
Adds and/or modifies data in a database. MERGE is part of the 2003 ANSI SQL standard.
SELECT
Retrieves data from a database.
Some people feel that DDL is the sole property of database administrators, while database
developers are responsible for writing DML statements, but the two are not so easily separated.
It is difficult to efficiently access and manipulate data without an understanding of what data
structures are available and how they are related; likewise, it is difficult to design appropriate
data structures without knowledge of how the data will be accessed. That being said, this book
deals almost exclusively with DML, except where DDL is presented to set the stage for
one or more DML examples. The reasons for focusing on just the DML portion of SQL include:
• DDL is well represented in various books on database design and administration as well
as in SQL reference guides.
• Most database performance issues are the result of inefficient DML statements.
Language Structure
SQL is a keyword based language. Each statement begins with a unique keyword. SQL
statements consist of clauses which begin with a keyword. SQL syntax is not case sensitive.
• names -- names of database elements: tables, columns, views, users, schemas; names
must begin with a letter (a - z) and may contain digits (0 - 9) and underscore (_)
25
INTRODUCTION TO PHP
What Is PHP?
PHP started out as a small open source project that evolved as more and more people found out
how useful it was. Rasmus Lerdorf unleashed the first version of PHP way back in 1994.
PHP is a server side scripting language that is embedded in HTML. It is used to manage
dynamic content, databases, session tracking, even build entire e-commerce sites.
PHP is pleasingly zippy in its execution, especially when compiled as an Apache module on the
Unix side. The MySQL server, once started, executes even very complex queries with huge
result sets in record-setting time.
26
PHP supports a large number of major protocols such as POP3, IMAP, and LDAP. PHP4 added
support for Java and distributed object architectures (COM and CORBA), making n-tier
development a possibility for the first time.
PHP SERVER
Have been the workhouse for data management operation for over a decade and continue
to evolve and mature, providing sophisticated storage, retrieval and distribution function to
enterprise – wide data processing and management system compared to the file system,
RDBMS provides organization with capability to easily integrate and leverage the massive
amount of operational data into meaningful data.
The first software architectural pattern that most of us encounter early as a PHP developer is the
Model View Controller (MVC).Almost every modern PHP framework comes with MVC
27
architecture baked in.First of all, what is MVC and where did it come from?MVC (Model-
View-Controller) was formulated by Trygve Reenskaug in 1979 for the SmallTalk language.It
separates the code into three layers. Model is the representation of all the data used, and the
code required to make it persist. The Controller handles requests and updates the model. And
lastly, View offers ways to extract and represent the data from the Model.
It was originally meant for the GUI interface in desktop applications.Thus the View actually
observed the changes in Model and updated itself automatically. But this approach has changed
as it made its way to the web. This is because updating the view automatically is not feasible
for the web.The view is no longer using any observer pattern. It is usually passed the updated
Model data by the Controller in almost all of the web frameworks.
PHPMYADMIN ARCHITECTURE
PHP Files
There are major three sets of files on the disk that compose database:
The most common is the database files where the data resides. The control and the redo logs
support the functioning of the architecture itself. All of these sets of files be present, open and
available to PHP Server for any data on database to be usable all these files are binary files.
28
INTRODUCTION TO SQL-SERVER
SQL-SERVER 2005
Have been the workhouse for data management operation for over a decade and continue
to evolve and mature, providing sophisticated storage, retrieval and distribution function to
enterprise – wide data processing and management system compared to the file system,
RDBMS provides organization with capability to easily integrate and leverage the massive
amount of operational data into meaningful data.
The SQL Server architecture in this section is generic architecture that applies all platforms
on which SQL run. These may be different platform, but the fundamentals are same. Physically
29
in its simplest form, an SQL database is nothing more than a set of files on the disk. The
physical relation of these files is irrelevant to the function of the database. Logically the
database is divided into a set of user account, each of which is identified by username and
password unique to the database. Tables and objects are owned one by one of these. SQL
Server maintains its own list of authorized user and their associated privileged, manages
memory cache paging; control locking for concurrent resource usage; dispatch and schedules
users request ; manages space usage within its table space structure.
SQL Files
There are major three sets of files on the disk that compose database:
The most common is the database files where the data resides. The control and the redo logs
support the functioning of the architecture itself. All of these sets of files be present, open and
available to SQL Server for any data on database to be usable all these files are binary files.
30
CHAPTER : 4
SYSTEM-ANALYSIS &DESIGN
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 software’s operational characteristics (function, data and
behavior), indicate software’s 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
31
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.
Gauze 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 developed from the users of the product and from the customer
through interviews and discussions.
Data collection is done by taking the copies of the documents involved in its working
from the organization.
METHODOLOGY ADOPTED
• 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.
32
• 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.
• 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.
• 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.
•
ANALYSIS METHODS
• Structured system analysis techniques are used for the analysis of algorithm and
development.
• Background analysis: concept of mining and about the algorithm is learned through
research papers on Internet and experts theory.
• Fact-finding: facts about the algorithm are collected from the books and Internet.
• Analysis: facts are analyzed through different examples related to algorithm.
• DFDs and flowchart are used to model the algorithm and logic design.
DESIGN METHODS
33
• Structured design techniques are used to design the software.
• Layering has been done to refine the architecture. Initially, two layers are introduced,
system layer and application layer.
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.
The Model
The Model pattern within a specific MVC set typically refers to only one implementation, and it
is comprised to one or more classes that represent the business entities, or -in OO parlance- the
34
Domain Model. In many case, you may have as part of the Model an Application Model also,
representing the core services of your application (mostly transversal services as data access,
layer invocation, operating system services, the file system, etc).
For the purpose of this first approach we will skip the differences between Domain or
Application models, and will think of both as The Model.
Something important to keep in mind is that the Model should not know nothing about the
Views.
The Views
These are normally more than once, and in fact having several Views of the same Model is one
of the main objectives in the MVC pattern.
Views are mostly visual implementations; although some views can be just APIs (application
programming interfaces) exposed as Windows Services, Web Services, COM components, etc.
Views have knowledge about the existence of the Model, but in a loosely coupled way.
The Controllers
Controllers are implementations of some behavior. Not business logic, but Model manipulation.
Each domain-specific algorithm is built into the Model, but all the usage coordination between
the Model and the outside world is done through Controllers. In most scenarios you use a
different Controller for each different type of behavior (like navigation, editing, etc).
Assembling the triad
Separation between Views and Controllers are somewhat important in Smalltalk, although in
other platforms like Java, .NET or Visual FoxPro the usual practice is to have the Model and
the Views separated, but not necessarily the Controllers. In any case, we will see a small
example with the three separate layers, and then you can decide what the approach that best fits
you is.
In any case Models, Views and Controllers typically communicate through events to minimize
coupling. Remember that the View only knows there is a Model with some specific public
interface, the Controller acts as a communicator, and the Model doesn't know anything about
the other two.
Figure 1 shows you the basic responsibilities and interactions between Model, Views and
Controllers. Notice how coupling is decreased by limiting calls to known interfaces. In practice,
most interaction is done trough events and the Controller is the one setting all the subscriptions
between events sources and delegates.
Figure 1: MVC relationshipss
35
CHAPTER : 5
LIFE CYCLE OF THE PROJECT
ARCHECTURE:
36
LOGIN-MODULE :-1
Start
37
SIGNUP Have already Yes
Account?
Login
QUIZ
Logout
Stop
38
DATA FLOW DIAGRAM
39
INTRODUCTION
The DFD also known as the Bubble Chart is a simple graphical formalism that can be
used to represent a system in terms of the input data to the system. Various processing carried
out on these data, and the output data generated by the system. The main reason why the DFD
technique is so popular is probably because of the fact that DFD is a very simple formalism-it is
simple to understand and use. A DFD uses a very limited number of primitive symbols to
represent the functions performed by a system and the data flow among these functions.
Starting with a set of high-level functions that a system performs, a DFD model hierarchically
represents various sub functions. The five different types of primitive symbols used for
constructing DFDs are:
SYMBOLS USED:
PROCESS:
A function is represented using a circle. This symbol is called a process or a bubble. Bubbles
are annotated with the names of the corresponding functions.
EXTERNAL ENTITY:
An external entity such as a librarian, a library member, etc. is represented by a rectangle. The
external entities are essentially those physical entities external to the software system that
interact with the system by inputting data to the system or by consuming
40
DATA FLOW:
A directed arc or an arrow is used as a data flow symbol. A data flow symbol represents the
data flow occurring between two processes, or between an external entity and a process, in the
direction of the data flow arrow. Data flow symbols are usually annotated with the
corresponding data names.
DATA STORE:
A data store represents a logical file. It is represented using two parallel lines. A logical file can
represent either a data store symbol, which can represent either a data structure, or a physical
file on disk. Each data store is connected to a process by means of a data flow symbol. The
direction of the data flow arrow shows whether data is being read from or written into a data
store. A arrow flowing in or out of a data store implicitly represents the entire data of the data
store and hence connecting to a data store need not be annotated with the name of the
corresponding data items.
OUTPUT SYMBOL:
The output symbol is used when a hard copy is produced and the user of the copies cannot be
clearly specified or there are several users of the output
41
CONTEXT DIAGRAM
The context diagram is the most abstract data flow representation of a system. It represents the
entire system as a single bubble. This bubble is labeled according to the main function of the
system. The various external entities with which the system interacts and the data flows
occurring between the system and the external entities are also represented.
42
FIRST LEVEL DFD
To develop the level 1 DFD, examine the high-level functional requirements. If there are
between three to seven high-level functional requirements, then these can be directly
represented as bubbles in the level 1 DFD. We can then examine the input data to these
functions and the data output by these functions, and represent them approximately in the
diagram.
LEVEL–1
43
CHAPTER : 6
STRUCTURAL-CHART
Coding The design must be translated into machine readable form. The
code generation step performs this task.
Data store: A logical construct used to depict data that is being recorded during
manual and automated processes. Data stores are organized by
logical data groupings without regard to the storage medium
DFD Data Flow Diagram-A diagram that shows the inputs and outputs of
a process and the data stores that store the data.
44
SRS Software Requirements Specifications
Unit Testing The project is divided into small units and then the testing is done
on each unit separately.
White-Box Testing It is a test case design method that uses the control the structure of
the procedural design to derive test cases.
45
TABLES:
1. SIGNUP TABLE:
46
2.CATEGORY TABLE:
47
3.QUESTION TABLE :
48
CHAPTER : 7
49
HOME PAGE:-
50
SHOWING CATEGORY:-
51
QUIZ QUESTIONS:-
52
RESULT ANALYSIS:-
53
ADMIN PANEL:
54
ADD CATEGORY:-
55
CODING OF LOGIN AND SIGNUP
<html>
<head>
<link rel="stylesheet"
href="http://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.0/jquery.min.js"></
script>
<script src="http://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"></
script>
</head>
<body>
</body>
</html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<!-- The above 3 meta tags *must* come first in the head; any other head content must
come *after* these tags -->
<title>Quiz in PHP</title>
56
<!-- Bootstrap -->
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media
queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
</head>
<body>
<div class="container">
<div class="row">
<br>
<div class="col-sm-5">
<br>
<br>
<br>
<br>
<div class="panel-heading"><u><b>LOGIN</b></u></div>
57
<div class="panel-body">
</div>
<?php
echo "your
email or password is not correct";
?>
<div class="form-group">
<label for="email">Email
address:</label>
</div>
<div class="form-group">
<label for="pwd">Password:</label>
</div>
<div class="checkbox">
58
<label><input type="checkbox">
Remember me</label>
</div>
</form>
</div>
</div>
</div>
<div class="col-sm-2"></div>
<div class="col-sm-5">
<br>
<div
class="panel-heading"><b><u>SIGNUP</u></b></div>
<div class="panel-body">
</div>
59
}
?>
<div class="form-group">
<label for="name">
Name</label>
<input type="text"
class="form-control" name="n" id="firstname">
</div>
<div class="form-group">
<label
for="email">Email</label>
<input type="email"
class="form-control" name="e" id="email">
</div>
<div class="form-group">
<label
for="pwd">Password:</label>
<input type="password"
class="form-control" name="p" id="pwd">
</div>
<div class="form-group">
<label
for="pwd">upload your image</label>
60
<input type="file"
class="form-control" name="img">
</div>
<div class="checkbox">
<label><input
type="checkbox"> Remember me</label>
</div>
<button type="submit"
class="btn btn-default" name="signup">Submit</button>
</form>
</div>
</div>
</div>
</div>
</div>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></
script>
<!-- Include all compiled plugins (below), or include individual files as needed -->
<script src="js/bootstrap.min.js"></script>
</body>
</html>
61
CODING OF HOME PAGE
<?php
include("class/users.php");
$email=$_SESSION['email'];
$profile=new users;
$profile->users_profile($email);
$profile->cat_show();
// print_r($profile->cat);
//print_r($profile->data);
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>home page</title>
<link rel="stylesheet"
href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.0/css/bootstrap.min.css">
62
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.0/js/bootstrap.min.js"></
script>
<style>
body{
background:url(images1.jpg);
background-size:cover;
}</style>
</head>
<body>
<div class="container">
<h2><center><u>ONLINE QUIZ</u></center></h2>
</ul>
<div class="tab-content">
<h3>HOME</h3>
63
<div class="col-sm-4"></div>
<div class="col-sm-4"><br>
<option>select category
<?php
foreach($profile->cat as $category)
?>
<?php
}?>
</select><br>
</form>
</div>
64
</div>
<div class="col-sem-4"></div>
</div>
<h3>Showing profile</h3>
<table class="table">
<thead>
<tr>
<th>id</th>
<th>name</th>
<th>email</th>
<th>image</th>
</tr>
</thead>
<tbody>
<?php
foreach($profile->data as $prof)
{?>
65
<tr>
</tr>
</tbody>
<?php }?>
</table>
</div>
<h3>Menu 2</h3>
<p>Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium
doloremque laudantium, totam rem aperiam.</p>
</div>
</div>
</div>
</div>
</body>
</html>
66
s
<?php
include("class/users.php");
$cat=new users;
$category=$cat->cat_show();
?>
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<!-- The above 3 meta tags *must* come first in the head; any other head content must
come *after* these tags -->
67
<!-- Bootstrap core CSS -->
<!-- Just for debugging purposes. Don't actually copy these 2 lines! -->
<script src="../../assets/js/ie-emulation-modes-warning.js"></script>
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media
queries -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.3/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<style>
body{
background:url(pic1.jpeg);
background-size:cover;
}</style>
68
</head>
<body>
<div class="container-fluid">
<div class="row">
<li><a href="#">Reports</a></li>
<li><a href="#">Analytics</a></li>
<li><a href="#">Export</a></li>
</ul>
</ul>
69
<li><a href="">Another nav item</a></li>
</ul>
</div>
<div class="container-fluid">
<div class="navbar-header">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
</div>
</div>
</nav>
<h1 class="page-header">Dashboard</h1>
<div class="table-responsive">
70
<table class="table table-striped">
<?php
if(isset($_GET['msg'])&& !empty($_GET['msg']))
?>
<div class="form-group">
<label for="text">question</label>
</div>
<div class="form-group">
<label for="text">option-1</label>
</div>
<div class="form-group">
<label for="text">option-2</label>
</div>
<div class="form-group">
<label for="text">option-3</label>
71
<input type="text" class="form-control" name="op3"
placeholder="Enter option-3">
</div>
<div class="form-group">
<label for="text">option-4</label>
</div>
<div class="form-group">
<label for="text">answer</label>
</div>
<?php
foreach($category as $c)
?>
</select>
72
</div>
</form>
<h2>add category</h2>
<div class="form-group">
<div class="col-sm-10">
</div>
</div>
<div class="form-group">
</div>
</div>
</form>
</tbody>
</table>
</div>
</div>
</div>
73
</div>
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<script>window.jQuery || document.write('<script
src="../../assets/js/vendor/jquery.min.js"><\/script>')</script>
<script src="../../dist/js/bootstrap.min.js"></script>
<!-- Just to make our placeholder images work. Don't actually copy the next line! -->
<script src="../../assets/js/vendor/holder.min.js"></script>
<script src="../../assets/js/ie10-viewport-bug-workaround.js"></script>
</body>
</html>
74
CLASS FILE
<?php
session_start();
class users{
public $host="localhost";
public $username="root";
public $pass="";
public $db_name="quiz_oops";
public $conn;
public $data;
public $cat;
public $qus;
public $ans;
$this->conn=new mysqli($this->host,$this->username,$this->pass,$this-
>db_name);
if($this->conn->connect_errno)
75
die ("database connection failed".$this->conn->connect_errno);
$this->conn->query($data);
return true;
$query->fetch_array(MYSQLI_ASSOC);
if($query->num_rows>0)
$_SESSION['email']=$email;
return true;
else {
return false;
76
}
$row=$query->fetch_array(MYSQLI_ASSOC);
if($query->num_rows>0)
$this->data[]=$row;
return $this->data;
while( $row=$query->fetch_array(MYSQLI_ASSOC))
77
{
$this->cat[]=$row;
return $this->cat;
while( $row=$query->fetch_array(MYSQLI_ASSOC))
$this->qus[]=$row;
return $this->qus;
$ans=implode("",$data);
$right=0;
$wrong=0;
78
$no_answer=0;
while( $qust=$query->fetch_array(MYSQLI_ASSOC))
if($qust['ans']==$_POST[$qust['id']])
$right++;
elseif($_POST[$qust['id']]=="4")
$no_answer++;
else
$wrong++;
$array=array();
$array['right']=$right;
$array['wrong']=$wrong;
79
$array['no_answer']=$no_answer;
return $array;
$a= $this->conn->query($rec);
return true;
$ca=$this->conn->query($arg);
return true;
header("location:".$url);
80
}
new users
CHAPTER : 8
TESTING
TESTING:
TESTING METHODS
• Structured testing tools had been used for testing the programs.
• The same group is respoSSnsible to test the reliability of software by using various
inputs and techniques, on various parts and functionalities.
81
TESTING METHODOLOGY
• Test plan has been created to guide the overall testing process.
• Black box testing has been used to test the functionality of each module.
• ASP.Net debugger has been used as a tool to black box test functional behavior of
module.
• C#.Net debugger has also been used for white box testing by comparing step-by-step
execution against white box cases.
82
CHAPTER : 9
SYSTEM- IMPLEMENTATION
SYSTEM MAINTENANCE
SYSTEM IMPLEMENTATION
Direct Implementation Method is used to implement the system at the user’s site. No special
Equipment (Hardware Device) is required to install the Software. The only requirement is the
user must have a Printer Installed & connected to the system for the generation of the various
receipts & the reports.
SYSTEM MAINTENANCE
System maintenance denotes any changes made to a software product after it has been
delivered to the customer. Maintenance is inevitable for almost any kind of product. However,
most products need maintenance due to the wear and tear caused by use. On the other hand,
software products do not need maintenance on this count, but need maintenance to correct
errors, enhance features, port to new platforms, etc.
83
Software maintenance is becoming an important activity of large number of
organizations. This is no surprise, given the rate of hardware obsolescence, the immortality of a
software product per se, and the demand of the user community to see the existing software
products run on newer platforms, run in newer environments, and/or with enhanced features.
When the hardware platform changes and a software product perform some low-level functions,
maintenance is necessary. Also, whenever the support environment of a software changes, the
software product requires re-work to cope with the newer interface. Thus, every software
product continues to evolve after its development through maintenance efforts.
84
FUTURE SCOPE OF ONLINE EXAM
Scope of this project is very broad in terms of other manually taken ecxamination.
85
LIMITATIONS
Current system provides multiple choices butb only one can be selected.
In case questions ans answers need to be in graphics, current system has no provision.
No information about the total number of students participated.
Students can only see their results , top score is not available.
Solution of questions is not displayed to users.
Based on the future security issues can be improved using emerging technologies.
86
CONCLUSION
This web application provides facility, to conduct online examination. It saves time as it allows
number of students to give the exam at a time and display the result as th etest gets over, so no
need to wait for the result. It is automatically generated.
Admin can easily add new questions ans answers. And also able to add new category.
Users can register, login and give the test with their specific id and can see the result which
contain totsl number of questions, attempted questions and correct , wrong number of questions
with percentage.
87
CHAPTER : 10
BIBLIOGRAPHY
BOOKS:
Head First PHP & MySQL – by Lynn Beighley & Michael Morrison
88
Learning PHP, MySQL, JavaScript, and CSS: A Step-by-Step Guide to Creating
LIBRARY:
MSDN
The MSDN Library is the essential reference for developers, with more than a
gigabyte of technical programming information; including sample code, documentation,
technical articles, the Microsoft Developer Knowledge Base, and anything else we might need
to develop solutions that implement Microsoft technology.
89
90