Establishing a work objective SQA (Software Quality Assurance, Software Quality Assurance) is a critical process area of CMM. Each key process domain of CMM has almost all of the software quality verification, which plays a very important role in software development. In CMM, the goal of software quality assurance is to provide the manager with the visibility of the current software project and the final product. Its main tasks include: review software engineering activities, auditing software products, and notify the project team members and related managers. From the CMM's framework structure, the main work objective of software quality assurance personnel is to ensure the quality of the software process. The quality of the software final product is the problem of project managers and quality engineers, rather than being responsible by software quality assurance.
The value of software quality assurance depends on some premise, and the most important of which is the following:
a) The software project development process follows clearly defined established rules, which is much greater than the cost it pays. First, there is a stable, clear user needs to develop, although the progress may be delayed, but it is much smaller than the products needed by the user after the development.
b) People sometimes deviate from the established rules without independent evaluation systems. Due to various reasons, software developers always consciously or unconsciously neglect the process, and the software quality assurance personnel need to find problems.
Ensuring the quality of the staff's independence is not equal to good product quality, but the bad process is difficult to bring good product quality. If a project completes development work in accordance with the established process, there is no deviation, indicating that the software quality assurance personnel have fulfilled his responsibilities. In order to better carry out software quality assurance, software quality assurance personnel should be independent, with the project manager without any administrative affiliation, and his assessment and evaluation should not be made by the project manager, and he can't bear this project. Any other work outside of software quality assurance to ensure its independence. It is recommended that the software quality assurance agency is set up into specialized independent institutions in the enterprise. If the company is small, it can be administered by the tester. In some companies, testers are subordinate to project groups. At this time, software quality assurance personnel should be held by testers in other project groups.
The standard objective software quality assurance is to provide managers to provide visibility. If there is a subjective factor, the manager does not see the real situation of the software development process, this is critical to the software quality assurance. For example, Lenovo's software products are implemented through the Quality Assurance Checklist. For each software engineering activity and software work products, there is a software quality assurance checklist. Software quality assurance personnel can determine if the current software engineering activity is deviated from the checklist and whether the software work product meets the requirements. Whether software engineering activities have deviated, mainly watching the entry criterion of software engineering activities, whether the input is correct, performs the task if the task meets the requirements, whether it meets the completion criteria and whether it has a desirable output. When auditing software work products, software quality assurance staff mainly audit software products meet regulations, standards, etc., generally do not consider technical issues. All software developers should accept targeted training in software quality assurance, understand the purpose, work mode and other related content of software quality assurance. Only all people recognize the meaning of software quality assurance work, this work can be carried out very well.
