HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study Jump to first slide Figure 14.7 Composite State with two States Sections
UML: Cameo Simulation Toolkit 19SP3: GOTCHA: CreateObjectAction ignores an Artifact as 'classifier' even though Artifact is a Classifier
GOTCHA: UML/SysML: Cameo Simulation Toolkit 19SP3: A [true] or [false] guard on an ActivityEdge MUST be a LiteralBoolean, not just characters typed in, or the evaluation may give unexpected or ill-defined results
UML/SysML: Cameo Simulation Toolkit 19SP3: A parent Activity with a DecisionNode that uses a Activity as a decisionInput Behavior terminates immediately after the decisionInput terminates (but OpaqueBehavior works)
UML/SysML: Cameo Simulation Toolkit 19SP3: GOTCHA: Will not evaluate a guard using a token from a decisionInputFlow UNLESS a decisionInput Behaviour is explicitly defined (but Alf does)
Sample problems and example diagrams in graphical language specifications are NOT necessarily indications of how one should model on a real-world project! They often just serve to demonstrate a particular aspect of the specified language.
MBSE: Languages and tools: NoMagic/Dassault vs SysML Gallery Tutorial MINI TRAIL: Some recommended tools for getting started with Model-Based Systems Engineering with SysML and simulation with Modelica and/or Simulink Section
MINI TRAIL: Some recommended tools for getting started with Model-Based Systems Engineering with SysML and simulation with Modelica and/or Simulink Jump to first slide MBSE: Languages and tools: NoMagic/Dassault vs SysML Sections
Not every task in Activity Diagrams is well-suited to graphical modelling; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf)
Not every task in Activity Diagrams is well-suited to graphical modelling and LoopNode and ConditionalNode are notoriously fiddly to setup; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf)
A quick look at accessing an Operation on a Transition or ActivityEdge guard with Alf vs ALH Gallery Tutorial HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study Section Slide kind UML Activity Diagram
StateMachine for the Dialer class Gallery Tutorial HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study Section Slide kind UML StateMachine Diagram
StateMachine diagram for comparing action language access to an operation for a guard Gallery Tutorial HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit Section Slide kind UML StateMachine Diagram
Class diagram for comparing action language access to an operation for a guard Gallery Tutorial HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit Section Slide kind UML Class Diagram
HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit Jump to first slide Class diagram for comparing action language access to an operation for a guard Sections
Alf zone Keywords Keywords Alf fUML Foundational UML execution simulation UML SysML Alf - the Action Language for Foundation UML - is a UML-friendly textual "surface language" intended for use together with fUML. Useful for those tasks in Activity and StateMachine diagrams that don't lend themselves to graphical modelling.
