6 Month Industrial Training Report

On

“OES”
Held at

IQAG

Submitted in partial fulfillment of the requirement for the award of the degree of

BACHELORS OF TECHNOLOGY
(CSE)
Under the supervision of

Internal Supervisor: External Supervisor:

Ms. Sonal Arora Mr. Bhupendra
Assistant Professor Developer
CSE IQAG

SUBMITTED BY

ANKIT CHAVAN
DPG Institute of Technology and Management
(Sec 34, Near Hero Honda Chowk, Gurugram -122001)

i
 OES

CANDIDATE’S DECLARATION CERTIFICATE

I hereby certify that the work that is presented in this report entitled
‘OES’ by Ankit Chavan in partial fulfillment of requirement for the
award of degree of BACHELORS OF TECHNOLOGY submitted to the
department of Computer Science & Engineering of DPG Institute of
Technology and Management is an authentic record of my work carried
out during a period of 20th January 2020 to 20th June 2020, under the
supervision of Ms.Sonal Arora.

Signature of Student

This is to certify that the above statement made by the candidate is correct
to the best of my knowledge and belief.

Signature of Supervisor

Signature of HOD

Page ii
 OES

Page iii
 OES

ABSTRACT

The proposed system is a web application which provides a platform to

facilitate a system of learning, evaluation and assessment such that they
not stay confined to the four walls of the classroom. It provides a
platform for paperless, easy and a simple system that can be used by a
person having minimal knowledge of using web applications. In a
traditional system a lot of effort and resource is required for the
managing the learning and assessment process. OES holds two types of
services, one for the Student/Candidate wishing to undertake the exam
and the other for the examiner which may be called an admin for the
particular exam. The proposed system is based on PHP, MySQL and
WAMP.

Page iv
 OES

Acknowledgement

I cannot express enough gratitude to Ms. Sonal Arora (Assistant

Professor, DPGITM) for her generous guidance, help and support
throughout the entirety of the project. She has been a wonderful mentor
giving valuable suggestions throughout.

I express my sincere gratitude to Ms. Rashmi (HOD, CSE ) for her valuable
advice, continuous encouragement and suggestions.

I am highly indebted to Mr. Bhupendra Singh for his generous help. This
project would not have been possible without his support and help. I
extend my thanks to my colleagues at IQAG for their encouragement and
help.

Ankit Chavan

Page v
 OES

List of Figures

Figure No Title Page No.

1.1 Few IQAG Clients 2
4.1 List of Technologies Used 7
7.1 Data Flow Diagram Notations 26
7.2 Use Case Notations 27
7.3 Admin Data Flow Diagram 28
7.4 Candidate Data Flow Diagram 29
7.5 Admin Use Case 30
7.6 Candidate Use Case 31
8.1 Agile Methodology 34
11.1 Registration Page 41
11.2 Login Page 42
11.3 Exam Selection Page 43
11.4 Examination View 44
11.5 Result View 45
11.6 Admin Login 46
11.7 Admin Dashboard 47
11.8 Test Creation 48
11.9 Exam Resources Provision 49
11.10 Result View 50

Page vi
 OES

Table of Contents

Title Page
Declaration of Student ii
Certificate of the Guide iii
Abstract of the Project iv
Acknowledgement v
List of Figures vi
Table of Contents vii

1. Company Introduction 1
1.1. Mission 1
1.2. Vision 1
1.3. Aim 2
1.4. Few of IQAG’s clients 2

2. Project Explanation 3
2.1. Introduction 3
2.2. Problems with existing system 3
2.3. Solution 4
2.4. Objectives of OES 4
2.5. Benefits of OES 5

3. Requirements of project 6
3.1. Hardware requirements 6
3.2. Software requirements 6

Page vii
 OES

4. Technologies Used 7
4.1. Why these technologies? 8
4.2. Front end Technologies 8
4.2.1. Html 8
4.2.2. CSS 9
4.2.3. JavaScript 10
4.2.4. PHP 11
4.2.5. Bootstrap 12
4.3. Backend Technology 14
4.3.1. MySQL 14
4.3.2. SQL 15

5. Literature survey 16
5.1. Existing System 16
5.2. Proposed System 16
5.2.1. Feasibility Study 17
5.2.2. Economic feasibility 17
5.2.3. Technical feasibility 18

6. System Analysis and design 19

6.1. Analysis of proposed system 19
6.2. Requirement Analysis 20
6.2.1. Requirement Analysis in this project 20
6.2.2. Requirement Specifications 22
6.3. System Design 22
6.3.1. Objectives and design 23
6.3.2. Logical design 23
6.4. Performance Requirement 24
Page viii
 OES

7. Structure of project 25
7.1. System design 25
7.2. Data Flow Diagrams 25
7.3. Use case diagram 26

8. Methodology used 33
8.1. Problems with traditional approach 33
8.2. Agile methodology 33

9. Testing 35
9.1. Testing 35
9.2. Testing strategies 35
9.2.1. Unit testing 35
9.2.2. Integration testing 37
9.3. Test approach 37
9.3.1. Bottom approach 37
9.3.2. Top down approach 38
9.4. Validation 38
9.5. Evaluation 38
9.6. Maintenance 39

10. Future scope 40

11. Results 41
11.1. Registration page 41
11.2. Login Page 42
11.3. Exam selection view 43

Page ix
 OES

11.4. Examination view 44

11.5. Result view 45
11.6. Admin login 46
11.7. Admin dashboard 47
11.8. Test creation 48
11.9. Exam resources provision 40
11.10. Result view 50

References 51
Appendix 52

Page x
 Chapter 1
Company Introduction

Independent Qualitative Assessors Guild - IQAG Private Limited is an ISO

9001:2015 certified company providing skill assessment services. Formed
on 21st March 2014 with a pool of Assessors and Industry experts, in the
Domain of Assessments and Skilling from various Sectors, the company is
based out of Hyderabad, India. IQAG provides a transparent assessment
ecosystem using a blended approach of qualified Assessor’s network,
Localized Test Centers, Practical/Viva-voice evaluation, Industry Vetted
Question Banks

1.1 Mission: IQAG's Mission is to provide qualitative skill assessment,

certification and analytics services to the skilled youth across the
world.

1.2 Vision: To provide premier assessment in the continuously evolving

global skill trainings domain and become an integral part of the
skilling revolution. Implementing a transparent assessment
ecosystem using a blended approach of localized assessor’s network,
localized test centers, real-time practical evaluation, industry vetted
skill question banks and online technology platform.

1
 OES

1.3 Aim: To be the trusted interface between trained youth, training

partners, skill councils and industry providing impeccable
assessment standards and impartial feedback mechanism\\
.
1.4 Few Of IQAG clients

Fig.1.1 Few of IQAG’s clients

Page 2
 OES

Chapter 2
Project Explanation

2.1 Introduction
OES is an examination and assessment portal for organizations and
institutes to take exams. Organizations and Institutes can design their
own test and assign test to candidates.

It provides a hassle free platform for paperless, easy and a simple system
that can be used by a person having minimal knowledge of using web
applications.

2.2 Problems with existing system

 Limited Reach: The traditional way has a limited reach and is not
accessible by everyone.

 Large Money Investment: Every time an assessment/exam has to

take place a large amount of capital is spent to provide basic
necessities such as pen, paper and other basic requirements.

 Complex and Time Consuming: From the initial step that is of

designing the exam to the commencement that is the declaration
of result the whole process is complex and time consuming.

Page 3
 OES

 Not Efficient: Traditional way is not entirely efficient and may

encounter a lot of hiccups along the way.

 Not economical: in current scenario the traditional way of taking

exams/assessments is not a viable option. There is a requirement
of a system to reduce the expenditure and resources.

2.3 Solution
OES includes a comprehensive system, using which assessment and
exams can be done in a much economical and secure way.
It provides an easy and efficient way to make the entire process of the
assessment a simple and economical one. Different types of assessments
can be done as per the requirement without any hassle.

2.4 Objectives of OES

 To develop an app that could be used for assessment ensuring
safe and procedured way of conducting exams.
 It reduces the hectic job of manually assessing the answers,
instead the system will review the response in no time.
 The results are shown immediately.

2.5 Benefits of OES

 It saves paper: There is no need to print an exam for students and
hand them out. It saves paper and saves trees.

Page 4
 OES

 Saves Money: There no need to buy paper. It saves the extra

expenses such as pen, logistics etc.

 Saves Time: One can set up an exam in such a way that will auto
grade itself if only multiple choice questions are used, hence there is
no need to check the exam again.

 Efficient: Since the exams are auto graded the efficiency is higher
than that of the traditional way.

Page 5
 OES

Chapter 3
Requirements of Project

3.1Hardware Requirements

• Client
Processor : Intel Core to Duo or advance
Ram : 2 GB
Hard disk : 10 GB

• Developer
Processor : Intel i3 processor or advance
Ram : 4 GB
Hard disk : 100 GB

3.2 Software Requirements

• Client
Web Browser : Chrome, Mozilla Firefox etc.
Operating System : Any

• Developer
Web Browser : Chrome, Mozilla Firefox etc.
IDE : Visual Studio Code
Database : MySQL
Programming : PHP, HTML, CSS, JavaScript
Operating System : Windows

Page 6
 OES

Chapter 4
Technologies Used

OES is developed using promising technologies. PHP, HTML, CSS,

JavaScipt, SQL, MySQL and a WAMP Stack. The front end of the project
was designed using HTML, CSS, PHP and JavaScript. SQL and MySQL on
the other hand provide the project the crucial support from backend.

Figure 4.1 List of Technologies used

Page 7
 OES

4.1 Why these technologies?

Mostly the technologies used are open source and are widely used and
being implemented in the real world. PHP and MySQL are the most
popular open source database and scripting in the current trend. PHP is a
server-side scripting language; hence it creates significant dynamic pages
with customized features. One of the main benefits of using PHP and
MySQL is, it provides an interactive, user-friendly website and also
facilitates visitors to openly interact while producing a genuinely dynamic
and flexible content. Similarly using HTML, CSS and JavaScript makes the
frontend part of the development a sight to watch. It provides an
impeccable GUI which is very interactive and easy to use as well.

4.2 Front-End Technology

4.2.1 HTML
HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be
embedded into the rendered page. HTML provides a means to create
structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items. HTML elements
are delineated by tags, written using angle brackets. Tags such as <img />
and <input /> directly introduce content into the page. Other tags such as
<p> surround and provide information about document text and may
include other tags as sub-elements. Browsers do not display the HTML
tags, but use them to interpret the content of the page.

Page 8
 OES

 HTML is the standard markup language for creating Web pages.

 HTML stands for Hyper Text Markup Language
 HTML describes the structure of Web pages using markup
 HTML elements are the building blocks of HTML pages
 HTML elements are represented by tags
 It is used to create the basic structure of website. It is the building
base of all the front end technologies.

4.2.2 CSS
Cascading Style Sheets (CSS) is a style sheet language used for
describing the presentation of a document written in a markup language
like HTML.CSS is a cornerstone technology of the World Wide Web,
alongside HTML and JavaScript.CSS is designed to enable the separation
of presentation and content, including layout, colors, and fonts. This
separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable
multiple web pages to share formatting by specifying the relevant CSS isa
separate .css file, and reduce complexity and repetition in the structural
content.

Page 9
 OES

 CSS stands for Cascading Style Sheets.

 CSS describes how HTML elements are to be displayed on screen,
paper, or in other media.
 CSS saves a lot of work. It can control the layout of multiple web
pages all at once.

4.2.3 JavaScript
JavaScript is incredibly versatile. You can start small, with carousels,
image galleries, fluctuating layouts, and responses to button clicks. With
more experience, you'll be able to create games, animated 2D and 3D
graphics, comprehensive database-driven apps, and much more!
JavaScript itself is fairly compact yet very flexible. Developers have
written a large variety of tools on top of the core JavaScript language,
unlocking a vast amount of extra functionality with minimum effort.
These include:
Browser Application Programming Interfaces (APIs) — APIs built into web
browsers, providing functionality like dynamically creating HTML and
setting CSS styles, collecting and manipulating a video stream from the
user's webcam, or generating 3D graphics and audio samples.

Page 10
 OES

• Third-party APIs to allow developers to incorporate functionality in

their sites from other content providers, such as Twitter or Facebook.
• Third-party frameworks and libraries you can apply to your HTML to
allow you to rapidly build up sites and applications.
• JavaScript (JS) is a programming language mostly used to dynamically
script WebPages on the client side.
• JavaScript provide inbuilt functions that make client side programming
very easy.
• It is used for client side verification, which help to reduce the load on
server.

4.2.4 PHP

Originally designed in 1994 by Rasmus Lerdorf, PHP has been

evolving since. PHP is a general purpose programming language at
server-side used for the purpose of scripting that is primarily

Page 11
 OES

designed to develop websites. Initially, it meant Personal Home

Page which has now been changed to Hypertext Preprocessor.

The leading social networking sites such as Facebook and reputed

organizations such as Harvard University are both based on PHP
which makes PHP popular and increases its credibility. This is so
because the websites developed using PHP can easily be improved,
maintained and updated from time to time.
What distinguishes PHP from something like client-side JavaScript is
that the code is executed on the server, generating HTML which is
then sent to the client. The client would receive the results of
running that script, but would not know what the underlying code
was. You can even configure your web server to process all your
HTML files with PHP, and then there's really no way that users can
tell what you have up your sleeve.

4.2.5 Bootstrap
Bootstrap is a free front-end framework for faster and easier
web development. Bootstrap includes HTML and CSS based design
templates for typography, forms, buttons, tables, navigation,

Page 12
 OES

modals, image carousels and many other, as well as optional

JavaScript plug-ins. Bootstrap also gives you the ability to easily
create responsive designs
Bootstrap is an open source toolkit for developing with HTML, CSS,
and JS. Quickly prototype your ideas or build your entire app with
our Sass variables and mixins, responsive grid system, extensive
prebuilt components, and powerful plugins built on jQuery.

Advantages of Bootstrap:
• Easy to use: Anybody with just basic knowledge of HTML and CSS
can start using Bootstrap
•Responsive features: Bootstrap's responsive CSS adjusts to
phones, tablets, and desktops
•Browser compatibility: Bootstrap is compatible with all modern
browsers

Page 13
 OES

4.3 Backend Technology

4.3.1 MySQL
MySQL is a freely available open source Relational Database
Management System (RDBMS) that uses Structured Query Language
(SQL).

SQL is the most popular language for adding, accessing and

managing content in a database. It is most noted for its quick
processing, proven reliability, ease and flexibility of use. MySQL is an
essential part of almost every open source PHP application.
MySQL is a component of the LAMP/WAMP web application
software stack, which is an acronym for Linux/Windows, Apache,
MySQL, and Perl/PHP/Python. MySQL is used by many database-
driven web applications, including Drupal, Joomla, phpBB, and Word
Press. MySQL is also used by many popular websites, including
Facebook, Flickr, MediaWiki, Twitter, and YouTube.

Page 14
 OES

4.3.2 SQL
SQL stands for Structured Query Language. SQL is used to
communicate with a database. According to ANSI (American
National Standards Institute), it is the standard language for
relational database management systems. SQL statements are used
to perform tasks such as update data on a database, or retrieve data
from a database. Some common relational database management
systems that use SQL are: Oracle, Sybase, Microsoft SQL Server,
Access, Ingres, etc. Although most database systems use SQL, most
of them also have their own additional proprietary extensions that
are usually only used on their system. However, the standard SQL
commands such as "Select", "Insert", "Update", "Delete", "Create",
and "Drop" can be used to accomplish almost everything that one
needs to do with a database.

 Using queries SQL can quickly and efficiently retrieve data from
a database.
 SQL supports portability to a great extent.

Page 15
 OES

CHAPTER 5
Literature Survey

5.1 Existing System

Current system has a lot of problems and constraints.
The existing system is a manual system which is based on pen and paper.
It also limits the learning and assessment within four walls. It requires a
lot of manual efforts. It also requires a lot of time and capital investment
to gather the necessary resources. With the existing system it takes a
substantial amount of time to generate the result, Moreover Managing
the test and providing suitable environment is a big hassle.

5.2 Proposed System

The OES is to replace the existing manual system with a better one.
It can provide a suitable environment to take the test. Is a system which
is cheap and easy to maintain. It is a system which is time efficient and
secure. A system which does not bound the process of learning within the
four walls. A system which eases the burden on both the student taking
the exam and the assessor.

Page 16
 OES

5.2.1 Feasibility Study

Preliminary investigation examines project feasibility;
The likelihood the system will be useful to the organization. The
main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and
debugging old running system. All systems are feasible if they are
given unlimited resources and infinite time.

There are aspects in the feasibility study portion of the preliminary

Investigation:

i. Technical Feasibility
ii. Operation Feasibility
iii. Economic Feasibility

5.2.2 Technical Feasibility

The technical issue usually raised during the feasibility stage of the
Investigation includes the following:
i. Does the necessary technology exist to do what is suggested?
ii. Do the proposed equipment have the technical capacity to hold
the data required to use the new system?
iii. Will the proposed system provide adequate response to
inquiries, regardless of the number or location of users?
iv. Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of
access and data security?

Page 17
 OES

5.2.3 Operational Feasibility

i. User-friendly: Both the admin and candidate feel comfortable
and confident while using the software. He should be able to find all
the related data and details and not be able to see unrelated data.
It should be easy to understand and use.

ii. Reliability: Project should be able to handle all the errors and
Exceptions.

iii. Security: The web server and database server should be

protected from hacking, virus etc.

iv. Portability: Web potable should be able to work in all browsers

and operating systems. And should to able to shift to other server if
something goes wrong.

v. Maintenance: Finish project should be easy to maintain and cost

of maintenance should be less.

Page 18
 OES

Chapter 6
System Analysis and Design

6.1 Analysis of the proposed system

System Analysis is first stage according to System Development Life Cycle
model. This System Analysis is a process that starts with the analyst.
Analysis is a detailed study of the Various operations performed by a
system and their relationships within and outside of the system. One
aspect of analysis is defining the boundaries of the system and
determining whether or not a candidate system should consider other
related systems. During analysis, data are collected on the available files,
decision points, and transactions handled by the present system. Logical
system models and tools that are used in analysis. Training, experience,
and common sense are required for collection of the information needed
to do the analysis.

OES is a distributed project. A distributed system is a network that

consists of autonomous computers that are connected using a
distribution middleware. They help in sharing different resources
and capabilities to provide users with a single and integrated
network.

Page 19
 OES

6.2 Requirement Analysis

The requirement phase basically consists of three activities:
6.2.1 Requirement Analysis in this Project
Requirement Analysis is a software engineering task that bridges the gap
between system level software allocation and software design. It
provides the system engineer to specify software function and
performance indicate software’s interface with the other system
elements and establish constraints that software must meet
The basic aim of this stage is to obtain a clear picture of the needs and
requirements of the end-user and also the organization. Analysis involves
interaction between the clients and the analysis. Usually analysts
research a problem by asking questions and reading existing documents.
The analysts have to uncover the real needs of the user even if they don’t
know them clearly. During analysis it is essential that a complete and
consistent set of specifications emerge for the system. Here it is essential
to resolve the contradictions that could emerge from information got
from various parties. This is essential to ensure that the final
specifications are consistent.
It may be divided into 5 areas of effort.

 Problem recognition
 Evaluation and synthesis
 Modeling
 Specification
 Review

Page 20
 OES

Each Requirement analysis method has a unique point of view. However

all analysis methods are related by a set of operational principles. They
are-

 The information domain of the problem must be represented and

understood.
 The functions that the software is to perform must be defined.
 The behavior of the software as a consequence of external events
must be defined.
 The models that depict information function and behavior must be
partitioned in a hierarchical or layered fashion.
 The analysis process must move from essential information to
implementation detail.
The main aim in this stage is to assess what kind of a system would be
suitable for a problem and how to build it. The requirements of this
system can be defined by going through the existing system and its
problems. The discussion is about system to be built and their
expectations from it.
The steps involved would be

 Problem Recognition: The main problem here is the wastage of

resources such as time, money, human resource and the
boundation of an assessment within a confined area.

 Evaluation and Synthesis: The system has to be designed only after

complete evaluation of the existing one, upon which we can see
that a lot depends on the way the assessments are conducted. The

Page 21
 OES

proposed system is such that there is optimal conduction of exams

without the wastage of resources.

 Specification: The specifications from the user, a way to conduct

exams, generate results, manage exams, upload study material, get
a comprehensive view, all requirements were met .

6.2.2 Requirements Specification

The requirement specification document is produced at the end of
Analysis of the system. This document is a very comprehensive document
& contains all the User requirements & Analysis diagrams. The
Requirements are broadly divided into two groups
Student: Any candidate undergoing assessment is a student. A student
can view and modify the personal information, assess course material,
change password, take exam and view results.
Admin: Admin is the person conducting the online assessment. They can
create exams, view results, upload course materials.

6.3 System Design

The most creative and challenging phase of the life cycle is system design.
The term design describes a final system and the process by which it is
developed. It refers to the technical specifications that will be applied in
implementations the candidate system. The design may be defined as
“the process of applying various techniques and principles for the
purpose of defining a device, a process or a system in sufficient details

Page 22
 OES

to permit its physical realization”.

The importance of software design can be stated in a single word
“Quality”. Design provides us with representations of software that can
be assessed for quality. Design is the only way that we can accurately
translate a customer’s requirements into a finished software product or
system without design we risk building an unstable system, that might fail
it small changes are made or may be difficult to test, or one who’s quality
can’t be tested. So it is an essential phase in the development of a
software product.
System design is transition from a user oriented, document oriented to
programmers or database personnel. The design is a solution, a “how to”
approach to the creation a new system. This is composed of several
steps. It provides the understanding and procedural details necessary for
implementing the system recommended in the feasibility study.
6.3.1 Objectives of Design
System design is like a blue print for a building, it specifies all the
features that are to be in the finished product. Design states how to
accomplish objectives determined in the analysis phase.
6.3.2 Logical Design
The design of an information system produces the details that state how
a system will meet the requirements identified during systems analysis.
This stage is logical design.
6.3.2.1 Module Description:
We have identified the following two major modules:

Page 23
 OES

 Admin Module: This module is responsible for managing the tests,

uploading the study material, generating results and a
comprehensive view of the candidates and the questions

 Student Module: This module focuses on the candidate experience

of taking examination. Functionalities include register, login,
undertaking a test and viewing results.

6.4 Performance Requirement

Performance is measured in terms of the output provided by the
application. Requirement specification plays an important part in the
analysis of a system. Only when the requirement specifications are
properly given, it is possible to design a system, which will fit into
required environment. It rests largely with the users of the existing
system to give the requirement specifications because they are the
people who finally use the system. This is because the requirements have
to be known during the initial stages so that the system can be designed
according to those requirements. It is very difficult to change the system
once it has been designed and on the other hand designing a system,
which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as
given below:
• The system should be able to interface with the existing system
• The system should be accurate
• The system should be better than the existing system.
Page 24
 OES

Chapter 7
Structure of Project

7.1 System Design:

Systems design is the process or art of defining the architecture,
components, modules, interfaces, and data for a system to satisfy
specified requirements. One could see it as the application of systems
theory to product development. There is some overlap and synergy
with the disciplines of systems analysis, systems architecture and
systems engineering

7.2 Data Flow Diagram (DFDs):

A data flow diagram (DFD) maps out the flow of information for any
process or system. It uses defined symbols like rectangles, circles and
arrows, plus short text labels, to show data inputs, outputs, storage
points and the routes between each destination. Data flowcharts can
range from simple, even hand-drawn process overviews, to in-depth,
multi-level DFDs that dig progressively deeper into how the data is
handled.

Page 25
 OES

7.2.1 DFD Notations:

Fig.7.1 Data Flow diagram notations

7.3 Use case Diagram:

A Use case diagram at its simplest is a representation of a user's
interaction with the system that shows the relationship between the user
and the different Usecases in which the user is involved. A use case
diagram can identify the different types of users of a system and the
different use cases and will often be accompanied by other types of
diagrams as well.

Page 26
 OES

Use case Notations:

Fig 7.2 Use case Notations

Page 27
 OES

OES Data Flow Diagrams

a) Level 1 (admin)

Figure 7.3 Admin DFD

Explanation
Entity:
Admin: This is the organizational admin at level such as school,
College or an assessment organization.

Page 28
 OES

Processes:
Login: Admin Logins using the credentials to the account and it takes
the admin to the dashboard.
Generate Paper: This process allows the admin to generate the
assessment that can be then taken by the students.
View Result: This process shows the results of the tests that are given to
the candidate.
Change Password: This process allows the admin the functionality of
changing password.
Upload Material: This allows the admin to upload the related course
material.

b) Level 2 (candidate)

Fig. 7.4 Candidate DFD

Page 29
 OES

Here the candidate has two options that is register or login.

Login: The candidate can login using the credentials and have access to ll
the features.
Study store: Here the candidate can access the study material that has
been provided to the candidate by the admin.
Give Test: Here the candidate can appear for the assessment.
View Result: Here the candidate has the provision to view the result.

Use Case Diagram for OES

Admin

Fig 7.5 Admin Use Case

Page 30
 OES

Explanation:
This use case defines the working and responsibilities of the admin.
After login admin goes to dashboard from where it can perform the
following operations.

 Generate test.
 View result
 Upload exam material.
 Get comprehensive details.

Candidate:

Fig 7.6 Candidate Use Case

Page 31
 OES

Explanation:
This use case defines the use case of a candidate
Register: A candidate can register for the use of the web application.
Login: The candidate can login using the credentials and have access to ll
the features.
Download resources: Here the candidate can access the study material
that has been provided to the candidate by the admin.
Give Test: Here the candidate can appear for the assessment.
View Result: Here the candidate has the provision to view the result.

Page 32
 OES

Chapter 8
Methodology Used

8.1 Problems with traditional approach

In traditional software development methodologies like Waterfall model,
a project can take several months or years to complete and the customer
may not get to see the end product until the completion of the project.
To overcome this Agile methodology was introduced. In this methodology
each project is broken up into several ‘Iterations’.

8.2 Agile Methodology

• In this methodology each project is broken up into several ‘Iterations’.
• All Iterations should be of the same time duration (between 2 to 8
weeks).
• At the end of each iteration, a working product should be delivered.
• In simple terms, in the agile approach the project will be broken up into
10 releases (assuming each iteration is set to last 4 weeks).
• Rather than spending 1.5 months on requirements gathering, in agile
software development, the team will decide the basic core features that
are required in the product and decide which of these features can be
developed in the first iteration.

Page 33
 OES

• Any remaining features that cannot be delivered in the first iteration

will be taken up in the next iteration or subsequent iterations, based on
priority.
• At the end of the first iterations, the team will deliver a working
Software with the features that were finalized for that iteration.
• There will be 10 iterations and at the end of each iteration the
customer is delivered working software that is incrementally enhanced
and updated with the features that were shortlisted for that iteration.

Fig 8.1 Agile Methodology

Page 34
 OES

Chapter 9
Testing

9.1 Testing:
Testing is a process, which reveals errors in the program. It is the major
quality measure employed during software development during software
development.
During testing, the program is executed with a set of test cases and the
output of the program for the test cases is evaluated to determine if the
program is performing as it is expected to perform.

9.2Testing in strategies:
In order to make sure that the system does not have errors, the different
levels of testing strategies that are applied at differing phases of software
development are:

9.2.1 Unit Testing:

Unit Testing is done on individual modules as they are completed and
become executable. It is confined only to the designer's requirements.
Each module can be tested using the following two Strategies:
 Black Box Testing
 White Box Testing

Page 35
 OES

Black Box Testing

In this strategy some test cases are generated as input conditions that
fully execute all functional requirements for the program. This testing has
been uses to find errors in the following categories:
i. Incorrect or missing functions
ii. Interface errors
iii. Errors in data structure or external database access
iv. Performance errors
v. Initialization and termination errors.
In this testing only the output is checked for correctness. The logical flow
of the data is not checked.

White Box Testing

In this the test cases are generated on the logic of each module by
drawing flow graphs of that module and logical decisions are tested on all
the cases. It has been uses to generate the test cases in the following
cases:
i. Guarantee that all independent paths have been executed.
ii. Execute all logical decisions on their true and false Sides.
iii. Execute all loops at their boundaries and within their operational
bounds
iv. Execute internal data structures to ensure their validity.

Page 36
 OES

9.2.2 Integration Testing

Integration testing ensures that software and subsystems work together
a whole. It tests the interface of all the modules to make sure that the
modules behave properly when integrated together.
• System Testing:
It involves in-house testing of the entire system before delivery to the
user. It's aim is to satisfy the user the system meets all requirements of
the client's specifications.

• Acceptance Testing:
It is a pre-delivery testing in which entire system is tested at client's site
on real world Data to find errors

9.3 Test Approach:

Testing can be done in two ways:
• Bottom up approach
• Top down approach

9.3.1 Bottom Up Approach:

Testing can be performed starting from smallest and lowest
level modules and proceeding one at a time. For each module in bottom
Page 37
 OES

up testing a short program executes the module and provides the needed
data so that the module is asked to perform the way it will when
embedded within the larger system. When bottom level modules are
tested attention turns to those on the next level that use the lower level
ones they are tested individually and then linked with the previously
examined lower level modules.
9.3.2 Top Down Approach:
This type of testing starts from upper level modules. Since the
detailed activities usually performed in the lower level routines are not
provided stubs are written. A stub is a module shell called by upper level
module and that when reached properly will return a message to the
calling module indicating that proper interaction occurred. No attempt is
made to verify the correctness of the lower level module.

9.4 Validation:
The system has been tested and implemented successfully and thus
ensured that all the requirements as listed in the software requirements
specification are completely fulfilled. In case of erroneous input
corresponding error messages are displayed.

9.5 Evaluation:
In evaluation we prepare the team to evaluate the system. The review
team prepares a formal review plan around the objectives of the review,
the type of evaluation to be carried out and the time schedule required.
An overall plan covers the following areas:
Page 38
 OES

Administrative Plan:
Review area objectives, operating costs, actual operating
performance and benefits.

Personnel Requirements Plan:

Review performance objectives and training performance to data.

Hardware Plan:
Review performance specifications. All plans have been done by
taken proper care and seriousness and each module is evaluated using
simulated data. This review not only evaluated how well the current
system is designed and implemented, but also is a valuable source of
information that can be applied to the next system project.

9.6 Maintenance:
Maintenance is the last part of the System Development Life
Cycle that is actually the implementation of the post-implementation
review plan. When this system is installed it is used for long period. The
average life of a system is 4 to 6 years and maximum used for 10 years.
However, this period of use brings with it the need to continually
maintain the system, but this system can be modified and new
technologies can be used which are prevalent in market at that period of
time.

Page 39
 OES

Chapter 10
Future Scope

OES with its features and capabilities looks very promising for the
following fields:

 OES can be used by institutions to perform assessments

 OES can be used by college’s schools to perform assessments as it is
a faster way of handling the overall assessments.
 It can be replace any offline assessment system which would end up
saving a ton of resources.
 It provides the feature of taking an assessment through any part of
the world
 It can be used to conduct assessments in difficult times, such as the
one we are going through now.

Page 40
 OES

Chapter 11
Results

11.1 Registration Page

Fig 11.1: Registration page of OES

By the above page Candidate can register to OES by providing the
required details like name, address, DoB and other details.

Page 41
 OES

11.2 Login Page

Fig. 11.2 Login Page

If the user is already registered he can provide the credentials i.e.
username and password. If the user forgets the password, then he can
click on the “Forgot Password” link to retrieve the password.

Page 42
 OES

11.3 Exam selection View

Fig. 11.3 Exam selection view

This is the exam selection view. Here the candidate can select the exam
they wish to appear for and the start the examination.

Page 43
 OES

11.4 Examination View

Fig. 11.4 Examination view

This is the examination view of OES, here the candidate can select the
response and move to the next as well as previous question.

Page 44
 OES

11.5 Result View

Fig 11.5 Result view for candidate

Here the candidate can view the result which is generated as well as see
previous results as well

Page 45
 OES

11.6 Admin Login

Fig 11.6 Login Page of Admin

By using this page the admin can login into the dashboard by providing
the username and password

Page 46
 OES

11.7 Admin Dashboard

Fig 11.7 Admin dashboard

This is the dashboard view of the admin, here the admin can see all the
necessary details at a glance.

Page 47
 OES

11.8 Test creation

Fig 11.8 Test creation by admin

This is where the admin can create the tests that can be then undertaken
by the students.

Page 48
 OES

11.9 Exam resources provision

Fig 11.9 Exam resource provision by Admin

Here the admin can upload the required exam materials for the students
to use.

Page 49
 OES

11.10 Result view

Fig.11.10 Result view for admin

Here the admin can see the various results that are present

Page 50
 OES

References

Websites:
[1] Https://getbootstrap.com/
[2] Https://w3school.com
[3] Https://PHPbuddy.com
[4] Https://sitepoint.com
[5] Https://www.xampserver.com.em/

Books:
[1] Mastering HTML, CSS & JavaScript Web Publishing – Lenny
Kyrin
[2] Modern PHP -Robert Dwight

Page 51
 OES

Appendix

Appendix -A
Glossary:
 WAMP: WAMP stands for Windows Apache MySQL and PHP. Its
software stack that is used for development
 Web Stack: It is the set of technologies that a company or a person
use to develop website
 Boilerplate: In computer programming, boilerplate code or
boilerplate refers to sections of code that have to be included in
many places with little or no alteration. It is often used when
referring to languages that are considered verbose, i.e. the
programmer must write a lot of code to do minimal jobs.
 Framework: In general, a framework is a real or conceptual
structure intended to serve as a support or guide for the building of
something that expands the structure into something useful.
 SQL: SQL is a domain-specific language used in programming and
designed for managing data held in a relational database
management system (RDBMS).

Page 52
 OES

Appendix -B

List of Abbreviations:
PHP: Hypertext Preprocessor Language
HTML: Hypertext Markup Language
CSS: Cascading Style sheets
WAMP: Windows, Apache, MySQL and PHP
JS: JavaScript
SQL: Structured Query Language
DFD: Data Flow Diagram

Page 53