Software Component Editors

AUTOSAR software components are generic application-level components that are designed to be independent of both CPU and location in the vehicle network. An AUTOSAR software component (SWC) can be mapped to any available ECU during system configuration, subject to constraints imposed by the system designer.

An AUTOSAR software component is therefore the atomic unit of distribution in an AUTOSAR system; it must be mapped completely onto one ECU.

Before an SWC can be created, its component type (SWC type) must be defined. The SWC type identifies fixed characteristics of an SWC, i.e. port names, how ports are typed by interfaces, how the SWC behaves, etc. The SWC type is named, and the name must be unique within the system. Thus, an SWC consists of the following parts:

• A complete formal SWC description that indicates how the infrastructure of the component must be configured.
• An SWC implementation that contains the functionality (in the form of C code or object code).

To allow an SWC to be used, it needs to be instantiated at configuration time. Furthermore, it is possible to configure an SWC in a way that it can be multiply instantiated. The distinction between type and instance is analogous to types and variables in conventional programming languages. You define an application-wide unique type name (SWC type), and declare one or more uniquely named variables of that type (one or more SWC instances).

AUTOSAR software components can be specified as block diagrams or in ESDL code. The block diagram and ESDL software component editors of ASCET allow defining and implementing the behavior of AUTOSAR-compliant vehicle functions in terms of software components. ASCET supports AUTOSAR SWC descriptions and the generation of AUTOSAR-compliant SWC production code according to AUTOSAR 4.0.2, 4.0.3, 4.2.2, 4.3.0 and R4.3.1.

See also

Ports and Interfaces

Runnable Entities and Events

Modes and Mode Groups

Editing Software Components

https://www.autosar.org