Sie sind auf Seite 1von 5

Bug Tracking System

ABSTRACT The system deals with providing online support to the people who are facing problems with various software technologies. Problems with the current system there is a communication gap between the customer and the organizations. People generally dont know the name of the sites of all Organizations to post their problem. Customer usually face some problem while posting the bugs occurred in different software as they have to post their bugs to different sites individually there is no surety of quick response from the organization .Few organizations may not be interested in responding to the customer problems .So in order to overcome all these limitations and to meet all their requirements , the current process is replaced with this application. he proposed system will provide facilities for !"#$%$S &! O&, #!%!'(&, (C)%$C!* +(&SO% and

C,S O#(&. !dministrator can update the details of anyone on their demand. #anager can view the bugs posted by the customers. #anager checks the status of his technical persons and finally observe the feedback of the customers. echnical person can view the bugs assigned to him by his manager. )e provides a suitable solution for the specific bug. )e has to also update the present status of the bug Customer ports the bugs to the manager. Customer can view the solution to his bugs - thereafter can send a feedback for his solution INTRODUCTION The objective of the proposed system is to build that provides the facility to the customer to post their bugs occurred in the various softwares usage. The system should keep track of bugs and within no time, the customer should get the solution for his problem. The proposed system should provide the facilities for the following modules. Administrator Module Manager Module Technical Person Module Customer Module Only the authorized persons can login to their respective modules using their username and password. In administrator module, once an administrator logs on to the system he/she can register the managers, technical persons and products.

The Administrator can update the details of anyone on their demand. He analyzes the performance of each individual staff. In customer module, once a customer logs on to the system, he can post a bug to the manager. The customer can view the solution to the bug posted by him. Thereafter the customer can send a feedback for his solution. They can edit their personnel details. In manager module, when manager logs on to the system, he can view the bugs posted by the customers. The manager can then assign the bug to the available technical person. He can view the status of the technical persons timely. In technical person module, when technical person logon to the system he can view the bugs assigned to him by his manager. He can then provide a suitable solution for the specific bug along with the priority. He can update the present status of the bug. CURRENT SYSTEM Now a days, almost everyone is using computers. Some people use it for writing letters, sending mails etc. Few people use it for developing applications and few people use it for entertainment purpose. Like this computers are useful for almost everyone in something or the other way. When people are working with computers, they may or may not be aware of computers and more importantly when they are using the software products of different vendors, they may face some problems. If such is the case, the users may not get a proper solution immediately and sometimes it would also take a very long time to get a solution for his/her problem. For getting proper solutions, the users have to contact the concerned organization that has provided the software and tell their problem. The concerned organization will then provide a solution for his/her problem within a period of time. Problems with the Current System There is a communication gap between the customer and organizations. People generally dont know the sites of all the organizations to post their bugs. Customer face problem while posting their bugs occurred in different software As they have to post their bugs to different sites individually. There is no surety of quick response from the organization. Few organizations may not be interested in responding to the customers. So in order to overcome all these limitations and to meet all their requirements the replaced with this application. PROPOSED SYSTEM Produ t !un tion O"er"iew# current process is

This product interacts with mainly three entities i.e. Customer, Manager and User Ch$r$ teristi s#

Technical person.

The main user of the system is the Manager, even though the Administrator uses it, he will have less interaction when compared to manager. So to use the system, the manager should have the knowledge of the following topics: 1. 2. The manager should have working knowledge on computers. The manager should know how to use an operating system for running applications.

Administr$tion Module The system should accept the following as input from Administration of organization for successful login. 1. Valid username 2. Password After successful login, the administrator is provided is provided with the following options, which require some data entry To add a new Product. To add a new Manager. To add a new Technical person under Manager. To view Reports. The administrator has to register the details of products, managers and technical persons. For every product there will be a concerned manager who will take care of posting the problem to the concerned technical person. M$n$%er Re%istr$tion& This takes the following as Input M$n$%er Usern$me ' P$ssword ' M$n$%er N$me ' Address ' Phone ' Em$il After submitting all the details, a unique ID is generated to uniquely identify that particular manager. Te hni $l Person Re%istr$tion& This takes the following as Input Te hni $l Usern$me ' P$ssword ' Te hni $l (erson N$me ' Address ' Phone ' Em$il ' M$n$%er&id ' St$tus After submitting all the details, a unique ID is generated to uniquely identify that particular technical person. Produ t Re%istr$tion& This takes the following as Input Produ t n$me ' )ersion ' )endor n$me ' M$n$%er&id After submitting all the details, ID will be generated which is given to the products. Customer Module Customer Login- This module takes the following details as Input

Customer name Password It validates all the above fields and if the input given is valid then the customer is allowed to enter to its main page. Postin% o* Bu%s - This module takes the following from customer as Input. Customer id Software list Assigned Priority Details File name Product id Summary OS Using Post date Severity

After submitting all the details, ID will be generated which is given to the bugs. M$n$%er Module M$n$%er +o%in& This module takes the following details as Input Manager username Password It validates all the above fields and if the input given is valid then the manager is allowed to enter to his home page. Assi%nin% Bu%s to te hni $l (erson- this module takes the input. I Bug ID Expected date Technical person ID Solved Assignment date

After submitting all the details, a unique ID will be generated which is given to the assignments. Te hni $l (erson Module Te hni $l (erson +o%in&This module takes the details as Input Username Password It system validates all the above fields and if the input given is valid ones then the manager are allowed to enter to its home page. ,ritin% solutions - This module takes the following input. Bug ID Date Technical person ID Priority Solution description

After submitting all the details, ID will be generated which is given to the solutions-

Software Environment Operating System Front End Tool Scripting language RDBMS Application Server - Microsoft Windows 2000/XP - Servlets and Java Server Pages - HTML, JavaScript - Oracle 8i - Apache Tomcat Web Server

Hardware Environment
RAM Hard Disk Processor Floppy Disk Monitor Mouse Keyboard - 64 MB - 20 GB - Intel Pentium 500MHz - 1.44 MB - Color Monitor (256 colors) -3 button scroll mouse -Multimedia Keyboard

Das könnte Ihnen auch gefallen