A

PROJECT REPORT

ON

BUG-TRACKER

RAJASTHAN TECHNICAL UNIVERSITY

(IN PARTIAL FULLFILLMENT FOR THE AWARD OF THE DEGREE)

OF

BACHELOR OF TECHNOLOGY IN

COMPUTER SCIENCE ENGINEERING

SESSION 2016-2020

JAGANNATH GUPTA INSTITUTE OF ENGINEERING AND TECHNOLOGY

SUBMITTED TO: SUBMITTED BY:

MR.PEEYUSH KULSHRESTHA SATYAM KUMAR
[HOD. CSE DEPT.] B.TECH 7TH SEM CSE
MR. GAJENDRA SHRIMAL 16EJGCS031

~1~
 PREFACE

The main objective of any computer science student is to get as much of practical
knowledge as possible .Being an able to have a practical knowledge by developing a
project is a lifetime experience. As practical knowledge is as important as theoretical
knowledge .We are thankful of having a project.
Through the development of the project we had a great experience of various
strategies that can be applied in development of project .This project is stepping stone
for our carrier . We are pleased to present this project .Proper care has been taken
while organizing the project so that is to comprehend. Also, various software
engineering concepts have been implemented.

~2~
 ACKNOWLEDGEMENT

This project has seen the light of the day due to the support, guidance, and blessings
of teachers ,colleagues and friends .I wish to express sincere gratitude to the CSE
department ,JNIT and faculties to support ,encouragement and motivating during
writing of the report .

I am extremely grateful to Mr. Peeyush Kulshrestha ,HOD of CS department to

giving me this opportunity .

I am extremely grateful to Mr. Gajendra Shrimal , Project coordinator ,CS

department to coordinate me.

I am extremely grateful to Mr. Parth Maheshwari, Project Supporter, to supporting

me.

ANUBHAV DUBEY

~3~
 CERTIFICATE

This is to certify that the project entitled “BUG TRACKER” submitted by ANUBHAV
DUBEY is partial fulfilment of the requirement for the award of Bachelor Of
Technology in Computer Science in Jagannatha Gupta Institute of Engineering and
Technology , Sitapura Industrial Area ,Jaipur is an authentic work carried out by her
under my supervision and guidance . To the best of my knowledge the matter
embodied in the project has not been submitted to any other University for the award
of any degree.

Mr. Gajendra Shrimal Mr. Peeyush Kulshrestha

(Assit. Prof. CS Dept.) (HOD CS Dept.)

~4~
 DECLARATION

I hereby declare that the work which is being presented entitled “BUG TRACKING
SYSTEM” in partial fulfilment for the award of the Degree of Bachelor Of Technology
in Computer Engineering affiliated to Rajasthan Technical University,Kota and
submitted to the Department of Computer Engineering of JaganNath Gupta Institute
of Engineering & Technology ,Jaipur ,is an authentic record of my own work carried
out under research paper during the session 2019-2020.
I have not submitted the matter presented in this report anywhere for the award of
any other institute/university.

Signature of the Student with Name & Reg. No.:

Place : _____________
Date : _____________

~5~
 ABSTRACT

Bug Tracking System is the system which enable to detect the bugs. It not merely detects the bug
but provides the complete information regarding bugs detected. Bug Tracking System ensures the
user of it who needs to know about a provide information regarding the identified bug. Using this no
bug will be unfixed in the developed application. The developer develops the project as per customer
requirements. In the testing phase the tester will identify the bugs. Whenever the tester encounter
Eon number of bugs he adds the bug id and information in the database. The tester reports to both
project manager and developer. The bug details in the database table are accessible to both project
manager and developer. When a customer puts request or orders for a product to be developed.
The project manager is responsible for adding users to Bus Tracking System and assigning projects
to the users.

The project manager assigns projects to the developers. The developer develops the projects as per
customer requirements. The project manager itself assigns the developed applications to the Testers
for testing. The tester tests the application and identify the bugs in the application. When the tester
encounter no. of bugs, he generates a unique id number for each individual bug. The bug information
along with its id are mailed to the project manager and 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.
This whole process continues until all the bugs are got fixed in the application.
The bug report is mailed to the project manager and 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.

~6~
 CONTENT
Serial Page
No no.
1 INTRODUCTION 9
1.1 Purpose 10
1.2 Scope 10
1.3 Technologies Used 10
1.4 Overview 10
2 OVERALL DESCRIPTION 11
2.1 Goals of proposed system 11
2.2 Background 12
2.3 Project Requirements 13
3 FEASIBILITY STUDY 14
3.1 Technical Feasibility 15
3.2 Economical Feasibility 15
3.3 Operational Feasibility 16
3.4 Schedule Feasibility 17
4 DATA FLOW DIAGRAMS 18
5 ER DIAGRAMS 19
6 USE CASE DIAGRAMS 20
7 SNAPSHOTS 21-29
8 CONCLUSION 30
9 REFERENCES 31

~7~
 LIST OF FIGURES

Figure Number Figure Content

Fig 1 Block diagram for login

Fig 2 Entity relationship Diagram

Fig 3 Use case Diagram

Fig 4 Login page for any operator

Fig 5 Registering Screen Page

Fig 6 Changing Password

Fig 7 Tester Page

Fig 8 Developer’s Page

Fig 9 Bug Entry

Fig 10 Bug Issue Having Details of the Bug

Fig 11 Email Verification

Fig 12 Database Structure

~8~
INTRODUCTION
A bug tracking system or defect tracking system is a software application that keeps track of
reported software bugs in software development projects. It may be regarded as a type of issue
tracking system.

Many bug tracking systems, such as those used by most open-source software projects, allow end-
users to enter bug reports directly. Other systems are used only internally in a company or organization
doing software development. Typically bug tracking systems are integrated with other project
management software.

A bug tracking system is usually a necessary component of a good software development

infrastructure, and consistent use of a bug or issue tracking system is considered one of the "hallmarks
of a good software team".

A major component of a bug tracking system is a database that records facts about known bugs. Facts
may include the time a bug was reported, its severity, the erroneous program behaviour, and detail on
how to reproduce the bug; as well as the identity of the person who reported it and any programmers
who may be working on fixing it.
Typical bug tracking systems support the concept of the life cycle for a bug which is tracked through
the status assigned to the bug. A bug tracking system should allow administrators to configure
permissions based on status, move the bug to another status, or delete the bug. The system should also
allow administrators to configure the bug statuses and to what extent a bug in a particular status can
be moved. Some systems will e-mail interested parties, such as the submitter and assigned
programmers, when new records are added or the status changes.

Traditional test management tools such as HP Quality Centre and IBM Rational Quality Manager
come with their own bug tracking systems, other tools integrate with popular bug tracking systems.

~9~
1.1) Purpose
• The Software acts as a communication bridge between a tester and developer .
• It maintains two levels of users:-
➢ Administrator Level
➢ User Level
• The Software includes:-
➢ Maintaining Bug description.
➢ Providing bug type, severity.

1.2) Scope
It can be used in any Software Organisation, Start-ups to improve their product ability.

1.3) Technologies to be used

This project will be a desktop application to be developed in Core Java having My SQL as backend.

• Database Design (My SQL)

• Frame Work(FLASK)
• Coding (PYTHON)
• IDE(PyCharm)
• XAMMP as a Server
• HTML,CSS and JS for webpages
1.4) Overview
➢ Project is related to Bug tracking

➢ The project maintains two levels of users:-

• Administrator Level
• User Level-Data Entry Operator
➢ Main facilities available in this project are:-
• Maintaining Bug Details.
• Providing effective ways to look on the Bug.

~ 10 ~
2. OVERALL DESCRIPTION
2.1) Goals of proposed system

1. Planned approach towards working: -

The working in the organization will be well planned and organized. The data will be
stored properly in data stores, which will help in retrieval of information as well as
its storage.

2. Accuracy: -
The level of accuracy in the proposed system will be higher. All operation would be
done correctly and it ensures that whatever information is coming from the user side
is accurate.

3.Reliability: -
The reliability of the proposed system will be high due to the above stated reasons.
The reason for the increased reliability of the system is that now there would be
proper storage of information.

4. No Redundancy: -
In the proposed system utmost care would be that no information is repeated
anywhere, in storage or otherwise. This would assure economic use of storage space
and consistency in the data stored.

5. Immediate retrieval of information: -

The main objective of proposed system is to provide for a quick and efficient
retrieval of information. Any type of information would be available whenever the
user requires.

6. Immediate storage of information: -

In manual system there are many problems to store the largest amount of
information.

7. Easy to Operate: -
The system should be easy to operate and should be such that it can be developed
within a short period of time and fit in the limited budget of the user.

~ 11 ~
 2.2) Background
It is important for an organization to improve its QOS and products for a client so testing is a
important phase to provide above benefits.
➢ Communication between tester and developer.
➢ To keep the track of a bug arises in the Software development.
➢ Providing better developing environment.

Various operational works that are done in a Software

organisation are: -

➢ Developing a Project based on client requirements

➢ Testing those projects.

➢ Removing of bugs
➢ Removing the error to make the project quality good
➢ Keeping information about various client’s requirements.

These are the various jobs that need to be done in a Hospital by the operational
staff and Doctors. All these works are done on papers.

~ 12 ~
2.3) Project Requirements

Hardware Requirements

Processor Ram Disk Space

Pentium II, Pentium III, 64 MB or higher 130 MB

Pentium IV or higher

Software Requirements

Operating Systems Databases

Win-98,Win-XP,Win-7,8,10,Linux,any other MySQL

higher version

2.4) User Characteristics Every user should be:

• Comfortable of working with computer.
• He must have knowledge in Web Browsing.
• He must also have basic knowledge of English too.

2.5) Constraints
• GUI is only in English.
• Login and password is used for identification of user and there is no
facility for guest.

~ 13 ~
3.FEASIBILITY STUDY

Depending on the results of the initial investigation the survey is now expanded to a more
detailed feasibility study. “FEASIBILITY STUDY” is a test of system proposal according to
its workability, impact of the organization, ability to meet needs and effective use of the
resources. It focuses on these major questions:
1. What are the user’s demonstrable needs and how does a candidate system
meet them?
2. What resources are available for given candidate system?
3. What are the likely impacts of the candidate system on the organization?
4. Whether it is worth to solve the problem?
During feasibility analysis for this project, following primary areas of interest are to be
considered. Investigation and generating ideas about a new system does this.

Steps in feasibility analysis

Eight steps involved in the feasibility analysis are:
✓ Form a project team and appoint a project leader.
✓ Prepare system flowcharts. Enumerate potential proposed system.
✓ Define and identify characteristics of proposed system.

✓ Determine and evaluate performance and cost effective of each proposed

system.
✓ Weight system performance and cost data.
✓ Select the best-proposed system.

✓ Prepare and report final project directive to management.

3.1) Technical feasibility

A study of resource availability that may affect the ability to achieve an acceptable system.
This evaluation determines whether the technology needed for the proposed system is
available or not.

~ 14 ~
 • Can the work for the project be done with current equipment existing software
technology & available personal?
• Can the system be upgraded if developed?
• If new technology is needed then what can be developed?
This is concerned with specifying equipment and software that will successfully satisfy the
user requirement. The technical needs of the system may include:

Front-end and back-end selection

An important issue for the development of a project is the selection of suitable front-end
and back-end. When we decided to develop the project we went through an extensive
study to determine the most suitable platform that suits the needs of the organization as
well as helps in development of the project.
The aspects of our study included the following factors.
Front-end selection:
1. It must have a graphical user interface that assists employees that are not from IT
background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the culture.
6. Must provide excellent reporting features with good printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Event driven programming facility.

10.Front end must support some popular back end like Ms Access.
According to the above stated features we selected HTML,CSS and Java Script as the
front-end for developing our project.

~ 15 ~
Back-end Selection:
1. Multiple user support.
2. Efficient data handling.
3. Provide inherent features for security.
4. Efficient data retrieval and maintenance.
5. Stored procedures.
6. Popularity.
7. Operating System compatible.
8. Easy to install.
9. Various drivers must be available.
10. Easy to implant with the Front-end.
According to above stated features we selected Ms-Access as the backend. The technical
feasibility is frequently the most difficult area encountered at this stage. It is essential
that the process of analysis and definition be conducted in parallel with an assessment to
technical feasibility. It centres on the existing computer system (hardware, software etc.)
and to what extent it can support the proposed system.

3.2) Economical feasibility

Economic justification is generally the “Bottom Line” consideration for most systems.
Economic justification includes a broad range of concerns that includes cost benefit
analysis. In this we weight the cost and the benefits associated with the candidate system
and if it suits the basic purpose of the organization i.e. profit making, the project is making
to the analysis and design phase.

The financial and the economic questions during the preliminary investigation are verified
to estimate the following:
• The cost to conduct a full system investigation.
• The cost of hardware and software for the class of application being considered.

~ 16 ~
 • The benefits in the form of reduced cost.
• The proposed system will give the minute information, as a result the
performance is improved which in turn may be expected to provide increased
profits.
• This feasibility checks whether the system can be developed with the available
funds. The Hospital Management System does not require enormous amount of
money to be developed. This can be done economically if planned judicially, so
it is economically feasible. The cost of project depends upon the number of
manhours required.

3.3) Operational Feasibility

It is mainly related to human organizations and political aspects.
The points to be considered are:
• What changes will be brought with the system?
• What organization structures are disturbed?
• What new skills will be required? Do the existing staff members have
these skills? If not, can they be trained in due course of time?
The system is operationally feasible as it very easy for the End users to operate it.
It only needs basic information about Windows platform.

3.4) Schedule feasibility

Time evaluation is the most important consideration in the development of
project. The time schedule required for the developed of this project is very
important since more development time effect machine time, cost and cause
delay in the development of other systems

A reliable Hospital Management System can be developed in the considerable

amount of time.

~ 17 ~
4.DATA FLOW DIAGRAMS

SCREEN1

Fig 1

~ 18 ~
5.ENTITY RELATIONSHIP DIAGRAMS

Fig 2

~ 19 ~
Fig 2: Use Case Diagrams

~ 20 ~
 6.SNAPSHOTS

Fig 4: Login page for any operator

~ 21 ~
Fig 5: Registering Page

~ 22 ~
Fig 6: Reset/Change Password

~ 23 ~
Fig 7: Tester’s Page

~ 24 ~
Fig 8: Developer’s Page

~ 25 ~
Fig 9: Bug Entry

~ 26 ~
Fig 10: Issue/Bug Details

~ 27 ~
Fig 11:Email Verification

~ 28 ~
Fig 12: Database Containing details of Tester/Developer

~ 29 ~
 CONCLUSION

In this document Bug Tracking System helps a software concern to detect and manage the bug in
their products effectively-efficiently. Utilizing bug tracking software can assist in troubleshooting
errors for testing and for development processes. With the ability to provide comprehensive reports,
documentation, searching capabilities, tracking bugs and issues, bug tracking software is a great tool
for those software development needs. Depending on your development needs and the bug tracking
software, you can hope to gain several benefits from bug tracking software.

Some of the benefits are:

❖ Improve communications between groups of people

❖ Increase the quality of the software
❖ Improve customer satisfaction with bug free software
❖ Provides a form of accountability
❖ Increases overall productivity

~ 30 ~
REFERENCE

❖ Bill Evjen, Thiru Thangarathinam, Bill Hatfield, „Professional ASP.NET 1.1

❖ Dave Mercer, „ASP.NET – A Beginners Guide‟, O‟Reilly Publications
❖ http://en.wikipedia.org/wiki/Bug_tracking_system
❖ Jonathan Corbet (May 14, 2008). "Distributed bug tracking". LWN.net .
http://lwn.net/Articles/281849/
❖ Joey Hess (6 April 2007). "Integrated issue tracking with Ikiwiki".
❖ LinuxWorld.com.
❖ http://www.linuxworld.com/news/2007/040607
❖ integrated-issue-tracking-ikiwiki.html

~ 31 ~