Allocation: An Allocation Dependency arrow (dashed-line with open-arrow notation and keyword = «allocate») associates or maps model elements of different types, or in different hierarchies. Allocate Dependency patterns are generally useful for improving model architecture integrity (a.k.a., well-formedness) and consistency. SysML predefines the following Allocation Dependencies:
Users are encourage to define their own Allocation Dependencies as needed. (See Best Practice Patterns below for examples of user-defined Allocations.)
Allocation Table: An Allocation Table is a tabular (matrix) notation for Allocation relationships, but the SysML standard does not prescribe a particular format for these so they tend to be vendor specific.
The purpose of an Allocation Table is to define relationship matrices within and across diagram types to improve model architectural integrity (well-formedness) and consistency.
Diagram Name | Diagram Type | UML 2 Analog | SDLC Usage | Essential AGILE SYSML? |
Dynamic Sim † |
Math Sim ‡ |
Auto Code Gen |
Rigor | Semi | Informal |
---|---|---|---|---|---|---|---|---|---|---|
Allocation Table | N/A [Relationship Matrix] |
N/A | All SDLC phases |
BEST PRACTICE PATTERNS | ANTI-PATTERNS |
---|---|
* Use Allocation Tables to define system architecture integrity (well-formedness rules) for System Analysis and System Design. | * Rely on the anemic subset of Allcoation Tables defined by the OMG SysML specification and SysML tool vendors. |
* Use Allocation Tables to define system Verification & Validation (V&V) relationships on both sides of the System V-Model. |
Made in RapidWeaver