This chapter to examine the technical support software quality in terms of construction.
Characteristics of software quality
- Correctness;
- Availability;
- effectiveness;
- reliability;
- Integrity;
- Adaptability;
- Accuracy;
- Robustness;
- Maintainability;
- flexibility;
- Can be performed;
- Reusability;
- readability;
- Testability;
- Comprehensibility
Technology to improve software quality
- Software quality objectives;
- A clear definition of quality assurance;
- Test strategy;
- Software Engineering Guidelines;
- Informal technical review;
- Formal technical review;
- External review.
development process
- The process of change of control;
- The results of quantification;
- Prototyping.
The relative effectiveness of different quality assurance techniques
- Defect detection rate;
- Find out the cost of defects;
- The cost of correcting defects
When quality assurance work
Before the start of this work should be added to the project plan, as part of the technology in the context of the project, and the project should be used as street bookstore, when the whole end of the work to test the quality of the product.
The general principles of software quality
The general principles of software quality is to improve quality in order to reduce development costs.
Checklist: Quality Assurance Plan
- [] Determine whether the particular quality characteristics of the project critical?
- [] Whether to let other people aware of the quality objectives of the project?
- [] Can distinguish whether the quality characteristics of external and internal characteristics?
- [] Have you considered the way certain characteristics specific constraints and other characteristics of each other or mutually reinforcing?
- [] At every stage of software development, project whether the requirements for different types of errors using different error detection techniques?
- [] Is there a project plan step by step to ensure the quality of the software at various stages of development?
- [] Are you using some kind of quality assessment methods, and thereby determine the quality is improving or decreased?
- [] Does management understand the additional costs for quality assurance trumpet early, late in the project purpose is to reduce costs?
More resources
Ginac《Customer Oriented Software Quality Assurance》
Lewis《Software Testing and Continuous Quality Improvement》
Points
The final development of high-quality code does not require you to pay more, but you need to reallocate resources, at low cost to prevent defects, thereby avoiding costly rectification work;
- Not all the quality assurance objectives can be fully achieved. The goal is clear what you hope to achieve, and communicate these goals and team members;
- No single error detection method can solve all the problems, the test itself is not the most effective method for troubleshooting errors. Successful quality assurance program should use a variety of different techniques to examine a variety of different types of errors;
- During construction should use some effective quality assurance techniques, but before that, has the same powerful features some quality assurance techniques is also essential. The sooner an error is found, it is less entangled with the rest of the code, so the loss is also smaller.
The field of software quality assurance is process-oriented. Software development and manufacturing is not the same, here there is no repeat stages will affect the final product, therefore, the quality of the final product is controlled by the development of software used in the process.