A Project Report

On
Job Management System

Submitted in partial fulfilment of the requirements for the award of degree of

Bachelor of Business Administration (Computer Application)

Submitted By:

Surabhi Sinha
&
Sonu Kumar

Academic Year: 2020– 2021

Submitted to:

Savitribai Phule Pune University

Shree Chanakya Education Society

Indira College of Commerce and Science, Pune

Vice Principal & (H.O.D) Guided By

Prof. Shivendu Bhushan Prof. Shubhangi Chavan
 Index
Sr.N Particular Page No.
o
A) Introduction 3

1) Title of Project 4

2) Existing System 5

3) Proposed System 6

4) Advantages of proposed System 7

5) Feasibility Study 8

6) Hardware/Software Requirement 10

B) Analysis 11

1) ERD 11

2) DFD 12

3) CLD 12

4) First Level DFD 13

5) File Design / Normalized database 18

6) Data Dictionary 21

C) Design 23

1) Input screen (Without Data) 23

2) Input screen (With Data) 31

3) Reports 34

D) Code Design (Sample code) 38

E) Limitations of System 45

F) Conclusion 46

G) Future Enhancement 47

H) Bibliography 48

1
 Acknowledgement
We would like to express our sincere and heartfelt gratitude to our institution” Indira
College of Commerce and Science” which provided us with excellent opportunity to achieve our
most cherished goal in life to become Bachelor degree in BBA-CA.

We are extremely grateful to our respected Vice Principal and HOD Prof, Shivendu
Bhushan for providing excellent academic environment which has made this endeavor possible.

We take this opportunity to express our gratitude to our guide, Prof. Shubhangi Chavan
for her constant encouragement in making this project unmitigated success. Their thoughtfulness
and understanding was vast and thoroughly helpful in successful completion of project. Our
sincere thanks to all our faculties and non-teaching staff for their at most co-operation.

Finally we proudly thank our parents and friends for their constant support and priceless
guidance in throughout this endeavor.

2
 Introduction

The importance of placement system is increasing day by day. Thousands of applicants are
depending on placement cell. But the applicants are facing so many problems. This project is an
attempt to minimize the problems of an applicant to find a correct job and will save the efforts
and money of the recruiters to find a suitable candidate. It will be so fast and convenient for the
applicants. As new technologies have predominantly made life better and considerably easier for
most people, and so it must be concluded that this system would be welcomed.

So, our system serves as a platform that helps to join the recruiters and the job seekers to
complete their requirements and goals. The recruiters look for the right candidate who has the
right qualification to handle the responsibilities efficiently. And job seekers look for a job where
they have a job security and are paid rightly. They look for a working environment which will
eventually help them to succeed and climb up their career ladder.

This system will work as a medium between the recruiters and job seekers. Eventually gathering
the data and match-making for the best of results skimming through all the fraudulent
applications out. And providing the future of our country their suitable jobs and work space.

3
 Title of Project

Job Management System

(JMS)

4
 Existing System

The present system requires applicants to search through print and visual media for job
opportunities. Applicants need to apply for jobs using conventional methods and appear for
interviews on a specified date at a specified location. In the current manual system job seekers
had to send resumes and cover letters by mail, deliver them in person or fax them, and then wait
for an interview request. Employers need to advertise the vacancies and sort all applicant details,
conduct selection procedures and complete the formalities. The job application process took
quite some time. This approach is tedious and requires much effort and resources. This process
was equally frustrating for recruiters, as it often took some time to fill positions with qualified
candidates.

5
 Proposed System

The proposed system is a management system which allows Applicants and Employers to
register their details. This system will save jobseekers time and money that would have been
spent on manually visiting organizations to look for job vacancies and also the time and money
employers would have spent to make billboards, flyers, advertisements. And also, Employers
are able to view and search for good candidates.

The below are some of the modules that are added to our system :

1. Admin Details
2. Staff Details
3. Applicant’s Details
4. Company’s Details
5. Job Details

6
 Advantages of the Proposed System

The following are the major advantages of using our system:

1. The system has a very user-friendly interface which makes it easy to handle for any person.

2. Employers can identify a large number of eligible candidates and get their information easily.

3. Cost saving. The companies using the system spend less to advertise their job vacancies as
compared to the traditional method of advertising.

4. It saves time and is safe. You don’t need to go out of your house and attend pre-fixed meeting
and appear for appointments. The candidate can easily send their resumes sitting at home as soon
as their request in approved.

5. Registration is free of cost and available anytime and anywhere. You just need to have your
device registered and you can use the service remotely as well.

7
 Feasibility Study

The proper analysis of the practicality of a proposed system, aiming to objectively and rationally
uncover the strengths and weakness of an existing business or proposed venture, analyzing the
opportunities and threats. Feasibility study is useful to evaluate the cost and benefit of the system
requested. This is nothing but a test, which is conducted on the proposed system, how the
requirements are achieved. It is also used to understand the scope. The feasibility study tries to
anticipate future scenarios of software development.

There are three major aspects in the feasibility study :

1. Technical Feasibility

2. Economical Feasibility

3. Operational Feasibility

1. Technical Feasibility :
The technical feasibility always focuses on the existing computer hardware and software
personnel. This includes the need for more hardware or software personnel and the possibility of
procuring or installing such facility.

The proposed system of job management does not require additional hardware and software. The
proposed system has the minimum requirement for hardware and software which are easily
available. Hence the proposed system is technically feasible.

8
2. Economical Feasibility :
Economical feasibility considers the cost benefits analysis of the proposed system. The benefits
are always expected to be overweighting the cost. Economical feasibility is helpful to find the
system development cost hence and checks whether it is justifiable for that it concentrate on.

1. Investigation cost.
2. Software and hardware cost.
3. Salaries and maintenance cost.
4. Supply cost
The proposed system requires minimum hardware and maintenance cost. Hence it is
economically feasible.

3. Operational Feasibility :
It considers the acceptability of the system. It checks whether system will be used if it developed
and implemented. It checks whether the users of the system will be able to handle as if the
proposed system does not create any problems.

The proposed system will be easy to handle as the overview is according to the requirement of
the user. It reduces extra workload of the user providing to be beneficial. Hence the proposed
system is operationally feasible.

9
 Hardware and Software Requirements

Software & Hardware Requirement

Operating System: Microsoft Windows

Software Requirement :-

Front –End Software: Net beans 8.2

Back-End Software: Microsoft Access
Hardware Requirement:-

Processer : Intel core i3 1.80GHZ

RAM : 2GB or More
Monitor : LCD monitor

Keyboard : Normal keyboard

Mouse : Compatible mouse

10
 ANALYSIS

Entity Relationship Diagram

(ERD)

An entity-relationship diagram is a type of structural diagram for use in database design. An

ERD contains different symbols and connectors that visualize two important information :
The major entities within the system scope, and the inter-relationship among these entities. There
are three basic elements in ER-Diagram :

1. Entities - They are the ‘things’ for which we want to store information. An entity can be a
person, place, thing or an event.

2. Attributes - They are the data we want to collect for an entity.

3. Relationships – They describe the relations between the entities. The following are some
symbols used in the ER-Diagram :

(1). This represents Entity.

(2). This represents Relationship.

(3). This represents Attributes.

(4). This line connects the entities to the attributes.

11
 The following is the Entity-Relationship Diagram of our System :

Admin

Create
Account

Receive Receive
Company Information Staff Details Applicant

Post Get
Vacancy Job

Approves Application
Gives

12
 Data Flow Diagram
A data flow diagram (DFD) graphically describes business processes and the flow of information
that passes among them. DFD also describes inputs and outputs of the process; and where the
data will be stored. Data Flow diagram starts with:

Context Level Diagram(CLD)

Context Level Diagram(CLD) also known as Zero level Diagram is the highest level in the Data
Flow Diagram. It is a popular tool for Business Analysts who use to understand the details and
boundaries of the system which is to be designed in the project. It basically defines the boundary
between the system or part of a system and its environment, showing the entities that interact
with it. This is the high level view of a system.
The following is the Context Level Diagram for our system :

0.0 Salar
Applicant
y
Staff Details
Staff Company
Details
Staff
Applicatio Job Applicant
Job Job
Details
n Details Data
Details
Applicant Applicant Company Applicant
Management Details
Vacancy Applicatio
Company System n
Job Details Applicant Company
Details
Report Generation
Query Admin
Admin Fired

13
 First Level Data Flow Diagram

In First-Level Data Flow Diagram, the context diagram is decomposed into multiple bubbles or
processes. In this level, we highlight the main functions of the system and breakdown the high-
level process of 0-level DFD into subprocesses.

1.0
Staff Details
Staff
Master Salary

Staff Staff Details Generation Applicant Details

Applicant
Application Details
Plan
Job Details
Company Details Company

14
 1.0
2.0
Username Username
Staff Password
Password
Login Validation Login
Access to System
Username
Process
Admin Password

1.0
3.0
Applicant Details
Applicant
Application Details
Applicant
Registration
Company Details
Company Company Details Company

15
 1.0
4.0
Applicant Filing
Applicant Resume
Application Details
Application Job Details Application
Filling
Job Application Details
Company Job Details
Company
Details

5.0
Company Details
Search Availability of job Applicant
Criteria
Search Result Application Job Description

Verification Job Posting

Company
Applicant Details
& Approval
Approval Vacancy
Admin
Applicant Details Information
Application Details Job
Company Details

16
 1.0
6.0
Staff Details Staff_Details
Query Fired Applicant Details
Admin Report Applicant_Detail
Generated
Report Employed
Job_Provided
Generation Details
Company Details
Company_Detail
Job Details
Job_Details

17
 File Design / Normalized database

Database normalization is the process of organizing data into tables in such a way that the results
of using the databases are always unambiguous and as required. Data normalization prevents
from data redundancy and helps to improve data integrity.
The following are the normalized databases of our system:

1. Table Name : Admin_Login

Sr. No. Field Name Data Type Width Constraints
01. Ad_Id Number 10 Primary Key
02. Username Short Text 20 Not Null
03. Password Short Text 6 Not Null
04. First_Name Short Text 20 Not Null
05. Last_Name Short Text 20 Not Null
06. Gender Date/Time 7 Not Null
07. D_O_B Number 10 Not Null
08. Aadhar_Numbe Number 12 Not Null
r
09. Contact Long Text 10 Not Null
10. Email_Id Long Text 30 Not Null
11. Address Number 30 Not Null
12. Pincode Number 10 Not Null

18
2. Table Name: Applicant_Details
Sr.No. Field Name Data Type Width Constraints
01. Ap_Id Number 10 Primary Key
02. First_Name Short Text 20 Not Null
03. Last_Name Short Text 20 Not Null
04. Gender Short Text 7 Not Null
05. D_O_B Date/Time 10 Not Null
06. Aadhar_Number Number 12 Not Null
07. Contact Number 10 Not Null
08. Email_Id Long Text 30 Not Null
09. Address Long Text 30 Not Null
10. Pincode Number 10 Not Null
11. Resume Attachment Upto 2 GB Not Null
12. S_id Number 10 Foreign Key

3. Table Name: Company_Details

Sr.No. Field Name Data Type Width Constraints
01. C_Id Number 10 Primary Key
02. Company_Nam Short Text 20 Not Null
e
03. Company_Type Short Text 20 Not Null
04. Post_Available Long Text 30 Not Null
05. Vacancy Long Text 30 Not Null
06. Location Long Text 30 Not Null
07. Pincode Number 10 Not Null
08. Contact Number 10 Not Null
09. S_Id Number 10 Foreign Key

4. Table Name: Job_Provided

Sr.No. Field Name Data Type Width Constraints
01. Jp_Id Number 10 Primary Key
02. C_Id Number 10 Foreign Key
03. A_Id Number 10 Foreign Key
04. Salary Number 10 Not Null
05. Job_Application Short Text 20 Not Null
06. Appli_Contact Number 10 Not Null

19
5. Table Name: Job_Descr
Sr.No. Field Name Data Type Width Constraints
01. J_Id Number 10 Primary Key
02. Company_Name Short Text 20 Foreign Key
03. Designation Short Text 20 Not Null
04. Job_Descr Long Text 30 Not Null
05. Min_Exp Number 12 Not Null
06. Min_Sal Number 10 Not Null
07. Max_Sal Number 10 Not Null
08. Location Long Text 30 Not Null
09. Ug_Qualif Short Text 10 Not Null
10. Pg_Qualif Short Text 10 Not Null
11. Working_Hours Number 10 Not Null
12. Hr_Contact Number 10 Not Null
13. S_Id Number 10 Foreign Key

6. Table Name: Staff_Details

Sr.No. Field Name Data Type Width Constraints
01. S_Id Number 10 Primary Key
02. Username Short Text 20 Not Null
03. Password Short Text 10 Not Null
04. First_Name Short Text 20 Not Null
05. Last_Name Short Text 20 Not Null
06. Gender Short Text 7 Not Null
07. D_O_B Date/Time 10 Not Null
08. Aadhar_Number Number 12 Not Null
09. Contact Number 10 Not Null
10. Email_Id Short Text 20 Not Null
11. Address Long Text 30 Not Null
12. Pincode Number 10 Not Null
13. Hire_Date Date/Time 10 Not Null

20
 Data Dictionary

A data dictionary is a file or set of files that contains a database’s metadata. The data dictionary
contains records about other objects in the database, such as data ownership, data relationships to
the other object, and other data. It provides additional information about relationships between
different database tables, helps to organize data in a neat and easily searchable way, and prevents
data redundancy.
The following is the Data Dictionary of our system :

Sr.no. Field Name Data Type Width Constraints Description Table Name

01. Ad_Id Number 10 Primary Key Admin Id Admin_Login

02. Username Short Text 20 Not Null Username for login Admin_Login
03. Password Short Text 6 Not Null Password for login Admin_Login
04. First_Name Short Text 20 Not Null Admin Detail Id Admin_Login
05. Last_Name Short Text 20 Not Null First name Admin_Login
06. Gender Date/Time 7 Not Null Last name Admin_Login
07. D_O_B Number 10 Not Null Gender Admin_Login
08. Aadhar_Number Number 12 Not Null Date of Birth Admin_Login
09. Contact Long Text 10 Not Null Aadhar no. of admin Admin_Login
10. Email_Id Long Text 30 Not Null Phone number Admin_Login
11. Address Number 30 Not Null Admin’s email Admin_Login
12. Pincode Number 10 Not Null Address of admin Admin_Login
13. Pincode Number 10 Not Null Pin Code Admin_Login
14. Ap_Id Number 10 Primary Key Applicant Id Applicant_Details
15. First_Name Short Text 20 Not Null First name Applicant_Details
16. Last_Name Short Text 20 Not Null Last name Applicant_Details
17. Gender Short Text 7 Not Null Gender Applicant_Details
18. D_O_B Date/Time 10 Not Null Date of Birth Applicant_Details
19. Aadhar_Number Number 12 Not Null Applicant’s Aadhar Applicant_Details
20. Contact Number 10 Not Null Phone number Applicant_Details
21. Email_Id Long Text 30 Not Null Applicant’s email Applicant_Details
22. Address Long Text 30 Not Null Applicant’s address Applicant_Details
23. Pincode Number 10 Not Null Pin code Applicant_Details

21
24. Resume Attachment >2GB Not Null Resume of Applicant Applicant_Details
25. S_id Number 10 Foreign Key Staff Id Staff_Details
26. C_Id Number 10 Primary Key Company Id Company_Details
27. Company_Name Short Text 20 Not Null Name of company Company_Details
28. Company_Type Short Text 20 Not Null Type of industry Company_Details
29. Post_Available Long Text 30 Not Null Type of posts Company_Details
30. Vacancy Long Text 30 Not Null Number of jobs Company_Details
31. Location Long Text 30 Not Null Location of company Company_Details
32. Pincode Number 10 Not Null Pincode Company_Details
33. Contact Number 10 Not Null Contact number Company_Details
34. J_Id Number 10 Primary Key Job id Job_Descr
35. Company_Name Short Text 20 Foreign Key Name of company Company_Details
36. Designation Short Text 20 Not Null Type of post Job_Descr
37. Job_Descr Long Text 30 Not Null About the job Job_Descr
38. Min_Exp Number 12 Not Null Previous experience Job_Descr
39. Min_Sal Number 10 Not Null Minimum Salary Job_Descr
40. Max_Sal Number 10 Not Null Maximum Salary Job_Descr
41. Location Long Text 30 Not Null Location of the job Job_Descr
42. Ug_Qualif Short Text 10 Not Null Grad. qualification Job_Descr
43. Pg_Qualif Short Text 10 Not Null P.Grad. qualification Job_Descr
44. Working_Hours Number 10 Not Null Total working hours Job_Descr
45. Hr_Contact Number 10 Not Null Contact of HR Job_Descr
46. S_Id Number 10 Foreign Key Staff Login id Staff_Details
47. Username Short Text 20 Not Null Username for login Staff_Details
48. Password Short Text 10 Not Null Password for login Staff_Details
49. First_Name Short Text 20 Not Null Staff Details id Staff_Details
50. Last_Name Short Text 20 Not Null Username for login Staff_Details
51. Gender Short Text 7 Not Null Password for login Staff_Details
52. D_O_B Date/Time 10 Not Null First name Staff_Details
53. Aadhar_Number Number 12 Not Null Last name Staff_Details
54. Contact Number 10 Not Null Gender Staff_Details
55. Email_Id Short Text 20 Not Null Date of Birth Staff_Details
56. Address Long Text 30 Not Null Aadhar no. of Staff Staff_Details
57. Pincode Number 10 Not Null Phone number Staff_Details
58. Hire_Date Date/Time 10 Not Null Email of staff Staff_Details
59. Jp_Id Number 10 Primary Key Table id Job_Provided
60. C_Id Number 10 Foreign Key Company Id Company_Details
61. A_Id Number 10 Foreign Key Applicant_Id Applicant_Details
62. Salary Number 10 Not Null Salary for the job Job_Provided

22
63. Job_Application Short Text 20 Not Null Job Application Job_Provided
64. Appli_Contact Number 10 Not Null Contact Number Job_Provided

23
 Design
Input Screen(Without Data)

Admin Login

24
25
Staff Login

Add New Staff

26
Add New Company
27
28
Add Applicant

29
Admin Profile

30
Job Details

31
Admin Page

32
Job Provided

33
Input Screen(With Data Entry)

Admin Login

34
Staff Login

35
Add Staff

36
New Company

37
New Applicant

38
Admin Profile

39
Job Details

40
 Data Reports

Applicant Data Report

41
Company Data Report

42
43
Job Provided Data Report

44
Job Details Data Report

45
Staff Data Report

46
 Code Design

package jobmanagementsystem;

import java.awt.Color;
import java.awt.HeadlessException;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.text.SimpleDateFormat;
import javax.swing.JOptionPane;

public class Add_staff extends javax.swing.JFrame {

Connection con;
PreparedStatement pst;
ResultSet rs;
int i,pin,lastid;
String Fn,ln,gender,email,Add,user,pass,dob,hire,Aadhar,cont ,sql;

public Add_staff() {
initComponents();

try {

47
 Class.forName("net.ucanaccess.jdbc.UcanaccessDriver");
con=DriverManager.getConnection("jdbc:ucanaccess://D:/jms.accdb");
sql="select max(S_id) from Staff_Details";
pst=con.prepareStatement(sql);
rs=pst.executeQuery();
if (rs.next()) {
lastid=rs.getInt(1);
lastid++;
jTextField8.setText(Integer.toString(lastid));
}
} catch (ClassNotFoundException | SQLException e) {
}

getContentPane().add(jButton1, new org.netbeans.lib.awtextra.AbsoluteConstraints(704,

412, 136, 41));

jButton2.setFont(new java.awt.Font("Sanskrit Text", 1, 24));

jButton2.setActionCommand("");
jButton2.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
jButton2ActionPerformed(evt);
}
});
getContentPane().add(jButton2, new org.netbeans.lib.awtextra.AbsoluteConstraints(704,
336, -1, 41));

jButton3.setFont(new java.awt.Font("Sanskrit Text", 1, 24));

48
 jButton3.setText("UPDATE");
jButton3.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
jButton3ActionPerformed(evt);
}
});
getContentPane().add(jButton3, new org.netbeans.lib.awtextra.AbsoluteConstraints(923,
336, -1, 41));

jButton4.setFont(new java.awt.Font("Sanskrit Text", 1, 24));

jButton4.setText("CLEAR");
jButton4.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
jButton4ActionPerformed(evt);
}
});
getContentPane().add(jButton4, new org.netbeans.lib.awtextra.AbsoluteConstraints(923,
412, 141, 41));

jLabel14.setFont(new java.awt.Font("Sanskrit Text", 0, 18));

jLabel14.setText("S_id");
getContentPane().add(jLabel14, new org.netbeans.lib.awtextra.AbsoluteConstraints(76, 73,
-1, -1));

jTextField8.setFont(new java.awt.Font("Sanskrit Text", 0, 14));

getContentPane().add(jTextField8, new org.netbeans.lib.awtextra.AbsoluteConstraints(146,
75, 37, -1));

jButton5.setFont(new java.awt.Font("Harrington", 1, 14));

jButton5.setText("Find");

49
 jButton5.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
jButton5ActionPerformed(evt);
}
});
getContentPane().add(jButton5, new org.netbeans.lib.awtextra.AbsoluteConstraints(212,
73, -1, -1));

jButton6.setFont(new java.awt.Font("Sanskrit Text", 1, 14));

jButton6.setText("Prev.");
jButton6.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
jButton6ActionPerformed(evt);
}
});
getContentPane().add(jButton6, new org.netbeans.lib.awtextra.AbsoluteConstraints(12, 12,
-1, -1));

jLabel15.setIcon(new javax.swing.ImageIcon("D:\\works\\projects\\job portal management

system\\design\\razvan-chisu-Ua-agENjmI4-unsplash.jpg")); // NOI18N
getContentPane().add(jLabel15, new org.netbeans.lib.awtextra.AbsoluteConstraints(-10, -
10, 1230, 740));

pack();
}

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

50
 private void jButton6ActionPerformed(java.awt.event.ActionEvent evt) {

Add_staff.this.setVisible(false);
Admin_details s=new Admin_details();
s.setVisible(true);
}
jTextField6.setText("");
jTextField7.setText("");
jTextField9.setText("");
jPasswordField1.setText("");
jDateChooser1.setDate(null);
jDateChooser2.setDate(null);
jRadioButton1.setSelected(false);
jRadioButton2.setSelected(false);

public static void main(String args[]) {

try {
for (javax.swing.UIManager.LookAndFeelInfo info :
javax.swing.UIManager.getInstalledLookAndFeels()) {
if ("Nimbus".equals(info.getName())) {
javax.swing.UIManager.setLookAndFeel(info.getClassName());
break;
}
}

51
 } catch (ClassNotFoundException ex) {

java.util.logging.Logger.getLogger(Add_staff.class.getName()).log(java.util.logging.Level.SEV
ERE, null, ex);
} catch (InstantiationException ex) {

java.util.logging.Logger.getLogger(Add_staff.class.getName()).log(java.util.logging.Level.SEV
ERE, null, ex);
} catch (IllegalAccessException ex) {

java.util.logging.Logger.getLogger(Add_staff.class.getName()).log(java.util.logging.Level.SEV
ERE, null, ex);
} catch (javax.swing.UnsupportedLookAndFeelException ex) {

java.util.logging.Logger.getLogger(Add_staff.class.getName()).log(java.util.logging.Level.SEV
ERE, null, ex);
}

java.awt.EventQueue.invokeLater(() -> {
new Add_staff().setVisible(true);
});
}
// Variables declaration - do not modify
private javax.swing.JButton jButton1;
private javax.swing.JButton jButton2;
private javax.swing.JButton jButton3;
private javax.swing.JButton jButton4;
private javax.swing.JButton jButton5;
private javax.swing.JButton jButton6;
private com.toedter.calendar.JDateChooser jDateChooser1;
private com.toedter.calendar.JDateChooser jDateChooser2;

52
private javax.swing.JLabel jLabel1;
private javax.swing.JLabel jLabel10;
private javax.swing.JLabel jLabel11;
private javax.swing.JLabel jLabel12;
private javax.swing.JLabel jLabel13;
private javax.swing.JLabel jLabel14;
private javax.swing.JLabel jLabel15;
private javax.swing.JLabel jLabel2;
private javax.swing.JLabel jLabel3;
private javax.swing.JLabel jLabel4;
private javax.swing.JLabel jLabel5;
private javax.swing.JLabel jLabel6;
private javax.swing.JLabel jLabel7;
private javax.swing.JLabel jLabel8;
private javax.swing.JLabel jLabel9;
private javax.swing.JPasswordField jPasswordField1;
private javax.swing.JRadioButton jRadioButton1;
private javax.swing.JRadioButton jRadioButton2;
private javax.swing.JTextField jTextField1;
private javax.swing.JTextField jTextField2;
private javax.swing.JTextField jTextField3;
private javax.swing.JTextField jTextField4;
private javax.swing.JTextField jTextField5;
private javax.swing.JTextField jTextField6;
private javax.swing.JTextField jTextField7;
private javax.swing.JTextField jTextField8;
private javax.swing.JTextField jTextField9;

53
 Limitations of the Proposed System

The system has some minor drawbacks which are as follows:

1. Data Security can be one of the major issues as the data is stored on the database on the
system which is accessible to all and records can be disarranged to tangle the work-flow.

2. Once deleted whether deliberately or unintentionally the retrieval of data will be a tedious task
and will require a lot of effort and time.

3. Sometimes there can be connectivity issue.

4. It can cause a little hassle for people who are not from the IT background and also who are not
used to the new technologies.

54
 Conclusion

We had a great experience while developing this software which gave us a clear picture of
visual basic and its functionality.
We had a good guidance from our project guide who helped us to develop this software.
Now we have a better knowledge of using NetBeans 8.2
We got a first-hand experience and a good understanding about how to implement real life
system into software application.
We have learned how to Analyze real life system to convert it into a software application.
And most importantly this experience taught us how to work in a team.

55
 Future Enhancement

1. In future we can develop this software for multiple user at a time.

2. We can make this existing single machine system into client and server base system.
3. We can conduct exams in future by developing a driving license test.
4. We can add new function to send machine generated messages for E-challans.
5. Also we can collect online payments in future.

56
 Bibliography

Reference Books:-
1. Informatics Practices By Sumita Arora.
2. Java Ee 7 Development with NetBeans 8 By David R. Heffelfinger.

Reference Websites :-
1. http://stackify.com
2. http://netbeans.org
3. http://www.codeacademy.com

57
58