Organization Policy
According to some organization policy,
- Defect Prevention (DP) Board are responsible to manage and handle activities of defect prevention at organizational level.
- Project Manager appoint DP Coordinator to manage and handle activities of defect prevention at project level.
- Long-term plan or goal is also established and developed for activities of defect prevention by DP Board.
- Senior Management generally review result of activities of DP to simply check their effectiveness.
Defect Prevention in Software Engineering
Software quality is one of the most important and essential factors from the last few years. This is due to forces from several sectors of the computer industry. Companies and organizations face many problems that have increased difficulty in obtaining and achieving rapid and successful development of software systems. The main challenge in any software product development is simply to reduce and minimize and number and occurrence of defects.
Defects are one of the major causes of a decrease in software quality and an increase in overall cost due to additional cost required for resolving defects. Therefore, identifying and resolving defects is the main focus of any development team that will help in preventing software products from occurring again.
For this identification and resolution of defects, defect prevention is the most significant and essential activity of the software development life cycle that directly effect controlling the cost and quality of software products. Someone has well said that “Prevention is better than cure”. The main goal of defect prevention is to identify defects and take corrective measures to minimize their impact and completely reduce the chances of their re-occurrence in future releases.
Contact Us