GB/Z 33013-2016Road vehicles - Development guidelines for motor vehicle embedded software (English PDF)
道路车辆 车用嵌入式软件开发指南
This is a limited preview
Buy now to download the full PDF (36 pages)
Need quotation for your management?
Get a formal quotation for GB/Z 33013-2016 in 30 minutes.
Issued by
SAMR; SAC
Level / Type
National · Recommended
Issue date
October 13, 2016
Implementation date
October 13, 2016
Scope
GB/Z 33013-2016 is the English-translated version of 道路车辆 车用嵌入式软件开发指南.
GB/Z 33013-2016 is a guidance document, not a mandatory standard, that sets out a development process and the accompanying requirements for embedded software used in road vehicles.
It is a redrafted, non-equivalent adaptation of ISO/TR 15497:2000, with the integrity level concept and the severity and exposure parameters rebuilt around ISO 26262 instead of the original MISRA safety integrity levels.
The document follows the software life cycle, covering automotive software design criteria, project planning, integrity, requirements specification, design, programming, testing and product support, then adds a software quality plan addressing management responsibility, education and experience, human factors, quality assurance, documentation and subcontracting.
Clause 1 states that it applies to the development, verification and management of road vehicle software. It was issued on 13 October 2016.
Found what you need?
Document preview — GB/Z 33013-2016
National Standard of the People's Republic of China
- ICS
- 43.040.10
- Classification
- T 36
Issued by: State Administration for Market Regulation; Standardization Administration of the PRC
Contents
- Foreword
- 1 Scope
- 2 Normative references
- 3 software life cycle
- 3.1 Automotive Software Design Guidelines
- 3.2 Project Plan
- 3.3 Integrity
- 3.4 Requirements Specification
- 3.5 Design
- 3.6 Programming
- 3.7 Test
- 3.8 Product Support
- 4 Software Quality Plan
- 4.1 Management responsibilities
- 4.2 Education and Experience
- 4.3 software development of human factors
- 4.4 Software Quality Assurance
- 4.5 Documentation Requirements
- 4.6 Subcontracting
- References
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.
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 document. 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.
......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 36 pages — is available in the English PDF.
Referenced standards
Similar standards
How to Download GB/Z 33013-2016
- 1
Add to cart
Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.
- 2
Checkout
Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).
- 3
Fast delivery
After payment you'll receive an email confirmation. The English PDF is sent to the same address, usually within minutes and at the latest within 1 business day.
- 4
Invoice included
A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.
Related Standards
GB/T 19001-2008 — [Replaced by GB/T 19001-2016] Quality management systems - Requirements [including MODIFICATION 1]
GB/Z 102.17-2026 — Semiconductor devices - Discrete devices - Part 17: Magnetic and capacitive coupler for basic and reinforced insulation
GB/Z 103-2026 — Health informatics - The architecture of internet healthcare service network
GB/Z 33013-2016
$510.00