|
US$779.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GBZ33013-2016: Road vehicles -- Development guidelines for motor vehicle embedded software
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/Z 33013-2016 | English | 779 |
Add to Cart
|
5 days [Need to translate]
|
Road vehicles -- Development guidelines for motor vehicle embedded software
| Valid |
GB/Z 33013-2016
|
PDF similar to GBZ33013-2016
Basic data | Standard ID | GB/Z 33013-2016 (GB/Z33013-2016) | | Description (Translated English) | Road vehicles -- Development guidelines for motor vehicle embedded software | | Sector / Industry | National Standard | | Classification of Chinese Standard | T36 | | Word Count Estimation | 39,332 | | Date of Issue | 2016-10-13 | | Date of Implementation | 2017-01-01 | | Regulation (derived from) | National Standard Notice No.1716 of 2016 | | Issuing agency(ies) | General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China | GBZ33013-2016: Road vehicles -- Development guidelines for motor vehicle embedded software---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.
(Development Guide for Embedded Software for Road Vehicles)
ICS 43.040.10
T36
People's Republic of China national standardization of technical guidance documents
Road vehicles with embedded software development guide
(ISO /T R15497.2000, Roadvehicles-
Developmentguidelinesforvehiclebasedsoftware, NEQ)
2016-10-13 released
2017-01-01 implementation
General Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
China National Standardization Administration released
Directory
Foreword Ⅲ
1 Scope 1
2 Normative references 1
3 software life cycle 1
3.1 Automotive Software Design Guidelines 1
3.2 Project Plan 1
3.3 Integrity 5
3.4 Requirements Specification 11
3.5 Design 17
3.6 Programming 24
3.7 Test 25
3.8 Product Support 27
4 Software Quality Plan 28
4.1 Management responsibilities 28
4.2 Education and Experience 29
4.3 software development of human factors 29
4.4 Software Quality Assurance 30
4.5 Documentation Requirements 32
Subcontracting 32
References 36
Foreword
This instructional document has been drafted in accordance with the rules given in GB/T 1.1-2009.
This Guidance Document uses the Redrafted Law Reference ISO /T R15497.2000 "Road Vehicles Embedded Software Development for Vehicles
South ", the degree of consistency with ISO /T R15497.2000 is not equivalent.
The main differences between this guidance document and ISO /T R15497.2000 are as follows.
--- The integrity level by the concept of ISO /T R15497.2000MISRA "Safety Integrity Level" instead of ISO 26262
Related concepts and their hierarchical tables;
--- Reference ISO 26262 to increase the concept of severity parameters and forms;
--- Reference ISO 26262 increase the exposure rate of the concept of parameters and forms;
--- Removed foreign laws and regulations and related issues that are not applicable;
--- Remove some abbreviations.
This Guidance Document is proposed by the National Development and Reform Commission.
The guidance of technical documents by the National Automotive Standardization Technical Committee (SAC/TC114) centralized.
The drafting of the guidance of technical documents. China Electronics Standardization Institute, Shanghai Computer Software Technology Development Center, China Automobile
Vehicle Technology Research Center.
The main drafters of this technical guidance document. Zhang Zhanxin, Ding Zhigang, Xu Xiu Hong.
Road vehicles with embedded software development guide
1 Scope
This guidance document defines the process of developing road vehicles software and related requirements.
This guidance document is applicable to the development, verification and management of road vehicle software.
2 Normative references
The following documents for the application of this document is essential. For dated references, only the dated version applies to this article
Pieces. For undated references, the latest edition (including all amendments) applies to this document.
GB/T 19001-2008 quality management system requirements (ISO 9001.2008, IDT)
Guidance for use in computer software GB/T 19001-2000.
2004, IDT)
ISO 26262-3.2004 Road vehicles functional safety Part 3. Program phase definition (Roadvehicles-Functional
safety-Part 3.Conceptphase)
3 software life cycle
3.1 Automotive Software Design Guidelines
Design criteria for automotive software security are as follows.
a) Safety must be clearly visible.
b) The greater the risk, the more information you need to provide.
c) The robustness, reliability and security of the software, as well as quality, should be built-in rather than additional.
d) Personal safety must be given priority when conflicts between personal and property safety requirements arise.
e) The system design should consider both random and systematic faults.
f) Whether or not there is failure, its robustness should be demonstrated.
g) Safety considerations should apply to every stage of the design, manufacture, operation, service and disposal of the entire product.
3.2 project plan
3.2.1 Project Definition
3.2.1.1 There are many benefits to using software in terms of cost, flexibility and functionality. However, due to the complexity of the software will cause a lot of questions
The problem is that software will only be included in the system if these benefits are really needed.
3.2.1.2 The method specified in this chapter can be applied to both the vehicle system layer and the software system layer.
3.2.1.3 Before starting the project, a clear project goal should be set.
Example. The goal of a mass-production system is different from that of researching and developing prototype products.
3.2.1.4 The project definition should contain a list of the features and functions to be implemented. Relevant departments of automobile manufacturers should reach an agreement and formulate documents,
Making it possible for the design and development team to use this definition before beginning a specific job.
3.2.1.5 The project definition should include any existing regulatory requirements, project ideas, and non-functional requirements.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GBZ33013-2016_English be delivered?Answer: Upon your order, we will start to translate GBZ33013-2016_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 GBZ33013-2016_English with my colleagues?Answer: Yes. The purchased PDF of GBZ33013-2016_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.
|