|
US$339.00 · In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 25000.12-2017: Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 12: Data quality model
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 25000.12-2017 | English | 339 |
Add to Cart
|
4 days [Need to translate]
|
Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 12: Data quality model
| Valid |
GB/T 25000.12-2017
|
PDF similar to GB/T 25000.12-2017
Basic data | Standard ID | GB/T 25000.12-2017 (GB/T25000.12-2017) | | Description (Translated English) | Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 12: Data quality model | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 17,176 | | Date of Issue | 2017-11-01 | | Date of Implementation | 2018-05-01 | | Regulation (derived from) | National Standard Announcement 2017 No. 29 | | 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 | GB/T 25000.12-2017: Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 12: Data quality model
---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 12. Data quality model
ICS 35.080
L77
National Standards of People's Republic of China
Systems and software engineering systems and software quality requirements and
Evaluation (SQuaRE) Part 12. Data Quality Model
andEvaluation (SQuaRE) -Part 12.Dataqualitymodel
[ISO /IEC 25012.2008, Softwareengineering-SoftwareproductQuality
Requirements and Evaluation (SQuaRE) -Dataqualitymodel, MOD]
Posted.2017-11-01
2018-05-01 implementation
General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
China National Standardization Administration released
Directory
Foreword Ⅲ
Introduction Ⅴ
1 Scope 1
2 Compliance 2
3 Normative references 2
4 Terms and definitions 2
5 data quality 3
5.1 Overview 3
5.1.1 Inherent data quality 3
5.1.2 Dependency System Data Quality 4
5.2 Data Quality Model 4
5.3 Data quality characteristics 5
5.3.1 Inherent viewpoint 5
5.3.2 Inherent and system dependent view 6
5.3.3 rely on the system's point of view 8
Appendix A (Informative) Terms and definitions from GB/T 25000.1-2010 10
References 11
Foreword
GB/T 25000 System and Software Engineering System and Software Quality Requirements and Evaluation (SQuaRE) "is divided into the following sections.
--- Part 1. SQuaRE Guide;
--- Part 2. Planning and Management;
--- Part 10. System and software quality model;
--- Part 12. Data Quality Model;
--- Part 20. Measurement reference model and guidelines;
--- Part 21. Quality measurement elements;
--- Part 22. Use of quality measurement;
--- Part 23. System and software product quality measurement;
--- Part 24. Data quality measurement;
--- Part 30. Quality Requirements;
--- Part 40. Evaluation process;
--- Part 41. Evaluation guidelines for developers, acquirers and independent evaluators;
--- Part 42. Evaluation module;
--- Part 45. Recoverability of the evaluation module;
--- Part 51. Quality requirements and test rules for ready-to-use software product (RUSP);
--- Part 60. Ease of use test report Common Format for Industry (CIF). Common Framework for Ease of Use related information;
--- Part 62. Usability test report industry common format (CIF);
--- Part 63. Industry Common Format for Ease of Use (CIF).
--- Part 64. Common Format for Industrial Ease of Use (CIF). User Requirements Report;
--- Part 65. Common Industrial Formats for Ease of Use (CIF). Specification of user requirements;
--- Part 66. Common Format (CIF) for Ease of Use. Evaluation Report.
This part is the 12th part of GB/T 25000.
This section drafted in accordance with GB/T 1.1-2009 given rules.
This section uses redrafted law revision using ISO /IEC 25012.2008 "software engineering software product quality requirements and evaluation
(SQuaRE) Data Quality Model ", the main technical differences compared with ISO /IEC 25012.2008 are as follows.
--- On the normative references, this section made a technical difference with the adjustment to adapt to China's technical conditions, adjust the situation
Concentration reflected in the second chapter "Normative references", the specific adjustments are as follows.
● Replace ISO /IEC 25000 with GB/T 25000.1-2010 that uses the same international standard.
--- In order to maintain the terminology and ISO /IEC 25024.2015 "Systems and software engineering systems and software quality requirements and evaluation
(SQuaRE) data quality measurement "consistency, with reference to ISO /IEC 25024.2015 for this section 4.1, 4.2, 4.7,
4.10,4.14 revised.
This section made the following editorial changes.
--- According to the latest SQuaRE series of international standards norms, with reference to ISO /IEC 25024.2015 Introduction to SQuaRE
A series of international standards introduced was revised.
--- According to the latest SQuaRE series of international standards, this part of the standard name has been modified.
Please note that some of this document may be patentable. The issuing agencies of this document do not bear the responsibility of identifying these patents.
This part of the National Information Technology Standardization Technical Committee (SAC/TC28) and focal point.
This part of the drafting unit. Wanda Information Co., Ltd., Fudan University, China Merchants Bank Co., Ltd., Dongguan City, Yakang Precision Machinery
Co., Ltd., Foshan Covey Optoelectronics Co., Ltd., Zhuhai Li Zhun Electronic Technology Co., Ltd., China Electronics Standardization Institute, China
Mobile (Shenzhen) Co., Ltd., National Application Software Product Quality Supervision and Inspection Center, Shanghai Computer Software Technology Development Center, Shanghai Hong Di
Information Technology Co., Ltd., CMB Silver Cloud (Shenzhen) Information Technology Co., Ltd., Shanghai Software Testing Center Co., Ltd., Chongqing Software Review
Test Center Co., Ltd., Sichuan Province Software and Information System Engineering Evaluation Center, Zhejiang Province, the inspection of electronic information products, Hubei Software Review
Heart, Fujian Provincial Supervision and Inspection of Electronic Products, Jilin Province Institute of Electronic Information Products Supervision and Inspection.
The main drafters of this section. Li Guangya, Wu Yijian, QIAN Leqiu, Zhao Wenyun, Zhang Yijun, Chen Cheng, Xiao Xiaohua, Wang Zhipeng, Liu Xiaojian, Cai Lizhi,
Gao Xulei, Xu Hongjun, Jia Jungang, Shu Mingen, Li Li, He Zhiming, Zhou Qingyun, Meng Yan, He Zhifeng, Zhang Kai, Luo Guoxiang, Hu Yun, Wang Wei, Chen Zhenyu,
Ding Xiaoming, Feng Li, Ji Yong Wei, Xia Qiming, Liu Yu Long, Xin Shi sector.
Introduction
The amount of data and information processed by computer systems is growing worldwide; data quality is the quality of the information derived from these data
And the key element of usefulness, most business processes rely on data quality.
A common prerequisite for all information technology projects is that between the computer system and the user and between the computer systems themselves
The quality of the data exchanged, processed and used.
It is important to manage and improve data quality because of this.
- Obtaining data from an organization of unknown or poor quality in the data production process;
--- There are flawed data, resulting in unsatisfactory information, useless results and customer dissatisfaction;
--- This data spread between different owners and users, according to a single organization's workflow needs to obtain the data often lack of
A consistent and integrated view necessary to ensure interoperability and cooperation;
--- Need to deal with due to semantic ambiguity or lack of consistency with other existing relevant data can not be directly reused
data;
--- legacy architecture and the coexistence of computer systems, these computer systems included in different periods, according to different standards and design
The present distributed system;
--- Existing information systems (such as the World Wide Web) data changes frequently, the integration has become a particularly important issue.
The data quality model as defined in this section is designed to meet these requirements and takes into account that data life cycles are generally more than software life cycles
long. This data quality model can be used in the following example aspects.
- Define and evaluate data quality requirements in data production, acquisition, and integration;
--- Identify data quality assurance guidelines, but also conducive to data reengineering, assessment and improvement;
--- Evaluation of data and legal and (or) compliance requirements.
Detecting errors or inefficiencies caused by data brings improvements and corrective interventions for other components of the system in which the data and data reside,
Here is an example.
--- Data (such as redesigning, analyzing, arranging, adding, converting, matching);
--- Software (for example, modify the source code to achieve consistency of control);
--- Hardware (eg upgrade computer system to improve response time);
--- human business processes (such as training of users to avoid errors in the data entry process; improve the accounting data management).
The data quality model as defined in this section is intended for use with other standards in the SQuaRE family of standards.
Figure 1 SQuaRE series of international standards organizations
The SQuaRE series of international standards consists of five main and expansion divisions, as shown in Figure 1 (rewritten from ISO /IEC 25000.
2005). An overview of each division in the SQuaRE series of standards is as follows.
--- ISO /IEC 2500n --- Quality Management Division. The standards that make up this division are defined by the SQuaRE series of standards
There are all the common models, terms and definitions referenced by other standards. This division also provides for planning and managing a project
Needs and guidelines.
--- ISO /IEC 2501n --- Quality Model Division. The criteria that make up this division are quality of use, data, and systems or software
The product provides a quality model. Quality of service is under development. A practical guide to using this quality model is also provided.
--- ISO /IEC 2502n --- Quality Measurement Division. The criteria that make up this division include a reference to quality measurement of the system or software product
Model, the definition of quality measurement and its practical guide. This division gives the system and software product quality measurement, use
Quality measures and data quality measures for "native" and "system-dependent" views. Definition and gives the composition of the quality test
The basic quality measure element.
--- ISO /IEC 2503n --- Quality Requirements Division. The criteria that make up this division help users set quality requirements. These qualities
The requirements are available in the quality requirements extraction process (designing a process that achieves the necessary quality) for the system or software product to be developed
Or as input to the evaluation process.
--- ISO /IEC 2504n --- Quality Evaluation Division. The criteria that make up this division are given by either the independent evaluator or the buyer
Is a requirement, recommendation, and guideline for system or software product evaluation performed by the developer. Also given as the quality of the evaluation module
Measure preparation support.
ISO /IEC 25050 ~ ISO /IEC 25099 is reserved for use with SQuaRE to expand international standards, currently including ISO /IEC 25051 and
ISO /IEC 25060 ~ ISO /IEC 25069.
Systems and software engineering systems and software quality requirements and
Evaluation (SQuaRE) Part 12. Data Quality Model
1 Scope
GB/T 25000 of this part of the computer system for a structured form of data stored in the definition of a common data quality
model.
This section focuses on the quality of data as an integral part of a computer system and defines the target data used by people and systems
Quality characteristics.
The target data is those data that the organization decides to analyze and confirm through this model. Non-target data includes two situations
Non-persistent data, such as data processed by the operating system; The second refers to the scope of this section, but the organization does not use this section into
Line analysis and evaluation of the data.
The structure of a general system is shown in Figure 2. The system can contain an information system which in turn can contain one or more gauges
Computer system.
Figure 2 Data Quality Model's target domain
This section can be used with other SQuaRE series of standards to establish data quality requirements, define data quality measures or plan and
Implement data quality assessment.
Data quality requirements and data quality measures can be categorized according to the data quality characteristics in 5.2 and determined by the evaluation process independently of the others
The way computer components are used to analyze data.
This section aims to support the realization of the system life cycle process (as defined in ISO /IEC 15288).
This section considers all data types (such as strings, text, dates, numbers, images, sounds, etc.), assigned data values, and data
(Eg, consistency between data in the same entity or in different entities); the scope does not include embedded devices or real-time sensors
Generated, not retained for further processing or as historical information data.
This section does not provide for the physical organization of the data (ie, database management system); in addition, conceptual, logical and physical model design activities
Nor is it within the scope of this section; all handling and deliverables related to such data may benefit from the application of this section.
Compliance with data and data design is covered by this section.
This section refers to the evaluation of data quality metadata, but the definition of metadata by the GB/T 18391.1 clarified.
|