The standardized software framework for intelligent mobility

Subgroups WP-A (Software Architecture)

Subgroup WP-A-LIB (Libraries)

Technical Scope

WP-A-LIB is responsible for the definition of all AUTOSAR Library functions which includes fixed-point and floating-point math functions including:

  • Basic arithmetic functions
  • Controller functions
  • Filter functions
  • Interpolation functions
  • Trigonometric functions
  • Other miscellaneous functions
  • Bit handling functions
  • CRC functions
  • Crypto functions
  • Software component end-to-end communication protection functions

Subgroups WP-M (Methodology and Templates)

Subgroup WP-M-SWCT (Software Component Template)

Technical Scope

The subgroup is responsible for the definition of the template documents and technical reports listed below

  • Software Component Template
  • Basic Software Module Description Template
  • Interoperability of AUTOSAR Tools

Subgroup WP-M-SYST (System Template, ECU Configuration)

Technical Scope

The subgroup is responsible for the definition of the following template documents:

  • System Template
  • ECU Configuration Template
  • ECU Resource Template

The subgroup is also responsible for the maintenance of configuration of basic software modules and for ECU Configuration Parameter.

Subgroup WP-M-TIMEX (Timing Extensions)

Technical Scope

The subgroup is responsible for the definition of the template document AUTOSAR Specification of Timing Extensions including

  • to specify capabilities for creating and maintaining timing models such that the construction and timing analysis of distributed embedded systems are supported.

Subgroup WP-M-METH (Methodology)

Technical Scope

The purpose/scope of the Methodology subgroup is to specify processes and workflows for designing and developing AUTOSAR based ECUs. The methodology documents provide guidance for adopting the AUTOSAR development process within a company.
The subgroup is responsible for the definition of the template documents and technical reports listed below

  • Methodology Template

Subgroup WP-M-GST (Generic Structure Template)

Technical Scope

The purpose/scope of the General Structure Template subgroup is to specify the core mechanisms used to define templates and setup the required understanding of AUTOSAR templates.
The subgroup is responsible for the definition of the template documents and technical reports listed below

  • General Structure Template
  • Standardization Template
  • Predefined Names
  • General Definitions

Subgroups WP-I (Application Interfaces)

Subgroup WP-I-BODY (Body and Comfort)

Technical Scope

WP-I-BODY is responsible for the definition of all the AUTOSAR elements related to the application level of Body and Comfort domain including

  • Decomposition into one or more software components
  • Definition of related ports, interfaces, data elements, design patterns
  • Relationship to other AUTOSAR application level domains

Subgroup WP-I-ENGINE (Powertrain Engine)

Technical Scope

WP-I-ENGINE is responsible for the definition of all the AUTOSAR elements related to the application level of Powertrain Engine domain including

  • Decomposition into one or more software components
  • Definition of related ports, interfaces, data elements, design patterns
  • Relationship to other AUTOSAR application level domains

Further activities include

  • Applying concepts relevant or specific to domain Powertrain Engine
  • Measurement and calibration issues

The scope includes the systems Combustion Engine / Electric Machine.

Subgroup WP-I-TRSM (Powertrain Transmission)

Technical Scope

WP-I- TRSM is responsible for the definition of all the AUTOSAR elements related to the application level of Powertrain Transmission domain including

  • Decomposition into one or more software components
  • Definition of related ports, interfaces, data elements, design patterns
  • Relationship to other AUTOSAR application level domains

The scope includes the system Transmission.

Subgroup WP-I-CHASSIS (Chassis Control)

Technical Scope

WP-I-CHASSIS is responsible for the definition of all the AUTOSAR elements related to the application level of Chassis Control domain including

  • Decomposition into one or more software components
  • Definition of related ports, interfaces, data elements, design patterns
  • Relationship to other AUTOSAR application level domains

Further activities include

  • Verification and validation of implementation by Lead WP-I
  • Chassis explanatory documentation
  • Technical coordination of inter domain interfaces

Subgroup WP-I-OCSAFE (Occupant and Pedestrian Safety)

Technical Scope

WP-I-OCSAFE is responsible for the definition of all the AUTOSAR elements related to the application level of Occupant and Pedestrian Safety domain including

  • Decomposition into one or more software components
  • Definition of related ports, interfaces, data elements, design patterns
  • Relationship to other AUTOSAR application level domains