Task: Allocate Design Functions on HW Components
This task specifies in which hardware element each function will execute.
Disciplines: Core Tasks
Purpose
The purpose of this task is to define a functional allocation such that the functional content of each hardware component is known.
Relationships
Main Description
Each of the Functions of the FDA will eventually be realized by software in an ECU. The Design architecture contains allocation constraints that define which Function will be allocated to which node.
To map the functional design architecture, each elementary Function will be associated to a hardware component by an allocation constraint. Composite Functions may also be allocated, in which case their entire hierarchy is allocated to the identified node.
In case no allocation constraint is defined for a Function, its allocation is free. Such Functions can in the implementation phase be allocated to any hardware component found appropriate.
Logical HW does not need to be explicitly allocated, as the type definition of each transfer function is already linked to their respective hardware component.
BSWFunctions can be allocated to hardware components of the HDA, but typically this is implicit by the allocation of application functions relying on the particular middleware service.
Steps
Map functions to hardware elements
Each function in the functional design architecture is mapped to an appropriate hardware component in the hardware design architecture. The mapping must not violate any design constraint.