BUG TRACKING SYSTEM Abstract

:
A bug tracking system is a software application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. 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 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 software project management applications. Having a bug tracking system is extremely valuable in software development, and they are used extensively by companies developing software products. 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 behavior, and details 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 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 status 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.

all users will have the details such as :  Bug id  Bud name  Project that the bug belonged to  Status of the bug  The person who assigned the bug  The person for whom the bug is assigned  Date of the bug assigned  Attachment for the reference of the bug The user can able to delete or can mark it as ‘checked bug’ by selecting the appropriate bug All users will be having searching criteria in their home page. The searching criteria will be done according to:      Project Bug assigned by the person Bug assigned to the person Status of the bug Priority of the bug .MODULES The modules involved in our project are: • Login • Project Maintenance • Employee Maintenance • Bug Maintenance • Task Management • Status Model • Priority • My Account LOGIN: The users like Tester. Administrator and Developer will enter into our project with their user name and password. When login.

administrator and developer  Username of the employee. BUG MAINTENANCE: Bug maintenance is done by the module add bug.  Projects assigned to the employees. Administrator and tester have the authority to add a bug. The project details are:  Project name  Project description  Developers assigned to the project  Start date of the project The developers can view the details of the project they need to work on.PROJECT MAINTENANCE: Project details are maintained by the administrator. we are providing high security options EMPLOYEE MAINTENANCE: All the employee details are viewed only by the administrator The details of the employee are:  Name of the employee  Email id of the employee  Category of the employee such as tester. An employee can involve in any modules of different projects. It should be unique  Password. None can view the details of the project that they not involved in. The bug details are:  Bug name . the username is used for the login purpose of the employee. Thus we have to keep the details of the projects assigned to that particular employee.

MY ACCOUNT: . image. Administrator can include any type of new status according to the flexibility of the bug flow. or snapshot. STATUS MODEL: It consists of type of status for the bug. where the bug belongs to  Name of the person who assigned the bug  Name of the developer who assigned for fixing the bug  Priority of the bug  Status of the bug  Assigned date for the bug  Attachments. priorities and statuses. closed. It will give the clear view about the bug. low. in progress. priorities and statuses. lowest and normal. PRIORITY: It consists of type of priority for the bug. No other users are allowed to be in this module. project. The priority may be high. TASK MANAGEMENT: Task management is done by administrator. hold. fixed. It consists of all details about the employee details. Administrator can add or edit or delete the details of the employee. It is assigned by the administrator. The statuses may be open. It may be of type word. project details. It is assigned by the administrator. medium. we can include a file to refer the bug. Administrator can include any type of priorities according to the flexibility of the bug flow. Bug description  Name of the project.

co m gopi@gmail. All users are provided with a option of changing their password in this module.This module consists of the personal details of the specific user.co m vivek@gmail.co m Category developer developer admin Assigned project Catalog system Library management PROJECT TABLE: Name Software quality management Library management Payroll system Catalog system Description decs1 decs2 decs3 decs4 Assigned developer kannan gopi kannan bala Start date 17/3/2009 5/6/2010 11/11/2010 16/10/2010 . TABLES Tables involved in our project are:  Employee Table  Project table  Bug table  Priority table  Status Table EMPLOYEE TABLE : Name Bala GopiKrishnan Vivek Username bala gopi vivek Id bala@gmail.

BUG TABLE: Name logical bug Project payroll system Database connection failure Operating system failure catalog system library manageme nt system bala high 7/8/2010 snapshots gopi high 12/11/2010 snapshots Developer assigned kannan Priority medium Assign date 12/12/2010 Attachments snapshots Priority table Priority name Low Medium High Lowest Normal Assigned by Admin Tester Admin Admin Admin Status Table: Status name Open Fixed Closed Inprogress Assigned by Admin Admin Admin Tester .

SharePoint Portal Services. infrastructure services and IT services. The company products are • • • • • Multiply e-VID Learning Management Solutions Material Management Packages Agri-Informatics Solutions . ITES Services. Seo Services. USA. Mobile Application Development. Data integration & Warehouse. The company services are financial solutions. support. Web Development & design. BI Report & Data Transformation. maintenance. Email & Mobile marketing services. It posses over a decade of hands on experience in varied domains such as Software Applications development.Hold Not a bug Tester Admin COMPANY PROFILE Binarch infosolutions is a global IT business solutions and services provider headquartered in New Jersey.

defect metrics and testing metrics also help in evaluating the success ratio of a tester or programmer. also known as metrics help the QA test management team to assess the quality of the software and in taking business decisions. A Bug tracking system not only tracks defects but also tracks metrics to make sure everything is going according to the software development plan A bug-tracking system helps the project team to successfully measure the project’s status. HARDWARE / SOFTWARE REQUIREMENT . a paper-based approach can result in chaos and confusion. bug reporting is a complex and complicated process that requires precision.Proposed System: In software test management. whereas for mission-critical or large projects. Reporting and tracking bugs manually works fine in case of small projects. The measurements. detailing and a whole lot of information. The software metrics like project metrics. A bug-tracking system helps the project team to successfully measure the project’s status. progress metrics. QA test management teams need an effective defect tracking management system to log the identified bugs and to monitor them.

Net : SQL SERVER 2005 : INTEL : 480 MB .Hardware Requirement PROCESSOR RAM Software Requirement FRONTEND BACKEND : C#.