Task: Assign Functionality to HW or SW |
| |
 |
This task decides which functional logic, in the function analysis architecture shall be executed by HW or SW. Check for possible reusable parts or solutions available on market and constraints related to them. |
Disciplines: Core Tasks |
|
Purpose
The purpose of this task is to decide which FAA functionality will be realized by
Hardware entities, and which part will be realized in SW.
|
Relationships
Roles | Primary Performer:
| Additional Performers:
|
Inputs | Mandatory:
| Optional:
|
Outputs |
|
Process Usage |
|
Main Description
The FAA is realized by the FDA, which in turn consists of a set of Functions. These are furthermore distributed on the
topology represented by the HDA.
This task assigns/partitions the Functions into two groups: the Functions to be implemented in software and those to be
implemented in hardware.
The partitioning will have certain implications on the allocation and the resulting performance. It could therefore be
helpful to consider some of these possible implications in subsequent tasks. The following paragraph enumerates a few
implications on allocation, but it should be emphasized that these actions are not performed by this task. This task only
performs the assignment/partitioning of Functions into two disjoint sets.
Functions in the FAA may be realized by software or programmable (or in some cases, custom-made) hardware.
In the case of software realization, Functions are defined in the FDA.
In the case of hardware realization, hardware elements are defined in the HDA and their behavior is defined as Functions
acting as transfer functions. In addition interfacing functionality need to be defined in the FDA.
Functional devices in the FAA are typically realized by HWFunctions, BSWFunctions and LocalDeviceManagers representing
sensors and actuators and interfacing functions
|
Steps
Assign functionality
Each Function of the FAA is marked as destined for either being implemented as
software or hardware.
|
Assess assignment
Make a rough and informal consequence analysis of the feasibility of the HW/SW
assignment from both implementation and performance points of view.
|
|
|