A Project Report

on
KWIKWIT – THE ONLINE EXAM PORTAL
Submitted to the Department of Computer Science

By
B.SC(MECS) VIth Semester

TATA ESWAR SAI ANURAG (718139705224)

Under The Esteemed Guidance Of

SRI D. Srinivasa Rao

ASSOCIATE PROFESSOR OF COMPUTER SCIENCE

ADITYA DEGREE COLLEGE

(Affiliated to Andhra University)
Accredited by NAAC with A Grade
Waltait-530017 Visakhapatnam District, ANDHRA PRADESH.
2020-2021

ADITYA DEGREE COLLEGE

PSR COMPLEX-VIZIANAGARAM

1
 (Affiliated to Andhra University)

Accredited by NAAC with A Grade

Waltait-530017 Visakhapatnam District, ANDHRA PRADESH.

DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE

This is to certify that the project entitled, “KWIKWIT” is a bona fide work of
TATA ESWAR SAI ANURAG bearing VI SEM BSC(MECS), submitted to the Department of
Computer Science, Aditya Degree College, Vizianagaram for the academic year 2020-2021.

Project Guide Head of the Department

Sri D. Srinivasa Rao Sri U. Rajesh Babu
Assistant Professor, Associate Professor& HOD
Department of Computer Science, Department of Computer Science,
Aditya Degree College, Aditya Degree College,
Vizianagaram . Vizianagaram.

External Examiner

2
 ACKNOWLEDGEMENT

The satisfaction and euphoria that accompany the successful completion of any task would be
incomplete without the mention of people who made it possible, whose constant guidance and
encouragement crowned our efforts with success. It is a pleasant aspect that i have the
opportunity to express my gratitude for all of them.

The first person I would like to thank is my guide Sri. D. Srinivasa Rao, Associate Professor,
Department of Computer Science, Aditya Degree College, Vizianagaram. His wide
knowledge and logical way of thinking have made a deep impression on me. His understanding,
encouragement and personal guidance have provided the basis for this project. He is a source of
inspiration for innovative ideas and his kind support is well known to all his students and
colleagues.

I wish to thank Sri. U. Rajesh Babu, Head of the Department, Department of Computer
Science, Aditya Degree College, Vizianagaram, who has extended her support for the success
of this project.

I wish to thank Sri B Damodara Rao, M. Sc, B.Ed. ,Principal ,Aditya Degree
College, Vizianagaram, who has extended his support for the success of this project.
I would like to thank all the Management & Technical Supporting Staff for their timely help
throughout the project.

3
 DECLARATION
I TATA ESWAR SAI ANURAG hereby declare that the project entitled “KWIKWIT”
submitted to Department of Computer Science, Aditya Degree College, and Vizianagaram has been
carried out by me alone under the guidance of Sri. D. Srinivasa Rao

Place: Vizianagaram
Date:

TATA ESWAR SAI ANURAG

4
 INDEX

S. N CONTENTS
1. INTRODUCTION - 6

2. ANALYSIS - 8

2.1 FEASABILITY STUDY - 9

2.2 SYSTEM ANALYSIS - 12

2.2 SYSTEM SPECIFICATIONS - 14

3. DESIGN APPROACH - 15

3.1 INTRODUCTION TO DESIGN - 16

3.2 PROJECT MODULES - 17

3.3 UML DIAGRAMS - 18

3.4 DATA FLOW DIAGRAMS - 23

3.5 E-R DIAGRAMS - 26

4. TECHNOLOGY DESCRIPTION - 29

5. SAMPLE CODE - 36

6. TESTING - 43

6.1 Introduction - 44
6.2 Test case design - 44
6.3 Software testing strategies - 45
6.4 Validation testing - 46
7. OUTPUT SCREENS - 48

8. FUTURE ENHANCEMENTS - 53

9. CONCLUSION - 55

10. BIBILIOGRAPHY - 57

5
6
INTRODUCTION:

Online examinations are an important method of evaluating the success potential of

students. This research effort the individuals under consideration were students who would be enrolling
in computer courses or Technologies Registrations. A prototype of a web-based placement examination
system is described from the standpoint of the research effort, end user, and software development.

An on-line educational system including exam processing and electronic journal

features. An instructor builds a course based questions which on-line contain in identification of
assignments. Which are compiled into an on-line exam syllabus?

Users enrolled in the platform may access the electronic details they provided and
perform various functions with the on-line educational system in order to participate in the on-line
examinations. Users can receive an on-line exam, having multimedia content, for the course, and they
can electronically provide answers for the exam. And after Completion of their duration of exam they
will be provided with the grade or marks secured in their examinations.

7
8
FEASIBILITY STUDY:

Feasibility study is conducted once the problem is clearly understood. Feasibility study is a high level
capsule version of the entire system analysis and design process. The objective is to determine quickly at
a minimum expense how to solve a problem. The purpose of feasibility is not to solve the problem but to
determine if the problem is worth solving.

The system has been tested for feasibility in the following points.
1. Technical Feasibility
2. Economic Feasibility
3. Operational Feasibility.

1. Technical Feasibility:
The project entitles "Courier Service System” is technically feasibility because of the below
mentioned feature. The project was developed in Java which Graphical User Interface.
It provides the high level of reliability, availability and compatibility. All these make Java
an appropriate language for this project. Thus the existing software Java is a powerful language.

2. Economic Feasibility:

The computerized system will help in automate the selection leading the profits and
details of the organization. With this software, the machine and manpower utilization are expected to go
up by 80-90% approximately. The costs incurred of not creating the system are set to be great, because
precious time can be wanted by manually.

3. Operational Feasibility:

In this project, the management will know the details of each project where he may be presented and
the data will be maintained as decentralized and if any inquires for that particular contract can be known
as per their requirements and necessaries.

9
Implementation:
Implementation is the stage where the theoretical design is turned into a working system. The most
crucial stage in achieving a new successful system and in giving confidence on the new system for the
users that it will work efficiently and effectively.

The system can be implemented only after thorough testing is done and if it is found to work according to
the specification.

It involves careful planning, investigation of the current system and its constraints on implementation,
design of methods to achieve the changeover and an evaluation of change over methods a part from
planning. Two major tasks of preparing the implementation are education and training of the users and
testing of the system.

The more complex the system being implemented, the more involved will be the systems analysis and
design effort required just for implementation.

The implementation phase comprises of several activities. The required hardware and software
acquisition is carried out. The system may require some software to be developed. For this, programs are
written and tested. The user then changes over to his new fully tested system and the old system is
discontinued.
TESTING
The testing phase is an important part of software development. It is the puterized system will help
in automate process of finding errors and missing operations and also a complete verification to determine
whether the objectives are met and the user requirements are satisfied.

Software testing is carried out in three steps:

1. The first includes unit testing, where in each module is tested to provide its correctness, validity
and also determine any missing operations and to verify whether the objectives have been met. Errors are
noted down and corrected immediately. Unit testing is the important and major part of the project. So
errors are rectified easily in particular module and program clarity is increased. In this project entire
system is divided into several modules and is developed individually. So unit testing is conducted to

10
individual modules.

2. The second step includes Integration testing. It need not be the case, the software whose
modules when run individually and showing perfect results, will also show perfect results when run as a
whole. The individual modules are clipped under this major module and tested again and verified the
results. This is due to poor interfacing, which may result in data being lost across an interface. A module
can have inadvertent, adverse effect on any other or on the global data structures, causing serious
problems.
3. The final step involves validation and testing which determines which the software functions
as the user expected. Here also some modifications were. In the completion of the project it is satisfied
fully by the end user.
Maintenance and environment:
AS the number of computer based systems, grieve libraries of computer software began to expand. In
house developed projects produced tones of thousand soft program source statements. Software products
purchased from the outside added hundreds of thousands of new statements. A dark cloud appeared on
the horizon. All of these programs, all of those source statements-had to be corrected when false were
detected, modified as user requirements changed, or adapted to new hardware that was purchased. These
activities were collectively called software Maintenance.
The maintenance phase focuses on change that is associated with error correction, adaptations required
as the software's environment evolves, and changes due to enhancements brought about by changing
customer requirements. Four types of changes are encountered during the maintenance phase.
Correction
Adaptation
Enhancement
Prevention

Correction:

Even with the best quality assurance activities is lightly that the customer will uncover
defects in the software. Corrective maintenance changes the software to correct defects.

Maintenance is a set of software Engineering activities that occur after software has been
delivered to the customer and put into operation. Software configuration management is a set of
tracking and control activities that began when a software project begins and terminates only when
the software is taken out of the operation.

11
 We may define maintenance by describing four activities that are undertaken after a program is
released for use:

Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance or Enhancement
Preventive Maintenance or reengineering

Only about 20 percent of all maintenance work are spent "fixing mistakes". The remaining 80
percent are spent adapting existing systems to changes in their external environment, making
enhancements requested by users, and reengineering an application for use.

ADAPTATION:

Over time, the original environment (E>G., CPU, operating system, business rules, external
product characteristics) for which the software was developed is likely to change. Adaptive maintenance
results in modification to the software to accommodate change to its external environment.

ENHANCEMENT:

As software is used, the customer/user will recognize additional functions that will provide benefit.
Perceptive maintenance extends the software beyond its original function requirements.

PREVENTION:

Computer software deteriorates due to change, and because of this, preventive maintenance,
often called software re-engineering, must be conducted to enable the software to serve the needs
of its end users. In essence, preventive maintenance makes changes to computer programs so that
they can be more easily corrected, adapted, and enhanced. Software configuration management
(SCM) is an umbrella activity that is applied throughout the software process. SCM activities are
developed to

SYSTEM ANALYSIS:

1. Existing System:

12
 Existing system is a manual one in which users are maintaining books to store the information
like Student Details, Instructor Details, Schedule Details and feedbacks about students who attempted
exam as per schedule. It is very difficult to maintain historical data.

DISADVANTAGES:

The following drawbacks of existing system emphasize the need for computerization:

1. A lot of copies of question papers have to be made

2. A lot of correction work hence delay in giving the results
3. A lot of tabulation work for each subject results

2. Proposed System:

This application is used to conduct online examination. The students can sit at individual
terminals and login to write the exam in the given duration. The questions have to be given to the
students. This application will perform correction, display the result immediately and also store it in
database. This application provides the administrator with a facility to add new exams. This application
provides the Instructor add questions to the exam, modify questions in the exam in a particular exam.
This application takes care of authentication of the administrator, Instructor as well as the student.

3. Objective of the System:

The objective of the Online Examination Tool is to provide better information for the users of this
system for better results for their maintenance in student examination schedule details and grading details.

13
 System Specifications

Hardware Requirements:

 Pentium-IV(Processor).
 256 MB Ram
 512 KB Cache Memory
 Hard disk 10 GB
 Microsoft Compatible 101 or more Key Board

Software Requirements:

 Operating System: Windows

 Web-Technology: PHP

 Front-End: HTML, CSS, JAVASCRIPT

 Back-End: MySQL

 Web Server: Apache SERVER.

14
15
INTRODUCTION:

Design is the first step in the development phase for any techniques and principles
for the purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.

Once the software requirements have been analyzed and specified the software
design involves three technical activities - design, coding, implementation and testing that are required to
build and verify the software.

The design activities are of main importance in this phase, because in this
activity, decisions ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability and maintainability of the
system. Design is the only way to accurately translate the customer’s requirements into finished software
or a system.

Design is the place where quality is fostered in development. Software

design is a process through which requirements are translated into a representation of software. Software
design is conducted in two steps. Preliminary design is concerned with the transformation of requirements
into data.

16
ONLINE EXAMINATION SYSTEM:

MODULES:

1: ADMIN MODULE
2.INSTRUCTOR MODULE
3.STUDENT MODULE

1.ADMIN MODULE:

1. REGISTER
2. LOGIN
3. CHANGE PASSWORD&FORGOTPASSWORD
4. STUDENT -MODIFING DETAILS
5. DEPARTMENTS-ENTERING/MODIFYING DETAILS
6. INSTRUCTOR DETAILS-MODIFYING DETAILS

1. REGISTER: To be authenticated first have to be registered.

2. LOGIN: The Registered User Can Be Allowed to view inner details for which he
Permitted

3. CHANGE PASSWORD & FORGOT PASSWORD: User has rights to modify his login
details&
also be informed through mails if he is unable to login.

4. STUDENT - MODIFING DETAILS: User can be modified to change status of

each User.

2. STUDENT MODULE:
I. REGISTER
II. LOGIN
III. TAKE EXAM- MULTIPLE CHOICE
IV. SEE EXAM RESULTS
V. LOGOUT

1.REGISTER: To be authenticated first have to be registered

2.LOGIN: The Registered User Can be allowed to view inner details for which he Permitted

3.TAKE EXAM- MULTIPLE CHOICE: The registered student allowed to start the exam

17
 4. SEE EXAM RESULTS: After Completion of exam he can view at his result.

5.LOGOUT: After the process of examination he turned to Logout page.

UML Diagrams:
Actor:
A coherent set of roles that users of use cases play when interacting with the use `cases.

Use case:
A description of sequence of actions, including variants, that a system performs that
Yields an observable result of value of and actor.

UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and
documenting the system. This is the step while developing any product after analysis. The goal from this
is to produce a model of the entities involved in the project which later need to be built. The
representation of the entities that are to be used in the product being developed need to be designed.
There are various kinds of methods in software design:
They are as follows:
 Use case Diagram
 Sequence Diagram
 Collaboration Diagram
 Activity Diagram
 State chat Diagram

USECASE DIAGRAMS:

18
 Use case diagrams model behavior within a system and helps the developers
understand of what the user requires. The stick man represents what’s called an actor.
Use case diagram can be useful for getting an overall view of the system and clarifying
who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction between the
use case and actors.

 The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system.
USECASE DIAGRAM:

A Use case is a description of set of sequence of actions. Graphically it is rendered as an ellipse

with solid line including only its name. Use case diagram is a behavioral diagram that shows a set of use
cases and actors and their relationship. It is an association between the use cases and actors. An actor
represents a real-world object. Primary Actor – Sender, Secondary Actor Receiver.

r
OptionsBasedQuestion Answering
Register

LogIN User view Result

True or False Question Answering LogOut

SEQUENCE DIAGRAM:

19
 Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS.
An interaction diagram shows an interaction, consisting of set of objects and their relationship including
the messages that may be dispatched among them.

A sequence diagram is an introduction that empathizes the time ordering of messages.

Graphically a sequence diagram is a table that shows objects arranged along the X-axis and messages
ordered in increasing time along the Y-axis

COLLABORATION DIAGRAM:

A collaboration diagram is an introduction diagram that emphasizes the structural organization of

the objects that send and receive messages. Graphically a collaboration diagram is a collection of vertices
and arcs.

20
CLASS DIAGRAM:

Class is nothing but a structure that contains both variables and methods. The Class
Diagram shows a set of classes, interfaces, and collaborations and their relating ships. There is most
common diagram in modeling the object oriented systems and are used to give the static view of a system.
It shows the dependency between the classes that can be used in our system.
The interactions between the modules or classes of our projects are shown below. Each block contains
Class Name, Variables and Methods.

CLASS:
A description of set of objects that share the same attributes, operations, relationships, and semantics

21
Maintaining User Details Maintaining Test Details

User registration
Test Details
id:int
name:varchar(50) id:int
Test Result:int
DOB:datetime
Gender:varchar(10)
Branch:varchar(20)
College:varchar(50) Take test()
uid:varchar(20) End test()
pwd:varchar(20)
rpwd:varchar(20)
utype:varchar(20)
que:varchar(500)
ans:varchar(500)

Update User()
View User Result()

22
State Chart Diagram:

DATA FLOW DIAGRAMS:

The DFD takes an input-process-output view of a system i.e. data objects flow into the
software, are transformed by processing elements, and resultant data objects flow out of the software.

Data objects represented by labeled arrows and transformation are represented by circles
also called as bubbles. DFD is presented in a hierarchical fashion i.e. the first data flow model represents
the system as a whole. Subsequent DFD refine the context diagram (level 0 DFD), providing increasing
details with each subsequent level.

23
 The DFD enables the software engineer to develop models of the information domain &
functional domain at the same time. As the DFD is refined into greater levels of details, the analyst
performs an implicit functional decomposition of the system. At the same time, the DFD refinement results
in a corresponding refinement of the data as it moves through the process that embody the applications.

A context-level DFD for the system the primary external entities produce information for
use by the system and consume information generated by the system. The labeled arrow represents data
objects or object hierarchy.

RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions

 Reads left to right and top to bottom.

 Identify all inputs and outputs.

 Identify and label each process internal to the system with Rounded circles.

 A process is required for all the data transformation and Transfers. Therefore, never connect a
data store to a data Source or the destinations or another data store with just a Data flow arrow.

 Do not indicate hardware and ignore control information.

 Make sure the names of the processes accurately convey everything the process is done.

 There must not be unnamed process.

 Indicate external sources and destinations of the data, with Squares.

 Number each occurrence of repeated external entities.

 Identify all data flows for each process step, except simple Record retrievals.

 Label data flow on each arrow.

 Use details flow on each arrow.

24
  Use the details flow arrow to indicate data movements.

DATAFLOW DIAGRAMS:

Database:

User
registration

Take
Test

Online
Examination

Database

25
user registration:

User
User registration details

Register Update Search for

user user view user
user details
details details

Taking Test:

User
Taking Test details

Start End Exam View

Exam Result

E-R Diagrams:

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way to
unify the network and relational database views. Simply stated the ER model is a conceptual data model
that views the real world as entities and relationships. A basic component of the model is the Entity-

26
Relationship diagram which is used to visually represents data objects. Since Chen wrote his paper the
model has been extended and today it is commonly used for database design for the database designer, the
utility of the ER model is:

 it maps well to the relational model. The constructs used in the ER model can easily be transformed
into relational tables.
 it is simple and easy to understand with a minimum of training. Therefore, the model can be used
by the database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to implement a data
model in a specific database management software.

Connectivity and Cardinality:

The basic types of connectivity for relations are: one-to-one, one-to-many, and many-to-many. A
one-to-one (1:1) relationship is when at most one instance of an entity A is associated with one instance
of entity B. For example, "employees in the company are each assigned their own office. For each
employee there exists a unique office and for each office there exists a unique employee.

A one-to-many (1: N) relationships is when for one instance of entity A, there are zero, one, or many
instances of entity B, but for one instance of entity B, there is only one instance of entity A. An example
of a 1: N relationships is

a department has many employees

each employee is assigned to one department

A many-to-many (M: N) relationship, sometimes called non-specific, is when for one instance of entity
A, there are zero, one, or many instances of entity B and for one instance of entity B there are zero, one,
or many instances of entity A. The connectivity of a relationship describes the mapping of associated

ER Notation:

There is no standard for representing data objects in ER diagrams. Each modeling methodology
uses its own notation. The original notation used by Chen is widely used in academic’s texts and journals

27
but rarely seen in either CASE tools or publications by non-academics. Today, there are a number of
notations used, among the more common are Bachman, crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The notation
used in this document is from Martin. The symbols used for the basic ER constructs are:

 entities are represented by labeled rectangles. The label is the name of the entity. Entity names

should be singular nouns.

 relationships are represented by a solid line connecting two entities. The name of the

relationship is written above the line. Relationship names should be verbs

 attributes, when included, are listed inside the entity rectangle. Attributes which are identifiers

are underlined. Attribute names should be singular nouns.

 cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is omitted,

the cardinality is one.

 existence is represented by placing a circle or a perpendicular bar on the line. Mandatory

existence is shown by the bar (looks like a 1) next to the entity for an instance is required.

Optional existence is shown by placing a circle next to the entity that is optional

28
29
 OVERVIEW OF TECHNOLOGIES USED

PHP
PHP: Hypertext Preprocessor, is a widely used, general-purpose scripting language that was originally
designed for web development, to produce dynamic web pages. It can be embedded into HTML and
generally runs on a web server, which needs to be configured to process PHP code and create web page
content from it. It can be deployed on most web servers and on almost every operating system and platform
free of charge.
PHP was originally created by Ramus Leadoff in 1995 and has been in continuous development ever
since. The main implementation of PHP is now produced by The PHP Group and serves as the de facto
standard for PHP as there is no formal specification. PHP is free software released under the PHP License,
which is incompatible with the GNU General Public License (GPL) because of restrictions on the use of the
term PHP
PHP has evolved to include a command line interface capability and can also be used in standalone
graphical applications.
USAGE:
PHP is a general-purpose scripting language that is especially suited for web development. PHP
generally runs on a web server. Any PHP code in a requested file is executed by the PHP runtime, usually to
create dynamic web page content. It can also be used for command-line scripting and client-side GUI
applications. PHP can be deployed on most web servers, many operating systems and platforms, and can be
used with many relational database management systems. It is available free of charge, and the PHP Group
provides the complete source code for users to build, customize and extend for their own use.
PHP primarily acts as a filter, taking input from a file or stream containing text and/or PHP instructions
and outputs another stream of data; most commonly the output will be HTML. Since PHP 4, the PHP parser
compiles input to produce byte code for processing by the Zend Engine, giving improved performance over
its interpreter predecessor
Originally designed to create dynamic web pages, PHP now focuses mainly on server-side scripting, and it
is similar to other server-side scripting languages that provide dynamic content from a web server to a
client, such as Microsoft's Active Server Pages, Sun Microsystems' Java Server Pages and mod_perl. PHP
has also attracted the development of many frameworks that provide building blocks and a design structure

30
to promote rapid application development (RAD). Some of these include CakePHP, Symfony, CodeIgniter,
and Zend Framework, offering features similar to other web application frameworks.
About HTML:

HTML, which stands for Hyper Text Markup Language, is the predominant markup language for web
pages. It provides a means to create structured documents by denoting structural semantics for text such as
headings, paragraphs, lists etc. as well as for links, quotes, and other items. It allows images and objects to
be embedded and can be used to create interactive forms. It is written in the form of HTML elements
consisting of "tags" surrounded by angle brackets within the web page content. It can include or can load
scripts in languages such as JavaScript which affect the behavior of HTML processors like Web browsers;
and Cascading Style Sheets (CSS) to define the appearance and layout of text and other material. The W3C,
maintainer of both HTML and CSS standards, encourages the use of CSS over explicit presentational
markup.
Hyper Text Markup Language(HTML) is the encoding scheme used to create and format a web
document. A user need not be an expert programmer to make use of HTML for creating hypertext
documents that can be put on the internet.
Most graphical e-mail clients allow the use of a subset of HTML (often ill-defined) to provide formatting
and semantic markup not available with plain text. This may include typographic information like colored
headings, emphasized and quoted text, inline images and diagrams. Many such clients include both a GUI
editor for composing HTML e-mail messages and a rendering engine for displaying them. Use of HTML in
e-mail is controversial because of compatibility issues, because it can help disguise phishing attacks,
because it can confuse spam filters and because the message size is larger than plain text.

NAMING CONVENTIONS:
The most common filename extension for files containing HTML is .html. A common abbreviation of this
is .html, which originated because some early operating systems and file systems, such as DOS and FAT,
limited file extensions to three letters.
HTML APPLICATION:
An HTML Application is a Microsoft Windows application that uses HTML and Dynamic HTML in a
browser to provide the application's graphical interface. A regular HTML file is confined to the security
model of the web browser, communicating only to web servers and manipulating only webpage objects and

31
site cookies. An HTA runs as a fully trusted application and therefore has more privileges, like
creation/editing/removal of files and Windows Registry entries. Because they operate outside the browser's
security model, HTAs cannot be executed via HTTP, but must be downloaded (just like an EXE file) and
executed from local file system
ABOUT JAVASCRIPT:
JavaScript is an object-oriented scripting language used to enable programmatic access to objects within
both the client application and other applications. It is primarily used in the form of client-side JavaScript,
implemented as an integrated component of the web browser, allowing the development of enhanced user
interfaces and dynamic websites. JavaScript is a dialect of the ECMAScript standard and is characterized as
a dynamic, weakly typed, prototype-based language with first-class functions. JavaScript was influenced by
many languages and was designed to look like Java, but to be easier for non-programmers to work with.
PROTOTYPE-BASED:
JavaScript uses prototypes instead of classes for inheritance. It is possible to simulate many class-based
features with prototypes in JavaScript.
Functions double as object constructors along with their typical role. Prefixing a function call with new
creates a new object and calls that function with its local this keyword bound to that object for that
invocation. The constructor's prototype property determines the object used for the new object's internal
prototype. JavaScript's built-in constructors, such as Array, also have prototypes that can be modified.
Unlike many object-oriented languages, there is no distinction between a function definition and a method
definition. Rather, the distinction occurs during function calling; a function can be called as a method. When
a function is called as a method of an object, the function's local this keyword is bound to that object for that
invocation.
USAGE:
The primary use of JavaScript is to write functions that are embedded in or included from HTML pages
and interact with the Document Object Model (DOM) of the page.
Because JavaScript code can run locally in a user's browser (rather than on a remote server) it can respond
to user actions quickly, making an application feel more responsive. Furthermore, JavaScript code can
detect user actions which HTML alone cannot, such as individual keystrokes. Applications such as Gmail
take advantage of this: much of the user-interface logic is written in JavaScript, and JavaScript dispatches

32
requests for information (such as the content of an e-mail message) to the server. The wider trend of Ajax
programming similarly exploits this strength.
A JavaScript engine (also known as JavaScript interpreter or JavaScript implementation) is an
interpreter that interprets JavaScript source code and executes the script accordingly. The first JavaScript
engine was created by Brendan Eich at Netscape Communications Corporation, for the Netscape
Navigator web browser. A web browser is by far the most common host environment for JavaScript.
Web browsers typically use the public API to create "host objects" responsible for reflecting the DOM
into JavaScript.

ABOUT MySQL:
MySQL Introduction:

There are a large number of database management systems currently available, some commercial and
some free.
Some of them : Oracle, Microsoft Access, MySQL and PostgreSQL.
These database systems are powerful, feature-rich software, capable of organizing and searching
millions of records at very high speeds.

Understanding Databases, Records, and Primary Keys:

Every Database is composed of one or more tables.

These Tables, which structure data into rows and columns, Impose organization on the data.

The records in a table(below) are not arranged in any particular order.

To make it easy to identify a specific record, therefore, it becomes necessary

standing Relationships and Foreign Keys(RDBMS):

You already know that a single database can hold multiple tables.
In a Relational database management system(RDBMS), these tables can be linked to each other by one
or more common fields, called foreign keys.

What is Database administrator(DBA)?

Database administrator is the super user of database, he has unrestricted rights and privileges to access
database, grant permission to other database users.

What is Database user(DBU)?

Database user is the person who uses the database in a restricted privilege, provided by database
administrator.

33
Download MySQL Database

If you have installed PHP’s WAMP or XAMPP server, then MySQL database already exists. if you
don’t have then download MySQL database from herehttp://www.mysql.com

DATABASE TABLES:

USER REG TABLE:

NAME NULL/NOTNULL TYPE KEY

ID NOTNULL INT PRIMARYKEY
NAME NULL VARCHAR(50)
DOB NULL DATETIME
GENDER NULL VARCHAR(10)
BRANCH NULL VARCHAR(20)
COLLEGE NULL VARCHAR(50)
UID NULL VARCHAR(50)
PWD NULL VARCHAR(20)
RPWD NULL VARCHAR(20)
UTYPE NULL VARCHAR(20)
QUE NULL VARCHAR(500)
ANS NULL VARCHAR(500)

True/False Based Question Table:

NAME NULL/NOTNULL TYPE KEY

ID NOTNULL INT PRIMARYKEY
QUE NULL VARCHAR(500)
AW NULL VARCHAR(500)

True/False Based Answer Table:

NAME NULL/NOTNULL TYPE KEY

ID NOTNULL INT FOREIGNKEY
AW NULL VARCHAR(500)

Options Based Question Table:

NAME NULL/NOTNULL TYPE KEY

34
 QID NOTNULL INT PRIMARYKEY
QN NULL VARCHAR(500)
OPTIONS1 NULL VARCHAR(100)
OPTIONS2 NULL VARCHAR(100)
ANSWER NULL VARCHAR(100)

Options Based Answers:

NAME NULL/NOTNULL TYPE KEY
QID NOTNULL INT FOREIGNKEY
ANSWER NULL VARCHAR(10)

All Student Marks

NAME NULL/NOTNULL TYPE KEY

ID NULL INT
MARKS NULL INT

Exam Schedule

NAME NULL/NOTNULL TYPE KEY

ENAME NULL VARCHAR(30)
EDATE NULL DATETIME

35
36
INDEX.PHP

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta name="viewport" content="width=device-width, initial-scale=1">

<title>Project Worlds || TEST YOUR SKILL </title>

<link rel="stylesheet" href="css/bootstrap.min.css"/>
<link rel="stylesheet" href="css/bootstrap-theme.min.css"/>
<link rel="stylesheet" href="css/main.css">
<link rel="stylesheet" href="css/font.css">
<script src="js/jquery.js" type="text/javascript"></script>

<script src="js/bootstrap.min.js" type="text/javascript"></script>

<link href='http://fonts.googleapis.com/css?family=Roboto:400,700,300' rel='stylesheet'
type='text/css'>
<?php if(@$_GET['w'])
{echo'<script>alert("'.@$_GET['w'].'");</script>';}
?>
<script>
function validateForm() {
var y = document.forms["form"]["name"].value; var letters = /^[A-Za-z]+$/;if (y == null || y == "")
{alert("Name must be filled out.");return false;}var z =document.forms["form"]["college"].value;if (z
== null || z == "") {alert("college must be filled out.");return false;}var x =
document.forms["form"]["email"].value;var atpos = x.indexOf("@");
var dotpos = x.lastIndexOf(".");if (atpos<1 || dotpos<atpos+2 || dotpos+2>=x.length) {alert("Not a valid
e-mail address.");return false;}var a = document.forms["form"]["password"].value;if(a == null || a ==
""){alert("Password must be filled out");return false;}if(a.length<5 || a.length>25){alert("Passwords
must be 5 to 25 characters long.");return false;}
var b = document.forms["form"]["cpassword"].value;if (a!=b){alert("Passwords must match.");return
false;}}
</script>

</head>

<body>
<div class="header">
<div class="row">
<div class="col-lg-6">
<span class="logo">Test Your Skill</span></div>
<div class="col-md-2 col-md-offset-4">

37
<a href="#" class="pull-right btn sub1" data-toggle="modal" data-target="#myModal"><span
class="glyphicon glyphicon-log-in" aria-hidden="true"></span>&nbsp;<span
class="title1"><b>Signin</b></span></a></div>
<!--sign in modal start-->
<div class="modal fade" id="myModal">
<div class="modal-dialog">
<div class="modal-content title1">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-
hidden="true">&times;</span></button>
<h4 class="modal-title title1"><span style="color:orange">Log In</span></h4>
</div>
<div class="modal-body">
<form class="form-horizontal" action="login.php?q=index.php" method="POST">
<fieldset>

<!-- Text input-->

<div class="form-group">
<label class="col-md-3 control-label" for="email"></label>
<div class="col-md-6">
<input id="email" name="email" placeholder="Enter your email-id" class="form-control input-md"
type="email">

</div>
</div>

<!-- Password input-->

<div class="form-group">
<label class="col-md-3 control-label" for="password"></label>
<div class="col-md-6">
<input id="password" name="password" placeholder="Enter your Password" class="form-control
input-md" type="password">

</div>
</div>

</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
<button type="submit" class="btn btn-primary">Log in</button>
</fieldset>
</form>
</div>
</div><!-- /.modal-content -->
</div><!-- /.modal-dialog -->

38
</div><!-- /.modal -->
<!--sign in modal closed-->

</div><!--header row closed-->

</div>

<div class="bg1">
<div class="row">

<div class="col-md-7"></div>
<div class="col-md-4 panel">
<!-- sign in form begins -->
<form class="form-horizontal" name="form" action="sign.php?q=account.php" onSubmit="return
validateForm()" method="POST">
<fieldset>

<!-- Text input-->

<div class="form-group">
<label class="col-md-12 control-label" for="name"></label>
<div class="col-md-12">
<input id="name" name="name" placeholder="Enter your name" class="form-control input-md"
type="text">

</div>
</div>

<!-- Text input-->

<div class="form-group">
<label class="col-md-12 control-label" for="gender"></label>
<div class="col-md-12">
<select id="gender" name="gender" placeholder="Enter your gender" class="form-control input-md"
>
<option value="Male">Select Gender</option>
<option value="M">Male</option>
<option value="F">Female</option> </select>
</div>
</div>

<!-- Text input-->

<div class="form-group">
<label class="col-md-12 control-label" for="name"></label>
<div class="col-md-12">
<input id="college" name="college" placeholder="Enter your college name" class="form-control
input-md" type="text">

</div>

39
</div>

<!-- Text input-->

<div class="form-group">
<label class="col-md-12 control-label title1" for="email"></label>
<div class="col-md-12">
<input id="email" name="email" placeholder="Enter your email-id" class="form-control input-md"
type="email">

</div>
</div>

<!-- Text input-->

<div class="form-group">
<label class="col-md-12 control-label" for="mob"></label>
<div class="col-md-12">
<input id="mob" name="mob" placeholder="Enter your mobile number" class="form-control input-
md" type="number">

</div>
</div>

<!-- Text input-->

<div class="form-group">
<label class="col-md-12 control-label" for="password"></label>
<div class="col-md-12">
<input id="password" name="password" placeholder="Enter your password" class="form-control
input-md" type="password">

</div>
</div>

<div class="form-group">
<label class="col-md-12control-label" for="cpassword"></label>
<div class="col-md-12">
<input id="cpassword" name="cpassword" placeholder="Conform Password" class="form-control
input-md" type="password">

</div>
</div>
<?php if(@$_GET['q7'])
{ echo'<p style="color:red;font-size:15px;">'.@$_GET['q7'];}?>
<!-- Button -->
<div class="form-group">
<label class="col-md-12 control-label" for=""></label>

40
 <div class="col-md-12">
<input type="submit" class="sub" value="sign up" class="btn btn-primary"/>
</div>
</div>

</fieldset>
</form>
</div><!--col-md-6 end-->
</div></div>
</div><!--container end-->

<!--Footer start-->
<div class="row footer">
<div class="col-md-3 box">
<a href="#" data-toggle="modal" data-target="#login">Admin Login</a></div>
<div class="col-md-3 box">
<a href="feedback.php" target="_blank">Feedback</a></div></div>
<!--Modal for admin login-->
<div class="modal fade" id="login">
<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal"><span aria-
hidden="true">&times;</span><span class="sr-only">Close</span></button>
<h4 class="modal-title"><span style="color:orange;font-family:'typo' ">LOGIN</span></h4>
</div>
<div class="modal-body title1">
<div class="row">
<div class="col-md-3"></div>
<div class="col-md-6">
<form role="form" method="post" action="admin.php?q=index.php">
<div class="form-group">
<input type="text" name="uname" maxlength="20" placeholder="Admin user id" class="form-
control"/>
</div>
<div class="form-group">
<input type="password" name="password" maxlength="15" placeholder="Password" class="form-
control"/>
</div>
<div class="form-group" align="center">
<input type="submit" name="login" value="Login" class="btn btn-primary" />
</div>
</form>
</div><div class="col-md-3"></div></div>
</div>
<!--<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>

41
 </div>-->
</div><!-- /.modal-content -->
</div><!-- /.modal-dialog -->
</div><!-- /.modal -->
<!--footer end-->

</body>
</html>

42
43
 Testing is a process of executing a program with the intent of finding an error. Testing is a crucial
element of software quality assurance and presents ultimate review of specification, design and coding.

System Testing is an important phase. Testing represents an interesting anomaly for the software. Thus a
series of testing are performed for the proposed system before the system is ready for user acceptance
testing.

A good test case is one that has a high probability of finding an as undiscovered error. A successful
test is one that uncovers an as undiscovered error.

Testing Objectives:

1.Testing is a process of executing a program with the intent of finding an error

2.A good test case is one that has a probability of finding an as yet undiscovered error
3.A successful test is one that uncovers an undiscovered error

Testing Principles:

1. All tests should be traceable to end user requirements

2.Tests should be planned long before testing begins

3.Testing should begin on a small scale and progress towards testing in large

4.Exhaustive testing is not possible

5.To be most effective testing should be conducted by an independent third party

The primary objective for test case design is to derive a set of tests that has the highest livelihood for
uncovering defects in software. To accomplish this objective two different categories of test case design
techniques are used. They are

White box testing.

Black box testing.

44
White-box testing:

White box testing focus on the program control structure. Test cases are derived to ensure that all
statements in the program have been executed at least once during testing and that all logical conditions
have been executed.

Block-box testing:

Black box testing is designed to validate functional requirements without regard to the internal workings
of a program. Black box testing mainly focuses on the information domain of the software, deriving test
cases by partitioning input and output in a manner that provides through test coverage. Incorrect and
missing functions, interface errors, errors in data structures, error in functional logic are the errors falling
in this category.

Testing strategies:

A strategy for software testing must accommodate low-level tests that are necessary to verify that
all small source code segment has been correctly implemented as well as high-level tests that validate
major system functions against customer requirements.

Testing fundamentals:

Testing is a process of executing program with the intent of finding error. A good test case is one
that has high probability of finding an undiscovered error. If testing is conducted successfully it uncovers
the errors in the software. Testing cannot show the absence of defects, it can only show that software
defects present.

Testing Information flow:

Information flow for testing flows the pattern. Two class of input provided to test the process. The
software configuration includes a software requirements specification, a design specification and source
code.

45
 Test configuration includes test plan and test cases and test tools. Tests are conducted and all the
results are evaluated. That is test results are compared with expected results. When erroneous data are
uncovered, an error is implied and debugging commences.

Unit testing:

Unit testing is essential for the verification of the code produced during the coding phase and hence
the goal is to test the internal logic of the modules. Using the detailed design description as a guide,
important paths are tested to uncover errors with in the boundary of the modules. These tests were carried
out during the programming stage itself. All units of Vienna SQL were successfully tested.

Integration testing:

Integration testing focuses on unit tested modules and build the program structure that is dictated
by the design phase.

System testing:

System testing tests the integration of each module in the system. It also tests to find discrepancies
between the system and its original objective, current specification and system documentation. The
primary concern is the compatibility of individual modules. Entire system is working properly or not will
be tested here, and specified path ODBC connection will correct or not, and giving output or not are tested
here these verifications and validations are done by giving input values to the system and by comparing
with expected output. Top-down testing implementing here.

Acceptance Testing:

This testing is done to verify the readiness of the system for the implementation. Acceptance testing begins
when the system is complete. Its purpose is to provide the end user with the confidence that the system is
ready for use. It involves planning and execution of functional tests, performance tests and stress tests in
order to demonstrate that the implemented system satisfies its requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test case.

46
Timing Analyzer – also called a profiler, reports the time spent in various regions of the code are areas to
concentrate on to improve system performance.

Coding standards – static analyzers and standard checkers are used to inspect code for deviations from
standards and guidelines.

Test Cases:

Test cases are derived to ensure that all statements in the program have been executed at least once
during testing and that all logical conditions have been executed.
Using White-Box testing methods, the software engineer can drive test cases that
 Guarantee that logical decisions on their true and false sides.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational bounds.
 Exercise internal data structure to assure their validity.
 The test case specification for system testing has to be submitted for review before system testing
commences.

47
48
49
50
51
52
53
FUTURE ENHANCEMENTS:

This application avoids the manual work and the problems concern with it. It is an easy way
to obtain the information regarding the different scheduled examinations information that are
Currently issued.
Well I and my team members have worked hard in order to present an
improved website better than the existing one’s regarding the information about the various activities.
Still, we found out that the project can be done in a better way. Primarily, when we request information
about a particular schedule it just shows the exam date and platform. So, after getting the information we
can get access to the online exam.
The enhancement that we can add the searching option. We can directly
search to the particular student details from this site.

54
55
CONCLUSION:

The package was designed in such a way that future modifications can be done easily. The
following conclusions can be deduced from the development of the project.

 Automation of the entire system improves the efficiency

 It provides a friendly graphical user interface which proves to be better when compared to
the existing system.
 It gives appropriate access to the authorized users depending on their permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is necessary.

56
57
The following books were referred during the analysis and execution phase of the project

 Books Referred:

 BEGINNING PHP 5 --- DAVE MERCER

 BLACK BOOK HTML --- WILEY DREAMTECH

 PHP AND MYSQL WEB DEVELOPMENT --- LUKEWELLING, LAURA

 Websites Referred:

 W3Schools
 JavatPoint
 Stackoverfolw
 GitHub

58