When it comes to today's IT projects, software engineering has received much attention. The quality of software is the focus of attention, because there is no set of perfect evaluation standards. Some people even suggested that the current software development cannot be called "engineering" at all, because it is too immature and there is no mature standard to compare with; therefore, software projects are prone to failures or mistakes. A lot of practice has proved that the success or failure of software engineering projects is usually due to management problems (the ability to work together), rather than technical problems. To make a "perfect" software dinner, the role of quality management is self-evident.
In the actual project quality management, quality management always revolves around the quality assurance (QualityAssurance) process and the quality control (QualityControl) process. These two processes interact and may intersect in practical applications. As mentioned in the introduction, it is difficult to give a very clear definition of the quality of software. This paper mainly discusses the quality management in software engineering.
The process of making software "big meal"
The purpose of software quality assurance (Software Quality Assurance, hereinafter referred to as SQA) is to verify whether appropriate processes and standards are followed during software development. The software quality assurance process generally includes the following activities:
The first is to establish an SQA group; the second is to select and determine the SQA activities, that is, to select the quality assurance activities to be carried out by the SQA group, these SQA activities will be used as the input of the SQA plan; then the development and maintenance of the SQA plan, this plan clearly defines the SQA activities and The relationship between various stages in the entire software development life cycle; there is also the implementation of the SQA plan, the training of relevant personnel, and the selection of quality assurance tools that are compatible with the entire software engineering environment; the last is to continuously improve the deficiencies in the quality assurance process activities, improve Project quality assurance process.
An independent SQA group is one of the metrics by which software development activities are measured. This independence of the SQA group enables it to enjoy a key right - "leapfrog reporting". When the SQA team finds a crisis in product quality, it has the right to report the crisis directly to the project team's higher-level agency. This undoubtedly has a considerable "deterrent" effect on the project team, and can also be regarded as an incentive for the project team to pay attention to the quality of software development. This format enables many problems to be solved within the group, improving the quality and efficiency of software development.
The purpose of the process of selecting and identifying SQA activities is to plan the quality assurance activities that need to be carried out throughout the project development process. Quality assurance activities should be aligned with the overall project development plan and configuration management plan. The activities are generally divided into the following five categories:
1) Review software products, tools and facilities
Software products are often referred to as "intangible" products. Judging is more difficult. One thing to note here is that the review should not only review the final software code, but also review the software development plan, standard, process, software requirements, software design, database, manual, and test information. The main purpose of evaluating software tools is to ensure that appropriate technologies and tools are used by the project team. The purpose of evaluating project facilities is to ensure that the project team has sufficient equipment and resources for software development work. This also provides a basis for planning equipment purchase, resource expansion, and resource sharing of future software projects.
2) Software development process reviewed by SQA activities
The software development process reviewed by SQA activities mainly includes: software product review process, project planning and tracking process, software requirements analysis process, software design process, software implementation and unit testing process, integration and system testing process, project delivery process, sub-process Contractor control process, configuration management process. In particular, to ensure software quality, SQA should be given the right to prevent the delivery of certain products that do not meet project requirements and standards.
3) Participate in technical and management reviews
The purpose of participating in technical and management reviews is to ensure that such reviews meet project requirements and facilitate oversight of problem resolution.
4) Do SQA report
An important part of SQA activities is to report the results of the software product or software process assessment and make recommendations for improvement. SQA should document the results of its assessment