GB/T 32422-2015 English PDF

US$569.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 32422-2015: Software engineering -- Guideline of classification for software anomalies
Status: Valid

Standard ID	USD	BUY PDF	Lead-Days	Standard Title (Description)	Status
GB/T 32422-2015	569	Add to Cart	5 days	Software engineering -- Guideline of classification for software anomalies	Valid

Similar standards

GB/T 39788   GB/T 39099   GB/T 25000.51   GB/T 32423   GB/T 32421   

Basic data

Standard ID: GB/T 32422-2015 (GB/T32422-2015)
Description (Translated English): Software engineering -- Guideline of classification for software anomalies
Sector / Industry: National Standard (Recommended)
Classification of Chinese Standard: L77
Classification of International Standard: 35.080
Word Count Estimation: 27,283
Date of Issue: 2015-12-31
Date of Implementation: 2016-07-01
Regulation (derived from): State Standard Announcement 2015 No.43
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 32422-2015: Software engineering -- Guideline of classification for software anomalies

---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.
Software engineering - Guideline of classification for software anomalies ICS 35.080 L77 National Standards of People's Republic of China Software engineering software anomalies Classification Guidelines Issued on. 2015-12-31 2016-07-01 implementation Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China Standardization Administration of China released

Table of Contents

Introduction Ⅲ Introduction Ⅳ 1 Scope 1 2 Normative references 1 3 Terms and definitions 4 abnormalities and problems, software changes the relationship 2 Relationship problems and failures 3 4.1 4.2 Relationship between failure and failure of 3 4.3 Relationship between faults and defects 3 4.4 Defects relationship with change requests 3 5 Classification Guidelines 4 5.1 points classification and step 4 5.2 classification process 4 6 Category 5 property 6.1 Defect Classification properties 5 6.2 Failure Classification properties 5 Classification property values \u200b\u200bin Appendix A (normative) defect 7 Appendix B (normative) failure classification attribute value 16 Annex C (informative) Classification Example 19 References 21

Foreword

This standard was drafted in accordance with GB/T 1.1-2009 given rules. This standard by the National Information Technology Standardization Technical Committee (SAC/TC28) and focal points. This standard was drafted. Shanghai computer software technology development center, China Electronics Standardization Institute, Shenzhen Ji Yang Automation Technology Co., Ltd. Liaoning North laboratories, the National Network Software Product Quality Supervision and Inspection Center (Jinan). The main drafters of this standard. Liu Zhenyu, Cai Lizhi, Liang Yong, Yang Ru-Kun, Huang Shanshan, Zheng Yang, Liu Wenjie, Li Haitao, Wu discipline, Guo Jun, Zhang Wen, phase Fumin, Zhang Xueli.

Introduction

Software during operation due to abnormal and cause the software to run properly. Whether or generate an exception when the software life cycle When it appears in the software anomaly classification guide provides a unified approach. Abnormal data can be applied to a variety of purposes, including cause analysis, project Management and software process improvement (for example. embedded defect reduction, or increase the probability of defect detection). In the software life cycle, the problems identified earlier, lower repair costs, more easily repaired. The standard encourages the use of various tools, techniques Qiao and methodology as early as possible to find the problem. This standard describes the data collection may provide valuable information that can be mentioned in many aspects For useful applications. Standardized anomaly data for assessing the effectiveness of tools, techniques and methodological work is necessary. Abnormal number It can determine the most problems in the software life cycle when introduced. Software optimization and discrepancies between the abnormality help solve. different Often data is also helpful in assessing quality attributes, such as reliability and productivity. Classification software anomalies in a number of important aspects of the application. First, the software product development process explicitly organizations (including enterprises, Departments, teams) to produce the type of abnormality. In the project implementation process or modification, abnormal classification is an abundant source of data. Orthogonal Cause analysis and defect classification techniques rely abnormal classified to determine its causes, by Capability Maturity Model integration process change Into the frame to help prevent recurrence of defects. For exceptions generated during project development, through to help classify abnormal properties Process improvement. Secondly, the standardized classification of such anomalies between developers and organizations to better communicate and carry out exceptionally letter Exchange of information. People often use the same words to express different meanings, or use different words to express the same thing. Similarly, as If the software in order to carry out efficient data communication abnormalities (such as the exchange of data), must share the same logical (rather than physical) data model. If the same data element in a software and another software named in different ways, by mapping or translation method can also exchange data Change, but at least every software to recognize and implement the same concept entities (objects), relationships, and attributes. An organization in the implementation of this standard procedure may be used to achieve the target, but it may involve additional details, different steps related organization. Software engineering software anomalies Classification Guidelines

1 Scope

This standard provides a software anomaly classification, classification attributes specified set of defects and failures. This standard applies to all phases of the software life cycle, the user can select the software life cycle model crop classification properties. Category attribute set specified in this standard is not complete, the user can increase the classification of property in accordance with a particular application or use.

2 Normative references

The following documents for the application of this document is essential. For dated references, only the dated version suitable for use herein Member. For undated references, the latest edition (including any amendments) applies to this document. GB/T 16260.1-2006 Software engineering - Product quality - Part 1. Quality model

3 Terms and Definitions

The following terms and definitions apply to this document. 3.1 Anomaly anomaly Viewed from any document or software to operate the event of deviation from the document previously validated software product or reference. [GB/T 11457.2006,2.64] 3.2 Category classification The object is assigned to a particular purpose mechanism. [GB/T 11457.2006,2.211] 3.3 Defect defect Work product defects or shortcomings appear, resulting in software products can not meet user requirements or specifications, or in need of repair replace. For example. omissions or shortcomings of the early stages of a) lifetime discovery; fault b) included in the software, because the software is not mature enough and the guide Caused by the operation is unsuccessful. [IEEEStd1044.2009, Chapter 2] 3.4 Error error Produce an incorrect result of human action. [IEEEStd1044.2009, Chapter 2] ......

Image     

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 32422-2015_English be delivered?

Answer: Upon your order, we will start to translate GB/T 32422-2015_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 32422-2015_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 32422-2015_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+ countries

Question 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 Sales@ChineseStandard.net. 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.