CASE STUDY: BUG TRACKING SYSTEM

A bug can be defined as an unexpected defect in a computer program Number of faults, flaws and imperfection can be encountered in an application developed with a given technology and platform. All these bugs should be reported to the organization responsible lot the development of that Particular software product. All software development companies are interested in getting updates for the recognized bugs in all of their products, so that, they can be fixed at the earliest by their technical experts. We need a system which can help in tracking bugs with all information about them. Such a system is known as bug tracking system.

The required information about a bug can include.
- Time, when the bug first appeared
- steps to reproduce this bug, if any.
- The product name and version related to bug.
- Environment (Windows. UNIX) in which bug appeared.
- Type of the bug (GUI, Server].

A bug tracking system is software which can be designed to help programmers in keeping track of reported bugs in their other software products. This can be seen as one of the form of issue tracking system. A bug tracking system allows user to report a detected bug directly to the concerned people who can fix it. A bug tracking system can be integrated with some other software management applications and can be used internally in a software developing organization to improve the team work efficiency.

A bug tracking system maintains a database that records all fads about all detected and reported bugs. The details about a bug may include its seventy, the unexpected program behavior, the identity of the user who reported it and identity of expert who is fixing it.

A bug can be assigned a status according to the stage of its life cycle and can be moved from one status to another status like new, assigned, closed and more. Only an administrator should be allowed to configure the different states of a bug. The complexity of fixing a bug does not depend on the severity of that bug.

This chapter discusses the software development life cycle of a project named Bug Tracking System which can be used to track all bugs reported by the user.

SDLC of the Project

The software development life cycle (SDLC) of a project should be discussed first when a project development is planned. An efficient requirement analysis and software design assures the development of equally efficient system with fewer efforts in changing modules again and again which the case may be with a poorly analyzed and designed system. The SDLC of the project has been discussed further in this chapter

Requirement Analysis

The requirement analysis of a given system specifies its exact need. All requirements to be fulfilled by the newly designed system should be considered first before designing it. A better design can only be prepared after a full requirement analysis of the system and finding why the system is required. A bug tracking system can be used by some end users who con report a bug encountered by them. The other users of this application are software management people who are responsible to handle all the bugs reported and fix them. Following is the list of requirements to be fulfilled for bug tracking system.

• it should provide a user Interface to submit the details of a newly discovered bug with all details like its type, its severity, the steps to reproduce it and some erroneous behavior of the application due to the bug

• There should be a provision of assigning reported bugs to a programmer or a group of programmers responsible and capable of fixing these bugs.

• All users should be capable of viewing status of reported bugs.

• The expert group should be provided some user interface to give some possible solutions for the reported bugs

• All types of access to the system should be checked and verified for the authentication of the user.

After going through requirement analysis, we can design various modules for the application. These modules can be designed and planned separately and integrated together to make whole application work and meet all requirements specified in requirement specifications.

• Login module
• Admin module
• Technical Expert module
• Bug Reporting module

Let us now discuss all these modules in detail.

Login Module

This module has been designed to manage login process. All types of accesses by different type of users are verified for their authentication. This module includes user interface to enter login id and password to check the identity of the user. Only the authorized user can configure reported bug for Ito status. Different modules ore secured from different type of users who dog

Admin Module
This module manages functions such as assigning various properties to the reported bugs (severity, priority) and changing its status. Further, it handles the assignment of specific bug to some technical expert who can fix it. An administrator can also delete the bugs if required.

Technical Expert Module
This module helps in handling of reported bugs by some technical experts assigned to them by administrator. They can provide some sort of solutions for the reported bugs. Some bugs cannot be fixed in the current version of the software produce and hence the solution can be given in the form of new version of the product. A technical expert can give solutions only for the bugs assigned to it.

Bug Reporting Module
This module provides user interfaces to submit details of a newly encountered bug. A normal user cart sign in and report a bug which has been detected by him. The user can enter it details of the bug including how the program behaves because of the bug, the steps to reproduce bug, and type of the bug, A user can see details all the bugs reported by him with the different comments given by num of technical experts.

Database Design
Facts about all reported bugs are to be maintained in database. The available authorized user Who can access the system is also stored in the form of table. Hence, we design a database schema to be managed by this application.

The queries for all tables have been given in queries.txt file which you can find in Bug Tracking System folder. Execute all queries given to create tables and input some records in them. The Insert queries have also been provided in the same file.

Development
With the available requirement specification prepared in requirement analysis phase and design specification created after software designing phase, we can start the development of our bug tracking system with the creation of different components like Servlet and JSP page.

The following details give a brief idea about various components in different modules:

      •Home page

JSP pages

      •header.jsp

      •menu.jsp

      •default.jsp

       •Login module

  Servlet

     •Login.java

 JSP pages

     •login.jsp

     •logout jsp

     •loginerror.jsp

     •admin.jsp

     •expert.jsp

    •user.jsp

Admin module

  Servlet

    •SignUp.java

  JSP pages

    • bugsadmin.jsp

    • updatebug.jsp

   • updatebug1.jsp

   •del.jsp

   •bugdetaill.jsp

   •configexp.jsp

   •configexpl.jsp

   •addexpert.isp

Technical Expert module

   JSP pages

    •bugcomment.jsp

    •addcomment.jsp

 Bug Reporting module

   Servlet

     • ReportBug.java

    JSP pages

     •signup.jsp

     •reportbuq.jsp

     •viewbugs.jsp

     •bugdetails.jsp

You can find the project folder with all sub folders and code files in Bug Tracking System folder. The project folder is named bug. Create a directory structure similar what has been created in the project folder. You can copy all code files from the bug folder. All .java files ore available in Bug Tracking System\bug\WEE-INF\src folder and all . jsp files are in Bug Tracking System\ bug folder.

The reader can copy the project folder bug and place d in the webapp folder of their Tomcat installation and can run the application to see the flow of project Figure V.1.1 presents the home page of this Web application.

Testing
Testing may be destructive for any of the project, but creation and checking of project for the test cases is important to find out all the logical flaws in the developed project. The project is also tested for the proper functioning of all methods and modules designed and developed along with the testing of all navigation routes in the application.

Implementation and Maintenance

This is the lost phase in the development of any project. A fully tested protect is implemented in the real working environment and maintained thereafter for the changes required due to change in requirement of the user or any other fault detected after implementation.

Attachment:- Assignment.rar