AUTOSAR 4.3.1开发方法论：电子架构设计指南

5星 · 超过95%的资源需积分: 49 75 浏览量更新于2024-07-18 2 收藏 4.16MB PDF 举报

AUTOSAR方法论是一份详尽的指南，专为理解和开发基于AUTOSAR（AUTomotive Open System ARchitecture）电子系统架构而设计。该文档详细介绍了AUTOSAR Classic Platform在第4.3.1版中的核心概念和开发流程，它是理解和实践AUTOSAR架构的关键参考资料。 AUTOSAR CP (Classic Platform) 是一种标准化的软件平台，用于汽车电子系统的模块化设计，它强调了功能划分、接口定义和一致性。4.3.1版本的Methodology文档特别关注于minor corrections和editorial changes，这些可能涉及对先前要求的修正，以及对文档结构和内容的优化，确保信息的准确性和一致性。自2014年起，该文档的更新引入了多项重要功能扩展，例如： - 在4.2.1版本中，加入了对Safety Extensions的支持，这是为了增强系统的安全性，确保符合严格的汽车电子安全标准。 - Diagnostic Extract功能的加入，使得系统诊断更为高效，有助于早期发现并修复问题。 - Rapid Prototyping支持的添加，加快了原型设计和验证的效率，缩短了产品上市时间。 - Sender Receiver Serialization功能的引入，优化了通信机制，提高了数据交换的可靠性和效率。 4.1.3版本进一步对AUTOSAR Methodology进行了调整，使其与System Description categories相一致，这有助于开发者编写更精确和结构化的系统描述文档。每一份修订都反映了AUTOSAR团队对于不断变化的市场需求和技术进步的响应，确保了文档内容始终紧跟行业标准。学习者可以通过这份文档学习如何遵循AUTOSAR的生命周期管理流程，包括需求分析、设计、实现、测试和集成，从而构建出高性能、可维护且兼容的汽车电子系统。 AUTOSAR方法论是汽车行业电子系统开发者的宝贵工具，它提供了从基础框架到高级功能的全面指导，是任何想要进入或深化理解AUTOSAR架构的工程师不可或缺的学习资料。

Methodology

AUTOSAR CP Release 4.3.1

Bibliography

[1] Requirements on Methodology

AUTOSAR_RS_Methodology

[2] Standardization Template

AUTOSAR_TPS_StandardizationTemplate

[3] Software Process Engineering Meta-Model Specification

http://www.omg.org/spec/SPEM/2.0/

[4] Integration of Franca IDL Software Component Descriptions

AUTOSAR_TR_FrancaIntegration

[5] Virtual Functional Bus

AUTOSAR_EXP_VFB

[6] Software Component Template

AUTOSAR_TPS_SoftwareComponentTemplate

[7] System Template

AUTOSAR_TPS_SystemTemplate

[8] General Specification of Basic Software Modules

AUTOSAR_SWS_BSWGeneral

[9] General Specification on Transformers

AUTOSAR_ASWS_TransformerGeneral

[10] Basic Software Module Description Template

AUTOSAR_TPS_BSWModuleDescriptionTemplate

[11] Specification of ECU Configuration

AUTOSAR_TPS_ECUConfiguration

[12] Specification of Memory Mapping

AUTOSAR_SWS_MemoryMapping

[13] Specification of Compiler Abstraction

AUTOSAR_SWS_CompilerAbstraction

[14] Specification of Module E2E Transformer

AUTOSAR_SWS_E2ETransformer

[15] Diagnostic Extract Template

AUTOSAR_TPS_DiagnosticExtractTemplate

[16] Specification of RTE Software

AUTOSAR_SWS_RTE

[17] Specifications of Safety Extensions

AUTOSAR_TPS_SafetyExtensions

16 of 520

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

Methodology

AUTOSAR CP Release 4.3.1

1 Introduction

1.1 Objective

AUTOSAR requires a common technical approach for some steps of system develop-

ment. This approach is called the AUTOSAR methodology. This document defines

and describes this AUTOSAR methodology. It covers all major steps of the develop-

ment of a system with AUTOSAR: from the definition of the Virtual Functional

Bus to the generation of an ECU executable.

The requirements for the methodology are defined in the document [1].

1.2 Document Conventions

This document follows a list of document conventions, which are described in the fol-

lowing.

Technical terms of AUTOSAR are typeset in mono spaced font, e.g. ECU. As a general

rule, plural forms of technical terms are created by adding "s" to the singular form, e.g.

ECUs.

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 d character and terminated by the c character. The conventions for requirements

traceability follow [TPS_STDT_00080], see Standardization Template ([2]).

1.3 Scope

[TR_METH_01003] Scope of the AUTOSAR methodology d The AUTOSAR method-

ology is not a complete process description, but rather aggregates the various elements

of AUTOSAR and shows how they are brought together to develop a complete system.

Sample aggregations are provided as Use Cases in Chapter 2. c(RS_METH_00006)

[TR_METH_01004] Support for various stakeholders by the AUTOSAR method-

ology d The structure of the methodology was designed to help cover the needs of

various AUTOSAR stakeholders:

• Organizations: Methodology is modeled in a modular format to allow organiza-

tions to tailor it and combine the Methodology within their own inter nal processes,

while identifying points where they interact with other organizations.

• Engineers: Methodology is scoped to allow engineers of various roles quickly find

AUTOSAR information that is relevant to their specific needs.

18 of 520

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

Methodology

AUTOSAR CP Release 4.3.1

• Tool Vendors: Methodology provides a common language to share among all

AUTOSAR members and a common expectation of what capabilities tools should

support.

c(RS_METH_00018, RS_METH_00056, RS_METH_00009)

[TR_METH_01005] Restrictions of AUTOSAR methodology d Furthermore, the

methodology does not prescribe a precise order in which activities should be carried

out. The methodology is a mere work-product flow: it defines the dependencies of

activities on work-products. This means that when the information specified in the

methodology is available, an activity can be carried out to produce the output work-

products. The set of activities is described in Chapter 3.

This restriction implies that the AUTOSAR methodology does not define an overall time-

line and does not define how and when iterations are carried out. For example during

system and design, the same activity (namely configuring the system) will be carried

out repeatedly with various levels of precision. There will be a first ”rough” configuration

and a final ”precise” configuration which might depend on the feedback from the actual

configuration or even implementation of ECUs. How and when such refinement steps

are to be carried out is NOT defined in the methodology. c(RS_METH_00047)

1.4 Overview

[TR_METH_01000] Domains of the AUTOSAR methodology d The AUTOSAR

methodology is structured into several domains of development:

• Virtual Functional Bus

• System

• Software Component

• Basic Software

• ECU

These domains are depicted in the methodology overview workflow Figure 2.9. c

(RS_METH_00018, RS_METH_00032)

[TR_METH_01001] AUTOSAR methodology assets d For each domain, relevant

Work Product, Task, Role, and Tool elements are defined (see chapter 3).

In addition, there are elements that are common for all domains (see 3.1). c

(RS_METH_00025, RS_METH_00028, RS_METH_00009)

[TR_METH_01002] AUTOSAR methodology use cases d Use cases (see chapter 2)

show how these standard reusable elements are applied to support real-world devel-

opment. The Overall View (see chapter 2.1) provides an end to end view on the typical

use cases of all domains. c(RS_METH_00018, RS_METH_00056, RS_METH_00009)

19 of 520

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

Methodology

AUTOSAR CP Release 4.3.1

1.5 Methodology Concepts

[TR_METH_01006] General AUTOSAR methodology concepts d The AUTOSAR

methodology defines activities

performed by roles that create work products as gen-

eral reusable method patterns. The reusable method pattern elements are described

in the methodology library elements section (cf. section 1.5.1). The methodology also

describes sample process patterns of typical use cases considered for the creation of

AUTOSAR work products. The patterns use process elements that are described in

the use case elements section (cf. section 1.5.2).

The definitions and the figures are made according to the Software Process Engi-

neering Meta-Model Specification [3]. The symbols are taken from the Enterprise

Architect modeling tool. c(RS_METH_00018, RS_METH_00021, RS_METH_00047,

RS_METH_00048, RS_METH_00025, RS_METH_00061, RS_METH_00028,

RS_METH_00056)

1.5.1 Methodology Library Elements

[TR_METH_01007] Methodology Library d The Methodology Library (see

chapter 3) defines the Methodology Library Elements of every method pattern

such as Roles, Tasks, and Work Product Definitions. c(RS_METH_00018,

RS_METH_00021, RS_METH_00025, RS_METH_00028)

[TR_METH_01008] Methodology Library Element d A Methodology Li-

brary Element contains a description of the element to define its purpose in

the methodology and thus provides the basic contents of the AUTOSAR methodol-

ogy. The Methodology Library Elements are used for the description of the

related development processes. These Methodology Library Elements can

been seen as a standard. c(RS_METH_00017, RS_METH_00043, RS_METH_00050,

RS_METH_00064)

[TR_METH_01009] Relation of Methodology Library and Methodology Li-

brary Element to the SPEM meta model d The Methodology Library and

the Methodology Library Elements correspond to the Method Content and

Method Content Elements in the SPEM meta model [3]. c(RS_METH_00009)

[TR_METH_01010] Overview of Methodology Library Elements d Methodol-

ogy Library Elements comprise:

• Task Definition (section 1.5.1.1)

• Work Product Definition (section 1.5.1.2)

• Role Definition (section 1.5.1.3)

The RS_Methodology document uses the term “Activity” when addressing process elements in gen-

eral. In this document the atomic process elements are called “Tasks”, whereas an “Activity” is used to

organize tasks and to define processes.

20 of 520

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

剩余519页未读，继续阅读

weixin_41326092

粉丝: 0
资源: 8

AUTOSAR 4.3.1开发方法论：电子架构设计指南

Autosar中文详细简介

Autosar详细文档

AUTOSAR软件架构_方法论_解决方案.pdf

在AutoSAR标准下，如何实现从应用层到硬件抽象层的模块化通信？请结合Vector AUTOSAR工具链给出示例。

AUTOSAR COM学习

autosar 相关书籍

如何下载autosar标准文档

在AutoSAR框架内，如何通过Vector工具链实现应用层到硬件抽象层的模块化通信？

autosar 支持lin从节点吗

matlab autosar 学习

最新资源