Be the first to like this
To get more insight into the quality of the product during development, it is needed to measure processes with two views: Introduction of defects, and detection. Introduction is done during the requirements, architecture, design and coding phases; defects are either introduced into documents or into the actual product code. Detection is done in test phases, and in the previously mentioned phases by means of inspections and reviews. By using these two measurements, a project can determine if and what the quality risk is: Too many defects in the product, or insufficient testing done.
The presentation will focus upon:
- Goals: What was the purpose of the model, why was it developed, what did we want to reach?
- How: Both the definition of the model and its implementation and application will be highlighted?
- Tools: The tool that was developed to implement the model, how it works, strengths.
- Results: How did the model and tool help the project? Did it live up to its purpose?
- Success factors: What were the key issues that we have dealt successfully with? Why did we focus on them, and how?
- Future: How is this model used in future projects, what could further increase its benefits?
The presentation will show the benefits that the model/tool has brought to the project and organisation. Mainly it was the ability to manage process & product quality, and support decisions, based on data collected in the project and industrial date, i.e. without having to build up historical data in previous projects.
The defect model uses techniques like Orthogonal Defect Classification and Test Matrices for analysis of the defect data. Feedback of the data towards designers, testers, and project management was key in validating the data, and getting good analysis results for corrective and preventive actions.