GB/T 16260.1-2006
Software engineering - Product quality - Part 1: Quality model (English Version)

Standard No.

GB/T 16260.1-2006

Language

Chinese, Available in English version

Release Date

2006

Published By

General Administration of Quality Supervision, Inspection and Quarantine of the People‘s Republic of China

Status

Be replaced 2017-05

Replace By

GB/T 25000.10-2016

Latest

GB/T 25000.10-2016

Replace

GB/T 16260-1996

Scope

This part of GB/T 16260 describes a two-part model for software product quality: a) internal quality and external quality, b) quality in use. The first part of the model specifies six characteristics for internal and external quality, which can be further subdivided into sub-characteristics. When software is part of a computer system, these subcharacteristics emerge externally as a result of internal software properties. This section does not elaborate on the internal and external quality models below the sub-characteristic level. The second part of the model specifies the characteristics of the quality of use of the four gases, but does not elaborate the model of the quality of use at a level below the characteristics. Quality in use is the combined effect of six user-oriented software product quality characteristics. The defined characteristics apply to every class of software, including computer programs and data in firmware. Features and sub-features provide a consistent terminology for software product quality and a framework for identifying software quality requirements and weighing software product capabilities. Appendix A provides recommendations and requirements for software product measurement and measurement of quality in use. Examples of these metrics are included elsewhere in this standard. These metrics can be applied to describe software product quality requirements and design goals, including intermediate products. Instructions on how to apply this quality model in software product evaluation are included in GB/T 18905.1-2002. This part enables software product quality to be determined and evaluated from different perspectives related to software acquisition: requirements, development, use, evaluation, support, maintenance, quality assurance and auditing. For example, it can be used by developers, acquirers, quality assurance personnel, and independent evaluators, especially those responsible for determining and evaluating the quality of software products. Examples of the use of the quality model defined in this standard are: Confirming the completeness of requirements definitions; Determining software requirements; Defining software design objectives; Defining software testing objectives; guidelines. · A software product quality definition framework in the customer-supplier process; · Support for review, verification and validation and a quantitative quality evaluation framework in the support process; · Support in the management process for setting organizational quality objectives. · A software product quality requirements definition framework in the life cycle basic process; · Support for review, verification and validation in the life cycle support process. • Support for setting quality objectives; • Support for design review, verification and validation.

GB/T 16260.1-2006 history

• 2016 GB/T 25000.10-2016 Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Part 10: System and software quality models
• 2006 GB/T 16260.1-2006 Software engineering - Product quality - Part 1: Quality model
• 1996 GB/T 16260-1996 Information technology--Software product evaluation--Quality characteristics and guidelines for their use

GB/T 16260.1-2006 Software engineering - Product quality - Part 1: Quality model was changed to GB/T 25000.10-2016 Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Part 10: System and software quality models.

GB/T 16260.1-2006 -All Parts