Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumQuality Assurance @ OneStopTestingDefect Management@ OneStopTesting

Message Icon Topic: Defect Management Process

Post Reply Post New Topic
Author Message
Leela
Groupie
Groupie
Avatar

Joined: 27Apr2007
Online Status: Offline
Posts: 43
Quote Leela Replybullet Topic: Defect Management Process
    Posted: 04Jun2007 at 4:12am

Defect Management Process


Defect Prevention  -- Implementation of techniques, methodology and standard processes to reduce the risk of defects.

Deliverable Baseline  -- Establishment of milestones where deliverables will be considered complete and ready for further development work.  When a deliverable is baselined, any further changes are controlled.  Errors in a deliverable are not considered defects until after the deliverable is baselined.

Defect Discovery  -- Identification and reporting of defects for development team acknowledgment.  A defect is only termed discovered when it has been documented and acknowledged as a valid defect by the development team member(s) responsible for the component(s) in error.

Defect Resolution  -- Work by the development team to prioritize, schedule and fix a defect, and document the resolution.  This also includes notification back to the tester to ensure that the resolution is verified.

Process Improvement -
- Identification and analysis of the process in which a defect originated to identify ways to improve the process to prevent future occurrences of similar defects.  Also the validation process that should have identified the defect earlier is analyzed to determine ways to strengthen that process.

Management Reporting  -- Analysis and reporting of defect information to assist management with risk management, process improvement and project management.




Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
getzephyr
Groupie
Groupie


Joined: 25Jan2008
Online Status: Offline
Posts: 47
Quote getzephyr Replybullet Posted: 16Jun2008 at 12:50am
The defect management process is based on the following general principles:

The primary goal is to prevent defects.  Where this is not possible or practical, the goals are to both find the defect as quickly as possible and minimize the impact of the defect.

The defect management process should be risk driven-- i.e., strategies, priorities, and resources should be based on the extent to which risk can be reduced.

Defect measurement should be integrated into the software development process and be used by the project team to improve the process.  In other words, the project staff, by doing their job, should capture information on defects at the source.  It should not be done after-the-fact by people unrelated to the project or system

As much as possible, the capture and analysis of the information should be automated.

Defect information should be used to improve the process.  This, in fact, is the primary reason for gathering defect information.

Most defects are caused by imperfect or flawed processes.  Thus to prevent defects, the process must be altered
IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.492 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting