This category has the following 4 subcategories, out of 4 total. This page was last edited on 15 August 2014, at 19:00. A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working secure software development life cycle pdf or produces an incorrect result. Bugs arise from mistakes and errors made by people, in either a program’s source code or its design.
An unwanted and unintended property of a program or piece of hardware, especially one that causes it to malfunction. A fault in a program, which causes the program to perform in an unintended or unanticipated manner. If you want to detect and resolve the defect in early development stage, defect tracking and software development phases should start simultaneously. These Optional Fields include Customer name, Browser, Operating system, File Attachments or screenshots.
Assigned to’ fields then you can specify these fields. Otherwise, Test manager will set status, Bug priority and assign the bug to the respective module owner. The figure is a quite complicated one but when you consider the significant steps in bug life cycle you will get a quick idea of bug life. On successful logging, the bug is reviewed by Development or Test manager. Test manager can set the bug status as Open, can Assign the bug to developer or bug may be deferred until next release. Need more info’ or Fixed then the QA responds with a specific action. If the bug is fixed then QA verifies the bug and can set the bug status as verified closed or Reopen.
These are various stages of bug life cycle. The status caption may vary depending upon the bug tracking system you are using. When QA files a new bug. If the bug is not related to a current build or cannot be fixed in this release or bug is not important to fix immediately then the project manager can set the bug status as deferred.
Assigned to’ field is set by a project lead or manager and the bug is assigned to a developer. Fixed’ and then the bug is passed to the testing team. QA needs action to check if the bug is reproduced and can assign it to a developer with detailed reproducing steps. In this case, QA needs to add detailed reproducing steps and assign bug back to dev for the fix.