MISRA C 2020合规指南：中英对照版概述

需积分: 15 20 浏览量更新于2024-07-09 收藏 899KB PDF 举报

"MISRA Compliance 2020-中英对照版.pdf" MISRA C是针对C语言编程的一种编码标准，主要应用于关键系统，如汽车、航空和医疗设备等行业的软件开发。这个标准由MISRA（Motor Industry Software Reliability Association，汽车工业软件可靠性协会）制定，旨在提高代码的安全性和可维护性。 MISRA C规范包含了若干规则，这些规则涵盖了语法、类型系统、指针操作、内存管理、错误处理等多个方面，旨在防止常见的编程错误，减少潜在的漏洞，并促进代码的一致性和可读性。例如，它可能规定禁止使用某些可能导致未定义行为或难以调试的C语言特性，如悬挂指针、类型强制转换的滥用以及全局变量的过度使用。 "MISRA Compliance 2020" 是MISRA C的最新版本，它提供了对之前版本的更新和改进，以适应不断发展的编程环境和技术需求。2020版可能会包含新的指导原则，对旧规则的修订，以及对现代C语言特性的处理方法。实现MISRA C合规性通常涉及到以下步骤： 1. **代码审查**：通过静态代码分析工具或人工审核，检查代码是否符合MISRA C规则。 2. **例外管理**：对于无法满足的规则，需要记录并解释原因，确保这些例外不会引入风险。 3. **持续集成**：在开发过程中集成MISRA检查，确保新代码符合标准。 4. **培训**：让开发人员了解MISRA C规则，提高他们编写安全、可靠代码的能力。 5. **文档更新**：保持与MISRA C规则一致的开发过程和文档。 MISRA C的遵循不仅有助于提高软件质量，还有助于满足行业认证要求，如ISO 26262（汽车行业）和DO-178C（航空航天行业）。然而，需要注意的是，MISRA C并不是银弹，它不能解决所有安全问题，但它是提高软件安全性和可靠性的有力工具。在实际应用中，开发者可能会遇到如何权衡MISRA规则与项目特定需求的问题。例如，某些规则可能过于严格，不适用于所有情况，或者某些现代编程实践可能与MISRA C不完全兼容。在这种情况下，理解和灵活应用MISRA C成为关键，同时确保任何偏离都能得到充分的评估和控制。 "MISRA Compliance 2020" 是一个重要的资源，它为关键系统软件开发提供了全面的编码指南，帮助开发者遵循最佳实践，降低软件风险。对于那些涉及关键系统开发的组织，理解和实施MISRA C标准是至关重要的。

Contents 
目录 
1
  Introduction 简介 .............................................................................................................................. 12 
2
  The software development process 软件开发过程过程 .................................................................. 14 
2.1
  The development contract 开发协议 .................................................................................... 14 
2.2
  Framework 框架 .................................................................................................................... 14 
2.3
  Training 培训 .......................................................................................................................... 15 
2.4
  Style guide 样式指南 ............................................................................................................. 16 
2.5
  Metrics 度量 ........................................................................................................................... 16 
2.6
  Tool management 工具管理 ................................................................................................. 16 
3
  Fundamental elements of compliance 符合的基本要素 .................................................................. 23 
3.1
  Guideline classification 分类指南 .......................................................................................... 23 
3.2
  Analysis scope 分析范围........................................................................................................ 23 
3.3
  The guideline enforcement plan 指南实施计划 ................................................................... 23 
3.4
  Investigating messages 审查信息 .......................................................................................... 25 
3.5
  Decidability 判定 .................................................................................................................... 25 
4
  Deviations 偏差 .................................................................................................................................. 29 
4.1
  The role of deviations 偏差的作用 ........................................................................................ 29 
4.2
  Deviation records 偏差记录 .................................................................................................. 29 
4.3
  Deviation permits 偏差许可 .................................................................................................. 30 
4.4
  Justifying a deviation 判定一个偏差 ..................................................................................... 31 
5
  The guideline re-categorization plan 指南重新分类计划 ................................................................ 34 
5.1
  Re-categorization 重新分类 .................................................................................................. 34 
6
  Adopted Code 采用的代码 ............................................................................................................... 37 
6.1
  The nature of adopted code 采用的代码的性质 .................................................................. 37 
6.2
  System wide analysis scope 系统范围的分析范围............................................................... 38 
6.3
  Adopted binary code 采用的二进制代码 ............................................................................. 39 
6.4
  Adopted source code 采用的源代码 .................................................................................... 39 
6.5
  Adopted header files 采用的头文件 ..................................................................................... 40 
6.6
  The Standard Library 标准库 ................................................................................................. 41 
7
  Claiming MISRA compliance 声明符合MISRA .................................................................................... 42 
7.2
  The management process 管理过程 ..................................................................................... 42 
7.3
  The guideline compliance summary 指南符合性报告 .......................................................... 44 
7.4
  Project delivery 项目交付 ...................................................................................................... 47 
8  References 参考文档 ......................................................................................................................... 49 
Appendix A  Process and tools checklist 附录A:过程和工具检查表 ........................................................ 50 

Introduction 简介

The MISRA language documents [1] and [2] (“The Guidelines”) are compilations of guidelines for coding in the C

[3] and C++ [4] languages. They are widely used in the development of critical software systems when the

requirements of a quality standard must be met. Many software projects specify that code quality should be

assured by meeting the requirements of The Guidelines. However, the meaning of the phrase “MISRA compliant”

needs to be carefully defined.

MISRA语言文档[1]和[2]（“准则”）是使用C [3]和C ++ [4]语言进行编码的准则的汇编。当必须满足质量标

准的要求时，它们广泛用于关键软件系统的开发中。许多软件项目指定应通过满足准则的要求来确保代

码质量。但是，短语“符合MISRA”的含义需要仔细定义。

In order for a claim of MISRA compliance to have meaning, it is necessary to establish:

●

Use of a disciplined software development process;

●

Exactly which guidelines are being applied;

●

The effectiveness of the enforcement methods;

●

The extent of any deviations from the guidelines;

●

The status of any software components developed outside of the project.

为了使符合MISRA的要求有意义，有必要确定：

●使用严格的软件开发流程；

●确切地应用了哪些准则；

●执法手段的有效性；

●偏离准则的程度；

●项目外开发的任何软件组件的状态。

The Guidelines recognize that, in some situations, it is unreasonable or even impossible to comply with a coding

guideline and that it is necessary to deviate from its requirements. The freedom to deviate does not necessarily

compromise claims of compliance, but it does carry with it great responsibility. In the absence of a disciplined

development process, it is easy for that freedom to be abused. At best, that will undermine the credibility of any

claims of MISRA compliance; at worst, it will compromise code quality, safety or security. It is therefore important

to emphasize that a credible claim of compliance with The Guidelines can only be made when code is developed

under a process which meets the principles laid out in this document.

该准则认识到，在某些情况下，遵守编码准则是不合理的，甚至是不可能的，并且有必要偏离其要求。

偏离的自由并不一定会损害合规要求，但确实会带来巨大的责任。在没有纪律严明的发展过程的情况下，

这种自由很容易被滥用。充其量，这将损害对MISRA合规性提出的任何要求的信誉；最糟糕的是，它将

损害代码质量，安全性或安全性。因此，必须强调的是，只有在符合本文档中列出的原则的过程中开发

代码时，才能提出对本准则的可信声明。

The guidance given in this document supersedes the compliance, deviation and process requirements published

previously in the various MISRA Guidelines.

本文档中提供的指南取代了先前在各种MISRA指南中发布的合规性，偏差和过程要求。

Note: The various MISRA Guideline documents have been refined and revised over a number of years. This

document uses examples and extracts from a number of them, but the issues discussed are equally relevant to all

of The Guidelines.

注意：多年来，MISRA各种指南文件均已完善和修订。本文档使用示例和其中的一些摘录，但是讨论的

问题与所有《准则》都同样相关。

剩余59页未读，继续阅读

ShepherdQu

粉丝: 4
资源: 5

MISRA C 2020合规指南：中英对照版概述

最新资源