|
US$1239.00 ยท In stock Delivery: <= 9 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 37970-2019: Trustworthiness assessment for software process and artifact Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 37970-2019 | English | 1239 |
Add to Cart
|
9 days [Need to translate]
|
Trustworthiness assessment for software process and artifact
| Valid |
GB/T 37970-2019
|
PDF similar to GB/T 37970-2019
Basic data | Standard ID | GB/T 37970-2019 (GB/T37970-2019) | | Description (Translated English) | Trustworthiness assessment for software process and artifact | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 62,611 | | Date of Issue | 2019-08-30 | | Date of Implementation | 2020-03-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration |
GB/T 37970-2019: Trustworthiness assessment for software process and artifact---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.
Trustworthiness assessment for software process and artifact
ICS 35.080
L77
National Standards of People's Republic of China
Software process and product credibility assessment
Published on.2019-08-30
2020-03-01 implementation
State market supervision and administration
China National Standardization Administration issued
Content
Foreword III
Introduction IV
1 Scope 1
2 Normative references 1
3 Terms and definitions, abbreviations 1
3.1 Terms and Definitions 1
3.2 Abbreviations 3
4 Software credibility model 3
4.1 Model Overview 3
4.2 Software Process Credibility Principle 4
4.3 Software Products Trusted Principles 7
4.4 Software Process Credible Evidence 7
4.5 Software Products Certified Evidence 11
5 Software Credibility Level 17
5.1 Software Process Credibility Level 17
5.2 Software Product Credibility Level 18
6 Software Process Credibility Assessment 19
6.1 Software Process Credibility Assessment Process 19
6.2 Assessment of the credibility of process evidence 19
6.3 Credibility assessment of the credibility principle 20
6.4 Reliability Assessment of Software Processes 20
7 Software Product Credibility Assessment 20
7.1 Software Product Credibility Assessment Process 20
7.2 Assessment of the credibility of product evidence 20
7.3 Reliability evaluation of software products 21
Appendix A (informative) Trusted Principles and CMMI Process Area 22
Appendix B (Normative) Software Process Evidence 24
Appendix C (Normative) Software Product Evidence 39
Appendix D (informative) Software Trustworthiness Evaluation Example 52
Reference 56
Foreword
This standard was drafted in accordance with the rules given in GB/T 1.1-2009.
Please note that some of the contents of this document may involve patents. The issuing organization of this document is not responsible for identifying these patents.
This standard is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28).
This standard was drafted. Institute of Software, Chinese Academy of Sciences, China Electronics Technology Standardization Institute, Nanjing University, Chinese Academy of Sciences
Strategic Consulting Institute, Xiamen University of Technology, Shanghai Computer Software Technology Development Center, Chongqing University of Posts and Telecommunications, Beijing Tulsi Information Technology Unit
Co., Ltd., Ropute (Xiamen) Technology Group Co., Ltd., Beijing Know Future Information Technology Co., Ltd.
The main drafters of this standard. Wang Dandan, Wang Dexin, Liu Zengzhi, Lai Yiliang, Wei Qingjie, Wu Dengsheng, Hu Wei, Feng Zhichao, He Wei, Wang Linzhang,
Cui Jianfeng, Zhang Wei, Wang Qing.
Introduction
Quality is formed in the process. The basic problem of software credibility is the need to have evidence that software products can meet the needs of users, and these
The evidence is spread throughout the life cycle of software development. Therefore, whether the software is trustworthy cannot rely solely on the testing of the final product.
The evaluation and validation of the letter requires the support of various relevant evidence in the software development process. This standard is intended to be built from the perspective of software processes and products.
Establish a systematic credibility assessment model to guide software development to collect appropriate data in the process to form evidence and support evidence-driven
Software credibility assessment.
Software credibility is not a new quality feature, but a variety of quality characteristics such as software functionality, security, maintainability, reliability, etc.
A measure of the extent to which the demand is met. Inspired by the traditional industry's total quality management theory, this standard proposes a process-oriented approach, through attention
And improve the quality of the software development process to improve the credibility of the software. CMMI is a software process management framework widely adopted by the industry.
Currently running CMMIV1.3 includes 22 process areas, using the knowledge technology of the software development process to solve the software management process, emphasizing improvement
Software process capability to improve the maturity of the software process, thus helping the company to deliver the expected and stable budget on time to meet the user's needs
Seeking products.
In line with the criteria of international popular technology, it is proposed that the software process credibility principle covers 22 process areas of CMMIV1.3, and further expands
It is filled with the guarantee of the credible entity, and the product of the software process is credibly enhanced through the credibility principle of the product. Formed software process and
Product credible evidence system, decompose software quality into various stages and processes of software development, and collect process data with target to form coverage
The chain of evidence throughout the software development process and ultimately assess the credibility of the delivered software product to meet the expected quality objectives.
Software process and product credibility assessment
1 Scope
This standard specifies the models, credibility levels, and assessment methods used for software process and product credibility assessment.
This standard applies to organizations that develop software products to establish trusted software processes, collect data, and accumulate evidence to support software.
Confidence in product quality. It is also applicable to third-party evaluation and certification bodies to establish evaluation methods, and to target software products and their development organizations.
Exhibition third party assessment.
2 Normative references
The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article.
Pieces. For undated references, the latest edition (including all amendments) applies to this document.
GB/T 19001-2016 Quality Management System Requirements
GB/T 25000.10-2016 System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Part 10.
System and software quality model
GB/T 25000.23-2019 System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Part 23.
System and software product quality measurement
3 terms and definitions, abbreviations
3.1 Terms and definitions
GB/T 25000.10-2016, GB/T 25000.23-2019 and GB/T 19001-2016 define the following terms and definitions
Applicable to this document.
3.1.1
Process
A sequence of steps performed for a given purpose, for example, a software development process.
[GB/T 11457-2006, definition 2.1183]
3.1.2
Software process softwareprocess
A collection of processes or processes used by an organization or project to plan, manage, execute, monitor, and improve its software-related activities.
[GB/T 11457-2006, definition 2.1512]
3.1.3
Software development process wholeprocessofsoftwaredevelopment
Requirements, design, coding, and testing processes in software development.
Note. Compared with the development process defined in GB/T 11457-2006, in order to facilitate the classification of trusted indicators, the whole process of software development refers to requirements, design, coding.
And test four processes.
3.1.4
Product artifact
A physical piece of information used or generated by a software development process. Examples of artifacts are models, source files, text, and
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 37970-2019_English be delivered?Answer: Upon your order, we will start to translate GB/T 37970-2019_English as soon as possible, and keep you informed of the progress. The lead time is typically 6 ~ 9 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 37970-2019_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 37970-2019_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|