Shulou(Shulou.com)06/02 Report--

Shandong Software Evaluation Center, based on many years of experience, summarizes the technical embodiment of software quality assurance in the whole process, hoping to bring help to everyone. You are also welcome to log on to http://www. × × / to discuss and learn. Please correct the deficiencies. The framework of the whole process quality control of the software project mainly includes the following modules: l quality requirements and quality requirements analysis: the implementation of the whole process quality control unit case is based on the collection and analysis of quality requirements. L establish quality assurance mechanism: the whole quality control unit case is a multi-party cooperative project implementation process, and a scientific and effective quality assurance mechanism is the basic guarantee to ensure the smooth implementation of the plan. L process-based quality assurance module: mainly includes product audit, process inspection, plan tracking and risk assessment; l process-based quality control module: mainly includes multi-level software testing (unit testing, integration testing, system testing, acceptance testing and other performance tests), phase review and code review and review. L technical support: mainly includes process management technology (software process management, project management system application and technical review implementation), software testing technology (model checking technology, automatic use case technology and performance testing technology, etc.) L key process areas: the whole process quality control mainly includes four key process areas: software requirement process quality control, software design process quality control, software coding process quality control and software delivery process quality control. L whole process defect management: with the implementation of the whole process quality control, a large number of defects in software projects will be found. how to manage these defects effectively is the key to ensure the implementation effect of the whole process quality control. Therefore, the whole process defect management is an indispensable part of the whole process quality control. The whole process defect management carries on the defect tracking and control according to the defect life cycle, and uses the automatic management tool to realize the defect discovery record, tracking and elimination to ensure that each defect is disposed of reasonably. L quality evaluation: through the implementation of the whole process quality control, we can accumulate and collect relevant development data from multiple levels of the software project, scientifically analyze these data, and we can effectively evaluate the process and results of the whole project. So as to provide a strong and reasonable basis for decision-making. 1. Quality assurance ROUTE1: product audit: audit the main work products (such as project plans, software requirements specifications, design documents, important source code, test documents, user use documents, etc.) produced in each stage of the project to verify whether the work products meet the predetermined requirements, format and content meet the appropriate standards, so as to ensure the quality of the work products produced during the implementation of the project. The evaluation standard will adopt the combination of product specifications and actual needs to improve the effectiveness of work products. Process inspection: the core work of software quality assurance activities, whose main purpose is to inspect the working process of important engineering and technical activities in the process of software project development in accordance with predetermined work specifications and inspection criteria, find non-conformities, notify the project stakeholders in time and take corrective actions to ensure the quality of the project process. L plan tracking: in the whole project development and construction process, take the "project plan" as the main line and according to the project progress tracking and inspection. L risk assessment: the purpose is to identify the risk problems in the progress of the project and make early response measures in order to reduce or reduce the impact or loss caused by the risk problems to the project. Risk assessment is mainly carried out at key stages (major milestones) of the project progress process according to the needs of the project stakeholders. Second, ROUTE2: quality control l Technical Review (Technical Review,TR) aims to find defects in the work results as soon as possible, and to help developers eliminate defects in time, so as to effectively improve the quality of products. L code review includes two parts: code review and code review, which mainly checks the consistency of the compilation and design of the code, the compliance of the code with coding specifications and other standards, the readability of the code, and the correctness of the logical expression of the code. the rationality of the code structure and so on. Through the code inspection, we can find the problems that violate the coding specification in time, such as insecurity, boundary overflow, dead code and so on. L document inspection: all kinds of documents generated during the construction of the system should be checked carefully and document testing should be carried out if necessary. Unit testing is the quality control work of checking the correctness of the smallest unit (module) of software design, testing and finding errors in syntax, format and logic of the module. Using the unit test case test program, the actual results are compared with the expected values to verify the correctness of the module design. L integration testing is on the basis of code audit to check whether each part of the work meets or achieves the corresponding technical specifications and requirements in the process of assembling all software units into modules, subsystems or systems according to the requirements of the design specification. L system testing is to combine the software that has passed the integration test, as an element of the whole computer system, with other system elements such as computer hardware, peripherals, some supporting software, data and so on, in the actual or simulated running environment, a series of tests are carried out on the system to find out the inconsistency or contradiction between the software and the system definition. The special topic test is a targeted enhanced test according to the specific quality requirements of the project consignor. L acceptance testing is mainly based on the software suitability, accuracy, interoperability, security, maturity, fault tolerance, easy to recover, easy to understand, easy to learn, easy to operate, attractiveness, time characteristics, resource utilization, analysis, changeability, stability, etc. based on the contract between the software developer and the user, the software requirement statement and the relevant industry standards, national standards, laws and regulations, etc. Rigorous testing is carried out on testability, adaptability, ease of installation, coexistence, ease of replacement and compliance.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.