[rtems-central commit] glossary: Restrict "scenario" definition

Sebastian Huber sebh at rtems.org
Tue Dec 19 07:28:52 UTC 2023


Module:    rtems-central
Branch:    master
Commit:    270fa8d65bb7d70ab90d16fdc0744edac877a7d4
Changeset: http://git.rtems.org/rtems-central/commit/?id=270fa8d65bb7d70ab90d16fdc0744edac877a7d4

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Tue Dec 19 08:18:06 2023 +0100

glossary: Restrict "scenario" definition

---

 spec-glossary/glossary/scenario.yml | 8 ++++----
 1 file 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



More information about the vc mailing list