SW-C and System Modeling Guideread.pudn.com/downloads411/doc/project/1747885/Auxiliary...

SW-C and System Modeling Guide V2.1.0

R4.0 Rev 2

Document Title SW-C and System Modeling Guide AUTOSAR Document Owner AUTOSAR Document Responsibility 207 Document Identification No Auxiliary Document Classification 2.1.0 Document Version Final Document Status 4.0 Part of Release 2 Revision

Document Change History Date Version Changed by Change Description 24.11.2010 2.1.0 AUTOSAR

Administration Modeling rules optimization for multiple

instances. New description of the standardized

Autosar packages structure. New RTE specification and

requirements references introduced. 30.11.2009 2.0.0 AUTOSAR

Administration Set of modelling rules changed to allow

different styles of modelling with respect to clustering and future extensibility.

Set of naming convention rules changed to allow more flexibility in creation of self-explicable names.

Name and number of standardized AR-Packages have changed. Scope of naming convention has been extended accordingly.

Blueprints concept supported as a dedicated AR-Package for Ports

Long Names are now out of scope Legal disclaimer revised

23.06.2008 1.0.1 AUTOSAR Administration

Legal disclaimer revised

13.12.2007 1.0.0 AUTOSAR Administration

Initial Release

1 of 64 Document ID 207: AUTOSAR_TR_SWCModelingGuide - AUTOSAR Confidential -


R4.0 Rev 2

Disclaimer This specification and the material contained in it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the companies that have contributed to it shall not be liable for any use of the specification. The material contained in this specification is protected by copyright and other types of Intellectual Property Rights. The commercial exploitation of the material contained in this specification requires a license to such Intellectual Property Rights. This specification may be utilized or reproduced without any modification, in any form or by any means, for informational purposes only. For any other purpose, no part of the specification may be utilized or reproduced, in any form or by any means, without permission in writing from the publisher. The AUTOSAR specifications have been developed for automotive applications only. They have neither been developed, nor tested for non-automotive applications. The word AUTOSAR and the AUTOSAR logo are registered trademarks. Advice for users AUTOSAR specifications may contain exemplary items (exemplary reference models, "use cases", and/or references to exemplary technical solutions, devices, processes or software). Any such exemplary items are contained in the specifications for illustration purposes only, and they themselves are not part of the AUTOSAR Standard. Neither their presence in such specifications, nor any later documentation of AUTOSAR conformance of products actually implementing such exemplary items, imply that intellectual property rights covering such exemplary items are licensed under the same rules as applicable to the AUTOSAR Standard.



R4.0 Rev 2

Table of Contents List of Figures ..............................................................................................................4 List of Tables ...............................................................................................................5 1 References ...........................................................................................................6 2 Scope ...................................................................................................................7 3 How to read this document...................................................................................8

3.1 Conventions used..........................................................................................8 3.2 Acronyms and Abbreviations.........................................................................9

4 Requirements traceability ...................................................................................10 5 Modeling Rules...................................................................................................11

5.1 Reuse of model element..............................................................................11 5.1.1 Reuse of one interface for multiple ports............................................. 11 5.1.2 Reuse of one data type for multiple interfaces .................................... 12

5.2 Use of multiple ComponentPrototypes ........................................................12 5.3 Clustering ....................................................................................................13 5.4 Future extensibility ......................................................................................14

6 Naming Convention for AUTOSAR Model Elements ..........................................16 6.1 General Rules for Short Names ..................................................................16 6.2 Relation between Model Level and the Implementation Level.....................17

6.2.1 Length Restrictions.............................................................................. 17 6.2.2 Data Types.......................................................................................... 18 6.2.3 RTE rules of name mapping................................................................ 18 6.2.4 Components and Ports........................................................................ 19 6.2.5 Sender Receiver Interfaces and Data Elements ................................. 20 6.2.6 Client Server Interfaces, Operations, and Arguments ......................... 21

6.3 Usage of Keywords .....................................................................................21 6.3.1 Keyword Composition Semantic Rules ............................................... 22

6.4 Model Elements...........................................................................................25 6.4.1 ARPackage (AR-PACKAGE) .............................................................. 26 6.4.2 SenderReceiverInterface (SENDER-RECEIVER-INTERFACE) ......... 28 6.4.3 VariableDataPrototype (VARIABLE-DATA-PROTOTYPE) ................. 28 6.4.4 ApplicationDataType ........................................................................... 29 6.4.5 CompuMethod (COMPU-METHOD) ................................................... 30 6.4.6 SwComponentType (COMPOSITION-SW-COMPONENT-TYPE) ...... 31 6.4.7 SwComponentPrototype (SW-COMPONENT-PROTOTYPE)............. 32 6.4.8 PortPrototype (P-PORT-PROTOTYPE, R-PORT-PROTOTYPE) ....... 33 6.4.9 Units (UNIT) ........................................................................................ 33 6.4.10 Enumerations ...................................................................................... 34 6.4.11 ClientServerInterface (CLIENT-SERVER-INTERFACE) ..................... 35 6.4.12 ParameterInterface (PARAMETER-INTERFACE) .............................. 35 6.4.13 ParameterDataPrototype (PARAMETER-DATA-PROTOTYPE) ......... 36 6.4.14 PortBlueprint (PORT-BLUEPRINT) ..................................................... 36 6.4.15 DataConstrs (DATA-CONSTRS)......................................................... 36

7 Appendix: Keywords...........................................................................................38



R4.0 Rev 2

List of Figures Figure 1: Re-use of PortInterfaces in Ports with variants...........................................12 Figure 2: Ports of multiple ComponentPrototypes. ....................................................13 Figure 3: Components and ports ...............................................................................19 Figure 4: SenderReceiverInterfaces and DataElements............................................20 Figure 5: ClientServerInterfaces and Operations.......................................................21 Figure 6: AUTOSAR Package structure ....................................................................27 Figure 7: Example of SwComponentType .................................................................32



R4.0 Rev 2

List of Tables Table 1 Example of keywords abbreviation of common usage.................................22 Table 2 Fields ............................................................................................................23 Table 3 Category of ARPackages..............................................................................27



R4.0 Rev 2

1 References

[1] Template UML Profile and Modeling Guide AUTOSAR_TemplateModelingGuide.pdf [2] Specification of RTE Software AUTOSAR_SWS_RTE.pdf [3] Software Component Template AUTOSAR_TPS_SoftwareComponentTemplate.pdf [4] AUTOSAR Model Persistence Rules for XML AUTOSAR_TR_XMLPersistenceRules.pdf [5] MISRA-C: 2004. Guidelines for the use of the C language in critical systems. [6] Technical Overview AUTOSAR_Technical_Overview.pdf [7] Generic Structure Template AUTOSAR_TPS_GenericStructureTemplate.pdf [8] Requirements on Runtime Environment AUTOSAR_SRS_RTE.pdf



R4.0 Rev 2

2 Scope

The limits of my language mean the limits of my world. Ludwig Wittgenstein This document gives guidelines and conventions on using the AUTOSAR model elements in order to build AUTOSAR systems. It does not contain guidelines for the AUTOSAR meta model. This is already covered by [1].



R4.0 Rev 2

3 How to read this document

All rules are identified by an ID. The ID starts with “MR” for the Modeling Rules followed by three digits (MRxxx). The ID starts with “NR” for the Naming Rules followed by three digits (NRxxx). The provided XML examples conform to the AUTOSAR metamodel R4.0 3.1 Conventions used In requirements, the following specific semantics are used (taken from Request for Comment RFC 2119 from the Internet Engineering Task Force IETF) The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Note that the requirement level of the document in which they are used modifies the force of these words.

MUST: This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.

MUST NOT: This phrase, or the phrase „SHALL NOT“, means that the definition is an absolute prohibition of the specification.

SHOULD: This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

SHOULD NOT: This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.

MAY: This word, or the adjective „OPTIONAL“, means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation, which does not include a particular option, MUST be prepared to interoperate with another implementation, which does include the option, though perhaps with reduced functionality. In the same vein an implementation, which does include a particular option, MUST be prepared to interoperate with another implementation, which does not include the option (except, of course, for the feature the option provides.)



R4.0 Rev 2

3.2 Acronyms and Abbreviations

API: Application Programming Interface AR: AUTOSAR CAN: Controller Area Network ECU: Electronic Control Unit HMI: Human Machine Interface MISRA: Motor Industry Software Reliability Association RTE: Real Time Environment SW-C: Software Component WP: Work Package XML: eXtensible Markup Language



R4.0 Rev 2

4 Requirements traceability

Document: AR_RS_SWC_System_Modeling Requirement Satisfied by [MG001] Distinguish Standardized vs. not standardized model elements of type ARElement

6.4.1 ARPackage:. Reserved to the model elements defined by the AUTOSAR partnership.

[MG002] Name should reflect the purpose of the model element

6.1, 6.4.2, 6.2.6 covers this requirement only partially.

[MG005] Easy creation of names 6.2.6 [MG006] Model Elements names shall be self-explanatory

6.1, 6.4.2 , 6.4.4, 6.4.6, 6.4.7, 6.4.8

[MG007] Distinguish model elements of different model element suppliers of not standardized model elements

5

[MG010] Model Element Names shall follow semantic rules

6.3.1

[MG011] Model Element Names are composed by arranging standardized keywords

6.2.6

[MG012] Semantic of Model Element Names shall allow variable number of keywords

6.3.1

[MG014] Length restriction for short names of Identifiable

6.1,

[MG016] Names shall allow to indicate if the value is a direct measurement or a conditioned value

6.2.6 covers this requirement only partially. Values for keywords are needed

[MG017] Names should follow the ISO 8855 for English naming

6.1 covers this requirement only partially, standard is not mentioned.

[MG030] Use English as Standard Language for Names

6.1

[MG031] No Architectural Information in Names 6.4.6, 6.4.7 [MG034] Usage of Unique Keywords 6.2.6 Keywords are used to compose names [MG039] Avoid usage of Trailing underscores 6.1 [MG040] Avoid sequences of underscores characters

6.1

[MG041] Do not rely on uppercase/lowercase difference only

6.1.

[MG048] Easy lookup of names in databases 6.3.1 [MG049] Support Identifiable already present in the MasterTable

6.4

[MG054] Provide guidelines how to resolve name conflicts

Whole document.

[MG052] Definition of Package Structure 6.4.1 [MG053] Model shall be compliant to the Meta Model

5

[MG055] Continuous Data Type resolution should be a power of two

5

[MG056] Standardized model elements shall not contain non standardized elements

4, 6.4.1

[MG057] Modeling Guide shall support the AUTOSAR methodology

Whole document.

[MG059] Provide Single Set of Keywords The standardized keyword list is included in the released Application Interfaces XML file.

[MG060] Applicability of Naming Convention 6 [MG061] Naming convention shall be unique 6



R4.0 Rev 2

5 Modeling Rules [MR001] Model shall be compliant to the Meta Model. [MR003] Use AR Package concept for SW-C to distinguish different suppliers of SW-C. This helps to trace SW-C supplier in case of errors due to the usage of elements not part of the released AUTOSAR Packages (e.g. the set of data that is in AUTOSAR Release 4.0). [MR017] Use AR Package category to distinguish what is standardized, according to the provider of the ARPackage, from what is not. See document [7] for AR Package categories classification. [MR004] Each element not defined by the AUTOSAR partnership, shall be included in a AR Package different from the one officially released by AUTOSAR, i.e. the AR Package ShortName shall be changed (e.g. SUPPLIER1) and the category shall be changed if it does not contain released elements. Recommendations:

- continuous Data Type resolution should be a power of two. 5.1 Reuse of model element 5.1.1 Reuse of one interface for multiple ports The reuse of interfaces is encouraged. Example: The Temperature interface is used for the InsideTemperature port and OutsideTemperature port of a component type. [MR011] Do not define different interfaces to implement variants. Define one interface that is independent on the variant and define several ports using this interface which are dependent on the variant. Using one interface for multiple ports makes variant handling more understandable since the interfaces are not affected by the variant. Ports can be enabled or disabled depending on the selected variant. Example: Gasoline spark ignition engine management systems know the concept of a slow path and a fast path for torque intervention. Current diesel systems do not know this distinction. The following modeling is not recommended:

Define an interface TorqueInterventionSlow and an interface TorqueInterventionFast.



R4.0 Rev 2

Define a port TorqeInterventionSlow with the interface TorqueInterventionSlow and a port TorqueInterventionFast with the interface TorqueInterventionFast.

In a diesel variant the TorqueInterventionSlow port and interface are ignored. The following modeling is recommended:

Define an interface TorqueIntervention1. Define a port TorqueInterventionSlow and a port TorqueInterventionFast which

both have the interface TorqueIntervention1. In a diesel variant the TorqueInterventionSlow port is disabled.

Figure 1: Re-use of PortInterfaces in Ports with variants.

Please note that in the example, as result of variant handling approach, the two ComponentPrototypes are of the same ComponentType. 5.1.2 Reuse of one data type for multiple interfaces The reuse of data types is encouraged. Example: The Torque data type is used in the DataElements of the interfaces MinimumTorqueAtClutch and MaximumTorqueAtClutch. 5.2 Use of multiple ComponentPrototypes If the same port P (either RPort or PPort) of multiple ComponentPrototypes A1..n of the same ComponentType is connected to another ComponentPrototype B, the name of the ports should be constructed by concatenating the name of the connected ComponentPrototype Ai and the name of the connected port P.

AtomicSoftwareComponent

EngineControl PortInterface

TorqueIntervention1EngineControl(gasoline variant)

TorqueInterventionFast

ComponentPrototype

PPort

PPort

TorqueInterventionSlow

EngineControl(diesel variant)

TorqueInterventionFast

ComponentPrototype

PPort



R4.0 Rev 2

It is recommended to do the concatenation by means of a preposition (see ch. 6) in the following order: <Port name>+<Preposition>+[<ComponentPrototype name>] Example: The “Washer” ComponentType has an RPort “Activation”. There are three ComponentPrototypes of this type: “WasherFront”, “WasherRear”, and “WasherHeadlamp”. The WiperWasherManager ComponentType should have separate PPorts that are connected to the RPorts of the three ComponentPrototypes. These PPorts should have the names “ActivationOfWasherFront”, “ActivationOfWasherRear”, and “ActivationOfWasherHeadlamp”.

Figure 2: Ports of multiple ComponentPrototypes.

5.3 Clustering [MR008] Functional elements that belong together shall also be represented in the model together. The AUTOSAR meta model provides several features to support clustering of model elements. For example, interfaces can contain multiple data elements, record data types and array data types can contain multiple elements. The use of structuring features improves the structure and comprehensibility of the model. If elements are clustered there is a choice between using three alternatives that have different behaviors and usually fit to different application scenarios: A) record data types,

elements of a record are transmitted atomically (in one block). elements of record data types can have different data types.

AtomicSoftwareComponent

WiperWasherMgr WasherFront

RPortActivation

ComponentPrototype

WasherRear

RPort Activation

ComponentPrototype

WasherHeadlamp

RPort

Activation

ComponentPrototype

Washer AtomicSoftwareComponet

WiperWasherMgr

ctivationOfWasherFront

ComponentPrototype

PPortA

PPort

ActivationOfWasherRear

PPortActivationOfWasherHeadlamp



R4.0 Rev 2

B) array data types elements of arrays are transmitted atomically (in one block), all elements of an array have to use the same data type.

C) interfaces with multiple data elements.

The data elements of interfaces are transmitted separately. Data elements of interfaces can have different data types.

Examples for usage of these three alternatives are:

To A): use a record data type that includes the o status and its value that belong together, e.g. for an actuator o wheel dependent information that belong together, o axle dependant information that belong together, o value(s) and their derivation(s).

To B): use an array data type o sending of dynamic configuration data, e.g. engine full-load curve, or

retarder brake torque curve which may change when vehicle is driven, depending on temperature or altitude. This use case is common in commercial vehicles J1939 bus protocol on CAN.

To C): data that belongs together with independent update times: o default for most signals, allows the system configurator most flexibility in

scheduling communication. The advantage to use a record instead of an array data type is that a separate name for each element is used. 5.4 Future extensibility It is often necessary to adapt and extend model elements to cope with new requirements. Defining or standardizing elements named “Reserved” (or with other names indicating a project dependent solution) with undefined meaning as placeholders for future extensions would lead to non standardized elements when customization is performed at a project level. [MR009] Placeholder model elements with undefined meaning are not allowed. The following rules ensure forward compatibility of relevant model elements towards new AUTOSAR releases. [MR010] If a new application requires the modification of any attribute (Enumeration Values, Enumeration Value Names) of a standardized enumeration data type, the existing data type shall not be changed, but a new enumeration data type shall be created. The name of the new data type shall differ from the name of the original data type only in the sequence number. [MR012] If a new application requires the modification of any attribute (Resolution, Physical Limits, Offset, Unit) of a standardized continuous data type, the existing data type shall not be changed, but a new continuous data type shall be created. The 14 of 64 Document ID 207: AUTOSAR_TR_SWCModelingGuide

- AUTOSAR Confidential -


R4.0 Rev 2

name of the new data type shall differ from the name of the original data type only in the sequence number. [MR013] If a new application requires the modification of any attribute (number of elements, type of elements) of a standardized array data type, the existing data type shall not be changed, but a new array data type shall be created. The name of the new data type shall differ from the name of the original data type only in the sequence number. [MR014] If a new application requires the modification of any attribute (Number of Elements, Elements Name, Elements Type) of a standardized record data type, the existing data type shall not be changed, but a new record data type shall be created. The name of the new data type shall differ from the name of the original data type only in the sequence number. [MR015] If a new application requires the modification of any attribute (number of data elements, name of the data elements, type of the data elements) of a standardized sender-receiver interface, the existing interface shall not be changed, but a new sender-receiver interface shall be created. The name of the new interface shall differ from the name of the original interface only in the sequence number. [MR016] If a new application requires the modification of any attribute (operation name, number of arguments, argument names, argument data types, argument in/out property) of a standardized client-server interface, the existing interface shall not be changed, but a new interface shall be created. The name of the new interface shall differ from the name of the original interface only in the sequence number.



R4.0 Rev 2

6 Naming Convention for AUTOSAR Model Elements This section contains naming conventions for AUTOSAR model elements. This naming convention is applicable in any vehicle application domain of AUTOSAR. [NR059] The naming convention applies to the following Model Elements:

- ARPackages, standardized Model Elements only. - SwComponentTypes - SwComponentPrototypes - ApplicationDataTypes - Units - PortInterfaces - PortBlueprints - DataPrototypes - CompuMethods

The XML code which is shown in the document is compliant to the AUTOSAR xsd of Release 4.0. 6.1 General Rules for Short Names In this chapter and in the rest of the document from now on, the term “name” refers to “short name” only. Long Names are out of scope. [NR001] The language for the names shall be English. A model element name shows up as a SHORT-NAME in XML in, for example: <SHORT-NAME>MyName</SHORT-NAME> According to the rules for AUTOSAR XML files the short name has the type AR:IDENTIFIER (see document [4]) and is restricted by the following regular expression: [a-zA-Z][a-zA-Z0-9_]{0,127} [NR002] A short name shall be between 1 and 128 characters long, shall begin with an alphabet, and shall consists of alphabets and numbers. [NR003] As additional requirement to the MetaModel, underscores are not allowed in the short names. Rules NR002 and NR003 lead to the following regular expression for short names: [a-zA-Z][a-zA-Z0-9]{0,127} [NR004] Names shall not differ in capitalization only. Do not distinguish names only from uppercase/lowercase format since the user can easily mix up names that differ only for capitalization. The following example lists not allowed name differentiation: Short name 1: DoorLocked Short name 2: doorLocked 16 of 64 Document ID 207: AUTOSAR_TR_SWCModelingGuide



R4.0 Rev 2

[NR005] A name must be usable as valid identifier in source code for C, C++ and C-preprocessor. The rationale behind this rule is, that some of the names are used by code generators, especially the RTE generator, to produce source code symbols. Since it would be difficult to state for each individual name if and in which context it will ever be used by generators, this general restriction is made. [NR006] The names of elements shall document their meaning or use. [NR007] No prefixes related to the kind of the element shall be used in the name of the model elements covered by this Naming Convention, listed in NR059. Reasons for not using prefixes:

Shorter names, e.g. if it shows up in the RTE API in names as RTE_... If we had any prefix for e.g. interfaces, prefixes would have to be defined for

all elements (ports, SWCs, data types,...). Prefixes can be introduced by code generators for the identifiers of

programming language APIs. The information, whether some element is a Component, DataType, Interface,

etc., is already contained in the structure of the XML file. 6.2 Relation between Model Level and the Implementation Level This section describes the relation between the model level of AUTOSAR and the implementation level. A “model” in this chapter means an AUTOSAR model, i.e., an instance of the AUTOSAR meta model. “Implementation” means the realization of the model in a programming language, like C. For a more detailed explanation please see the “AUTOSAR Technical Overview” [6]. 6.2.1 Length Restrictions The RTE Specification [2] contains rules on how to map model-level names to generated names on implementation-level. For example, an implementation-level name for a sender/receiver implicit write is created as follows: Rte_IWrite_<runnable-entity-name>_<port-name>_<data-element-name> This name is visible to the linker as an external identifier. MISRA [5] rule 1.4 requires that the significant part of such a name shall not exceed 31 chars. Since AUTOSAR decided to allow a deviation from this rule, the size of the generated name can exceed 31. Taking into account that each single name from the model cannot exceed 128 characters, the name given above could have as much as 11 + 1 + 128 + 1 +128 + 1 + 128 = 398 characters.



R4.0 Rev 2

It is currently not yet decided, whether compilers/linkers must support this worst case for AUTOSAR or a lower limit for the total budget of the name size will be defined. See [RTE00051] in [8] 6.2.2 Data Types [NR008] Data type names in an AUTOSAR model shall conform to C/C++ names for typedefs (e.g. they shall not be C keywords). The implementation level "typedef" names (generated by the RTE API generator) must be unique on an ECU to avoid compiler name clashes. 6.2.3 RTE rules of name mapping The following RTE requirements describe the mapping from modeling level to implementation level:

rte_sws_1153 rte_sws_3837

Such rte_sws rules define the sequence in which model element ShortNames are concatenated to obtain generated function names in the RTE C Code.

Example: 1

ShortName of component type: Wshr ShortName of the component prototype: WshrFrnt ShortName of runnable entity: Monr ShortName of provide port: OutdT ShortName of sender-receiver interface of this port: T1 ShortName the data element: Val Examples of generated function names for rule rte_sws_3837: Rte_IRead_Monr_OutdT_Val Rte_IRead_Wshr_Monr_OutdT_Val


1 The keywords and keyword abbreviations used in this example may not be consistent to the keyword list.


R4.0 Rev 2

6.2.4 Components and Ports

Figure 3: Components and ports

The figure above shows the scope of Components and Ports names. SwComponentTypes names are local to an AR-Package therefore within an AR-Package there must not be two SwComponentTypes having the same name, i.e, the short-names shall be unique. The same applies for:

- SwComponentPrototypes within a CompositionSwComponentType - PortPrototypes within a SwComponentType.

See document [3] for detailed information on name space provided by Software Components. Port names will appear in the RTE APIs, see RTE specifications [2]. The figure also shows that names of connected ports can be different (example: pp2 from Component3 connected to rp3 of Component2).

Component2

<AR-PACKAGE> <SHORT-NAME>Package1</SHORT-NAME> <ELEMENTS> <COMPOSITION-SW-COMPONENT-TYPE> <SHORT-NAME>Component1</SHORT-NAME> <PORTS> <P-PORT-PROTOTYPE> <SHORT-NAME>pp1</SHORT-NAME> <SENDER-RECEIVER-INTERFACE-TREF> Interface1 </ SENDER-RECEIVER-INTERFACE-TREF> </R-PORT-PROTOTYPE> </PORTS> </ COMPOSITION-SW-COMPONENT-TYPE > </ELEMENTS> </AR-PACKAGE>

Component3

pp2 rp3

rp2

rp1

Component1

pp2

pp1

rp1

rp2

Component Name - will not appear in the source code (but in the header file and the binary interface) - will be used as part of the file name of the header file - Is local to an AUTOSAR package

Port Name - will appear in the source code - is local to a component

pp1

pp1



R4.0 Rev 2

6.2.5 Sender Receiver Interfaces and Data Elements Interface Name- will NOT appear in the source code- Is local to an AUTOSAR package

Data Element Name- will appear in the source code- is local to an interface

<AR-PACKAGE><SHORT-NAME>Package1</SHORT-NAME><ELEMENTS>

<SENDER-RECEIVER-INTERFACE><SHORT-NAME>Interface1</SHORT-NAME><DATA-ELEMENTS>

<VARIABLE-DATA-PROTOTYPE><SHORT-NAME>de1</SHORT-NAME><TYPE-TREF>

type1</ TYPE-TREF>

</ VARIABLE-DATA-PROTOTYPE ></DATA-ELEMENTS>

</SENDER-RECEIVER-INTERFACE></ELEMENTS>

</AR-PACKAGE>

Interface Name- will NOT appear in the source code- Is local to an AUTOSAR package

Data Element Name- will appear in the source code- is local to an interface

<AR-PACKAGE><SHORT-NAME>Package1</SHORT-NAME><ELEMENTS>

<SENDER-RECEIVER-INTERFACE><SHORT-NAME>Interface1</SHORT-NAME><DATA-ELEMENTS>

<VARIABLE-DATA-PROTOTYPE><SHORT-NAME>de1</SHORT-NAME><TYPE-TREF>

type1</ TYPE-TREF>

</ VARIABLE-DATA-PROTOTYPE ></DATA-ELEMENTS>

</SENDER-RECEIVER-INTERFACE></ELEMENTS>

</AR-PACKAGE>

Figure 4: SenderReceiverInterfaces and DataElements The figure above shows the scope of SenderReceiverInterfaces and DataElements names. Interface names are local to an AR-Package therefore within an AR-Package there must not be two Interfaces having the same name, i.e, the short-names shall be unique. The same applies for DataElements i.e. within an Interface, DataElement names shall be unique. See document [3] for detailed information on name space provided by Sender Receiver Interfaces. DataElement names will appear in the RTE APIs, see RTE specifications [2].



R4.0 Rev 2

6.2.6 Client Server Interfaces, Operations, and Arguments

<AR-PACKAGE> <SHORT-NAME>Package1</SHORT-NAME> <ELEMENTS> <CLIENT-SERVER-INTERFACE> <SHORT-NAME>TrsmRatGear1</SHORT-NAME> <DESC><L-2 L='EN'>Theoretical transmission…...</L-2></DESC> <OPERATIONS> <CLIENT-SERVER-OPERATION> <SHORT-NAME>GetTrsmRatGear</SHORT-NAME> <ARGUMENTS> <ARGUMENT-DATA-PROTOTYPE> <SHORT-NAME>Gear</SHORT-NAME>

Interface Name - will NOT appear in the source code - Is local to an AUTOSAR package Operation Name

- will appear in the source code - is local to an interface

Argument Name - will appear in the source code - is local to an interface

<TYPE-TREF DEST='APPLICATION-PRIMITIVE-DATA-TYPE'>/AUTOSAR/ARDataTypes/Nr4</TYPE-TREF> <DIRECTION>IN</DIRECTION> </ARGUMENT-DATA-PROTOTYPE> <ARGUMENT-DATA-PROTOTYPE> <SHORT-NAME>Rat</SHORT-NAME> <TYPE-TREF DEST='APPLICATION-PRIMITIVE-DATA-TYPE'>/AUTOSAR/ARDataTypes/Fac1</TYPE-TREF> <DIRECTION>OUT</DIRECTION> </ARGUMENT-DATA-PROTOTYPE> </ARGUMENTS> </CLIENT-SERVER-OPERATION> </OPERATIONS> </CLIENT-SERVER-INTERFACE> </ELEMENTS> </AR-PACKAGE>

Figure 5: ClientServerInterfaces and Operations

The figure above shows the scope of ClientServerInterfaces, Operations, and Argument names. Interface names are local to an AR-Package therefore within an AR-Package there must not be two Interfaces having the same name, i.e, the short-names shall be unique. The same applies for:

- Operations within a ClientServerInterface. - Arguments within an Operation.

See document [3] for detailed information on name space provided by Client Server Interfaces. DataElement names will appear in the RTE APIs, see RTE specifications [2]. 6.3 Usage of Keywords Depending on its role in the component design, short names for component types, ports, port interfaces or data elements can make use of the predefined keywords and their abbreviations, which are described in more detail in 6.3.1. The advantage is, that this results in relatively short names with established meaning. [NR009] No underscores shall be used to separate keyword abbreviations in short names, because the RTE uses them to separate port names from Data Element names. Instead of underscores capital letters shall be used to separate the keyword abbreviations. 21 of 64 Document ID 207: AUTOSAR_TR_SWCModelingGuide



R4.0 Rev 2

6.3.1 Keyword Composition Semantic Rules [NR010] Short names are composed by concatenating predefined keyword abbreviations. [NR011] Each keyword shall start with an uppercase letter, or a number, followed by lowercase letters. [NR013] A keyword shall be a single English word or a multiplier prefix, such as “kilo”, “giga” or “milli”. To shorten the names within maximum allowed numbers of characters keyword abbreviations are provided. [NR018] A keyword (abbreviation) shall not be a valid single English word unless the meanings of the keyword and the English word are the same. This avoids potential misunderstanding while reading short names. The following example is not a valid short name, because non-abbreviated keywords are used: EngineSpd. The correct short name would be: EngSpd. [NR016] Keywords and keyword abbreviations must be unique. Two different keywords shall not be abbreviated in the same way. Two different abbreviations cannot belong to the same keyword even if the keyword can have multiple meaning. Examples: Charge Ch Channel Ch Duplicated abbreviation. One of the keyword abbreviation shall be changed. Current Curnt (here intended as adjective) Current Curr (here intended as noun) Duplicated keyword. Merge into one by indicating in the definition what multiple meanings it can have. [NR017] Some terms of common usage in the automotive environment cannot be expressed by a single English word. In such a case the abbreviation and the keyword shall be identical. Examples:

Keyword Abbreviation Keyword DefinitionEnglish

Engine Eng Engine Abs Abs Antilock Braking System

Table 1 Example of keywords abbreviation of common usage

[NR058] In order to build readable and understandable names, keywords shall be arranged according to semantic rules. Such rules define Semantic Fields that must be used in a defined sequence: 22 of 64 Document ID 207: AUTOSAR_TR_SWCModelingGuide



R4.0 Rev 2

Semantic Field Name Sequence Description Rules and Examples

1 Mean-

Environment- Device

Physical mean, environment. Define the element subject of Action.

It shall be a noun. It can be also a compound definition. Abbreviation or acronym cannot end with a digit. Examples for Mean: Fuel Examples for Environment: Air, Ambient Examples for Device: Accelerator, AcceleratorPedal, Engine

2

Action- Physical Type

Action or physical type conditioning or modifying the Mean/Environment /Device.

The Action shall be a verb. The Physical Type shall be a noun. It can be also a compound. Abbreviation or acronym cannot end with a digit.Examples for Action: Move, Pull, Release, Lock, OpenClose, ShiftUp Examples for Physical Type: Temperature, Speed

3 Condition- Qualifier

Qualifies the Mean / Environment / Device or Action in terms of data flow, event issuing or expresses a particular condition of the signal in terms of numeric treatment, time validity, precision quality, location.

It shall be a noun or an adjective. It can be also a compound definition. Abbreviation or acronym cannot end with a digit. Examples for Condition: Absolute, Old, New, AbsoluteEstimated, Examples for Qualifier: Request, Command, Status

4 Index

Identifies the signal as part of a logically structured information. Can be used to identify elements multiply instanced (index) or section of information.

It shall be a number, a single character, or an adjective describing the part. When used, it is always the last keyword in the sequence: Examples for Index: BrakeSwitch1

Table 2 Fields

All the predefined keywords and their corresponding keyword abbreviations are classified according to the semantic fields. Each keyword can be classified as belonging to more than one semantic field, this is needed to support NR016. Semantic fields are concatenated according to the Sequence column numbering: Mean-Environment-DeviceAction-PhysicalTypeCondition-QualifierIndex - this sequence is called FieldBlock. [NR019] None of the semantic fields are mandatory and semantic fields can be repeated, i.e. names can be built by using an arbitrary number of semantic fields. [NR020] Only keywords classified as Index shall start with a number. When used, Index field is always the last in the field block.



R4.0 Rev 2

The following examples are valid short names2: GearAct MirrMoveCmd EngSpd EngSpdMax Recommendation: if a semantic field contains more than one keyword they either have to be arranged in a natural English order or the most important keyword has to come first. Example: BrakePedalStatus PedalBrake is not recommended, since “brake pedal” is a very well-known English term. Other examples of compound definitions where not all semantic fields are present: BrkPedlSwt1 VehBodyAVertBasMeasd OpenClsReq AcvDamprSts To increase readability of names, a list of predefined Prepositions is provided within the standardized keyword list. [NR034] An arbitrary number of field blocks can be concatenated. However, the number of field blocks should be limited. It is encouraged to separate each field block by adding an appropriate preposition. This leads to the following naming pattern: Mean-Environment-DeviceAction-PhysicalTypeCondition-QualifierIndexPrepositionMean-Environment-DeviceAction-PhysicalTypeCondition-QualifierIndexPreposition … Portion of names separated by prepositions are called FieldBlocks:

FieldBlock1Preposition1FieldBlock2Preposition2…FieldBlockN. The following example shows the usage of prepositions: EngSpdAtGearTar [NR053] Each FieldBlock shall have a meaning independent of the other FieldBlocks. Example: The interface with the description “Generic interface for total powertrain torque at wheels” can not be represented by “PtTqAtWhlsTot”. The FieldBlock “WhlsTot” has not the intended meaning, because “Tot” relates to “Tq”. Therefore, one of the possible compliant solutions for the name is “PtTqTotAtWhls”.


2 The keywords and keyword abbreviations used in the examples of this chapter may not be consistent to the keyword list


R4.0 Rev 2

[NR050] If one or more prepositions are used to build a short name the most essential / important element has to be in the FieldBlock1. FieldBlocks that are following are refining the before mentioned FieldBlock. NR050 ensures that the names start with most essential information and end with very special details. Example: The following interface description: “Driver request torque limitation if accelerator and brake pedal pressed at the same time and implausibilities have occurred.” would result in the following name: DrvrTqLimnReqForBrkAccrPedlImpy1. The whole interface describes a driver torque limitation request. Therefore, DrvrTqLimnReq is the most important FieldBlock. Hence it is the first FieldBlock. The following examples show incorrect names: Naming a PortPrototype: MaximumEngineSpeed causes a keyword sequence error: Condition-Qualifier keyword cannot precede Mean-Environment-Device keyword. The correct sequencing is: EngineSpeedMaximum. 6.4 Model Elements The naming conventions apply to the ShortName (SHORT-NAME) attribute of the element. The element must be a specialization of Identifiable. The elements are referred to by their meta-model name. The names in brackets are the XML element names. To come to a reasonable naming conventions, for each element the objectives of the convention are described first.



R4.0 Rev 2

6.4.1 ARPackage (AR-PACKAGE) An ARPackage creates a name space3. In one system package names have to be unique. Packages can have sub-packages. The following rules are defined for the standardized package structure:

[NR022] Below the root an ARPackage with LongName AUTOSAR and ShortName AUTOSAR shall be placed. Everything inside the top-level package AUTOSAR is released by the AUTOSAR partnership (see requirement [MG001], [MG056]). The top-level package LongName and ShortName AUTOSAR is reserved by the AUTOSAR partnership and shall not be used elsewhere.

[NR023] Within this ARPackage, “AUTOSAR” packages called (ShortNames) ARApplicationDataTypes, ARUnits, ARSenderReceiverInterfaces, ARClientServerInterfaces, ARPortPrototypeBlueprints, ARCompuMethods, ARDataConstrs, and ARComponentTypes shall be placed.

These rules define the standardized package structure for the defined elements of the M1 [1] modeling level. According to requirement MG056 the AUTOSAR package is a reserved name space.

[MR018] Only elements which are defined by the AUTOSAR partnership shall be added to this name space. These elements shall not be modified.


3 For a description of the name space concept see [4].


R4.0 Rev 2

The following figure shows an example for the resulting standardized package structure.

Figure 6: AUTOSAR Package structure

…

ARPackage ARApplicationDataTypes

ARPackage ARSenderReceiverInterfaces

ARPackage ARUnits

ARPackage ARComponentTypes

ARPackage AUTOSAR

ARPackage ARClientServerInterfaces

ARPackage ARPortPrototypeBlueprints

ARPackage ARCompuMethods

ARPackage ARDataConstrs

As recommendation, names of non standardized AUTOSAR packages should follow the general rules defined in chapter 6.3.1. ARPackage AUTOSAR does not have a category, while its sub-packages do. In R4.0, categories of the sub-packages are set as follows:

ARPackage Category ARApplicationDataTypes BLUEPRINT

ARUnits BLUEPRINTARSenderReceiverInterfaces BLUEPRINT

ARClientServerInterfaces BLUEPRINTARPortPrototypeBlueprints BLUEPRINT

ARCompuMethods BLUEPRINTARDataConstrs STANDARD

ARComponentTypes EXAMPLE

Table 3 Category of ARPackages



R4.0 Rev 2

6.4.2 SenderReceiverInterface (SENDER-RECEIVER-INTERFACE) [NR051] The interface name shall end with a sequence number to take into account the future evolution of interfaces. The rule NR051 for interfaces is similar to NR044 for data types. Example: <SENDER-RECEIVER-INTERFACE> <SHORT-NAME>BattU1</SHORT-NAME> <LONG-NAME><L-4 L="EN">BatteryVoltage</L-4></LONG-NAME> <DESC><L-2 L="EN">This interface provides the actual voltage level as measured at the battery.</L-2></DESC> <DATA-ELEMENTS> <VARIABLE-DATA-PROTOTYPE> <SHORT-NAME>BattU</SHORT-NAME> <TYPE-TREF DEST="APPLICATION-PRIMITIVE-DATA-TYPE" BASE="ARApplicationDataTypes">U1</TYPE-TREF> </VARIABLE-DATA-PROTOTYPE> </DATA-ELEMENTS> </SENDER-RECEIVER-INTERFACE>

Recommendations: A SenderReceiverInterface should be a reusable element. The name should be independent of its concrete usage by components and ports and should only reflect its general purpose. To allow reuse, the communication path (the indication of source or destination of ports using the interface) should not be encoded in the interface name. The following short names are bad examples for interface names: YawRateStdByEsc YawRateStdBySecCtrlrYawRate The interface name in this example shall be “YawRate1” and reused by two ports whose names could be “YawRateStdByEsc” and “YawRateStdBySecCtrlrYawRate”. 6.4.3 VariableDataPrototype (VARIABLE-DATA-PROTOTYPE) Objectives:

Should only be significant relative to the SenderReceiverInterface. Shall be a unique name per SenderReceiverInterface.

Rules:

[NR026] The name shall reflect the content of the data. If no sensible name for the data element can be found and the interface is used to indicate a data transfer, it is recommended to use the name Val (abbreviation of Value).

Example:

<VARIABLE-DATA-PROTOTYPE>


<SHORT-NAME>Val</SHORT-NAME>


R4.0 Rev 2

<TYPE-TREF DEST='APPLICATION-PRIMITIVE-DATA-TYPE'>/AUTOSAR/ARDataTypes/T1</TYPE-TREF> </VARIABLE-DATA-PROTOTYPE>

[NR027] If the data element prototype contains no value information, but an

operation, the name shall reflect the operation that is driven by the data element prototype. Example: Cls (abbreviation of Close). If no sensible name for the data element prototype can be found and the interface is used to indicate an operation, the name Oper (abbreviation of Operation) should be used.

[NR029] If the SenderReceiverInterface contains more than one data element prototype denoting the same operation, a “Mean/Environment/Device” keyword must be used to differentiate the operations. (Here “operation” is not used in the sense of ClientServerInterface operations, but as an operation or action which is triggered by a SenderReceiver communication. “Operation” is also not identical to the semantic field “Action”.) Example: UserTransmit UsrTx TelegramTrasmit TelgrmTx ExteriorLightDisplay ExtrLiDisp ParkingLightDisplay PrkgLiDisp Remark: In the last two examples all keywords are classified as “Mean/Environment/Device” so they can be arranged in any order

Recommendations:

Repeating the name of the enclosing interface in the name of the data element is allowed, but not recommended. Repetition of the name would result in redundant information and would reflect negatively in RTE generated function names (see ch 6.2.3 for an example of distribution of information between interface name and data element name).

6.4.4 ApplicationDataType The following classes are subclasses of the class ApplicationDataType in the AUTOSAR meta model. Therefore, the naming convention applies also to these classes. ApplicationPrimitiveType (APPLICATION-PRIMITIVE-TYPE) ApplicationRecordType (APPLICATION-RECORD_DATA-TYPE) ApplicationArrayType (APPLICATION-ARRAY-TYPE)

The name will show up at implementation level via “typedef” Rules:

[NR056] The name shall reflect the meaning of the type.

[NR057] No prefixes, such as “t_” shall be used in the type name.



R4.0 Rev 2

[NR055] No numbers shall be used in an ApplicationArrayType name to specify its length.

[NR044] The data type name shall end with a sequence number to take into

account the future evolution. This rule shall also be applied to distinguish data types, which represent the same physical entity, but with different ranges or resolution i.e. names of such data types shall differ only for the sequence number.

Example: Temperature1 T1 Temperature2 T2 Temperature3 T3 The rules NR044 ensures the reusability of the data types.

[NR048] To allow reuse, the communication path shall not be encoded in the

data type name. Example XML:

<APPLICATION-PRIMITIVE-DATA-TYPE> <SHORT-NAME>U1</SHORT-NAME> <LONG-NAME><L-4 L="EN">Voltage1</L-4></LONG-NAME> <DESC><L-2 L="EN">Generic voltage data type 1</L-2></DESC> <CATEGORY>VALUE</CATEGORY> <SW-DATA-DEF-PROPS> <SW-DATA-DEF-PROPS-VARIANTS> <SW-DATA-DEF-PROPS-CONDITIONAL> <DATA-CONSTR-REF DEST="DATA-CONSTR" BASE="ARDataConstrs">U1</DATA-CONSTR-REF> <SW-INTENDED-RESOLUTION>0.1</SW-INTENDED-RESOLUTION> <UNIT-REF DEST="UNIT" BASE="ARUnits">Volt</UNIT-REF> </SW-DATA-DEF-PROPS-CONDITIONAL> </SW-DATA-DEF-PROPS-VARIANTS> </SW-DATA-DEF-PROPS> </APPLICATION-PRIMITIVE-DATA-TYPE>

6.4.5 CompuMethod (COMPU-METHOD) No specific naming convention rules for COMPU-METHOD elements are defined. Example: <COMPU-METHOD> <SHORT-NAME>U1</SHORT-NAME> <CATEGORY>LINEAR</CATEGORY> <UNIT-REF DEST="UNIT" BASE="ARUnits">Volt</UNIT-REF> <COMPU-PHYS-TO-INTERNAL> <COMPU-SCALES> <COMPU-SCALE> <LOWER-LIMIT INTERVAL-TYPE="CLOSED">0</LOWER-LIMIT> <UPPER-LIMIT INTERVAL-TYPE="CLOSED">25.2</UPPER-LIMIT> <COMPU-RATIONAL-COEFFS> <COMPU-NUMERATOR> <V>0</V> <V>0.1</V> </COMPU-NUMERATOR> <COMPU-DENOMINATOR>



R4.0 Rev 2

<V>1</V> </COMPU-DENOMINATOR> </COMPU-RATIONAL-COEFFS> </COMPU-SCALE> </COMPU-SCALES> </COMPU-PHYS-TO-INTERNAL> </COMPU-METHOD>

6.4.6 SwComponentType (COMPOSITION-SW-COMPONENT-TYPE) The naming convention applies to the following subclasses of the class SwComponentType: ApplicationSwComponentType CompositionSwComponentType SensorActuatorSwComponentType ParameterSwComponentType Objectives:

Avoid name clashes within the package Classification of components Not for component prototypes (see 6.4.7)

Rules

[NR035] Using a prefix to indicate the application domain (such as powertrain, body, chassis) of the SwComponentType is not allowed.

Recommendations:

Use a noun or concatenation of nouns. Example SensorSpeed SnsrSpd

The name should be understandable.

Examples VehicleSpeed VehSpd VehicleMotionDemand VehMtnDmd WiperWasher WiprWshr

Example (to shorten the example, some lines have been removed): <COMPOSITION-SW-COMPONENT-TYPE> <SHORT-NAME>KeyPad</SHORT-NAME> <PORTS> <P-PORT-PROTOTYPE> <SHORT-NAME>DrvrDoorKeyPad</SHORT-NAME> <DESC><L-2 L='EN'></L-2></DESC> <PROVIDED-INTERFACE-TREF DEST='SENDER-RECEIVER-INTERFACE'>/AUTOSAR/ARSenderReceiverInterface/LockgCenReq1</PROVIDED-INTERFACE-TREF> </P-PORT-PROTOTYPE> …some ports skipped <P-PORT-PROTOTYPE> <SHORT-NAME>KeyPadOfLidRe</SHORT-NAME> <DESC><L-2 L='EN'></L-2></DESC> <PROVIDED-INTERFACE-TREF DEST='SENDER-RECEIVER-INTERFACE'>/AUTOSAR/ARSenderReceiverInterface/LockgCenReq1</PROVIDED-INTERFACE-TREF> </P-PORT-PROTOTYPE> </PORTS> <COMPONENTS> <SW-COMPONENT-PROTOTYPE> <SHORT-NAME>KeyPadMgr</SHORT-NAME>



R4.0 Rev 2

<TYPE-TREF DEST='COMPOSITION-SW-COMPONENT-TYPE'>/AUTOSAR/ARComponentTypes/KeyPadMgr</TYPE-TREF> </SW-COMPONENT-PROTOTYPE> </COMPONENTS> <CONNECTORS> <DELEGATION-SW-CONNECTOR> <SHORT-NAME>delcon_0</SHORT-NAME> <INNER-PORT-IREF> <P-PORT-IN-COMPOSITION-INSTANCE-REF> <CONTEXT-COMPONENT-REF DEST='SW-COMPONENT-PROTOTYPE'>/AUTOSAR/ARComponentTypes/KeyPad/KeyPadMgr</CONTEXT-COMPONENT-REF> <TARGET-P-PORT-REF DEST='P-PORT-PROTOTYPE'>/AUTOSAR/ARComponentTypes/KeyPadMgr/DrvrDoorKeyPad</TARGET-P-PORT-REF> </P-PORT-IN-COMPOSITION-INSTANCE-REF> </INNER-PORT-IREF> <OUTER-PORT-REF DEST='P-PORT-PROTOTYPE'>/AUTOSAR/ARComponentTypes/KeyPad/DrvrDoorKeyPad</OUTER-PORT-REF> </DELEGATION-SW-CONNECTOR> ….some delegation ports skipped </CONNECTORS> </COMPOSITION-SW-COMPONENT-TYPE>

KeyPadMgr

DrvrDoorKeypad

DrvrDoorKeypad

Figure 7: Example of SwComponentType 6.4.7 SwComponentPrototype (SW-COMPONENT-PROTOTYPE) Objectives of naming conventions for component prototypes (which are the instances of each component type):

avoid name clashes within the composition classification of components

These names are not used within the API to the RTE. Rules:

[NR036] Using a prefix to indicate the application domain (such as powertrain, body, chassis) of the SwComponentPrototype is not allowed.

Recommendations:

The name should be understandable. In case a composition contains more than one instance of the same component type, the prototype name should reflect the role of this specific instance in the composition. An example on how to name multiple SwComponentPrototypes is given in section 5.2.

KeyPadOfLidRe

SwComponentPrototype

SwComponentType KeyPad



R4.0 Rev 2

Example: DoorLe, DoorRi Example: <SW-COMPONENT-PROTOTYPE> <SHORT-NAME>MgrOfMirrAdjAutReqByUsr</SHORT-NAME> <TYPE-TREF DEST='COMPOSITION-SW-COMPONENT-TYPE'>/AUTOSAR/ARComponentTypes/MgrOfMirrAdjAutReqByUsr</TYPE-TREF> </SW-COMPONENT-PROTOTYPE>

6.4.8 PortPrototype (P-PORT-PROTOTYPE, R-PORT-PROTOTYPE) Objectives:

should only be significant relative to the SW component (e.g. left, right etc.) unique name per component

PortProtoypes can be connected as long as they are typed with compatible PortInterfaces. Please refer to document [3] for such compatibility rules. Rules:

[NR037] The PortPrototype shall indicate the operation or data that is provided/required by the port

[NR052] Port names shall not contain sequence numbers. Example: Short-Name: PassDoorLockSt <R-PORT-PROTOTYPE> <SHORT-NAME>PassDoorLockSt</SHORT-NAME> <DESC><L-2 L='EN'></L-2></DESC> <REQUIRED-INTERFACE-TREF DEST='SENDER-RECEIVER-INTERFACE'>/AUTOSAR/ARSenderReceiverInterface/LockSts1</REQUIRED-INTERFACE-TREF> </R-PORT-PROTOTYPE>

6.4.9 Units (UNIT) Objectives:

Shall be unique. Rules:

[NR040] If the unit is a formula containing “x to the power of 2” the name shall contain “Squared”.

[NR041] If the unit is a formula containing “x to the power of 3” the name shall contain “Cubed”.

[NR042] If the unit is a formula containing “x to the power of number >3” the name shall contain ToPwrOf<number>.

[NR043] If the unit is a formula containing a division the name shall contain “Per”

Example:



R4.0 Rev 2

<UNIT> <SHORT-NAME>NwtPerMtr</SHORT-NAME> <DESC><L-2 L='EN'>surface tension (derived from SI units).</L-2></DESC> <DISPLAY-NAME>N/m</DISPLAY-NAME> </UNIT> <UNIT> <SHORT-NAME>NwtSecPerMtr</SHORT-NAME> <DESC><L-2 L='EN'>damping factor or coefficient (derived from SI units)</L-2></DESC> <DISPLAY-NAME>Ns/m</DISPLAY-NAME> </UNIT> <UNIT> <SHORT-NAME>MtrPerSecCubd</SHORT-NAME> <DESC><L-2 L='EN'>jerk (derived from SI units),also called jolt (esp. in British English), surge or lurch, is the rate of change of acceleration; more precisely, the derivative of acceleration with respect to time, the second derivative of velocity, or the third derivative of displacement. </L-2></DESC> <DISPLAY-NAME>m/s^3</DISPLAY-NAME> </UNIT>

6.4.10 Enumerations There is no explicit support for enumeration types in the metamodel. Enumerations are modeled by using a DataType and a CompuMethod. Example: <APPLICATION-PRIMITIVE-DATA-TYPE> <SHORT-NAME>UsrReqForWipg1</SHORT-NAME> <DESC><L-2 L="EN">It represents the selection of the interval time or the speed of the wiper requested by the user. The exact timings and wipe speeds are not standardized and need therefore to be parameterized.</L-2></DESC> <CATEGORY>VALUE</CATEGORY> <SW-DATA-DEF-PROPS> <SW-DATA-DEF-PROPS-VARIANTS> <SW-DATA-DEF-PROPS-CONDITIONAL> <COMPU-METHOD-REF DEST="COMPU-METHOD" BASE="ARCompuMethods">UsrReqForWipg1</COMPU-METHOD-REF> <DATA-CONSTR-REF DEST="DATA-CONSTR" BASE="ARDataConstrs">UsrReqForWipg1</DATA-CONSTR-REF> </SW-DATA-DEF-PROPS-CONDITIONAL> </SW-DATA-DEF-PROPS-VARIANTS> </SW-DATA-DEF-PROPS> </APPLICATION-PRIMITIVE-DATA-TYPE> <COMPU-METHOD> <SHORT-NAME>UsrReqForWipg1</SHORT-NAME> <LONG-NAME><L-4 L="EN">Enumeration{ UsrReqForWipgSpdHi, UsrReqForWipgIntl, UsrReqForWipgSpdLo, UsrReqForWipgOff, WipgStrikeSngReqByUsr }</L-4></LONG-NAME> <CATEGORY>TEXTTABLE</CATEGORY> <COMPU-INTERNAL-TO-PHYS> <COMPU-SCALES> <COMPU-SCALE> <DESC><L-2 L="EN">4 = UsrReqForWipgSpdHi</L-2></DESC> <LOWER-LIMIT>4</LOWER-LIMIT> <UPPER-LIMIT>4</UPPER-LIMIT> <COMPU-CONST><VT>UsrReqForWipgSpdHi</VT></COMPU-CONST> </COMPU-SCALE> <COMPU-SCALE> <DESC><L-2 L="EN">2 = UsrReqForWipgIntl</L-2></DESC> <LOWER-LIMIT>2</LOWER-LIMIT> <UPPER-LIMIT>2</UPPER-LIMIT> <COMPU-CONST><VT>UsrReqForWipgIntl</VT></COMPU-CONST> </COMPU-SCALE> <COMPU-SCALE> <DESC><L-2 L="EN">3 = UsrReqForWipgSpdLo</L-2></DESC> <LOWER-LIMIT>3</LOWER-LIMIT> <UPPER-LIMIT>3</UPPER-LIMIT> <COMPU-CONST><VT>UsrReqForWipgSpdLo</VT></COMPU-CONST> </COMPU-SCALE>



R4.0 Rev 2

<COMPU-SCALE> <DESC><L-2 L="EN">0 = UsrReqForWipgOff</L-2></DESC> <LOWER-LIMIT>0</LOWER-LIMIT> <UPPER-LIMIT>0</UPPER-LIMIT> <COMPU-CONST><VT>UsrReqForWipgOff</VT></COMPU-CONST> </COMPU-SCALE> <COMPU-SCALE> <DESC><L-2 L="EN">1 = WipgStrikeSngReqByUsr</L-2></DESC> <LOWER-LIMIT>1</LOWER-LIMIT> <UPPER-LIMIT>1</UPPER-LIMIT> <COMPU-CONST><VT>WipgStrikeSngReqByUsr</VT></COMPU-CONST> </COMPU-SCALE> </COMPU-SCALES> </COMPU-INTERNAL-TO-PHYS> </COMPU-METHOD>

6.4.11 ClientServerInterface (CLIENT-SERVER-INTERFACE) While modeling a ClientServerInterface, names for the following attributes shall be also defined:

OperationPrototype ArgumentPrototype

Rules:

[NR062] The interface name shall end with a sequence number to take into account the future evolution of interfaces.

The name of OperationPrototype attribute shall follow rule NR029 in place for VariableDataPrototype (see 6.4.3)

The name of ArgumentPrototype attribute shall follow all the rules in place for VariableDataPrototype (see 6.4.3)

Recommendations:

A ClientServerInterface should be a reusable element. The name of interface should be independent of its concrete usage by components and ports and should only reflect its general purpose.

To allow reuse, the communication path (the indication of source or destination of ports using the interface) shall not be encoded in the interface name.

The name of ArgumentPrototype attribute should follow all the recommendation in place for VariableDataPrototype (see 6.4.3)

The name of OperationPrototype attribute should start with a keyword classified as “Action / Physical Type”

Example for OperationPrototype: Short-Name: SetEventStatus 6.4.12 ParameterInterface (PARAMETER-INTERFACE) To this model element, same rules and recommendations as for SenderReceiverInterface (see Ch 6.4.2) apply. 35 of 64 Document ID 207: AUTOSAR_TR_SWCModelingGuide



R4.0 Rev 2

6.4.13 ParameterDataPrototype (PARAMETER-DATA-PROTOTYPE) Objectives:

Should only be significant relative to the ParameterInterface. Shall be a unique name per ParameterInterface.

To this model element, same rules and recommendations as for VariableDataPrototype (see Ch 6.4.3) apply. 6.4.14 PortBlueprint (PORT-BLUEPRINT) PortBlueprints allow the user to define reusable ports outside the scope of a SwComponentType, i.e. each PortBlueprint can be used to create more than one PortPrototype. See document [3] for further explanation. Objectives:

Shall be a unique name per ARPackage. PortBlueprints names follow all the naming convention rules in place for PortPrototypes as defined in chapter 6.4.8. Example: <AR-PACKAGE> <SHORT-NAME>ARPortPrototypeBlueprints</SHORT-NAME> <CATEGORY>BLUEPRINT</CATEGORY> <AR-PACKAGES> <AR-PACKAGE> <SHORT-NAME>Body</SHORT-NAME> <ELEMENTS> <PORT-BLUEPRINT> <SHORT-NAME>DrvrProf</SHORT-NAME> <DESC><L-2 L='EN'></L-2></DESC> <INTERFACE-REF DEST='SENDER-RECEIVER-INTERFACE'>/AUTOSAR/ARSenderReceiverInterface/ProfPenSts1</INTERFACE-REF> </PORT-BLUEPRINT> </ELEMENTS> </AR-PACKAGE> </AR-PACKAGES> </AR-PACKAGE>

6.4.15 DataConstrs (DATA-CONSTRS) No specific naming convention rules for DATA-CONSTRS elements are defined. Example: <DATA-CONSTR> <SHORT-NAME>Boolean</SHORT-NAME> <DATA-CONSTR-RULES> <DATA-CONSTR-RULE> <PHYS-CONSTRS> <LOWER-LIMIT INTERVAL-TYPE="CLOSED">0</LOWER-LIMIT>



R4.0 Rev 2

<UPPER-LIMIT INTERVAL-TYPE="CLOSED">1</UPPER-LIMIT> </PHYS-CONSTRS> </DATA-CONSTR-RULE> </DATA-CONSTR-RULES> </DATA-CONSTR>



R4.0 Rev 2

7 Appendix: Keywords

Keyword Abbreviation Keyword Definition English M

ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names)

0 0

Index 0. This keyword is used to express the number zero in form of an index

x

DamprMod0

1 1

Index 1. This keyword is used to express the number one in form of an index x BrkReqTyp1

2 2

Index 2. This keyword is used to express the number two in form of an index x BrkReqTyp2

3 3

Index 3. This keyword is used to express the number three in form of an index x AgSpd3

4 4

Index 4. This keyword is used to express the number four in form of an index x Ag4

5 5

Index 5. This keyword is used to express the number five in form of an index x Fac5

6 6

Index 6. This keyword is used to express the number six in form of an index x Perc6

7 7

Index 7. This keyword is used to express the number seven in form of an index x A7

8 8

Index 8. This keyword is used to express the number eight in form of an index x Len8

9 9

Index 9. This keyword is used to express the number nine in form of an index x Prof9

1d 1d

index 1D. used for location of oxigen sensors (4 banks and 2 sensors) - Parameter Identification 1D according with ISO15031-5. 2 banks and 4 sensors are identified by the index 13 x

Abort Abort x Abort Abs Abs antilock braking system x AbsCtrlActv Absolute Abslt Absolute value x BodyPitchAgAbsltEstimd Ac Ac Alternating current / voltage x Acc Acc Adaptive Cruise Control x AccActv

Acceleration A

This keyword is used to give the physical value of acceleration. It is the value of gaining speed. x WhlAVertBas

Accelerator Accr x AccrPedlRat Accept Acpt x TirePMonAcptOfWhlsNew Access Acs x AcsKeyls Accessory Acsy x AcsyPost Accommodation Acco x Acknowledge Ack x DispBltLockAck Acknowledged Ackd x

Acoustic Acoust x SeatBltRmnAcoustWarnReq

Acquire Acq x Acquired Acqd x Action Actn x MirrActnSt Activate Actvt x ActvtWipgAutFromHmi Activated Actvd x Actvd Activation Actvn x MirrActvn Active Actv x BrkActrActv



R4.0 Rev 2

Mea

n-E

nviro

nmen

t-D

evic

e

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Pre

posi

tion

Inde

x

Keyword Abbreviation Keyword Definition English Use Case (short names)

Actual Act x RollCmpLvlAct Actuation Acttn x Acttn Actuator Actr x BrkActrMod Adapter Adpr x MirrActrAdpr Adaptive Adpv x Additional Addl x SteerAgFrntAddlReqd Additive Add x Address Adr x Adhesion Adh x Adjust Adj x MirrAdjMgr Adjustment Adjmt x MirrAdjmt Advance Adv x After Aft x Aging Agi x Ahead Ahd x WhlAhdOrStandStill Aid Aid x PullAidReRi Air Air Also used as definition of "fresh gas" x Airbag Airb airbag x Ajar Ajar x Ajar Alarm Alrm x AlrmSt Alarmed Alrmd x Alrmd All All x InhbShiftAll Allowable Allwbl x Allowed Allwd x Alternative Altv x Alternator Alt alternator x AltTqReq Altitude Alti x Ambient Amb x Amount Amnt x RainAmntSts Ampere Ampr x AmprPerMtr Amplitude Amp x Amp Amt Amt automated manual transmission x Amt Analog An x Anchorfitting Anchrfitg x ActrAnchrfitgTensnrAtDrvr And And Preposition x EngSpdAndPosn Angle Ag x BodyPitchAgAbsltEstimd Angular Agr x WhlAAgrStd Anti-submarine Antisub x Antitheft Antithft x SnsrCtrlOfAntithftPas Apillar Apil A-Pillar of a car x ApilPedProtnLe Application Appl x Applied Appld x PrkgBrkAppldIndcn Apply Apply x ApplyReq Approved Aprvd x IdAprvd Arbitrated Arbd x Arbitration Arbn x AArbnRes Area Ar x

Arm Arm Intended as the action of arming some device x ArmCmd

Armature Armtr

This keyword described the constructional element of an armature. It should be used e.g. for calculations of the armature movement of a coil actuator. x

Armed Armed x PreArmed

Arming Arming Intended as the action of arming some device x Arming

Array Ary x Asc Asc Acceleration Slip Control x Ashtray Ashtray x AshtrayLiGroup Assist Assi x BrkAssiReq



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion


Assistance Assc

assistance. this keyword expresses the availability of an electronic assitance for a component or system x SteerDrvrAsscSys

Assistant Asst assistant. For example: the electronic brake assistant. x

Assisted Assid x Asynchronous Async x At At Preposition for location, time, presence x TqActAtClu

Attenuator Attn

The attenuator switch is a part of the powerstage which drives the piezo injectors. x

Australia Australia x CtryCodAustralia Authentication Authent x TrsmAuthent Authorization Authn x KeyAuthn Authorize Auth x Automatic Aut x PanAdjAut Auxiliary Aux x Available Avl x Axis Axis x AxisPosn Axle Axle x AxleFrnt Axles Axles Front and rear axel x TirePMonPTarAtAxles Back Back anatomic human back x BackBlstrPosnRi Backed Backed x SnsrSoundrBattBacked Backlit Backlt x Backlite Backlite x BackliteWinSt Backward Backw x RollgBackw Balance Bal x HndlgBalCoeff Bank Bnk x RoadBnkAEstimn Bar Bar As unit of measure x Bar Barometric Baro x

Base Bas Preprocessed sensor data, model free, abstraction of the sensor hardware. x PitchRateBas

Basic Basc x WhlSteerReBascErrSts Battery Batt x BattMonr Beam Beam x BeamLoIndcn Belgium Belgium x CtryCodBelgium

Belt Blt

seat belt. this keyword is used to express the seat belt, which is a kind of security rope to keep the passenger in the seat in case of an accident. x DispBltLockStOfDrvr

Bench Bench

bench mode. During OBD I / OBD II diagnoses and error management validation and tuning, the bench mode has to be used so as to force some failures. x

Bicycle Bicycle x MotorcycleBicycle Blind Bli x Blink Blink x BlinkMgr Block Blk x Blocked Blkd x Board Bd x Body Body x BodyPitchAgRelEstimd Bolster Blstr x BackBlstrPosnRi

Boost Boost

A general expression to increase performance for a short period of time or to give a higher output. e.g. to give high voltage output or to support the combustion engine with additional torque (e.g. with a Integrated Starter Generator) for acceleration x

Boot Boot x Bottom Botm x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Bounce Bnce x Boundless Bndls x KnobRotyBndlsStep15 Box Box x GlvBoxSt Bpillar Bpil B-Pillar of a car x Bracket Brkt x Brake Brk x BrkActrMod Braking Brkg x BrkgCtrlDyn Brazil Brazil x CtryCodBrazil Break Break x SnsrForGlassBreak Bridge Brdg bridge contact x Brightness Bri x OutdBri

Buckle Buc Part of supplement restraint system to protect occupant in case of crash x ActrBucRtrctrAtDrvr

Buckled Bucd Buckling of occupant x DispBucdStOfDrvr Buffer Buf x Bumper Bmp x AOnBmpAtFrntLe Burner Brnr x Burning Brng x

Bus Bus used for the vehicle and not as a data bus x TruckBusVan

Button Btn x EpbBtnCtrlSt Buzzer Buz x By By Preposition x Bypass Byp x BypSlipCtrlReqByRsc Cabin Cbn x CbnLiFrntCen Calculated Calcd x PedCrashSevCalcd Calculation Calcn x SeatBltRmnCalcn Calibration Cal x TirePMonCalStsAtReRi Call Call x Camshaft Camsft x Canada Canada x CtryCodCanada Cancel Cncl x Cncl Cancelled Cncld x Candela Cd Unit of measure of luminous intensity x Cd Canister Cstr x Capability Cpby x

Capacity Cp

this keyword is used to express the Physical Meaning of a capacity (e.g. thermal capacity of oil) x

Car Car x CarFindr Case Case x Catalyst Cat x Centigrade Cgrd x DegCgrd Central Cen x LockgCen Chamber Chmb x Change Chg x ChgInfoOfBltLockSt

Channel Ch

This keyword is used to express a channel. A channel is a defined port (of a bundle of ports) of a data line. x

Characteristic Chartc x Charge Chrg x ChrgOff Charger Chrgr x Charging Chrgn x Chrgn Chassis Chassis x ChassisNr Check Chk x Checksum Chks x Child Chd x ChdProtn Chimer Chimer x ChimerFb China China x CtryCodChina Chirp Chirp x ChirpTyp



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion


Choke Choke

Choking, choke line. this keyword is used to describe the appearance of choking effects in an (air-)stream, e.g. at the choke line of a turbocharger (which is a characteristic parameter) x

Cigarette Cigarette x Circuit Circ x

Circumference Circum Used in the meaning of the wheel circumference x

Circumferential Circuml x WhlSpdCircumlStd Clamp Clmp x ClmpCtrl Clamped Clmpd x Class Class x Classification Classn x NoClassn Cleaner Clnr x

Cleaning Clng Cleaning. This keyword describes the action of cleaning e.g. a component. x

Clear Clr x Cleared Clrd x Climatisation Clima x Clock Clk x Close Cls x OpenClsCmft Closed Clsd x OpendClsd Clutch Clu x TqActAtClu

Coasting Coast

situation of vehicle, where the clutch is kept open and the vehicle is moving by its own inertia, e.g. rolling downhill (coast driving state of a vehicle is a typical transmission / clutch function). x

Coated Cot x Code Cod x CtryCod Coefficient Coeff x HndlgBalCoeff Cog Cog Center of Gravity x CogPosnEstimd Coil Coil x Cold Cold x Collector Coll x Collision Cllsn x Column Col x Combustion Cmb x CmbEngSts

Comfort Cmft comfort. this keyword is used to express something as comfortable or convenient x ACmdForCmft

Coming Cmng x HomeCmngAndHomeLvng Command Cmd x DrvrDoorLockgCmd

Common Cmn

common. for common environmental data (stored with all failures of one project). x

Communication Com x AlrmByCom Commutation Cmu x Comparison Comp x Compartment Cmptmt x Compensation Cmp x RollCmpLvlAct Complement Cpl x Complete Cmpl x Complex Cmplx x SnsrAdprCmplxAlrm Component Cpt x Compression Cmpn x

Compressor Cmpr

This keyword is used to express a component producing a compressed (= with raised pressure) working medium, e.g. air, refrigerant. x

Concentration Conc x Condition Cdn x RoadCdn



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Conditioner Cdnr x Conditioning Cdng x Configuration Cfg x Configured Cfgd x Confirmation Cfm x Confirmed Cfmd x Constant Con x Consume Cnse x CnseEgy Consumption Cns x Continuous Contns x Control Ctrl x BodyLvlCtrl Controlled Ctrld x Controller Ctrlr x InterdomCtrlr Convection Cnvc x Conversion Cnvn x Converter Cnvr x Convertible Cnvtb x RoofCnvtb Cool Cool x DrvrCoolSeatFlt Coolant Coolt x

Cooling Coolg

This keyword is used to describe the cooling system e.g. of the engine. A cooling request can be fulfilled by air, coolant, ECF, CWP, etc. x CoolgReq

Coordinated Coord x Coordination Coorn x Coordinator Coorr x PtCoorr Copy Copy x Corner Cornr x CornrMkr Cornering Cornrg x AdprCornrg Corrected Corrd x VehCourseCrvtCorrd Correction Corrn x Correlation Corrln x Coulomb Coulomb Unit of measure for Electric charge x Coulomb Count Cnt x Counter Cntr Also applicable to running indexes. x Countershaft Ctrsft x GbxCtrsftActv Country Ctry x CtryCod Coupled Coupld x

Coupling Coupl

It is the keyword for any linkage of software modules or functionalities or to express a kind of strict connection between two elsewise not linked parts. x

Course Course x VehCourseCrvtPred Cpillar Cpil C-Pillar of a car x Crank Crk x Crk Crankcase Crkcs x Crankshaft Crksft x Crash Crash x VehCrashDetn Crawl Crawl x

Creep Crp example: creep mode of automatic transmission x

Criteria Cta x Critical Crit x Cruise Crs x CrsCtrlActv Cryptography Crypto x CryptoProcStsReq1 Cubed Cubd x MtrCubd Cubic Cub x Curb Curb American english for Kerb x CurbLiFrntLe Curtain Curt x Curvature Crvt x VehCourseCrvtPred Cushion Cush x CushBlstrPosnRi



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Customer Cust x Cut Cut x AlrmByLineCut Cvt Cvt continuous variable transmission x Cvt Cycle Cyc x IndcrCyc Cylinder Cyl x D D Differential part of a control structure x Damper Dampr x DamprSts Damping Dampg x Das Das Driver Assistance System x Dashboard Dshb x DshbBri Dashpot Dash x Data Data x ListOfObjDataRlvForAcc

Date Date

date, point of time. This keyword is used to refer to a precise moment or a specific date. This can be a "time stamp" or a calendar date as well. x

DateTi

Day Day x Day Daytime Dayti x LiDaytiRunng Dc Dc direct current/voltage x

Dcc Dcc

distance cruise control. In case of cruise control on, the distance to the vehicle ahead is measured. If the distance falls below a defined limit, the vehicle speed is reduced automatically. x

Dct Dct Dual Clutch Transmission x Dct Deactivate Deactvt x Deactvt Deactivated Deactvd x Deactvd Deactivation Deactvn x Deadband Dbnd x BrkActrTqDbnd Debounce Deb x Deceleration Decel x

Decrease Dec

decrease, decrementation. this keyword is used to express the stepwise descent of a value or counter. x

EngTqDecAtCrksftReqdByEscFast

Default Dft default x Defect Dfct x DispDfct Defined Defd x NotDefd Defrost Defrst x DefrstCtrl

Defueling Defu defueling. It shall be used to describe the action of taking fuel out of the tank. x

Degraded Degraded x Degraded Degree Deg x DegCgrd Delay Dly x Delta Delta x Dem Dem Diagnostic Event Manager x Demand Dmd x HldOnDmdSt Density Dens x Depression Dep x Desired Des x DftlTqDesAtAxleRe Detected Detd x Detection Detn x OccptDetn Deviation De x Device Dev x DevSts1 Dew Dew Dew Point x Diagnosis Diag x BackliteWinDiagLock Diagnostic Diagc x DiagcReq

Diameter Diam This name describes the component size, e.g. of driving wheels x

Diesel Dsl x Difference Dif x WhlLoadDifEstimdFrnt Differential Dftl drive train context x DftlTqDesAtAxleRe Digital Dig x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Dilution Dil x Dim Dim used as compound with Light x LiDimGlb Direction Dir x WhlDirRotlStd Directory Dire x Disable Di x WipgDiFrnt

Disappear Disa disappear. used, in order to define a state of failure: "disappeared failure" x

Disarm Disarm x DisarmCmd Disarmed Disarmed x Disarmed Discharge Dcha x Dcha Discrete Dis x Disk Dsk x Displacement Dpl x DplLat

Display Disp

In both meanings, the display (Component) and to display (Characteristic) x PrkgLiDisp

Displayed Dispd x SetSpdDispd Distance Dst x WhlDstTrvld Distribution Distbn x DtTqDistbn Division Div x Door Door x DoorLockStReLe Down Dwn x

Drag Drg

resistance, caused by mechanical, aerodynamical of topographical influences, being effective against a movement x

Drift Drift x Drive Drv drive (gear engaged) x Drv Driver Drvr Driver of the vehicle. x DrvrDoorLock Drivetrain Dt x DtTqDistbn Driving Drvg Action of driving the vehicle. x Drop Drp x

Dry Dry dry. dry is the opposite of lubricated in case of friction x

Dtd Dtd Drivetrain Torque Distribution x Dummy Dummy x Dummy Duration Durn x During Durg x DurgRels Duty Duty x Dynamic Dyn x EngTqCorrnDyn Dynamometer Dyno x Easy Easy x EntryEasy1 Ec Ec Eupopean Community x CtryCodEc

Economy Eco

economy. related to the detection of driver type either an economy/comfort oriented or a sportive/power requesting driver can be distinguished. x

Ecu Ecu electronic control unit x Edge Edge x Edit Edit x Effective Efc x Efficiency Eff x Egr Egr exhaust gas recirculation x Egypt Egypt x CtryCodEgypt Ehb Ehb electro hydraulic brake x Elapsed Elpd x Electric Elec x MacElec Electronic Electc x Electropneumatic Eltpnm x Element Elm x Elm Emergency Emgy x EmgyLockg Emission Emi x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Empty Empty x WshrFldEmpty Emulated Emuld x Emulation Emuln x Enable Ena x WiprWshrEnaDi Enabled Enad x Enabling Enag x End End x Energy Egy x EgyMngt Engaged Engd x GearParkEngd

Engagement Engmt

engagement. to express the situation of engaging e.g. a gear from neutral position / transmission gutter until synchronization performed. x

Engine Eng x England England x CtryCodEngland Enhanced Enhd x Enhancement Enhmt x Enough Engh x WshrFldEngh Enrichment Enchmt x Entry Entry x EntryEasy1 Environmental Envtl x Epb Epb Electric Parking Brake x EpbActrMod Equal Equ x Equipment Equip x Equipped Equid x Equivalent Equiv x Erase Erase x Error Err information of a defect x LampErrSts Esc Esc electronic stability control x EscSts Estimated Estimd x BodyPitchAgAbsltEstimd Estimation Estimn x RoadBnkAEstimn Estimator Estimr x Evaluation Evln x NoEvln Evaluator Evlr x EvlrWipgAut Evaporative Evap x Event Eve x GetEveSts Exceed Excd x Exceeded Excdd x SpdMaxExcdd Excenter Excr x Exception Excpn x

Excitation Exct

the keyword is used to express the technical effect of excitation, e.g. in connection with a current or a voltage in a generator x RoadExct

Exclusion Exclsn x SnsrExclsn Exist Exist x NotExist

Expansion Exp This keyword can be used for the expansion phase of the engine cycle. x

Experiment Expt

experiment. In contrast to the keyword Test, it is not used to check an existing functionality, but to try something new. x

Export Exprt x Extend Extn x CushPosnExtn Extended Extd x RollRateRngExtd Exterior Extr x ExtrLiMgr External Ext x YawTqExtReqd Extrapolation Extrpn x Faced Facd x Factor Fac factor, coefficient x Fac6 Fade Fade x Failed Faild x EveStsFaild



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Failure Failr x SnsrFailrSt Falling Fall x Fan Fan x FanSt Farad Frd Unit of measure for Electric capacitance x Frd Fast Fast x Fault Flt x MirrFlt Favourable Fav x Feedback Fb x LockgFb Female Fmale x Field Fie x File File x Filling Fillg x Filter Fil x Filtered Fild x AccrPedlRatFild Final Final x ActvWarnFinal Finder Findr x CarFindr Fine Fine x Finished Finshd x CalFinshd First First x BltLockAtRowFirstMid Fixation Fixa x SeatFixaStsOfDrvr Fixed Fixd x Flag Flg Flag is a binary value. x Flank Flank x Flap Flap x TankFlap Flash Flash x FlashMgr Flashing Flsg x Flipper Flpr x FlprGlass Flood Flood x Flow Flow x Fluctuation Fluc x Fluid Fld x WshrFldTank Flywheel Flywh x Fm Fm frequency modulation x Fob Fob Transponder device in the Key x ImobFobSig1 Fog Fog x FogIndcnFrnt Fold Fold x HdPosnFold Follow Folw x VehDetdByFolwCtrl Follower Fol x Footwell Footwell Space for vehicle occupants legs x FootwellGroup For For Preposition x AFbForCmft Force F describes the physical parameter 'force' x DamprFEstimd Format Fmt x Forward Fwd x RollgFwd Free Free x CrsCtrlFree Freewheeling Fw x Frequency Frq x RadioFrqPanic Friction Fric Friction torque from turbo charger x FricCoeffEstimd From From Preposition x CoolgReqFromSteer Front Frnt x WiprFrnt Frozen Frzn x Fuel Fu x NoFuCutOff Full Full x SuspActvFullSts

Function Fct Purpose x SteerAgSuppsnEstimdOfCmftFct

Fusion Fusn x AccSnsrDataFusn Gain Gain x Gap Gap x TiGapInc Gas Gas x

Gasoline Gsl This keyword is used to express the fuel type "gasoline". x

Gear Gear x GearShiftPrevn



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Gearbox Gbx x Generated Gend x Generator Genr x PlsGenrMod Generic Gen x SnsrObjGen Germany Germany x CtryCodGermany Get Get x GetEveSts Giga Giga x GigaHz Glass Glass x FlprGlass Global Glb x LiDimGlb Glove Glv x GlvBoxSt Glow Glw x Governor Govr x Grade Grd x Gradient Grdt gradient/slope x EngNGrdt Gram Gr Unit of measure for mass x KiloGr

Gravity Grvy

This keyword describes the force of attraction between to masses, well known as gravity. x

Grip Grip example: Maximum desired engine torque for grip adaptation x

Ground Gnd x AlrmByGndLineCut Group Group x TrCmptmtGroup Gulf Gulf x CtryCodGulfRegn

Half Half

half, semi-. This keyword is used to characterize something for being only one part of two that make a whole item. Example: the time for a half engine segment. x

Handbrake Hndbrk x HndbrkSwt Handle Hndl The physical device for opening a door x DoorHndl Handling Hndlg x HndlgBalCoeff Hard Hard x HardClsd

Hardware Hw

This keyword is used to express a relationship to Hardware within a functionality or an environmental tools, e.g. Labcar. x

Hazard Hzrd x HzrdWarn Head Hd x HdMoveFold Header Hdr x Headlamp Hdlamp x WshrHdlamp Headrest Hdrest Headrest of seats x

Heal Heal

This keyword is needed for functions that try to heal a failure. E.g. an actuator or a control valve is blocked due to a dirt particel. A free-shaking control signal can lead to releasing the partikel from the actuator. x

Heat Heat x Heated Heatd x Heater Heatr x NozHeatr Heating Heatg x Heavy Hvy x Hecto Hecto Unit of measure for pressure x HectoPa Height Hei x PosnHei Hertz Hz Unit of measure for frequency x Hz Hibernate Hbrnt x HbrntLvl1 High Hi x BeamHi Hill Hill x History Hist for data stored in history memory x Hitch Hitch x TrlrHitch Hmi Hmi Human-Machine Interface x TankFlapHmi Hold Hld x HldOnDmdSt



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Home Home x HomeCmngAndHomeLvng Homogeneous Hom e. g. used in homogeneous injection x Hood Hood e. g. engine hood x EngHoodSt Hoop Hoop x HoopRollSts Horizontal Hozl x AxisHozl Horn Horn x HornCtrl Hot Hot x Hotel Htl x HtlMod Hour Hr Unit of measure for time x KiloMtrPerHr

Hud Hud

head up display. This keyword is used to express the feature of show information right in the field of view of the driver, e.g. by mirroring it onto the wind screen. x

Humidity Hum

the keyword is used to assign the amount of water in a gas or a gaseous mixture. Example: the humidity in the exhaust gas. x

Hvac Hvac Heating Ventilation and Air Conditioning x HvacDefrstReqFrnt

Hybrid Hyb

Any vehicle that combines two or more sources of power that can directly or indirectly provide propulsion power is a hybrid x

Hydraulic Hyd used to characterize hydraulic components x

SteerLoadHydAct

Hysteresis Hys x I I Electric current x

Ice Ice

This keyword expresses an interrelation with ice or with an icy environment, e.g. a functionality to improve the drivability on frosted streets. x

Identification Idn x DrvrKeyIdn Identifier Id x IdAprvd Idle Idle x Idle Ignition Ign x IgnOn Illumination Illmn x SwtIllmnForHzrdWarn

Immediate Imdt

this keyword is used to assign a requirement of minimum delay time or the need to take action as soon as possible. x

WipgImdt

Immobilisation Imobn Immobilisation x ImobnWirelsReq1 Immobilizer Imob x ImobMgr Impact Impct x Implausibility Impy x Implausible Imps x WipgSpdIntlImps Import Imprt x Impossible Impo x Impulse Imp x In In Preposition for location or condition x Inclination Incln x RoadInclnAEstimn Incline Incl x PosnIncl

Increase Inc This keyword is used to express a stepwise accretion of a value or counter x Inc

Increment Inct This keyword is used to express a stepwise accretion of a value or counter x

Index Idx x Idx India India x CtryCodIndia Indicated Indcd x Indication Indcn x PrkgLiIndcn Indicator Indcr x IndcrDisp Individual Ind x Indonesia Indonesia x CtryCodIndonesia



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Inductive Indu x

Inertia J

this keyword is used to express the physical effect that the mass of a body is interacting against its acceleration x

Information Info x RoofCnvtbInfo Inhibit Inhb x InhbShiftUp Inhibition Inhbn x Initial Ini x ActvWarnIni Initialization Inin x Inin Injection Inj x Injector Injr x Input Inp x TrsmNInp Insert Insert x KeyInsertSts1 Inside Insd x

Instance Inst

This keyword is used for the characterisation e.g. of a diagnosis, instance of the intake air temperature diagnosis x

Intake Intk x Integer Intgr x Integral Intgl x Intended Intd x VehBrkTqIntd Intensity Inten x BrkLiInten Intercooler Ico x Interdomain Interdom x InterdomCtrlr Interface If x Interior Intr x IntrLiMgr Intermediary Intery x Intermediate Inter x Inter Intermittent Intm x Internal Int x LidReFromHmiInt Interpolation Intrpn x Interpreter Itp For the networklayer of KWP2000 x Interrupt Intrpt x Interval Intl x WipgSpdIntlFromHmi Intervention Intv x EngTqIntvReq Invalid Invld x CtryCodInvld Inverse Ivs x MoveInIvsDir Invert Ivt x

Irreversible Irrv

this keyword is used to express that something can not return to a previous status, e.g. in Cruise Control deactivation it means in this case that cruise can not be activated again in the same driving cycle once a deactivation occured x

Italy Italy x Jam Jam x Japan Japan x CtryCodJapan Jerk Jerk x JerkMinReq Joule Jou Unit of measure for energy, work x Jou Jump Jmp x Kelvin Kelvin Unit of measure for temperature x Kelvin Key Key x KeyPad Keyless Keyls x AcsKeyls Kickdown Kd x Kilo Kilo x KiloGr Knee Knee knee of human body x Knob Knob x KnobRotyBndlsStep15 Knock Knk x Korea Korea x CtryCodKorea Lambda Lam Air/Fuel Ratio x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion


Lamp Lamp

this keyword is used do describe the component of a lamp, e.g in the display of the instrument panel x LampErrSts

Lane Lane x LaneProblty Large Lrg x Last Lst x Latch Ltch x TankFlapLtchRels Lateral Lat x ALatBas

Leak Leak

The powerstage for the piezo injectors has a special hardware (leakage compensation) to avoid discharging of capacities. x

Lean Lean x Learn Lrn x Learning Lrng x Leaving Lvng x HomeCmngAndHomeLvng Led Led Light Emitting Diode x LedActr Left Le x WhlFrntLe Length Len x Len3 Level Lvl x BodyLvlCtrl Leveling Lvlg x LvlgMan Lever Lvr x Lid Lid x LidReSt Light Li x PrkgLiDisp Lighter Lighter x Lighting Ltg x Limit Lim x ObjRlvcLowrLim Limitation Limn x Limited Limd x Limiter Limr x

Limp Limp example: Timeout camshaft sensor limp home x

Line Line x AlrmByLineCut Linear Lnr used for description of linear qualities x List List x ListOfObjData Liter L unit of measure for volume x Load Load Unit must be percent x AltLoadReqd Location Locn Position x Locn Lock Lock x DrvrDoorLockSt Locked Lockd x Lockd Locking Lockg x LockgCen Logical Logl x Long Long x Longitudinal Lgt longitudinal x Loop Loop x Loss Loss x Lost Lost x Loudness Ldn x Low Lo x BeamLoIndcn Lower Lowr x ObjRlvcLowrLim Lumbar Lum x LumPosnHei Machine Mac x MacElec Magnetic Mag x Magnitude Mgn x Main Mai x Maintenance Mntn x Malaysia Malaysia x CtryCodMalaysia Male Male x Manage Mng x Management Mngt x EgyMngt Manager Mgr x IntrLiMgr



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Manifold Mnfld x Manual Man x PanAdjMan Map Map x Mapping Mpg x SnsrMpgSimpleInp Marker Mkr x SideMkr

Market Mkt

This keyword is used to express market in the meaning of delivery areas, e.g. to characterize deviances in a component or function due to different customer market requirements. x

Mask Mask

this keyword is used to characterize a masking of a certain value to separate it from the non-masked one. x

Mass M x VehMEstimd Massage Massg x MassgSts Master Mst x LockgCenMst Mathematical Mat x Maximum Max x EngNSpMax Measure Meas x Measured Measd x VehBodyAVertMeasdBas Mechanic Mec x Mechanical Mecl x DrvrDoorKeyMecl Medium Med x HeiMed Mega Mega x MegaHz Memorise Memr x Memorized Memd x Memory Mem x MemPosnStore Meter Mtr x MtrPerSec Mexico Mexico x CtryCodMexico Micro Micro x MicroMtr Middle Mid x SnsrAAtReMid Mileage Milg x Milg Milli Milli x MilliMtr Minimum Min x EngSpdSpMin Minute Mins Unit of measure for time x Mins Mirror Mirr x MirrPosn Miscellaneous Misc x CmbEngMisc Misfire Misf x Misfiring Misfg x Missing Miss x Miss Mitigation Mtgtn x Mode Mod x HtlMod Model Mdl x Modulation Modln x Mole Mol x Mol Moment Mom x Momentum Momtm x RollMomtmDistbn Monitor Monr x BattMonr Monitoring Mon x TirePMon Month Mth x Mth Motion Mtn x VehMtnSt Motor Mot x SteerMotAgFrntStd Motorcycle Motorcycle x MotorcycleBicycle Mounted Mntd x Mounting Mntg x Move Move x MirrMoveSts Movement Movmt x AxisMovmt Moving Movg x Movg

Msr Msr engine drag torque control (also known as "Motorschleppmomentregelung") x

Mt Mt manual shifted transmission x Mt



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Multimedia Mmed x MmedTelmHmi Multiple Mpl x BtnMplSt8 Multiplexer Mux x N N rotational speed. x NGrdt1 Nano Nano x Natural Nat x Near Near x NearClsd Negation Negn x Negative Neg x

Network Net

describes all kind of networks in general, e. g. an electric network consisting of any type of consumsers and generators x

Neutral Neut x Neut New New x TirePMonRcndOfWhlNew Newton Nwt x NwtMtr Night Night x NightPanActv No No x NoWarn

Node Nod keyword for a junction or joining of lines or ways x

Noise Noise x Nominal Nom x

Nonlinear Nlnr

nonlinear. used for description of non linear characteristics (e.g. for an optional additional nonlinear correction) x

Nordic Nrdc x CtryCodNrdc

Normal Norm

this keyword is used to describe something as being in the most common mode, e.g. a state machine has a state normal when running properly without disturbance. Do not mix it with Basic for description of fulfilling a basic or minimum requirement. x

Norm

Not Not x WhlTqReqNotActv Notification Notif x Now Now in this moment x

Nox Nox

nox. This keyword is used to describe the nitrogen oxides (NOx) part of the emissions of a combustion engine. x

Nozzle Noz x NozHeatr

Number Nr this keyword is used to express a numbering in physical meaning x ChassisNr

Object Obj x PrioOfObj Observe Obs x

Observer Obsvr x CrsCtrlAndAccObsvrForVehSt

Obstacle Obstcl x DstFromObstclNear1 Obstruction Obstrcn x ObstrcnProblty Occupant Occpt x OccptPedSfty Of Of Preposition x DoorLockOfLidRe Off Off x OnOff Offroad Offroad x SuspModOffroad Offset Offs x YawRateOffsStdByEsc Ohm Ohm Unit of measure for electric resistance x Ohm Oil Oil x TrsmOilT Ok Ok x Ok

Old Old

in the calculation period n, the keyword OLD assigns a value from the period (n-1). x

On On x BrkLiOnReq1 Only Only x SftyFctOnly Open Open x OpenClsCmft



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Opened Opend x DtOpend Opener Opener x Operation Oper x Optical Optic x SeatBltRmnOpticWarnReq Optimum Optm x Optional Opt x Or Or x WhlAhdOrStandStill Orientation Orntn x Orntn

Oscillate Osc x

Oscillation Oscn This keyword is used to describe occurrences of pulsation or oscillation x

Out Out x LockOutPrevn Outlet Outl Outlet (e.g. camshaft) x Output Outp x OutpMplSt8 Outside Outd x OutdBri Over Over x Overflow Ovf x Overheated Ovrheatd x WhlBrkOvrheatd Overheating Ovrheatg x

Overload Ovld

The keyword is used for an electrical actuator, if the requested power exceeds the allowed longtime power limit. The overload must be possible for a certain time. x

Overridden Ovrdn x Override Ovrd x BrkPedlOvrd Oxidation Oxd x Pad Pad x KeyPad Panel Pan x NightPanActv Panic Panic x PanicAlrm Parameter Prm x CalPrm Parity Par x Park Park x GearParkReq Parking Prkg x PrkgLi

Partial Ptl

this keyword expresses the characterization of "only partly, not completely" x

Pascal Pa Unit of measure for pressure x HectoPa Pase Pase PassiveEntry x PasePanic Passed Passd x EveStsPassd Passenger Pass x PassDoorLock Passive Pas x SnsrAntithftPas Path Pah x Pattern Pat x IndcrPat Peak Peak x Pedal Pedl x BrkPedlPsd Pedestrian Ped x RoofPedProtn Pelvis Pelv pelvis of human body x

Pending Pnd

This keyword is used to build the "pending" fault used in the error management aggregate defined by the the ISO 15031-5.5 service $07. x

Per Per Preposition x MtrPerSec Percent Perc x Perc6 Period Perd x Permanent Prmnt x PrmntErr Permille Perml x Perml1 Personal Prsnl x Personalization Pen x ProfPenSts1 Phase Pha x Philippine Philippine x CtryCodPhilippine



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Physical Phy x Pi Pi x Pico Pico x Pid Pid pid. proportional integral differential x Pin Pin x Pinion Pinion x PinionSteerAg

Piston Pist

central component in a combustion engine. It serves to transform the gas pressure within the cylinder into a movement. The keyword is used e.g. to express the name for piston temperature x

Pitch Pitch x PitchRateBas Pitchover Pitchovr x PitchovrDetn Plant Pla x Plate Plate x PlateNr Plausible Plaus x

Pneumatic Pnm

used e.g. for description of pneumatic actuators (such as recirculation valve actuator or wastegate actuator) x

Pointer Ptr x Polling Polling x Pool Pool x SnsrPoolOccptPedSfty Port Port x Position Posn x MirrPosn Positioning Posng x Posng Positive Pos x Possible Psbl x NoFctPsbl Post Post x PostCrash Potentiometer Poti x Power Pwr x AlrmByPwrSplyCut Powertrain Pt x

Pre Pre used to express any kind of pre-processing like e.g. for pre-injection x

PreCrash

Precharge Prec x Predicted Pred x VehCourseCrvtPred Preliminary Prel x Premature Prem x

Preparation Prepn

this characteristic is used to express a general status of preperation, e.g. processing of certain tasks before an activation of a certain component or functionality x

Prepare Prep x PrepIdn Presence Pres x PresStOfDrvr Present Prsnt x NotPrsnt Pressed Psd x BrkPedlPsd Pressure P x Prevention Prevn x GearShiftPrevn Previous Prev x Primary Prim x Priority Prio x PrioOfObj Probability Problty x LaneProblty Process Proc x CryptoProcStrtReq1 Profile Prof x DrvrProf Program Prog x SeatMassgProg1 Programmed Progd x FobNotProgd Programming Progm x Progress Progs x ShiftInProgs Project Prj x Property Ppty x DynPpty Proportional Prop x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion


Propulsive Prp

opposite of drag resistance. Notion of positive forces generated by a system. Example: for a car, we can list internal combustion engine + starter/generator + electrical engine x

Protected Protd x Protection Protn x ChdProtnReRi Ptc Ptc Power Train Controller x Puddle Puddle x PuddleLi Pull Pull x DrvrDoorPullAid

Pulse Pls a pulse is a simple electrical signal with a defined shape x PlsGenrMod

Pump Pmp x TrsmOilPmpLoadAct Purge Purg x

Push Push

push (start), towing, power on driving, press. keyword for push or active towing (e.g. if a vehicle has to be started by towing, a button is pressed, if there is positive torque inside powertrain) x

Put Put x Pwm Pwm pulse width modulation x

Pyrometer Pyro

this keyword is used to express a relationship to a pyrometer which is a contactless instrument to measure high temperatures x

Quality Qly This keyword is used to express the word 'quality' x DataQly

Quantity Qnty x Quotient Quo x Radian Rad As unit of measure for angles x RadPerSec

Radiator Radr

a radiator is a component, that sens out heat. It can be found e.g. in the cooling circiut of a car. x

Radio Radio x RadioSts Radius Rd x WhlRdTolrCoeff

Rail Rail

common rail. This keyword shall be used to express the common rail, which is a core component in some fuel system configurations (esp. diesel). It is a high pressure fuel container mostly in form of a tube and located close to the engine. x

Rain Rain x DispRainSnsrActv Ram Ram Random Access Memory x Ramp Ramp x Ramp7 Random Rnd x Range Rng x RollRateRngExtd

Rate Rate this keyword is used to express a rate in physical meaning x PitchRateBas

Ratio Rat

RATIO is used to describe a value gained from a proportion of other values. The unit of RATIO must be [-] (no unit). x AccrPedlRat

Raw Raw Unprocessed sensor data. x WhlVAgrRaw

Reaction Reactn x SteerWhlReactnTqModReqd

Reactivation Reacvn x Read Read x Reading Reading x Ready Rdy readiness identification x BrkRdyReq Real Real Real part x Realized Relzd x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Rear Re x WhlReLe Rebound Rbd x DamprRateActRbd Recall Recall x Recall Receive Rx x Receiver Rxr x RxrOn Reception Rxn x Reciprocal Recpr x MtrRecpr Recirculation Recirc x Recognized Rcnd x TirePMonRcndOfWhlNew Record Rec x Reduction Redn x Reference Ref x YawRateRefValByEsc Refuel Refu x Regeneration Rgn x Region Regn x CtryCodGulfRegn

Regular Rgl

this keyword is used to describe e.g. a process as being in a normal status in sense of correctness. It is behaving like wanted (it behaves like wanted to treat a disturbance), it is not out of order. x

Reinforce Reinf x Rejected Rejctd x CalRejctd Relative Rel x BodyRollAgRelEstimd Relay Rly x Release Rels x TankFlapLtchRels Released Reld x Reld Relevance Rlvc x ObjRlvc Relevant Rlv x ListOfObjDataRlvForAcc Reminder Rmn x SeatBltRmnWarnCtrl Remote Rem x KeyRemMgr Repeat Rep x Repetition Repn x Request Req x SpdSpReq Requested Reqd x AltLoadReqd Required Rqrd x Reserve Resv x TqResvReq Reserved Resd x Reset Rst x TirePMonAckRst Residual Resi x Resistance R Unit must be Ohm x Resolution Resl x Response Resp x Rest Rest x CtryCodRestOfWorld Restart Rstrt x Restore Restore x RestorePosn Restraint Restrnt x Result Res x AArbnRes Resume Resu x Resu Retard Rtd x Retarder Rtdr x

Retractor Rtrctr Part of supplement restraint system to protect occupant in case of crash x ActrBucRtrctrAtDrvr

Reverse Rvs x WhlRvs

Reversible Rvsb

This keyword is used to express that something can return to a previous status, e.g. in Cruise Control deactivation: It means in this case that cruise can be activated again in the same driving cycle once a deactivation occured. x

Reversing Rvsg x Rvsg Revolution Rev As unit of measure x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Rho Rho density x Rich Rich x Ricirculation Rcrltn x Ride Ride x RideHeiLvlEstimdFrnt Right Ri right x WhlReRi Rise Rise x Rising Risng x Rke Rke Remote Keyless Entry x

Road Road

this keyword is used to express the conditions a street can apply to the vehicle x RoadWhlAg

Roll Roll x RollRateBas

Rollbar Rollbar (Active) safety roll bar to protect passengers x

Roller Rollr x Rolling Rollg x RollgFwd Rollover Rollovr Info from airbag control unit x RollovrDetn Rom Rom read only memory x Ron Ron research octane number x Roof Roof x RoofPosn Rotary Roty x KnobRotyBndlsStep15

Rotation Rot This keyword is used to express circular motions. x

Rotational Rotl x WhlDirRotlStd Roughness Roughns x Row Row x BltLockStAtRowThrdLe Rpm Rpm As unit of measure for frequency x RpmPerSec Rsa Rsa Republic of South Africa x CtryCodRsa Rsc Rsc Roll Stability Control x YawCtrlOvrdnByRsc Run Run x Running Runng x LiDaytiRunng Runtime Rt x Safe Safe x Safe Safety Sfty x OccptPedSfty Sale Sale x Sample Sample x Saturation Satn x BrkActrSatn Save Save x Saved Saved x Scale Sca x Scan Scan x Scanner Scanr x SnsrScanrIntr

Scavenging Scav

The process of pushing fresh gas from the inlet into the exhaust by having big overlap of opened inlet and outlet valve, especially at charged engines is called scavening. x

Scheduler Sdl x Seat Seat x SeatBltRmn Seating Seatg x

Second Sec As time unit (mean/env/device), used as "2nd" it is a condition/qualifier x x

MtrPerSec, BltLockAtRowSecRi

Sector Sector x ObstclReSector0 Security Secu x SwtTrSecu Seed Seed x Segment Seg x Segmented Segd x Selected Seld x UnlckSeld



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion


Selection Seln

Seln is used to assign e.g. the selection of a certain fuctionality (one out of several strategies) or component (one of several gears, sensors,..) as well as in simulation to select a single entry of an Array by putting Seln at the end of the name x AccObjTarSeln

Self Self x SelfTest Send Snd x Sensing Sen x RainSen Sensitivity Snvty x RainSenSnvty1 Sensor Snsr x DispRainSnsrActv Sequence Seq x BlinkSeqSts1 Sequential Seql x Serial Serl x Serie Ser x

Service Srv

a service is a processing routine within a certain functionality. This keyword is used to nominate such services. x

WiprPosnReqdForSrv

Servo Servo x Set Set x SetEveSts Setpoint Sp x EngSpdSp Severity Sev x PedCrashSevCalcd

Shaft Shaft

a shaft is a rotating rod, carrying out a certain task or transmitting a force in a powertrain. Example: outbox gearbox shaft. x

Shield Shd x Shift Shift x ShiftInProgs Short Sho short trip x Shortening Shong x Shutter Shttr x

Side Side This keyword is intended for common consideration of inlet and exhaust side. x SideMkr

Siemens S Unit of measure for conductance x Signal Sig x Sill Sill x Simple Simple x BtnSimple Simulated Simd x Simulation Simn x Single Sng x WipgStrikeSngReqByUsr Sinus Sin x Slave Slave x Slide Sld x PosnSld Sliding Sldg x RoofSldgSt Slip Slip x BypSlipCtrlReqByRsc Slope Slop x Slow Slow x

Smart Smt

more and more electronic components take over tasks that had been done before by a central processing unit. Such components are seen as "intelligent" or "smart", whereas the second expression is the one used more generally. x

Smoothing Smotng x Soft Soft x SoftWarn Soi Soi start of injection. Unit must be angle x Solenoid Soln x Soon Soon x Sound Sound x SoundOff Sounder Soundr x SnsrSoundrBattBacked



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Source Src x LockTrigSrc1

Spare Spare x TirePMonCalStsAtWhlSpare

Special Spcl x SpclMod

Specific Spc

for specific environmental data (stored individualy with particular failures of one project). x AccYawRateSpc

Speed Spd x Spi Spi serial peripheral interface x

Spontaneous Spo

this Keyword characterizes a sudden, unexpected occurrence. E.g. a not pre-arranged catalyst regeneration phase. x

Sport Spt

Related to the (short- and long term) detection of driver type either an economic/comfort oriented or a sportive/ power requesting driver can be distinguished. x SuspModSpt

Spring Sprg x SprgFEstimd

Square Sq

the Keyword is used to describe the relationship of a Functional Data to the arithmetic procedure of multiplication of a value with itself. x

Squared Sqd x MtrSqd Ssm Ssm Stand Still Manager x SsmReqStsToEsc Stability Staby x YawStabyCtrlActv Stabilization Stabn x Stabilizer Stabr x StabrSts Stable Stab x Stage Stg x Stall Stall x Stalling Stallg x Stamp Stamp x DateTiStamp1 Stand Stand x StandStill

Standard Std

Signals that are computed by a model, offset compensated and/or filtered, which can be combination of more than one base signals. x

WhlAAgrStd

Standardization Stdn x Standby Stb x Standing Standg x Standg Start Strt x EngStrtRem Started Strtd x CalStrtd Starter Strtr x Starting Strtg x State St x DrvrDoorLockSt Static Stat x

Stationary Staty

This keyword is used to describe a situation, where a movable part is at rest or a certain condition does not change x

Statistic Stc x Status Sts x DamprSts

Steering Steer This keyword is used to express the steering of a car. x SteerWhlAgBas

Step Step x KnobRotyBndlsStep15 Steradian Srad As a unit of measure for solid angle x Srad

Stiffness Stfn

stiffness is the grade of hardness of a material, e.g. in a damper: it is composed of a spring (stiffness part: force proportional to displacement) and a fluid friction (viscous part: force proportional to speed) x StabrStfnAct



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Still Still x StandStill

Stimulation Sti The stimulation descibes the inputs for testing of functions. x

Stoichiometric Stoi x Stop Stop x StopInIvsDir Storage Storg x SeatStorgPosn1 Store Store x SeatPosnStore Strategy Stgy x Stratified Strat e. g. used in stratified injection x Strike Strike x WipgStrikeSngReqByUsr Stroke Stk x Structure Struct x

Stuck Stuck

the keyword STUCK is used to express e.g. a "stuck reading" coolant temperature sensor. This is an official expression of the CARB (Californian Air Resources Board) and is used in term of OBD II requirements. x

Substitute Sub x Subtractive Subt x Subtype Subtyp x Suction Suctn x Sulphur Su x Sum Sum x SteerTqSum Super Sup example: super charger x Superior Supr x Superposition Suppsn x SteerAgSuppsnAct Supplementary Sppl x Supply Sply x AlrmByPwrSplyCut Suppress Supp x

Surge Surge

surging, surge line. this keyword is used to describe the appearance of surging effects in an (air-)stream, e.g. at the surge line of a turbocharger (which is a characteristic parameter) x

Surroundings Surrndgs x SurrndgsSnsr Suspension Susp x SuspActvFullSts Suspicion Suspc x Swirl Swirl x Switch Swt x HndbrkSwt Switchable Swil x SprgSwilSts Switzerland Switzerland x CtryCodSwitzerland Symptom Sym x Synchronization Syncn x Synchronize Sync x Synchronized Syncd x System Sys x SysPedProtnActvn Table Tbl x Taiwan Taiwan x CtryCodTaiwan Tank Tank x TankFlap Target Tar x GearTar

Tau Tau Time constant of a control sys. (-> P, I, D!) x

Telegram Telgrm x RkeTelgrmRxn Telematics Telm x MmedTelmHmi Telltale Telltl x TelltlDefrstSts Temperature T x AmbAirT1 Temporary Tmp x TmpErr Tensioner Tensnr x ActrBltTensnrAtDrvr Term Term x Terminal Terminal x TerminalClmpCtrl Test Test x SelfTest



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Thailand Thailand x CtryCodThailand Theoretical Theo x Thermal Therm x Thermo Thermo x Thermostat Th x Third Thrd x SeatFixaStsOfRowThrdLe Thorax Thorax thorax of human body x Threshold Thd x Throttle Thr x Tightness Tgtnss x Tilt Tilt x HdPosnTilt Time Ti Time, duration x DateTi

Timer Tmr

this keyword is used to express a timer. A timer is counter for a defined time span. x

Tinting Tintg Action of changing the color of an object x MirrTintg Tip Tip x Tire Tire x TirePMon Titanium Tit x

Tn Tn

time constant for discret control structures. This keyword is used in control engineering context as time constant for discret control structures x

To To toward something,….. x SsmReqStsToEsc Toggle Tog x TogSt Tolerance Tolr x WhlRdTolrCoeff Tooth Tooth x Top Top x TopPosnIncl Torque Tq x Torsion Tors x Total Tot x Touched Touchd x Touchd Tout Tout time out x Traction Trac x TracCtrlActv

Trailer Trlr

a wheeled but not motorized vehicle which can be pulled by a motorized vehicle x TrlrSts

Transfer Trf x DftlTqActAtDftlForTqTrf Transient Tra x Transition Tran x Transmission Trsm In a mechanical context x TrsmNrTyp Transmit Tx In a communication protocol context x

Transversal Trv transversal in opposite to longitudinal. e.g. used for acceleration x

Trap Trap x

Trapping Trapg

In case of scavening the total fresh gas flowing into the cylinder is bigger than the mass air flow staying in the cylinder. The ratio of the mass air flow in the cylinder to the total mass air flow is called trapping efficency x

Travel Trvl x SprgTrvl Travelled Trvld x DstTrvld Treatment Treat x Trigger Trig x TrigSrc Trip Trip x Trouble Tro x Truck Truck x TruckBusVan Trunk Tr x TrUnlck

Tube Tube the keyword TUBE expresses any kind of a pipe, for instance the exhaust . x

Tumble Tumb x



R4.0 Rev 2


ean-

Env

ironm

ent-

Dev

ice

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Tuning Tun x DamprCtrlTunReq

Turbine Trb

To describe a turbine (turbine wheel) in general, e.g. in a hydraulic torque converter or in a turbocharger x

Turbulence Trbl Flow regime characterized by chaotic stochastic property changes x

Turn Turn x IndcrTurnSeq1 Twilight Twli x Twli1 Type Typ x TrsmNrTyp

Uds Uds

Unified Diagnostic Services. UDS (Unified Diagnostic Services) is a new world-wide standard for Diagnostics according to ISO14229-1 x

Undefined Undefd x Undefd Unfavourable Unfav x Unit Unit x Unknown Ukwn x Ukwn Unlock Unlck x LockUnlckReq1 Unlocked Unlckd x RoofUnlckd Up Up x InhbShiftUp Update Upd x Upper Uppr x ActrADbndUppr Upstream Us x Upward Upw x AUpwAtCen Usa Usa United States of America x CtryCodUsa Use Use x User Usr x UsrReqForWipg1 Vacuum Vac x Valid Vld x Vld Validate Vldt x Value Val x BrkPedlVal Valve Vlv x Van Van x TruckBusVan Vanity Vanity x VanityLiFrntLe Vapor Vap x Variance Vari x Variant Vrnt x Vcc Vcc supply voltage x

Vcv Vcv high pressure pump volume control valve x

Vector Vect x Vehicle Veh x Velocity V x WhlVAgrStd Vent Vent x Ventilation Ventn x Version Vers x Vertical Vert x WhlAVertEstimd Vietnam Vietnam x CtryCodVietnam

Vin Vin

vehicle identification number. this keyword is used to decribe the vehicle identification number. This is certain code which is unique for every vehicle and is used for its identification. x

Virtual Virt x

Viscosity Vcos

Viscosity describes the thickness of a fluid, e.g. in a damper: it is composed of a spring (stiffness part: force proportional to displacement) and a fluid friction (viscous part: force proportional to speed) x

Visibility Visy x Visual Vis x AlrmVis



R4.0 Rev 2


Keyword Keyword

Abbreviation Definition English Mea

n-E

nviro

nmen

t-D

evic

e

Act

ion-

Phy

sica

lTyp

e

Con

ditio

n-Q

ualif

ier

Inde

x

Pre

posi

tion

Use Case (short names) Vlc Vlc Vehicle Logitudinal Control x VlcAAct Volt Volt As unit of measure for voltage x Volt Voltage U x BattU1 Volume Vol x BmpPedProtnVolAdj Volumetric Volmc x Wait Wait x Warm Wrm x Warning Warn x LiOnWarn Washer Wshr x WiprWshr Washing Wshng x WshngReq1 Water Wtr x Watt Watt As unit of measure for power x Watt Way Way x Weather Wthr x Weight Wght x Wheel Whl x WhlFrntLe Wheels Whls x

Wide Wide

keyword is used to specify gear box type, which is distinguished via variant coding (wide ratio: long transmission ratio for lower rpm. closed ratio: sports transmission ratio) x

Width Width x Width Window Win x WinCtrl Windscreen Wind x

Winter Wntr x WiprPosnReqdForPosnWntr

Wiper Wipr x WiprWshr Wiping Wipg x WipgReq1 Wireless Wirels Used for Wireless connection x ImobnWirelsReq1 Wish Wish x

Wished Wishd x RoadWhlAgEstimdFrntWishdByDrvr

With With preposition x ALgtStdWithPitchCmp Within Within preposition x Without Wo preposition x Word Word x Work W Energy x World World x CtryCodRestOfWorld Write Wr x

Wrong Wrg

is used to express a mismatch which does not have to be treated by error management diagnosis x

Xposition Xpos X position x CrashXpos Yaw Yaw x YawRateBas Year Yr x Yr Yposition Ypos Y position x CrashYpos

SW-C and System Modeling Guideread.pudn.com/downloads411/doc/project/1747885/Auxiliary...

Documents

Transcript of SW-C and System Modeling Guideread.pudn.com/downloads411/doc/project/1747885/Auxiliary...