Employee Management System Report

PROJECT REPORT
ON
LIBRARY MANAGEMENT
SYSTEM
In
JAVA
MINOR PROJECT
BLS INSTITUTE OF TECHNOLOGY

MANEGEMNT
SUBMITTED TO: ASHWANI SANGWAN
Submitted by: MANAS SARKAR

ENROLL NO. : 00520502014
1
BLS INSTITUTE OF TECHNOLOGY MANAGEMENT
CERTIFICATE
NAME OF THE STUDENT : SANJIT SHARMA
ENROLLMENT NO. : 30320502014
TITLE : EMPLOYMENT MANAGEMENT SYSTEM
This is to certify that the project entitled EMPLOYMENT

MANAGEMENT SYSTEM is a Bonafide work done by the SANJIT
SHARMA(ENROLLMENT NO.: 30320502014) in partial fulfillment of
the requirements for the BACHELOR OF COMPUTER APPLICATION
during the academic year 2016 in the original work of candidate.
PROJECT GUIDE BY:
MR. ASWANI SANGWAN
2
ACKNOWLEDGEMENT
I express my Gratitude to MR. ASHWANI SANGWAN for her
help, guidance throughout the work for this project without which I
would not have been able to complete this project to such a success.
I would also like to thank my class mates who helped me directly or

indirectly in accomplishing this work
Finally I would also like to thank other faculty members who

provided me with Moral support during the course of this project.
STUDENT NAME:
SANJIT SHARMA
30320502014
3
ABSTRACT
Employee Management System is a distributed application, developed to maintain the details of

employees working in any organization. It maintains the information about the personal details of their
employees, also the details about the payroll system which enable to generate the payslip. The
application is actually a suite of applications developed using Java.
It is simple to understand and can be used by anyone who is not even familiar with simple employees
system. It is user friendly and just asks the user to follow step by step operations by giving him few
options. It is fast and can perform many operations of a company.
This software package has been developed using the powerful coding tools of JAVA at Front End and
Microsoft Sql Server at Back End.The software is very user friendly. The package contains different
modules like Employee details. This version of the software has multi-user approach. For further
enhancement or development of the package, users feedback will be considered.
4
List of Symbol
Emp Employee
EMS Employee Management System
GUI- Graphical User Interface
Jdk Java Development Kit
SRS- Software Requirement Analysis
5
CONTENTS
1.INTRODUCTION
2.OBJECTIVES AND SCOPE
3.SYSTEM SPECIFICATION
a. Requirement Analysis
b. SRS
c. Hardware and Software Requirements
4.TOOLS , PLATFORM AND LANGUAGE USED
5.SYSTEM DESIGN
a. Data Flow Diagrams
b. Design Phase
c. Form Layouts
6. CODING
7. TESTING
8. IMPLEMENTATION, EVALUATION AND MAINTENANCE
9. CONCLUSION
10. BIBLIOGRAPHY
6
INTRODUCTION TO THE PROJECT
Employee Management system is an application that enables users to create and store Employee
Records. The application also provides facilities of a payroll system which enables user to generate Pay
slips too. This application is helpful to department of the organization which maintains data of
employees related to an organization .
Java is a platform independent language. Its created applications can be used on a standalone machine
as well as on distributed network. More over applications developed in java can be extended to Internet
based applications.
Thus java was chosen as background to design this application.
7
OBJECTIVE OF THE PROJECT
In this world of growing technologies everything has been computerized. With large number of work
opportunities the Human workforce has increased. Thus there is a need of a system which can handle
the data of such a large number of Employees in an organization. This project simplifies the task of
maintain records because of its user friendly nature.
8
SYSTEM SPECIFICATIONS
Software Engineers have been trying various tools, methods and procedures to control the process of
software development in order to build high quality software with high productivity. This method
provides how it is for building the software while the tools provide automated or semi automated
support for the methods. They are used in all stages of software development process, namely,
planning, analysis, design, development and maintenance. The software development procedure
integrates the methods and tools together and enables rational and timely development of the software
system.
Software Development
Procedures
Methods
Tools
They provide the guidelines as how to apply these methods and tools, how to
produce the deliverable at each stage, what controls to apply, and what milestones
to use to assess the performance of the program. There exist a number of software
development paradigms each using a different set of methods and tools. The
selection of a particular paradigm depends on the nature of application of the
programming language used for the controls and the deliverables required. The
development of such successful systems depends not only on the use of appropriate
methods and techniques but also the developers commitment to the objective of the
system.
9
A successful system must: -
1. Satisfy the user requirements
2. Be easy to understand by user and operator
3. Be easy to operate
4. Have a good user interface
5. Be easy to modify
6. Be expandable
7. Have adequate security control against the misuse of data
8. Handle the errors and exceptions satisfactorily
9. Be delivered on schedule within the budget
10
SOFTWARE LIFE CYCLE MODEL
The series of stages depicting the various tasks involved in development process is called
Software Life Cycle Model. The model implemented by us is Waterfall Model, which is most widely
used in procedure-oriented development. This model attempts to break up the identifiable activities into
series of actions, each of which must be completed before the next begins. The activities include
problem definition, requirement analysis, design, coding, testing, maintenance. Further refinements to
this model include iteration back to previous stages in order to incorporate any changes or missing
links.
The phases and the outputs of the waterfall model at each phase are summarized below in tabular
format.
PHASE
OUTPUT
Problem Description Feasibility Report
Analysis SRS
Design Detailed Design Report
Coding Complete Source Code
Testing Test plan, report and manual
Installation Installation Report
11
Problem
Definition
Analysis
Design
Coding
Testing
Maintenance
ITERATIVE WATERFALL MODEL
Software development life cycle process specifies a method of developing the software. Each software
development projects starts with some needs and ends with some software that satisfies those needs. A
software development life cycle specifies the set of activities that should be preformed to go from user
needs to final products. There are different models of SDLC process and each model specifies the
activities and the order in which they should be preformed. Depending on the nature of project, a
suitable model is chosen and the entire process of software requirement analysis, design, coding, testing
and maintenance is preformed accordingly.
Various life cycle models are present, but our system is based on WATER FALL MODEL,
which is most widely used in procedure oriented development. This model attempts to break up the
identifiable activities into series of action, each of which must be completed before the next begins. The
activities include Problem definition, Requirement Analysis, Design, Coding, Testing and maintenance.
An initial investigation culminates in a proposal that determines whether a system is feasible or
not. It determines its workability, impact on the organization, ability to meet user needs, and effective
user resources. The objective of feasibility study is not solve the problem but to acquire a sense of its
scope. During the study, the problem definition is crystallized and aspects of the problem to be included
in the system are determined. Consequently, cost and benefits are estimated with greater accuracy at
this stage. This is a bridge in between the User Requirements and the output that he can avail under a
set of given constraints, inputs and outputs.
The main steps are :
. Statement of constraints
. Identification of specific system objectives
12
. Description of outputs
SOFTWARE REQUIREMENT SPECIFICATION (SRS)
The aim of the system is to develope EMPLOYEE MANAGEMENT SYSTEM software, which
should automate the process to create and store employee details . The system is supposed to be used as
a subsystem in a large office system, which could be manual system or a computerized one. Therefore,
the proposed system must be able to function under both circumstances.
The proposed system is not a freeware and due to the usage of swings, becomes user interactive.
The project demand a page of employee details that include:
Employees personel detail.
Employees salary, allowances, deductions.
13
HARDWARE AND SOFTWARE REQUIREMENTS
Hardware Requirements
MEMORY SPACE:
Minimum - 32 MB
Recommended- - 64 MB
HDD - To install the software at least 2 GB and the data storage is

depending upon the organizational setup.
PROCESSOR - Intel Pentium IV, 1GHZ or above
RAM - 256MB or above
VIDEO - 1024x768, 24-bit colors
KEYBOARD - Standard 104 Keys(QWERTY)
Blank writable CD to keep the backup of the Package.
14
Software Requirements
OPERATING SYSTEM - WindowsXP Professional
DEVELOPING LANGUAGE - JAVA(jdk-5)
DATABASE - MICROSOFT SQL SERVER 2005
15
TOOLS, PLATFORM AND LANGUAGE USED
FRONT END:
The programming has been done using the language Java. It is Sun Microsystems strategic language
for platform independent programming. It is easy to use, efficient and flexible. This language is
preferred because one can build a program using this object oriented and platform independent
programming with less effort than with any other programming language. Its a natural language for
building database applications, owing to the level and sophistication of the tools included with the
language.
BACK END:
Microsoft Sql Server is one of the leading database management systems available on the market today.
It is easy to use and administer, and it comes with tools and wizards that make it easy to develop
applications. The database itself has been redesigned to automatically perform many tuning functions,
leaving you free to focus on most important tasks.
PLATFORM USED:
The Acconts Automation System is targeted at Microsoft Windows platforms.
WINDOWS XP PROFESSIONAL
Windows (Operating System)
a) Window derived from its name from the on-screen WINDOWS that it used to display
informations.
b) Windows XP Professional is a multi-user operating system. It has been designed and

developed by Microsoft Co-operation.
c) When a computer is switch on for working, it needs the operating system because all the
activities of a system are supervised by the operating system.
The features of the operating system are:-
16
1. Provides an interactive environment.
2. Graphical user interfaces.
i. The Commands are displayed on the screen and we dont have to remember all
commands.
ii. GUI makes it easy to work with disks and directories. It can display tree like
diagram of directories, directories sub-0 directories on hard disk.
3. Point and Click.
4. User friendly.
17
LANGUAGE USED JAVA:
Java is a general computer programming language developed by Sun Microsystems. Originally called
"Oak", by its inventor James Gosling, Java was designed with several innovative features. These
include a language that is entirely object oriented, and the ability to write an application once and move
it to virtually any platform.
INNOVATIONS
The benefits of object-oriented programming are not necessarily obvious to non-programmers.

Essentially what this means to managers is that code written in Java will be easier to maintain and
reuse in the long run. The downside is that object-oriented programming requires better planning from
the beginning of a project, and may increase the amount of initial development time a project requires.
For this reason alone, Java is rarely a good choice for small projects requiring a fast turnaround time.
The second innovation that Java provides, platform neutrality, is perhaps the greatest reason for its
wide acceptance. The fact that Java was originally intended a language for writing device controllers
for items such as garage openers and microwave ovens is the key reason for this. In practice, however,
this ability has been more useful in writing enterprise class business applications, where mission critical
software may be required to run on a variety of platforms over its lifetime. Theoretically at least, once
compiled, a Java binary should be able to run on any machine that also has a piece of software called a
Java Virtual Machine. In reality, this is not always the case. However, more often than not Java does
succeed in this regards, whereas this is impossible with an application written in a language such as C+
+.
JAVA IN WEB DEVELOPMENT
In terms of web development, Java is frequently used in two ways. Most commonly Java is used to
write server-side web applications using two t echnologies: JSPs and servlets. Using Java in this
capacity is a good choice for complex applications, that will have large numbers (~1000+) of
concurrent users, and will be developed by a team of programmers. Less complex projects, with fewer
concurrent users may have better outcomes when developed in procedural scripting languages such as
PHP or PERL.
The second way in which Java is used, is to create special, browser embeddable, programs called
Applets. While applets had a brief period of acceptance, their use is becoming increasingly rare, being
replaced by a number of technologies such a Flash and JavaScript, which are more effective at
providing design enhancements such as animation and rollovers. Using applets for these purposes is a
mistake frequently made by beginning developers. Still, Applets do have a place in writing specialized
browser-based applications that cannot be accomplished by these other technologies. Careful
consideration should be made before approving any project that uses Applets.
18
ORIGIN AND GROWTH
Like many recently developed computer languages, Java borrows much of its language design from
C/C++. For that reason, many programmers who are proficient in those languages have leaned Java,
and provide a large pool of qualified developers. Java has gained additional ground as a first language,
as it is generally simpler to master than C++, another commonly used programming language.
CLASSES AND OBJECTS
CLASSES
In the real world, you'll often find many individual objects all of the same kind. There may be
thousands of other bicycles in existence, all of the same make and model. Each bicycle was built from
the same set of blueprints and therefore contains the same components. In object-oriented terms, we say
that your bicycle is an instance of the class of objects known as bicycles. A class is the blueprint from
which individual objects are created.
OBJECTS
Objects are key to understanding object-oriented technology. Look around right now and you'll find
many examples of real-world objects: your dog, your desk, your television set, your bicycle.
Real-world objects share two characteristics: They all have state and behavior. Dogs have state (name,
color, breed, hungry) and behavior (barking, fetching, wagging tail). Bicycles also have state (current
gear, current pedal cadence, current speed) and behavior (changing gear, changing pedal cadence,
applying brakes). Identifying the state and behavior for real-world objects is a great way to begin
thinking in terms of object-oriented programming.
Take a minute right now to observe the real-world objects that are in your immediate area. For each
object that you see, ask yourself two questions: "What possible states can this object be in?" and "What
possible behavior can this object perform?". Make sure to write down your observations. As you do,
you'll notice that real-world objects vary in complexity; your desktop lamp may have only two possible
states (on and off) and two possible behaviors (turn on, turn off), but your desktop radio might have
additional states (on, off, current volume, current station) and behavior (turn on, turn off, increase
volume, decrease volume, seek, scan, and tune). You may also notice that some objects, in turn, will
also contain other objects. These real-world observations all translate into the world of object-oriented
programming.
Software objects are conceptually similar to real-world objects: they too consist of state and related
behavior. An object stores its state in fields (variables in some programming languages) and exposes its
behavior through methods (functions in some programming languages). Methods operate on an object's
internal state and serve as the primary mechanism for object-to-object communication. Hiding internal
19
state and requiring all interaction to be performed through an object's methods is known as data
encapsulation a fundamental principle of object-oriented programming.
By attributing state (current speed, current pedal cadence, and current gear) and providing methods for
changing that state, the object remains in control of how the outside world is allowed to use it. For
example, if the bicycle only has 6 gears, a method to change gears could reject any value that is less
than 1 or greater than 6.
Bundling code into individual software objects provides a number of benefits, including:
1. Modularity: The source code for an object can be written and maintained independently of the
source code for other objects. Once created, an object can be easily passed around inside the
system.
2. Information-hiding: By interacting only with an object's methods, the details of its internal
implementation remain hidden from the outside world.
3. Code re-use: If an object already exists (perhaps written by another software developer), you
can use that object in your program. This allows specialists to implement/test/debug complex,
task-specific objects, which you can then trust to run in your own code.
4. Pluggability and debugging ease: If a particular object turns out to be problematic, you can
simply remove it from your application and plug in a different object as its replacement. This is
analogous to fixing mechanical problems in the real world. If a bolt breaks, you replace it, not
the entire machine.
INHERITANCE
Different kinds of objects often have a certain amount in common with each other. Mountain bikes,
road bikes, and tandem bikes, for example, all share the characteristics of bicycles (current speed,
current pedal cadence, current gear). Yet each also defines additional features that make them different:
tandem bicycles have two seats and two sets of handlebars; road bikes have drop handlebars; some
mountain bikes have an additional chain ring, giving them a lower gear ratio.
Object-oriented programming allows classes to inherit commonly used state and behavior from other
classes. For example, Bicycle becomes the superclass of MountainBike, RoadBike, and TandemBike.
In the Java programming language, each class is allowed to have one direct superclass, and each
superclass has the potential for an unlimited number of subclasses.
INTERFACE
20
As you've already learned, objects define their interaction with the outside world through the methods
that they expose. Methods form the object's interface with the outside world; the buttons on the front of
your television set, for example, are the interface between you and the electrical wiring on the other
side of its plastic casing. You press the "power" button to turn the television on and off.
In its most common form, an interface is a group of related methods with empty bodies. A bicycle's
behavior, if specified as an interface, might appear as follows:
interface Bicycle {
void changeCadence(int newValue);
void changeGear(int newValue);
void speedUp(int increment);
void applyBrakes(int decrement);

}
To implement this interface, the name of your class would change (to ACMEBicycle, for example), and
you'd use the implements keyword in the class declaration:
class ACMEBicycle implements Bicycle {
// remainder of this class implemented as before
Implementing an interface allows a class to become more formal about the behavior it promises to
provide. Interfaces form a contract between the class and the outside world, and this contract is
enforced at build time by the compiler. If your class claims to implement an interface, all methods
defined
by that interface must appear in its source code before the class will successfully compile.
PACKAGE
A package is a namespace that organizes a set of related classes and interfaces. Conceptually you can
think of packages as being similar to different folders on your computer. You might keep HTML pages
in one folder, images in another, and scripts or applications in yet another. Because software written in
the Java programming language can be composed of hundreds or thousands of individual classes, it
makes sense to keep things organized by placing related classes and interfaces into packages.
The Java platform provides an enormous class library (a set of packages) suitable for use in your own
applications. This library is known as the "Application Programming Interface", or "API" for short. Its
packages represent the tasks most commonly associated with general-purpose programming. For
example, a String object contains state and behavior for character strings; a File object allows a
programmer to easily create, delete, inspect, compare, or modify a file on the filesystem; a Socket
21
object allows for the creation and use of network sockets; various GUI objects control buttons and
checkboxes and anything else related to graphical user interfaces. There are literally thousands of
classes to choose from. This allows you, the programmer, to focus on the design of your particular
application, rather than the infrastructure required to make it work.
The Java Platform API Specification contains the complete listing for all packages, interfaces, classes,
fields, and methods supplied by the Java Platform 6, Standard Edition. Load the page in your browser
and bookmark it. As a programmer, it will become your single most important piece of reference
documentation.
GUI SWING WIDGETS
A Graphical User Interface (GUI) is a visual paradigm which allows a user to communicate with a
program in an intuitive way. Its main features are widgets (aka controls) and event driven activities.
Clients expect a graphical interface in an application.
Java has two GUI packages, the original Abstract Windows Toolkit (AWT) and the newer Swing. AWT
uses the native operating system's window routines and therefore the visual effect is dependent on the
run-time system platform. But this is contrary to the concept of having a virtual model. Swing allows
three modes: a unified 'Java' look and feel [the default], the native platform look, or a specific
platform's look. Swing is built on the original objects and framework of AWT. Swing components have
the prefix J to distinguish them from the original AWT ones (eg JFrame instead of Frame). To include
Swing components and methods in your project you must import the java.awt.*, java.awt.event.*, and
javax.swing.* packages.
CONTAINERS, FRAMES AND CONTENT PANES

Containers are widgets (GUI controls) that are used to hold and group other widgets such as text fields
and checkboxes. Displayable frames are top-level containers such as JFrame, JWindow, JDialog,
JApplet and JInternalFrame which interface to the operating system's window manager. Non-displaying
content panes are intermediate containers such as JPanel, JOptionPane, JScrollPane, JLayeredPane,
JSplitPane and JTabbedPane which organize the layout structure when multiple controls are being used.
JWindow is an unadorned container that has been superceded for the most part by JDialog. However it
does provide a useful container for a splash screen.
COMMON WIDGET METHODS
Several methods can be used with many different controls. These include: add(), requestFocus(),
setToolTipText().
22
JFRAME AND JPANEL
JFrame is the most commonly used top-level container. It adds basic functionality such as minimize,
maximize, close, title and border to basic frames and windows. Some important JFrame methods are:
setBounds(x,y,w,h), setLocation(x,y), setSize(w,h), setResizable(bool), setTitle(str), setVisible(bool),
isResizable() and getTitle(). The setDefaultCloseOperation(constant) method controls the action that
occurs when the close icon is clicked. Normally the constant used is JFrame.EXIT_ON_CLOSE.
JPanel is the most commonly used content pane. An instance of the pane is created and then added to a
frame. The add() method allows widgets (GUI components) to be added to the pane. The way they are
added is controlled by the current layout manager.
LABELS, ICONS AND BUTTONS
Labels are non-interactive text objects most commonly used as prompts. They are created using the
JLabel() constructor with the required text as the first parameter. Another parameter can be added using
a SwingConstant value to set horizontal alignment. Vertical alignment is through the
setVerticalAlignment() method. The contents of a label can be changed with the setText() method.
Icons can be easily added to labels or other controls either to brand, dress up, or aid accessibility. Icons
are constructed from the ImageIcon class and then added as a parameter to the label (or other) control.
An extra parameter can be used to control the position of the text relative to the icon. It must use one of
the SwingConstants values.
Simple buttons are used to start operations. They are created with the JButton() constructor. They can
be deactivated with the setEnabled(false) method and tested with the isEnabled() method. One useful
button method is setMnemonic(char) which allows a hot key to be associated with the button
Simple buttons require an ActionEvent event listener that reacts to the button click.
Toggle buttons are a visual push on - push off mechanism. They are created with the JToggleButton()
constructor. The isSelected() method returns the state of the button. And in addition to ActionEvent, the
ChangeEvent is triggered.
EVENT LISTENERS
GUIs are event-based. That is they respond to buttons, keyboard input or mouse activities. Java uses
event listeners to monitor activity on specified objects and react to specific conditions. For a listing of
useful event listeners check the appendix. For techniques on organizing many different events in larger
projects, view advanced event listeners.
The first step in adding a basic button push event handler to the above example is to import
awt.event.* which contains all of the event classes. Next add the phrase implements ActionListener to
the class header. Register event listeners for each button widget using the addActionListener(this)
method.
23
24
SYSTEM DESIGN
Process Diagram
LOGIN
SCREEN
MENU
SCREEN
ADD EMPLOYEE VIEW GENERATE EXIT

EMPLOYEE LIST DETAILS SLIP
Nam Addre Post Experi Edit DELET BACK

e ss ence E
OK
Salary House Travellin
g
Allowan
I. Tax
25
DATA FLOW DIAGRAMS
LEVEL 0 DFD:
AddEmp Operator EmpDetail Operator
Emp info Emp detail Modification

Entry
Administrator
EMS EmpSlip
For login user, password Emp Payroll Slip Generation
Emp detail report

Generation
EmpList Exit
26
LEVEL 1 DFD:
27
ENTITY RELATIONSHIP DIAGRAM:
28
FORMS LAYOUT
Package employeeManagement
Class Summary
AddEmp This class provides code for Addition of Employee to the Firm
EmpDetail Provides code to view Employee Details and also to Delete/Modify Accounts
EmpList Provides the code to show the List of employees in the Firm
EmpSlip Provides codes for Salary Slip Generation
Intro Contains code for Welcome/Login Page of the project
Main The Base class which has the code to show the First/Login Screen
This class has code which represents the Screen which shows the Buttons for Selection
Menuscrn
of Different Tasks
29
Intro.java
Contains code for username /Password Authentication. When user enters correct login and password It
opens Main form otherwise it gives an error message. You can exit by clicking the X button on the
right top corner of the window.
Press submit button to submit your request and reset to reset the fields.
30
MenuScrn.java
Using Add employee you can add employee to the firm. Clicking on it opens the add employee
window. It calls the AddEmp Class.
Clicking on Employee List shows the list of employees in the firm. It calls the EmpList Class.
By Clicking on View details you can View/Modify/Delete Records of the employees. It calls
EmpDetail.java.
By clicking on generate slip Salary slip is generated. It calls EmpSlip.java
On clicking Exit The Application exits.
Note: You cannot exit using X button in this window.
31
AddEmp.java
Clicking Back takes you back to main menu screen
Clicking Submit submits the records.
Clicking Clear Clears the Fields
32
EmpList.java
Shows the list of employees. On clicking Back takes you back to the Main Menu screen
33
EmpDetail.java
To be able to edit records you must press Edit. Before that please select a record and press OK. This
will enable the Edit and Delete Buttons. As Shown below
34
Clicking on Edit will change it to save after making changes Please click on save to save the changes.
Clicking on Delete will change it Save Please press Save to Confirm the deletion. As shown Below
35
Press save to confirm Deletion
Select another EmpId and press OK to select
Press Back to go back
36
EmpSlip.Java
Press OK to generate slip for selected ID
Print Function is Currently Disabled and is left for Future scope

Press Back to Go Back.
37
CODING
/*
AddEmp.java
*/
package employeemanagement;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import java.util.logging.Level;
import java.util.logging.Logger;
public class AddEmp extends javax.swing.JFrame {
Connection con;
Statement stmt;
PreparedStatement stat;
ResultSet rs;
static int eid=0;
/** Creates new form AddEmp */
public AddEmp() throws ClassNotFoundException, SQLException {
initComponents();
this.setVisible(true);
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con=DriverManager.getConnection("jdbc:odbc:Employee");
stmt=con.createStatement();
stmt=con.createStatement(rs.TYPE_SCROLL_SENSITIVE,rs.CONCUR_READ_ONLY);
rs=stmt.executeQuery("select * from emp");
rs.last();
eid=rs.getInt(10);
}
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated Code">
private void initComponents() {
label1 = new java.awt.Label();

textField1 = new java.awt.TextField();
38
button1 = new java.awt.Button();
setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);
label1.setText("NAME");
label2.setText("ADDRESS");
label3.setText("SALARY");
label4.setText("POST");
label5.setText("EXPERIANCE");
label6.setText("Allowences");
label7.setText("HOUSE");
label8.setText("TRAVELLING");
label9.setText("Deductions");
label10.setText("PROVIDENT FUND");
label11.setText("INCOME TAX");
button1.setLabel("SUBMIT");
button1.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
button1ActionPerformed(evt);
}
});
button2.setLabel("CLEAR");
button3.setLabel("BACK");
}
});
javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());

getContentPane().setLayout(layout);
layout.setHorizontalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(layout.createSequentialGroup()
.addGroup(layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGap(46, 46, 46)
.addComponent(label1, javax.swing.GroupLayout.PREFERRED_SIZE, 116,
javax.swing.GroupLayout.PREFERRED_SIZE)
.addComponent(label5, javax.swing.GroupLayout.PREFERRED_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.PREFERRED_SIZE))
39
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED)
.addComponent(textField1, javax.swing.GroupLayout.DEFAULT_SIZE, 258, Short.MAX_VALUE)
.addComponent(button1, javax.swing.GroupLayout.PREFERRED_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED, 24, Short.MAX_VALUE)
.addComponent(button3, javax.swing.GroupLayout.PREFERRED_SIZE, 77,
.addGap(23, 23, 23)
.addGap(18, 18, 18))))
.addContainerGap()
.addGap(43, 43, 43)
javax.swing.GroupLayout.PREFERRED_SIZE)))
.addContainerGap()
.addGap(45, 45, 45)
javax.swing.GroupLayout.PREFERRED_SIZE))))
.addContainerGap(71, Short.MAX_VALUE))
);
layout.setVerticalGroup(
.addGap(20, 20, 20)
.addGroup(layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING, false)
40
.addComponent(textField1, javax.swing.GroupLayout.PREFERRED_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED, javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE)
.addGroup(layout.createParallelGroup(javax.swing.GroupLayout.Alignment.TRAILING)
.addGap(2, 2, 2)
.addComponent(label8, javax.swing.GroupLayout.PREFERRED_SIZE, 20, javax.swing.GroupLayout.PREFERRED_SIZE)
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED, javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE)
41
.addGap(34, 34, 34)
.addGap(19, 19, 19)
);
pack();
}// </editor-fold>
private void button1ActionPerformed(java.awt.event.ActionEvent evt) {

try {
try {
// TODO add your handling code here:
stat = con.prepareStatement("Insert into Emp values(?,?,?,?,?,?,?,?,?,?)");
} catch (SQLException ex) {
Logger.getLogger(AddEmp.class.getName()).log(Level.SEVERE, null, ex);
}
String name = textField1.getText();
String address = textField2.getText();
String post = textField13.getText();
String experiance = textField8.getText();
String salary = textField14.getText();
String house = textField9.getText();
String travelling = textField10.getText();
String pf = textField11.getText();
String it = textField12.getText();
stat.setString(1, name);
stat.setString(2, address);
stat.setString(3, post);
stat.setInt(4,Integer.parseInt(experiance));
stat.setInt(5,Integer.parseInt(salary));
stat.setInt(6,Integer.parseInt(house));
stat.setInt(7,Integer.parseInt(travelling));
stat.setInt(8,Integer.parseInt(pf));
stat.setInt(9,Integer.parseInt(it));
stat.setInt(10,++eid);
label12.setText("Success");
stat.executeUpdate();
con.close();
this.setVisible(false);
Menuscrn menu = new Menuscrn();
42
menu.setVisible(true);
}

}
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
try {
new AddEmp().setVisible(true);
} catch (ClassNotFoundException ex) {
}
}
});
}
// Variables declaration - do not modify

private java.awt.Button button1;
private java.awt.Label label1;
private java.awt.TextField textField1;
// End of variables declaration }
/*
* Intro.java
43
*/
public class Intro extends javax.swing.JFrame {
/** Creates new form Intro */

public Intro() {
initComponents();
textField2.setEchoChar('*');
}
/** 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.
*/

setBackground(new java.awt.Color(51, 0, 51));
label1.setBackground(new java.awt.Color(0, 153, 0));

label1.setFont(new java.awt.Font("Arial", 3, 18)); // NOI18N
label1.setText("WELCOME TO EMPLOYEE MANAGEMENT SYSTEM");
label2.setText("User Name");
label3.setText("Password");
button1.setLabel("Submit");
}
});
button2.setLabel("Reset");

44
.addGroup(javax.swing.GroupLayout.Alignment.TRAILING, layout.createSequentialGroup()
.addGap(96, 96, 96)
.addComponent(label1, javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE)
.addGap(67, 67, 67))
.addGap(161, 161, 161)
.addGap(38, 38, 38)
.addComponent(textField1, javax.swing.GroupLayout.DEFAULT_SIZE, 166, Short.MAX_VALUE))
.addGap(178, 178, 178))
.addGap(206, 206, 206)
.addGap(66, 66, 66)
.addContainerGap(62, Short.MAX_VALUE)
.addGap(38, 38, 38))
);
.addContainerGap()
.addGap(41, 41, 41)
.addComponent(textField1, javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE)
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED))
.addGap(39, 39, 39)
45
.addGap(22, 22, 22)
.addContainerGap())
);
pack();
}// </editor-fold>

if((textField1.getText().equals("Admin"))&&(textField2.getText().equals("adminadmin")))
{
label4.setText("");
}
else
label4.setText("Wrong Password/Username");
}
/**
* @param args the command line arguments
*/
java.awt.EventQueue.invokeLater(new RunnableImpl());
}

// End of variables declaration
private static class RunnableImpl implements Runnable {
public RunnableImpl() {
}
public void run() {

new Intro().setVisible(true);
/*
* Menuscrn.java
*/
46
public class Menuscrn extends javax.swing.JFrame {

Connection con;
Statement stmt;
ResultSet rs;
/** Creates new form Menuscrn */

public Menuscrn() {
try {
initComponents();
this.setDefaultCloseOperation(DO_NOTHING_ON_CLOSE);
con = DriverManager.getConnection("jdbc:odbc:Employee");
rs=stmt.executeQuery("select * from Emp" );
if(ex.getErrorCode()==208)
{
try {
rs = stmt.executeQuery("CREATE TABLE [dbo].[Emp]([Name] [char](20) NOT NULL,[Address] [char](30) NOT NULL,[Post]
[char](10) NOT NULL,[Experiance] [int] NULL,[Salary] [int] NOT NULL,[HRA] [int] NULL,[TA] [int] NULL,[PF] [int] NULL,[ITax] [int] NULL,
[Eid] [int] NOT NULL) ON [PRIMARY]");
} catch (SQLException ex1) {
Logger.getLogger(Menuscrn.class.getName()).log(Level.SEVERE, null, ex1);
}
}
Logger.getLogger(Menuscrn.class.getName()).log(Level.SEVERE, null, ex);
}
}

*/

47
addWindowListener(new java.awt.event.WindowAdapter() {
public void windowClosed(java.awt.event.WindowEvent evt) {
formWindowClosed(evt);
}
public void windowClosing(java.awt.event.WindowEvent evt) {
formWindowClosing(evt);
}
});
button5.setLabel("GENERATE SLIP");
}
});
button6.setLabel("EXIT");
}
});
button3.setLabel("VIEW DETAILS");
}
});
button1.setLabel("EMPLOYEE LIST");
}
});
button2.setLabel("ADD EMPLOYEE");
}
});

.addComponent(button2, javax.swing.GroupLayout.DEFAULT_SIZE, 224, Short.MAX_VALUE)
.addComponent(button3, javax.swing.GroupLayout.Alignment.TRAILING, javax.swing.GroupLayout.DEFAULT_SIZE, 224,
Short.MAX_VALUE)
);
48
.addComponent(button2, javax.swing.GroupLayout.PREFERRED_SIZE, 46, javax.swing.GroupLayout.PREFERRED_SIZE)
.addGap(1, 1, 1)
.addGap(1, 1, 1)
.addGap(2, 2, 2)
.addGap(2, 2, 2)
.addComponent(button6, javax.swing.GroupLayout.PREFERRED_SIZE, 46, javax.swing.GroupLayout.PREFERRED_SIZE))
);
pack();
}// </editor-fold>

EmpSlip emp = new EmpSlip();
}

try {
AddEmp emp = new AddEmp();
}
}

try {
EmpList emp = new EmpList();
}
}

try {
EmpDetail emp = new EmpDetail();
}
49
}

System.exit(0);
}
private void formWindowClosed(java.awt.event.WindowEvent evt) {

private void formWindowClosing(java.awt.event.WindowEvent evt) {

/**
*/
public void run() {
new Menuscrn().setVisible(true);
}
});
}

50
/*
* EmpList.java
*/
public class EmpList extends javax.swing.JFrame {
Connection con;
Statement stmt;
ResultSet rs;
/** Creates new form EmpList */
public EmpList() throws ClassNotFoundException, SQLException {
initComponents();
textArea1.setEditable(false);
rs=stmt.executeQuery("Select * from emp");
textArea1.append("Name\t\tAddress\t\t\tPost\t\tEMPID\n");
while(rs.next())
{
textArea1.append(rs.getString(1)+"\t");
textArea1.append(Integer.toString(rs.getInt(10))+"\t");
textArea1.append("\n");
}
}

*/
menuBar1 = new java.awt.MenuBar();

menu1 = new java.awt.Menu();
textArea1 = new java.awt.TextArea();
menu1.setLabel("Menu");
menuBar1.add(menu1);
51
button1.setLabel("Back");
}
});

.addComponent(textArea1, javax.swing.GroupLayout.DEFAULT_SIZE, 723, Short.MAX_VALUE)
.addContainerGap(328, Short.MAX_VALUE)
.addGap(300, 300, 300))
);
.addComponent(textArea1, javax.swing.GroupLayout.PREFERRED_SIZE, 439, javax.swing.GroupLayout.PREFERRED_SIZE)
.addContainerGap())
);
pack();
}// </editor-fold>

}
/**
*/
public void run() {
try {
new EmpList().setVisible(true);
Logger.getLogger(EmpList.class.getName()).log(Level.SEVERE, null, ex);
Logger.getLogger(EmpList.class.getName()).log(Level.SEVERE, null, ex);
}
}
});
}
52
private java.awt.Menu menu1;
private java.awt.MenuBar menuBar1;
private java.awt.TextArea textArea1;
53
/*
* EmpDetail.java
*/
public class EmpDetail extends javax.swing.JFrame {

Connection con;
Statement stmt;
ResultSet rs;
int i=0;
//int selected_id;
/** Creates new form EmpDetail */
public EmpDetail() throws ClassNotFoundException, SQLException {
initComponents();
textField1.setEditable(false);
button1.setEnabled(false);
rs=stmt.executeQuery("Select * from emp");
while(rs.next())
{
choice1.insert(Integer.toString(rs.getInt(10)), i);
}

*/
54
choice1 = new java.awt.Choice();
label1.setText("NAME");
label5.setText("EXPERIANCE");
label2.setText("ADDRESS");
label4.setText("POST");
label3.setText("SALARY");
button1.setLabel("EDIT");
}
});
label6.setText("Allowences");
label7.setText("HOUSE");
label8.setText("TRAVELLING");
label9.setText("Deductions");
label11.setText("INCOME TAX");
55
label10.setText("PROVIDENT FUND");
button2.setLabel("DELETE");
}
});
}
});
label13.setText("EMPID");
button4.setLabel("OK");
}
});

.addGap(46, 46, 46)
.addGap(83, 83, 83)
.addComponent(button1, javax.swing.GroupLayout.DEFAULT_SIZE, 83, Short.MAX_VALUE)))
56
Short.MAX_VALUE)
.addComponent(textField13, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)
Short.MAX_VALUE)
Short.MAX_VALUE)
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)))
.addGap(45, 45, 45)
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED,
javax.swing.GroupLayout.PREFERRED_SIZE))))
.addContainerGap()
.addGap(43, 43, 43)
.addContainerGap()
.addGap(45, 45, 45)
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED, 279, Short.MAX_VALUE)))
.addGap(18, 18, 18)
.addGap(22, 22, 22)
.addComponent(choice1, javax.swing.GroupLayout.PREFERRED_SIZE, 70,
57
.addGap(36, 36, 36)
.addContainerGap())
.addGap(69, 69, 69)
.addComponent(label12, javax.swing.GroupLayout.DEFAULT_SIZE, 244, Short.MAX_VALUE)
.addGap(282, 282, 282))
);
.addGap(20, 20, 20)
.addComponent(textField1, javax.swing.GroupLayout.PREFERRED_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.PREFERRED_SIZE)
javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.PREFERRED_SIZE)))
.addGap(2, 2, 2)
58
.addComponent(choice1, javax.swing.GroupLayout.PREFERRED_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
.addGap(83, 83, 83)
.addContainerGap(javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE))
);
pack();
}// </editor-fold>

textField1.setEditable(true);
59
button1.setLabel("SAVE");
//evt.setSource("NULL");
int selected_id =Integer.parseInt(label12.getText());
if(evt.getActionCommand().equals("SAVE"))
{
try {
stat=con.prepareStatement("UPDATE Emp SET Name = ?,Address = ?,Post = ?,Experiance = ?,Salary = ?,HRA = ?,TA = ?,PF
= ?,ITax = ? WHERE Eid="+ selected_id);
stat.setString(1,textField1.getText());
stat.setString(2, textField2.getText());
stat.setString(3, textField13.getText());
stat.setInt(4,Integer.parseInt(textField8.getText()));
label12.setText("SAVED");
Logger.getLogger(EmpDetail.class.getName()).log(Level.SEVERE, null, ex);
}
}

try {
label12.setText(choice1.getSelectedItem().toString());
int selected_id =Integer.parseInt(label12.getText());
try {
stmt = con.createStatement();
}
try {
rs = stmt.executeQuery("Select * from emp WHERE Eid="+ selected_id);
}
while(rs.next())
{
textField1.setText(rs.getString(1));
textField8.setText(Integer.toString(rs.getInt(4)));
60
}
button1.setEnabled(true);
}catch (SQLException ex) {
}
}

try {
con.close();
}
}
try {
button2.setLabel("SAVE");
int selected_id = Integer.parseInt(label12.getText());
stat = con.prepareStatement("DELETE from Emp WHERE Eid = ?");
stat.setInt(1, selected_id);
if (evt.getActionCommand().equals("SAVE")) {
label12.setText("CHANGES SAVED");
}
}
}
/**
*/
public void run() {
try {
new EmpDetail().setVisible(true);
}
}
});
}
61
private java.awt.Choice choice1;
62
/*
* EmpSlip.java
*/
import java.awt.HeadlessException;
import java.awt.print.PageFormat;
import java.awt.print.Pageable;
import java.awt.print.Printable;
import java.awt.print.PrinterException;
import java.awt.print.PrinterJob;
import java.text.SimpleDateFormat;
import java.util.Calendar;
import java.util.Date;
public class EmpSlip extends javax.swing.JFrame {
Connection con;
Statement stmt;
ResultSet rs;
int i=0;
/** Creates new form EmpSlip */
public EmpSlip() {
try {
initComponents();
Calendar cal=Calendar.getInstance();
Date now=new Date();
now=cal.getTime();
SimpleDateFormat formatter=new SimpleDateFormat();
// System.out.println(now);
label18.setText(formatter.format(now));
con = DriverManager.getConnection("jdbc:odbc:Employee");
stmt = con.createStatement(rs.TYPE_SCROLL_SENSITIVE,rs.CONCUR_READ_ONLY);
rs = stmt.executeQuery("Select * from emp");
while (rs.next()) {
choice1.insert(Integer.toString(rs.getInt(10)),++i);
}
Logger.getLogger(EmpSlip.class.getName()).log(Level.SEVERE, null, ex);
}
}
63
*/

choice1 = new java.awt.Choice();
setBackground(new java.awt.Color(255, 255, 255));

label1.setForeground(new java.awt.Color(255, 255, 255));
label1.setText("COMPUTER GENRATED PAYSLIP");

button1.setLabel("OK");
}
});
button2.setLabel("PRINT");
}
});
64
label3.setText("EMP ID");
label4.setText("BASIC PAY");
label5.setText("+ HOUSE ALLOWANCE");
label7.setText("+ TRAVELLING ALLOWANCE");

label9.setText("- PROVIDENT FUND");
label10.setText("- INCOME TAX");
label16.setText("NET PAY");
label17.setText("------------------------------------------------------------------------------------");
}
});

.addContainerGap()
.addGap(19, 19, 19)
.addContainerGap()
.addContainerGap()
.addGroup(layout.createParallelGroup(javax.swing.GroupLayout.Alignment.TRAILING, false)
.addComponent(label9, javax.swing.GroupLayout.Alignment.LEADING, javax.swing.GroupLayout.DEFAULT_SIZE,
.addComponent(label10, javax.swing.GroupLayout.Alignment.LEADING,
javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE))))
65
.addGroup(layout.createParallelGroup(javax.swing.GroupLayout.Alignment.TRAILING, false)
99, Short.MAX_VALUE)
.addComponent(label8, javax.swing.GroupLayout.Alignment.LEADING,
javax.swing.GroupLayout.PREFERRED_SIZE, 157, javax.swing.GroupLayout.PREFERRED_SIZE))))
.addContainerGap()
.addGap(53, 53, 53)
.addGap(56, 56, 56)
.addGap(27, 27, 27)
javax.swing.GroupLayout.PREFERRED_SIZE)))))
.addContainerGap(javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE))
.addContainerGap()
.addComponent(choice1, javax.swing.GroupLayout.PREFERRED_SIZE, 64, javax.swing.GroupLayout.PREFERRED_SIZE)
.addGap(109, 109, 109)
.addGap(23, 23, 23))
);
.addContainerGap()
.addComponent(label3, javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE)
66
.addComponent(choice1, javax.swing.GroupLayout.Alignment.TRAILING, javax.swing.GroupLayout.DEFAULT_SIZE,
.addGap(1, 1, 1)
.addGap(1, 1, 1)
.addGap(10, 10, 10)
.addGap(67, 67, 67)
67
.addComponent(button1, javax.swing.GroupLayout.Alignment.LEADING, javax.swing.GroupLayout.DEFAULT_SIZE,
38, Short.MAX_VALUE)
.addComponent(button2, javax.swing.GroupLayout.Alignment.LEADING, javax.swing.GroupLayout.DEFAULT_SIZE,
38, Short.MAX_VALUE)))
);
pack();
}// </editor-fold>

try {
int selected_id = Integer.parseInt(choice1.getSelectedItem().toString());
stmt = con.createStatement(rs.TYPE_SCROLL_SENSITIVE,rs.CONCUR_READ_ONLY);
rs = stmt.executeQuery("Select * from emp WHERE Eid=" + selected_id);
while (rs.next()) {
label2.setText(rs.getString(1).trim()+","+rs.getString(2).trim());
label8.setText("POSITION: "+rs.getString(3));
label11.setText(Integer.toString(rs.getInt(5)));
rs.first();
double npay=rs.getInt(5)+rs.getInt(6)+rs.getInt(7)-rs.getInt(8)-rs.getInt(9);
label6.setText(Double.toString(npay));
}
}
}

final PrinterJob prn=new PrinterJob() {
@Override
public void setPrintable(Printable painter) {
throw new UnsupportedOperationException("Not supported yet.");
}
@Override
public void setPrintable(Printable painter, PageFormat format) {
}
@Override
public void setPageable(Pageable document) throws NullPointerException {
}
@Override
68
public boolean printDialog() throws HeadlessException {
}
@Override
public PageFormat pageDialog(PageFormat page) throws HeadlessException {
}
@Override
public PageFormat defaultPage(PageFormat page) {
}
@Override
public PageFormat validatePage(PageFormat page) {
}
@Override
public void print() throws PrinterException {
}
@Override
public void setCopies(int copies) {
}
@Override
public int getCopies() {
}
@Override
public String getUserName() {
}
@Override
public void setJobName(String jobName) {
}
@Override
public String getJobName() {
}
@Override
public void cancel() {
}
@Override
public boolean isCancelled() {
69
}
};
}

try {
con.close();
}
}
/**
*/
public void run() {
new EmpSlip().setVisible(true);
}
});
}

private java.awt.Choice choice1;
// End of variables declaration )
/*
*Main.java
* To change this template, choose Tools | Templates
* and open the template in the editor.
70
*/
public class Main {
/**
*/
public static void main(String[] args) {
// TODO code application logic here
Intro intr = new Intro();
}
71
SYSTEM TESTING
During systems testing, the system is used experimentally to ensure that the software does not fail. In
other words, we can say that it will run according to its specifications and in the way users expect.
Special test data are input for processing, and the results examined. A limited number of users may be
allowed to use the system so that analyst can see whether they try to use it in unforeseen ways. It is
desirable to discover any surprises before the organization implements the system and depends on it.
Software modules are tested for their functionality as per the requirements identified during the
requirements analysis phase. To test the functionality of the file transfer and chat application, a Quality
Assurance (QA) team is formed. The requirements identified during the requirements analysis phase
are submitted to the QA team. In this phase the QA team tests the application for these requirements.
The development team submits a test case report to the QA team so that the application can be tested in
the various possible scenarios.
The software development project, errors can be injected at any stage during development i.e. if there is
an error injected in the design phase then it can be detected in the coding phase because there is
the product to be executed ultimately on the machine, so we employ a testing process.
During the testing the program to be tested is executed with certain test cases and output of these test
cases is evaluated to check the correctness of the program. It is the testing that performs first step in
determining the errors in the program.
TEST CASES AND TEST CRITERIA
During Test Cases that are good at revealing the presence of faults is central to successful testing. The
reason for this is that if there is a fault in the program, the program can still provide the expected
behavior on the certain inputs. Only for the set of inputs the faults that exercise the fault in the program
will the output of the program devise from the expected behavior. Hence, it is fair to say that testing is
as good as its test case.
The number of test cases used to determine errors in the program should be minimum. There are two
fundamental goals of a practical testing activity:-
maximize the number of errors detected and.
minimize the number of test cases.
As these two goals are contradictory so the problem of selecting test cases is a complex one. While
selecting the test cases the primary objective is to ensure that if there is an error or fault in the program,
it is exercised by one of its test cases. An ideal test case is one which succeeds (meaning that there are
no errors, revealed in its execution) only it there are no errors in the program one possible set of ideal
test cases is one which includes all the possible inputs to the program. This is often called "exhaustive
testing", however it is impractical and infeasible as even a small program can have an infinite input
domain.
72
So to avoid this problem we use "test criteria" in selection of the test cases. There are two aspects of the
test case selection:-
specifying a criteria for evaluating the test cases

generating the set of cases that satisfy a given criteria.
The fully automated process of generating test criteria has not been yet found rather guidelines are only
the automated tool available to us previously. The two fundamental properties for a testing criterion
are:-
Reliability: a criterion is reliable if all the sets that satisfy the criteria detect the same error. .
Validity: a criterion is valid if for any error in the program there is some set satisfying the
criteria that will reveal the error.
The fundamental theorem of testing is that if a testing criterion is valid and reliable, if a set satisfying
criteria succeeds then the program contains no errors.
APPROACHES TO TESTING
There are two fundamental approaches to testing they are:
Functional Testing/Black Box Testing:
In functional testing the structure of the program is not considered. Test cases are solely determined on
the basis of requirement or specification of the program or module. Internals of the modules and the
programs are not considered for selection of test cases. Due to this nature it is also called "black box
testing".
The most obvious functional testing procedure is "exhaustive testing", which is impractical.
The other criteria for generating the test case are to generate them "randomly" this strategy has a little
chance of resulting in a test case that is close to optimal.
There is no appropriate criterion for developing the test case so we have certain heuristic approaches-:
a) Equivalence Class Partitioning: in which the domain of all inputs is divided into a set of
equivalence classes, so that if any test in that class succeeds, then every test in that class will succeed
i.e. the success of one set element implies the success of the other.
b) Boundary Value Analysis: It has been observed that programs work correctly for a set of values in
an equivalence class fail on certain values. These values generally lie on the boundary of equivalence
class. So in the boundary value analysis we chose an input for a test case from an equivalence class,
such that input lies on the edge of equivalence class. Boundary value test cases are also called "extreme
cases".
c) Cause-Effect Graphing: The problem with the prior approaches is that they consider each input
separately i.e. both concentrate on classes and conditions of one input. The combination of inputs is not
73
considered which is used in many cases. One way to exercise the combination of various input
conditions is to consider all the valid combinations of the equivalence class of the input conditions. The
technique starts with identifying the causes and the effect of system under testing.
STRUCTURAL TESTING:
In the structural approach the test cases are generated an the basis of the actual code of the program or
the module to be tested, This structural approach is sometimes called "glass box testing", This testing is
concerned with the implementation of the program. The content is not to exercise the various input
conditions rather different programming structures and data structures used in the program.
There are three different approaches to structural testing they are- :
a) Control flow based criteria:
Most common structure based criteria use control flow based testing in which the control flow graph of
the program is considered and coverage of various aspects of graph are specified as criteria. The
various control flow based strategies are
statement coverage,
branch coverage and
all path coverage
b) Data Flow based testing:
The basic idea behind the data flow based testing is to make sure that during testing, the definitions of
variables and their subsequent use is tested. To implement the data flow based testing the data flow
graph is first made from the control flow graph.
c) Mutation Testing:
In the above two testing techniques the focus is on which path to be executed, but mutation testing is
not a path-based approach. The mutation testing requires that the set of test cases must be such that they
can distinguish between the original programs and is mutants. In software world there is no fault model
as in hardware so most of the techniques do guess work regarding where the fault must lie and then
select the test cases to reveal those faults. In Mutation testing faults of some pre-decided types are
introduced in the program being tested. Then those faults are found in the mutants.
Implementation, Evaluation And Testing
74
Implementation is the process of having systems personnel check out and put new equipment into use,
train users, install the new application and construct any files of data needed to use it. This phase is less
creative than system design. Depending on the size of the organization that will be involved in using
the application and the risk involved in its use, systems developers may choose to test the operation in
only one area of the firm with only one or two persons. Sometimes, they will run both old and new
system in parallel way to compare the results. In still other situations, system developers stop using the
old system one day and start using the new one the next.
Evaluation of the system is performed to identify its strengths and weaknesses. The actual evaluation
can occur along any of the following dimensions:
1. Operational Evaluation: Assessment of the manner in which the system functions, including
case of use, response time, overall reliability and level of utilization.
2. Organizational Impact: Identification and measurement of benefits to the organization in such
areas as financial concerns, operational efficiency and competitive impact.
3. User Manager Assessment: Evaluation of the attitudes of senior and user manager within the
organization, as well as end-users.
4. Development Performance: Evaluation of the development process in accordance with such
yardsticks as overall development time and effort, conformance to budgets and standards and
other project management criteria.
Maintenance is necessary to eliminate errors in the working system during its working life and to tune
the system to any variations in its working environment often small system deficiencies are found as a
system is brought into operations and changes are made to remove them. System planners must always
plan for resource availability to carry out these maintenance functions. The importance of maintenance
is to continue to bring the new system to standards.
75
CONCLUSION
Since this project has been designed exclusively as a project, certain complexities that do faced by any
real life manual problem like total no. of employee, address redundancy etc. are considered in this
project. But enhancement to the project can easily be made without changing the current design and
programming structure.
76
BIBLIOGRAPHY
1. CORE JAVA(Vol-I) by SUN MICROSYSTEMS
2. WWW.GOOGLE.COM
3. WWW.JAVA.SUN.COM
4. WWW.ONLY4GURUS.COM
5. WWW.SMARTDRAW.COM
6. HEAD FIRST BY KATHY SIERRA & BERT BATES
77

Employee Management System Report

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Employee Management System Report

Încărcat de

Drepturi de autor:

Formate disponibile

PROJECT REPORT

BLS INSTITUTE OF TECHNOLOGY

SUBMITTED TO: ASHWANI SANGWAN

Submitted by: MANAS SARKAR

NAME OF THE STUDENT : SANJIT SHARMA

ENROLLMENT NO. : 30320502014

TITLE : EMPLOYMENT MANAGEMENT SYSTEM

This is to certify that the project entitled EMPLOYMENT

PROJECT GUIDE BY:

MR. ASWANI SANGWAN

I would also like to thank my class mates who helped me directly or

Finally I would also like to thank other faculty members who

Employee Management System is a distributed application, developed to maintain the details of

EMS Employee Management System

GUI- Graphical User Interface

Jdk Java Development Kit

SRS- Software Requirement Analysis

2.OBJECTIVES AND SCOPE

8. IMPLEMENTATION, EVALUATION AND MAINTENANCE

Thus java was chosen as background to design this application.

Design Detailed Design Report

Coding Complete Source Code

Testing Test plan, report and manual

Installation Installation Report

ITERATIVE WATERFALL MODEL

SOFTWARE REQUIREMENT SPECIFICATION (SRS)

HDD - To install the software at least 2 GB and the data storage is

PROCESSOR - Intel Pentium IV, 1GHZ or above

RAM - 256MB or above

VIDEO - 1024x768, 24-bit colors

KEYBOARD - Standard 104 Keys(QWERTY)

Blank writable CD to keep the backup of the Package.

OPERATING SYSTEM - WindowsXP Professional

DEVELOPING LANGUAGE - JAVA(jdk-5)

DATABASE - MICROSOFT SQL SERVER 2005

The Acconts Automation System is targeted at Microsoft Windows platforms.

Windows (Operating System)

b) Windows XP Professional is a multi-user operating system. It has been designed and

The features of the operating system are:-

2. Graphical user interfaces.

3. Point and Click.

The benefits of object-oriented programming are not necessarily obvious to non-programmers.

JAVA IN WEB DEVELOPMENT

CLASSES AND OBJECTS

void changeGear(int newValue);

void speedUp(int increment);

void applyBrakes(int decrement);

class ACMEBicycle implements Bicycle {

// remainder of this class implemented as before

GUI SWING WIDGETS

CONTAINERS, FRAMES AND CONTENT PANES

COMMON WIDGET METHODS

LABELS, ICONS AND BUTTONS

ADD EMPLOYEE VIEW GENERATE EXIT

Nam Addre Post Experi Edit DELET BACK

AddEmp Operator EmpDetail Operator

Emp info Emp detail Modification

Emp detail report

By clicking on generate slip Salary slip is generated. It calls EmpSlip.java

On clicking Exit The Application exits.

Note: You cannot exit using X button in this window.

Clicking Back takes you back to main menu screen

Clicking Submit submits the records.