![]() Here are some practical points were defect management is concerned. This way of defect management is important in the continuous monitoring of product quality throughout the whole lifecycle of the product. The purpose of defect management is to provide information to improve the development process. The fact that a defect was found is the trigger to an improvement action with the purpose to prevent such errors from happening again. Theoretically, if a defect occurs, it should be found as quickly as possible and fixed immediately at the source. Agile, based on Lean, strives for zero defects. Also the purpose of defect management can be different. In an Agile environment, defects can be handled differently than in a Waterfall environment. The latter group of tools often has the advantage that the defects administration is integrated with testware management and plan and progress monitoring. There are various freeware or commercial tools available. Most tools also enable the creation of management reports and metrics. Defect management tools support the registration and handling of defects found during test activities. Ideally, the defects procedure is supported by a defect tool. Several parties, in different locations, can be involved in handling defects. This also makes it possible to detect overall trends, over and above test varieties.ĭefect management can be complex and voluminous. In a waterfall environment, this procedure can best be defined at master test plan level. For successfull defect management we need a working defect procedure as well A defect procedure facilitates the handling and managing of defects. These overviews are used, among other things, to make well-founded quality statements. Sometimes the procedure to handle defects depends on the severity of the defect.Ī good defect administration provides various overviews. This categorisation reflects the damage to the business operations, for example ‘Production-obstructive’ or ‘Cosmetic’. What makes a good defect administration? A good defect administration must be able to monitor the lifecycle of a defect and make clear who should make a decision or take action to get a defect in the next state. ![]() Each defect can also be the trigger for development process improvement - what was the reason that the defect occured and can we prevent the defect from occuring in the future.Give input for status and progress reports.Operational support for solving and retesting defects. ![]() The purpose of defect management for your project or organisation can be: The purpose of defect management may vary. Defect management is a means that gives insight in the quality level of the code or documentation that is being tested: the number of defects found during testing and the number of unsolved defects that are remaining in the code (or documentation). To be able to provision information and advice concerning risks and quality insight in the quality is required. In TMap the following definition of defect is used: DefinitionĪ defect (fault) is the result of an error residing in the code or document. ![]() When the system is performing differently from the required behaviour, from a viewpoint outside the system.Fault is the state where mistake or error exists. Fault is the view from inside the system. Human mistake this action takes place prior to any faults and/or failures.In this book, the following distinction is made: Confusion sometimes arises concerning the various terms, such as errors, faults and failures. This way the defect can’t get lost or forgotten.Ī defect is also termed a 'fault'. That is why defects are often recorded and tracked. While it should be clear that the purpose of testing is much more ( the provision of information and advice concerning risks and quality) the fact remains that finding defects is one of the most important activities of testing. Many people see the finding of defects as the purpose of testing. A defect is an observed difference between the expectation or prediction and the actual outcome of a test. What is a defect and why is it important? During all activities in software development, defects can be found. ![]()
0 Comments
Leave a Reply. |