New RAAS

Minor Project Report Raas Examination System
Chapter : 1
INTRODUCTION
1.1 Purpose
The purpose of Raas Examination System is to take test in an efficient manner and no
time wasting for checking the paper. The main objective of Raas Examination System
is to efficiently evaluate the candidate thoroughly through a fully automated system
that not only saves lot of time but also gives fast results. For students they give papers
according to their convenience and time and there is no need of using extra thing like
paper, pen etc. It saves time as it allows number of students to give the exam at a time
and displays the results as the test gets over, so no need to wait for the result. It is
automatically generated by the server .User can register, login and give the test with
his specific id, and can see the results as well.
Raas Examination System helps students to offer a quick and easy way to appear for the
test. It also provides the results immediately after the examination with 100% accuracy
and security. Student can enter to perform exam only with their valid username and
password. This examination contains multiple choice questions and appropriate number
of options. There are no limitations on number of options and it can be randomized so
same set of question will not appear to all student so it prevent manipulation. More than
one option can be correct but the user can select only one option. This provides time limit.
The user can see their results after completing the exam. This helps the students to write
the exam from far distance and which can provide security and simplicity and other
beneficial features to the user.
1.2 Technologies Used

Front end as:
Core Java
1
Back end as:

PhpMyAdmin(MySql)
Database:
PhpMyAdmin(MySql)
Querying language:
MySql
Hardware Interface:
Client Side:
Internet Explorer: 6.0
Processor : Pentium IV 2.0 and above.
RAM : 256 MB
2
Chapter : 2
FEASIBILITY STUDY
2.1 Feasibility Study

 Provides complete online web based solution, including student registration,
giving tests, storing of results.
 Complete web based administration, administrator can manage examination
and question bank from web interface.
 No geographical boundary Student can give examination from anywhere of
the world by 24X7
 100% accuracy in result calculation
 Randomization of question set
2.1.1. Economic Feasibility
Economic analysis is most frequently used for evaluation of the effectiveness of the
system. More commonly knows as cost/benefit analysis he procedure is to determine
the benefit and saving that are expected from a system and compare them with costs,
decisions is made to design and implement the system. This part of feasibility study
gives the top management the economic justification for the new system. This is an
important input to the management the management, because very often the top
management does not like to get confounded by the various technicalities that bound
to be associated with a project of this kind. A simple economic analysis that gives the
actual comparison of costs and benefits is much more meaningful in such cases. In the
system, the organization is most satisfied by economic feasibility . Because, if the
organization implements this system, it need not require any additional hardware
resources as well as it will be saving lot of time.
3
2.1.2. Technical Feasibility
Technical feasibility centers on the existing manual system of the test management
process and to what extent it can support the system .According to feasibility analysis
procedure the technical feasibility of the system is analyzed and the technical
requirements such as software facilities, procedure, inputs are identified. It is also one
of the important phases of the system development activities .The system offers
greater levels of user friendliness combined with greater processing speed. Therefore,
the cost of maintenance can be reduced. Since ,processing speed is very high and the
work is reduced in the maintenance point of view management convince that the
project is operationally feasible.
2.1.3. Behavioural Feasibility
People are inherently resistant to change and computer has been known to facilitate
changes. An estimate should be made of how strong the user is likely to move towards
the development of computerized system. These are various levels of users in order to
ensure proper authentication and authorization and security of sensitive data of the
organization.
2.2. Existing System :
 User has to Login first by giving any user name and password it will be added
automatically in database so that user can login again in future by same user
name and password.
 If new user wish to login he/she can register first by clicking registeration
button appeared after log in button.
 After choosing log in button continue page will be appear to continue test.
 After Clicking on start exam multiple choice questions will come
automatically one by one with a specific time limit.
4
 User has to choose any of four existing options and then user has to hit the
submit button and each right answer will automatically count the score.
At the end of the test it will show the score of the user .All these findings demands
new application which will reduce the manual work & do everything automatically.
Also the existing systems have some major drawbacks which motivate us to develop
new system .Those drawbacks are as follows:
 Quest won't get update automatically need to update manually.

 Existing systems has not type of fields in like questions on History ,Game
,Sports ,Geography etc.
 There is possibility of hanging down the existing systems.
2.3. Proposed System :
Unlike the websites where you need to make account for every quiz you want to play,
using this application based on java, you just have to login by user name and
password and then you will get access to all quizzes from it. The proposed system is
an application for the Java plat for for pcs and mobiles will help in improving the
knowledge and accuracy. Java is an open source development platform which helps in
developing apps with low cost. Java runs on web servers, websites and local
machines. Java powers tablet PCs, smartphones, and mobile devices. Be it any
industry from banking, manufacturing, IT services or entertainment all have java
applications to cater to their customers.
Characteristics of the Proposed System :
The Raas Examination System created for taking test has following features:
 In comparison to the present system the proposed system will be less time
consuming and is more efficient.
 Analysis will be very easy in proposed system as it is automated
5
 Result will be very precise and accurate and will be declared in very short
span of time because calculation and evaluations are done by the simulator
itself.
 The proposed system is very secure as no chances of leakage of question paper
as it is dependent on the administrator only.
 The logs of appeared candidates and their marks are stored and can be backup
for future use.
 Questions are in randomization order.
Need for the Proposed System :
To solve these problems they required a computerized system to handle all the works.
They required a web based application that will provide a working environment that
will be flexible and will provide ease of work and will reduce the time for report
generation and other paper works.
Aims and Objective
The main purpose behind the proposed system is to provide a comprehensive

computerized system, which can capture, collate and analyze the data fromthese
wards and evaluate the impact of the program.
Constraints, Assumptions, Dependencies
Constraints
As this system is based on client server technology, so for normal operation minimum
of 64 MB RAM will be required on all clients.
Assumptions
In general it has been assumed that the user has complete knowledge of the system
that means user is not a naïve user. Any data entered by him/her will be valid. To
make the software as user friendly as possible but at the same time keeping in minds
user requirements.
6
• Server OS should be Windows NT/2000/XP.
• Client PC should be Windows 9X/NT/WorkStation or Windows 2000with latest

service pack.
Dependencies
It depends that the one should follow the international standards for the generating the
User ID & should fill the related information in the proper format.
7
Chapter : 3
DATA FLOW DIAGRAM
3.1. Use Case Diagram
Use case diagrams are usually referred to as behavior diagrams used to describe a set
of actions (use cases) that some system or systems (subject) should or can perform in
collaboration with one or more external users of the system (actors). Each use case
should provide some observable and valuable result to the actors or other stakeholders
of the system. Note, that UML 2.0 to 2.4 specifications also described use case
diagram as a specialization of a class diagram, and class diagram is a structure
diagram. Use case diagrams are in fact twofold - they are both behavior diagrams,
because they describe behavior of the system, and they are also structure diagrams -
as a special case of class diagrams where classifiers are restricted to be either actors .
8
Fig 3.1(Data Flow Diagram)
9
Chapter 4
Testing and Validation
4.1 Introduction
Software testing is an investigation conducted to provide stakeholders with

information about the quality of the product or service under test. Software testing
can also provide an objective, independent view of the software to allow the business
to appreciate and understand the risks of software implementation. Test techniques
include, but are not limited to the process of executing a program or application with
the intent of finding software bugs (errors or other defects).Software testing can be
stated as the process of validating and verifying that a computer
program/application/product meets the requirements that guided its design and
development ,can be implemented with the same characteristics ,and satisfies the
needs of stakeholders .Software testing, depending on the testing method employed,
can be implemented at any time in the software development process. Traditionally
most of the test effort occurs after the requirements have been defined and the coding
process has been completed, but in the Agile approaches most of the test effort is on-
going. As such, the methodology of the test is governed by the chosen software
development methodology.
4.1.1 Testing Strategies
Testing is a set of activities that can be planned in advance and conducted

systematically. A strategy for software testing must accommodation lowlevel tests
that are necessary to verify that a small source code segment has been correctly
implemented as well as high-level tests that validate major system functions against
customer requirements
Software testing is one element of verification and validation. Verification refers to

the set of activities that ensure that software correctly implements as specific function.
10
Validation refers to a different set of activities that ensure that the software that has
been built is traceable to customer requirements.
The objective of software testing is to uncover errors. To fulfill this objective, a

series of test steps unit, integration, validation and system tests are planned and
executed. Each test step is accomplished through a series of systematic test technique
that assist in the design of test cases. With each testing step, the level of abstraction
with which software is considered is broadened.
Unit Testing
Unit testing focuses verification effort on the smallest unit of software design the
module. The unit test is always white box oriented. The tests that occur as part of unit
testing are testing the module interface, examining the local data structures, testing the
boundary conditions, executing all the independent paths and testing error-handling
paths.
Integration Testing
Integration testing is a systematic technique for constructing the program structure

while at the same time conducting tests to uncover errors associated with interfacing.
Scope of testing summarizes the specific functional, performance, and internal design
characteristics that are to be tested. It employs top-down testing and bottom-up testing
methods for this case. Software testing methods are traditionally divided into white-
and blackbox testing. These two approaches are used to describe the point of view
that a test engineer takes when designing test cases.
 White-box testing (also known as clear box testing, glass box testing,
transparent box testing and structural testing) tests internal structures or
workings of a program, as opposed to the functionality exposed to the end-
user. In white-box testing an internal perspective of the system, as well as
programming skills, are used to design test cases. The tester chooses inputs to
exercise paths through the code and determine the appropriate outputs. This is
analogous to testing nodes in a circuit, e.g. in circuit testing (ICT). While
11
white-box testing can be applied at the unit, integration and system levels of
the software testing process, 27 it is usually done at the unit level. It can test
paths within a unit, paths between units during integration, and between
subsystems during a system level test. Though this method of test design can
uncover many errors or problems, it might not detect unimplemented parts of
the specification or missing requirements.
 Black-box testing treats the software as a ”black box”, examining
functionality without any knowledge of internal implementation. The testers
are only aware of what the software is supposed to do, not how it does
it.Black-box testing methods include: equivalence partitioning, boundary
value analysis, all-pairs testing, state transition tables, decision table testing,
fuzz testing, model-based testing, use case testing, exploratory testing and
specification-based testing.
4.2 Design of test cases
I have discussed the various test case designs that can be implemented in this project.
4.2.1 Login
The test case design of login is given below.
Table 4.1: Login
4.2.2 Register
This test case checks whether client is able to register.
12
Table 4.2: User Register
4.2.3 Registration for Examinatation
This test case checks whether User is successfully registered for Online
Examinitation.
Table 6.3: Register for Examination
4.3 Validation
Validation is the process of checking that a software system meets specifications and
that it fulfills its intended purpose. It may also be referred to as software quality
control. It is normally the responsibility of software testers as part of the software
development life cycle.Validation checks that the product design satisfies or fits the
intended use (high-level checking), i.e., the software meets the user requirements.
This is done through dynamic testing and other forms of review.Results of validation
testing of test case scenarios are:-
Table 4.4: Validation
13
4.4 Conclusion
In this chapter various test cases were designed and validated. The project passed the
all four test cases designed.
14
CHAPTER : 5
METHODOLOGY
5.1 Objectives:
 To provide an interface through which student can appear for examination for
objective as well as subjective type questions.
 To provide registration for students done by themselves.
 To not provide facility of copy and paste while attempting the Subjective
questions on the web page.
 When the student starts the exam the timer will start automatically and show
the student how much time is left.
 The questions will be display randomly from question bank.
 Objective answers will be checked automatically by the system from the
database.
 For subjective answer manually checking by exam department will take place.
 To provided user name and password facility and credentials should be
checked properly at the time of login for student, expert, controller and Exam
Dept Admin.
 To provide an interface from where controller will create new Expert and
Admin for Exam Dept.
 The authority to modify the criteria is provided to the controller of
examination.
 To facilitate Experts to send a collection of questions in Question Bank.
 The Exam Dept will manage the question bank sent by experts.
 To facilitate Exam Dept Admin to make schedule and declare Result.
15
5.2 Software Requirement
 NetBeans IDE 8.2

 Technologies : Core java, jdk 10.0.1
 Xampp Control Panel v3.2.2
 Operating System : Windows XP or Advanced
4.3 Hardware Requirement
 Intel 3.0 ghz or higher

 processor 2 GB
 RAM 10 GB HDD Space
16
CHAPTER : 6
PROJECT IMPLEMENTATION
6.1 Front End

Our front is designed using NetBeans to design the UI and JAVA to design the logics.
So screenshots of the whole project are included below with the explanation.
Implementation
MainFrame.Java :
Source Code -
import javax.swing.JFrame;
public class MainFrame extends javax.swing.JFrame {
/** Creates new form MainFrame */

public MainFrame() {
initComponents();
}
public void setChild(JFrame child) {
this.child = child;
}
/** This method is called from within the constructor to
* initialize the form.
* WARNING: Do NOT modify this code. The content of this method is
* always regenerated by the Form Editor.
*/
17
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated Code">
private void initComponents() {
jPanel1 = new javax.swing.JPanel();

btnExamination = new javax.swing.JButton();
btnRegistration = new javax.swing.JButton();
lblTitle = new javax.swing.JLabel();
jLabel1 = new javax.swing.JLabel();
setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);
setTitle("Online Examination System");
setResizable(false);
jPanel1.setBackground(new java.awt.Color(255, 255, 255));
btnExamination.setFont(new java.awt.Font("Segoe Print", 1, 14)); // NOI18N

btnExamination.setText("Examination");
btnExamination.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
btnExaminationActionPerformed(evt);
}
});
18
btnRegistration.setFont(new java.awt.Font("Segoe Print", 1, 14)); // NOI18N

btnRegistration.setText("Registration");
btnRegistration.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
btnRegistrationActionPerformed(evt);
}
});
lblTitle.setFont(new java.awt.Font("Microsoft Sans Serif", 1, 24)); // NOI18N

lblTitle.setText(" RAAS Examination System Welcomes You");
jLabel1.setIcon(new
javax.swing.ImageIcon("C:\\Users\\Rishav\\Desktop\\Capture34.PNG")); // NOI18N
jLabel1.setText("jLabel1");
jLabel2.setIcon(new
javax.swing.ImageIcon(getClass().getResource("/Capture99999.png"))); // NOI18N
jLabel3.setIcon(new
javax.swing.ImageIcon(getClass().getResource("/Capture888.PNG"))); // NOI18N
jLabel4.setFont(new java.awt.Font("Tahoma", 0, 12)); // NOI18N

jLabel4.setText("DEVELOPED BY: Rishav , Aditya , Ankush , Shubham students of
ABGIET (Shimla)");
jLabel5.setFont(new java.awt.Font("Tahoma", 0, 12)); // NOI18N

jLabel5.setText("Under The Guidance of Er. Shivani Thakur (Asst. Prof CSE Dpt)");
19
javax.swing.GroupLayout jPanel1Layout=new javax.swing.GroupLayout(jPanel1);

jPanel1.setLayout(jPanel1Layout);
jPanel1Layout.setHorizontalGroup(
jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(javax.swing.GroupLayout.Alignment.TRAILING,
jPanel1Layout.createSequentialGroup()
.addGap(0, 0, Short.MAX_VALUE)
.addComponent(lblTitle, javax.swing.GroupLayout.PREFERRED_SIZE, 535,
javax.swing.GroupLayout.PREFERRED_SIZE)
.addGap(279, 279, 279))
.addGroup(jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.T
RAILING)
.addGroup(jPanel1Layout.createSequentialGroup()
.addGap(28, 28, 28)
.addComponent(jLabel1, javax.swing.GroupLayout.PREFERRED_SIZE,
256, javax.swing.GroupLayout.PREFERRED_SIZE)
.addGroup(jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.L
EADING)
.addGap(36, 36, 36)
.addComponent(jLabel4))
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED)
20
.addComponent(jLabel5,
javax.swing.GroupLayout.PREFERRED_SIZE,365,
.addGap(58, 58, 58))))
EADING)
.addGap(50, 50, 50)
javax.swing.GroupLayout.PREFERRED_SIZE))
.addGap(103, 103, 103)
javax.swing.GroupLayout.PREFERRED_SIZE)))
.addGap(71, 71, 71)
RAILING)
.addComponent(btnExamination,
.addComponent(btnRegistration,
.addGap(0, 0, Short.MAX_VALUE)))
.addGap(107, 107, 107))
);
jPanel1Layout.setVerticalGroup(
21
jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addContainerGap()
EADING)
.addComponent(jLabel1, javax.swing.GroupLayout.PREFERRED_SIZE, 84,
42, javax.swing.GroupLayout.PREFERRED_SIZE)
30, javax.swing.GroupLayout.PREFERRED_SIZE)))
.addGap(18, 18, 18)
.addComponent(lblTitle, javax.swing.GroupLayout.PREFERRED_SIZE, 45,
.addGap(57, 57, 57)
RAILING)
.addComponent(jLabel2)
.addComponent(btnExamination,
EADING)
22
208, javax.swing.GroupLayout.PREFERRED_SIZE))
.addGap(97, 97, 97)
.addComponent(btnRegistration,
javax.swing.GroupLayout.PREFERRED_SIZE)))
.addContainerGap(104, Short.MAX_VALUE))
);
javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());

getContentPane().setLayout(layout);
layout.setHorizontalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
layout.createSequentialGroup()
.addComponent(jPanel1,javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)
.addContainerGap())
);
layout.setVerticalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addComponent(jPanel1,javax.swing.GroupLayout.Alignment.TRAILING,
javax.swing.GroupLayout.DEFAULT_SIZE,javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE)
);
pack();
}// </editor-fold>
23
private void btnRegistrationActionPerformed(java.awt.event.ActionEvent evt) {

RegistrationFrame f = new RegistrationFrame();
f.setLocationRelativeTo(null);
f.setParentFrame(this);
f.setVisible(true);
this.setVisible(false);
}
private void btnExaminationActionPerformed(java.awt.event.ActionEvent evt) {

LoginFrame f = new LoginFrame("exam");
f.setParentFrame(this);
f.setVisible(true);
this.setVisible(false);
}
/**
* @param args the command line arguments
*/
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {

MainFrame f = new MainFrame();
f.setVisible(true);
}
});
24
}
// Variables declaration - do not modify
private javax.swing.JButton btnExamination;
private javax.swing.JButton btnRegistration;
private javax.swing.JLabel jLabel1;
private javax.swing.JPanel jPanel1;
private javax.swing.JLabel lblTitle;
// End of variables declaration
private JFrame child;
}
6.2 Back End
As you might have come to know by now that we are using firebase as our
backend utility. So we need not to do any extra effort for maintaining the
backend either for authentication or for the storage of student‘s data.
Everything here is maintained by the firebase itself. But surely there are
certain things which we can monitor and do with the help of firebase and
those are mentioned below:
WELCOME FORM:
This is the very first page of the Raas Examination System having two
25
buttons for examination and registration (For new user).
Figure 6.1( Home Page)
26
REGISTRATION FORM:
The registration page is made for new user to login into Raas Examination
System.
Figure 6.2(Registeration Page)
27
LOGIN FORM :
The Login Form is made for Security Purpose . So only Authenticated User only
access into the Project.
Figure 6.3(Log in Page)
28
SELECTION OF SUBJECT:
Figure 6.4(Select Exam Page)
29
QUESTION PATTERN:
Figure 6.5(Test Frame)
30
Exam Result :
This is the last page of the Raas Examination System gives user
result. It also provides an option to save / print the given result.
Figure 6.6(Result Report)
31
Chapter :7
CONCLUSION
The Raas Examination System is developed using Java and PhpMyAdmin fully meets
the objectives of the system for which it has been developed. The system has reached
a steady state where all bugs have been eliminated. The system is operated at a high
level of efficiency and all the teachers and user associated with the system
understands its advantage. The system solves the problem. It was intended to solve as.
This System provides facility to conduct examination worldwide. It saves time as it

allows number of students to give the exam at a time and displays the results as the
test gets over, so no need to wait for the result. It is automatically generated by the
server. System is developed using Java Platform that fully meets the objectives of the
system for which it has been developed. The system has reached a steady state where
all bugs have been eliminated. The system is operated at a high level of efficiency and
all the teachers and user associated with the system understands its advantage.. User
can register, login and give the test with his specific id, and can see the results as well.
32
Chapter : 8
FUTURE ENHANCEMENT
The basic aim of the project was to pave way for a user-friendly and an interactive
session in the classroom for a better future. The task has been successfully completed
by the team and all the above mentioned features and characteristics have been
incorporated in these:
Figure 7.2: (Examination control in Future)

regarding this project can be:
 Add images with Questions for better understanding of questions.

 Polling should have editable options and a feature to add more choices when
needed, also students can optionally give their views in brief with votes on
same topic.
 Enable students to know their relative performance after each quiz.
 Teacher should able to view a Students performance for entire semester,
overall performance as well as performance in each quiz.
33
 Lastly, if the Instructor is physically unable to attend any lecture, he can

conduct the lecture remotely or have pre-planned activity for students, which
would be conducted automatically in absence of Instructor.
 Tutorials can be integrated into the application where in the student can
browse through the subject whenever required.
 Use GPS for giving quiz such that, no two near students gets the same order.
 To implement batching algorithm so that access point will be more he project.
34
BIBLIOGRAPHY
[1] H.M.DIETEL.P.J.DIETEL,Java How to Program,PhL, Second Edition,

page 169.
[2] Gray Cornett, Horstmann, Corel Java, Sunsoft Press, 1996.
[3] Grady Booch, Object Oriented Analysis and Design with Applications,
the Benjamin and Cummings, 1994.
[4] Baker, F. T. “Chief Programmer Team Management of Production
Programming,” IBM Systems Journal, 11(1), 1972.
[5] http://stackoverflow.com/questions/tagged/java
[6] http://www.javatpoint.com/encrypt-servlet.html
[7] http://www.ibm.com/developerworks/library
[8] http://www.java.sun.com/products/java
[9] http://www.javaworld.com/category/java-app-dev
35

New RAAS

Uploaded by

Copyright:

Available Formats

New RAAS

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

New RAAS

Uploaded by

Copyright:

Available Formats

Minor Project Report Raas Examination System

1.2 Technologies Used

Back end as:

2.1 Feasibility Study

2.1.1. Economic Feasibility

2.1.2. Technical Feasibility

2.1.3. Behavioural Feasibility

2.2. Existing System :

 Quest won't get update automatically need to update manually.

2.3. Proposed System :

Characteristics of the Proposed System :

Need for the Proposed System :

Aims and Objective

The main purpose behind the proposed system is to provide a comprehensive

Constraints, Assumptions, Dependencies

• Server OS should be Windows NT/2000/XP.

• Client PC should be Windows 9X/NT/WorkStation or Windows 2000with latest

DATA FLOW DIAGRAM

3.1. Use Case Diagram

Fig 3.1(Data Flow Diagram)

Testing and Validation

Software testing is an investigation conducted to provide stakeholders with

4.1.1 Testing Strategies

Testing is a set of activities that can be planned in advance and conducted

Software testing is one element of verification and validation. Verification refers to

The objective of software testing is to uncover errors. To fulfill this objective, a

Integration testing is a systematic technique for constructing the program structure

4.2 Design of test cases

The test case design of login is given below.

Table 4.1: Login

This test case checks whether client is able to register.

Table 4.2: User Register

4.2.3 Registration for Examinatation

Table 6.3: Register for Examination

Table 4.4: Validation

all four test cases designed.

5.2 Software Requirement

 NetBeans IDE 8.2

4.3 Hardware Requirement

 Intel 3.0 ghz or higher

6.1 Front End

public class MainFrame extends javax.swing.JFrame {

/** Creates new form MainFrame */

jPanel1 = new javax.swing.JPanel();

jPanel1.setBackground(new java.awt.Color(255, 255, 255));

btnExamination.setFont(new java.awt.Font("Segoe Print", 1, 14)); // NOI18N

btnRegistration.setFont(new java.awt.Font("Segoe Print", 1, 14)); // NOI18N

lblTitle.setFont(new java.awt.Font("Microsoft Sans Serif", 1, 24)); // NOI18N

jLabel4.setFont(new java.awt.Font("Tahoma", 0, 12)); // NOI18N

jLabel5.setFont(new java.awt.Font("Tahoma", 0, 12)); // NOI18N

javax.swing.GroupLayout jPanel1Layout=new javax.swing.GroupLayout(jPanel1);

javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());

private void btnRegistrationActionPerformed(java.awt.event.ActionEvent evt) {

private void btnExaminationActionPerformed(java.awt.event.ActionEvent evt) {

public void run() {

6.2 Back End

buttons for examination and registration (For new user).

Figure 6.1( Home Page)

Figure 6.2(Registeration Page)