Implicit base class of all classes in metamodel. checksum calculated from the * attributes * aggregations and aggregated non-identifiables * references the timestamp of the creation or modification of an instance, its attributes, references or aggregated non-identifiables. AUTOSAR package, allowing to create top level packages to structure the contained ARElements. ARPackages are open sets, which means that in a file based description system, multiple files can be used to partially describe the contents of a package. This is an extended version of MSR's SW-SYSTEM. AUTOSAR package, allowing to create top level packages to structure the contained ARElements. ARPackages are open sets, which means that in a file based description system, multiple files can be used to partially describe the contents of a package. This is an extended version of MSR's SW-SYSTEM. Root element of an AUTOSAR description, also the root element in corresponding XML documents. Root element of an AUTOSAR description, also the root element in corresponding XML documents. Root element of an AUTOSAR description, also the root element in corresponding XML documents. Instances of this class can be referred to by their identifier (while adhering to namespace borders). A machine readable name of the meta class instance. As defined for the M2 datatype Identifier, the shortName needs to be unique within the namespace it is declared in. A category allows specifying the particular nature of the object in question. In most cases, this categorization ends up in a subset of information which is appropriate for an object of the category in question. Instances of this class can be referred to by their identifier (while adhering to namespace borders). The purpose of this attribute is to provide a globally unique identifier for an instance of a metaclass. The values of this attribute should be globally unique strings prefixed by the type of identifier. For example, to include a DCE UUID as defined by The Open Group, the UUID would be preceded by "DCE:". The values of this attribute may be used to support merging of different AUTOSAR models. The form of the UUID (Universally Unique Identifier) is taken from a standard defined by the Open Group (was Open Software Foundation). This standard is widely used, including by Microsoft for COM (GUIDs) and by many companies for DCE, which is based on CORBA. The method for generating these 128-bit IDs is published in the standard and the effectiveness and uniqueness of the IDs is not in practice disputed. If the id namespace is omitted, DCE is assumed. An example is "DCE:2fac1234-31f8-11b4-a222-08002b34c003". Use <longName1> to create a comprehensive name for the context element Use <sup> to display sections of text within a paragraph element, in a smaller font above the base line. Use <sub> to display sections of text within a paragraph element, in a smaller font beneath the base line. Use <longName1> to create a comprehensive name for the context element Use <sup> to display sections of text within a paragraph element, in a smaller font above the base line. Use <sub> to display sections of text within a paragraph element, in a smaller font beneath the base line. Use <sup> to display sections of text within a paragraph element, in a smaller font above the base line. Use <sub> to display sections of text within a paragraph element, in a smaller font beneath the base line. Use <sup> to display sections of text within a paragraph element, in a smaller font above the base line. Use <sub> to display sections of text within a paragraph element, in a smaller font beneath the base line. Use <sup> to display sections of text within a paragraph element, in a smaller font above the base line. Use <sub> to display sections of text within a paragraph element, in a smaller font beneath the base line. This element is the same as function here as in a HTML document i.e. it forces a line break. Use <ft> , to create a footnote. Use <ft> , to create a footnote. Use <ie> to create an index that is to appear in the index directory. Use <sup> to display sections of text within a paragraph element, in a smaller font above the base line. Use <sub> to display sections of text within a paragraph element, in a smaller font beneath the base line. Use <ie> to create an index that is to appear in the index directory. Use <ie> to create an index that is to appear in the index directory. Use <std> to reference external standards within a paragraph element. Use <subtitle> to enter a sub-heading of an external standard. Use <state1> to enter the version and state of a standard or an external document. Use <date1> , to enter the validity date of a standard document, or the creation date of an external document. The element is like <date> but is never handled multilingual. <date> is used to capture a time stamp. It must match to one of the following syntaxes based on Representation of dates and times ISO-8601: <YYYY>-<MM>-<DD>[T<hh>:<mm>:<ss>] <YYYY>.<MM>.<DD>[T<hh>:<mm>:<ss>] <YYYY>/<MM>/<DD>[T<hh>:<mm>:<ss>] The last pattern is the most preferred one, since it reflects a common use in US. Use <position> to enter references to the relevant positions of a standard. Use <std> to reference external standards within a paragraph element. Use <tt> to format technical terms within the paragraph element. Use <tt> to format technical terms within the paragraph element. This element specifies the Uniform Resource Locator (URL) of the context contained in the <url> element. This element specifies the Uniform Resource Locator (URL) of the context contained in the <url> element. Use <xdoc> , to reference an external document. Use <number> to enter the version number of an external document that is referenced. Use <state1> to enter the version and state of a standard or an external document. Use <date1> , to enter the validity date of a standard document, or the creation date of an external document. The element is like <date> but is never handled multilingual. <date> is used to capture a time stamp. It must match to one of the following syntaxes based on Representation of dates and times ISO-8601: <YYYY>-<MM>-<DD>[T<hh>:<mm>:<ss>] <YYYY>.<MM>.<DD>[T<hh>:<mm>:<ss>] <YYYY>/<MM>/<DD>[T<hh>:<mm>:<ss>] The last pattern is the most preferred one, since it reflects a common use in US. Use <publisher> to enter the publisher of an external document that is being referenced. Use <position> to enter references to the relevant positions of a standard. Use <xdoc> , to reference an external document. Use <xfile> , to reference an external file. This element indicates the data format of the external file in which the superordinated XFILE is located. The identifier itself must be arranged amongst the project participants. The contents of <notation> are treated in a similar way to an SGML notation format. Possible values are for example: Notation * Meaning EPS * Encapsulated Postscript PDF * Portable Document Format PaCo * Parameter Contents File in MSRSW2.2 structure ... * ... This element describes the tool which was used to generate the corresponding <xfile> . This element describes the tool version which was used to generate the corresponding <xfile> . Use <xfile> , to reference an external file. Use <xref> , to generate cross-references within the document. Use <xref> , to generate cross-references within the document. This element specifies a reference target which can be scattered throughout the text. This element specifies a reference target which can be scattered throughout the text. <adminData> can be used to set administrative information for an element. This administration information is to be treated as metadata such as revision id or state of the file. There are basically four kinds of metadata * The language and/or used laguages. * Revision information covering e.g. revision number, state, release date, changes. Note that this information can be given in general as well as related to a particular company. * Document metadata specific for a company * Formatting controls that can affect layouts for example. * Revision information for the element. <language> represents the human language used within the file. Its primary use is to prompt the tools to switch to an appropriate language. This element is in accordance with the ISO 639-1 two letter language codes ( Codes for the Representation of Names of Languages http://www.loc.gov/standards/iso639-2/langcodes.html ). The most frequently used codes are given in : Most common language codes (alphabetical) Code * Language de * German en * English es * Spanish fr * French it * Italian jp * Japanese <adminData> can be used to set administrative information for an element. This administration information is to be treated as metadata such as revision id or state of the file. There are basically four kinds of metadata * The language and/or used laguages. * Revision information covering e.g. revision number, state, release date, changes. Note that this information can be given in general as well as related to a particular company. * Document metadata specific for a company * Formatting controls that can affect layouts for example. * Revision information for the element. Use <companyRevisionInfo> , to generate information on document version within the respective company. Use <revisionLabelP1>, to enter the version number of the ** of the document, or the document section to which administrative is applied.. The syntax is free and refers to the configuration management plan respectively the version management tool being used. This element is used, if the document or document section is the result of a merge process in which two branches are merged in to one new revision. Use <revisionLabelP1>, to enter the version number of the ** of the document, or the document section to which administrative is applied.. The syntax is free and refers to the configuration management plan respectively the version management tool being used. This element is used, if the document or document section is the result of a merge process in which two branches are merged in to one new revision. Use <companyRevisionInfo> , to generate information on document version within the respective company. Use <docRevision> , to generate information on the corresponding document version. Use <revisionLabelP1>, to enter the version number of the ** of the document, or the document section to which administrative is applied.. The syntax is free and refers to the configuration management plan respectively the version management tool being used. This element is used, if the document or document section is the result of a merge process in which two branches are merged in to one new revision. Use <revisionLabelP1>, to enter the version number of the ** of the document, or the document section to which administrative is applied.. The syntax is free and refers to the configuration management plan respectively the version management tool being used. This element is used, if the document or document section is the result of a merge process in which two branches are merged in to one new revision. Use <docRevision> , to generate information on the corresponding document version. Use <modification> to record what has changed in a document in comparison to its predecessor. Use <modification> to record what has changed in a document in comparison to its predecessor. System aggregates all elements that define a system constraint description or system configuration description. System is a PropertyContainer since we want to model variants as properties. For each dimension of variability, one property is added. Configuration parameter type for Boolean. allowed values are true and false. Default value of the boolean configuration parameter. Configuration parameter type for Boolean. allowed values are true and false. Used to define configuration containers that provide a choice between several ParamConfContainerDef. But in the actual ECU Configuration Description only one instance from the choice list can be used. Used to define configuration containers that provide a choice between several ParamConfContainerDef. But in the actual ECU Configuration Description only one instance from the choice list can be used. Specify alternative references where in the ECU Configuration description only one of the specified references will actually be used. Specify alternative references where in the ECU Configuration description only one of the specified references will actually be used. Attributes used by Configuration Parameters as well as References. Specifying the actual configuration class of a configuration parameter in the "vendor specific module definition" in which it is mandatory. String specifying if this configuration parameter is an AUTOSAR standardized configuration parameter or if the parameter is hardware- or vendor-specific. Abstract class used to define the similarities of all ECU Configuration Parameter types defined as subclasses. Specifies that this parameter's value is used, together with the aggregating container, to derive a symbolic name definition. E.g.: #define "container_shortName" "this parameter's value". Base class used to gather common attributes of configuration container definitions. Specifies if the number of instances of this container my be changed postBuild time. This parameter may only be set to true if all of the following conditions hold: - the container's upperMultiplicity > lowerMultiplicity - all parameters within the container and subContainers are postBuild changeable. If any of the aggregated parameters is either preCompile time or link time this attribute is ignored and may be ommited. Derived value is of type Boolean Derived value is an Enumeration. Derived value is of type Float Derived value is of type Integer. Allows to define configuration items that are calculated based on the value of * other parameters values * elements (attributes /classes) defined in other AUTOSAR templates such as System template and SW component template. For these definitions there is no corresponding entry in the ECUC description. Instead, a calculation definition is given that defines how Configuration Editors and Generators can calculate the value from other values when needed to display/use the configuration item Definition of the formula used to calculate the value of the configuration element. Definition of the languag used to specify the formula in attribute calculationFormula. Currentlfy, only informal definition of the formula is supported. Derived value is of type String. This represents the anchor point of an ECU Parameter Definition within the AUTOSAR templates structure. This represents the anchor point of an ECU Parameter Definition within the AUTOSAR templates structure. Configuration parameter type for enumeration literals definition. Configuration parameter type for Enumeration. Default value of the enumeration configuration parameter. This string nees to be one of the literals specified for this enumeration. Configuration parameter type for Enumeration. Configuration parameter type for Float. Default value of the float configuration parameter. max value allowed for the parameter defined. min value allowed for the parameter defined. Configuration parameter type for Float. Specify a reference to an XML description of an entity desribed in another AUTOSAR template. The type in the AUTOSAR Metamodel to which' instance this reference is allowed to point to. Specify a reference to an XML description of an entity desribed in another AUTOSAR template. Configuration parameter type for Function Names like those used to specify callback functions. Specify a reference to an XML description of an entity desribed in another AUTOSAR template using the INSTANCE REFERENCE semantics. The context in the AUTOSAR Metamodel to which' this reference is allowed to point to. The type in the AUTOSAR Metamodel to which' instance this reference is allowed to point to. Specify a reference to an XML description of an entity desribed in another AUTOSAR template using the INSTANCE REFERENCE semantics. Configuration parameter type for Integer. Default value of the integer configuration parameter. max value allowed for the parameter defined. min value allowed for the parameter defined. Configuration parameter type for Integer. Used as the top-level element for configuration definition for Software Modules, including BSW and RTE as well as ECU Infrastructure. Used to define the actual implemented configuration variant in a specific "vendor specific module definition", where it is mandatory. Used as the top-level element for configuration definition for Software Modules, including BSW and RTE as well as ECU Infrastructure. Used to define configuration containers that can hierarchically contain other containers and/or parameter definitions. Used to define configuration containers that can hierarchically contain other containers and/or parameter definitions. Common class used to express multiplicities in the definition of configuration parameters and containers. If not stated otherwise the default multiplicity is exactly one mandatory occurrence of the specified element. The lower multiplicity of the specified element. 0: optional 1: at least one occurence n: at least n occurrences The upper multiplicity of the specified element. 1: at most one occurrence m: at most m occurrences *: arbitrary number of occurrences Specify references within the ECU Configuration Description between parameter containers. Specify references within the ECU Configuration Description between parameter containers. Configuration parameter type for String. Default value of the string configuration parameter. Configuration parameter type for String. This specialization of a ReferenceDef specifies that the implementation of the reference is done using a symbolic name defined by the referenced Container's shortName. Representing a configuration value of definition type BooleanParamDef Stores the value of the Boolean parameter. Representing a configuration value of definition type BooleanParamDef Abstract class to be used as common parent for all reference values in the ECU Configuration Description. Represents a Container definition in the ECU Configuration Description. Represents a Container definition in the ECU Configuration Description. This represents the anchor point of the ECU configuration description. This represents the anchor point of the ECU configuration description. Representing a configuration value of definition type EnumerationParamDef Stores the chosen literal. Representing a configuration value of definition type EnumerationParamDef Representing a configuration value of definition type FloatParamDef Stores the value of the Float parameter. Representing a configuration value of definition type FloatParamDef Representing a configuration value of definition type FunctionNameParamDef Representing a configuration value of definition type IntegerParamDef Stores the value of the Integer parameter. Representing a configuration value of definition type IntegerParamDef Head of the configuration of one Module. A Module can be a BSW module as well as the RTE and ECU Infrastructure. As part of tthe BSW module description, the ModuleConfiguration has two different roles: The recommendedConfiguration contains parameter values recommended by the BSW module vendor. The preconfiguredConfiguration contains values for those parameters which are fixed by the implementation and cannot be changed. These two ModuleConfigurations are used when the base ModuleConfiguration (as part of the base ECU configuration) is created to fill parameters with initial values. Head of the configuration of one Module. A Module can be a BSW module as well as the RTE and ECU Infrastructure. As part of tthe BSW module description, the ModuleConfiguration has two different roles: The recommendedConfiguration contains parameter values recommended by the BSW module vendor. The preconfiguredConfiguration contains values for those parameters which are fixed by the implementation and cannot be changed. These two ModuleConfigurations are used when the base ModuleConfiguration (as part of the base ECU configuration) is created to fill parameters with initial values. Common class to all types of configuration values Used to represent a configuration value that has a parameter definition of type ConfigReference (used for all of its specializations excluding InstanceReferenceDef). Used to represent a configuration value that has a parameter definition of type ConfigReference (used for all of its specializations excluding InstanceReferenceDef). Representing a configuration value of definition type StringParamDef Stores the value of the String parameter. Representing a configuration value of definition type StringParamDef