MID TERM INDUSTRIAL TRAINING REPORT

Bug Tracker
Submitted in partial fulfillment of the
Requirements for the award of

DEGREE OF BACHELOR OF TECHNOLOGY IN COMPUTER SCIENCE

&ENGINEERING

Submitted By

Submitted to

Name:

Name:

University Roll No.:

Designation: Assistant Professor

(HOD)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

The systems development life cycle (SDLC), is a term used in software engineering to describe a
process for planning, creating, testing, and deploying an information system.

Phases
1. Preliminary analysis: The objective of phase 1 is to conduct a preliminary analysis, propose
alternative solutions, describe costs and benefits and submit a preliminary plan with
recommendations.
The objective of this application is to develop a Bug Tracking for Improving Software
Quality and Reliability is useful for applications developed in an organization. This
system can be used for logging Bugs against an application/module, assigning Bugs to
individuals and tracking the Bugs to resolution.
The Bug Tracking System can dramatically increase the productivity and accountability
of individual employees by providing a documented workflow and positive feedback for
good performance.
2. Systems analysis, requirements definition: Defines project goals into defined functions
and operation of the intended application. Analyzes end-user information.
The present system is not efficient and effective as the bug tracking cannot be done easily
to improve the softwares quality. The logging Bugs against an application/module,
assigning Bugs to individuals and tracking the Bugs to resolution cannot be done very
effectively.

3. Systems design: Describes desired features and operations in detail, including screen
layouts, business rules, process diagrams, pseudo code and other documentation.
The purpose of the Bug Tracker System is to test the application for the bugs and report it
to the Admin and developer. The main intention behind the Bug Tracker System is that to
track bugs and report them. Store the bug information with a unique id in the database
for future reference. So, this makes the job of handling the bugs easy. The Bug Report
can be mailed in form of documents also. And the Bug List can be stored in form of excel
document (using apache POI API).
4. Development: The real code is written here.

5. Integration and testing: Brings all the pieces together into a special testing
environment, then checks for errors, bugs and interoperability.
6. Acceptance, installation, deployment: The final stage of initial development, where
the software is put into production and runs actual business.
7. Maintenance: During the maintenance stage of the SDLC, the system is assessed to
ensure it does not become obsolete. This is also where changes are made to initial
software. It involves continuous evaluation of the system in terms of its performance.
8. Evaluation: Some companies do not view this as an official stage of the SDLC, but is
it an important part of the life cycle. Evaluation step is an extension of the
Maintenance stage, and may be referred to in some circles as Post-implementation
Review. This is where the system that was developed, as well as the entire process, is
evaluated. Some of the questions that need to be answered include: does the newly
implemented system meet the initial business requirements and objectives? Is the
system reliable and fault-tolerant? Does the system function according to the approved
functional requirements. In addition to evaluating the software that was released, it is
important to assess the effectiveness of the development process. If there are any
aspects of the entire process, or certain stages, that management is not satisfied with,
this is the time to improve. Evaluation and assessment is a difficult issue. However,
the company must reflect on the process and address weaknesses.
9. Disposal: In this phase, plans are developed for discarding system information,
hardware and software in making the transition to a new system. The purpose here is
to properly move, archive, discard or destroy information, hardware and software that
is being replaced, in a matter that prevents any possibility of unauthorized disclosure
of sensitive data. The disposal activities ensure proper migration to a new system.
Particular emphasis is given to proper preservation and archival of data processed by
the previous system. All of this should be done in accordance with the organization's
security requirements.

ABSTRACT
OBJECTIVE

EXISTING SYSTEM & DISADVANTAGES

In the existing system, the Admin assigns the projects to the developers. The developers develop
the projects as per customer requirements. The Admin itself assign the developed applications to
the tester for testing. In the testing phase, when the tester encounters a bug, a unique id number
for each individual bug is generated. The bug information along with its id are mailed to the
developer. This is Bug Report. These are stored in the database. This is useful for further
reference.
Bottlenecks of the Existing System:

The tester report which is called Bug Report is in the form of physical document. If the
document is damaged then the total information about the bug will be lost.

The bug information is not stored in the database for future reference.

PROPOSED SYSTEM & ITS ADVANTAGES

The proposed system organizes the data effectively. The Bug Tracking for Improving Software
Quality and Reliability is a web based application that can be accessed throughout the
organization. This system can be used for logging Bugs against an application/module, assigning
Bugs to individuals and tracking the Bugs to resolution. This system can be used as an
application for the any software based (IT) company to reduce the Bugs in softwares quality and
reliability.
It is simple to understand and can be used by anyone who is not even familiar with simple
employees systems. 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.

The Admin is responsible for adding users to Bug Tracker System and assigning projects to the
users.
The Admin assigns projects to the developers. The developer develops the projects as per
customer requirements. The Admin itself assigns the developed projects to the Testers for
testing. The tester tests the application and identifies the bugs in the projects.
When the tester encounters a bug, a unique id number for each individual bug is generated. The
bug information along with its id are mailed to the developer. This is Bug Report. These are
stored in the database. This is useful for further reference.
Bug information includes the bug id, bug name, bug priority, project name, bug location, bug
type.
The bug report is mailed to the developer as soon as the bug is identified. This makes that no
error will go unfixed because of poor communication. It makes ensure that anyone who needs to
know about a bug can learn of it soon after it is reported. Bug Tracker System plays an vital role
in the testing phase. But it also supports assigning projects for the developer, tester by the
Admin. The Bug Tracker System maintains the different users separately i.e., it provides
separate environments for Admin, developer and tester.

MODULE
Project has following modules:

Admin

Developer

Tester

Module Description
1. Admin
Has option to access User data, Project data and Report data.
User Information:
Add User details into the database.
Delete User from the database.
Modify User details.

Project Information:
Add Project into database.
Delete Project from the database by specifying the Project id.
Modify the project details by specifying the project id.
Assign Information:
To assign Project to other users- Developer and Tester.
View all projects.
Assign Project to Developer and Tester by gathering information like user name, project id, and
assigned date.
Search a particular project details by specifying Corresponding project id.
Report:
Used to shown the bug report after specifying the project id.
Export Details of Project List, User List, Bug List into document (excel, docx -using Apache Poi
API)

2. Tester
View Project, Track Bugs, Add Bugs and Profile Details.
View Project:
Option to view all his assigned projects.
Track Bug:
Tracks bug in his assigned project.
Add bug information along with bug id & project id, assigned developer, create date and Bug
description.
Profile Details:
This option used to view profile details.
Option to change password.

3. Developer
View Project, Bugs & Profile Details.
View Project:

Option to view all his assigned projects.

View Bugs:
Option to view all bugs corresponding to his assigned project.
Self:
This option used to view profile details.
Option to change password.

Database Requirement
Following are the required details that should be managed by the system:
User Details
Project Details
Bug Details
Bug Assignment Details

Security & Administration

The Bug Tracker have a security system to restrict the user access & role based security for
administration the system resources like:
User Logins
Projects
Task Assignments

TOOLS AND LANGUAGE USED

FRONT END: Java Server Page (JSP), Servlet, JSTL
LANGUAGES USED: HTML, Java Server Page (JSP), Java Scripts (JS), Ajax,
JQuery
BACK END: MySQL

JAVA and JEE

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 requiresThe 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.

FRONT END
LANGUAGES USED
HTML:- It is used to generate web page. HTML, an initialism of Hypertext Markup Language, is
the predominant markup language for web pages. It provides a means to describe the structure of
text-based information in a document by denoting certain text as headings, paragraphs, lists,
and so on.
JSP:- Java Server Pages (JSP) is a technology that helps software developers create dynamically
generated web pages based on HTML, XML, or other document types. Released in 1999 by Sun
Microsystems, JSP is similar to PHP, but it uses the Java programming language.

To deploy and run Java Server Pages, a compatible web server with a servlet container, such as
Apache Tomcat or Jetty, is required.

BACK END
My SQL is a relational database management system (RDBMS) which has more than 6 million
installations. MySQL stands for "My Structured Query Language". The program runs as a server
providing multi-user access to a number of databases.

PLATFORM
APACHE TOMCAT:- - Apache is a web container, or application server developed at the
Apache Software Foundation (ASF).It adds tools for configuration and management but can also
be configured by editing configuration files that are normally XML-formatted. Apache includes
its own internal HTTP server.

JEE
JEE stands for Java Platform Enterprise Edition. It is one of the most widely used platformindependent Java-centric environments for developing and deploying enterprise-grade web
applications. A set of services, APIs and protocol make up the J2EE platform. Java is a very
useful language as it lets you build a cross-platform application that can communicate with
multiple devices. Codes can be developed on a desktop computer and run across all Java enabled
devices like computers, routers, mobile phones and others. Java is a portable language and its
main feature has made it one of the most successful programming languages
Why should you go with JEE application development?
JEE is already popular among the community of developers. Quick support is available.
Any JEE application development remains object-oriented to provide very fine modular
approach to applications.
There are many similarities among the syntaxes of Java, C and C++. It helps developers easily
understand Java programming. Development requires less time as well.
Java is the ideal language for developing securest web based applications.
Java is already in use as a enterprise-grade programming language.

JEE History
Java Platform, Enterprise Edition or Java EE (formerly known as Java Platform, Enterprise
Edition or JEE up to version 1.5), is a programming platform part of the Java Platform for
developing and running distributed multitier architecture Java applications, based largely on
modular software components running on an application server. The Java EE platform is defined
by a specification.
The year 2000 has seen Java 2, Enterprise Edition (JEE) compliancy move out of the realm of
marketing and into nine shipping products. JEE vendor strategic positioning has continually
changed, from focusing on core products, to an integrated range of JEE services, to JEE
compliancy and finally to avoiding commoditization by leveraging JEE servers as platforms for
Web Services, Wireless and EAI development.
The dominant players in the game have surfaced, but a variety of strategic takeovers may
reshape JEE app. server market share for 2001. The original JEE specification was developed by
Sun Microsystems.
Starting with JEE 1.3, the specification was developed under the Java Community Process. JSR
58 specifies JEE 1.3 and JSR 151 specifies the JEE 1.4 specification.
The JEE 1.3 SDK was first released by Sun as a beta in April 2001. The JEE 1.4 SDK beta was
released by Sun in December 2002.
The Java EE 5 specification was developed under JSR 244 and the final release was made on
May 11, 2006.
Java EE includes several API specifications, such as JDBC, RMI, e-mail, JMS, web services,
XML, etc, and defines how to coordinate them. Java EE also features some specifications unique
to Java EE for components.

ABOUT JAVA SERVER PAGE(JSP)

Java Server Pages (JSP) is a technology that helps software developers create dynamically
generated web pages based on HTML, XML, or other document types. Released in 1999 by Sun
Microsystems, JSP is similar to PHP, but it uses the Java programming language.
To deploy and run Java Server Pages, a compatible web server with a servlet container, such as
Apache Tomcat or Jetty, is required.
JSP may be viewed as a high-level abstraction of Java servlets. JSPs are translated into servlets at
runtime; each JSP's servlet is cached and re-used until the original JSP is modified.
JSP can be used independently or as the view component of a server-side modelviewcontroller
design, normally with JavaBeans as the model and Java servlets (or a framework such as Apache
Struts) as the controller. This is a type of Model 2 architecture.

JSP allows Java code and certain pre-defined actions to be interleaved with static web markup
content, with the resulting page being compiled and executed on the server to deliver a
document. The compiled pages, as well as any dependent Java libraries, use Java byte code
rather than a native software format. Like any other Java program, they must be executed within
a Java virtual machine (JVM) that integrates with the server's host operating system to provide
an abstract platform-neutral environment.

Compiler
A Java Server Pages compiler is a program that parses JSPs, and transforms them into executable
Java Servlets. A program of this type is usually embedded into the application server and run
automatically the first time a JSP is accessed, but pages may also be precompiled for better
performance, or compiled as a part of the build process to test for errors.
Some JSP containers support configuring how often the container checks JSP file timestamps to
see whether the page has changed. Typically, this timestamp would be set to a short interval
(perhaps seconds) during software development, and a longer interval (perhaps minutes, or even
never) for a deployed Web application.

Comparison with similar technologies

JSP pages are similar to PHP pages and ASP.NET Web Forms, in that all three add server-side
code to an HTML page. However, all three terms refer to a different component of the system.
JSP refers to the JSP pages, which can be used alone, with Java servlets, or with a framework
such as Apache Struts. PHP is itself a programming language, designed for dynamic Web pages.
ASP.net is a framework comparable to Struts or Java Server Faces that uses pages called Web
Forms.
While JSP pages use the Java language, ASP.NET pages can use any .NET-compatible language,
usually C#.
ASP.NET is designed for a Microsoft Windows web server, while PHP and Java server
technologies (including JSP) are fairly operating system agnostic.

Caching to improve performance

The popularity of Java Server Pages has meant that it is being used quite frequently in
developing high-traffic web apps. And, this is causing performance bottlenecks as you try to add
more users and transaction load on your Java Server Pages application.
Although, Java Server Pages application can scale very nicely to multiple web servers, the
database server cannot. The main reason for the database becoming a bottleneck is that while you
can add more and more servers to the Java Server Pages application server farm, you cannot do
the same at the database tier.
This results in limited scalability at the data tier. You can remove these Java Server Pages
Servlets performance bottlenecks by using a distributed cache for storing the frequently used
data.

MYSQL
MySQL is a relational database management system (RDBMS) which has more than 6 million
installations. MySQL stands for "My Structured Query Language". The program runs as a server
providing multi-user access to a number of databases.
The project's source code is available under terms of the GNU General Public License, as well as
under a variety of proprietary agreements. MySQL is owned and sponsored by a single for-profit
firm, the Swedish company MySQL AB, now a subsidiary of Sun Microsystems, which holds the
copyright to most of the codebase.
MySQL is commonly used by free software projects which require a full-featured database
management system, such as WordPress, phpBB and other software built on the LAMP software

stack. It is also used in very high-scale World Wide Web products including Google and
Facebook.

References
http://www.google.com
http://www.apache.org
http://www.mysql.com
http://www.wikipedia.org
http://www.java.sun.com