1 介绍 Introduction
1.1 目标和范围Objective and Scope
AUTOSAR 要求提供一种至少涵盖大部分开发步骤的技术方法，我们称之为 AUTOSAR 方法论。
AUTOSAR requires a common technical approach for at least the major development steps, called the AUTOSAR Methodology.
CP的方法论可以参考文献【1】，而我们这篇文章定义的是AP的方法论。
The methodology for the AUTOSAR Classic Platform is given by [1], whereas this document defines the methodology for the AUTOSAR Adaptive Platform.
相关的需求定义在文献【2】.
The corresponding requirements are defined in [2].
相比于CP,目前的扩展是必要的，因为AP引入了新的概念.
The present expansion was necessary, because the AUTOSAR Adaptive Platform has introduced new concepts.
相比于CP平台，AP软件的实例是由进程上下文执行（这些实体由操作系统统一管理）。如果操作系统的配置允许，进程可以在机器生命周期中的任何时间启动、执行或停止。结果就是，AP的配置方式（通过Manifest文件配置）和软件是何时以及怎样部署（例如软件更新通过OTA），这些概念和CP有明显区别。
In contrast to the AUTOSAR Classic Platform, instances of Adaptive Software, are executed within the context of processes (which are entities managed by the operating system). If permitted by the configuration of the operating system, processes may be started, executed or stopped, at any time during the life cycle of a Machine. As a consequence, the way of configuration (by the means of Manifests) or when and how software packages are deployed (e.g., by software updates over-the-air) clearly differ from the concepts of the AUTOSAR Classic Platform.
此外，“机器”这个术语也被引入到AP平台。“机器”类似虚拟化的硬件ECU,一个可以部署软件的实体。在这种情况下，一个真正的硬件ECU可以同时运行多个“机器”，尽管该方法论没有对其进行详细说明。最简单的情况下，“机器”和硬件ECU是1：1的映射关系。
Moreover, the term Machine has been newly introduced with the AUTOSAR Adaptive Platform. A Machine is quasi a virtualized ECU-HW, an entity where software can be deployed to. In this spirit, one real ECU-HW could run several Machines, even though the methodology will not detail this. In the simplest case there is a 1:1 mapping between a Machine and a ECU-HW.
虽然清单不完整，但上述方面足以为AP 平台提供一套独有的方法论。
Although the list is not complete, aforementioned aspects may serve as sufficient motivation to provide a separate methodology for the AUTOSAR Adaptive Platform.
尽管存在这些差异，但也有许多共同点，例如对系统特性(如拓扑或硬件功能)的描述。然而，为了避免重复，本文档将更侧重于AP的细节。两个平台的公共方面的规范可能会在后续单独的文档中(基础文档)体现。
Despite all the differences, there are also many commonalities, such as the description of the system features, like topologies or hardware capabilities. This document, however, will rather focus on the specifics of the AUTOSAR Adaptive platform, in order to avoid duplications. The specification of the common aspects of both platforms may be the subject of a separate document (foundation document) later.
[TR_AMETH_00100] AP方法论的范围 :该方法论描述了构建AP系统所需的主要方面(用例、任务、工作产品等)以及它们之间的相互关系。然而，该方法既没有提供完整的过程描述，也没有规定软件行为的精确顺序。活动的迭代是可能的，但是没有描述如何以及何时进行迭代。(RS_METH_00006, RS_METH_00020, RS_METH_00056)
[TR_AMETH_00100] Scope of the Methodology for the AUTOSAR Adaptive Platform dThe methodology for the AUTOSAR Adaptive Platform describes main aspects (use-cases, tasks, work products, ...) necessary to build an Adaptive AUTOSAR system and how they relate to each other. However, the methodology does neither provide a complete process description, nor does it stipulate a precise order of activities. Iterations of activities are possible, but it is not described how and when iterations shall be carried out.c(RS_METH_00006, RS_METH_00020, RS_METH_00056)
1.2 文档大纲 Document Outline
本文档将遵循AUTOSAR经典平台的策略，即如何对用例建模，如何构建文档以及如何进行详细说明。
This document will follow the policies of the AUTOSAR Classic Platform, i.e., the way how to model use-cases, how to structure the document and the way to specify.
因此，本文档的大纲大致遵循CP平台的对应章节:
Thus, the outline of this document follows roughly its counterpart of the AUTOSAR Classic Platform:
章节2（AP的用例）描述了实现AP系统的的主要用例。注意，软件包生命周期的描述并没有涵盖在本方法论中。
Section 2 (Use Cases for the Adaptive Platform) describes the major use cases for the development of a system implementing an AUTOSAR Adaptive Platform. Note that the description of the life cycle of a Software Package is not included in the AUTOSAR Methodology.
章节3（AP方法论软件库）列举并描述了 “任务”，和 “工作产品”，这些在章节2中用例的描述中有提到。
Section 3 (Adaptive Methodology Library) lists and describes all tasks and work products, which are used in the descriptions of the use cases in section 2.
本引言部分的其余部分将记录所使用的策略和需求可追溯性图。
The rest of this Introduction section documents the policies utilized and the requirements traceability map.
1.3 文档约定 Document Conventions
本文档将遵循以下约定：
This document follows a list of document conventions, which are described in the following.
AUTOSAR的技术术语以等宽字体排版，例如:机器。一般来说，技术术语的复数形式是在单数形式后面加“s”形成的，例如Machines。
Technical terms of AUTOSAR are typeset in mono spaced font, e.g. Machine. As a general rule, plural forms of technical terms are created by adding "s" to the singular form, e.g. Machines.
该文档包含文本形式的规范项，通过唯一的数字ID、标题和以‘【’字符开始并以‘】’字符结束的实际文本来与其他文本区分开来。需求可追溯性的约定遵循[TPS_STDT_00080]，参见标准化模板([3])。
This document contains specification items in textual form that are distinguished from the rest of the text by a unique numerical ID, a headline, and the actual text starting after the [ character and terminated by the ] character. The conventions for requirements traceability follow [TPS_STDT_00080], see Standardization Template ([3]).
1.4 缩写和术语 Abbreviations and Technical Terms
| Technical Term 技术术语 | 含义 |
|---|---|
| Adaptive Software | 在AP平台上运行的应用级或平台级软件实体。这些软件实体可能由运行在多个操作系统进程中的多个可执行文件组成。 An application-level or platform-level software entity tailored to run on the AUTOSAR Adaptive Platform. These software entities may consist of multiple Executables running in multiple OS Processes. |
| Bottom-up approach | 一种设计模式，从具体/细颗粒度到抽象/粗颗粒度的工作/设计流程。例如SWC -> binary ->software cluster -> System。 A methodology pattern in which the work/design flows |
| Diagnostic Manager | 诊断管理是包含诊断通信和事件处理的完整功能。 The term Diagnostic Management is a placeholder for |
| Function Group | 功能组为一组运行时可能具有相互依赖的实例(即进程)定义了状态机。该进程指定其在功能组中的参与。 A Function Group defines a state-machine for a set of |
| Instance Specifier | 实例说明符是实例引用的缩短的“字符串化”表示。在ARXML中，实例引用是用<InstanceRef>如果在目标上没有必要，也可以使用<atpUriDef>:在此场景中，只有实例说明符在目标机配置文件中可见。 An Instance Specifier is a shortened, "stringified" representation of an instance reference. In terms |
| Top-down approach | 一种设计模式，从抽象/粗颗粒度到具体/细颗粒度的工作/设计流程。例如System ->softwarecluster ->binary ->SWC A methodology pattern in which the work/design flows |
1.5方法论概念 Methodology Concepts
AP平台方法论概念与CP平台的方法论概念是相同的。因此，我们在这里只提主要原则。详情请参阅[1]第1.5节。
The concepts of the methodology for the Adaptive Platform are identical with the concepts of the methodology for the Classic Platform. Hence, we will only mention the main principles here. Please refer to section 1.5 in [1] for further details.
[TR_AMETH_00101]任务、工作产品和用例的定义[该方法通过活动、聚合任务的实体及其相应的工作产品来描述典型的用例。任务被定义为可重用的元素:输入信息(例如，存储在特定的工作产品中)被处理以生成新的工作产品](RS_METH_00018)
[TR_AMETH_00101] Definition of tasks, work products and use cases [The methodology describes typical use cases by means of activitys, entities to aggregate tasks and their corresponding work products. Tasks are defined as reusable elements: input information (e.g., stored within particular work products) is processed in order to generate new work products.](RS_METH_00018)
[TR_AMETH_00226]工作产品的文档[为了在开发过程中记录设计规定或约束，每个工作产品都可以形成一份相应的文档](RS_METH_00069)
[TR_AMETH_00226] Documentation of work products dIn order to document design decisions or restrictions during the development process, each work product may aggregate a corresponding documentation.c(RS_METH_00069)
定义和图表主要遵循软件过程工程模型规范[5,SPEM], 其使用的符号是利用SPEM支持的EA建模工具实现的。
The definitions and figures follow mostly the Software Process Engineering Meta- Model Specification [5, SPEM] using symbols as per SPEM support of Enterprise Architect modeling tool.
1.6 需求追溯 Requirements Traceability
略
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
