UML/SysML with TRAKMetamodel
The simplified metamodel that described how part of the UML / SysML metamodel is linked to the TRAK metamodel is provided below.
Simplified Metamodel Linking UML/SysML with TRAK
TRAK Resources (Job, Organisation, Physical, Role, Software and System) as Classes / SysML Blocks provide the basis to link States and Use Cases:-
- Resources are defined as the subject of a Use Case - UseCase applies to Resource
- Resources are defined as collaborators or participants in a Use Case - UseCase defines collaborator as Resource
- these same Resources may exhibit one or more States - Resource exhibits State
Use Cases are typically created to help understand and refine requirements - hence the right hand side:-
- UseCase refines Contract
- UseCase refines (atomic) Requirement
- UseCase refines Standard
... where a Standard represents a normative artefact.
States may be triggered by:-
- A Resource Interaction between a pair of Resources carrying one or more Interaction Elements. See also TRAK SV-02 Solution Resource Interaction architecture view.
- A Function (performed by a Resource). See also TRAK SV-04 Solution Function architecture view.
- An Event (which itself may be caused by the combination or two or more Events, a Resource, a Function, a Resource Interaction or Interaction Element). See also TRAK SV-11 Solution Event Causes architecture view.