 |
 |
 |
Defect are fault in a software system, such software system when executed results in failure. So we can say that Failure occurs because of the defect in a software system. To track defects, a defect workflow process has been implemented. Defect workflow training will be conducted for all test engineers. The steps in the defect workflow process are as follows:
a) When a defect is generated initially, the status is set to "New". (Note: How to document the defect, what fields need to be filled in and so on, also need to be specified.)
a) When a defect is generated initially, the status is set to "New". (Note: How to document the defect, what fields need to be filled in and so on, also need to be specified.)
b) The Tester selects the type of defects:
* Bug
* Cosmetic
* Enhancement
* Omission
c) The tester then selects the priority of the defect:
* Critical - fatal error
* High - require immediate attention
* Medium - needs to be resolved as soon as possible but not a showstopper
* Low - cosmetic error
d) A designated person (in some companies, the software manager; in other companies, a special board) evaluates the defect and assigns a status and makes modifications of type of defect and/or priority if applicable).
* Bug
* Cosmetic
* Enhancement
* Omission
c) The tester then selects the priority of the defect:
* Critical - fatal error
* High - require immediate attention
* Medium - needs to be resolved as soon as possible but not a showstopper
* Low - cosmetic error
d) A designated person (in some companies, the software manager; in other companies, a special board) evaluates the defect and assigns a status and makes modifications of type of defect and/or priority if applicable).
* The status "Open" is assigned if it is a valid defect.
* The status "Close" is assigned if it is a duplicate defect or user error. The reason for "closing" the defect needs to be documented.
* The status "Deferred" is assigned if the defect will be addressed in a later release.
* The status "Enhancement" is assigned if the defect is an enhancement requirement.
e) If the status is determined to be "Open", the software manager (or other designated person) assigns the defect to the responsible person (developer) and sets the status to "Assigned".
f) Once the developer is working on the defect, the status can be set to "Work in Progress".
g) After the defect has been fixed, the developer documents the fix in the defect tracking tool and sets the status to .fixed,. if it was fixed, or "Duplicate", if the defect is a duplication (specifying the duplicated defect). The status can also be set to "As Designed", if the function executes correctly. At the same time, the developer reassigns the defect to the originator.
h) Once a new build is received with the implemented fix, the test engineer retests the fix and other possible affected code. If the defect has been corrected with the fix, the test engineer sets the status to "Close". If the defect has not been corrected with the fix, the test engineer sets the status to .Reopen.. Defect correction is the responsibility of system developers; defect detection is the responsibility of the AMSI test team. The test leads will manage the testing process, but the defects will fall under the purview of the configuration management group. When a software defect is identified during testing of the application, the tester will notify system developers by entering the defect into the PVCS Tracker tool and filling out the applicable information.
Defect Tracking Tools and Their Impact on Total Product Life Cycle
Our modern world has created an array of incredibly complex systems, and incredibly complex processes for making goods, writing software, and developing new products. This complexity allows modern coding and manufacturing to scale up to levels of societal and personal wealth unimaginable to people living even a century ago, but they do mean that every step along the way, there's a chance for defects and other issues to get wrapped up in the process and need coordinated development. Defect tracking tools are a major part the total product life cycle investment.
Defect trackers, much like software bug trackers, allow users to input reports about issues they're having with a product; where they differ is that they're not limited solely to software issues; they can be used for a wide variety of projects, ranging from reporting on hardware defects in toys and consumer electronics to being an internal tool for diagnosing product dependency chain issues and help desk support.
Indeed, help desk management software is a set of generalized defect tracking tools at its core: Someone reports a problem, the problem is assigned to someone who has to fix it, as the problem is documented (and the fix is implemented) the process is documented, and ideally, the person who reported the problem gets a report of its ongoing progress.
In manufacturing, defect tracking software is used for return merchandise authorizations - the customer reports the defect in the item, submits a report, and gets a shipping tag to send the defective item in and get a replacement. (This is also used by several internet point of sale sites, such as Amazon, to handle customer returns.)
Defect tracking tools are all about maintaining a chain of responsibility, from the time the problem is indicated, to the time the problem is resolved. They allow the end user to see the status of their problem, they allow the managers of the staffers solving the problem to see what's going on, who's assigned to the problem and see if they need more help, and they allow people doing new product development to get a statistical database of what kinds of issues a product is having; this can weed out manufacturing problem defects, or sometimes lead to entire new product categories, as a significant number of customers use a product for things it was never intended for, which indicates a demand for something that could be developed profitably.
A good defect tracking tool set can help you not only improve your process for solving problems brought to you by your customer base, but can help you meet the basic paradigm that every problem a customer brings you is an opportunity to either improve your product, or generate new business.
* The status "Close" is assigned if it is a duplicate defect or user error. The reason for "closing" the defect needs to be documented.
* The status "Deferred" is assigned if the defect will be addressed in a later release.
* The status "Enhancement" is assigned if the defect is an enhancement requirement.
e) If the status is determined to be "Open", the software manager (or other designated person) assigns the defect to the responsible person (developer) and sets the status to "Assigned".
f) Once the developer is working on the defect, the status can be set to "Work in Progress".
g) After the defect has been fixed, the developer documents the fix in the defect tracking tool and sets the status to .fixed,. if it was fixed, or "Duplicate", if the defect is a duplication (specifying the duplicated defect). The status can also be set to "As Designed", if the function executes correctly. At the same time, the developer reassigns the defect to the originator.
h) Once a new build is received with the implemented fix, the test engineer retests the fix and other possible affected code. If the defect has been corrected with the fix, the test engineer sets the status to "Close". If the defect has not been corrected with the fix, the test engineer sets the status to .Reopen.. Defect correction is the responsibility of system developers; defect detection is the responsibility of the AMSI test team. The test leads will manage the testing process, but the defects will fall under the purview of the configuration management group. When a software defect is identified during testing of the application, the tester will notify system developers by entering the defect into the PVCS Tracker tool and filling out the applicable information.
Defect Tracking Tools and Their Impact on Total Product Life Cycle
Our modern world has created an array of incredibly complex systems, and incredibly complex processes for making goods, writing software, and developing new products. This complexity allows modern coding and manufacturing to scale up to levels of societal and personal wealth unimaginable to people living even a century ago, but they do mean that every step along the way, there's a chance for defects and other issues to get wrapped up in the process and need coordinated development. Defect tracking tools are a major part the total product life cycle investment.
Defect trackers, much like software bug trackers, allow users to input reports about issues they're having with a product; where they differ is that they're not limited solely to software issues; they can be used for a wide variety of projects, ranging from reporting on hardware defects in toys and consumer electronics to being an internal tool for diagnosing product dependency chain issues and help desk support.
Indeed, help desk management software is a set of generalized defect tracking tools at its core: Someone reports a problem, the problem is assigned to someone who has to fix it, as the problem is documented (and the fix is implemented) the process is documented, and ideally, the person who reported the problem gets a report of its ongoing progress.
In manufacturing, defect tracking software is used for return merchandise authorizations - the customer reports the defect in the item, submits a report, and gets a shipping tag to send the defective item in and get a replacement. (This is also used by several internet point of sale sites, such as Amazon, to handle customer returns.)
Defect tracking tools are all about maintaining a chain of responsibility, from the time the problem is indicated, to the time the problem is resolved. They allow the end user to see the status of their problem, they allow the managers of the staffers solving the problem to see what's going on, who's assigned to the problem and see if they need more help, and they allow people doing new product development to get a statistical database of what kinds of issues a product is having; this can weed out manufacturing problem defects, or sometimes lead to entire new product categories, as a significant number of customers use a product for things it was never intended for, which indicates a demand for something that could be developed profitably.
A good defect tracking tool set can help you not only improve your process for solving problems brought to you by your customer base, but can help you meet the basic paradigm that every problem a customer brings you is an opportunity to either improve your product, or generate new business.
Defect Tracking