Home › OMG zone › SysML1.2 specification overview using hyperlinked SysML Parsing Analysis [ARCHIVAL] › 15 Allocations › 15.3 UML Extensions › 15.3.2 Stereotypes ›

15.3.2.1 Allocate(from Allocations)

[stereotype] Submitted by webel on Sun, 11/07/2010 - 19:05
This page contains, describes, or reports suspected ERROR(S) in content, a specification, or a tool !
Source
Source: UML2.3 superstructure: formal/2010-05-05 (as PDF)
Object Management Group™ (OMG™)
formal/2010-05-05 (as PDF)
Package(s)
SysML Allocations
Extends metaclass(es)
7.3.1 Abstraction (from Dependencies)
Description
  1. Allocate is a dependency based on UML::abstraction.
  2. It is a mechanism for associating elements of different types, or in different hierarchies, at an abstract level.
  3. Allocate is used for assessing user model consistency and directing future design activity.
  4. 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.
  5. Allocate is a stereotype of a UML4SysML::Abstraction which is permissible between any two NamedElements.
  6. It is depicted as a dependency with the “allocate” keyword attached to it.
  7. Allocate is directional in that one NamedElement is the “from” end (no arrow), and at least one NamedElement is the “to” end (the end with the arrow).
  8. The following paragraphs describe types of allocation that are typical in systems engineering.
  9. Behavior allocation relates to the systems engineering concept segregating form from function. [..]
  10. Flow allocation specifically maps flows in functional system representations to flows in structural system representations.
  11. Flow between activities can either be control or object flow. [..]
  12. Note that allocation of ObjectFlow to Connector is an Allocation of Usage, and does NOT imply any relation between any defining Blocks of ObjectFlows and any defining associations of connectors.
  13. The figures in the Usage Examples illustrate an available mechanism for relating the objectNode from an activity diagram to the itemFlow on an internal block diagram.
  14. ItemFlow is discussed in Chapter 9, Ports and Flows.
  15. Pin to Port allocation is not addressed in this release of SysML.
  16. Structure allocation is associated with the concept of separate “logical” and “physical” representations of a system. [..]
Constraints
  1. A single «allocate» dependency shall have only one client (from), but may have one or many suppliers (to).
  2. If subtypes of the «allocate» dependency are introduced to represent more specialized forms of allocation, then they should have constraints applied to supplier and client as appropriate.