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 PROPOSED SYSTEM DESCRIPTION BUG TRACKING SYSTEM is a basic, yet fully functional web based error or Bug Tracking system that the organization’s may use as a framework to create an expanded system or use 'as is'. It is beneficial for small teams working on software projects or manufacturing processes. All businesses have issues that need to be tracked and managed to resolution. In software and hardware development, for example, issues such as defects or bugs and enhancement requests need to be tracked and managed. Resolution of these issues requires the coordination of multiple individuals within and perhaps even outside the company. The proposed Defect Tracker can be used by all team members to coordinate their work, and to make sure that reported bugs and enhancement requests won't be forgotten and handled effectively and efficiently. A company can use the defect Tracking system to enable its QA Engineers, Development Engineers, Customer Support to report bugs; and Marketing, Product Managers to file enhancement requests. The built-in workflow of the proposed system would automatically route these issues (bugs and enhancement requests) to the appropriate engineers to get them implemented, and to the QA Engineers for testing.
The engineers can make attachments to the bug records and associate bug records to the files in the source code control system. Meanwhile, Managers can obtain status, reports, charts and graphs showing trends and problem areas. Issues that are not taken care of in time will automatically be escalated. Everyone involved can obtain status, automatic notification, reports, and charts and graphs; and share knowledge and information. Their clients and partners can report problems directly, and obtain status, notification, etc. in a “self-service” manner. The proposed system will thus delivers up-to-the-minute project information and status to team members everywhere to foster better communication and collaboration, and automatically manages these issues to resolution. As a result, it increases productivity, improves the quality of products, and increases customer satisfactions. The proposed system will have to analyze the business requirements as follows: BUSINESS REQUIREMENTS What business requirements will be needed for this tool to meet? That is, how is it going to support the organization in the manufacturing or software development effort? It has to deal with Project management and metrics Security Administration PROPOSED SYSTEM FEATURES • Developers can work entirely within the system, without having to switch to the defect tracker and re-enter data. • Managers gain control by enforcing the defect tracker's workflow in Perforce. • Provides traceability between defects and changes. • Allows reporting of defects fixed in codelines and releases. • Makes work completed and work in progress visible from the defect tracker. • Log and classify each incident by Call Type, Severity, Priority and other attributes. You can classify incidents any way you like. Each field is fully configurable and you can classify incidents any way you like. • Record an overview of the incident or the full details including error messages and the surrounding circumstances. You can also attach external files such as faxes, log files and screen dumps to each incident. • Record any number of responses to an incident as the incident progresses to some end-status. Instantly review the history of responses to a selected incident. • Record release notes for an incident. Relevant release notes can be extracted and printed when a new version of your product is released.
• Allocate a call to a user or a group of users. Use the Job Queue to quickly view who is working on what and easily reassign calls. • Estimate the time and amount spent for each incident and let the proposed Defect Tracking calculate the actual time and amount spent. Track the total cost and time spent to resolve a problem. • Use work flow to automatically reassign a call when the status changes from one state to another. Work flow is fully configurable based on call type. • Track how a call will impact on other areas and schedule tasks to be performed before work commences on a call or after it is resolved. • Track parts used to resolve an incident and the total cost of parts used. • Link common incidents together. • Attach unlimited number of files to each incident. • Use Job Activities to show total number of new, open, closed and escalated incidents and also total number of responses for a given date range. PROPOSED SYSTEM MODULES 1. SERVER AND ADMINISTRATION MODULE a. Login Authentication b. Administration module 1. Administration by Users, Administration of Priorities 2. Administration of Projects, Administration of Statuses c. Tracking -- Tracking reported bugs, defects, business issues, enhancement requests, etc. d. Workflow -- Automatic routing and notification to get issues resolved. e. Process enforcement -- Managing and enforcing your company's process of resolving issues. f. Status -- Up-to-the-minute project information and status to team members everywhere to foster collaboration. 2. AUTOMATIC NOTIFICATION Automatically notify clients and internal users of any changes. With automatic notification, nothing falls through the cracks. We can also customize the message being sent by inserting system directives, fields from the database and any free form text. This allows our system to create a more personalize message for each notification type. Two levels of notifications are provided; record level and field level notifications. • With record level notification, the system can define the appropriate clients and user to notify when a new incident is added, edited, copied or deleted. The notification is based on changes to a record.
• With field level notification, the system defines the appropriate clients and users to notify when a field is changed or when a field equals a defined value. The notification is based on changes to a field on a record. • For example, we can automatically notify the QA team or client when the status of an incident is Resolved or notify the user whom you allocated the incident to for resolution. 3. CLIENT MANAGEMENT MODULE The system can create unlimited number of contacts for each client. Stores all the client details in one central location. • Easily generates phone list, mailing list, e-mail list, contact list and any other list from your client database. Record client feedback. Record products purchased by clients. a. Search by Project, Assigned Person, Priority, Status b. Sorting by any of the columns (Bug Name, Project, Priority, Assigned Person, Status) c. Job assigned d. Verification of issues quoted 4. UTILITY MODULE a. Communication -- Capturing discussions and sharing knowledge. b. Accountability -- History and audit trail. c. Chat interaction d. Mail service e. Broadcast messenger f. Queue defects 5. KNOWLEDGE BASE CREATOR Full searchable knowledge base with resolution histories. The system can automatically create a knowledge base from the incident records you added. Over a period of time, the system can built up a knowledge base of common problems and also a resolution history. Resolve incidents quickly using the fully searchable knowledge base with resolution histories. Draw on the knowledge of all team members. 6. MANAGEMENT REPORTS GENERATOR
No comments:
Post a Comment