As the saying goes, “TO ERR IS HUMAN”. But rectifying the errors is one’s significant duty irrespective of whether it is a single individual or an organization. In different perspectives or situations, we need a defect free system. Generally for the smooth functioning of an organization, there should be a verification system for the processes undergoing in any organization.
If an individual would have been nominated by their manager or his/her team to select a defect tracking system for his/her organization, then there would be a question of as to – “Where do they begin? Of course, the concerned employee would be expected to conduct the relevant research while carrying out their regular responsibilities.
Hence there is a need to come up with a quick strategy that enables the entire organization involving all parties involved to objectively evaluate various options and select a system in a timely manner. We define generally a Bug tracking tool as a powerful, easy-to-use Web-based collaboration tool to help companies’ track business issues and automatically manage them through to resolution. The particular organization need to make sure that the tool, which we develop has to track the defects the organization’s selects, is the best fit for the organization—a tool that offers the features that we need, a reasonable response time at normal and even large load levels, a price that’s within the specified budget of the organization, and integration with the existing systems of the organization.
It’s not a casual decision, because you know that once the tool is deployed it will be difficult and costly to change. If you are doing this for the first time, it’s a challenge to know where to begin and what to look for in an effective defect tracking and management solution. If you have done this before, you may find that several new commercially available defect tracking solutions offer many advanced feature sets. The most important step in any organization’s process is defining the business and technical requirements of the system. Identifying these requirements allows them to generate a features list, which in turn will help the organization to evaluate and trim down the list of tool options.
In addition, the proposed system, has a built-in defect tracking system which, allows actions performed by the users to automatically send their requests the defect tracking system. Conversely, the users can convert issues and status entered into the respective defect tracking system automatically to metadata for easy access. In this proposed project we would deal with all the steps toward the selection of the most appropriate solution for the respective company. This process should deal
with the examination of our organization’s business and technical requirements for the tool.
PROPOSED SYSTEM OBJECTIVE
The proposed system’s fundamental objective or the main objective of a Bug tracking solution is to track every identified issue so that valid defects that affect customer satisfaction, business financial success, and reputation can be fixed in a timely manner.
PROPOSED SYSTEM SOFTWARE REQUIREMENTS
- Server: Windows 2000 / XP
- Client: Windows Client
- Software: ASP .NET
- Protocol: TCP/IP Protocol
- Database: Oracle 8i
- Web Server : JWS
- Network Interface
PROPOSED SYSTEM HARDWARE REQUIREMENTS
PIV, 512 MB RAM, 80 GB HDD, Color Monitor