Tencent Youtest software testing platform shares the characteristics of software quality management
1. Software quality management should run through the entire process of software development, not just the software itself
Software quality is not just some test data, statistical data, customer satisfaction survey responses, etc., to measure the quality of a software, we should first consider whether the entire process of completing the software production meets certain quality requirements.
In software development practice , Software quality control can rely on process management (such as defect handling process, development document control management, release process, etc.), strictly implemented in software engineering to ensure quality.
For example:
· Through the process definition, control and continuous improvement of the process from "User Function Confirmation" to "Detailed Software Design" to ensure the "functionality" of the software;
· Pass the definition of the "system test" and "regression test" process of the testing department , Implementation and continuous improvement to ensure the "reliability" and "availability" of the software;
·through the "performance test" of the testing department to ensure the "efficiency" of the
software ; ·through the design process of the software architecture and the realization of the code and documentation during development Process to ensure the "maintainability" of the software;
· Ensure the "portability" of the software by introducing appropriate programming methods, programming tools and design ideas
2 . The review of development documents is an important way of product inspection
Since the software is the code executed on the computer, it is difficult to do without the installation of the software, the instructions for use, etc., so many documents in the development process are also used as part of the product, and they need to be inspected like the product. Review constitutes an important way of product inspection
3. Use technology to ensure quality
Use a variety of tools and software to perform various tasks of quality assurance, such as using CVS software for configuration management and document management, MR software for change control, and RATIONAL ROSE software for software development, etc.,
using advanced system analysis methods and software design methods ( OOA, OOD, software reuse, etc.) to promote the improvement of software quality
4. Apply quality management ideas to meet customer needs
·Defect prevention
-Analyze the defects encountered in the past and adopt corresponding measures to avoid these types of defects from reappearing in the future
1. Planning defect prevention activities
-Find and determine the usual cause of the defect
A pair of common causes of defects are prioritized and systematically eliminated
·Follow user needs tightly
There are two types of users: Customer and User. The
former pays, while the latter is the user
. The requirements of the two are sometimes different.
So both requirements must be met
. Use rapid prototyping as soon as possible Demonstration (Demo) to users and get user feedback in time, and constantly modify the software according to user feedback, instead of giving
it to the user after all the work is completed. Otherwise, there may be many places to be changed,
or even overturned.
·Coding after sufficient design to prevent rework due to poor consideration
·Firmly control the modification of defects
Special software should be used to record and track the repair of software defects.
Defect tracking records include: discoverer, defect description, repairer, repair record, confirmer, confirmation conclusion, and close the record after passing
·Fully carry out software system testing
After software coding, unit testing, and integration testing, sufficient system testing and regression testing must be carried out. After the software is stable and no new defects appear, then the software will be considered for delivery.
· Appropriately master the software release standards
It is not software with zero defects that is of high quality. Zero software defects are almost impossible. The remaining defects must be fully analyzed. As long as the needs of users can be met, the remaining defects of the software can be resolved in future upgrades