Requirements on Execution Management, No.720, AUTOSAR R21-11  (22) AP

Requirements on Execution Management, No.720, 2021-11

https://www.autosar.org/fileadmin/standards/adaptive/21-11/AUTOSAR_RS_ExecutionManagement.pdf

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

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

# 用語(terms)

|Term| Description|
|:----|:----|
|process| A process refers to the OS concept of a running process. Attention: process is not equal to Modelled Process (see below). Hence each Modelled Process has at some time a related (OS) process but a process may not always have a related Modelled Process.|
|Modelled Process| A Modelled Process is an instance of an Executable to be executed on a Machine.|
|Execution Dependency| Dependencies between Executable instances can be configured to define a sequence for starting and terminating them.|
|Execution Management| The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.|
|State Management| The element defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at any given time.|
|Identity and Access Management (IAM)| A Adaptive Platform Service within the AUTOSAR Adaptive Platform|
|Function Group|A Function Group is a set of coherent Modelled Processes, which need to be controlled consistently. Depending on the state of the Function Group, processes (related to the Modelled Processes) are started or terminated. processes can belong to more than one Function Group State (but at exactly one Function Group). MachineFG is a Function Group with a predefined name, which is mainly used to control Machine lifecycle and processes of platform level Applications. Other Function Groups are sort of general purpose tools used (for example) to control processes of user level Applications.|
|Function Group State| The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States is machine specific and are configured in Machine Manifest.|
|Machine State| A state of Function Group "MachineFG" with some predefined states (Startup/Shutdown/Restart). This can term can refer to the current state ("The Machine State is ..."), to a specific state("In Machine State Startup ..."), or to a set of states ("In Machine States Startup or Shutdown ...").|
|Time Determinism| The results of a calculation are guaranteed to be available before a given deadline.|
|Data Determinism| The results of a calculation only depend on the input data and are reproducible, assuming a given initial internal state.|
|Full Determinism| Combination of Time and Data Determinism.|
|Communication Management| A Functional Cluster within the Adaptive PlatformFoundation|
|Execution Manifest| Manifest file to configure execution of an Adaptive Application. An Execution Manifest is created at integration time and deployed onto a Machine together with the Executable to which it is attached. It supports the integration of the Executable code and describes the configuration properties (startup parameters, resource group assignment etc.) of each process, i.e. started instance of that Executable.|
|Machine Manifest| Manifest file to configure a Machine. The Machine Manifest holds all configuration information which cannot be assigned to a specific Executable or process.|
|Operating System| Software responsible for managing processes on a Machine and for providing an interface to hardware resources.|
|ResourceGroup| Configuration element to enable restrictions on resources uses by Adaptive Applications running in the group.|
|ExecutionClient| Adaptive Application interface to Execution Management.|
|DeterministicClient|Adaptive Application interface to Execution Management to support control of the process-internal cycle, a deterministic worker pool, activation time stamps and random numbers.|
|Platform Health Management| A Functional Cluster within the Adaptive Platform Foundation|
|Recovery Action| Actions defined by the integrator to control Adaptive Application error recovery.|
|Process State| Lifecycle state of a Modelled Process|
|Service Instance Manifest| Manifest file to configure Service usage of an AdaptiveApplication.|
|Trusted Platform| An execution platform supporting a continuous chain of trust from boot through to application supporting authentication (that all code executed is from the claimed source) and integrity validation (that prevents tampered code/data from being executed).|

## 英日
日本語は仮訳

|no.|count|word|日本語|
|:----|:----|:----|:----|
|1|173|the|その|
|2|156|rs_main_|rs_main_|
|3|153|of|の|
|4|144|management|管理|
|5|125|execution|実行|
|6|111|and|と|
|7|110|autosar|AUTomotive Open System Architecture(短縮名)|
|8|106|to|に|
|9|94|shall|しなければならない|
|10|93|rs_em_|rs_em_|
|11|64|for|にとって|
|12|61|a|一つの|
|13|53|requirements|要件|
|14|52|support|支援|
|15|50|on|の上|
|16|48|process|処理する|
|17|46|be|です|
|18|44|rs_em_na|rs_em_na|
|19|41|document|資料|
|20|40|platform|土台|
|21|39|is|です|
|22|38|in|の|
|23|37|processes|過程|
|24|35|adaptive|適応|
|25|32|an|と|
|26|32|this|これ|
|27|31|state|状態|
|28|29|that|それ|
|29|27|description|説明|
|30|27|machine|機械|
|31|27|or|また|
|32|26|by|に|
|33|25|r|r|
|34|24|are|それは|
|35|24|provide|提供|
|36|23|executable|実行可能|
|37|23|not|いいえ|
|38|22|applications|応用|
|39|22|use|使用する|
|40|21|ap|adaptive platform(短縮名)|
|41|21|autosar_rs_execution|autosar_rs_execution|
|42|21|dependencies|依存関係|
|43|21|id|identifier, 識別子(短縮名）|
|44|21|material|材料|
|45|21|supporting|支援|
|46|20|application|応用|
|47|20|case|場合|
|48|20|down|下|
|49|20|software|ソフトウェア|
|50|19|c|c|
|51|19|d|d|
|52|19|manifest|管理票|
|53|19|startup|起動|
|54|18|rationale|理論的根拠|
|55|18|shut|閉める|
|56|17|function|働き|
|57|16|can|できる|
|58|16|glossary|用語集|
|59|15|communication|通信|
|60|15|draft|下書き|
|61|15|group|班|
|62|15|see|見る|
|63|14|access|接続|
|64|14|from|から|
|65|14|release|開放|
|66|14|which|どれの|
|67|13|activities|活動|
|68|13|data|与件|
|69|13|functional|機能的|
|70|13|means|意味|
|71|13|time|時間|
|72|12|it|それ|
|73|12|may|かもしれない|
|74|12|modelled|模型にした|
|75|12|safety|安全性|
|76|11|any|どれか|
|77|11|as|なので|
|78|11|requirement|要件|
|79|11|service|奉仕|
|80|11|specification|仕様|
|81|11|with|と|
|82|11|work|仕事|
|83|10|lifecycle|輪廻|
|84|10|only|それだけ|
|85|10|specific|明確|
|86|10|system|系|
|87|10|used|使った|
|88|9|at|で|
|89|9|based|基づく|
|90|9|e|e|
|91|9|instance|実例|
|92|9|interface|界面|
|93|9|running|走行中|
|94|9|runtime|実行時|
|95|8|all|すべて|
|96|8|between|の間に|
|97|8|configuration|構成|
|98|8|control|制御|
|99|8|ensure|確認|
|100|8|information|情報|
|101|8|other|他の|
|102|8|rs_saf_|rs_saf_|
|103|8|set|設定する|
|104|8|should|したほうがいい|
|105|8|started|始めた|
|106|8|starting|起動|
|107|8|their|彼らの|


# 参照(reference)

[1] Standardization Template, AUTOSAR_TPS_StandardizationTemplate
[2] Glossary, AUTOSAR_TR_Glossary
https://www.autosar.org/fileadmin/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf
[3] Specification of Manifest, AUTOSAR_TPS_ManifestSpecification
[4] Safety Requirements for AUTOSAR Adaptive Platform and AUTOSAR Classic Platform, AUTOSAR_RS_Safety
[5] Explanation of Safety Overview, AUTOSAR_EXP_SafetyOverview
[6] Requirements of State Management, AUTOSAR_RS_StateManagement
[7] Main Requirements, AUTOSAR_RS_Main