summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2023-12-19 08:18:06 +0100
committerSebastian Huber <sebastian.huber@embedded-brains.de>2023-12-19 08:18:25 +0100
commit270fa8d65bb7d70ab90d16fdc0744edac877a7d4 (patch)
treeea1591bf49ac4038b8e6eb0b2270c39890a69926
parentglossary: Add formal methods terms (diff)
downloadrtems-central-270fa8d65bb7d70ab90d16fdc0744edac877a7d4.tar.bz2
glossary: Restrict "scenario" definition
-rw-r--r--spec-glossary/glossary/scenario.yml8
1 files changed, 4 insertions, 4 deletions
diff --git a/spec-glossary/glossary/scenario.yml b/spec-glossary/glossary/scenario.yml
index 6db3cd86..47008b6a 100644
--- a/spec-glossary/glossary/scenario.yml
+++ b/spec-glossary/glossary/scenario.yml
@@ -8,8 +8,8 @@ links:
uid: ../glossary-general
term: scenario
text: |
- In a setting that involves many concurrent tasks that interleave in arbitrary
- ways, a scenario describes a single specific possible interleaving. One
- interpretation of the behaviour of a concurrent system is the set of all its
- scenarios.
+ In the context of formal verification, in a setting that involves many
+ concurrent tasks that interleave in arbitrary ways, a scenario describes a
+ single specific possible interleaving. One interpretation of the behaviour
+ of a concurrent system is the set of all its scenarios.
type: glossary