Glossary · System coordination, integration and orchestration
Allocation relationship
Also known as: allocate relationship, allocation (SysML)
German: Allokationsbeziehung
In SysML, an allocation relationship is a dependency that assigns one model element to another across different structures or levels, for example a function or activity to the block that performs it, or a logical element to a physical one.
- System integration
- Standards
In one sentence
In SysML, an allocation relationship assigns a function, activity or logical element to the structure that realizes it, such as a block or component.
Example
In the SysML model of a palletizer, the activity “Detect pallet position” is allocated to the block “Vision sensor,” and the block “Palletizing logic” is allocated to the cell PLC.
How it applies
- Systems engineering: Allocations connect the “what” of a Functional architecture with the “how” of a Logical architecture or physical architecture. They make it possible to ask which component realizes a function and which functions a component carries.
- Change management: When a component changes, its allocations show which functions and requirements are affected, which feeds impact analysis.
- Documentation: Allocations are a good source for generating component descriptions and function-to-module tables in technical documentation. Keep them consistent with the model rather than maintaining a separate table by hand.
Allocation vs. trace link
An allocation is a design decision: this element is realized by that element. A general Trace link records any dependency, for example between a requirement and a test case, without saying that one element implements the other.