GB/T 25000.20-2021 English PDFUS$489.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 25000.20-2021: Systems and software engineering - Systems and software quality requirements and evaluation (SQuaRE) - Part 20: Quality measurement framework Status: Valid
Basic dataStandard ID: GB/T 25000.20-2021 (GB/T25000.20-2021)Description (Translated English): Systems and software engineering - Systems and software quality requirements and evaluation (SQuaRE) - Part 20: Quality measurement framework Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L77 Word Count Estimation: 26,247 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration GB/T 25000.20-2021: Systems and software engineering - Systems and software quality requirements and evaluation (SQuaRE) - Part 20: Quality measurement framework---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order. Systems and software engineering - Systems and software quality requirements and evaluation (SQuaRE) - Part 20.Quality measurement framework ICS 35.080 L77 National Standards of People's Republic of China System and Software Engineering System and Software Quality Requirements and Evaluation (SQuaRE) Part 20.Quality Measurement Framework [ISO /IEC 25020.2019,Systemsandsoftwareengineering- Released on 2021-04-30 and implemented on 2021-11-01 State Administration of Market Supervision and Administration Issued by the National Standardization Management Committee Table of contentsForeword Ⅰ Introduction Ⅲ 1 Scope 1 2 Normative references 1 3 Terms and definitions 1 4 Abbreviations 2 5 Compliance 2 6 Quality measurement 2 6.1 Quality measurement reference model 2 6.2 Different QMs and their interrelationships 3 6.3 Choice of QM 6 6.4 Construction of QM 6 6.5 Planning and execution of measurements 7 6.6 Application of measurement results 8 Appendix A (informative appendix) QM and QME selection considerations 10 Appendix B (informative appendix) Measurement reliability and QM effectiveness evaluation 11 Appendix C (informative appendix) Elements of the preparation of QM 13 Appendix D (informative appendix) The normalization of the QM measurement function 16 Appendix E (informative appendix) Measurement information model in ISO /IEC /IEEE15939 18 Reference 21 System and Software Engineering System and Software Quality Requirements and Evaluation (SQuaRE) Part 20.Quality Measurement Framework1 ScopeThis part of GB/T 25000 specifies the framework for carrying out quality measurement work. The content of this section is as follows. ---Quality measurement reference model; ---The relationship between different types of quality measures; ---Guidelines for choosing quality measures; ---Guidelines for constructing quality measures; ---Guidelines for planning and performing measurements; ---Guidelines for applying measurement results. This section also gives considerations for the selection of quality measurement and quality measurement elements (see Appendix A), and the measurement reliability and quality measurement are valid. The evaluation of quality (see Appendix B), the elements of compiling quality measures (see Appendix C), the normalization of the measurement function of quality measures (see Appendix C) D) and the measurement information model in ISO /IEC /IEEE15939 (see Appendix E). This part can be used to design, identify, evaluate and implement system and software product quality, use quality and data quality measurement models. The The reference model can be used by developers, demanders, quality assurance personnel, and independent evaluators, especially responsible for specifying and evaluating ICT systems Used by quality personnel.2 Normative referencesThe following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this article Pieces. For undated reference documents, the latest version (including all amendments) is applicable to this document. GB/T 25000.1 System and Software Engineering System and Software Quality Requirements and Evaluation (SQuaRE) Part 1.SQuaRE Guide (GB/T 25000.1-2021, ISO /IEC 25000.2014, MOD) ISO /IEC /IEEE15939 system and software engineering measurement process (Systemsandsoftwareengineering-Meas- urementprocess)3 Terms and definitionsThe following terms and definitions defined in GB/T 25000.1 and ISO /IEC /IEEE15939 apply to this document. 3.1 Derivedmeasure A measure defined by a function of at least two basic measure values. [Source. ISO /IEC /IEEE15939.2017, definition 3.3, with modification] The quality of use requirements are based on the expected results/consequences of the system and/or software products (e.g., the cost of the user to complete a specific expected task Time) to determine effectiveness, efficiency, satisfaction, anti-risk and surrounding coverage. They can derive the use of external quality requirements (for example, throughput Volume, response time, etc.). The use of external quality requirements should adopt external QM criteria in the quality requirements specification. Quantitative descriptions are performed, and these criteria are used when evaluating target entities. The use of external quality requirements can derive the use of internal quality Requirements (for example, the complexity of the program structure, etc.). Use internal quality requirements to reflect technical/structural characteristics. They can be used to specify The nature of deliverable, non-executable software products (such as documents and manuals). They can also be used as the target entity for verification and are Define verification criteria for each stage. Through the quality life cycle, the required quality can be measured at different levels for verification and confirmation. At the usage level, usage week The environment plays an important role in the confirmation between the use quality requirements and the quality impact. At the operational level, use external quality requirements and external The quality of the department can be mutually confirmed and verified. At the implementation level, the quality requirements using internal properties and internal quality properties can be mutually confirmed And verification. Note. The use of quality QM means the quality explained by the influence of stakeholders; the external QM means that it is used in prototype testing, product testing and actual testing. The quality explained by the behavior of the target entity when used; internal QM means that it is explained by the results of the specification and/or source code review the quality of. 6.3 Selection of QM QM is to meet the information needs of developers, demanders, managers, direct and indirect users, and other stakeholders. of. Candidate QMs that potentially meet quality requirements should be determined from the part of GB/T 25000 that provides specific QMs, such as GB/T 25000.22, GB/T 25000.23 or GB/T 25000.24.Then, the candidate QM can be further refined as needed. At least it should be stated that QM (package A criterion including a combination of measures explains the reason for choosing QM. A variety of different combinations of basic measures and derived measures can be selected to build attachments Added QM, these QMs are used as indicators to clarify specific quality requirements. When choosing QM, it is recommended to consider the following factors. Level of relevance of information needs; the feasibility of collecting data in the organizational unit; the availability of human resources for collecting and managing data; receipt How easy it is to collect data. When QM is used to define quality requirements, the criticality of these quality requirements or insufficient quality requirements definition results Risk can be used as one of the criteria for choosing QM. When using QM to evaluate quality, applicable rigor and timeliness can be used as guidelines. The selected measure will affect people's behavior. In many cases, this behavior may be due to someone trying to profit from the relevant system. Will cause abnormal results. Users should anticipate these challenges and take measures (including training, guidance and additional strategic governance) to reduce risk. The criteria for selecting QM to meet these information needs should be documented. Appendix A provides suggestions on the criteria for selecting QM. Note 1.GB/T 25000.30 and GB/T 25000.40 respectively provide guidance for quality requirements specification and product quality evaluation. When using modified or not in the quality measurement part of the GB/T 25000 standard (e.g. GB/T 25000.22, GB/T 25000.23 Or the new measure identified in GB/T 25000.24), the user should explain the relationship between the measure and its corresponding quality model, and its How is it built from QME. Appendix C provides examples of programming QM. Note 2.GB/T 25000.10 provides guidance on the definition and use of system and software product quality models. 6.4 Construction of QM 6.4.1 Identify the QM that needs to be built The quality of a system refers to the extent to which the system meets the explicit and implicit needs of various stakeholders and provides a measure of value. This standard adopts the quality model To express these explicit and implicit needs, the quality model divides the quality into a set of characteristics, and the characteristics are further decomposed into sub-features under certain circumstances. Sex. The complete set of quality characteristics of these models is not relevant to every stakeholder. Nonetheless, every type of stakeholder should be Send a representative to review and consider the relevance of the quality characteristics in each model before finally determining a set of quality characteristics to be used, such as these quality characteristics. Performance will be used to establish performance requirements or evaluation criteria for systems and software products. The applicable QM is not limited to the QM listed in GB/T 25000.22, GB/T 25000.23 and GB/T 25000.24.If needed, New QM can be constructed and included in the QM set of specific features or sub-features to meet the additional quality requirements of users. new QM should be described in accordance with 6.4.2, appropriate QME should be selected, and the combination of QMEs should be used with measurement functions (see Appendix D). Any new definition of QM, including QM modified from the various parts of the GB/T 25000 standard quality measurement, should be recorded. The definition of QM should include the information contained in the examples provided in Appendix C. Note 1.GB/T 25000.22 gives a set of recommended quality measures and their definitions. Note 2.GB/T 25000.23 gives a set of recommended system and software product quality measures and their definitions. Note 3.GB/T 25000.24 gives a set of recommended data quality measures and their definitions. 6.4.2 Description of QM When users measure the system and software products and data, the following information is very important to record the definition of each QM. user More detailed information should be recorded when describing QM for better operation. For more detailed information on QM, see Appendix C. a) ID. QM identification code. Each ID consists of the following three parts. 1) Abbreviations for quality characteristics and possible sub-characteristics. (For example, "PTb" stands for "time characteristic" and is used to measure "sexual "Energy efficiency", "Acc" stands for a measure of accuracy). 2) The sequence number in the quality sub-characteristic. 3) Use tags. G. Generally applicable, with a wide range of applications; S. For specific needs. Note. ID can include additional parts (for example, PTb-1-G-IT-1 identifies the modification of PTb-1-G). b) Name. The name of the QM. c) Description. Including the required information and quality characteristics/sub-characteristics of QM, and (where applicable) the purpose of measurement. d) Measurement function. a formula that expresses the composition of QME into QM. e) Measurement method. the type of method that can be used to obtain the measurement. 6.4.3 Definition of QME QME is used for the entire life cycle of information and communication technology systems, and builds systems and software by applying measurement methods to specific attributes QM of product quality, use quality and data quality, and record the measurement obtained through the combination of measurement functions when necessary. QME is used to test The attributes of the system and software products themselves, the results of using the system and software products under specific circumstances, and the development of systems and software products, Resources consumed or activities performed during testing and maintenance. Note 1.An information and communication technology system is a system that applies information and communication technology. Note 2.GB/T 25000.21 gives a set of recommended QMEs and their definitions. 6.5 Planning and execution of measurements The users of GB/T 25000.22, GB/T 25000.23 and GB/T 25000.24 should plan and implement according to the reference model in Figure 2. Perform measurement to determine the value of QME and QM. Quality measurement should consider resources such as personnel, measurement automation, and software and hardware environments. The measurement plan should not contain repetitive work content in order to Take the same measure to clarify different information needs. Note 1.Some QMEs and QMs are usually planned to be repeated, iterated or periodically carried out in a specific phase or product life cycle to monitor trends or improve quality. The criteria for selecting QM and QME should be considered in the measurement plan, so as to reduce the risk of error and reduce the workload. At least the following should be considered factor. ---Measurement budget; ---The priority and rigor of QM and QME reflecting key quality requirements; ---Progress and resources involved; ---Application of measurement results; ---The relevance and importance of QM based on quality requirements and usage context. Note 2.The above-mentioned problems in a single project are usually solved by coordinating and sharing organizational measurement strategies, which provide measurement and analysis methods. Training, tools, environment, personnel, etc. The main activities related to performing measurement are as follows. ---The quality model needs to be determined according to different information related to the quality characteristics of the system or software product, data or quality of use; ---According to the determined quality model, determine the candidate QM and select the QM and construct the QME of the QM; ---Communicate with measurement personnel or data providers, make full use of QM and QME, plan and collaborate with stakeholders, Get QM and QME; ---Use measurement methods to generate QME values; ---Using the measurement function to calculate the QM value; ---Verify and save the value of QM and QME, as well as the measured surrounding information; Note 3.Various techniques can be used to verify the value of QM and QME, for example, the range and type of values, singular values, classification errors or large fluctuations. ---Use QM to measure quality characteristics and/or sub-characteristics; ---Record the results and inform users who need quality information to make decisions during the project or operation. It is recommended that users of GB/T 25000.22, GB/T 25000.23 and GB/T 25000.24 combine GB/T 25000.40, GB/T 25000.41 and Use GB/T 25000.45 and GB/T 25000.30 together. 6.6 Application of measurement results The measurement results can be interpreted according to quality requirements, including system and software product quality requirements, use quality requirements, and data quality requirements. begging. Quality requirements are defined through quality models and QM. In GB/T 25000.30, the quality model Details of the relationship between the relationship and quality requirements. The measurement results provide a basis for quality evaluation. Strict measurement is required to achieve progress between systems, software products, and data. Make reliable comparisons. In addition, the measurement results need to be compared with standard values. The measurement procedures should measure their claims with sufficient accuracy The quality characteristic (or sub-characteristic) to be measured. Quality evaluation requirements should be allocated to appropriate components related to them so that they can be defined for evaluation Quality of each appropriate QM. The decision criterion should be determined for the selected single measure. According to the evaluation plan, the selected QM should be applied to Evaluate the object and obtain the measurement scale value. GB/T 25000.40 provides general requirements for software quality specification and evaluation. Some QMs may be difficult to explain individually. The following provides ways that can be used in QM to make it easier to understand and explain. a) Compliance. compare the measurement results with specific business or usage requirements. Example. In a specific business or usage requirement, the maximum acceptable response time is 10 minutes. b) Benchmark. Compare measurement results with benchmarks of the same or similar products or systems used for the same purpose. Example. Using the new system to complete a task may take less time than using the old system. c) Time series. multiple comparisons of measurement results over time and analysis of trends. Example. The number of user errors reduced by each new prototype version of the system. d) Proficiency. Compare the measurement results with the values obtained by well-trained users or expert users. Example. How much time does a new user need to spend compared to an experienced user? e) Satisfactory number of people standard. when there is a database of historical values, the measurement result can be expressed as the number of users who have given a rating of at least this value percentage. This is more suitable for explaining the use of quality measures. Note. The measurement interpreter draws some preliminary conclusions based on the results. However, if they are not directly involved in the technical and management process, these conclusions should/should be Review by other stakeholders. It is recommended that all interpreters consider the context of these measures. For example, the interpreter can be a system analyst, tester Mass personnel, system users, project managers, quality engineers, developers and testers. When these interpreters belong to an independent developer It is very important to consider the surroundings in the interpretation process and review the preliminary conclusions of the interpretation when the demand side of maintenance or the evaluation organization.Appendix A(Informative appendix) QM and QME selection considerations A.1 Criteria for choosing QM and QME Many different combinations of QME and software quality measurement can be specified to clarify the user's perception of each part of GB/T 25000 quality measurement. Specific information needs for system and software product quality measurement. It is recommended to consider the following criteria. ---Relevance to prioritized quality requirements; ---Ability to clarify all relevant quality characteristics and sub-characteristics; ---Measurement repeatability and reproducibility; ---The effectiveness of QM; ---The feasibility of collecting data in the organization unit; ---The availability of human resources for collecting, analyzing and managing data; ---How easy it is to collect data; --- Availability of applicable tools; ---privacy protection; ---The ease with which users interpret the measurement results; ---Applicability of the context of use and/or evidence of suitability for the target measured in the life cycle stage (internal or external to the organizational unit). The cost of collecting, managing and analyzing data at all levels should be considered. The cost includes the following. ---Measure usage cost. data collection associated with each measure,...... |
