A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

What is meant by defect prevention?

The best thing to do with the defects would be to remove them completely from a software system and application. The best thing to do would be to focus on the prevention of these defects as it is said that “prevention is always better than cure” i.e. not to allow any defects in the software system and application in the first place itself. This is necessary until and unless we have so called methodologies that can locate the defects quickly and reduce their impact on the working of the system. Thus, the highest priority should be given to the identification and implementation of the best defect prevention techniques that we have today. This process forms a big part of the best software development practices identification process.

With what defect prevention process should be started?

– The process is to be started with the critical risk assessment process.
– This process identifies all the critical risks that are currently associated with a project.
– Once you have identified all the critical risks, it becomes possible for you to know what kind of defects have a probability of occurring in your software system or application and the ones that can have a really bad impact on it. – A number of strategies can be developed to prevent those defects.

There are 3 major steps to be taken in the defect prevention process namely:
1. Identification of the critical risks
2. Estimation of the expected impact
3. Minimization of the expected impact

Identification of Critical Risks

– The first step i.e., the identification of the critical risks involves identifying the risks that your project or software might be facing.
– There exist a number of defects that can hamper the successful development, operation as well the delivery of the system.

Estimation of Expected Impact

– In the second step, you need to make an assessment of the impact both physical and financial that a risk can impose up on the project.
– Once you are done with the identification thing, you should now focus up on minimizing the impact of the defects so that risks associated with them could be eliminated.
– This will reduce the probability of a risk becoming a hazard for your software system.

What is Defect Prevention?

– Defect prevention is both a way to enhance the quality of the software and reduce its cost.
– Defects have been defined as the variances from the attributes which are supposed to have correct and complete specifications and requirements as obtained from the users desires.
– Thus, defects have a potential to disable the software to meet the user requirements.
– As early as a defect is diagnosed, the easier and cheaper it gets to rectify it.
– The end product either has no error or has minimal errors.
– Defects cannot be removed just by putting them in to a defect tracking system even though this is the first step towards defect prevention.
– It rather requires a problem solving methodology for the identification, analyzation and prevention of defects from occurring.
– Defect prevention process follows a defect prevention cycle.
– The requirement analysis process is one of the integral parts of the defect prevention process.
– The user requirements are converted into specifications for the software product preventing additional errors entering in to the system.
– The following are the main steps in the defect prevention process:
1. Designing the software architecture
2. Reviewing the code
3. Testing the code
4. Defect logging and
5. Documentation

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>