6.2.5.1. Architecture-ARXMLImportModel

Instantiate and import an AUTOSAR classic ECU extract of System Description into an RFG

Required inputs: RFG

This rule is intended for projects developed according to AUTOSAR classic methodology. See option arxml_name to select the ARXML import.

The model represented in ARXML is imported into the RFG for inspection of the imported data or for model-to-model checks (to compare it to a high-level architecture model).

Possible Messages

This rule has no predefined messages.

Options

advanced

Advanced settings. Typically these should not be changed.
 

advanced.map_from_rfg_instead_of_ir : bool = False

Do not require an IR file to be present in the project. Instead, compute the source mapping directly from the RFG. This can be useful for debugging if IR is not available. Setting this to true may negatively impact execution time and parallelization.
 

arxml_name

arxml_name : str = 'default'

Name of the ARXML import. This shall be configured in an instance of the rule Frameworks-AutosarArxml to refer to a specific set of ARXML files.
 

export_warnings

export_warnings : bool = True

Export output messages to the analysis database.
 

hierarchy_view_name

hierarchy_view_name : str = 'Module'

Hierarchy view to map source code onto the swc_types_view
 

loglevel

loglevel : LogLevel = 'WARNING'

Logging mode. WARNING only outputs errors and warnings, INFO additionally prints info messages, DEBUG additionally outputs info and debug messages.
 

prototype_instantiation_view_name

prototype_instantiation_view_name : str | None = None

Connect prototypes from the prototype_view to the type representation in swc_type_view, if those two are generated. This view can be used to trace an instance back to its type node.
 

prototype_view_name

prototype_view_name : str | None = 'ARXML'

Name of the view containing the instantiated software component prototypes. This contains the set of deployed systems and their connections. Set to None to omit this view.
 

provide_dependencies_in_type_view

provide_dependencies_in_type_view : bool = False

In the swc_type_view, it may be useful to also see the dependencies between ports. Although naturally, they would only be represented in the prototype_view, the dependencies can be inserted in the swc_type_view. This means, if any pair of port prototypes P and R of SWC prototypes (instantiated from SWC types) are connected, then the corresponding port prototypes P' and R' of the SWC types will also be connected.
 

provide_runnables_in_prototype_view

provide_runnables_in_prototype_view : bool = False

In the prototype_view, it may be useful to also see the SWCs runnable entities. Although naturally, they would be represented in the swc_type_view, the runnable entities can be copied into the prototype_view. In case of multiply instantiated SWCs, their runnable entities would exists several times in this view. Thus, this view can not be used for a mapping of source code onto this view (that would be ambiguous).
 

swc_type_mapping_name

swc_type_mapping_name : str | None = 'ARXML Type Mapping'

Mapping of source code implementation to the swc_type_view. Set to None to omit this view.
 

swc_type_view_name

swc_type_view_name : str | None = 'ARXML Types'

Name of the view for software component types. The nodes created in this view can be mapped to the implementation of the application's runnable entities. Set to None to omit this view.
 

systems_to_deploy

systems_to_deploy : set[str] = set()

Set of names of Systems to instantiate into the prototype_view. Each System defines a root composition prototype. We proceed from this to select all the prototypes (and their types) to instantiate.
 

Option Types

These types are used by options listed above:

LogLevel

An enumeration.
 

  • WARNING

  • INFO

  • DEBUG