Provided Interface

To connect to a sender-
Software Components Required Interface
To connect to a sender-
receiver interface
This is a sender
receiver interface
This is a receiver

 A SWC is described on three

distinctive levels:
 SWC type describes the external
behaviour
 Provided interfaces Software
– What the component gives
– This is done through P-Ports
Component
 Required interfaces
– What the component needs
– This is done through R-Ports
 SWC internal behaviour describes how
the software component behaves
internally.
 SWC implementation e.g. resource Required Interface Provided Interface
To connect to a client-server
usage. interface
To connect to a client-server
interface
This is a client
 SWC-description is a standardized This is a server
XML format

Volvo 3P
 External interfaces

Receiver
Sender
 AUTOSAR provides 2
communication paradigms for
software components

RTE
 Sender-Receiver
 Message passing

Client Server
 Client-Server
 Function invocation

RTE

Volvo 3P
 Internal Behaviour captures what happens inside the

Internal Behaviour software component

External
My Component Runnables capture a
thread of execution in
Behaviour inside the software
The ports component – this is a
define the model of the code that will
run when something
external view
of the SWC – Runnable happens.
what other
SWCs see.
Events link events on the ports
to runnables inside the SWC.

Runnable Inter-runnable variables

provide communication between
runnables in a SWC
Variable

PIM Per-instance memory provide

Runnable persistant storage between
runnable invocations
Parameter
Calibration Parameters provide
access to parameters

Volvo 3P
 This is an assembly We can group components into a
connector between a P- composition. Note that connectors do not
Visualising Compositions PORT and an R-PORT need to be connected within the
composition.

A port on a
Composition composition

SWC SWC
Instance Instance
SWC
Instance
A delegation
connector

An assembly
connector

A delegation connector
A port on a
SWC composition
Instance

An assembly Composition
connector

Volvo 3P
 Port Specific Attributes
SWC
Component
Type
 Each instance created inherits
the properties of the parent type
 All ports, characteristcs etc. IS-QUEUED = true
Queue 6 elements on this
receiver

 However, each port on each

instance can be parameterised
 For example different receiver
instances may need to queue Receiver1
different numbers of data elements Component
Instance Receiver2
Component
Instance
 Parameterisation is done through
[SENDER|RECEIVER|SERVER-
Queue 3 elements on this
COM-SPECS receiver
 Clients are not parameterised
Volvo 3P
 Defining an ECU
 Before a system can be created an ECU must be created
 This is the hardware equivalent of a SWC
 We do not map SWCs to ECUs
 We map SWC instances to ECU instances

Component
Type


A
Component
Instance
B
Component
Instance


 So we need to define ECU types and create instances of them

Volvo 3P
 System Mappings
 For the inter-ECU SYSTEM a SYSTEM-MAPPING is required to map SWCs
onto ECUs

Composition
SWC SWC SWC
Prototype Prototype Prototype

Composition SWC
Prototype

ECUs

Volvo 3P
 Mapping Runnables to Tasks

 SWC Instance ->ECU Instance

mapping is not sufficient
 Need to know how runnables are
mapped into tasks.
 This mapping is defined in the
AUTOSAR ECU configuration
description
 ECU configuration is a standardized
XML format
 The configuration defines
 Tasks, Priorities and the order Task1_ECU1 Task1_ECU2
runnables occur in the task

Task2_ECU1

Volvo 3P
 Data Mappings: Data Element to COM Signal

 Each data element sent on a sender-receiver interface must be mapped to a COM signal

 Mapping is done in the ECU configuration description

 Specifies which data element is mapped to which COM signal

 Data Element
SWC Letter SWC

COMSignal
Envelope1

Volvo 3P