Specification of Safety Extensions, No.671, AUTOSAR 21-11 (218) CP

Specification of Safety Extensions, No.671, 2021-11

https://www.autosar.org/fileadmin/standards/classic/21-11/AUTOSAR_TPS_SafetyExtensions.pdf


AUTOSAR R21-11記事一覧はこちら。

AUTOSAR 21-11, 200文書読んだ。2022年5月に全部到達。

https://qiita.com/kaizen_nagoya/items/4043e8414f850ce266a4

AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成

https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e

# 文書変更(Document Change) 


# 用語(terms)

|Term|Description|
|:--|:--|
|ASIL |Automotive Safety Integrity Level
|DC| Diagnostic Coverage
|ECC| Error Correction Code
|EDC |Error Detection Code
|HARA |Hazard Analysis and Risk Assessment
|HW |Hardware
|FSC |Functional Safety Concept
|TSC |Technical Safety Concept
|SEooC |Safety Element out of Context
|SM |Safety Mechanism or Measure
|SW |Software
|SWC| Software Component
|URI |Uniform Resource Identifier
|URL| Uniform Resource Locator
|ASIL attribute |The ASIL for elements of the system specify the necessary requirements of ISO 26262 and safety measures to apply for avoiding unreasonable residual risk. See section 5 for further details.
|Fault, Failure, Error |A fault is an abnormal condition that may cause an HW or SW element to fail. An error describes the resulting discrepancy in a  value or condition and is the consequence of a (set of) faults. A failure defines the termination of the ability of an HW or SW element to perform its function (see [3]). Faults comprise systematic SW faults (i.e. ”defects”, ”bugs”), random HW faults (e.g. due to stress/aging of the equipment) as well as systematic HW faults.
|Safe state| A safe state is always meant to be described on system level (see [3]). A certain software state may be part of this ”system state” or the relation might be undefined (e.g. if the microcontroller running the software is switched off in the safe state).
|Safety Mechanism |A safety mechanism is a technical solution [...], to detect faults or control failures in order to achieve or maintain a safe state (see [3]). The term is used in this specification exactly in this broader sense, so that not only the AUTOSAR safety mechanisms (”safety features”) can be described, but any HW/SW or combined solution of the system for which an AUTOSAR software is implemented (cp. section 7).
|Safety Measure| A safety measure is an activity or solution to avoid systematic failures and to detect random hardware failures or control failures (see [3]). Therefore, a safety measure might only define a process activity like dedicated testing methods, additional code verifications, and so on (cp. section 7). This specification will use the term safety measure to subsume both activities during development as well as safety measure implemented into the system.
|Safety Requirement| ISO 26262 defines a hierarchy of safety requirements: safety goals, technical, hardware and software. In this document a safety requirement could be any of these. For details refer to ISO 26262-3, 4 and 9.


## 英日単語帳
日本語は仮訳

T.B.D.

# 参考(reference)

[1] Requirements on Safety Extensions
AUTOSAR_RS_SafetyExtensions
[2] Standardization Template
AUTOSAR_TPS_StandardizationTemplate
[3] ISO 26262:2018 (all parts) – Road vehicles – Functional Safety
http://www.iso.org
[4] Methodology for Classic Platform
AUTOSAR_TR_Methodology