GB/T 25000.30-2021 Active National standards

GB/T 25000.30-2021 Systems and software engineering—Systems and software quality requirements and evaluation(SQuaRE)—Part 30:Quality requirements framework

Publish Date: 2021-04-30 Implement Date: 2021-11-01 For services related to genuine standard inquiry, procurement, translation, and other related services in China, please Contact Us

Price: $ 122

Download

Basic Information

Standard Code: GB/T 25000.30-2021

Standard Type: National standards

Standard Status: Active

is_force_gb: no

CCS Name: Software engineering

ICS Name: Software development and system files

Publish Date: 2021-04-30

Implement Date: 2021-11-01

Pages: 42 pages

Scope

This part of GB/T 25000 provides a framework for quality requirements for systems, software products, and data, including the concept of quality requirements and the process and methods of extracting, defining, and controlling them. The intended readers of this part include but are not limited to:
—— Clients: Evaluate whether systems, software products, and data meet their value positioning, that is, whether they meet the expected quality;
—— Developers: Design, implement, and test systems, software products, and data to ensure that they meet the expected quality;
—— Testers: Verify and confirm whether systems, software products, and data meet the expected quality;
—— Project managers: Plan, supervise, and control the progress of the expected quality;
—— Independent evaluators: Evaluate systems, software products, and data according to objective criteria.
This part follows the technical process defined in GB/T 22032, which is related to extracting the quality requirements of stakeholders and analyzing, defining, and maintaining quality requirements. In this part, the quality models of GB/T 25000.10 and GB/T 25000.12 are used to classify quality requirements, and based on the quality metrics in GB/T 25000.20, GB/T 25000.21, GB/T 25000.22, GB/T 25000.23, and GB/T 25000.24, a foundation is laid for quantifying quality requirements.
This part does not include the definition of other requirements (such as functional requirements, process requirements, etc.). This part does not specify any specific software quality metrics or development processes.