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

SysMLv2: Webel: The challenge of the twice-performed action (or twice exhibited state) when combining "logical" functional analysis breakdown using performed actions with allocations to "physical" components

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
CAVEAT
COMPLICATION
EXPLANATION
MODELLING
Policy level
INFORMATIVE
Specification keywords
SysMLv2
SysMLv2 keywords
AllocationDefinition
AllocationUsage
allocation
allocation definition
allocation usage
performed action
exhibited state
«perform action»
«perform»
«exhibit state»
Keywords
Relates to:
SysMLv2: Webel Best Practice: Prefer use performed actions and exhibited states as the primary mechanism for "logical" layer/zone systems engineering functional analysis breakdown (not SysMLv2 allocations).
The challenge (concern) is illustrated by the following SysMLv2 PILOT GitHub sample (see also the other Relates to slides linked below):
38. Allocation: Allocation Usage Example.sysml [EXPANDED DISCUSSION]

The rationale behind "twice-performed" actions seems to be:

SysMLv2: A performed action may be a skeleton or stub for performance by another elaborating action
Relates to
38. Allocation: Allocation Definition Example.sysml
38. Allocation: Allocation Usage Example.sysml [EXPANDED DISCUSSION]
12-Dependency Relationships: 12b-Allocation-1.sysml
Related notes
[MODELLING, PATTERN, TIP]{RECOMMENDED} SysMLv2: Webel Best Practice: An allocation definition should be of a specific "nature" (possibly related to a formal systems engineering methodology, and optionally with the "nature" further distilled using custom Metadata).
[MODELLING, PATTERN, TIP]{RECOMMENDED} SysMLv2: Webel Best Practice: If you have as many allocation definitions as allocation usages in your final model you might not be using them effectively!
[MODELLING, PATTERN, TIP]{STRONG} SysMLv2: Webel Best Practice: Prefer use performed actions and exhibited states as the primary mechanism for "logical" layer/zone systems engineering functional analysis breakdown (not SysMLv2 allocations).
[ANTI-PATTERN, MODELLING, TIP]{INFORMATIVE} Webel Best Practice: “There is nothing worse than a sharp image of a fuzzy concept.” (Ansell Adams, photographer)
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)