Task: Specify Hardware Component Details |
| |
 |
This task decomposes a top-level hardware component, and specifies it in more detail. |
|
Purpose
The purpose of this task is to specify the internals of a hardware component of the
hardware design architecture.
|
Relationships
Roles | Primary:
| Additional:
| Assisting:
|
Inputs | Mandatory:
| Optional:
| External:
|
Outputs |
|
Main Description
The top-level structure that already exists in the HDA is further refined in this task. A hardware component is further
detailed with an internal structure. The internal structure could for instance represent on and off-chip peripherals such
as AD converters and amplifiers. If necessary, the task also includes building simulation models, or other behavioural
models, of the component.
During the detailing of the hardware component, new information may emerge that calls for a change in the interfaces of the
component. For that reason, it is allowed to modify also the interfaces of the component, although it is not of primary
concern for this task. This requires, however, close collaboration with the HDA architect.
In the decomposition and modeling process, certain assumptions and constraints on the environment and possibly also on
functions to be allocated on the hardware component, may be derived. This is also to be documented in a separate work
product.
|
Steps
Specify hardware component
This step further details the hardware component with an internal structure. The internal structure could for instance
represent on and off-chip peripherals such as AD converters and amplifiers. |
Modify interfaces if necessary
This step may modify the interfaces specified by the top-level hardware architecture, if new needs or findings are
discovered during the detailed design of the hardware component. However, this requires close cooperation with the HDA
architect. |
Identify design constraints
Assumptions and constraints that have been derived during the detailing process are identified and documented in a separate
work product. |
|
Properties
Multiple Occurrences |  |
Event Driven |  |
Ongoing |  |
Optional |  |
Planned |  |
Repeatable |  |
|