<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words in order.

Release Overviews

Classic Platform Release Overview, AUTOSAR No.0 ,R23-11, CP
https://qiita.com/kaizen_nagoya/items/8468435185e109189ead

Adaptive Platform Release Overview, AUTOSAR 782, R23-11, AP
https://qiita.com/kaizen_nagoya/items/13a104606a34fe24fcf7

term

Table 2.1: Acronyms and abbreviations used in the scope of this Document

Short Name (Abbreviation / Acronym)	Description:
Adaptive Application	see [1] AUTOSAR Glossary
ARTI	see [1] AUTOSAR Glossary
AUTOSAR Adaptive Platform	see [1] AUTOSAR Glossary
Executable	see [1] AUTOSAR Glossary
Execution Management [2]	The element of AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive Platform and Adaptive Applications.
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	see [1] AUTOSAR Glossary
Manifest	see [1] AUTOSAR Glossary
Modelled Process	A Modelled Process is an instance of an Executable to be executed on a Machine and has a 1:1 association with the ARXML/Meta-Model element Process. This document also uses the term process (without the “modelled” prefix) to refer to the OS concept of a running process.
Operating System	Software responsible for managing Processes on a Machine and for providing an interface to hardware resources.
Process	see [1] AUTOSAR Glossary
Task	see [1] AUTOSAR Glossary. In case of POSIX a task is called thread.

ver. 0.01初稿　　20231203

いいね　💚、フォローをお願いします。

Please press the like icon 💚　and follow me for your happy life.