HOME   Cart(0)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189760 (25 Oct 2025)

GB/T 16260.4-2006 English PDF

Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 16260.4-2006EnglishRFQ ASK 6 days [Need to translate] Software engineering -- Product quality -- Part 4: Quality in metrics Obsolete GB/T 16260.4-2006

PDF similar to GB/T 16260.4-2006


Standard similar to GB/T 16260.4-2006

GB/T 39099   GB/T 25000.51   GB/T 28172   GB/T 45395   GB/T 45400   GB/T 45281   

Basic data

Standard ID GB/T 16260.4-2006 (GB/T16260.4-2006)
Description (Translated English) Software engineering -- Product quality -- Part 4: Quality in metrics
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard L77
Classification of International Standard 35.080
Word Count Estimation 51,516
Date of Issue 2006-03-14
Date of Implementation 2006-07-01
Quoted Standard GB/T 8566-2001; GB/T 16260.1-2006; GB/T 16260.2-2006; GB/T 16260.3-2006; GB/T 18905.1-2002; GB/T 18905.2-2002; GB/T 18905.3-2002; GB/T 18905.4-2002; GB/T 18905.5-2002; GB/T 18905.6-2002; GB/T 18491.1-2001; ISO 9241-10: 1998
Adopted Standard ISO/IEC TR 9126-4-2004, IDT
Regulation (derived from) China Announcement of Newly Approved National Standards No. 4, 2006 (No. 91 overall)
Issuing agency(ies) General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China
Summary This standard defines the basis GB/T16260. 1-2O06 defined properties and sub- properties to quantitatively measure the internal internal software quality metrics. This section is intended to be used together with GB/T16260. 1-2006. This section includes the following information: a) how to use the software metrics and qualitative interpretation, b) the basic characteristics of each sub- measure set. c) the software product life cycle examples of the use of these metrics. This section is not level or for a compliance assessment level and set up a range of these measurements, since these values ??are based on each software product or software part of the product depending on its own characteristics, ie, the software according to coarse classification, complete resistance levels and user needs and other factors. Some properties may be expected value range circle, but does not depend on a specific user's Challenge requirements, while Van hardship often identified by trip on general factors, such as human cognitive factors. This part can be used for various applications. Users can select, modify, and application metrics in this section and side degrees, unique application can also be annoying for a specific application domain defined metrics. For example, for safety and security and confidentiality of the specific quality characteristics such as the amount can be found on the side of national standards and international standards. This section is intended for the following users: a) demand-side (that acquires or procures a system, software product or software service individual or organization), b) evaluators (Implementation Evaluation of the individual or organization, such as evaluators can be side of the test laboratory, the quality of software development organizations and governmental organizations, departments or user ", c) developers (executive development activities of individuals or organizations, development activities include software life cycle