没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
Safety Requirements for AUTOSAR Adaptive
Platform and AUTOSAR Classic Platform
AUTOSAR FO R20-11
Document Title
Safety Requirements for
AUTOSAR Adaptive Platform
and AUTOSAR Classic Platform
Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 986
Document Status published
Part of AUTOSAR Standard Foundation
Part of Standard Release R20-11
Document Change History
Date Release Changed by
Description
2020-11-30 R20-11
AUTOSAR
Release
Management
• Initial release
• Functional safety requirements for
the AUTOSAR Adaptive Platform
• Technical safety requirements for
PHM, EM, SM, OS, PER, CM and
UCM
1 of 27 Document ID 986: AUTOSAR_RS_Safety
Safety Requirements for AUTOSAR Adaptive
Platform and AUTOSAR Classic Platform
AUTOSAR FO R20-11
Disclaimer
This work (specification and/or software implementation) and the material contained in
it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the
companies that have contributed to it shall not be liable for any use of the work.
The material contained in this work is protected by copyright and other types of intel-
lectual property rights. The commercial exploitation of the material contained in this
work requires a license to such intellectual property rights.
This work may be utilized or reproduced without any modification, in any form or by
any means, for informational purposes only. For any other purpose, no part of the work
may be utilized or reproduced, in any form or by any means, without permission in
writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.
2 of 27 Document ID 986: AUTOSAR_RS_Safety
Safety Requirements for AUTOSAR Adaptive
Platform and AUTOSAR Classic Platform
AUTOSAR FO R20-11
Table of Contents
1 Scope of Document 4
2 How to Read This Document 4
2.1 Requirements Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2.1 Requirement Identifier Coding . . . . . . . . . . . . . . . . . 5
3 Acronyms and abbreviations 7
4 Requirements Specification 7
4.1 Top Level Safety Requirements and Safety Goals . . . . . . . . . . . . 7
4.2 Functional Safety Requirements . . . . . . . . . . . . . . . . . . . . . . 9
4.3 Technical Safety Requirements . . . . . . . . . . . . . . . . . . . . . . 14
4.3.1 AUTOSAR AdaptivePlatform . . . . . . . . . . . . . . . . . . 14
4.3.1.1 Functional Cluster: Platform Health Management
(PHM) . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.1.2 Functional Cluster: Execution Management (EM) . . 17
4.3.1.3 Functional Cluster: State Management (SM) . . . . 18
4.3.1.4 Operating System (OS) . . . . . . . . . . . . . . . . 19
4.3.1.5 Functional Cluster: Persistency (PER) . . . . . . . . 20
4.3.1.6 Functional Cluster: Communication Management (CM) 21
4.3.1.7 Functional Cluster: Update and Configuration Man-
agement (UCM) . . . . . . . . . . . . . . . . . . . . . 23
5 Requirements Tracing 24
6 References 26
3 of 27 Document ID 986: AUTOSAR_RS_Safety
Safety Requirements for AUTOSAR Adaptive
Platform and AUTOSAR Classic Platform
AUTOSAR FO R20-11
1 Scope of Document
This document specifies safety requirements on the AUTOSAR Platform, the
AUTOSAR Adaptive Platform in particular. This document elaborates the high level
safety requirements written in RS_Main. It makes use of the intended functionality
described in EXP_PlatformDesign document. The functional safety requirements are
derived from the safety goals and hazards mentioned in EXP_SafetyOverview. Tech-
nical safety requirements towards the AUTOSAR functional cluster and safety relevant
applications are derived from the functional safety requirements.
The AUTOSAR Classic Platform is not in scope.
No ASIL Ratings
The AUTOSAR consortium, especially the AUTOSAR Adaptive Platform Working
Groups are only providing an architecture definition, descr iptions of the functional
blocks and a proof of concept implementation, it is not possible to add an ASIL rat-
ing to any requirement in this scope as described in ISO26262[1].
2 How to Read This Document
This document contains functional safety requirements which are generic and do not
mention specific solutions/components of AUTOSAR. The technical safety require-
ments are then derived from functional safety requirements, which mention the specific
responsibilities of AUTOSAR components. Each requirement has its unique identifier
starting with the prefix "RS_SAF_" (for "Safety Requirement").
2.1 Requirements Guidelines
The representation of requirements in AUTOSAR documents follows the table spec-
ified in [TPS_STDT_00078], see Standardization Template [2], chapter Support for
Traceability.
The verbal forms for the expression of obligation specified in [TPS_STDT_00053] shall
be used to indicate requirements, see Standardization Template [2], chapter Support
for Traceability.
4 of 27 Document ID 986: AUTOSAR_RS_Safety
Safety Requirements for AUTOSAR Adaptive
Platform and AUTOSAR Classic Platform
AUTOSAR FO R20-11
2.2 Conventions used
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as follows, based on [3].
Note that the requirement level of the document in which they are used modifies the
force of these words.
• MUST: This word, or the adjective "LEGALLY REQUIRED", means that the defi-
nition is an absolute requirement of the specification due to legal issues.
• MUST NOT: This phrase, or the phrase "MUST NOT", means that the definition
is an absolute prohibition of the specification due to legal issues.
• SHALL: This phrase, or the adjective "REQUIRED", means that the definition is
an absolute requirement of the specification.
• SHALL NOT: This phrase means that the definition is an absolute prohibition of
the specification.
• SHOULD: This word, or the adjective "RECOMMENDED", means that there may
exist valid reasons in particular circumstances to ignore a particular item, but the
full implications must be understood and carefully weighed before choosing a
different course.
• SHOULD NOT: This phrase, or the phrase "NOT RECOMMENDED", means that
there may exist valid reasons in particular circumstances when the particular be-
havior is acceptable or even useful, but the full implications should be understood
and the case carefully weighed before implementing any behavior described with
this label.
• MAY: This word, or the adjective "OPTIONAL", means that an item is truly op-
tional. One vendor may choose to include the item because a particular market-
place requires it or because the vendor feels that it enhances the product while
another vendor may omit the same item.
An implementation, which does not include a particular option, SHALL be prepared
to interoperate with another implementation, which does include the option, though
perhaps with reduced functionality. In the same vein an implementation, which does
include a particular option, SHALL be prepared to interoperate with another implemen-
tation, which does not include the option (except, of course, for the feature the option
provides.)
2.2.1 Requirement Identifier Coding
The unique identifier for safety requirements shall consist of
• a document identifier
5 of 27 Document ID 986: AUTOSAR_RS_Safety
剩余26页未读,继续阅读
资源评论
- Jia_blog2022-03-23用户下载后在一定时间内未进行评价,系统默认好评。
电动汽车控制与安全
- 粉丝: 254
- 资源: 4273
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 基于matlab开发的全面详解LTE:MATLAB建模、仿真与实现-simulink.rar
- 自动驾驶定位系列教程二:系统架构.pdf
- 整站程序8优技巧网-8ujq.rar
- 世界各个国家或地区国际域名缩写
- 基于matlab开发的根据rvm回归模型自己编的matlab程序.rar
- 基于matlab开发的该程序为国内一所大学编写的LTE链路层仿真程序,根据LTE标准协议编写的,很容易看懂.rar
- 高效C++学生成绩管理系统:教育技术+C++17编程+数据管理+教务自动化
- 搜索链接要广告分类系统 v2.0-yad20.rar
- 基于matlab开发的Tipping的相关向量机RVM的回归MATLAB程序,有英文注释,可以运行.rar
- 一个点击正反转程序实例,可实现案件电机正反转
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功