Research On Software Defect Management And Auxiliary Tools Realization

Software testing as an important part of software development is receiving more and more attention. Enforcing the organization and management of software testing is of great significance. After much effort of software experts, software testing theories are becoming more and more mature. The techniques, methods and tools of software testing are also developed. However, there is little research into the management of defects discovered in software testing. This thesis is a study on the management of software defects and it designed an auxiliary tool for defect management, which could be put into application by middle-sized and small software corporation. In the first place, the thesis defines what software defects are, its classification and its features. It points out the possible causes for the occurrence of defects and the ways to avoid defects. In addition, the thesis analyzes the correlation between software defects and software reliability, according to specific formulas. Following this, the thesis makes a systematic investigation into the procedure of management of software defects. It expounds the goal of defect management, the procedure of software management and the distribution of roles in defect management. It also elaborates on the important factor for defect management from the aspects of the collection of defect information and analysis of defect information. In addition, from the perspective of CMM, it argues how software organizations of different maturity manage the defects in their software. It points out the relation between the defect management and the capability maturity model for software. It further explores into the importance of introducing defect management system for a corporation. And it introduces and compares several typical defect management tools. Based on the above research, the author designs a model system of defect management for middle-sized and small corporations. It could help software corporations to regulate the electronic procedure of development, testing and defect management in program development. It could assign a specific task to the person who is responsible for the problem and tell them what is significant and what is urgent. According to the analysis of record of defect history, it could trace the shortcomings and find out the key points for improvement, which could serve as the reference data for evaluation of effects. The system is composed of six modes: defect tracking module; attachment management module; defect statistics module; system management module; report output module; automatic mails notice module. The features of the system are as follows. The software based on B/S structure guarantees that persons concerned could communicate with each other without being restricted by time and place, which can enhance communication and cooperation, accelerate the information transmission and the course of dealing with the defects. The system regulates the users according to their different roles. It offers three basic roles: the system administrator, advanced user and ordinary user. Each of the three roles has their own rights. The system administrator is responsible for all the projects in the system: management of users'basic information; allocation of test resources; configuration of E-mail notification; deletion the defect records of the database. Ordinary users refer to the products / general members in the project group. Typical ground, every developer, tester are ordinary users. Ordinary user is responsible for dealing with the defects: testers report the software defects and verify the results of the correction and close the recovered defect. The developers are to revise the software defects and fill in the revision record. Advanced user is to help the management personnel, such as project manager, corporation manager, etc, to know the software the corporation is developing at present. Their tasks are to supervise the testing process of the project. They have the right to analyze the defect status and produce the statistical report of the defects. They are alsoresponsible for the allocation of staff to revise the defects. The system adopts an action-driven switch of the states. Users could not revise the defect states directly; only the system action could changes the defect states. The system provides different actions to different roles, which could ensure the explicit allocation of work in the process of the testing. The system could record the defect history. The defect system is the history of the changes of defect stages in its cycle of life. The system gives a detailed record of each of the changes of defect stages, which could help users to know the process of the changes of the defect states. This system supports automatic E-mail notification.When the state of defects changes, the system automatically sends out the latest dynamic information, helping testers and developers to communicate with each other. In this way, it could guarantee that users could receive information of state changes of defects. The system has the function of statistic analysis. It gives a statistical analysis of the state of the module, the tendency of the defect development; the state of the project according to the defect information the system receives. The results of the analysis could be shown in the form of bar chart and broken line picture. Hence, the users could know the total state of the project as well as the specific details of the project. The system could produce the defect information in the form of Word, Excel, and PDF and so on. The users could set the defect field of the Report. They could also classify the field and put them in ascending and descending order, which will help the development organization copy the defect information. The system also has the function of dynamic search. When users are selecting the condition for the search, the system automatically produces standard SQL sentence and exposes it to the users in simple forms. After the confirmation of the users, it will disclose the defect information. Thus, it decreases the frequent interaction between the users and the system and raises...