AUTOSAR经典平台4.4.0开发方法论：官方详细指南

需积分: 9 77 浏览量更新于2024-07-16 收藏 4.05MB PDF 举报

AUTOSAR TR Methodology.pdf 是一份由AUTOSAR官方发布的文档，专注于汽车操作系统架构开发的方法论。该文档详细介绍了AUTOSAR Classic Platform在不同版本中的发展和变化，特别是从4.1.3版到4.4.0版的迭代过程。这份方法论对于理解和实践AUTOSAR标准在汽车行业中的应用至关重要。在4.4.0版本中，文档对过时要求的引用进行了移除，并进行了一些编辑修订，以保持内容的最新性和一致性。这一版本着重于确保架构的持续改进和与当前行业需求的同步。此外，文档还记录了2018年10月31日的更改，包括对DataExchange Points的支持，这可能涉及到系统间的通信和数据交换的标准化处理。在4.3.1版更新中，主要对原有要求进行了小范围修正，并进行了编辑性调整，可能是为了提高文档的清晰度和易读性。2016年11月30日的4.3.0版引入了新功能，如对Safety Extensions、Diagnostic Extract、Rapid Prototyping以及Sender Receiver Serialization的支持，这些扩展旨在增强系统的安全性和效率，同时也支持更快的产品开发流程。从4.2.2版开始，文档继续关注细节的完善和编辑修订，反映了对现有标准的不断优化。4.2.1版的重要更新涉及了对安全和诊断功能的增强，以及支持快速原型制作，这些都是现代汽车系统设计中不可或缺的部分。 4.1.3版之前的内容表明，AUTOSAR TR Methodology经历了逐步演进的过程，每一次版本升级都旨在提升汽车电子系统的性能、安全性和互操作性。这份文档不仅为开发者提供了明确的开发路径，还展示了AUTOSAR组织如何随着技术进步不断更新其方法论，以适应汽车行业的快速发展。 AUTOSAR TR Methodology.pdf是汽车行业工程师和项目经理在设计、实现和维护高度复杂的车载电子系统时的重要参考资料，它提供了关于如何采用AUTOSAR标准进行系统架构设计，以及如何跟踪标准版本变化，确保系统与最新规范保持一致的实用指导。

Methodology

AUTOSAR CP Release 4.4.0

References

[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 515

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

Methodology

AUTOSAR CP Release 4.4.0

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 515

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

Methodology

AUTOSAR CP Release 4.4.0

• 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)

[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 configur ing 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()

The referenced deliverables AUTOSAR TR InteroperabilityOfAutosarTools is set to sta-

tus obsolete in release 4.4.0.

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()

[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)

19 of 515

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

Methodology

AUTOSAR CP Release 4.4.0

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 Engineer-

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

modeling tool. c(RS_METH_00018, 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)

[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 methodology. The

Methodology Library Elements are used for the description of the related devel-

opment processes. These Methodology Library Elements can been seen as a

standard. c()

[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()

[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)

• Tool Definition (section 1.5.1.4)

• Guidance (section 1.5.1.5)

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.

The Guidance is currently not used in the AUTOSAR Methodology. It may be used in future docu-

ments.

20 of 515

— AUTOSAR CONFIDENTIAL —

Document ID 068: AUTOSAR_TR_Methodology

剩余514页未读，继续阅读

wagens

粉丝: 0
资源: 2

AUTOSAR经典平台4.4.0开发方法论：官方详细指南

AUTOSAR_TR_SomeIpExample_4.2.1.pdf

AUTOSAR_Methodology.pdf

autosar方法论

AUTOSAR_TR_Methodology.zip

AUTOSAR_RS_Methodology.pdf

AUTOSAR_TR_HWTestManagementIntegrationGuide.pdf

AUTOSAR_TR_FoundationReleaseOverview.pdf

AUTOSAR_TR_AdaptiveMethodology.pdf

AUTOSAR_TR_ListOfKnownIssuesSecureHardwareExtensions.pdf

AUTOSAR_TR_AIDesignPatternsCatalogue.pdf

最新资源