God’s Eye (Exam Monitoring System)

CSE-413 MAJOR PROJECT (Phase-1)

Submitted in partial fulfillment for the award of the degree of
BACHELOR OF TECHNOLOGY
(Computer Science and Engineering)

Submitted to
INDIAN INSTITUTE OF INFORMATION TECHNOLOGY
BHOPAL (M.P.)

Submitted by
Project Group Number: 2023-MP-VII-G3

Nikhil Kumar (20U02005)

Satyam Lodhi (20U02044)

Under the supervision of

Dr. Sonal Chandel
A.P. (computer Science & Engineering)

NOVEMBER 2023
 INDIAN INSTITUTE OF
INFORMATION TECHNOLOGY
BHOPAL (M.P.)

CERTIFICATE

This is to certify that the Major project entitled “God’s Eye (Exam Monitoring System)”,
submitted by Nikhil Kumar, Satyam Lodhi in partial fulfillment of the requirements for the
award of the degree of Bachelor of Technology in Computer Science & Engineering. This
document is comprehensive planning of the proposed work of need to completed in final
semester for final evaluation.

Date: 06/11/2023

Dr. Sonal Chandel Dr. Gagan Vishwakarma

Asst. Professor, Computer Science Major Project Co-Ordinator
& Engineering Computer Science & Engineering
IIIT Bhopal (M.P.) IIIT Bhopal (M.P.)
 INDIAN INSTITUTE OF
INFORMATION TECHNOLOGY
BHOPAL (M.P.)

DECLARATION

We hereby declare that the following major project entitled “God’s Eye (Exam Monitoring
System)” presented in the is the partial fulfillment of the requirements for the award of the
degree of Bachelor of Technology in Computer Science & Engineering. It is an authentic
documentation of our original work carried out under the able guidance of Dr. Sonal
Chandel. The work has been carried out entirely at the Indian Institute of Information
Technology, Bhopal. The project work presented has not been submitted in part or whole to
award of any degree or professional diploma in any other institute or organization.

We, with this, declare that the facts mentioned above are true to the best of our knowledge. In
case of any unlikely discrepancy that may occur, we will be the ones to take responsibility.

Nikhil Kumar (20U02005)

Satyam Lodhi (20U02044)

 AREA OF WORK

Exam monitoring system is a technology-based solution designed to help ensure the integrity
and security of online exams and assessments. This area of work typically involves a
combination of software, hardware, and policies to prevent cheating and maintain the
credibility of online exams. Here are some key aspects of work in this area:

 Software Development: Building and maintaining the software components of the

monitoring system. This includes creating the application that students use to take
exams, as well as the monitoring software that tracks their activity during the test.

 User Interface Design: Designing user-friendly interfaces for students and

instructors to access the system, schedule exams, and review reports.

 Security Measures: Implementing security protocols to ensure that the exam

environment is tamper-proof. This includes protecting against unauthorized access,
screen recording, copy-pasting, and the use of external materials.

 Biometric Authentication: Integrating biometric authentication methods such as

facial recognition or fingerprint scans to verify the identity of test-takers.

 Live Proctoring: Developing and maintaining the technology for live proctoring,
where a proctor monitors students in real-time during the exam to detect and prevent
cheating.

 AI and Machine Learning: Implementing AI and machine learning algorithms to

detect cheating behaviors, like using forbidden materials, looking away from the
screen, or having someone else in the room.

 Data Privacy and Compliance: Ensuring that the system complies with data privacy
regulations and that personal information of test-takers is handled securely.
  Analytics and Reporting: Providing tools for instructors and administrators to
review the data collected during exams and generate reports on suspicious activities.

 Integration with Learning Management Systems: Integrating the monitoring

system with existing learning management systems (LMS) and assessment tools that
educational institutions use.

 Scalability and Performance: Ensuring that the system can handle a large number of
concurrent users, especially during peak exam periods.

 Technical Support and Maintenance: Providing ongoing technical support to users

and maintaining the system to address bugs, updates, and improvements.

 Training and Documentation: Developing training materials and documentation for

instructors, proctors, and students to use the monitoring system effectively.

 Policy and Compliance Development: Collaborating with educational institutions to

establish clear policies and guidelines for the use of the monitoring system, including
addressing issues related to student privacy and exam scheduling.

 Research and Development: Staying up-to-date with the latest advancements in

online exam monitoring, including new technologies, best practices, and academic
research.

 Customer Support and Feedback: Engaging with users to gather feedback and
make continuous improvements to the system based on their needs and experiences.

Working on a exam monitoring system requires a multidisciplinary approach, combining

expertise in software development, security, education, and user experience design. It's an
important area of work, particularly with the growing trend of online education and remote
learning.
 TABLE OF CONTENT
S.no Title Page No.
Certificate
Declaration
Area of work
1 Introduction 1
2 Literature review or Survey 2
3 Methodology & Work Description 3
4 Requirement Analysis 4
5 Design - Proposed flowchart/ DFD/ Block Diagram 5
6 Implementation & Coding 6
7 Testing 7
8 Summary of chapters 8
9 Conclusion & Future Scope 9
10 References 10
 LIST OF FIGURES
Fig Description Page no.
1 Stream Processing Pipeline
2 Lambda Architecture
3 Kappa Architecture
4 HDFS Architecture
5 Streaming Data Pipeline
6 Kafka Producer & Consumer
7 Multiple Node Multiple Broker Cluster
8 Output of Clusters
9 Output of Clusters for Analysis
 LIST OF TABLES

Table No Description Page no.

1 Comparison of Data Ingestion Methods
2 Analysis of Clusters
 INTRODUCTION

Exam monitoring systems are demand of time in the era of digital world where everything is
swift and nimble. We needed a system which will reduce the workload on the management
time reduction, ease in conducting examination swift monitoring and fast result generation
with least error. Java is very useful for system architecture. The system of assessment
monitoring helps to reduce the difficulties of organizing a broad test, constant monitoring of
students to eliminate any foul play, immediate correction and simultaneous presentation of
the results. In the Scholastic Institute and Training Center, this framework is effectively used
because it helps to administer the exams and get the results in a positive and constructive
manner.

The requirement of modern-day test results is a virtual examination. This system offers
multiple advantages over offline Examination mode. There are many upsides to using an
online exam method. Here are some features of e exams over paper-based exams that should
enable you to start using an online system of tests. This platform is focused on constructs for
multi-threading. The review of results is often carried out online and the generation of results
is at the end of the outcome or may be released at the time of the preference of the host. An
internet — based act allows you the versatility to schedule, evaluate and rate assessment
papers, and students may also have the same or different problems. It is crucial for the further
selection or evaluation process phase.

Online learning has gained popularity over the years and allows educational institutions to
manage at a underprice and have larger access to more students. To prevent compromising
online authorization, verification should be done regularly or continuously. One of those
processes is Online proctoring, which usually refers to monitoring online testing with a
webcam.

Online proctoring usually refers to proctor (people) who monitor online testing with a
webcam. It involves the process of verifying the person writing the test easily. Insufficient
identity verification method affect the reliability of information and certificates obtained
online. To prevent compromising online authorization, verification should be done regularly

1
or continuously. At the same time, validation should be unobtrusive and non-disruptive and
does not interfere with the learning process.
In addition to certification of online student identity, the desire for full online
education is limited along with the knowledge test. Few are people-based solutions
(unlimited) or fully automated (unreliable). There are also a few scientific methods that
develop the concept of combining few of the identified activities. However, there is no
complete and reliable solution that combines continuous multiple biometric verification
with continuous visual and audio monitoring, and monitoring instrument project to ensure
100% reliable results.

Here is a new web-based system that provides continuous ID service for online
readers with a consistent biometric recognition system. It can be used to reassure students
throughout the exam on a continuous basis.

2
3
 LITERATURE REVIEW
A lot of researches has been conducted on the E assessment and online examination system a
few are stated below:

1. Luecht (2001) focuses his research on online testing in terms of the challenges that
may be encountered. Among the challenges mentioned was the problem of identifying
students who use the system as well as security risks, skills in answering different
questions among students, problems in maintenance and evaluation.

2. Jassó (2008) studied on e-learning in courses at the University of Perugia, known as

e-studium. The study consisted of two stages, through student’s application for online
tests or tests that are made directly to students. The study took two years with four
semester examinations to graduate students in computer science. Their study focused
on the effectiveness of the system used to students.

3. Xue (2006), adapted the online examination system using a mode known as "B/W
Mode". Web server was used to control the tests and provide information to students.
The main goal of the study is to reduce the use of paper and develop a test system that
is safe to use. Among the features utilized was only allow the system to be used after
receiving the application from student to use it.

4. Ria Mae H (2013), studied about an online examination system that can be
administered manually or automatically by lecturers. Lecturers can send questions via
the web and students will answer and send their answers online via the Internet. By
using this online examination system, grading process can be done automatically.
Researcher has conducted a survey about the form and type of examination questions
that will be included in the online examination system.

5. Ria Mae H(2013), telah mendapatkan bentuk dan jenis soalan-soalan peperiksaan,
teknologi demonstrasi modul Moodle Examination dalam Moodle telah dibangunkan
dan pensyarah telah mencuba menggunakan modul Moodle Examination tersebut
seterusnya membincangkan mengenai ciri-ciri yang mereka mahu untuk dilaksanakan

4
 dalam sistem peperiksaan atas talian. Sistem peperiksaan atas talian amat berguna
kepada para pelajar dan pensyarah.

6. Ria Mae H (2013), has received the form and type of examination questions,
technology demonstration module Moodle Examination in Moodle had been
developed and lecturers have tried to use the Moodle Examination module then
discussed about the features that they want to implement in the online examination
system. Online examination system is very useful to students and lecturers. Students
do not need to go to a certain venue to sit for their examinations and the automatic
grading system that exist in the online examination system helps lecturers to give
marks and then issue grades to their students.

7. Huang Darong (2010), studied the online examination system which has combined
Struts2, Spring and Hibernate. Selections to review the combined results are based on
an important function in the online examination is online fields was completed, in
addition the framework S2SH (Struts2 + Spring + Hibernate) have been adopted in
this system by separating multiple levels of control such as, the level views, the level
of control, the level of business logic and level of data access into different
components.

8. According to Huang Darong (2010), an online examination system will also use the
MVC (Model_View_Controller) pattern in the development stage of web system to
achieve loose coupling between stages. The database for this system has been
equipped with delaminating system that will increase the strength of the safety control
system together with authentication Login technology and power role. The results of
this study, the framework Struts2 + Spring + Hibernater may be applied in the online
examination system. Struts2, Hibernate and Spring that has been developed has
gained great merit.

5
 PROPOSED METHODOLOGY AND WORK
DESCRIPTION

3.0 Introduction
In this chapter, the author reviews the research methodology that will be used in developing
and conducting this study will be specified, select the most appropriate methodology that will
suits this study. Also in this chapter, the author reviews the problem statement of the existing
system and what are the causes and probably what solution are needed to overcome this
problems. More also, the fact finding method that will be used in collecting data for solving
the problem statement will be stated as well. The author will also describe the system
development life cycle (SDLC) and what are to be done on each step of the SDLC in regards
to the proposed system.
3.1 Problem Statement
The manual system in theEducation Group has some limited functionalities in their current
system based up the research carried out by the author. In current system, there are only
manual entry of up keeping of the details of the students as well as the examination. For
instance, setting of examination paper by the lecturers is indeed very deteriorate and stressful.
Due to the limited functionalities of the current system, most of the operations are still
executed on paper which in return leads to data redundancy. Though the manual system is
organized in a well-defined way, still the conveying of paper based records of the students
and examination is still very slow. The manual system for conducting examination in the
college continues for weeks or months as well thereby causing both physical and mental
strains to the examinees. Calculation of how many students registered, and verifying of
details of these students in a mouth by hand is quite a difficult task for lecturers as well as to
the staff. At time, the delay in declaration of result cause heavy losses to the students as
generally they cannot be allowed to join further studies or appear in a competitive exams
because of the non- availability of examination result in time. It is also very difficult for each
student to come to the exam center to take their exam, and more difficult for students from
very far distance to reach the exam center. The manual system is still not efficient in carrying
out the whole process of conducting examination in the college. Another factor that takes into

6
account in the manual system is there is always a possibility of errors. However, below are
the most noticeable problems of the manual system that was analyzed by the author.
 There are no database to help store the examination records
 The student registration are always done on paper which leads at times to loss of data
of the students
 A lot of time being consumed for creating the question papers.
 All the examination process are still paper based and its done on Excel
 Students have to reach at the exam center to appear for the exam, and sometimes due
to other problems may not reach ay stipulated time.
 Students are not able to choose their subjects as per choice and or check their exam
results immediately.

The diagram below describes the basic problems of the as-is-system as illustrated with the
help of ishikawa diagram

Figure: Ishikawa diagram

Specifically all the stated problems above will be dealt it with the help of the proposed
system when it is finally implemented, as the online examination system are expected to be
executed effectively and efficiently. The problems to be solved by the proposed system
7
includes:, too much work overload, manual checking of wrong and right answers, declaration
of results takes too long, remote candidates can’t sit for exam, manual setting of question
papers.
So with the implementation of the online examination system, candidates from remote
location will now be able to sit for exam from any location across the globe. With the
proposed system in place, there will no longer be manual checking of wrong and right
answers because every of the examination will now be automated to aid ease the too much
work overload that the lecturers do experience. The proposed system will help solved the
problem of delay in the declaration of examination results because with online examination
system candidates will now be able to see their immediately the exam gets over.
3.2 System Development Methodology Justification (Prototyping)
The chosen methodology for the project is the prototyping. The prototyping methodology
performs the analysis, design and implementation phases concurrently, and all three phases
are performed repeatedly in a cycle until the said system is completed. In this type of
methodology, basic of analysis and design are performed and work immediately begins in a
system prototype with a quick and dirty program that provides a minimal amount of features.
This process continues in a proper cycle until the analyst, users and sponsor agree that the
prototype provides adequate information to be installed and used in the institution, but after
the prototype is installed, the refinement still takes place until it is accepted as the new
system.
However, the first prototype is mainly the first part of the said system that is used, and it is
then shown to the users and project sponsor, who thereafter provide comments. These
comments are now used to reanalyzed, redesign and re-implement a second prototype which
provides a few more features that the formal (Alan,W,T, et all ,2010) . However, the author
decides to use this methodology because a lot of application functionality can be
implemented easily at a very low cost. The prototyping methodology is also used due to the
fact that the proposed system desired needs is said to have a lot of interaction with the end
users. It will help ensures that the end users constantly work with the system and provide a
feedback which can now be incorporated back in the prototype to result in a usable system.
Users are extremely capable of criticizing or anticipating their needs. This methodology are
so ideal for designing good human computer interface system (For example the Online
Examination system). It provides a common life line and reference point for both to the users
and designing in identifying potential problems and solution at the early stage of the
development. So at the end of prototyping processes, users usually gets satisfied because they

8
feel they have deep influence in the design process. Though there are some shortcomings
attributed to this methodology but none of them seems troublesome enough to outweigh it
potential advantages.
This methodology is ideal for this project because it will enable the developers to understand
the user requirements at an early stage of the development. It will also help get valuable
feedback from the user and helps system developers and designers understand about what
exactly is expected from the product under development. In requirement engineering process,
a prototype can assist with the elicitation and validation of system requirement compared to
other models. In system design process, it can be used to run back to back test with the
system that will be delivered. More also, rather than attempting to understand a system
specification on paper, the user can interact with the prototype to better understand what and
what I can do and it cannot do.
3.2.1 Prototyping Methodology Phases to be applied to this project
3.2.1.1 Planning Phase
This phase is the fundamental process by which the author will use to understand why the
information system needs to be built and determined how the project team will go about
building it. So in this phase, the author will conducts research thoroughly on the current
system in order to know how it works, the limitations and area that needs to be improved and
what is needed to be done to meet the requirements of the system. The author will be able to
provide a system that saves the efforts and time of both the university and the students.
The questionnaire technique will be used in gathering the requirements and to understand
more about the existing system through the examination board. After that, the tools as such as
the Microsoft project will be used in creating the workplan (Gantt Chart) of the whole project
based on the tasks that has to be done with specific time duration, staffing of the project will
also be included in this workplan, and the necessary techniques that are to be put in place to
help the project team control and direct the project throughout the entire SDLC will also be
included in this workplan. At the end of this phase, the author will ascertain ways to
convinced Legenda Education Group stakeholders for the acceptance of the system request.
However, below is the workplan for the proposed system that was design by the author using
Microsoft project.

9
3.2.1.2 Analysis Phase
This is the second phase of the SDLC. So during this phase, the author will analyze the
current system “manual system”, to find out what are the limitation of the existing system,
and then identifies improvement opportunities that are to be made in the proposed system in
order to make it a better one compared to the current system. However, to analyze the current
system, the author will make use of the questionnaires fact-finding method to do that, and this
will be achieve by distributing the questionnaire that was draft out by the author in chapter
two of this project to the students as well as to the staff of the university. After this stage, the
author will still make use of questionnaire method to find out what the users (students/staff)
want the new system to do. So based on the information gathered, and the analysis that was
carried out; now the functional and non-functional requirements of the proposed system will
be analyzed by the author, and the hardware and software requirements needed for the
proposed to be developed will now be made available. The modelling tools such as the
Rationale Rose Edition for UML diagram are to be used in drawing the use case, sequence,
and class diagrams, and then ERD diagram are to be used to have the exact vision of how the
proposed system works, and how the actors will interact with the system functionalities and
the activities to be performed while making use of the system.
3.2.1.3 Design Phase
This is next phase that will come after the analysis phase has been completed by the author.
So once the requirement information has been gathered, the author will now focus on the
high-level design, databases and the interfaces. In this phase, the system is designed to satisfy
the requirements identified in the earlier phases. The requirements identified in the analysis
phase are transformed into system design document that actually describes the design of the
proposed system. Here also, the author will now use the information gathered earlier to create
the system storyboards, and as well creates all the UML diagrams for the proposed system.
Before drawing UML diagrams, the author will then identify who are the actors and what are
the important use cases that are needed for the new system. After that, the author will now
begin to draw the use case diagram. After the use case diagram has been drawn, the author
will now draft out what are the important use cases needed for the system, and as well the use
cases description which will help describe the flow of events for each use case. After that, the
author will now use the information drafted out in the use cases description to draw the
sequence diagram. Before the author starts to draw the sequence diagram, the entity,
boundary, actor and controller of each use case will be identity. After the sequence diagram
has been drawn completely, the author will now go ahead to identify what are the important

10
classes needed for the proposed system and then use it to draw the class diagram as well as
the relationships that exist between two class classes or more. After all the UML diagrams
have been drawn, the author will then design the storyboard diagrams for the proposed
system which will be apply during implementation phase. When designing the storyboard
diagrams, the author will then be able to find out know what graphical user interface (GUI) is
most ideal for the new system. However, the high level design will then depicts the structure
of the data and algorithm required to implement the system, while the database design will
give a clear description of the data schema required to support the high level design. In this
database design, the author will develop the physical and logical designs for the proposed
system based on the ER diagram. However, the interface design will describe how the human
computer interaction of the system will be, so that the existing system designs can be
incorporated into the prototype. The author will use the Dreamweaver as tool to design the
interface of the proposed system because it is so ideal in designing a good graphical user
interface for any workable system. Finally, this phase will show the exact structure of how
the proposed system should operate.
3.2.1.4 System Prototype
After the design phase is completed, the information gathered then will be immediately
incorporate into a prototype by the author. This may signify the modification or creation of
system information, as well as inclusion of new codes and then modification of existing
coding’s to make it align with the proposed system coding’s. After this, the prototype system
will now be shown to users and the project sponsor for comment and review. These
comments will now be used to redesign and re-implement a second prototype which then
comes with a few more features.
3.2.1.5 Implementation Phase
After the system prototype requirement is perfectly understood by the author, the system is
now rewritten once more. So to this, the author will transform the high level design into
codes and integrate the database into codes. This phase will actually include rewriting of the
codes that will help to ensure that each and every function of the system performs and meet
the needs of the users as well as to the project sponsor. In this stage, there will also be an
integration of the entire system, to ensure that the system interfaces and coding are
cooperating with each other to achieve maximum performance. At this phase, the author will
then create the database tables for the proposed system with the help of MySQL server. At
this phase also, the author will use some testing method such as black and white box testing
to ensure that each and every function of the proposed system requirements as it is been

11
required by Legenda Education Group Examination board are duly met. After completion, the
system will also be reviewed all over again to identify if there are any major or minor
changes for the system that are needed. This phase will also include activities such as user
training and system maintenance. The user training will needed most in order to teach the
students and staff of the university how to make best use of the new system.
3.2.1.6 System
This is the last phase that will be carried within this chosen methodology. In this phase, final
new system is now up and running, and ready to use and all functionalities are working with
no noticeable error or changes. After this, the fully developed online examination system will
now be handed over to the management of the institution for use in conduct of any
examinations in the college.
3.3 Fact-Finding Method
The fact finding is the process of collection of data and information based on techniques
which contain sampling of observations, interviews, and questionnaires. It is used to collect
facts about the systems, requirements and preferences. The system analyst uses suitable fact
finding techniques to develop and implement the current existing system.
3.3.1 Questionnaire Fact-Finding method
It is a tool used to obtain and collect information about a particular issue of interest from
individual. The questionnaires are designed in order to give respondents more freedom in
answering questions asked. It is usually made up of series of questions, there are also always
a clear instructions and spaces for answers. The questionnaire is so ideal for collecting of
information from large number of user. So with this method, information will be collected
from large number of student of Legenda Education Group due to the fact that research is
mainly aimed at knowing the student’s opinion of the current examination system of the
institution, the limitation and what the preferred system they need. This method will assist in
understanding the research much better and help to ascertain the limit of the research, and to
understand what and how to go about developing the online examination system based on the
user requirements gathered. The Author will choose a sample of thirty (30) students from
large number of students of Legenda Education Group in this questionnaire fact finding
method. The selected sample will be chosen irrespective of the student’s gender, age or level
to help the author understand are the students views based on the current system.
3.5 Conclusion
In conclusion of this chapter, the author has analyzed about the problem statement of the
existing system which includes the cause and the solution, the system development life cycle

12
(SDLC) that are chosen for the development of the proposed system are also specified ,and
what the author will do in each step of the chosen SDLC phases are also indicated. The
chosen fact finding method was also analyze, and it includes the question to be asked, the
expected results and the motive behind asking such question. The chapter also helped to
identify how to develop the new starting from the planning phase to the final phase (system).
This chapter has also assists to have a good planning as well as exact structure of the final
proposed system. So to this, the online examination system will help solve the problems
faced by institution with the use of paper based examination system.

4.1 Requirement Analysis

The requirement analysis which is at times referred as requirement engineering, is the process
of determining user expectations for the new or modified system. According to bernd bruegge
and Allen H.dutoit (2000), the requirement analysis involves regular interaction with the
client/user to determine their expectation, giving visual representation’s, creating mapping
between loose ends, and defining boundaries of the system. The information gathered during
the requirement analysis is then used to plan the basic project approach and to conduct
system feasibility study in the operational, economical and technical areas. During the
requirement analysis, energy are mostly directed towards ensuring that the final system
conforms to user needs rather than attempting to mold user expectations to fit the
requirements. Requirement analysis may be either functional requirement i.e. User
requirement and Non-functional requirement i.e. System requirement. In addition, prior
analyses are reviewed and updated, refining mission and environment definitions to support
system definition. Requirements analysis is mainly conducted iteratively with functional
analysis to optimize performance requirements for identified functions, and to verify that
synthesized solutions can satisfy user requirements. The purpose of requirements analysis is
to: refine user requirements and objectives; define initial performance objectives and refine
them into requirements.
4.3.1 Functional Requirements
According to (Allen H et al., 2004), a functional requirements is a description of the feature
requirement. Specifically, the functional requirements relates with what the system should or
provide for users which are related to the proposed system. It describes an interaction
between the system and it environment, and the functional requirement include description of
the required functions, provision of associated online reports or queries and the details of data

13
 to be held in the system. Essentially it also describe what the system must do or the steps it is
going to have to take to perform an action. However, Legenda Online Examination system is
a system that must be capable to allow users to take exam online, be able to login and logout
of the system, check result, review their result among other functions. All these things that
system are capable to do are been termed as functional requirements.
4.3.1.1 System Actors and Description
Taking a proper look at the interpretation user requirements collected from the students of
Legenda Education Group, the actors for proposed system is been identified and describe
below.
 Administrator
 Lecturer
 Student

4.3.1.2 Roles of the actors for the proposed system

From the data interpretation, the following are the roles that should be performed by the users
of the proposed system.
4.3.1.2.1 Administrator: The administrator will be the able to create new class and delete
old class as well, and at the same time manage the entire system. The administrator also has
the ability to add, view, delete and update student accounts or profile as well as that of the
lecturer, and at the same time manage the entire system by keeping track of the whole
examination process to avoid any exam malpractice.
4.3.1.2.1 Student: A student is also an important user in the proposed system. After
registration, student can see his/her profile. A student can be able to take exam, view his/her
exam result and at the same time print result. The student will be facilitated with all the latest
news update regarding taking exam online.
4.3.1.2.1 Lecturer: This is third type of user for the proposed system. After registration the
lecturer has the ability to add/set new module, update module, view module and at the same
time be able to delete old module that has already been taken. The lecturer will also be able to
manage question paper.
Below is a table showing the functional requirements use to develop the Legenda Online
Examination system in more detail
Hint: High Priority and Low Priority
Table 1:0 functional requirements

Actor Functional requirement type Description Priority

14
 Login The system shall let the admin to High
log into the system in order to
Administrator have full access to other system
functionalities
Manage ModuleThe system shall let the admin to High
(Add/Delete/Edit) manage Module
Manage User (Add/Delete/Edit) The system shall let the admin to High
add, delete, and edit user.
Logout The system shall let the admin to High
logout from the system after using
it

Actor Functional requirement Description Priority

type
Login The system shall let the student to log intoHigh
the system using their valid username and
Student password in order to have full access to other
system functionalities
Register The system shall let the student to register to High
the system
Take exam The system shall let the student to take theirHigh
exam online after logging to the system
View result The system shall let the student to view their High
result immediately the exam gets over
Print result The system shall let the student to print their High
results after the exam is done.
Review answer The system shall let the student to review Low
their answers before final submission.
Logout The system shall let the student to logoutHigh
from the system after using it

Actor Functional requirement type Description Priority

15
 Login The system shall let the lecturer to log High
into the system in order to have full
Lecturer access to other system functionalities
Register The system shall let the lecturer to High
register to the system
Manage Exam (Add/Edit/Delete) The system shall let the lecturer to add, High
delete, and edit exams
Manage Question Paper (setThe system shall let the lecturer to High
question paper and timemanage question paper such as setting
duration/delete/edit questionof question paper and their time
paper duration, as well as delete, and edit
question paper at the same time.
Logout The system shall let the lecturer to High
logout from the system after using it

4.3.2 Non-Functional Requirements

The non-functional requirements are those requirements that are not directly concerned with
the specific functions delivered by the system. It is a description of and where possible target
values of associated non-functional requirements. According to (Allen, et al., 2004) it
describes how well or what standard a function should be provided. So generally, the non-
functional may cover the system as a whole or relate to specific functional requirement. It
also refers to the behavior properties that the system should have such reliability, usability
etc. The non-functional requirements help to ensure that the functional requirement identified
from users met and executed normally according to (Stack Overflow, 2014). Below is a table
showing all the Non-Functional Requirement which are used in developing the Legenda
Online Examination System in more details.
Table 2:1 non-functional requirements

S/No Requirement Name Description

1 Availability The system should be able and ever ready to perform all the
required functions at any point in time, under any specified
conditions when been used. Also the system should be made
available at any given point in time so that it can be used by the
students.

16
2 Accessibility The system should be able to be access by multiple students at any
given moment without any downtime on the system. The system
should be able to accessible 24/7 for students to make use of it at
their own convenient time.
3 Usability The system should be ease and simple to be use and understand, so
that students can be able to use it without having any difficulties.
4 Performance The system performance should be very fast when student make
use of it, and under no circumstances should the system operates
very low. The system should also be able to insert and save as well
as retrieves data at a very good speed. The system should retrieve
the student’s information within 0.2 second.
5 Reliability The system should be very reliable so that it can be used at any
time of the month, week or day, although the system could be
maintained once every 3 month, and this may be carried out on the
last Sunday of the month, so during this day the system is not
functioning.
6 Extensibility The system should be able to reach out to students in different
geographical locations around Malaysia and beyond.
7 Supportability The system should be ease of changes after any deployment.
However, the system should be capable to support any additional
component that needs to be added to the system. The system should
be able to change its status in order to deal with any new
technology amendment or to fix defects
8 Operational The system should operate in any Windows platform, and also the
system should be able to automatically back up every files at the
end of each day.
9 Security The system should only allow registered users under the admin
with a valid User ID and Password to be able to access the system,
so in no circumstances should unregistered users be able to use the
system. The system should only let the admin to do data analysis.
10 Backup The system should be able to recover lost information from the
back up memory within an hour if any form of failure occurs.
11 Interoperability The system should be able to work with other key technologies if

17
 the need arises.
12 Capacity The system should be capable of supporting multiple users/students
simultaneously without experiencing a downtime
13 Documentation The system should have documentation which makes it easy for
administrator to understand the system and in case of any
improvements in the near future

4.3.3 Hardware and Software Requirements

4.3.3.1 Hardware Requirements
These are some of the most ideal set of requirements defined by any operating system. The
hardware requirement list is often accompanied by a hardware compatibility list (HLC),
mainly in the case of operating system. However, the table below depicts the hardware
requirements needed for developing the proposed system in terms of their specifications,
minimum requirement and other features.
Table 3:2 hardware requirements

Hardware Minimum Requirement Availability

Processor Intel ® core (™) i3 or higher Yes

Hard disk 500GB or higher Yes
Processor Speed 2.00GHz or higher Yes
System Type 64 bit Operating system Yes
Random Access Memory4.00 GB(2.86 GB usable or higher Yes
(RAM)
Monitor Screen resolution LCD 17”/1367*768 (recommended) or higher Yes
Modem Cable or ADSL/SDL(recommended Yes
CD ROM None Yes
Printer Laser printer Yes
Keyboard QWERTY keyboard Yes
Scanner Flatbed Scanner Yes
Mouse Optical mouse Yes

18
 4.3.3.2 Software Requirements
These are the description of the services that a software system must provide and the
constraint under which it must operate. However, the table below depicts the software
requirements needed for developing the proposed system in terms of their specifications,
minimum requirement and other features.
Table 4:3 software requirements

Software Minimum Descriptions Availability

Requirement
Adobe Dreamweaver Cs5 It is a tool used for designing theYes
interface which can as well be used
as PHP editor
IBM Rational Rose Enterprise EditionUML modelling Tool Yes
2010
Internet Web BrowserVersion 11.0 To be Use to preview the system Yes
(Mozilla Firefox)
PhotoScape V3.6.4 Tools for creating slide shows Yes
Antivirus Software Avast or KasperskyApplication to be used to protect theYes
Antivirus system
Microsoft Office Project 2010 Tool for creating Gantt chart Yes
Microsoft Word 2013 Use for documentation Yes
Operating system Windows 7 orUsed to run the computer system Yes
higher
Wampserver (MySQL) 2.1 Tool for MySQL database. ItYes
supports PHP.
PHP and JavaScript 5.5 version Used to connect to the server and to Yes
display the interface in browser

4.4 Conclusion
In conclusion, the author has achieve a maximum understand to the system he is going to
develop. In this chapter, the author outlined the results of the fact find method
(Questionnaire) used in the collection of information and data to find out what the user
requirements for the proposed system are. The author also discussed about the requirements

19
analysis used in developing the proposed system which includes the functional and non-
functional requirements. And finally, the author then highlights the hardware and software
requirements in table format that are to be used in developing the proposed system.

20
 PROPOSED FLOWCHART/ DFD/ BLOCK
DIAGRAM

5.1 Introduction
In this chapter, the author will review the entire design of the proposed system requirement
analysis. The requirement design analysis that will be cover by the author in this chapter will
include the use case diagram as well the use cases description, the sequence diagram, class
diagram and story board that will aid in the developing the Legenda Online Examination
System. Specifically, this chapter will help the author with the exact pattern of what the
proposed will do for users before final implementation of the entire system.
5.2 Use Case Diagram
Use case diagram is a graphical depiction of the interactions among the elements of a system.
It is used to describe the functionality of a system in a horizontal way (Andrew.com.edu,
2015). So rather merely depicting the details of individual features of the, the use case
diagram can be used to show all of its available functionality. The main purpose of a use case
diagram is to depict the different way that a user might interact with a system. The next page
depicts the use case diagram for the proposed system.

21
5.2.1 Use Case Diagram

Legenda Online Examination System

Edit Exam
Add Exam <<extend>>
<<extend>>
Take Exam
View Result

<<extend>>
Print Result Manage Exam

Delete Exam

Review Answer

Student

Register

Lecturer
Login <<include>>

Edit Module Logout

<<extend>>
<<extend>> Manage Question Paper
<<extend>>
Admin Add Module Set Question paper <<extend>>

<<extend>> <<extend>>
Manage Module

Delete Module
Delete Question Paper
<<extend>>
Manage User
<<extend>>
Add User
Edit Question Paper
<<extend>>

Delete User

Edit User

Figure 1:1 Use case diagram

22
5.3 Use Case Description
5.3.1 Registration Use Case Description
Table 5:1 Registration use case description

1: Use Case Name: Registration ID: 1 Importance level: High

2: Primary Actor: User (Student/Lecturer) Use Case type: Detail, Essential

2.1 Visual

Register
User

3: Stakeholders and Interest:

Student: Wants to Register to the online examination system
4: Brief Description:
This use case describes how new user(student/lecturer) can register to our online examination system

5:Trigger: The user come and Register

Type: External
6:Relationship: N/A
7: Association: Student and lecturer
8: Include: N/A
9: Extend: N/A
10: Generalization: N/A

11: Input: User Required Information

12: Output: New User added to the system successfully
13: Pre-condition: User must have a valid email address
14: Post condition: User can make use of all the functions provided in the system after registration

23
15: Normal flow of Events:
 The user goes to the system click register button
 The system display the register page with the form
 The user fill up the register form and click on submit button
 The system respond by verifying the user details provided and then save the information
 The system then display student registration is successful

16: Exceptional Flows: E1:All the required must not be left blank
17: Alternate Flow: A1: User can cancel their registration if there is any mistake
18: Constraints: Valid email Address

5.3.2 Take Exam Use Case Description

Table 6:2.5 Take exam use case description

1: Use Case Name: Take Exam ID: 2 Importance level: High

2: Primary Actor: Student Use Case type: Detail, Essential

2.1 Visual

Student Take Exam

3: Stakeholders and Interest:

Student: Wants to sit for their examination
4: Brief Description:
This use case describes how registered student can take their examination

5:Trigger: The Student come and sit for exam

Type: External

24
6:Relationship: N/A
7: Association: Student
8: Include: N/A
9: Extend: N/A
10: Generalization: N/A

11: Input: User Login information

12: Output: Examination completed
13: Pre-condition: Must be a registered student
14: Post condition: Student can now give their exam
15: Normal flow of Events:
 The student go to the homepage
 The student then click on login button
 The system then display student login page
 The student key in their valid Username and Password
 The system the responds by verifying the Username and Password key into the system
 The system then display the exam panel homepage
 The student then choose the subject they want to give exam to and click submit button
 The system then verify the subject
 The student then click begin exam
 The system now begin the exam process with a stop time
 The student choose their choice of option from the number options provided for each
question.
 The process continue until all the question has been answered
 The student now click finish button to submit their final answer.
 The system then verify and save the student answer
 The system then display thank you. Your examination has been completed.
16: Exceptional Flows: E1 Invalid Username or Password, No question set on the Subject
17: Alternate Flow: A1 User can cancel their answer
18: Constraints: Password must be valid as well as Username

25
5.3.3 Login Use Case Description
Table 7:6 Login use case description

1: Use Case Name: Login ID: 6 Importance level: High

2: Primary Actor: User (Admin, Student and Lecturer) Use Case type: Detail, Essential

2.1 Visual

Login
User

3: Stakeholders and Interest:

User: Wants to login to the system
4: Brief Description:
This use case describes how the user (Admin /Student/Lecturer) will login to the system in order to
make use of order functions of the system
5: Trigger: The user login to the system to perform other function
Type: Internal
6:Relationship: N/A
7: Association: Admin, Student, Lecturer
8: Include: N/A
9: Extend: Logout
10: Generalization: N/A

11: Input: Valid UserID and Password

12: Output: Has successfully Sign in
13: Pre-condition: User sign in using valid userid and password
14: Post condition: The user can now make of the system function if is already registered user
15: Normal flow of Events:
 The system display the homepage
 The user click on the login button
 The system display the login page
 User key in username and password, and click login button
 The system verify the provided details and , and then the system will display the particular

26
 user page
16: Exceptional Flows: E1 Key in wrong password and username
17: Alternate Flow: A1:Cancel
18: Constraints: Must key in a valid email address

5.4 Sequence Diagram

The sequence diagram are simple subsets of interaction diagrams. It is seen as an interaction
diagram that depict how processes operate with one another and in what patter (Lucidchart,
2014). It help to map out events in an engineering process in order to streamline activities of
the new system. The sequence diagram do describes an interaction merely by focusing on the
sequence of message that are exchanged in response with their corresponding occurrence
specification on the lifelines. The sequence diagram showcase not only the component of
objects but also with the objects and actors that are involved in their behavior. This diagram
are usually used by software developers to understand requirements for a new system or
enhance an existing system. The sequence diagram is more dynamic compared to
collaboration, use case and collaboration diagrams. The next page depicts the sequence
diagrams for the proposed Online Examination System:

27
5.4.1 Login Sequence Diagram

Login Controller Regisration Table UserHomepage

: Legenda Homepage Login Page
User

1: Go to Hompage

2: Click on login link

3: Display

4: key in userid and password E1: Invalid

userid and
password
5: Click on Login Button

6: Send Info()

A1:Cancel 7: check info

8: verify info

9: Return info()

10: Display you have successfully Login

Figure 2:2 Login sequence diagram

5.4.2 Registration Sequence Diagram

28
 Regisration Page Registration Controller Regisration Table
User : Legenda Homepage

1: Go to Hompage

2: Click on Registration link

3: Display
E1: Invalid
Email ID
4: Key in all required fill

5: Click on Login Button

6: Send Info()

7: verify inof()
A1:Cancel

8: Save info()

9: Display "Your Registration is Successful"

Figure 3:3 Registration sequence diagram

29
Lecturer Question PaperTable Question Paper Controller
Lecturer Login Page Lecturer Page Manage question paper Page : Login Controller

1: key in LecturerID and password

E1:Invalid
2: Click on Login Button Userid and
Password

A1:Cancel 3: send info()

4: verify info

5: Display access

6: click on manage question paper button

7: display

8: click on view, update or delete question paper button

E2: Invalid
9: key in the required detail detail

10: click on submit button

11: send info()

12: verify info()

A2:Cancel

13: save or delete info

14: Display changes has been successfully made

Figure 4:8 Manage Question paper sequence diagram

30
Figure 5:10 Review answer sequence diagram

Figure 6:11 Logout sequence diagram

Figure 7:12 Manage class sequence diagram

Figure 8:14 Add module sequence diagram

Figure 9:15 Manage module sequence diagram

31
5.5 Collaboration Diagram
5.5.1 Login collaboration diagram 8: verify info

Login 7: check info

Controller

10: Display you have successfully Login 9: Return info()

Regisration Table

1: Go to Hompage
2: Click on login link
UserHomepage

: Legenda Homepage

User : Student

6: Send Info()

3: Display
4: key in userid and password
5: Click on Login Button

Login Page

Figure 10:16 Login collaboration diagram

Figure 11:17 Manage student collaboration diagram

32
5.6 Class Diagram
The class diagram provides the general overview of the target system by describing the class
and classes inside the system and the relationships between them. It describes the information
without reference to any particular implementation. The class diagram provides a lot variety
of usages from modeling the domain specific data to detailed design of the proposed system
(Visual-paradigm.com, 2015). It is also seen as the heart of UML because it represents the
core purposes of UML due to the fact that it separates the design elements from the coding of
the system. In class diagram generally, the classes are arranged in groups that share common
characteristics, and it classes and relationship can be implemented in many way such as
database tables or composition of software objects.

5.12 Conclusion
In conclusion, the author has do far created the use case diagram with the use case
descriptions, the class diagram, the sequence diagram as well as the storyboard for
developing the proposed system. So with this stated point/diagram above, the design phase of
the proposed system is completed which will now form the base for the next stage of the
system development which is the implementation phase.

33
 Chapter 6
System Implementation
6.1 Introduction
This particular chapter will be mainly discussed about the system implementation; which will
be carry out with reference to what have been discussed in the analysis phase (chapter 4)
before, the last system prototype accessed will be used in implementing the coding. However,
system design is required to be implemented in order to turn it into an effective system. This
makes it necessary that the coding of designs is turn into a computer language that can be
understood, that is, programming language. More also, other crucial areas that will be
discussed in this chapter are; the software and software development requirement tools and
technologies, system implementation, implementation of GUI with the necessary codes,
implementation of database as well as table structure.
6.2 Development Environment
In some of the computer software and programs product development, the development
environment is been referred as the set of processes and programming tools used to create the
program or software product. The term development may sometimes also imply the physical
environment. Processes and tools are coordinated to provide developers an orderly interface
to convenient view of the development process which is called an integrated development
environment (Rouse, 2008).
6.2.1 Hardware Development Environment
Hardware development environment are the particular hardware a system needs for its
development. The table below describes the hardware used in developing the newly proposed
Legenda Online Examination system.
Table 6:0 hardware development requirement

Hardware Requirement
Computer HP Pavilion Laptop 15-eh2xxx
Processor Intel ® core (™) i5-4200U [email protected] 2.30 Ghz
Hard disk 500GB or higher
System Type 64 bit Operating system
Installed Memory (RAM) 4.00 GB(3.90 GB usable)
Monitor Screen resolution 14”/1367*768 (recommended) or higher

34
 6.2.2 Software Development Environment
Software development environment are the specific software’s a system needs for its
development. The table below describes the software used in developing the newly proposed
Legenda Online Examination system.
Table 8:1 software development environment

Software Requirement Descriptions

Adobe Dreamweaver Version 11.0 It is a tool used for designing the interface which can
as well be used as PHP editor
IBM Rational RoseVersion 7.0.0 Tool for UML modelling diagrams
Enterprise Edition 2003
Internet Web BrowserVersion 10.0 To be Use to preview and run the system
(Google Chrome)
PhotoScape V3.6.4 Tools for creating slide shows
Antivirus Software (Avast) Version 2012 Application to be used to protect the system
Microsoft Office Project 2010 Version Tool for creating Gantt chart
2010
Microsoft Word 2013 Use for documentation
Operating system Windows 8 pro Used to run the computer system
Wampserver Version 2.1 Tool for MySQL database. It supports PHP.
PHP 5.5 Version For database development of the system

6.3 System Implementation

System implementation can be seen as a process of defining, designing, testing and
implementation of a new software application or program. This may involve the internal
development of customized systems, creations of database systems, and the purchasing of
third parties developed software’s. In system implementation all written standards and
procedures must guide all information systems processing functions.
6.3.1 Three-tier Architecture
Three tier architecture is a type of multi-tier computing architecture in which an entire
application is distributed across three different computing tiers or layers. The first layer in
the 3-tier architecture is the user layer which runs on the clients computer or pcs, the business
logic and data processing layer which is the middle tier runs on the server which is called the

35
application layer, a database management system (DBMS) which stores the data required by
the middle tier, and this tier could also be run as a separate server called the database server.
The three tier allows for one central server location for all the business logic and one central
server location for all of the data leading to consistency, uniformity and reuse of applications
in this environment. In three-tier architecture the more users access the system the more
scalable the system will become unlike any other solutions because you can add as many
middle tiers (running on each own server) so as to ensure a good performance. Finally the
distribution of the entire application logic across three tiers helps optimize the overall
application access and layer level development and management

Figure 12:1 three tier architecture

Figure 13:2 proposed architecture

36
6.4 Implementation of Graphical User Interface (GUI) ad Coding
The implementation of graphical user interface (GUI) explains the system interface with
design with its respective coding. The functions include Registration, Login, Take exam,
Check result, Update, Delete etc.
6.4.1 Admin Login Page (GUI)

6.4.1 Admin Dashboard Page (GUI)

37
6.4.1 Student Manager Panel (GUI)

6.4.1 Faculty Manager Panel (GUI)

38
6.4.1 Question Manager Panel (GUI)

6.4.1 Question Manager Panel 2 (GUI)

6.4.Student Login Page (GUI and Code)

<!--Body Starts Here-->

<div class="main">

39
 <div class="login">
<form method="post" action="">
<h2>Student Log In</h2>
<?php
if(isset($_SESSION['invalid']))
{
echo $_SESSION['invalid'];
unset($_SESSION['invalid']);
}
?>
<input type="text" name="username" placeholder="Username"
required="true" />
<input type="password" name="password"
placeholder="Password" required="true" />
<input type="submit" name="submit" value="Log In"
class="btn-go" />
<input type="reset" name="reset" value="Reset" class="btn-
exit" />
</form>
<?php
if(isset($_POST['submit']))
{
//echo "CLicked";
//Get Values from forms
$username=$obj->sanitize($conn,$_POST['username']);
$password=$obj->sanitize($conn,$_POST['password']);
//Check Login
$tbl_name="tbl_student";
$where="username='$username' && password='$password'
&& is_active='yes'";
$query=$obj->select_data($tbl_name,$where);
$res=$obj->execute_query($conn,$query);
$count_rows=$obj->num_rows($res);
if($count_rows>0)
{
$_SESSION['student']=$username;
$_SESSION['login']="<div class='success'>Login
Successful.</div>";
header('location:'.SITEURL.'index.php?
page=welcome');
}
else
{
$_SESSION['invalid']="<div class='error'>Username
or Password is invalid.</div>";
header('location:'.SITEURL.'index.php?
page=login');
}

40
 }
?>
</div>
</div>
<!--Body Ends Here-->

Figure 14:3 Login GUI and code

The code and GUI above describes the login function for the student of the system to login,
so if the student key in invalid data the displays an error message, thus if login input data is
correct the system will proceed to display student homepage.

41
6.4.Student Exam commencing Page (GUI)

42
CHAPTER 7
TESTING
7.1 Introduction
This particular chapter is dedicated to perform testing to access the efficiency and
effectiveness of the Legenda Online examination system functionalities. This chapter is
regarded as one of the most significant chapters in system development as it conduct and
performs the final system testing to checkmate errors, mistakes and to ensure that the new
developed system functionalities meet the initial requirements to prevail over the problems in
the current system. So before the system reach to the hand of it users. This testing is to be
carried to ensure that the system satisfies it requirements and solves the problem for which it
is being developed to solve.

7.2 Testing Plan

The test plan is a document describing the scope, approach, resources and schedule of
intended test activities, it help identifies amongst others test items, the features to be tested,
testing tasks, who will do each task, degree of tester independence, the test environment and
exist criteria to be used, and the rationale for their choice, and any risks requiring
contingency planning. (Softwaretestingfundamentals.com, 2011)

7.3 Blackbox Testing

Black-box testing is a software testing method in which the internal
structure/design/implementation of the item being tested it not known to the tester. The black-
box testing examines the functionality of an application based on the specifications. It also
takes an external perspective of test object to derive test cases. For instance, in a black box on
a software design, the tester only knows the inputs and what the expected outcomes should be
and not how the program arrives at those inputs.
It also takes an external perspective of the test object to derive test cases. For example in a
black box test on a software design the tester only knows the inputs and what the expected
outcomes should be and not how the program arrives at those outputs.

43
 Table 9:1 black box testing of online exam system description

Test ID Function Description Input Expected ResultActual Student

Result Pass/Fail
1 Registration Pre-condition: Student and -Form is -Data Pass.
using valid Student/Lecturer Lecturer enter validated. provided is
data must be registering valid registration -registration validated.
for the first time data or information -registration
Actor: Student and information provided saved information
Lecturer in database. provided
- system displays saved in
“ registration database.
successful” - system
displays “
registration
successful”
2 Registering Pre-condition: Student and The system The system Pass
with Student/Lecturer Lecturer enter should display displays an
incorrect or must be registering valid registration an error message error message
invalid data for the first time data or that the that the
Actor: Student and information but username or username or
Lecturer the username or email are already email are
email are existed exists already exists
in the database
3 Login with Pre—condition: Enter valid -form is form is Pass
valid info users (admin, student username and validated validated
and lecturer) must password - log in users to - users are
have an existing their account logged in to
account before login their account
Actors: Student,
Lecturer,
administrator
Add module Pre-condition: Click “add -system should System Pass
4 Administrator has module button” display module display

44
 logged in form module form
Actors: administrator -enter valid -system
module details display a
and click “save message
button” -system
-system should display a
display a message
message “module is
“module is added
added successfully”
successfully”

5 Take exam Pre-condition: Click “take System should System Pass

student has logged exam” button retrieve and retrieve and
into the system display the exam display the
Actor: student questions exam
questions
6 Check result Pre-condition: Click” check System should System Pass
student has logged result” button retrieve and retrieve and
into the system, and display the result display the
must have taken of the student result of the
exam student
Actors: student

7 Edit module Pre-condition: Enter valid System should System Pass

administrator has module details save the should save
logged in and must Click on “save” immediate the
has added module button changes made immediate
earlier - system display changes
Actor: administrator a message made
“module has - system
been updated” display a
message

45
 “module has
been
updated”

8 Delete Pre-condition: Check module System should System Pass

module administrator has check box and save the should save
logged in click “delete immediate the
Actors: administrator module” button changes made immediate
- system display changes
a message made
“module has - system
successfully display a
deleted” message
“module has
successfully
deleted”

CHAPTER 8
CONCLUSION
8.0 Introduction
This main is quite difficult and required a lot of research to achieve its sole aim. So to this,
this chapter is the last chapter of this project report. The chapter will recap and conclude all
the chapters that has been earlier in this project development. So it is crucial to compare the

46
findings obtained with the main objectives of the project report so as to ascertain whether the
research is successful or not. However, this online exam system was designed and
implemented successfully based on the user requirement discussed in chapter 4 and five of
this project. The new system was aimed to replace the current manual system of Legenda
College in order to provide fast means of taking exam and checking results by the students.
This chapter will further summarize all the other chapters, finding and result, lesson learnt,
problem encounter, and finally future enhancements.

8.1 Summary of the chapters

8.1.1 Chapter 1 Introduction
This first chapter of this project provides the general overview of the current system of the
system. The other important areas that was also discussed in this chapter include, problem
statement, objectives, project scope, aim and rationale. The main purpose of this chapter is to
review in order to have a clear picture of the current system and to identify and define the
scope of the proposed system.
8.1.2 Chapter 2 Literature Review
This second chapter is aimed to conduct the literature review of both the current and the
proposed system. The main areas that was discussed in this chapter are the background study,
status of the current system, review on other similar existing systems, and analysis of the
tools and technologies that will be used in developed the newly proposed online exam
system.
8.1.3 Chapter 3 Methodology
In this chapter, the general overview research on methodology that will be suitable for the
implementation of this newly system were discussed. The finding method that are to be used
to gather the user requirements in regards to the proposed system were also discussed in this
chapter such as questionnaires interview and Join application development (JAD).

8.1.4 Chapter 5 Analysis

In this chapter, the analysis of the current and new system was carried out. So to this, the
comprehensive analysis of the questionnaires, functional and non-functional requirements,
hardware and software requirements that give the clear picture of the features and functions
of the new proposed system was discussed
8.1.5 Chapter 5 Design
In this chapter, the requirements gathered in the analysis phase were used to design the
system. The use case diagram, use case description, class diagram, sequence diagram, state

47
chart diagram, activity diagram, entity relationship diagram and the storyboards were all
discussed and designed in this chapter
8.1.6 Chapter 6 Implementation
In this chapter, the coding for each function of the system was created and built. Hardware
and software tools and technologies, system architecture, database implementation are
discussed for the implementation of the new system.
8.1.7 Chapter 7 Testing
The main purpose of this chapter is to carry out system testing to ascertain the new system’
functionalities are working perfectly well. The test was performed and all errors and bugs
discovered were immediately corrected.
8.1.8 Chapter 8 Conclusion
This chapter review the entire chapters discussed in regards to the newly developed system,
findings and result, lesson learnt, problem encountered and future enhancement are identified
as well.

Chapter 9 Conclusion and Future Scope

9.1 Finding and result
It simply indicates the final outcome achieved in the completion of the system. Well the final
finding and result of this project is successful because the author is able to come up with the
sole aim of this project which is the development and implementation of online examination
system. More also, all the objectives of system as stated in the beginning of this project are
also achieved.

9.2 Lesson learnt

This particular section provides the overview of the lessons learnt by the author during the
development of the new system. However, this project development was quite challenging

48
and at the same time encouraging; this is due to the fact that it required lots of research and
findings of new skills, so this resulted in enhancing the author’s research skills, analytical and
critical thinking. The following elaborate the lessons learnt;
 Proper understanding of system development processes
 Adequate knowledge in use of PHP and MYSQL was acquired.
 Proper research skills was also acquired by the author.
 Actual understanding of the online examination system development was another
crucial knowledge obtained by the author.
 Improved skill in time management was also another thing achieved by the author.
 Use of proper Harvard referencing style is another lesson learnt.
 The right format for word documentation was also learnt.
 The use of in-text citation is another crucial knowledge gained by the author

9.3 Problem encountered

The following highlights the problem encountered during the research and development of
the online examination system for Legenda College.
 Time management is the first problem the author experience. Time management was
quite difficult issue for the author because the system is a complex one and at the
same time complicated to design. But with diligent and dedication the problem was
overcome.
 During the requirement stage, it very difficult to find students that wiling to answer
and fill the questionnaires with complete honesty. Some of the student ignored the
questionnaire given to them by the author while some even refuse to collect the
questionnaire.
 Some set dates to meet with the supervisor was not achieved because at the functions
needed to complete and show to the supervisor were not ready or completed on time,
so this lead to delay but missing were later rescheduled and all other thing went fine
as expected.
 Lack of sound programming skill is another issue experience by the author. However,
the author is quite good in system interface but lack strong PHP programming skills;
this result to delay in the system implementation but is was completed before reaching
the system testing phase.

49
  Some of the UML diagram were quite difficult for the author to design and some of
the crucial functions of the system were also every difficult to design but with right on
schedule everything was done perfectly well.

9.4 Future enhancements

The following additional features are suggested by the author for further improvement on the
developed system so as to always meet the ever changing demands of users.
Multiple language option: A multiple language such as Chinese or French should be
inculcate so as to allow foreign students from china or France to be able to the write the
examination on their own language
Automatic question generation: In the near future, questions should be able to be generated
automatically
Instant result email: This function should be provided in the future so that the student can
be able to receive their result on their email immediately the exam is over.
Support theory question: The system can be enhanced to support other question like the
theory question in the near future.
Download study material: In the near, the system should be able to allow users to download
study material.

Chapter 10 REFERENCES

Jacobsen, I and Booch, G (1999) the Unified Software Development Process, 2 nd edition
London
Dennis, A, Wixom, H and teagarden, D (2005) System Architecture and Design Version 2.0,
An Object-Oriented Approach, 2nd edition, United States of America.
Bahrami A (1999). Object Oriented Systems Development Using the Unified Modeling
Language. Boston, MA: Irwin McGraw-Hill
Bernd, H and Allen, H.D. (2004).Object oriented software engineering using UML, patterns
and Java, 2nd edition, Pearson prentice hall, united states of America.

50
Dennis, A., And Haley, B. (2000): “System Analysis and Design”, 2nd edition. John Wiley
and Sons Inc, New York
Bocij, P., Chaffey, D., Greasly, A., and Hickie, S. (2006): “Business Information System
Dennis. A, Wixom. B and Roth. R, (2010), System Analysis and Design, 4thed,
USA: John Wiley & Son.Inc.
Bruegge. B and Dutoit. A, (2010), Object Oriented Software Engineering, 3rd Ed, USA:
Pearson

Softwaretestingfundamentals.com. (2011). Test Plan | Software Testing Fundamentals.

[online] Available at: http://softwaretestingfundamentals.com/test-plan/ [Accessed 20 Apr.
2016].
http://searchsoftwarequality.techtarget.com/definition/user-acceptance-testing-UAT

Websites
Programmer2programmer.net, (2015). Free final year project synopsis on Online
Examination System, PHP and MySQL. [Online] Available at:
http://www.programmer2programmer.net/live_projects/project_11/online_examination_syste
m_synopsis.aspx [Accessed 29 Sep. 2015].
123projectlab.com, (2012). Online Examination System. [Online] Available at:
http://123projectlab.com/13-online-examination-system/ [Accessed 23 Sep. 2015].
Member, R. (2015). Role of Online Examination, Important of Online Exams in Education.
[Online] Recruitmentforms.in. Available at: http://www.recruitmentforms.in/what-is-the-role-
of-online-exams-in-education.html [Accessed 22 Oct. 2015].
Www2.ed.gov, (2015). Archived: An Introduction to the Internet. [Online] Available at:
https://www2.ed.gov/pubs/OR/ConsumerGuides/internet.html [Accessed 9 Oct. 2015].

51
SearchNetworking, (2015). What is client/server (client/server model, client/server
architecture)? - Definition from WhatIs.com. [Online] Available at:
http://searchnetworking.techtarget.com/definition/client-server [Accessed 18 Oct. 2015].
Techopedia.com, (2015). What is a Two-Tier Client/Server? - Definition from Techopedia.
[Online] Available at: https://www.techopedia.com/definition/23846/two-tier-clientserver
[Accessed 21 Oct. 2015].
Beriwal, A. (2012). Unified Modeling Language: Online Examination - Use Case Diagram.
[Online] Umldiagramtutorial.blogspot.my. Available at:
http://umldiagramtutorial.blogspot.my/2012/02/online-examination-use-case-diagram.html
[Accessed 3 Nov. 2015].
Softwaretestingclass.com, (2015). What is Difference between Two-Tier and Three-Tier
Architecture? | Software Testing Class. [Online] Available at:
http://www.softwaretestingclass.com/what-is-difference-between-two-tier-and-three-tier-
architecture/ [Accessed 8 Nov. 2015].
Maurya, A. (2014). Online examination system. [Online] Slideshare.net. Available at:
http://www.slideshare.net/shaitaana1/online-examination-system-32350542 [Accessed 23
Nov. 2015].

52