Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

The concept of “allocation” requires flexibility suitable for abstract system specification, rather than a particular constrained method of system or software design.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Source
OMG Systems Modeling Language (SysML) 1.6
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
SysML keywords
Allocate
Allocation is the term used by systems engineers to denote the organized cross-association (mapping) of elements within the various structures or hierarchies of a user model.
Full quote
The concept of “allocation” requires flexibility suitable for abstract system specification, rather than a particular constrained method of system or software design.
Next snippet
System modelers often associate various elements in a user model in abstract, preliminary, and sometimes tentative ways. Allocations can be used early in the design as a precursor to more detailed rigorous specifications and implementations.
Related snippets
Systems engineers have frequent need to allocate structural model elements (e.g., blocks, parts, or connectors) to other structural elements.
Allocate is a dependency based on UML::Abstraction. It is a mechanism for associating elements of different types, or in different hierarchies, at an abstract level. Allocate is used for assessing user model consistency and directing future design ...
It is expected that an «allocate» relationship between model elements is a precursor to a more concrete relationship between the elements, their properties, operations, attributes, or sub-classes.
Allocate is a stereotype of a UML4SysML::Abstraction that is permissible between any two NamedElements. It is depicted as a dependency with the "allocate" keyword attached to it.
Allocate is directional in that one NamedElement is the "from" end (no arrow), and one NamedElement is the "to" end (the end with the arrow).
The Allocate stereotype specializes DirectedRelationshipPropertyPath to enable allocations to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets.
Allocation is the term used by systems engineers to denote the organized cross-association (mapping) of elements within the various structures or hierarchies of a user model.
Related snippets (backlinks)
The allocation relationship can provide an effective means for navigating the model by establishing cross relationships, and ensuring the various parts of the model are properly integrated.
... does not try to limit the use of the term “allocation,” but provides a basic capability to support allocation in the broadest sense. It does include some specific subclasses of allocation for allocating behavior, structure, and flows.
A typical example is the allocation of activities to blocks (e.g., functions to components)
Visit also
Visit also (backlinks)