Select model: .
Select object: .
Doc.
Open settings:
display
:
,
semantics- show hyperlinks as normal text
- show port objects
- Displayed objects selection
- Strucural diagram
- hide objects
- show actors as objects (e.g., to see property values and event pool contents)
- show event pool and ether messages on objects
- hide operations
- hide methods
- show connector end names when available
- show class diagram
- show methods as activities
- State diagram
- hide state machines
- hide frame with object name around state machines
- show transitions to same state as internal (warning: this may be ambiguous, for instance if there are time triggers ("after") or entry or exit actions)
- display transition labels as narrowly as possible
- show explicit state machines (work in progress: notably no support for 'do', 'when', non-trivial history)
- Comments
- enable comments
- place class & object comments to the
- place operation comments to the
- place property comments to the
- place state comments to the
- place transition state comments to the
- History/trace interaction diagram
- hide state invariants
- show pseudostates as state invariants
- hide set/assignment pseudo-messages
- show transition notes, with values of watch expressions after the transition, and previous configuration in tooltip
:
,
remote engine- automatically fire initial transitions
- automatically fire outgoing transition of choice (only when exploring as of now)
- operations (or communication diagram messages) are not automatically received
- consider all guards as true
- transitions only fireable if trigger matches a sent event, and operations only callable if they match a sent event
- cap the number of messages in the Ether to one per distinct trigger (state space will likely be unbounded if unset)
- use event pools for messages sent to specific objects, instead of using the ether
- only consider the first matching event of each event pool
- treat undefined values as symbolic values instead of as 0 or false
- consider that the system is reactive (i.e., faster than the environment): all its fireable transitions (except those with an after trigger) must be fired before any environment transition
- allow synchronous communication
- enable time tracking with a Difference Bound Matrix (DBM)
:
,
analysis tools- Connect to the remote engine:
- log messages exchanged with EMI in console
- animate when using the EMI engine
- Examples of compatible remote engines:
- the EMI-UML model interpreter (more information)
- controllable generated code
- Connected to EMI model "" (disconnect)
:
,
export- Watch expressions
(click on name or expression to edit, add an expression, or clear name to delete):
Name Expression Current value - LTL properties
(click name or expression to edit, add a property, or clear name to delete, show/hide automata):
Remark: atomic propositions in LTL properties can either be watch expression names, or inline expressions surrounded by pipe characters ('|').Name Expression - In-browser analysis
- No output yet
- Commands
- Reset and explore state space
- Reset and explore state space until
- Explore state space from current state until
-
Synchronize with interaction
- Check that the model can reproduce the interaction
- enable observers.
- breadth-first instead of depth-first exploration.
- show heat map if available. Remarks: 1) the model must be explored at least partially first, and 2) transitions from pseudostates (e.g., initial, choice) may be erroneously shown as not fired because some execution engines do not notify AnimUML.
- use watch expression value as configuration representation (leave blank to use actual configuration)
- use the z2mc analysis tool instead of the legacy AnimUML one
- evaluate breakpoints on execution steps (source configuration, transition, target configuration) instead of on a single configuration
- STOP
- Connect to external analysis tool:
- Wait milliseconds before sending configuration or fireable transitions
- animate when driven by analysis tool
- log messages exchanged with analysis tool in console
- keep exchanged messages in sequence & timing diagrams when setting configurations (warning: may make these diagrams inconsistent)
- Disconnect from analysis tool
:
- model without history
- download as an HTML file for easy edition
- open as a sharable AnimUML link
- download as a pretty-printed JSON file
- model with history
- download as an HTML file for easy edition
- open as a sharable AnimUML link
- download as a pretty-printed JSON file
- download as a tUML file
- open main or interaction diagram as a PlantUML textual diagram (or download as SVG if not a PlantUML diagram)
- with annotations
- for animation
,
generate
.:
- download as a C code tgz file
- download as a ceptre source file
Edit
.