Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M MTSA
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lafhis
  • MTSA
  • Wiki
    • Enduser
  • Modal Transition Systems

Modal Transition Systems · Changes

Page history
Update Modal Transition Systems authored Sep 26, 2026 by Sebastian Uchitel's avatar Sebastian Uchitel
Hide whitespace changes
Inline Side-by-side
Showing with 43 additions and 1 deletion
+43 -1
  • enduser/Modal-Transition-Systems.md enduser/Modal-Transition-Systems.md +43 -1
  • No files found.
enduser/Modal-Transition-Systems.md
View page @ c4632ef8
# Modal Transition Systems
The tool, as its name suggests support model checking and synthesis using modal transition systems. This functionality has not received attention in many years and may not be fully functional.
### component
The `component` keyword is intended to build a Modal Transition System (MTS)
*component* by projecting a composed system onto a given interface alphabet
(the actions listed after `|`), abstracting away the rest of the behaviour:
```
component ||NAME = (P || Q) | {interfaceActions}.
```
The `optimistic` and `pessimistic` keywords are MTS refinement operations, applied as
a prefix to a modal model:
* `optimistic` — the *optimistic* model: the maximal implementation, treating *maybe* transitions as present, e.g. `optimistic ||M = (...)`.
* `pessimistic` — the dual *pessimistic* model: the minimal implementation, dropping *maybe* transitions and keeping only required behaviour.
Other Modal Transition System and scenario keywords, not yet documented:
* `restricts` — scenario restriction
* `instances` — scenario instances
* `condition` — a named Fluent Propositional Logic predicate used inside triggered scenarios (`eTS`/`uTS`), referenced by the pre/main charts.
* `prechart` — prechart in a triggered scenario
* `mainchart` — main chart in a triggered scenario
* `eTS` — existentially triggered scenario
* `uTS` — universally triggered scenario
* `starenv` — star environment
* `buchi` — Büchi automaton specification
### Abstract
The `abstract` keyword builds a Modal Transition System (MTS) from the LTS resulting
from compiling an FSP process, adding a *may* transition for every label that is
disabled (not enabled) in a state.
The keyword can be used with sequential and composite processes.
```
abstract LOWER = (a -> b -> LOWER).
LOWER = (a -> b -> LOWER).
abstract ||PL = (LOWER)\{a}.
```
Modal transition systems (MTS) can be modelled by using a question mark (`?`) on event labels to indicate may-transitions (transitions that may or may not be present in an implementation).
......@@ -18,4 +60,4 @@ abstract ||COMP = (B).
```
---
[← End User](End-User)
[← End User](End-User)
\ No newline at end of file
Clone repository
  • Developer
  • End User
  • devs
    • outputmessages
  • enduser
    • DCS
    • Discrete Event Controller Synthesis
    • Hello World
    • MTSA Syntax
    • Modal Transition Systems
  • Home