ERROR TRACKING SYSTEM

AN INDUSTRIAL INTERNSHIP REPORT

Submitted in partial fulfilment for the award of the degree of

MTech
in
Software Engineering
by

B SAI ATCHUTHA REDDY (16MIS0176)

School of Information Technology and Engineering

Department of Software and Systems Engineering
OCTOBER 2019

i
 School of Information Technology and Engineering

Department of Software and Systems Engineering

DECLARATION BY THE CANDIDATE

I hereby declare that the Industrial Internship report entitled

“ERROR TRACKING SYSTEM” submitted by me to VIT, Vellore, in
partial fulfillment of the requirement for the award of the degree of
MTech (Software Engineering) is a record of bonafide Industrial
Internship -SWE3099 carried out by me under the guidance of “O
Suman Siddhartha”. I further declare that the work reported in this
project has not been submitted and will not be submitted, either in part or
in full, for the award of any other degree in this institute or any other
institute or university.

Place: Vellore B Sai Atchutha Reddy

Date: 16-10-2019

ii
 School of Information Technology and Engineering

Department of Software and Systems Engineering

BONAFIDE CERTIFICATE

This is to certify that the Industrial Internship report entitled “ERROR

TRACKING SYSTEM” by B SAI ATCHUTHA REDDY
(16MIS0176) to VIT, Vellore, in partial fulfillment of the requirement
for the award of the degree of MTech (Software Engineering) is a
record of bonafide work carried out by him /her under my guidance.
The project fulfills the requirements as per the regulations of this
Institute and in my opinion meets the necessary standards for
submission. The contents of this report have not been submitted and will
not be submitted either in part or in full, for the award of any other
degree or diploma in this institute or any other institute or university.

Prof. Asha N

Examiner(s) Signature

1.
2.

iii
Certificate

iv
 ABSTRACT

Error Tracking System is aimed at providing the Tracking

System of the bugs generated in software, maintenance of the bug levels, fixing of

the Bugs by the developers or programmers inside the organization, the status of the

bugs etc. It also provides ways to view the Bug priorities and assigned levels to the

bug identified and yet accordingly for the bug status.

The Bug priorities are maintained in the form of filters and those

filters are created according to the user level or Administrator level depending upon

the status organized. Reports are now and then produced to maintain the functionality

of the System.

Error Tracking mechanism is employed only is some of the large software

development houses. Most of the others never bothered with bug tracking at all, and
instead simply relied on shared lists and email to monitor the status of defects. This
procedure is error-prone and tends to cause those bugs judged least significant by
developers to be dropped or ignored.

Error Tracking System is an ideal solution to track the bugs of a product, solution
or an application. Bug Tacking System allows individual or groups of developers to
keep track of outstanding bugs in their product effectively. This can also be called as
Defect Tracking System.

The Error Tracking System can dramatically increase the productivity and
accountability of individual employees by providing a documented work flow and
positive feedback for good performance.

All the above features like entry of the bug information, fixing them

up and the filter maintenance category are dealt within the Error Tracking System.

This Project is implemented in Java.

v
 ACKNOWLEDGEMENT
I wish to express our heartfelt gratitude to Dr.G.Viswanathan, Chancellor,
VIT, Vellore, for providing facilities for the Industrial Internship. I am highly
grateful to our Vice President, Dr.G. Sekar Viswanathan, Vice chancellor Dr.
Anand A. Samuel, and Pro-Vice Chancellor Dr.S.Narayanan, for providing the
necessary resources.
My sincere gratitude to Dr. Balakrushna Tripathy, Dean, School of
Information Technology and Engineering, for giving me the opportunity to undertake
the project.
I wish to express my sincere gratitude to Dr. S. Sree Dharinya, Head of the
Department, Software and Systems Engineering, Prof. P.Ushapreethi & Prof.
Ramaprabha KP, Industrial Internship Coordinators, M.Tech (Software
Engineering), School of Information Technology and Engineering for providing me
continuous support to do my project work.
I would like to express my special gratitude and thanks to my external guide
Mr O Suman Siddhartha, Bhaskara Info Services Pvt.Ltd and internal guide Prof.
Asha N Assistant Professor, SITE for their esteemed guidance, immense support and
encouragement to complete the internship successfully.
I thank the management of VIT, Vellore for permitting me to use the library
resources. I also thank all the faculty members of VIT, Vellore for giving me the
courage and strength I needed to complete my goals. This acknowledgement would
be incomplete without expressing my whole hearted thanks to my family and friends
who motivated me during the course of the work.

Place: Vellore
Date: 16-10-2019 B Sai Atchutha Reddy

vi
 TABLE OF CONTENTS

CHAPTER NO. TITLE PAGE NO.

ABSTRACT v
LIST OF TABLES ix
LIST OF FIGURES x
LIST OF SYMBOLS xi

1. INTRODUCTION
1.1.Problem Statement 1
1.2.Motivation 1
1.3.Objective 1
1.3.1.Proposed System 1
1.3.2.Advantages of Proposed system 2
2. TECHNOLOGIES LEARNT 3-4

3. SYSTEM DESIGN 5
3.1 System Architecture 5
3.2 Module description 5-6
3.3 System Specification 6-7
3.3.1 Software Requirements 6
3..3.2 Hardware Requirements 7
3.4 Detailed Design 8
3.4.1 Use case Diagram 8-9
3.4.2 Sequence Diagram 10-11
3.4.3 Class Diagram 12
3.4.4 Dataflow diagram 13
3.4.5 Activity diagram 13-15

vii
4. IMPLEMENTATION 16
4.1 Implementation details 16-22

5. TEST RESULTS 23
5.1 Test cases

6. RESULTS AND DISCUSSIONS 24-26

7. CONCLUSION AND FUTURE WORK 27

7.1 Conclusion 27
7.2 Future Work 27

8. REFERENCES 28

viii
 LIST OF TABLES
Table No Title Page No
4.1.1 Login Details 21
4.1.2 Employee Details 21
4.1.3 Bug Details 21
4.1.4 Bug Entry Details 22
4.1.5 Appraisal Details 22
5.1 Test cases 23

ix
 LIST OF FIGURES

Fig No Title Page No

3.1 System Architecture 5
3.4.1.1 Use case diagram 8
3.4.1.2 Use case diagram for employee 9
3.4.1.3 Use case diagram for admin 9
3.4.2.1 Sequence diagram for admin 10
3.4.2.2 Sequence diagram for employee 11
3.4.3 Class diagram 12
3.4.4 Dataflow diagram 13
3.4.5.1 Activity diagram for login 13
3.4.5.2 Activity diagram for employee 14
3.4.5.3 Activity diagram for admin 15
6.1 Login page 24
6.2 Employee details 24
6.3 Employee stages 25
6.4 Updating employee details 25
6.5 Tester login 26
6.6 Bug entry 26

x
 LIST OF ABBREVIATIONS

ACRONYM EXPANSION
DSR Dynamic Source Routing
AODV Ah hoc On Demand Distance Vector
FSR Fisheye State Routing Protocol
IDT Indirect Trust
IDTREQ Indirect Trust Request
IDTREP Indirect Trust Reply
TTL Time To Live
NSG Network simulator Script Generator

xi
 Chapter 1

INTRODUCTION

1.1 Problem Statement

Error tracking system is aimed at providing the tracking system of bugs generated in
the software, maintenance of bug levels, and fixation of bugs by the developers in the
organization, the status of the bugs etc.
It also provides way to view the bug priorities and assign levels to the identified bugs
and yet according to the bug status. The bug priorities are maintained in the form of
filters and those filters are created according to the user level or administrator level
depending on the status organized.
1.2 Motivation

The main motivation of this system is develop flawless system, which is access real
time information from anywhere in the world, 24 hours a day 365 days in a year.
Another aim is that manage hundred of projects in multiple locations or just a few.
The another main motive of this system is track the all the defects or bugs in the
project and make the project user friendly and bugs free system.

1.3 Objective

The objective of this project is to build a tool for the maintenance of bugs
involved in the software production. Based on the performance of each programmer
in terms of bugs, the appraisal value must be calculated. It also automates the process
of manually handling the status and critical evaluation of bugs and its priorities.

1.3.1 Proposed System

This system maintains the products, Bugs and bug Tracking. It has advantage of
maintaining bug history it stores all the details from bug origin to bug resolution.
Each product can have versions for easy maintenance of the product and all the user
of the product is stored in the database. It provides the advantage of maintaining
users to the bugs and resolutions provided by them. Our System provides the
searching based on status, priority, and operating system. It provides with user and
bug hierarchy, which would be helpful in knowing the relation between bugs and

1
users allotted to the bug. It is provided with a fully authenticated system with
password encryption. And has the facility for storing attachments for a bug. One can
keep a track of the bug in a product with much lower cost and effort. The most
advantage of this system is maintaining log records which are helpful in knowing any
errors or misuse of the system by other users.

1.3.2 Advantages of proposed system

The methodology deployed for the development of this project is prototyping.
This is one of the best options to develop real time projects. The applications which
are to be built in the quick space of time can be effectively created using this method.
First of all, a model of the application is exemplified with the minimal and
sufficient requirements. Then the application further evolves based on the user views
about the model. Due to this the end user can get a clear picture of what and how the
product will look like and the programmer can accommodate changes easily. Hence
this method of application development was chosen for this project.

2
 Chapter 2
TECHNOLOGIES LEARNT
Java
Java technology is both a programming language and a platform.The Java
programming language is a high-level language that can be characterized by all of
the following buzzwords:
 Simple
 Object oriented
 Distributed
 Interpreted
 Robust
 Secure
 Portable
 High performance
 Dynamic

A platform is the hardware or software environment in which a program runs. We've

already mentioned some of the most popular platforms like Windows 2000, Linux,
Solaris, and MacOS. Most platforms can be described as a combination of the
operating system and hardware. The Java platform differs from most other platforms
in that it's a software-only platform that runs on top of other hardware-based
platforms.

The Java platform has two components:

 The Java Virtual Machine (Java VM)

 The Java Application Programming Interface (Java API)

ODBC
Open Database Connectivity is a standard application programming interface for
accessing database management systems. The designers of ODBC aimed to make it
independent of database systems and operating systems. An application written using
ODBC can be ported to other platforms, both on the client and server side, with few
changes to the data access code.
ODBC accomplishes DBMS independence by using an ODBC driver as a translation
layer between the application and the DBMS. The application uses ODBC functions
through an ODBC driver manager with which it is linked, and the driver passes the
query to the DBMS. An ODBC driver can be thought of as analogous to a printer
driver or other driver, providing a standard set of functions for the application to use,
and implementing DBMS-specific functionality. An application that can use ODBC

3
is referred to as "ODBC-compliant". Any ODBC-compliant application can access
any DBMS for which a driver is installed.
Drivers exist for all major DBMSs, many other data sources like address book
systems and Microsoft Excel, and even for text or comma-separated values files.
ODBC remains in wide use today, with drivers available for most platforms and most
databases. It is not uncommon to find ODBC drivers for database engines that are
meant to be embedded, like SQLite, as a way to allow existing tools to act as front-
ends to these engines for testing and debugging.
However, the rise of thin client computing using HTML as an intermediate format
has reduced the need for ODBC. Many web development platforms contain direct
links to target databases – MySQL being very common. In these scenarios, there is
no direct client-side access nor multiple client software systems to support;
everything goes through the programmer-supplied HTML application. The
virtualization that ODBC offers is no longer a strong requirement, and development
of ODBC is no longer as active as it once was.

Rational Rose
Rational Rose is an object-oriented programming (OOP) and unified modelling
language (UML) tool to design enterprise-level software applications and
components. It creates visual software application models under object-oriented
principles. Example application models include the creation of actors, use cases,
relationships, objects, entities, etc. Rational Rose uses classical UML concepts to
graphically model software applications. This facilitates documenting the
environment, requirements and overall design.
OOP methodologies use UML to graphically depict software application behaviour
and architecture. These models are the building blocks and development blueprint of
the application’s entire construction process. The popular Rational Rose modelling
tool allows developers to create entire architecture or component-level system
models, while depicting relationship and control flow.

Rational Rose is a powerful graphical user interface modelling tool using efficient
and user-friendly drag and drop and design manoeuvrability. Certain Rational Rose
versions actually produce relevant source code for designed models.

4
 Chapter 3
SYSTEM DESIGN
3.1 System Architecture

Guest

Employee
Admin

Error
Tracking
System

Tester Programmer/De
veloper

Manager

Fig 3.1 System Architecture

3.2 Module Description

3.2.1 Employee
Employees are of two types, developers and testers. Developers are used to
develop program and open bugs where as testers resolve the bugs and save to the
database.
3.2.2 Administrator
Administrator is a person who will take care of all registration status,
acceptance of new bugs, and many other tasks to reduce burden on employee.

5
3.2.3 Bug Identification

This module identifies the bug for a specific language. The languages will be
distinguished by unique language code. This module includes the types of errors
which are present in the program and a master table is maintained for the type of
errors.
3.2.4 Bug Status Maintenance

There are four different states –Wait, Open, Ready, Closed.

Initially the status of the bug will be wait. When the bug is viewed the status is set to
open. After the bug is cleared the status is set to ready. Then the project leader cross
checks the bug and if he is satisfied then the status of the bug is set to close.
3.2.5 Programmer Tracking

In this module the employee details are maintained in a separate database.

Also the details of the project under which the employees are working is maintained.
3.2.6 Appraisal

The appraisal is calculated depending upon the performance of the employee.

The factors for deciding the performance includes efficiency, effectiveness, total
working hours, time taken to clear the bugs etc.,

3.3 System specification

3.3.1 Software Requirements
 Front End: Java 1.4
 Back End: Oracle 8i

Front-end tool: JAVA 1.4

Java is an object-oriented programming language developed sun

microsystems and it is also a powerful internet programming language. Java is a
high-level programming language. Java is an efficient application programming
language. It has APIs to support the GUI based application development. The
following feature of java makes it more suitable for implementing this project.

6
Platform Independent

Platform independence-that is, the ability of a program to move easily

from one computer system to another-is one of the most significant advantages that
Java has over other programming languages. Java is platform independent at both the
source and the binary level.

Powerful database connectivity

Java has powerful database connectivity. The effective back end

connectivity support will results in quick retrieval and storage of large volume of
data .It also supports concurrency control mechanisms and thus it can improve the
data consistency.
Back-end tool: Oracle 8i

 Oracle supports the largest of databases, which can contain terabytes of

data.
 It minimizes data contention and guarantees data concurrency.
 Oracle maintains the preceding features with a high degree of overall
system performance.
 Database users do not suffer from slow processing performance.
 Oracle also offers the heterogeneous option that allows users to access
data on some non oracle database transparently.

3.3.2 Hardware Requirements

 Monitor : 800*600 minimum resolution of 256 colors

 Processor: At least 166 MHz processor
 Input : Two or Three button mouse and standard 104 keyboards.

7
3.4 Detailed Design

3.4.1 Use case Diagram

Overall Use case

<<include>>

Validation Login

Project

Administrator

Department
Employee

Monitor

Manager

Developer Tester
Bugs

Testplan

Fig 3.4.1.1 Use case diagram

8
Employee

Register

Login

Project

Employee

Bugs

Testplan

Developer Tester

Logout

Fig 3.4.1.2 Use case diagram for employee

Administration

Login

Permission

Project

Administrator
Department

Developers

Create Employee

Testers

Create Manager

Logout

Fig 3.4.1.3 Use case diagram for admin

9
3.4.2 Sequence Diagram

Administrative Process

Login Permission Manager Employee Department Project

: Administrator

1: loginrequest()
validation
response()

2: Create()
response()

3: create()
valid()
confirmation()

4: create()
valid()
confirmation()

5: view()

6: view()

Fig 3.4.2.1 Sequence diagram for admin

10
Employee Process

Register Login Project Bugs Test Plan

: Employee

1:Fill up the details

Developer()
Verfication
Confirmation()

Tester()
Verification
Confirmation()
2: Login Request()
Validation
response()

3: employee selects alloted project()

response()

4: Tester identify bugs()

5: tester develop testplan
submit to developer
submit to developer

employee rectify bugs

confirmation()

Fig 3.4.2.2 Sequence diagram for employee

11
3.4.3 Class Diagram

Fig 3.4.3 Class diagram

12
 3.4.4 Dataflow Diagram
Appraisal Value
Entry
Add Employee Fixation of Bugs
Details

Bug entry Error Assigning

Tracking Priority
System

View & Change Corrects &

status of Bugs Change status of
Bugs

Fig 3.4.4 Data flow diagram

3.4.5 Activity Diagram

Login

Providing
Credentials

Retry

Validation

<<No>>

<<YES>>

Services

Fig 3.4.5.1 Activity diagram for login

13
Employee Process

Employee

Developer Tester

Login
Bugs Testplan

validation
Projects update delete
create create update delete

select
Login

Rectify

Logout

Fig 3.4.5.2 Activity diagram for employee

14
Administrative Process

Login

validation

Employee Manager Projects Department

Create/upd
ate/delete
View

Permission

Logout

Fig 3.4.5.3 Activity diagram for admin

15
 Chapter 4

IMPLEMENTATION

4.1 Implementation Details

login.java
import javax.swing.*;
import javax.swing.border.*;
import java.awt.*;
import java.awt.event.*;
import java.util.*;
import java.text.*;
import java.sql.*;
import java.net.*;
import java.io.*;
class login implements ActionListener,KeyListener,FocusListener
{
JFrame f;
Container c;
Connection connection;
Statement statement;
ResultSet rs;
boolean f1=false;
String a2="hai";
JTextField tfield_user_name;
JPasswordField tfield_password;
JLabel label_user_name,label_password,label_message;
JButton button_login,button_cancel;
String[] tfield_text_login=new String[4];
String uid,pwd;
login()
{ try{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
connection = DriverManager.getConnection("jdbc:odbc:siva","scott","tiger");

16
statement = connection.createStatement();
} catch(Exception x)
{System.out.println(x); }
f=new JFrame("Login Process");
c=f.getContentPane();
tfield_user_name=new JTextField();
tfield_password=new JPasswordField();
label_message=new JLabel("Enter username & password");
label_user_name=new JLabel("User Name");
label_password=new JLabel("Password");
button_login=new JButton("Login");
button_cancel=new JButton("Cancel");
c.setLayout(null);
f.setBounds(200,200,300,170);
label_message.setBounds(60,10,225,20);
label_user_name.setBounds(10,35,75,20);
label_password.setBounds(10,65,75,20);
tfield_user_name.setBounds(120,35,150,20);
tfield_password.setBounds(120,65,150,20);
button_login.setBounds(50,100,75,25);
button_cancel.setBounds(150,100,75,25);
c.add(label_message);
c.add(label_user_name);
c.add(label_password);
c.add(tfield_user_name);
c.add(tfield_password);
c.add(button_login);
c.add(button_cancel);
tfield_user_name.addKeyListener(this);
tfield_user_name.addFocusListener(this);
tfield_password.addFocusListener(this);
tfield_password.addKeyListener(this);
button_cancel.addActionListener(this);
button_cancel.addKeyListener(this);
17
button_cancel.addFocusListener(this);
button_login.setFocusable(true);
button_login.addActionListener(this);
button_login.addKeyListener(this);
button_login.addFocusListener(this);
f.setResizable(false);
f.show();
}
public void focusGained(FocusEvent fe)
{
}
public void focusLost(FocusEvent fe)
{
}
public void keyPressed(KeyEvent ke)
{
if(ke.getKeyCode() == 10)
{
{ if (ke.getSource()==tfield_user_name)
{ tfield_password.requestFocusInWindow();}
if (ke.getSource()==tfield_password)
{ button_login.requestFocusInWindow();}
if (ke.getSource()==button_login)
{ button_login.doClick();}
if(ke.getSource()==button_cancel)
{
button_cancel.doClick();
} }}}

bugentry.java

import java.awt.*;
import java.lang.*;
import javax.swing.*;

18
import javax.swing.border.*;
import java.awt.event.*;
import javax.swing.tree.*;
import javax.swing.event.*;
import java.net.*;
import java.io.*;
import java.sql.*;
public class bugentry implements FocusListener,KeyListener,ActionListener
{ Connection connection;
Statement statement;
ResultSet rs1,rs;
int value;
JPanel testername_panel=new JPanel();
JPanel bugdetail_panel=new JPanel();
JPanel btn_panel=new JPanel();
Border border= new LineBorder(Color.gray,1);
GridLayout grid=new GridLayout(2,5,5,5);
Container c;
JFrame f=new JFrame("Bug Entry");
JLabel lbl_testername=new JLabel("Tester Name");
JTextField tf_testername=new JTextField();
JLabel lbl_code=new JLabel("Code");
JTextField tf_code=new JTextField();
JLabel lbl_date=new JLabel("Date");
JTextField tf_date=new JTextField();
JLabel lbl_duedate=new JLabel("Due Date");
JTextField tf_duedate=new JTextField();

JLabel lbl_projname=new JLabel("Project Name");

JTextField tf_projname=new JTextField();
JLabel lbl_modname=new JLabel("Module Name");
JTextField tf_modname=new JTextField();
JLabel lbl_section=new JLabel("Section");
JTextField tf_section=new JTextField();
19
 JLabel lbl_lang=new JLabel("Language");
JTextField tf_lang=new JTextField();
JLabel lbl_errorcode=new JLabel("Error Code");
JTextField tf_errorcode=new JTextField();
JLabel lbl_name=new JLabel("Name");
JTextField tf_name=new JTextField();
JLabel lbl_desc=new JLabel("Description");
JTextArea tf_desc=new JTextArea();
JLabel lbl_pgmname=new JLabel("Program Name");
JTextField tf_pgmname=new JTextField();
JLabel lbl_status=new JLabel("Status");
JTextField tf_status=new JTextField();
JButton btn_add=new JButton("ADD");
JButton btn_clear=new JButton("CLEAR");
JButton btn_cancel=new JButton("CANCEL");
bugentry()
{
try{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
connection = DriverManager.getConnection("jdbc:odbc:mano","scott","tiger");
statement = connection.createStatement();
}
catch(Exception x)
{
System.out.println(x);
}

20
 Database Design
Login

Username Varchar2(25)
Password Varchar2(25)
Designation Varchar2(25)

Table 4.1.1 Login Details

Employee
Ecode Varchar2(10)
Ename Varchar2(25)
Eadd Varchar2(25)
Ecity Varchar2(25)
Epin Varchar2(25)
Ephone Varchar2(10)
Edept Varchar2(25)
Edesign Varchar2(25)
Eskillset Varchar2(10)
Epstage Varchar2(25)

Table 4.1.2 Employee Details

Bug details
Buglang Varchar2(10)
Bugcode Varchar2(10)
Bugtype Varchar2(10)
Bugname Varchar2(10)
Bugdesc Varchar2(25)

Table 4.1.3 Bug Details

21
Bug entry

Ename Varchar2(25)
Ecode Varchar2(10)
Opendate Date
Duedate Date
Projname Varchar2(25)
Modname Varchar2(25)
Section Varchar2(25)
Langtype Varchar2(10)
Errcode Varchar2(10)
Errname Varchar2(25)
Errstatus Varchar2(10)

Table 4.1.4 Bug Entry Details

Appraisal details

Ecode Varchar2(10)
Ename Varchar2(25)
Edesign Varchar2(25)
Joindate Date
Appperiod Varchar2(10)
Projteam Varchar2(10)
Projname Varchar2(25)
Valuepoints Number

Table 4.1.5 Appraisal Details

22
 Chapter 5

TEST RESULTS

5.1 Test cases

Test case is a specification of the inputs, execution conditions, testing procedure, and
expected results that define a single test to be executed to achieve a particular
software testing objective, such as to exercise a particular program path or to verify
compliance with a specific requirement.

S.no Input Expected Actual output Pass/Fail

output
1. Click on login Admin menu Admin menu Pass
button with page will be page is
admin opened opened
credentials
2. Click on Employee Bug entry Fail
employee page should page is
details be opened opened

3. Click on view Bug details Bug details Pass

Bug details module should module is
menu be opened opened

4. Enter User should User logged Pass

Username and be able to into the
password access the system
page
5. Click on Employee Employee Fail
Update details should details not
employee be updated updated
details
6. Click on Already Records not Fail
search records existing found
records should
be displayed

Table 5.1 Test cases

23
 Chapter 6
RESULTS AND DISCUSSIONS

Screenshots

Fig 6.1 Login Page

Fig 6.2 Employee Details

24
 Fig 6.3 Employee Stages

Fig 6.4 Updating Employee Details

25
Fig 6.5 Tester Login

Fig 6.6 Bug Entry

26
 Chapter 7

CONCLUSION & FUTURE WORK

7.1 Conclusion

This proposed system enables the bug maintenance easier and eliminates the
chaos involved in the complexities of tracing a bug within a project team.
Performance appraisal can be done based on the performance criteria fixed by the
organization and provisions are provided to evaluate the efficiency of programmer
under various circumstances.

7.2 Future Work

Different kind of statistical data can be fetched from the database and the
results can be presented in the form of reports. Request for password changes can be
automated so that the indication need not be done manually for the given point of
time. The employee details within an organization can be centralized. It enables the
employers to gather information about an employee from anywhere within the
organization.

27
 Chapter 8

REFERENCES

[1] J. Aranda and G. Venolia, “The secret life of bugs: Going past the errors and
omissions in software repositories”, In ICSE’09 Proceedings of the 31st International
Conference on Software Engineering, 2009.
[2] Singh V.B., Kapur P.K. and Abhishek Tandon, “Measuring Reliability Growth of
Software by Considering Fault Dependency, Debugging Time Lag and Irregular
Fluctuation”, ACM SIGSOFT, Software Engineering Notes Vol. 35 , No.3 pp.1-11,
May 2010.
[3] V.B. Singh, Krishna Kumar Chaturvedi, “Bug Tracking and Reliability
Assessment System (BTRAS)” International Journal of Software Engineering and Its
Applications Vol. 5 No. 4, October, 2011.
[4] J. Anvik, L. Hiew, and G. C. Murphy, Who should fix this bug?, In ICSE06
Proceedings of the 28th International Conference on Software engineering, pages
361370.
[5] Hert Schildt, Herbert Schildt, “JAVA 2: The Complete Reference “, TMH,
California, 1999.
[6] Dr. Sathyaraj Pantham, “Pure JFC Swing”, Sams Tech Media Publications,

Delhi, 1999.

28