Project Report

on

BUG MONITORING SYSTEM

by
(Name of the student1)
Admn No: MCA90
&
(Name of the student2)
Admn No: MCA90

Under the guidance of

Internal Guide
Mr. (Teachers Name).
Teacher, Dept. of Computer Science,

St. Xaviers School

Hazaribagh 825301

SYMBOL OF YOUR SCHOOL

ST. XAVIERS SCHOOL

Hazaribagh 825301
2011-12

Project Report
on

BUG MONITORING SYSTEM

by
(Name of the student)
Admn No: MCA90
Under the guidance of
Internal Guide
Mr. (Teachers Name).
Teacher, Dept. of Computer Science,

St. Xaviers School

Hazaribagh 825301

SYMBOL OF YOUR SCHOOL

ST. XAVIERS SCHOOL

Hazaribagh 825301
2011-12
Sign of External

Sign of Internal

ACKNOWLEDGEMENT
I express my sincere thanks and indebtedness to my esteemed institution, St. Xaviers
School, Hazaribag which has provided me with an opportunity to fulfill my desire and reach my
goal.
I would like to express my sincere gratitude and deep debt to Mr. (Teachers Name)
(Project Guide) for their invaluable suggestions, meticulous guidance and constant support which
have gone a long way in the successful completion of the project.
I thank in a very special way our beloved principal Fr. P.J.James for having inspired me by
his dynamic personality and creating the right academic environment that made my task appreciable.
On a moral personal note, my deepest appreciation and gratitude to my beloved parents, who
have been a fountain of inspiration and have provided unrelenting encouragement and support.
The project would never have been a success, if not for the blessing from the Almighty, my
guiding light and strength.
I heartily thank all those who have helped me directly or indirectly in the successful
completion of this project.

(Name of the
Student)DECLARATION

I declare that this project entitled (Project title) done at St. Xaviers School, Hazaribag
is a record of project work submitted by me for the partial fulfillment of the 10+2 of CBSE under
the supervision and guidance of (Teachers Name).
The Project is genuine and not a reproduction of any project previously done or submitted.

(Students Name)
(Admn No.)

CONTENTS
Sl. No.
1.
2.
3.
4.
5.
6.
7.

Particulars
Introduction to the project
Hardware & Software requirement
I.
Hardware Requirements
II.
Software Requirements
Modules Description
Future enhancements
Conclusion
Screen Shots
Bibliography

Page
No.
3
10
11
11
12
43
45
46
58

1. INTRODUCTION OF THE PROJECT:

Bug monitoring is the process of reporting and tracking the progress of bugs from discovery through
to resolution, where a bug is defined as a deviation from requirements.
Bug monitoring systems are most commonly used in the coding and testing phases of the software
development process. However, tracking systems can in fact be used for many other purposes such
as general issue tracking, simple task lists, help desk situations or contact management, where the
focus is on the tracking aspect rather than what is being tracked. Even in software development,
tracking systems are quite often not limited to simply tracking bugs, but extended to track feature
requests or enhancements as well as enquiries.
The project entitled BUG MONITORING SYSTEM is to develop a software product for i-SIT for
easy handling, to give information to Administrator about customers problems, details for all
products, customer & employee details, etc.
The various call details such as problem, status, and data recovery from problem are handled in this
system. There are two types of action performed by the software:

Using this software, company can provide solution to the customer for different kind of
software failure, But before providing solution they have to check whether the customer is
valid or not.

Using this software, company can keep track of all records of the firm. These records include
customers details, employee details, product details, bug reports, repair records.etc.

The project is mainly divided into two modules:

1. Administrator:The administrator activates are done through the administrator part like customer
and employee details, assigning technicians, product details, maintaining all records,etc.
2. User:User will find the solution for the s/w problems and maintains all records regarding s/w
solutions.The project BUG MONITORING SYSTEM is well developed with ASP.Net for the
server side programming. The reason for that Asp .Net is one of the most existing new technologies.

2. HARDWARE AND SOFTWARE REQUIRMENTS

2.1 Hardware requirements:
Processor

Pentium 4

Memory size

512 MB or above

Storage

10 GB

2.2 Software requirements:

Operating System

Windows XP or above

Browsers

Internet Explorer 6.0

Application Technology

ASP.Net

Language

C#.Net

Database

SQL Server 2005

3.

MODULES DESCRIPTION
Admin module:
The Objective of this module is to

User Management
Project Management
Module Management

Reporting Bugs

Administrator:
The administrator enters with a high security and gives permissions to the new user to enter, and
keeps track of all bugs submitted, assigns projects to users, allots the priorities and status. He has the
authority to edit all the above functions. No user can enter the administrator side.
User Management:
This module provide to admin, add a new user information to database, modify the existing user
information and also its provided admin can see, update ,delete the existing user details.
Project Management:
This module provide to admin, add a new project information to database, add project allocate to
users and also its provided admin can update ,delete the project related details.
Module Allocation /Reallocation:
This module divided into two categories, one is add, delete, and modify the module information
under particular project. And another is Module Allocation, that admin can assign or reassign the
particular module to appropriate users.
Bug Module:

Once you have logged into system, you can follow the Add New Bug link from the top navigation
bar to create new bug. If there is more than one project for which you can submit a bug, you will be
prompted to choose any one from Project list drop down menu.

4. FUTURE ENHANCEMENTS

Allows attaching files and screenshots to bugs. Screenshots that lets you take a screenshot,
annotate it, and post it as a bug with just a few clicks.

Create hyperlinks between related bugs, so that you can jump from one to the other directly.

Includes some starter bug statistic reports with pie charts and bar charts. Easy to create your
own reports if you know SQL.

Set permissions controlling who can view, report, and edit bugs by project.

No search option to search the information according to Bug Id.

5. CONCLUSION
Bug Monitoring System is a, web-based bug monitoring system development developed using
ASP.NET, C#, and Microsoft SQL Server. It is in daily use by hundreds (maybe thousands) of
development and support teams around the world. This is GUI based Application. Its offers all the
features needed to manage improvement, Bugs, and so on. It also provides project Team oriented
information, module oriented information, and further option which allow the users to simplify all
the stage of project development and maintains.
Bug Monitoring System is easy to install and learn how to use. When you first install it, it is very
simple and you can start using it right away. However, it offers you the ability to change its
configuration to handle your needs if they are more complex. This is platform independent
application.

6. SCREEN SHOTS:

Figure 11.1 Login Screen

DESCRIPTION: By using this page both Administrator and User enter into the system with their
valid login id and password.

Figure 11.2 Home page

DESCRIPTION: This home page appears when administrator login into the system. Using this
page administrator can use all modules and sub modules

Figure 11.3 Add new user page

DESCRIPTION: This page appears only when administrator login into the system. Using this page
administrator can create new user.

Figure 11.4 User management page

DESCRIPTION: This page appears only when administrator login into the system and it displays
detail information of all existing users. Using this page administrator can modify
and delete these userss information.

Figure 11.5 Project management page.

DESCRIPTION: This page appears only when administrator login into the system and it displays
detail information of all existing projects. Using this page administrator can
modify and delete the information of these projects.

Figure 11.6 Module management page.

DESCRIPTION: This page appears only when administrator login into the system and it displays
all existing projects in the drop down window. Using this page administrator can
assign the modules to the particular user.

Figure 11.7 Module management page.

DESCRIPTION: This page appears only when administrator login into the system and it displays
detail information of all modules for the selected project. Using this page
administrator can modify and delete the information of any module.

Figure 11.8 Module management page.

DESCRIPTION: This page appears only when administrator login into the system and it displays
detail information of all existing projects in the drop down window. Using this
page administrator can allocate module to the particular user.

Figure 11.9 Module management page.

DESCRIPTION: This page appears only when administrator login into the system and it displays
detail information of the status of allocated module.

Figure 11.10 Bug management page.

DESCRIPTION: This page appears only when administrator login into the system and it displays
detail information of all existing projects and modules in the drop down windows.
Using this page administrator can assign new bug id, category, content etc and
save it by specifying the path.

BIBLIOGRAPHY
1. Professional C# - 3rd Edition, 2005.
Simon Robinson, Christian Nagel, Karli Watson, Jay Glynn,
Morgan Skinner, Bill Evjen.
2. C# and the .Net Platform, Public Beta Edition, Dec 2005, Apress Inc.
Andrew Troelsen.
3. ASP.NET Unleashed, Second Edition,
Stephen Walther
4. www.dotnetspider.com
5. www.advancescripts.com/ASP_DOT_NET/