KIRINYAGA UNIVERITY

SCHOOL OF PURE AND APPLIED SCIENCE

PROJECT

PROJECT TITLE: BUG TRACKING SYSTEM

A PROJECT REPORT SUBMITTED TO THE

DEPARTMENT OF COMPUTER SCIENCE AND IT

AS A REQUIREMENT FOR THE BSC SOFTWARE

ENGINEERING DEGREE.

NYERERE GEORGE OYARO

PA106/G/6215/19

SUPERVISOR: EDWIN IRERI

Dedication:
I dedicate this work to God, who has always been at my side and has provided me

with knowledge, energy, direction, and the chance to complete this project-oriented

effort.. I thank my dearest parents for supporting me through motivation and finance.

Their support has been endless. To all my family, lecturers, and friends. Thank you

for always moving with me and lifting me whenever I went down.

ACKNOWLEDGEMENT

ii | P a g e
 My sincere acknowledgment goes to our Almighty for the guidance and

protection He has granted me throughout my studies. Wish to extend my

gratitude to my family members and classmates for their tireless efforts, and

to my parents, for the financial and moral support, they have always given me

throughout the academic period. Last but not least I thank my project

supervisor, Mr. Edwin Ireri, for his guidance and support through out this

period, he also happens to be my class mentor.

DECLARATION

iii | P a g e
I declare that this work is mine and an improvement to the existing systems.

Name Regno Signature Date

NYERERE GEORGE PA106/G/6215/19 …………… …………..

Supervisor Signature Date

MR EDWIN IRERI ……………. …………….

iv | P a g e
 ABSTRACT

When a programmer encounters a bug, bug-tracking software is used to

record it so that it can be readily fixed if it occurs again. Everyone on the team

must be able to identify and log bugs. The system that makes it possible to

find bugs is called a bug tracking system. It doesn't just find bugs; it also

gives you all the details you need to know about the bugs you find. A bug can

be recorded by priority status using a bug tracking system. A bug can be

anything from a straightforward question posed by the user to a thorough

technical report of an error or flaw. The tester adds the bug id and details to

the database whenever he runs into a number of bugs. This study presents a

suggested defect tracking approach for categorizing the inserted defect reports

in a step-by-step fashion to further improve software quality. When a user

requests that a product be built, both the project manager and the developer

have access to the data that is stored in the database. The project manager is in

charge of adding users to the bug tracking system and allocating projects to

the users who have bug detection information. while getting a work flow that

is documented and compliments for doing a good job. It has a chat system so

that team members may communicate with one another and work on Bug

issues.

v|P a g e
Table of contents

Dedication:...............................................................................................................................2

ACKNOWLEDGEMENT........................................................................................................2

DECLARATION......................................................................................................................3

ABSTRACT.................................................................................................................................3

CHAPTER ONE...........................................................................................................................6

1.1 Introduction........................................................................................................................6

1.2 Background.........................................................................................................................6

1.3 Current/existing system......................................................................................................6

1.4 Problem Statement.............................................................................................................6

1.5: Proposed System...............................................................................................................6

1.5.1 Feasibility Study............................................................................................................6

1.6 Purpose of the study...........................................................................................................7

1.7 General objective................................................................................................................8

1.8 Specific objectives...............................................................................................................8

1.9 Justification.........................................................................................................................8

1.10 Scope................................................................................................................................8

1.11 Limitations........................................................................................................................8

1.12 Significance of the Study...................................................................................................8

1.13 0peration definition of terms............................................................................................9

CHAPTER TWO:

vi | P a g e
 LITERATURE REVIEW............................................................................................................9

2.1 Introduction....................................................................................................................9

2.2 Related literature review................................................................................................9

2.3: Gaps.............................................................................................................................11

2.4 Conceptual framework..................................................................................................11

Diagram..................................................................................................................................12

2.6 Conclusion.....................................................................................................................13

CHAPTER 3

RESEARCH METHODOLOGY............................................................................................14

3.1 Introduction..............................................................................................................14

3.2 Development methodology......................................................................................15

3.3 Justification of methodology.....................................................................................16

3.4 Data collection..........................................................................................................16

3.5 Data analysis.............................................................................................................17

3.6 CONCLUSION.............................................................................................................18

3.7 REFERENCES..............................................................................................................19

3.8 Appendices................................................................................................................20

vii | P a g e
 CHAPTER ONE

1.1 Introduction

A bug tracking system or defect tracking system is a programme that records and

monitors software development projects' reported bugs. During testing, bug logging

and monitoring are the processes involved . It is being implemented by many software

development companies. It is a tool that many developers and testers have found

useful to use during their development process as it helps them keep track of any

defects. It has also been useful to organizations as the software helps them minimize

their costs by minimizing the risk of the bugs causing system breakdown and

destabilize operations.It is possible for anybody to keep track of their bug record by

the use of this system.The main advantage of this system is that it greatly simplifies

the tracking of bugs for all the parties involved in the development process.The

greatest benefit of this system is its flexibility.

1.2 Background

A bug tracking system or defect tracking system is an application that help developers

and testers to keep track of defects for a software project in a database.

1.3 Current/existing system

Companies/organizations such as Jira, Monday, Github and Redmine have come up with

effective bug tracking systems that have proved to be effective with a great impact. However

1|P a g e
their integration with this systems has much limitations such as; One can only access the bug

tracking system within their site and not beyond that. This research aims to come with a

better solution of making a more utilizable system.

1.4 Problem Statement

Developers and companies want to face the problem of system failure after a system has been

implemented to start operating. As a result there is need to counter combat this issue thus

need for developing a bug tracking system which will help minimize the costs which may

arise as a result of system failure.

1.5: Proposed System

The proposed system is in the form a browser that duplicates an online system, that

provides the centralized database. This system will store the defect data and

description of this defect data. It works based on the information that is in its

database.

1.5.1 Feasibility Study

At this stage, the business proposal is put forth with a fairly general strategy for the

venture and some cost estimations. During system evaluation, the feasibility study of

the proposed system is performed. This is to ensure that the proposed system does not

inhibit the company. It is important to have an understanding of the vital requirements

of the system for feasibility assessment.

Three key considerations involved in the feasibility analysis are;

I. Technical Feasibility

2|P a g e
 The purpose of this research is to determine whether there is a technical barrier to

implementing the system. The system must be technically feasible. This will lead to

high demands on the client. Due to the lack of technical resources, the client will

demand a lot. Because only minor or no alterations are required to put the

programme into practise, it must be technically sound.

II. Operational Feasibility

In this we study when the project will be completed in a given deadline. We ask

ourselves, is the the project feasible according to time or not or it might be very

big and completed in the given time.

III. Economic Feasibility

This research seeks to determine whether the system will benefit the organisation

economically. Because the company does not have unlimited funds for research and

development, the expenses must be justified. Therefore, the system was developed

within the budget using mostly open-source technologies. Only customised products

were purchased.

3|P a g e
1.6 Purpose of the study

The project involves creation of a bug tracking system that will be utilized by

organizations and developers to curb bugs or defects in systems.

1.7 General objective

To allow teams identify defects easily, measure their scope, determine their impact

and manage all the steps involved in resolving them.

1.8 Specific objectives

1.To build a robust bug tracking system where the information about bugs is well

managed.

2.To aid in easy access of bugs at any time.

3.Allows teams to identify defects easily.

1.8.1 Major Modules

I. Manager module;A project's status (whether it is still in progress, has been

finished, or is waiting for additional information) can be known by the

administrator at any time, based on the reports of the various users working on the

project.

II. Admin module; the administrator too has the authority to update the

master details of security and status levels of the project. He can also track

bugs automatically.

4|P a g e
1.9 Justification

The main benefit of this project is that it provides a centralized location where all the

bugs related to a certain product can be managed and resolved due to the available

documentation.

1.10 Scope

The proposed methodology can be employed to track and monitor issues or errors

during software testing. Defect tracking or issue tracking is the procedure of logging

and monitoring bugs or errors. A large programme may have hundreds or thousands

of problems. Each must be evaluated, monitored, and prioritized for fixing.

1.11 Limitations

The main limitation of a bug tracking system is that the developers, product

managing persons and customers find it difficult to maintain which bug is fixed and

in which release it is located.

1.12 Significance of the Study

The research improved our understanding of how to create and maintain

systems. In an effort to understand user needs, it also improved our social

conduct through social engagement with system users. The system guarantees

data consistency, simple record generation, storage, and retrieval, all of which

contribute to data security. By reducing paperwork and time, the technology

also lowers administrative expenditures. The paper could serve as a starting

point for more study to help close the knowledge gap and provide better

information.

5|P a g e
1.13 0peration definition of terms

Bug- This is an unexpected problem with a software or hardware.

Tracking system- this is a software that is installed in a system or software to give

information about it or its status.

CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction

A tracking system is used to determine the location or direction of a target on an

almost continuous basis or routine.In our case a bug tracking system is going to be

6|P a g e
used to track down and keep record of bugs in a software development process.

Developers, managers and testers deploy this tool to help in reposing their

development, managing and testing processes simultaneously (Hazratifard et al.).

Allows bugs to be tracked down, recorded and to be solved.

2.2 Related literature review

1] GITHUB

Github is a repository hosting service and can be used for collaboration and project

management. Developers also use it as a bug tracking software as it offers github issues. It

has a color coded label that aids in issue categorization. Github allows the use of mentions

and references inside issues in order to notify other team members about any need (Ma et

al. 2020).Github Issues bug tracking system is a flexible and powerful tool but also has some

restrictions which must not be exceeded.

I. Allows no sub tasks.

II. Allows no room for custom work flows and automation.

III. If you manage many tasks , it is hard to navigate through them.

IV.

2] MONDAY

Monday is bug tracking tool that enables developers and testers to analyze your

performance and manage your team in one place.Availability of a flexible dashboard

enables visualization of data.

Its features include;

7|P a g e
I. Allows collaboration with other people.

II. Allows you to work remotely.

III. Allows exportation of files in PDF, PNG, JPEG, CSV and SVG formats.

IV. It supports windows, mac, iOS , Android and linux.

Its cons include;

i. The minimum size for paid plans is three people.

ii. The basic plan lacks sharing functionality.

iii. Addition of tasks is a process that can be challenging.

3] JIRA

ResJira provides teams with several real-time, Agile reports for bug

tracking.However, it lacks idea management features (“Information and Computation

| Journal | ScienceDirect.com by Elsevier”). Software developers need a creative

enviroment to develop new designs, software solutions and bug tracking plans. This

becomes a challenge due to the lack of idea management features.

Its features mainly include;

I. Agile views like scrum boards and Kanban boards.

II. Customizable dashboards.

III. Track milestones, launches and bugs.

Its limitations include;

i. The free planning is very limiting.

8|P a g e
ii. Sandbox functionality for testing codes is only available in the premium plan.

iii. Cant search issues easily without knowledge of Jira Query Language.

4] REDMINE

Redmine is a flexible open-source tool with Gantt charts, calender views and more.

This tool supports multiple projects and contains a built-in time tracker (Ma et al.

2019). It works by mining bugs from softwares thus the name Redmine.

Its key features include;

I. Create subtasks and assign them to key different members of the team.

II. Create issues and edit the subject.

III. Supports email notifications.

Limitations;

i. Not suitable for Agile issue tracking teams.

ii. Limited built-in fused with powerful project management tools.

iii. The user interface is not very intuitive.

5] ZOHO BUG TRACKER

Zoho bug tracker is a bug tracking tool that allows you create custom fields and work

flows and personalize your interface to catch any software bug (Del Mathew 2021).

Unfortunately it does not offer unlimited storage, making it complex for software

developers to store their bug data in the app.

9|P a g e
Key features;

I. It has custom work flows that help you submit and fix bugs with ease.

II. Allows developers to add comments with bug descriptions and attachments.

III. Allows for email notifications.

limitations;

i. Does not offer unlimited storage.

ii. Limited integration with non-Zoho apps.

iii. Can only access Kanban boards and lists when bug viewing.

2.3: Gaps

Bug tracking is a critical process In software development life cycle. But common

few problems may possibly lead to improper bug tracking.

A. Improper bug logging process; a bug should be properly described and be

explainable. Missing fields like incorrect defect tittle, missing expected result or

steps to reproduce increase the defect life cycle process.

10 | P a g e
B. Use of different bug tracking template; using a different issue tracking template

to report the issues which may lead to discrepancy in later stages. As a result of

this standard tracking and logging template should be used.

C. Improper set up of severity and priority; the importance and urgency of fixing a

defect should be prioritized if better results are to be accrued. But if wrong

instances are prioritized then the defect life cycle may take much time.

D. SPOC(Single Point of Contact); many of the times a single point of contact not

present in the team to talk about defects to the stakeholders.

2.4 Conceptual framework

The presence of a lot of user feedback and assistance during the development and

deployment of information systems is beneficial. It is advantageous to involve users

in the development and management of information systems. Developers and testers

are heavily involved in the development of information systems, and they have more

control over the results. Because of their involvement in the creation of the system,

developers and testers are more likely to embrace the transition process. It has been

11 | P a g e
difficult to set up tracking systems due to the cooperation between developers,

testers, and corporations. They come from various backgrounds and possess unique

priorities, resulting in miscommunication. When bug tracking systems are

implemented, specialists from all kinds of organizations must communicate.

Divergent organisational loyalties, problem-solving techniques, and lexicons, to

name a few, can be the result of this.

Fig: conceptual framework

2.6 Conclusion

An efficient bug tracking system will help you to manage your software development

process with ease. It should have the capability to track, monitor, and report on every

bug or issue reported by your users in a single system. A good bug tracking system

should be easy to use, have a user-friendly interface, and provide quick assistance to

the users. It should also have the ability to create workflows and assign tasks to team

12 | P a g e
members. The best bug tracking system will be one that supports different operating

systems, has a responsive and robust system for better performance, and provides an

option for customization.

CHAPTER 3

RESEARCH METHODOLOGY

3.1 Introduction

This chapter will concentrate on the methods and equipment that we

employed to complete the investigation. The chapter will include the analysis

13 | P a g e
 of existing systems, which will include information on system requirements,

procedures, limitations, and system design tools.

3.2 Development methodology

These are some of the key activities that form the foundation of the SDLC model. In

the diagram below, you can see the V model where there are development stages

where the code is being written and tested. After the testing is complete, it is verified

and validated. This is one way of executing the V model. There is another way of

doing it. Testing may start even before the development starts. This is known as

ATDD (Acceptance Testing Driven Development). ATDD is more like TDD but the

focus is more on the acceptance criteria rather than testing the code.

Acceptance Test Design

Acceptance Testi
Requirement
Analysis

System Test Design System Verification

System Design

Architecture Integration Test Design Integration Testing

Design
14 | P a g e Unit Test Design
Module Design
 Unit testing

Coding

Requirement Analysis:It also involves gathering data to understand the customer

needs, which can be done through surveys, one-on-one meetings, phone calls, etc. It is

critical for the success of the project that both parties have a good understanding of

what is needed. There are many ways to collect data to understand customer needs.

The most important thing is to select the best way to communicate with customers

that works for your specific situation. Communication is key for a successful project,

but the most important thing is to make sure everyone involved in the process is on

the same page and has a clear understanding of the goals of the project.

15 | P a g e
 System Design:It also involves gathering data to understand the customer needs,

which can be done through surveys, one-on-one meetings, phone calls, etc. It is

critical for the success of the project that both parties have a good understanding of

what is needed. There are many ways to collect data to understand customer needs.

The most important thing is to select the best way to communicate with customers

that works for your specific situation. Communication is key for a successful project,

but the most important thing is to make sure everyone involved in the process is on

the same page and has a clear understanding of the goals of the project.

Architecture Design:It is designed keeping the beginner users in mind - anyone can

pick up this course and start learning blockchain with no prior knowledge required.

The course is divided into different sections with each section building on the

previous one. Each section is further divided into different sub topics and each sub

topic has a lecture and a corresponding exercise that has to be solved. To solve these

exercises, you only need a computer with an internet connection. After every 3-4 sub

topics, there will be a quiz to test your knowledge. At the end of the course, you will

be given a certificate.

Module Design: System broken down into small modules.

Testing Phase

Unit Testing: Unit test plan are developed during module design phase and are

executed to eliminate bugs at codes.

Integration testing: The modules are integrated and the system is tested.

System Testing: It is designed keeping the beginner users in mind - anyone can pick

up this course and start learning blockchain with no prior knowledge required. The

course is divided into different sections with each section building on the previous

16 | P a g e
one. Each section is further divided into different sub topics and each sub topic has a

lecture and a corresponding exercise that has to be solved. To solve these exercises,

you only need a computer with an internet connection. After every 3-4 sub topics,

there will be a quiz to test your knowledge. At the end of the course, you will be given

a certificate.

User Acceptance: Verifies the delivered system if it meets the requirements.

3.2.1: Strengths of the model

Phases are finished one at a time under this model, which requires extreme discipline.

It is intended for small projects with clearly defined criteria.

It is Proactive defect tracking, which means that errors are discovered at an early

stage.basic, understandable, and easy to use.

Testing activities like test design and planning take place long before coding.

3.2.2: Weakness of the model

i. High risk of uncertainty.

ii. It is not good for complex and object –oriented projects.

iii. Not suitable for projects where requirements are not clear and contains high

risk of changing.

3.3 Justification of methodology

I used the V model because of the following reasons:

17 | P a g e
 1) It is simple to use and understand

2) It has clearly defined development stages

3) It is well and easily manageable because it is rigid.

4) It works very well in projects where all the requirements are well

documented and understood.

3.4 Data collection

This are methods in which I used to access and gather information from my

participants that helped in developing the system. The following methods was used:

3.4.1.1: Use of questionnaires

This is a set of printed questions that are set for the purpose of the research. It was

used to assess the parents, administration and student’s perception of the online web

portal and give their corrections and suggestions.

Why use of questionnaires

i. Respondents provide information which can be easily converted into

quantitative data

ii. Questions are standardized

iii. It is a cost-effective method

18 | P a g e
 iv. It is a speedy way getting results.

3.4.1.2: Interviews

I held a face to face interview with some customers to get their views about the

system and also to see their reactions as they respond.

Why use of interviews

i. Easy correction of any misunderstanding and mistakes

ii. Development of relationship

iii. Collect fresh new and primary information

iv. It is time saving

3.4.2: SECONDARY COLLECTION METHODS

Studying of available documents: I got some information from existing reports of

some previous work that had been done to gather more information about the system

and the information that was useful in the development of the system.

3.5 Data analysis

19 | P a g e
3.6 CONCLUSION

According to the report from Jira tracking software as shown on the figure above, the trends

of bugs reported in softwares is significantly reducing as a result of bug tracking systems.

Therefore this bug tracking system has great expectations in the process combating bugs or

defects in software development process. As a result there is cost minimization because

there is minimized occurrence of bugs in the future which purpotedly were to take some

extra costs in order to overcome them.

3.7 REFERENCES

20 | P a g e
Hazratifard, Mehdi, et al. “Using Machine Learning for Dynamic Authentication in

Telehealth: A Tutorial.” Sensors, vol. 22, no. 19, 9 Oct. 2022, p. 7655,

10.3390/s22197655. Accessed 17 Nov. 2022.

“Information and Computation | Journal | ScienceDirect.com by Elsevier.”

Www.sciencedirect.com, www.sciencedirect.com/journal/information-and-

computation. Accessed 21 Nov. 2022.

Ma, Chun-Guang, et al. “Security Flaws in Two Improved Remote User

Authentication Schemes Using Smart Cards.” International Journal of

Communication Systems, vol. 27, no. 10, 7 Nov. 2012, pp. 2215–2227,

10.1002/dac.2468. Accessed 28 Feb. 2020.

3.8 Appendices

Appendix A

21 | P a g e
Questionnaire Guide for Knowledge Acquisition

1. Are there any issues with the current system?

Yes No

2. Does the current system enable you to perform your task?

Yes No Not all

3. Will you recommend the current system to your friends?

Yes NO NOT SURE

4. What’s the level of satisfaction with the current system?

Excellent very good Poor

5. How long has the system been in

operation………………………………………………………………………

……

6. What are the major and specific services the system

offers?..................................................................................................................

7. What would you like the new system to

do?......................................................................................................................

Appendix B: Budget

Serial Description Quantity Unit Price Total Price

22 | P a g e
number

1 Laptop 1 40,000/= 40,000/=

2 Flash disk 1 800/= 800/=

3 Internet fiber 1 700/= 700/=

4 Data bundle subscription 4 200/= 800/=

5 Software services 1 500/= 500/=

6 Printing documentation 800/= 800/=

TOTALS 43,600/=

Appendix C: Work plan

Activity Months

Background of the study and September

problem identification

Literature review October

Research methodology October

Presentation November

23 | P a g e
24 | P a g e
25 | P a g e