Predefined Names in AUTOSAR - Enabling Innovation

Predefined Names in AUTOSARAUTOSAR FO R20-11

Document Title Predefined Names in AUTOSARDocument Owner AUTOSAR

Document Responsibility AUTOSAR

Document Identification No 600

Document Status published

Part of AUTOSAR Standard Foundation

Part of Standard Release R20-11

Document Change HistoryDate Release Changed by Description

2020-11-30 R20-11AUTOSARReleaseManagement

• Added abbreviations for DEXT,SECXT, ATS and ATR• Modified abbreviations for

MetaModel and XmlSchema

2019-11-28 R19-11AUTOSARReleaseManagement

• Included abbreviations for ARTI• Removed references to

TR_InteroperabilityOfAutosarTools• Changed Document Status from

Final to published

2018-10-31 4.4.0AUTOSARReleaseManagement

• Removed reference toTR_SafetyConceptStatusReport


• Include abbreviations for NameSpaces• Include Mentioned Class Tables


• Include abbreviations for PDEP


• Include abbreviations for AcceptanceTests


• Complete list of Module Abbreviationfor each AUTOSAR document• Include additional keywords


• editorial changes

1 of 21 Document ID 600: AUTOSAR_TR_PredefinedNames



• harmonization of keywords with Listof Basic Software Modules

2013-03-15 4.1.1 AUTOSARAdministration

• editorial changes• harmonization of keywords with other

documents

2011-12-22 4.0.3 AUTOSARAdministration Initial release



Disclaimer

This work (specification and/or software implementation) and the material contained init, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and thecompanies that have contributed to it shall not be liable for any use of the work.

The material contained in this work is protected by copyright and other types of intel-lectual property rights. The commercial exploitation of the material contained in thiswork requires a license to such intellectual property rights.

This work may be utilized or reproduced without any modification, in any form or byany means, for informational purposes only. For any other purpose, no part of the workmay be utilized or reproduced, in any form or by any means, without permission inwriting from the publisher.

The work has been developed for automotive applications only. It has neither beendeveloped, nor tested for non-automotive applications.

The word AUTOSAR and the AUTOSAR logo are registered trademarks.



Table of Contents

1 Introduction 6

2 [VirtualModules] Virtual Modules 7

3 [InformationCategories] AUTOSAR Information Categories 8

4 [DocumentAbbreviations] AUTOSAR Document Abbreviations for Trace Pre-fixes 10

5 [NamespaceAbbreviations] AUTOSAR Name Spaces 17

A Mentioned Class Tables 19



References

[1] List of Basic Software ModulesAUTOSAR_TR_BSWModuleList

[2] XML Specification of Application InterfacesAUTOSAR_MOD_AISpecification

[3] Specification of ECU Configuration Parameters (XML)AUTOSAR_MOD_ECUConfigurationParameters

[4] Standardization TemplateAUTOSAR_TPS_StandardizationTemplate

[5] Generic Structure TemplateAUTOSAR_TPS_GenericStructureTemplate



1 Introduction

This document describes various predefined names used in AUTOSAR models anddocuments. The main purpose of this document is to serve as an entry point to findnames which are predefined in AUTOSAR beyond the following documents:

• [1] Basic software module list

• [2] Application interfaces

• [3] Ecu configuration parameters

Note that the definitions in this document are also available as AUTOSAR XML model.In this model, the predefined names are represented as Keywords according to [4].They are represented as tables with the following colums:

shortName: a unique name for the abbreviation, taken from shortName of Keyword

abbrName: This is the reserved name itself according to [4]. Note that the namemight be rendered with line breaks in order to fit into the table cell. The reservedname in this column never has a white space, so the line breaks shall be ignored.

longName: This is the longName for the reserved name (see [5] for details aboutlongName).

Classification, Description : This is the list of keyword classifications as refer-enced e.g. by [TPS_STDT_00042] respectively [TPS_GST_0017]. In addition tothis, desc of the keyword is shown as well in order to understand the purpose ofthe reserved name.



2 [VirtualModules] Virtual Modules

This keyword set defines virtual modules which take the role of module designators innaming conventions but do not exist as e.g. C-implementations.

[TR_PDN_00001] Definition of Virtual Modules dThis keyword set contains two key-word classifications:

• ModuleDesignator: The abbrName represents a valid module designator de-fined by AUTOSAR (see [TPS_GST_00017] in [5] ).

• AUTOSAR-Document: The shortName represents a module name for the im-plementation of a specification provided by AUTOSAR.

c()

shortName abbrName longName Classification, Description

Arti Arti AUTOSAR Run-Time Interface ModuleDesignator

Arti is a pseudo module which definesparameters holding run-time informationof the application for debugging andtracing.

AISpecification AISpecification XML Specification ofApplication Interfaces

AUTOSAR-Document, ModuleDesignator

This represents the AppplicationInterfaces.

EcuC EcuC Ecu Configuration ModuleDesignator

EcuC is a pseudo module which definesparameters applicable to all other BSWmodules.

GeneralBlueprints GenBlpr General Blueprints ModuleDesignator

Collection of blueprints for AUTOSARM1 models.

GeneralDefinitions GenDef General Definitions ModuleDesignator

This represents general elements thatcan be applied for both, basic (BSW)and application software (ASW), but forwhich no explicit AUTOSAR Documentis maintained. Example for objects inthis virtual module are elements such aslife cycle definitions, role definitions etc.

V2X V2X Vehicle-2-X ModuleDesignator

V2X is used as a cluster abbreviation byall cross module types used by theVehicle-2-X communication modules.

Table 2.1: Virtual Modules



3 [InformationCategories] AUTOSAR InformationCategories

This keyword set denotes abbreviations used e.g. in filenames respectively in tracetags.

[TR_PDN_00002] Definition of AUTOSAR Information Categories dThis keywordset contains the following keyword classifications:

• DocumentCategory: The keyword (abbrName) represents a valid category of adocument provided by AUTOSAR (see [TPS_STDT_00050] in [4] ).

• TraceCategory: The keyword (abbrName) represents a valid category of a trace-able text within a document provided by AUTOSAR (see [TPS_STDT_00042] in[4] ).

• InternalDocumentCategory: The keyword ( abbrName) represents a valid cat-egory of a document internal to AUTOSAR which is not published but still followsthe conventions.

c()


ASWS ASWS Abstract SWS SoftwareSpecification

DocumentCategory, TraceCategory

General Specification of AUTOSARBasic Software Modules

ATR ATR Acceptance Test Requirement DocumentCategory, TraceCategory

Specification of requirements foracceptance tests

ATS ATS Acceptance Test Specification DocumentCategory, TraceCategory

Test specification and scripts for theexecution of acceptance tests

CONC CONC Concept Document DocumentCategory, TraceCategory

Concept describing planned changesfor the next minor or major release

CTCF CTCF Configuration Settings DocumentCategory, TraceCategory

Configuration settings for the executionof conformance Tests

CTSP CTSP Conformance Test Specification DocumentCategory, TraceCategory

Test specification and scripts for theexecution of conformance tests

EXP EXP Explanation DocumentCategory, TraceCategory

Explanatory material discussiongcontents already shown in otherdocuments

MMOD MetaModel MetaModel DocumentCategory, TraceCategory

Modeled contents (a model orgenerated from a model) on meta level2 (Meta-Model)

5



4shortName abbrName longName Classification, Description

MOD MOD Model DocumentCategory, TraceCategory

Modeled contents (a model orgenerated from a model) on meta level1 (Model)

PD PD Process Description DocumentCategory, TraceCategory

Description of process applied withinAUTOSAR standardization activities

PDEP PDEP Profile of Data Exchange Point DocumentCategory, TraceCategory

Contains models that tailor AUTOSARspecifications and templates for specificdata exchange points

PRS PRS Protocol Specification DocumentCategory, TraceCategory

Specification of Protocols standardizedby AUTOSAR

RS RS Requirement Specification DocumentCategory, TraceCategory

Specification of requirements other thanfor software specifications

SRC SRC Source DocumentCategory, TraceCategory

Source code artifacts

SRS SRS Software RequirementSpecification

DocumentCategory, TraceCategory

Specification of requirements forsoftware specifications

SWS SWS Software Specification DocumentCategory, TraceCategory

Specification of AUTOSAR Software

TMPL TMPL Template InternalDocumentCategory

Predefined documentation templates

TPS TPS Template Specification DocumentCategory, TraceCategory

Specification of AUTOSAR Templates,containing Meta model information,constraints etc.

TR TR Technical Report DocumentCategory, TraceCategory

A general technical report describingarbitrary AUTOSAR related topics

UC UC Use Case Specification TraceCategory

Specification of use cases from whichrequirements are derived. Note thatthere are documents which maintain theuse cases in their requirement spec. Sothis documentCategory may exist, evenif it is not an own artifact.

ZAUX ZAUX Auxilary material InternalDocumentCategory

Auxillary files used internally for thecreation of the standard. May bemerged with ZSUPP.

ZGEN ZGEN Generated intermediatematerial

InternalDocumentCategory

Generated intermediate products whichare maintained in the SCM system ofAUTOSAR and used internally for thecreation of the standard

5




ZSUPP ZSUPP Supplemental material InternalDocumentCategory

Supplementary material used internallyfor the creation of the standard

Table 3.1: AUTOSAR Information Categories

4 [DocumentAbbreviations] AUTOSAR DocumentAbbreviations for Trace Prefixes

These keywords represent the abbreviations to indicate documents e.g. in the require-ments tags

[TR_PDN_00003] Document Abbreviations for Trace Prefixes dThis keyword setcontains the keyword classifications:

• DocumentAbbreviation: The abbrName represents a valid document abbrevia-tion in tracing tags (see [TPS_STDT_00042] in [5] ).

Note that there are cases where one document uses more than one abbreviation (e.g.[SWMC, SWNR], [MCM, MCG, MCA]). There are also cases where one abbreviationis used across multiple documents (e.g. [BSW]).c()


ARTI ARTI AUTOSAR Run-Time Interface DocumentAbbreviation

This document explains Interfaces forthe "AUTOSAR Run-Time Interface"

AIBodyAndComfort AIBC Application Interfaces "Bodyand Comfort"

DocumentAbbreviation

This document explains ApplicationInterfaces for "Body and Comfort".

AIChassis AICS Application Interfaces "Chassis" DocumentAbbreviation

This document explains ApplicationInterfaces for "Chassis".

AIDesignPatternCatalogue

AIDPC Application Interface DesignPattern Catalogue


This document contains ApplicationInterface Design Pattern Catalogue.

AIHMIMultimediaAndTelematics

AIHMI Application Interfaces "HMIMultimedia and Telematics"


This document explains ApplicationInterfaces for "HMI Multimedia AndTelematics".

AIOccupantAndPedestrianSafety

AIOPS Application Interfaces"Occupant and pedestrianSafety"


This document explains ApplicationInterfaces for "Application InterfaceOccupant and pedestrian Safety".

5




AIPowertrain AIPT Application Interfaces"Powertrain"


This document document explainsApplication Interfaces for "Powertrain".

AISpecificationExamples

AISE XML Examples of ApplicationInterfaces


This represents XML Examples ofAppplication Interfaces.

AIUserGuide AIUG Application Interfaces UserGuide


This document aims at explaining allrelevant details about the AI Table.

ApplicationLevelErrorHandling

ALEH Application Level Error Handling DocumentAbbreviation

This document explains the ApplicationLevel Error Handling.

AdaptiveNetworkManagement

ANM Adaptive Network Management DocumentAbbreviation

Adaptive Platform - to be filled correclty

AdaptivePlatformDemonstrator

APD Adaptive Platform Demonstrator DocumentAbbreviation

This specifies the Adaptive PlatformDemonstrator

AdaptivePlatformDemonstratorTestdata

APDT Adaptive Platform DemonstratorTestdata


This specifies the Adaptive PlatformDemonstrator Testdata

AutosarModelConstraints

ArModC Autosar Model Constraints DocumentAbbreviation

This document explains Autosar ModelConstraints.

ARXMLSerializationRules

ASR ARXML Serialization Rules DocumentAbbreviation

This document explains how to serializeAUTOSAR models into ARXML filesand vice versa.

ATBM ATBM Interaction with BehavioralModels


This document describes interactionwith behavioral models.

BSWAndRTEFeatures BRF AUTOSAR BSW and RTEFeatures


This document specifies the features ofthe BSW Architecture and the RTE.

BSW BSW Basic Software DocumentAbbreviation

This abbreviation represents thesuperset of all BSW softwarerequirement specifications. This meansthat this abbreviation is used throughoutall Basic Software Specifications.

BSWModuleDescriptionTemplate

BSWMDT Basic Software ModuleDescription Template


This document specifies how todescribe a Basic Software

BSWModuleList BSWML Basic Software Module List DocumentAbbreviation

This document lists the BSW modules.

BSWUMLModelModelingGuide

BSWUMG BSW UML Model ModelingGuide


This guideline describes the BSW UMLModel modeling.

5




BSWUML BSWUML Basic Software UML model DocumentAbbreviation

This abbreviation represents the BSWUML model. This means that thisabbreviation is used throughout allelements maintained in the BSW UMLmodel.

BWCStatement BWC BWC Statement DocumentAbbreviation

This document describes the backwardcompatibility statement.

CDDDesignAndIntegrationGuideline

CDDG CDD Design And IntegrationGuideline


This guideline describes the Design andthe Integration of CDD.

CommunicationCan COMCAN Communication on Can DocumentAbbreviation

Relevant for communication on CAN.

CommunicationFlexray COMFR Communication on Flexray DocumentAbbreviation

Relevant for communication on Flexray.

CommunicationLin COMLIN Communication on Lin DocumentAbbreviation

Relevant for communication on LIN.

CommunicationManagement

COMMGMT Communication Management DocumentAbbreviation

Relevant for communicationmanagement.

CommunicationViaBus COMVB Communication via a bus DocumentAbbreviation

Relevant for communication via a bus.DiagnosticExtractTemplate

DEXT Diagnostic Extract Template DocumentAbbreviation

This document specifies diagnosticexchange data.

Diagnostic DIAG Requirements on Diagnostic DocumentAbbreviation

The goal of AUTOSAR WP Diagnosticsand this document is to define to whatextent elements of the diagnostic basicsoftware have to be configurable andwhat preliminaries they shall complywith to meet the tailoring requirements.The handling of the legislated OBD andenhanced Diagnostics shall also beachieved.

AdaptiveDiagnostics DM Adaptive Diagnostics DocumentAbbreviation


ECUConfiguration ECUC Specification of ECUConfiguration


This document specifies the technicaldetails of the ECU configuration

ECUConfigurationParameters

ECUCP ECU Configuration Parameters DocumentAbbreviation

This document describes ECUConfiguration Parameters.

EcuModeManagement ECUMGMT ECU Mode Management DocumentAbbreviation

Relevant for ECU mode management.

ECUResourceTemplate ECUR Specification of ECU ResourceTemplate


This specifies how to describeResources of an ECU

5




ErrorDescription ED Error Description DocumentAbbreviation

This document explains the ErrorDescription.

ExecutionManagement EM Execution Management DocumentAbbreviation


ErrataSheet ERSH Errata Sheet DocumentAbbreviation

This document explains the ErrataSheet.

FrancaIntegration FCAINT Franca Integration DocumentAbbreviation

This document describes the FrancaIntegration.

Features Feature Feature SpecificationAcceptance Tests


Feature Specification of the acceptancetests.

FeatureModelExchangeFormat

FMDT Specification of Feature ModelExchange Format


This specifies how to describe theFeature Model Exchange Format.

FreeRunningTimer FRT Free Running Timer DocumentAbbreviation

This document describes the FreeRunning Timer.

Glossary GLOS Glossary DocumentAbbreviation

This document lists all Glossary items.

GenericStructureTemplate

GST Generic Structure Template DocumentAbbreviation

This specifies common aspectsapplicable to all templates.

Gateway GTW Gateway DocumentAbbreviation

This document explains the Gateway.

HealthManagement HM Health Management DocumentAbbreviation


InteroperabilityOfAutosarTools

IOAT Interoperability of AUTOSARTools


This document describes variousaspects of interoperability of AUTOSARtools.

InteroperabilityOfAutosarToolsSupplement

IOATS Interoperability of AUTOSARTools Supplement


This document contains baselineprofiles of data exchange points andexamples.

IOHWAbstraction IOHWAB IO Hardware Abstraction DocumentAbbreviation

This document describes the IOHardware Abstraction.

InterruptHandlingExplanation

IRH Interrupt Handling Explanation DocumentAbbreviation

This document explains the InterruptHandling.

SRSLibraries LIBS Requirements on Libraries DocumentAbbreviation

This document specifies requirementson the AUTOSAR Libraries.

AdaptiveLogAndTrace LOG Adaptive Log and Trace DocumentAbbreviation


5




LayeredSoftwareArchitecture

LSA Layered Software Architecture DocumentAbbreviation

This document describes the LayeredSoftware Architecture.

MainRequirements Main AUTOSAR Main Requirements DocumentAbbreviation

This document specifies the AUTOSARmain requirements.

AIMeasurementCalibrationDiagnostics

MCAI Unique Names forDocumentation, Measurementand Calibration: Modeling andNaming Aspects includingAutomatic Generation


This document discusses how toautomatically generate display namesfor measurement, calibration anddiagnostic tools (MCD).

AIMeasurementCalibrationDiagnostics_Assumptions

MCA Assumptions in Unique Namesfor Documentation,Measurement and Calibration:Modeling and Naming Aspectsincluding Automatic Generation


This keyword reflects the assumptionshow to automatically generate displaynames for measurement, calibrationand diagnostic tools (MCD). Thekeyword is used for document internaltracing

AIMeasurementCalibrationDiagnostics_GenerationRules

MCG Generation Rules in UniqueNames for Documentation,Measurement and Calibration:Modeling and Naming Aspectsincluding Automatic Generation


This keyword reflects the generationrules how to automatically generatedisplay names for measurement,calibration and diagnostic tools (MCD).The keyword is used for documentinternal tracing.

AIMeasurementCalibrationDiagnostics_ModelingRules

MCM Modeling Rules in UniqueNames for Documentation,Measurement and Calibration:Modeling and Naming Aspectsincluding Automatic Generation


This keyword reflects the modeling rulesof how to automatically generate displaynames for measurement, calibrationand diagnostic tools (MCD). Thekeyword is used for document internaltracing.

AIMeasurementCalibrationDiagnostics_Requirements

MCR Requirements in Unique Namesfor Documentation,Measurement and Calibration:Modeling and Naming Aspectsincluding Automatic Generation


This keyword reflects the requirments ofhow to automatically generate displaynames for measurement, calibrationand diagnostic tools (MCD). Thekeyword is used for document internaltracing.

MemoryServices MEM Requirements on MemoryServices


This document specifies requirementson Basic Software Modules of thememory services.

Methodology METH AUTOSAR Methodology DocumentAbbreviation

This describes the AUTOSARMethodolgy.

MethodologyModelRules

MethModR Methodology Model Rules DocumentAbbreviation

This document describes theMethodology Model Rules.

MiscSupport MICS Miscellaneous Support DocumentAbbreviation

This document contains miscellaneoussupport items.

5




MetaModel MM Meta Model DocumentAbbreviation

This document describes the MetaModel.

MemoryHWAbstractionLayer

MMHWABLY Memory Hardware AbstractionLayer


This document describes the MemoryHardware Abstraction Layer.

ModeManagementGuide

MMG Mode Management Guide DocumentAbbreviation

This guideline describes the ModeManagement.

ModeMgm ModeMgm Mode Management DocumentAbbreviation

This document specifies ModeManagement in AUTOSAR.

MultiCoreGuide MTCG Multi Core Guide DocumentAbbreviation

This guideline describes Multi Core.

MethodologyAndTemplatesGeneral

MTG General Requirements onMethodology and Templates


This document has the purpose tocollect requirements on Methodologyand Templates which are relevant formore than one document.

OperatingSystemInterface

OSI Operating System Interface DocumentAbbreviation


Pesistency PER Persistency DocumentAbbreviation


PredefinedNames PDN AUTOSAR PredefinedNames DocumentAbbreviation

This document describes variouspredefined names used in AUTOSAR.

ProjectObjectives PO AUTOSAR Project Objectives DocumentAbbreviation

This document specifies the AUTOSARProject Objectives.

ReferenceBase RefBase Reference Base DocumentAbbreviation

This document contains ReferenceBase items.

Requirements Requirement Requirements AcceptanceTests


Requirements for the acceptance tests.

ReleaseOverviewAndRevHistory

RORH Release Overview And RevHistory


This document provides a ReleaseOverview and Rev History.

RTE RTE Runtime Environment DocumentAbbreviation

This document specifies the AUTOSARRuntime Environment.

SAE SAE Society of AutomotiveEngineers


This document describes the networkstandard developed by the Society ofAutomotive Engineers.

SafetyExtensions SAFEX Specifcation of SafetyExtensions


This document specifes how to describethe safety relevant properties andrequirements of an AUTOSAR System.

5




XMLSchemaSupplement

SchemaSupp XML Schema Supplement DocumentAbbreviation

This document explains the XMLSchema.

SecurityExtractTemplate

SECXT Security Extract Template DocumentAbbreviation

This document specifies securityexchange data.

SomeIpExample SIPEX SomeIp Example DocumentAbbreviation

This document contains SomeIpExamples.

SPAL SPAL Standard Peripheral AbstractionLayer


This document describes the StandardPeripheral Abstraction Layer.

SafetyUseCase SUC Safety Use Case DocumentAbbreviation

This document explains the Safety UseCases.

SWCModeling SWCM Software Component Modeling DocumentAbbreviation

This document describes the modelingof Software Components.

SoftwareComponentTemplate

SWCT Software Component Template DocumentAbbreviation

This document specifies how todescribe Software Components.

SWCModelingGuide SWMG SW-C and System ModelingGuide


This document gives guidelines andconventions on using the AUTOSARmodel elements in order to buildAUTOSAR systems.

SWCModelingGuide_NamingRules

SWNR Naming Rules in SW-C andSystem Modeling Guide


This document gives guidelines andconventions, in particular the namingrules on using the AUTOSAR modelelements in order to build AUTOSARsystems.

StandardizationTemplate

STDT Standardization Template DocumentAbbreviation

This specifies how AUTOSARStandardization is represented asARXML file.

SystemTemplate SYST System Template DocumentAbbreviation

This document specifies how todescribe AUTOSAR Systems.

TimingAnalysis TIMAY Specification of Timing Analysis DocumentAbbreviation

This document explains the TimingAnalysis.

TimingExtensions TIMEX Specification of TimingExtensions


This document specifies how todescribe the timing of an AUTOSARSystem.

TTCAN TTCAN Requirements on TTCAN DocumentAbbreviation

This document specifies the additionalTTCAN requirements for the CAN BSWstack.

5




UtilizationOfCryptoServices

UOC Utilization Of Crypto Services DocumentAbbreviation

This document explains the Utilizationof Crypto Services.

VirtualFunctionalBus VFB Virtual Functional Bus DocumentAbbreviation

This document describes the VirtualFunctional Bus.

XMLSchema XMLSchema XML Schema DocumentAbbreviation

This document describes the XMLSchema.

XMLSchemaProductionRules

XMLSPR XML Schema Production Rules DocumentAbbreviation

This document describes how a W3CXML schema specification compliantXML schema can be compiled out of theAUTOSAR meta-model.

Table 4.1: AUTOSAR Document Abbreviations for Trace Prefixes

5 [NamespaceAbbreviations] AUTOSAR Name Spaces

These keywords represent the name space abbreviations of AUTOSAR Adaptive Plat-form Functional Cluster.

[TR_PDN_00004] Document Abbreviations for Name Spaces dThis keyword setcontains the name space definitions:

• NamespaceAbbreviation: The abbrName represents a valid name space ab-breviation).

c()


com com Communication Management NamespaceAbbreviation

To be filled.exec exec Execution Management NamespaceAbbreviation

To be filled.not_available not_available Operating System NamespaceAbbreviation

To be filled.per per Persistency NamespaceAbbreviation

To be filled.diag diag Diagnostics NamespaceAbbreviation

To be filled.log log Log and Trace NamespaceAbbreviation

To be filled.5




time time Time Synchronisation NamespaceAbbreviation

To be filled.rest rest REpresentational State Transfer NamespaceAbbreviation

To be filled.ara ara Autosar API (in combination

with a cluster name ex:ara::rest)

NamespaceAbbreviation

To be filled.

Table 5.1: AUTOSAR Name Spaces



A Mentioned Class Tables

For the sake of completeness, this chapter contains a set of class tables representingmeta-classes mentioned in the context of this document but which are not containeddirectly in the scope of describing specific meta-model semantics.

Class Identifiable (abstract)

Package M2::AUTOSARTemplates::GenericStructure::GeneralTemplateClasses::Identifiable

Note Instances of this class can be referred to by their identifier (within the namespace borders). In addition tothis, Identifiables are objects which contribute significantly to the overall structure of an AUTOSARdescription. In particular, Identifiables might contain Identifiables.

Base ARObject , MultilanguageReferrable, Referrable

Subclasses ARPackage, AbstractDoIpLogicAddressProps, AbstractEvent , AbstractImplementationDataTypeElement ,AbstractSecurityEventFilter , AbstractSecurityIdsmInstanceFilter , AbstractServiceInstance, ApplicationEndpoint, ApplicationError, AtpBlueprint , AtpBlueprintable, AtpClassifier , AtpFeature, AutosarOperationArgumentInstance, AutosarVariableInstance, BlockState, BuildActionEntity , BuildActionEnvironment,Chapter, ClassContentConditional, ClientIdDefinition, ClientServerOperation, Code, CollectableElement ,ComManagementMapping, CommConnectorPort , CommunicationConnector , CommunicationController ,Compiler, ConsistencyNeeds, ConsumedEventGroup, CouplingPort, CouplingPortStructuralElement ,CryptoKeySlot, CryptoServiceMapping, DataPrototypeGroup, DataTransformation, DependencyOnArtifact, DiagEventDebounceAlgorithm, DiagnosticConnectedIndicator, DiagnosticDataElement,DiagnosticFunctionInhibitSource, DiagnosticRoutineSubfunction, DltArgument, DltLogChannel, DltMessage, DoIpInterface, DoIpLogicAddress, DoIpRoutingActivation, EndToEndProtection, EthernetWakeupSleepOnDatalineConfig, ExclusiveArea, ExecutableEntity , ExecutionTime, FMAttributeDef, FMFeatureMapAssertion, FMFeatureMapCondition, FMFeatureMapElement, FMFeatureRelation, FMFeatureRestriction, FMFeatureSelection, FrameTriggering, GeneralParameter, GlobalTimeGateway,GlobalTimeMaster , GlobalTimeSlave, HeapUsage, HwAttributeDef, HwAttributeLiteralDef, HwPin, HwPinGroup, IPSecRule, IPv6ExtHeaderFilterList, ISignalToIPduMapping, ISignalTriggering, IdentCaption,InternalTriggeringPoint, Keyword, LifeCycleState, Linker, MacMulticastGroup, McDataInstance, MemorySection, ModeDeclaration, ModeDeclarationMapping, ModeSwitchPoint, NetworkEndpoint, NmCluster ,NmNode, PackageableElement , ParameterAccess, PduToFrameMapping, PduTriggering, PhysicalChannel , PortGroup, PortInterfaceMapping, PossibleErrorReaction, ResourceConsumption, RootSwCompositionPrototype, RptComponent, RptContainer, RptExecutableEntity, RptExecutableEntityEvent,RptExecutionContext, RptProfile, RptServicePoint, SdgAttribute, SdgClass, SecureCommunicationAuthenticationProps, SecureCommunicationFreshnessProps, SecurityEventContextProps, ServiceNeeds, SignalServiceTranslationEventProps, SignalServiceTranslationProps, SocketAddress, SomeipTpChannel, SpecElementReference, StackUsage, StaticSocketConnection, StructuredReq, SwGenericAxisParamType, SwServiceArg, SwcServiceDependency, SystemMapping, TimeBaseResource, TimingCondition, TimingConstraint , TimingDescription, TimingExtensionResource, TimingModeInstance,Topic1, TpAddress, TraceableTable, TraceableText, TracedFailure, TransformationProps, TransformationTechnology, Trigger, VariableAccess, VariationPointProxy, ViewMap, VlanConfig

Attribute Type Mult. Kind Note

adminData AdminData 0..1 aggr This represents the administrative data for the identifiableobject.

Tags:xml.sequenceOffset=-40

annotation Annotation * aggr Possibility to provide additional notes while defining amodel element (e.g. the ECU Configuration ParameterValues). These are not intended as documentation butare mere design notes.


category CategoryString 0..1 attr The category is a keyword that specializes the semanticsof the Identifiable. It affects the expected existence ofattributes and the applicability of constraints.


5



4Class Identifiable (abstract)

desc MultiLanguageOverviewParagraph

0..1 aggr This represents a general but brief (one paragraph)description what the object in question is about. It is onlyone paragraph! Desc is intended to be collected intooverview tables. This property helps a human reader toidentify the object in question.

More elaborate documentation, (in particular how theobject is built or used) should go to "introduction".


introduction DocumentationBlock 0..1 aggr This represents more information about how the object inquestion is built or is used. Therefore it is aDocumentationBlock.


uuid String 0..1 attr The purpose of this attribute is to provide a globallyunique identifier for an instance of a meta-class. Thevalues of this attribute should be globally unique stringsprefixed by the type of identifier. For example, to include aDCE UUID as defined by The Open Group, the UUIDwould be preceded by "DCE:". The values of this attributemay be used to support merging of different AUTOSARmodels. The form of the UUID (Universally UniqueIdentifier) is taken from a standard defined by the OpenGroup (was Open Software Foundation). This standard iswidely used, including by Microsoft for COM (GUIDs) andby many companies for DCE, which is based on CORBA.The method for generating these 128-bit IDs is publishedin the standard and the effectiveness and uniqueness ofthe IDs is not in practice disputed. If the id namespace isomitted, DCE is assumed. An example is"DCE:2fac1234-31f8-11b4-a222-08002b34c003". Theuuid attribute has no semantic meaning for an AUTOSARmodel and there is no requirement for AUTOSAR tools tomanage the timestamp.

Tags:xml.attribute=true

Table A.1: Identifiable

Class Keyword

Package M2::AUTOSARTemplates::CommonStructure::StandardizationTemplate::Keyword

Note This meta-class represents the ability to predefine keywords which may subsequently be used toconstruct names following a given naming convention, e.g. the AUTOSAR naming conventions.

Note that such names is not only shortName. It could be symbol, or even longName. Application ofkeywords is not limited to particular names.

Base ARObject , Identifiable, MultilanguageReferrable, Referrable


abbrName NameToken 1 attr This attribute specifies an abbreviated name of akeyword. This abbreviation may e.g. be used forconstructing valid shortNames according to theAUTOSAR naming conventions.

Unlike shortName, it may contain any name token. E.g. itmay consist of digits only.

classification NameToken * attr This attribute allows to attach classification to theKeyword such as MEAN, ACTION, CONDITION, INDEX,PREPOSITION

Table A.2: Keyword



Class MultilanguageReferrable (abstract)


Note Instances of this class can be referred to by their identifier (while adhering to namespace borders). Theyalso may have a longName. But they are not considered to contribute substantially to the overallstructure of an AUTOSAR description. In particular it does not contain other Referrables.

Base ARObject , Referrable

Subclasses Caption, DefItem, DocumentationContext, Identifiable, SdgCaption, TraceReferrable, Traceable


longName MultilanguageLongName

0..1 aggr This specifies the long name of the object. Long name istargeted to human readers and acts like a headline.

Table A.3: MultilanguageReferrable

Class Referrable (abstract)


Note Instances of this class can be referred to by their identifier (while adhering to namespace borders).

Base ARObject

Subclasses AtpDefinition, BswDistinguishedPartition, BswModuleCallPoint , BswModuleClientServerEntry, BswVariableAccess, CouplingPortTrafficClassAssignment, DiagnosticDebounceAlgorithmProps, DiagnosticEnvModeElement , EthernetPriorityRegeneration, EventHandler, ExclusiveAreaNestingOrder, HwDescriptionEntity , ImplementationProps, LinSlaveConfigIdent, ModeTransition, MultilanguageReferrable,PduActivationRoutingGroup, PncMappingIdent, SingleLanguageReferrable, SoConIPduIdentifier, SocketConnectionBundle, TimeSyncServerConfiguration, TpConnectionIdent


shortName Identifier 1 attr This specifies an identifying shortName for the object. Itneeds to be unique within its context and is intended forhumans but even more for technical reference.

Stereotypes: atpIdentityContributorTags:xml.enforceMinMultiplicity=truexml.sequenceOffset=-100

shortNameFragment

ShortNameFragment * aggr This specifies how the Referrable.shortName iscomposed of several shortNameFragments.


Table A.4: Referrable


Predefined Names in AUTOSAR - Enabling Innovation

Documents

Transcript of Predefined Names in AUTOSAR - Enabling Innovation