diff --git a/models/Application_examples/Authentication.mp b/models/Application_examples/Authentication.mp
index 275b59a8224826db5277d051d43b404b175a006b..02b85bdcc35b48339e45fd4ec9ac42bd1883fb40 100644
--- a/models/Application_examples/Authentication.mp
+++ b/models/Application_examples/Authentication.mp
@@ -15,9 +15,12 @@ constraints.
References:
-Search terms:
+Search terms: authentication system behavior; coordination, event; ENSURE condition; event sharing
-Instructions:
+Instructions: Run for Scopes 1, 2, and 3.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 4 traces in less than 1 sec.
+ Scope 3: 6 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Autonomous_Car.mp b/models/Application_examples/Autonomous_Car.mp
index 05984df4616f48f67bcdd77a604539e964b1c879..607baa68167386ce9c2a6e44cdf70340821ee9d1 100644
--- a/models/Application_examples/Autonomous_Car.mp
+++ b/models/Application_examples/Autonomous_Car.mp
@@ -10,9 +10,10 @@ Created by G. Kaminski, November 2015
References:
-Search terms:
+Search terms: autonomous car behavior; autonomous; failure mode analysis; coordination, event
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 8 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Beginner_Use_of_MP.mp b/models/Application_examples/Beginner_Use_of_MP.mp
index 6cd3631130538bf7ee38d5fadfee5fb1f011f717..8216174b28c262015caf7f9ea40e85b666fd65a5 100644
--- a/models/Application_examples/Beginner_Use_of_MP.mp
+++ b/models/Application_examples/Beginner_Use_of_MP.mp
@@ -20,18 +20,18 @@ ROOT A: B C; A is a root event that includes events B followed by C
(* B *) iterate B zero or more times
{ B , C } B and C are unordered
-Experiment with this model by running it at scopes 1, 2, 3, 4 and 5.
-You may also make changes to this model and run it with your changes.
+References:
+
+Search terms: beginner use of MP; use of MP-Firebird; trace annotation; SAY statement
+
+Instructions: Run for Scopes 1 and up. You may also make changes to this model and run it with your changes.
Save your model using the EXPORT button ("Code" exports a .mp text file
of the contents of the text editor, and "Code and Event Trace" exports
the contents of the text editor plus the graphs and any changes you made
to the graph element positions.
-
-References:
-
-Search terms:
-
-Instructions:
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 3 traces in less than 1 sec.
+ Scope 3: 4 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/CargoScreening.mp b/models/Application_examples/CargoScreening.mp
index 5d18b3a67599b5c720fc47985a4a439a633f8692..44f90fa6659df1e3d5a5ea7a8f6907a4f3c284e3 100644
--- a/models/Application_examples/CargoScreening.mp
+++ b/models/Application_examples/CargoScreening.mp
@@ -26,9 +26,10 @@ MP-Firebird may be used at least for the following:
References:
-Search terms:
+Search terms: cargo screening process behavior; graph, flowchart
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 6 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Commercial_Flight b/models/Application_examples/Commercial_Flight
index b609d0de24bfe17e4dc19c6a54c3b2083e446ccb..8e39c3ea6e2b4d9a7fc2138b41f229ee78ba667b 100644
--- a/models/Application_examples/Commercial_Flight
+++ b/models/Application_examples/Commercial_Flight
@@ -13,9 +13,10 @@ COORDINATE statements were implemented in the early MP tools.
References:
-Search terms:
+Search terms: commercial flight behavior; event sharing; coordination, event
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 2 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Cycle_Pattern.mp b/models/Application_examples/Cycle_Pattern.mp
index aaa8d596c91823f85e0315957c39814bb2c97ebe..ae4c30353d60e856ec5dadc3a7c93eb94e1bb70a 100644
--- a/models/Application_examples/Cycle_Pattern.mp
+++ b/models/Application_examples/Cycle_Pattern.mp
@@ -18,16 +18,15 @@ and "under", "increase" and "decrease", etc., or
discinyms (discipline-specific synonyms) as they
may appear in the preferred domain taxonomy.
-Run the model for scopes 2, and 3 and inspect
-the different possible patterns for Cycle.
-Running at scope 1 will generate zero traces because
-of the ENSURE constraint on line 29.
-
References:
-Search terms:
+Search terms: cycle pattern behavior; ENSURE condition; SAY statement; isomorphism
-Instructions:
+Instructions: Run for Scope 1. This will generate zero traces because
+of the ENSURE constraint on line 29. Then run for Scopes 2 and 3.
+ Scope 1: 0 traces in less than 1 sec.
+ Scope 2: 40 traces in less than 1 sec.
+ Scope 3: 2952 traces in approx. 2.9 sec.
==========================================================*/
diff --git a/models/Application_examples/Dining_Philosophers.mp b/models/Application_examples/Dining_Philosophers.mp
index c467e09c694067ae8707c7cf38b2045eebaf2992..5ecbf7168275e7aa69a0f6300d755f119185317b 100644
--- a/models/Application_examples/Dining_Philosophers.mp
+++ b/models/Application_examples/Dining_Philosophers.mp
@@ -30,17 +30,17 @@ behaviors, but does not provide implementation details.
Since MP supports automated use case extraction, this model may be used
as a source of test cases for testing the implementation.
-scope 1 yields zero traces, because Philosopher cannot eat with a single fork.
-scope 2 yields 2 traces in approx. 0.01 sec.
-scope 3 yields 6 traces in approx. 0.05 sec.
-scope 4 yields 14 traces in approx. 0.44 sec.
-scope 5 yields 30 traces in approx. 1.6 sec.
-
References:
-Search terms:
+Search terms: dining philosophers behavior; ring topology behavior; event reshuffling; BUILD block; isomorphism
-Instructions:
+Instructions: Run for Scope 1. This will generate zero traces because
+a philosopher cannot eat with a single fork. Then run for Scopes 2 and up.
+ Scope 1: 0 traces in less than 1 sec.
+ Scope 2: 2 traces in less than 1 sec.
+ Scope 3: 6 traces in less than 1 sec.
+ Scope 4: 14 traces in less than 1 sec.
+ Scope 5: 30 traces in approx. 1.4 sec.
==========================================================*/
diff --git a/models/Application_examples/Elevator.mp b/models/Application_examples/Elevator.mp
index 6f85993589c4dfe6618a301f67e522a4b74fe2a5..25ca511112f11e5cc9353d9c47034a250eb78a36 100644
--- a/models/Application_examples/Elevator.mp
+++ b/models/Application_examples/Elevator.mp
@@ -21,9 +21,10 @@ in the case of this model,
References:
-Search terms:
+Search terms: elevator behavior; event sharing; coordination, event
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 3 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/FindAdvisor.mp b/models/Application_examples/FindAdvisor.mp
index b8d184d544992cf0599a872e97c66fffcadb41b0..b49f73dee21bc0aa2f25112497288e2e658e138f 100644
--- a/models/Application_examples/FindAdvisor.mp
+++ b/models/Application_examples/FindAdvisor.mp
@@ -18,17 +18,14 @@ Because the same modeling approach can be used for human systems and technologic
it becomes possible to have integrated behavior models containing both humans and
technology to study the possible interactions among them.
-Run for scope 1 (there is no iteration in this example, so increaasing the scope will not
-produce more scenarios).
-
-The "Sequence" or "Swim Lanes" layouts are the most appropriate for browsing traces here.
-The "Sequence" mode yields views very similar to the UML or SysML Sequence Diagrams.
-
References:
-Search terms:
+Search terms: finding advisor; human interactions modeling; human systems behavior
-Instructions:
+Instructions: Run for Scope 1 (there is no iteration in this example, so increasing the scope will not
+produce more scenarios). "Sequence" mode yields views very similar to the UML or SysML
+Sequence Diagrams.
+ Scope 1: 3 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/First_Responder.mp b/models/Application_examples/First_Responder.mp
index 53a2fbb62539c0933b17b1b945dfd51ce828df8e..bc745159165a614578fe84e8a11341f4fdb35c14 100644
--- a/models/Application_examples/First_Responder.mp
+++ b/models/Application_examples/First_Responder.mp
@@ -10,16 +10,15 @@ Bystander.
Create by J. Bryant, May 2016
-The model was developed to compare response times, but unexpected
-scenarios emerged that was previously not considered. Trace 6 and others
-show a double administration of Narcan by both the bystander and the first
-responder.
-
References:
-Search terms:
+Search terms: first responder behavior; bystander behavior; unexpected emergent behavior
-Instructions:
+Instructions: Run for Scope 1. The model was developed to compare response times, but unexpected
+scenarios emerged that were previously not considered. Trace 6 and others
+show a double administration of Narcan by both the bystander and the first
+responder.
+ Scope 1: 8 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Knapsack_Weight_Limit.mp b/models/Application_examples/Knapsack_Weight_Limit.mp
index 9c09b79c969200e3887094f60fb8a32ad1f76871..8e91ccd7bb703b51b5dd1ad1124c17e1f6e49c2c 100644
--- a/models/Application_examples/Knapsack_Weight_Limit.mp
+++ b/models/Application_examples/Knapsack_Weight_Limit.mp
@@ -16,14 +16,17 @@ Example 38 Knapsack
for all optimal solutions within the given scope
(certainly not the optimal performance, but is acceptable for relatively
small N,in particular, it stabilizes at scope 4).
-
- Run for scope 1 and up to 5
References:
-Search terms:
+Search terms: event attribute, number; optimization, weight; BUILD block; WITHIN command; report, global
-Instructions:
+Instructions: Run for Scopes 1 and up.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 4 traces in less than 1 sec.
+ Scope 3: 6 traces in less than 1 sec.
+ Scope 4: 7 traces in less than 1 sec.
+ Scope 5: 7 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/MP_Architecture_Specification.mp b/models/Application_examples/MP_Architecture_Specification.mp
index 8f68fed3e7ae8609d3b636096cf43741e494f232..0d7ddfc6c379cba2ef1776720b62b6c5a62b89c6 100644
--- a/models/Application_examples/MP_Architecture_Specification.mp
+++ b/models/Application_examples/MP_Architecture_Specification.mp
@@ -5,15 +5,15 @@ Purpose:
Description:
Example 28
- MP compiler/trace generator architecture model
-
- run for scope 1 or more
+ MP compiler/trace generator architecture model
References:
-Search terms:
+Search terms: architecture; trace annotation; compiler behavior; parser behavior; graph, component diagram; report, global; isomorphism
-Instructions:
+Instructions: Run for Scopes 1 and 2.
+ Scope 1: 16 traces in less than 1 sec.
+ Scope 2: 272 traces in approx. 26 sec.
==========================================================*/
diff --git a/models/Application_examples/Manufacturing_Process.mp b/models/Application_examples/Manufacturing_Process.mp
index 83a252cb58b88360ca422e1d21e8bb376c5cfacd..f4070934e8171f61f6ff4a1fea205db793e3dfb0 100644
--- a/models/Application_examples/Manufacturing_Process.mp
+++ b/models/Application_examples/Manufacturing_Process.mp
@@ -13,9 +13,10 @@ August 2014
References:
-Search terms:
+Search terms: manufacturing process behavior; manufacturing system; event sharing; probability analysis
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 8 traces in approx. 1.4 min.
==========================================================*/
diff --git a/models/Application_examples/Martian_Lander.mp b/models/Application_examples/Martian_Lander.mp
index 8ead385cd2639e4624b7ffa839217b85165cb390..4b9aa27ecc20ec03d138fe20c2b0374764bd4edc 100644
--- a/models/Application_examples/Martian_Lander.mp
+++ b/models/Application_examples/Martian_Lander.mp
@@ -57,13 +57,16 @@ IALT 20
CKDT 10
RRM 10
- run for scope 1 and up.
-
References:
-Search terms:
+Search terms: Martian Lander system; landing system behavior; event attribute, timing; trace annotation; table; graph, Gantt chart; graph, bar chart
-Instructions:
+Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 16 traces in less than 1 sec.
+ Scope 3: 45 traces in less than 1 sec.
+ Scope 4: 96 traces in approx. 1.2 sec.
+ Scope 5: 170 traces in approx. 2.8 sec.
==========================================================*/
diff --git a/models/Application_examples/Prisoners_Dilemma.mp b/models/Application_examples/Prisoners_Dilemma.mp
index ee66e9f3e515c57753d3c49a9ccde130ae570428..6287c62bad9c7f34ae608f404f0087757f42bbbc 100644
--- a/models/Application_examples/Prisoners_Dilemma.mp
+++ b/models/Application_examples/Prisoners_Dilemma.mp
@@ -62,9 +62,10 @@ The total payoff is computed from the assignments above and then subtracting 2.
References:
-Search terms:
+Search terms: prisoners dilemma behavior; matrix game behavior; event attribute, number; BUILD block; SAY statement; isomorphism
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 4 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Railroad_Crossing_Safety.mp b/models/Application_examples/Railroad_Crossing_Safety.mp
index 0433f8a9c22d3ef3c0fade4663b6749390cad574..b9b1050174601b2616cb68b61f6cb29269372652 100644
--- a/models/Application_examples/Railroad_Crossing_Safety.mp
+++ b/models/Application_examples/Railroad_Crossing_Safety.mp
@@ -15,9 +15,12 @@ then gate must be down.
References:
-Search terms:
+Search terms: railroad crossing behavior; safety requirement; failure mode; event attribute, timing
-Instructions:
+Instructions: Run for Scopes 1 and up.
+ Scope 1: 1 trace in less than 1 sec.
+ Scope 2: 2 traces in less than 1 sec.
+ Scope 3: 3 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Replay_Attack.mp b/models/Application_examples/Replay_Attack.mp
index 35f1450f850eeff9c2cb5dd9058a2be25779e597..60f144da00849546dc0b9ae08c53b1696134f564 100644
--- a/models/Application_examples/Replay_Attack.mp
+++ b/models/Application_examples/Replay_Attack.mp
@@ -8,13 +8,14 @@ Example 41. The description of Replay Attack
is available at
https://en.wikipedia.org/wiki/Replay_attack
- run scope up to 5
-
References:
-Search terms:
+Search terms: replay attack behavior; message eavesdropping; coordination, event
-Instructions:
+Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 6 traces in less than 1 sec.
+ Scope 3: 12 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Small_Package_Delivery.mp b/models/Application_examples/Small_Package_Delivery.mp
index ef3fb30bb9e0b620630b58f4c262cace6fe484cd..846d70e44785644ddbbab03eb46b90baf2b2647d 100644
--- a/models/Application_examples/Small_Package_Delivery.mp
+++ b/models/Application_examples/Small_Package_Delivery.mp
@@ -28,20 +28,19 @@ raining? Hailing?"
Non-combatant Scenario 1 authored by N. Roberts (Engility)
MP model authored by K. Giammarco (NPS) and D. Shifflett (NPS)
-This model shows only two scenarios due to overloading constraints
-(constraints that suppress entire branches of execution that a user
-intended to permit).
-
-Removing everything except the SCHEMA definition and the Air_Vehicle
-root (line 36 and lines 114-128) and running that model subset, one can
-see 6 event traces, one of which is unexpected: the Air_Vehicle drops
-the payload with no vessel in sight (trace 6).
-
References:
-Search terms:
+Search terms: small package delivery; autonomous; ENSURE condition; Type 1 probability
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 2 traces in less than 1 sec.
+This model shows only two scenarios due to overloading constraints
+(constraints that suppress entire branches of execution that a user
+intended to permit). Commenting everything out except the SCHEMA definition and the Air_Vehicle
+root, and running that model subset at Scope 1, there are 6 event traces that can be seen.
+Two of these are unexpected. In Trace 5, there is no vessel in sight but the Air_Vehicle still
+drops the payload and the payload is on target. In Trace 6, there is no vessel in sight but
+the Air_Vehicle still drops the payload and the payload misses the target.
==========================================================*/
diff --git a/models/Application_examples/Spent_Fuel_Cooling_and_Cleanup.mp b/models/Application_examples/Spent_Fuel_Cooling_and_Cleanup.mp
index 6e599101a8b9f82c7778064d45abcc33147d6076..14ce1c115f97c4d771f90b0883004e1e575fc6ec 100644
--- a/models/Application_examples/Spent_Fuel_Cooling_and_Cleanup.mp
+++ b/models/Application_examples/Spent_Fuel_Cooling_and_Cleanup.mp
@@ -15,9 +15,10 @@ interactions among a spent nuclear fuel cooling pool and its environment.
References:
-Search terms:
+Search terms: nuclear fuel cooling behavior; coordination, event; heat exchanger; purification subsystem
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 6 traces in approx. 1.4 sec.
==========================================================*/
diff --git a/models/Application_examples/Spiral_Software_Process b/models/Application_examples/Spiral_Software_Process
index dd1bb9f323b3afd7092645f7a2429284dcc74149..43d1e1a4926e6a93877ff7dbbc691cac9a144cbb 100644
--- a/models/Application_examples/Spiral_Software_Process
+++ b/models/Application_examples/Spiral_Software_Process
@@ -11,13 +11,16 @@ Example 16, model of the spiral software process
are constrained to produce designs which are copies of the
communication structures of these organizations."
- run scope up to 5
-
References:
-Search terms:
+Search terms: spiral software process behavior; communication; architecture; event sharing
-Instructions:
+Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 7 traces in less than 1 sec.
+ Scope 3: 15 traces in approx. 1.6 sec.
+ Scope 4: 31 traces in approx. 10 sec.
+ Scope 5: 63 traces in approx. 1.0 min.
==========================================================*/
diff --git a/models/Application_examples/Surgery.mp b/models/Application_examples/Surgery.mp
index 8a0458e9b2d25285c6d1f889f2eca8441c3adbda..c18c2bfc46723ea7ca28a018330cd89380614c19 100644
--- a/models/Application_examples/Surgery.mp
+++ b/models/Application_examples/Surgery.mp
@@ -17,9 +17,10 @@ Naval Postgraduate School
References:
-Search terms:
+Search terms: surgery process; behavior of environment; decision pattern; failure mode
-Instructions:
+Instructions: Run for Scope 1.
+ Scope 1: 12 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Swarm_Search_and_Track.mp b/models/Application_examples/Swarm_Search_and_Track.mp
index f11628085cb0ceb62d31fd732591e474cbf4b656..71bdbc42266917d1592a7e5ad19eb1c4bac5dfdb 100644
--- a/models/Application_examples/Swarm_Search_and_Track.mp
+++ b/models/Application_examples/Swarm_Search_and_Track.mp
@@ -16,14 +16,14 @@ Noun-oriented events are actors (root events)
Verb-oriented events in sentence case are activities
Verb-oriented events in title case are states
-This model demonstrates the found unexpected behavior for
-object discovery after bingo fuel (trace 6)
-
References:
-Search terms:
+Search terms: swarm behavior; search and track; autonomous; behavior of environment; failure mode; failsafe behavior; emergent behavior; unexpected behavior
-Instructions:
+Instructions: Run for Scope 1.
+This model demonstrates the found unexpected behavior for
+object discovery after bingo fuel (trace 6).
+ Scope 1: 8 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Swarm_UAV.mp b/models/Application_examples/Swarm_UAV.mp
index 4e3e7b58246a67c018e2cdc3eacfc74303ab2c3e..a23e27906e90eb016ba02ad1ce5ff9b49687d9ae 100644
--- a/models/Application_examples/Swarm_UAV.mp
+++ b/models/Application_examples/Swarm_UAV.mp
@@ -9,17 +9,19 @@ Kristin Giammarco and Mikhail Auguston
11 February 2015 - Initial Model Started by KGiammarco
25 May 2015 - M.Auguston Merged several COORDINATE, SHARE ALL to speed up
trace generation
- 22 July 2015 - added a few more coordinate statements to capture dependencies
-
- This model demonstrates how to get several instances of the same actor (UAV)
- coordinated with external events (run for scopes 2 and 3 to see 2 and 3 UAVs,
- respectively).
+ 22 July 2015 - added a few more coordinate statements to capture dependencies
References:
-Search terms:
+Search terms: swarm behavior; autonomous; dependency tracking
-Instructions:
+Instructions: Run for Scopes 1, 2, and 3.
+This model demonstrates how to get several instances of the same actor (UAV)
+coordinated with external events (run for scopes 2 and 3 to see 2 and 3 UAVs,
+respectively).
+ Scope 1: 1 trace in less than 1 sec.
+ Scope 2: 3 traces in approx. 2.2 sec.
+ Scope 3: 6 traces in approx. 21 sec.
==========================================================*/
diff --git a/models/Application_examples/Turtles_in_the_Desert.mp b/models/Application_examples/Turtles_in_the_Desert.mp
index d8152e7c80f8fdee596a7fcaba1fa7ed2282ff14..b1f3dfef351df788a4baa3e9e98f5444eb3e6928 100644
--- a/models/Application_examples/Turtles_in_the_Desert.mp
+++ b/models/Application_examples/Turtles_in_the_Desert.mp
@@ -25,16 +25,13 @@ Don't try to construct a non-Euclidean geometry to
or all three of them. It becomes too complicated...."
Now it is time to use MP to obtain all possible scenarios for that story.
-
- Here it is. Run for scope 1.
- There are 13 possible scenarios, and none when all three
- are telling the truth.
References:
-Search terms:
+Search terms: lying turtles; ENSURE condition; BUILD block; SAY statement; MARK command; predicate logic
-Instructions:
+Instructions: Run for Scope 1. There are 13 possible scenarios, and none when all three are telling the truth.
+ Scope 1: 13 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/UAV_Ingress.mp b/models/Application_examples/UAV_Ingress.mp
index 08097bc880eda38767e36a702d7b919d1f360860..607ceee33fb44edd62b631f8e48b213090c92f9b 100644
--- a/models/Application_examples/UAV_Ingress.mp
+++ b/models/Application_examples/UAV_Ingress.mp
@@ -10,16 +10,16 @@ The following model specifies the ingress phase of the UAS HADR
reference mission. The ingress phase is preceded by the preflight
phase, and followed by the on-station phase.
-This model contains an unexpected behavior in which the UAV status
-is acceptable but the operator aborts the ingress (trace 2).
-
created by A. Constable May 2017
References:
-Search terms:
+Search terms: UAV ingress behavior; autonomous; emergent behavior; unexpected behavior
-Instructions:
+Instructions: Run for Scope 1.
+This model contains an unexpected behavior in which the UAV status
+is acceptable but the operator aborts the ingress (trace 2).
+ Scope 1: 2 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/UAV_OnStation.mp b/models/Application_examples/UAV_OnStation.mp
index 94555c400dc16e84c1c2eaed3be205f322e7f3ad..adbd1f7b80f6dcecc33247de5a58b6b40637f707 100644
--- a/models/Application_examples/UAV_OnStation.mp
+++ b/models/Application_examples/UAV_OnStation.mp
@@ -20,9 +20,11 @@ Paper available at https://ieeexplore.ieee.org/abstract/document/7994950
References:
-Search terms:
+Search terms: UAV OnStation behavior; autonomous; system of systems behavior; behavior of environment; SAY statement; MARK command; failure mode; failsafe behavior
-Instructions:
+Instructions: Run for Scopes 1 and 2.
+ Scope 1: 16 traces in less than 1 sec.
+ Scope 2: 36 traces in approx. 29 sec.
==========================================================*/
diff --git a/models/Application_examples/Unmanned_Spacecraft_Comms.mp b/models/Application_examples/Unmanned_Spacecraft_Comms.mp
index 82332ac90ce60f7c83f82b2472b02c0c2e0b9f0f..8205b46a18219b0a59736c02d0c8b9f60bc8f124 100644
--- a/models/Application_examples/Unmanned_Spacecraft_Comms.mp
+++ b/models/Application_examples/Unmanned_Spacecraft_Comms.mp
@@ -13,13 +13,15 @@ through a frame counter called the "Heartbeat". This model represents
the behavior of the Heartbeat while a Spacecraft is approaching
the ISS.
-Run for scope 1 and up.
-
References:
-Search terms:
+Search terms: unmanned spacecraft; Heartbeat; communication; autonomous
-Instructions:
+Instructions: Run for Scopes 1, 2, 3, and 4.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 20 traces in less than 1 sec.
+ Scope 3: 84 traces in approx. 3.0 sec.
+ Scope 4: 340 traces in approx. 1.2 min.
==========================================================*/
diff --git a/models/Application_examples/Web_Browser_Formal_Security.mp b/models/Application_examples/Web_Browser_Formal_Security.mp
index c64a6b35009af295940bdb7095e996701a004811..5e6e260755ba43a7074302ffbba780444f2e51a3 100644
--- a/models/Application_examples/Web_Browser_Formal_Security.mp
+++ b/models/Application_examples/Web_Browser_Formal_Security.mp
@@ -33,10 +33,6 @@ form the “backbone†of the model" (page 292)
This has motivated to design the MP behavior model of the web activities
in order to model the vulnerabilities explained in the papers above.
-
- run for scope 1: 3 traces, no counterexamples for Property1, in less than 0.001 sec.
- run for scope 2: 7 traces, 1 counterexample for Property1, in 0.13 sec.
- run for scope 3: 52 traces, 16 counterexamples for Property1, in 15 sec.
This example borrowed from Daniel Jackson's paper demonstrates
how MP can check whether Client's web query may
@@ -44,9 +40,12 @@ in order to model the vulnerabilities explained in the papers above.
References:
-Search terms:
+Search terms: web browser formal security; browser behavior; server behavior; BUILD block; coordination, one-to-many; nested composition
-Instructions:
+Instructions: Run for Scopes 1, 2, and 3.
+ Scope 1: 3 traces (no counterexamples for Property1) in less than 1 sec.
+ Scope 2: 7 traces (including 1 counterexample for Property1) in less than 1 sec.
+ Scope 3: 52 traces (including 16 counterexamples for Property1) in approx. 20 sec.
==========================================================*/
diff --git a/models/Application_examples/Wide_Range_Search_for_Wreckage_and_Survivors b/models/Application_examples/Wide_Range_Search_for_Wreckage_and_Survivors
index 9549df3c08d77227573bd6c88fc44c9967a0d06c..40b3dd65f4e66d421e39a9bfe107aa55fcd3b1bf 100644
--- a/models/Application_examples/Wide_Range_Search_for_Wreckage_and_Survivors
+++ b/models/Application_examples/Wide_Range_Search_for_Wreckage_and_Survivors
@@ -23,18 +23,15 @@ A System of Systems (SoS) analysis might expand the "SAR Asset" actor into disti
participating in or potentially participating in the scenario to study emergent behaviors of
those interacting systems in a SoS construct.
-Run for scope 1 (there is no iteration in this example, so increaasing the scope will not
-produce more scenarios). Only one scenario is produced because no decision points have been
-added to this model yet.
-
-The "Sequence" or "Swim Lanes" layouts are the most appropriate for browsing traces here.
-The "Sequence" mode yields views very similar to the UML or SysML Sequence Diagrams.
-
References:
-Search terms:
+Search terms: operational process behavior; wide range search; behavior of environment; system of systems behavior; emergent behavior
-Instructions:
+Instructions: Run for Scope 1 (there is no iteration in this example, so increasing the scope will not
+produce more scenarios). Only one scenario is produced because no decision points have been
+added to this model yet. "Sequence" mode yields views very similar to the UML or SysML
+Sequence Diagrams.
+ Scope 1: 1 trace in less than 1 sec.
==========================================================*/
diff --git a/models/Application_examples/Work_Productivity.mp b/models/Application_examples/Work_Productivity.mp
index c7db03e200b91534f40ad7d2fb329bc10779d11d..6c196e95cd17a05d23107ce7ec4b95eddf4c9954 100644
--- a/models/Application_examples/Work_Productivity.mp
+++ b/models/Application_examples/Work_Productivity.mp
@@ -10,13 +10,16 @@ Example 26, timing attribute use
events present in the trace
with timing attributes
- run for scopes 1 and up
-
References:
-Search terms:
+Search terms: work productivity behavior; distraction behavior; event attribute, timing; event attribute, interval; BUILD block
-Instructions:
+Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 12 traces in less than 1 sec.
+ Scope 3: 84 traces in less than 1 sec.
+ Scope 4: 780 traces in approx. 1.5 sec.
+ Scope 5: 9330 traces in approx. 1.0 min.
==========================================================*/
diff --git a/models/Example01_SimpleMessageFlow_EventCoordination.mp b/models/Example01_SimpleMessageFlow_EventCoordination.mp
index 6120cf7827d00a1db3d489f03ad4c4df376500f9..fa94e3cd97890bb3a6cd1fc2e7d59f787fb20f92 100644
--- a/models/Example01_SimpleMessageFlow_EventCoordination.mp
+++ b/models/Example01_SimpleMessageFlow_EventCoordination.mp
@@ -19,13 +19,16 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: simple message flow, simple interaction pattern, event coordination
+Search terms: simple message flow; simple interaction pattern; coordination, event
Instructions: Run for Scopes 1 and up. Traces are generated
in a sequence diagram-like format by default. Try rotating
a selected trace 90 degrees counterclockwise, or (from the
Options menu above the diagram) selecting the "Swim Lanes"
checkbox to view the trace in an activity diagram format.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 3 traces in less than 1 sec.
+ Scope 3: 4 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example01a_UnreliableMessageFlow_VirtualEvents.mp b/models/Example01a_UnreliableMessageFlow_VirtualEvents.mp
index 62db1d7d919b137c6edd0aa8c4ce13fcb906b2db..30c1084b6ce2a02c0ad54a31c6bc6c39637457e0 100644
--- a/models/Example01a_UnreliableMessageFlow_VirtualEvents.mp
+++ b/models/Example01a_UnreliableMessageFlow_VirtualEvents.mp
@@ -11,12 +11,15 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: unreliable message flow, unreliable communication, event coordination, virtual event
+Search terms: unreliable message flow; unreliable communication; coordination, event; virtual event
We may want to specify behaviors when some messages get lost in the transition.
It can be done using ‘virtual’ events.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 7 traces in less than 1 sec.
+ Scope 3: 15 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example02_DataFlow_EventSharing.mp b/models/Example02_DataFlow_EventSharing.mp
index 9b7862f6ffad5906a186e4bfbcd0e38a1acbd182..0fe71b540ac7ac79fd5e2b10a4ffce2c7d521360 100644
--- a/models/Example02_DataFlow_EventSharing.mp
+++ b/models/Example02_DataFlow_EventSharing.mp
@@ -11,7 +11,7 @@ Architecture and Workflow Modeling Language Manual"
(Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: data flow, event sharing
+Search terms: data flow behavior; event sharing
data items as behaviors
@@ -34,6 +34,9 @@ where behaviors of subsystems are influenced by the coordination.
This is a toy example of System of Systems emerging behavior modeling.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 28 traces in less than 1 sec.
+ Scope 3: 165 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp b/models/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp
index e19a9b8e2ca8da5d95612ab6557469ee71d3edcf..6abe79c23e1cdaee1fff585adf6c8fc4d740be0c 100644
--- a/models/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp
+++ b/models/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: ATM withdrawal, behavior of environment, ATM system, data base
+Search terms: ATM withdrawal; behavior of environment; ATM system; database
Integrated system and environment behaviors
@@ -36,6 +36,9 @@ to view a traditional "box-and-arrow" architecture diagram, i.e. to visualize an
Instructions: Run for Scopes 1 and up. "Sequence" mode yields views very similar to the UML or SysML
Sequence Diagrams.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 13 traces in less than 1 sec.
+ Scope 3: 40 traces in approx. 12 sec.
==========================================================*/
diff --git a/models/Example04_StackBehavior_EnsureCondition.mp b/models/Example04_StackBehavior_EnsureCondition.mp
index 6b8002566e52186a86b5b9b2b21011da871c8012..0fe7131e7f70108b72855ee889bb69e4626ae3e0 100644
--- a/models/Example04_StackBehavior_EnsureCondition.mp
+++ b/models/Example04_StackBehavior_EnsureCondition.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: stack behavior, ensure condition
+Search terms: stack behavior; ENSURE condition
The event trace is a set of events and the Boolean expressions
in MP can embrace the traditional predicate calculus notation. A set
@@ -41,6 +41,9 @@ and declarative (Boolean expressions) constructs for behavior
specification.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 4 traces in less than 1 sec.
+ Scope 3: 7 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example04a_StackBehavior_UserDefinedRelations.mp b/models/Example04a_StackBehavior_UserDefinedRelations.mp
index bc4f203bd1d58553692e5f7dd02742439e725e80..7f195042479b59f207cb000ac535cc8ddcb45f9a 100644
--- a/models/Example04a_StackBehavior_UserDefinedRelations.mp
+++ b/models/Example04a_StackBehavior_UserDefinedRelations.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: stack behavior, pop/push relationship, user defined relation, isomorphic behavior
+Search terms: stack behavior; user-defined relation; isomorphism
The event trace is a set of events and the Boolean expression constructs in MP
can support the traditional first order predicate calculus notation.
@@ -39,6 +39,9 @@ example of combining imperative (event grammar) and declarative
(Boolean expressions) constructs for behavior specification.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 4 traces in less than 1 sec.
+ Scope 3: 7 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example04b_QueueBehavior_UserDefinedRelations.mp b/models/Example04b_QueueBehavior_UserDefinedRelations.mp
index f6f4e4cb9df6f49a4b8c00ce6b7b8f869adcffe8..fd3bf637d08719c504bfcf3a692b876c691c8b30 100644
--- a/models/Example04b_QueueBehavior_UserDefinedRelations.mp
+++ b/models/Example04b_QueueBehavior_UserDefinedRelations.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: queue behavior, user defined relation, isomorphic behavior
+Search terms: queue behavior; user-defined relation; isomorphism
This rule specifies the behavior of a queue in terms of queue operations
enqueue and dequeue. It is assumed that initially Queue is empty.
@@ -31,6 +31,9 @@ example of combining imperative (event grammar) and declarative
(Boolean expressions) constructs for behavior specification.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 4 traces in less than 1 sec.
+ Scope 3: 7 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example05_CarRace_NestedComposition.mp b/models/Example05_CarRace_NestedComposition.mp
index 16ba248170d8ee06b7c661cc544da9e874a85203..03643b55e43bc15406f7662a35e84497cccc9222 100644
--- a/models/Example05_CarRace_NestedComposition.mp
+++ b/models/Example05_CarRace_NestedComposition.mp
@@ -11,7 +11,7 @@ Modeling Language Manual" (Version 4). 2020. Available
online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: car race, event sharing, nested composition
+Search terms: car race behavior; event sharing; coordination, one-to-many; nested composition; SAY statement; BUILD block; predicate logic; trace annotation
more coordination patterns:
- ordering of selected events in concurrent threads
@@ -20,6 +20,9 @@ more coordination patterns:
- one-many coordination.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 30 traces in less than 1 sec.
+ Scope 3: 236 traces in approx. 1.5 sec.
==========================================================*/
diff --git a/models/Example06_UnreliableChannel_AssertionChecking.mp b/models/Example06_UnreliableChannel_AssertionChecking.mp
index 1c0e312ce22c2a08ad4c56a819e3cfec6ace3b3c..1aa1055d98e0f94cd51cab03e91330afe1b6e932 100644
--- a/models/Example06_UnreliableChannel_AssertionChecking.mp
+++ b/models/Example06_UnreliableChannel_AssertionChecking.mp
@@ -11,7 +11,7 @@ Architecture and Workflow Modeling Language Manual"
(Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: unreliable channel, communicating, assertion checking
+Search terms: unreliable channel; communication; assertion checking
Assertion checking, Communicating via unreliable channel.
@@ -34,6 +34,9 @@ Search terms: unreliable channel, communicating, assertion checking
into the ENSURE condition.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 13 traces in less than 1 sec.
+ Scope 3: 40 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example07_UnconstrainedStack_TraceAnnotation.mp b/models/Example07_UnconstrainedStack_TraceAnnotation.mp
index f66c9e5b090cc7295a001243939131d660273479..323414e7dd7c005b44f68fd0eea9eeaa22d4987d 100644
--- a/models/Example07_UnconstrainedStack_TraceAnnotation.mp
+++ b/models/Example07_UnconstrainedStack_TraceAnnotation.mp
@@ -11,7 +11,7 @@ Architecture and Workflow Modeling Language Manual"
(Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: unconstrained stack, testing/debugging, trace annotation, empty stack
+Search terms: stack behavior; testing; debugging; trace annotation
Trace annotation techniques
@@ -31,6 +31,9 @@ events in the trace with additional messages. Programmers will recognize
the use of debugging print statements for traditional program testing/debugging.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 7 traces in less than 1 sec.
+ Scope 3: 15 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp b/models/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp
index 1c53216fe6a235ee9738ca9e38eb4e2287bf1909..b926df07e6cc3dc467febd290937f48be488e4df 100644
--- a/models/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp
+++ b/models/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: employee, employer, business process, coordination across hierarchy levels
+Search terms: business process behavior; coordination, across hierarchy levels
The web site http://www.infoq.com/articles/bpelbpm
“Why BPEL is not the holy grail for BPM “
@@ -33,9 +33,9 @@ Of course, you may want to model this simple process differently,
but the point here is that you cannot define a structured
parallel workflow [in BPEL] that is equivalent to this one ..."
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes
-a "Swim Lanes" option. Some box reshuffling may be needed to improve
-the trace layout.
+Instructions: Run for Scope 1. Trace viewing also includes
+a "Swim Lanes" option.
+ Scope 1: 1 trace in less than 1 sec.
==========================================================*/
diff --git a/models/Example09_PipeFilter_TraceAnnotationQueries.mp b/models/Example09_PipeFilter_TraceAnnotationQueries.mp
index e44ddcaf7c1e96f27bbe911440590032af4a94d6..ceb2717876d0d8a80a1c4e185284ec3c0d762c09 100644
--- a/models/Example09_PipeFilter_TraceAnnotationQueries.mp
+++ b/models/Example09_PipeFilter_TraceAnnotationQueries.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: pipe filter, architecture model, trace annotation queries
+Search terms: pipe filter behavior; architecture; query, trace annotation; isomorphism
pipe/filter architecture model with 2 filters
@@ -21,8 +21,10 @@ Search terms: pipe filter, architecture model, trace annotation queries
3) received message can stay in the Filter for while,
before being sent (if at all).
-Instructions: Run for Scopes 1, 2, 3, and 4.
- Scope 4: 959 traces in approx. 6.1 sec.
+Instructions: Run for Scopes 1, 2, and 3.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 19 traces in less than 1 sec.
+ Scope 3: 121 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example10_PublishSubscribe_EventReshuffling.mp b/models/Example10_PublishSubscribe_EventReshuffling.mp
index 2689d9a7c42e357ada424745eb51f30b25c21ccd..dd40ff16f1dae670d5d18f3efb3eeb97a8c43ccd 100644
--- a/models/Example10_PublishSubscribe_EventReshuffling.mp
+++ b/models/Example10_PublishSubscribe_EventReshuffling.mp
@@ -11,12 +11,14 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: publish, subscribe, architecture model, event reshuffling
+Search terms: publish subscribe behavior; architecture; event reshuffling; isomorphism
Publisher sends a notification to all active Subscribers
when new information is available.
Instructions: Run for Scopes 1, 2, and 3.
+ Scope 1: 1 trace in less than 1 sec.
+ Scope 2: 51 traces in less than 1 sec.
Scope 3: 3813 traces in approx. 7.4 min.
==========================================================*/
diff --git a/models/Example11_RingTopology_UserDefinedRelations.mp b/models/Example11_RingTopology_UserDefinedRelations.mp
index 889291733a88940c3b82f8f4a52bb2907b9967be..69669fb14f19978160a04e029c429d746d2cb14d 100644
--- a/models/Example11_RingTopology_UserDefinedRelations.mp
+++ b/models/Example11_RingTopology_UserDefinedRelations.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: ring topology, event reshuffling, user defined relation
+Search terms: ring topology behavior; event reshuffling; user-defined relation; isomorphism
ring topology
an example of user-defined relation use
@@ -19,7 +19,9 @@ Search terms: ring topology, event reshuffling, user defined relation
The following is a model of network ring,
where each node interacts with its left and right neighbors only.
-Instructions: Run for Scopes 1, 2, and 3.
+Instructions: Run for Scopes 1, 2, and 3.
+ Scope 1: 1 trace in less than 1 sec.
+ Scope 2: 32 traces in less than 1 sec.
Scope 3: 1570 traces in approx. 31 sec.
==========================================================*/
diff --git a/models/Example12_CardiacArrestWorkflow_VirtualEvents.mp b/models/Example12_CardiacArrestWorkflow_VirtualEvents.mp
index c0f33e9a784f338321d7607a052b077acb8ac8ef..070a42cbfbddd8ef1d9d0a27da2ef964c31123c9 100644
--- a/models/Example12_CardiacArrestWorkflow_VirtualEvents.mp
+++ b/models/Example12_CardiacArrestWorkflow_VirtualEvents.mp
@@ -11,7 +11,7 @@ Software Architecture and Workflow Modeling Language
Manual" (Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: cardiac arrest, workflow patterns, virtual event, triage task
+Search terms: triage behavior; workflow pattern; virtual event
the web site
http://workflowpatterns.com/patterns/control/index.php
@@ -26,6 +26,7 @@ is commenced. Completion of the other task is ignored and does not result
in a second instance of the triage task.
Instructions: Run for Scope 1.
+ Scope 1: 2 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example13_ConsumersSuppliers_DependencyTracking.mp b/models/Example13_ConsumersSuppliers_DependencyTracking.mp
index 50aaed7280783dbc84765469bf667f2b20f87b9a..ddd83a856f5dfba6df5da5823330af8cb3b73b6c 100644
--- a/models/Example13_ConsumersSuppliers_DependencyTracking.mp
+++ b/models/Example13_ConsumersSuppliers_DependencyTracking.mp
@@ -12,7 +12,7 @@ Modeling Language Manual" (Version 4). 2020. Available
online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: consumer, supplier, dependency tracking, asynchronous coordination
+Search terms: consumer supplier behavior; dependency tracking; coordination, asynchronous
Asynchronous coordination and dependency definition example.
@@ -20,6 +20,7 @@ user-defined relation related_to connects events within each
single Request_delivery -> Consume chain
Instructions: Run for Scopes 1 and 2.
+ Scope 1: 2 traces in less than 1 sec.
Scope 2: 110 traces in approx. 38 sec.
==========================================================*/
diff --git a/models/Example14_ShoppingSpree_NumberAttributes.mp b/models/Example14_ShoppingSpree_NumberAttributes.mp
index 99f84dee380a5adbdb9a5c40b1483bfabc4f7998..567f72cb22974e5a5456453bcb07104c3c9f3fd2 100644
--- a/models/Example14_ShoppingSpree_NumberAttributes.mp
+++ b/models/Example14_ShoppingSpree_NumberAttributes.mp
@@ -11,9 +11,12 @@ Modeling Language Manual" (Version 4). 2020. Available
online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: shopping spree, number attribute
+Search terms: shopping spree behavior; event attribute, number; BUILD block; SAY statement; isomorphism
Instructions: Run for Scopes 1 and up.
+ Scope 1: 9 traces in less than 1 sec.
+ Scope 2: 49 traces in less than 1 sec.
+ Scope 3: 225 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example15_BackpackWeight_IntervalAttributes.mp b/models/Example15_BackpackWeight_IntervalAttributes.mp
index 06a696a5561afe612827e3d7c553d180a94222e6..24b9f0f6338a48a268a6bf7595992d6d94afaf0b 100644
--- a/models/Example15_BackpackWeight_IntervalAttributes.mp
+++ b/models/Example15_BackpackWeight_IntervalAttributes.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: backpack weight, interval attribute
+Search terms: event attribute, interval; optimization, weight; BUILD block; SAY statement
Use of interval attributes.
@@ -20,6 +20,9 @@ Search terms: backpack weight, interval attribute
There may be several instances of the same item.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 5 traces in less than 1 sec.
+ Scope 3: 9 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example16_StackBehavior_ProbabilityCalculationsType1.mp b/models/Example16_StackBehavior_ProbabilityCalculationsType1.mp
index 08204c7edbb952cb4986e61a720b10ddf469538c..4e43df5b483d50685ef47f729a04b39d38a3c777 100644
--- a/models/Example16_StackBehavior_ProbabilityCalculationsType1.mp
+++ b/models/Example16_StackBehavior_ProbabilityCalculationsType1.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: stack behavior, type 1 probability
+Search terms: stack behavior; Type 1 probability; ENSURE condition
Here is a simple stack behavior model. Valid behaviors don’t permit
a scenario when Pop operation is applied to the empty stack. For the
@@ -27,6 +27,9 @@ impossible in a real stack, so they are cut from the model.
By removing some scenarios, the remaining probabilities change.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 4 traces in less than 1 sec.
+ Scope 3: 7 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example17_SharedEvents_ProbabilityCalculationsType1.mp b/models/Example17_SharedEvents_ProbabilityCalculationsType1.mp
index 4c58da1c25156ef670fe962e030f49641529fdcd..cd9104c4656f31fcbb447264271ac06539dbd540 100644
--- a/models/Example17_SharedEvents_ProbabilityCalculationsType1.mp
+++ b/models/Example17_SharedEvents_ProbabilityCalculationsType1.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: shared events, type 1 probability
+Search terms: event sharing; Type 1 probability
A simple example of shared events. If one root has a, the other root
also has a. If neither root has a, then root 1 must have b, and root 2
@@ -19,6 +19,7 @@ must have c. Additionally, probabilities show how "SHARE ALL" increases
the chances of the shared event.
Instructions: Run for Scope 1.
+ Scope 1: 2 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp b/models/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp
index 3ed1d30a31cff7d5148f2e5917ac97ceef7ce844..6cf2f87ea857979e388a968ca5230cc73ac78977 100644
--- a/models/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp
+++ b/models/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: red, green, number attribute, type 2 probability, bayesian probability
+Search terms: event attribute, number; Type 2 probability; Bayesian probability
Bayesian attribute example
@@ -27,6 +27,7 @@ Search terms: red, green, number attribute, type 2 probability, bayesian probabi
constant for the whole derivation process.
Instructions: Run for Scope 1.
+ Scope 1: 7 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp b/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp
index 66817d77b0edd91c60fc6491257e7344073ba243..45aed0fe886d8cb43346a01d2d10b00f1b672e8e 100644
--- a/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp
+++ b/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: stack behavior, number attribute, type 2 probability, bayesian probability
+Search terms: stack behavior; event attribute, number; Type 2 probability; Bayesian probability
An example of Bayesian probability calculation.
@@ -36,6 +36,9 @@ Search terms: stack behavior, number attribute, type 2 probability, bayesian pro
it will become p2 := 1/(M + 1);
Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 4 traces in less than 1 sec.
+ Scope 3: 7 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example20_Activity_Diagram.mp b/models/Example20_Activity_Diagram.mp
index 55adc6a202b1d568cc999a940cb2c9123a150e19..772f245c9b91ee1352492099072f0ef93325a325 100644
--- a/models/Example20_Activity_Diagram.mp
+++ b/models/Example20_Activity_Diagram.mp
@@ -11,13 +11,14 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: activity diagram, flowchart
+Search terms: graph, activity diagram; graph, flowchart
This model demonstrates how to use "SHOW ACTIVITY DIAGRAM" to
display the possible traces in flowchart form. Root A has 4 different
possible traces at scope 1, and the flowchart displays those possiblities.
Instructions: Run for Scope 1.
+ Scope 1: 4 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example21_DataFlow_LocalReport.mp b/models/Example21_DataFlow_LocalReport.mp
index 476ab6291914ceabb71cacb623d09fd223ce4c7a..615a22eec981aba2e87eaf61b605ceef29f7ef9c 100644
--- a/models/Example21_DataFlow_LocalReport.mp
+++ b/models/Example21_DataFlow_LocalReport.mp
@@ -11,11 +11,14 @@ Architecture and Workflow Modeling Language Manual"
(Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: data flow, local report, basic statistics
+Search terms: data flow behavior; report, local; statistics, basic
Local Report within a trace.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 28 traces in less than 1 sec.
+ Scope 3: 165 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example22_SimpleMessageFlow_GlobalReport.mp b/models/Example22_SimpleMessageFlow_GlobalReport.mp
index 0144f8c607deb946a37325a4065210ae5299743c..bbf0289c3cc14fe75aa1756a2cbc6fe6d7bdea76 100644
--- a/models/Example22_SimpleMessageFlow_GlobalReport.mp
+++ b/models/Example22_SimpleMessageFlow_GlobalReport.mp
@@ -12,9 +12,12 @@ Modeling Language Manual" (Version 4). 2020. Available
online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: simple message flow, global report, statistics
+Search terms: simple message flow; report, global; statistics, global
Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 7 traces in less than 1 sec.
+ Scope 3: 15 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example23_CarRace_LocalGraph.mp b/models/Example23_CarRace_LocalGraph.mp
index 10219950e95b64a05433b1b3f4983eedd6e02c19..d931a04d21aaaee6a4fc4c51af156cf87fdb2017 100644
--- a/models/Example23_CarRace_LocalGraph.mp
+++ b/models/Example23_CarRace_LocalGraph.mp
@@ -11,11 +11,14 @@ System and Software Architecture and Workflow Modeling
Language Manual" (Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: car race, local graph, local trace view
+Search terms: car race behavior; graph, local; WITHIN command
Local graph within the event trace.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 30 traces in less than 1 sec.
+ Scope 3: 236 traces in approx. 1.5 sec.
==========================================================*/
diff --git a/models/Example24_Compiler_ComponentDiagram.mp b/models/Example24_Compiler_ComponentDiagram.mp
index 266e8a1bad13daade6f91feef96ee450a7398778..f360d8082ee4128e369df13238272526c1e588a4 100644
--- a/models/Example24_Compiler_ComponentDiagram.mp
+++ b/models/Example24_Compiler_ComponentDiagram.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: compiler, component diagram, global report, lexer, parser, stack
+Search terms: compiler behavior; graph, component diagram; report, global; lexer behavior; parser behavior; stack behavior; isomorphism
Compiler front end, bottom-up parser
Lexer and parser in interactive mode.
diff --git a/models/Example25_Graph_as_Data_Structure.mp b/models/Example25_Graph_as_Data_Structure.mp
index 770e90cba70bf9cee4fe6f4159812a2403c63bc7..7c43ec987548f4adddfc15748d0591de9b4d0c6e 100644
--- a/models/Example25_Graph_as_Data_Structure.mp
+++ b/models/Example25_Graph_as_Data_Structure.mp
@@ -11,12 +11,15 @@ and Software Architecture and Workflow Modeling Language
Manual" (Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: graph as data structure, number attribute, global report, total event statistics
+Search terms: graph as data structure; event attribute, number; report, global; statistics, global
Accumulating and rendering statistics from event traces.
Graphs as container data structures
Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 14 traces in less than 1 sec.
+ Scope 3: 45 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example26_UnreliableMessageFlow_GlobalQuery.mp b/models/Example26_UnreliableMessageFlow_GlobalQuery.mp
index 662d4fd9908cdfad6bffbc19ed56687ec5ebfed1..9b7803d66432200583950f8f347f19e2c58670f9 100644
--- a/models/Example26_UnreliableMessageFlow_GlobalQuery.mp
+++ b/models/Example26_UnreliableMessageFlow_GlobalQuery.mp
@@ -11,7 +11,7 @@ System and Software Architecture and Workflow Modeling
Language Manual" (Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: unreliable message flow, global query, number attribute, probability summary
+Search terms: unreliable message flow; query, global; event attribute, number; query, probability summary
GLOBAL query
@@ -30,6 +30,9 @@ ROOT Sender: (+<1..7> send +);
ROOT Receiver: (+<1..7> (receive |<<0.2>> does_not_receive) +);
Instructions: Run for Scopes 1 and up.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 6 traces in less than 1 sec.
+ Scope 3: 14 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp b/models/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp
index 1d5238c7c7a0b89aa898418cd67d247d0426044b..07ece148792d9a6bf21b2e6638b39d2c4d68975e 100644
--- a/models/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp
+++ b/models/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp
@@ -12,12 +12,13 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: table, bar chart, assembling statistics, number attribute
+Search terms: table; graph, bar chart; statistics, assembling; event attribute, number
Assembling statistics about a current trace in a TABLE and rendering it.
Table and bar chart example.
Instructions: Run for Scope 1.
+ Scope 1: 1 trace in less than 1 sec.
==========================================================*/
diff --git a/models/Example28_AssemblingStatistics_Histogram.mp b/models/Example28_AssemblingStatistics_Histogram.mp
index f86f7bd628f0928817f681363ada9473aca1965f..c57f451cf721a1bf146fadfedce41ae0e17d4a07 100644
--- a/models/Example28_AssemblingStatistics_Histogram.mp
+++ b/models/Example28_AssemblingStatistics_Histogram.mp
@@ -12,11 +12,14 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: histogram, assembling statistics, number attribute, global report, probability interval
+Search terms: graph, histogram; statistics, assembling; event attribute, number; report, global; probability interval
Histogram example
Instructions: Run for Scopes 1 and up.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 5 traces in less than 1 sec.
+ Scope 3: 6 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example29_AssemblingStatistics_Gantt_Chart.mp b/models/Example29_AssemblingStatistics_Gantt_Chart.mp
index f6ed9732bd49a6a88d5a1ca9abd477afea59a806..e4a0dc988932ccc5e9f7955b06e7dde9766b4c49 100644
--- a/models/Example29_AssemblingStatistics_Gantt_Chart.mp
+++ b/models/Example29_AssemblingStatistics_Gantt_Chart.mp
@@ -11,11 +11,12 @@ Modeling Language Manual" (Version 4). 2020. Available
online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: gantt chart, assembling statistics, table, bar chart
+Search terms: graph, Gantt chart; statistics, assembling; table; graph, bar chart
Gantt chart example
Instructions: Run for Scope 1.
+ Scope 1: 1 trace in less than 1 sec.
==========================================================*/
diff --git a/models/Example30_MicrowaveOven_ModelingModelChecking.mp b/models/Example30_MicrowaveOven_ModelingModelChecking.mp
index 781992ea6b602055d269da2f238965282ca653bb..8f1dfd28474554b2bf5b55d7272d88b45cc78e47 100644
--- a/models/Example30_MicrowaveOven_ModelingModelChecking.mp
+++ b/models/Example30_MicrowaveOven_ModelingModelChecking.mp
@@ -11,7 +11,7 @@ Architecture and Workflow Modeling Language Manual"
(Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: microwave oven, model checking, finite state diagram, state visit, state transition, atomic proposition, inner event
+Search terms: microwave oven behavior; model checking; finite state diagram; state transition; propositional logic
example of finite state diagram behavior model,
CTL formula representation in MP, and model checking for a small scope.
diff --git a/models/Example31_Aspect_Oriented_Paradigm.mp b/models/Example31_Aspect_Oriented_Paradigm.mp
index 3e367e01aa6c2c375d5f2b3425ca7aec286cc40f..f76abe156c1eb09fa586989754b47407bc9d0512 100644
--- a/models/Example31_Aspect_Oriented_Paradigm.mp
+++ b/models/Example31_Aspect_Oriented_Paradigm.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: aspect-oriented paradigm, join point, aspect behavior, advice coordination
+Search terms: aspect-oriented paradigm; join point; aspect behavior; coordination, advice
The COORDINATE operation supports a “cause-effect†refinement for
the behavior of two components and it bears a certain similarity
@@ -27,6 +27,9 @@ a call to Prolog before, and to Epilog after each method call as an
advice. The corresponding MP model may look like the following.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 13 traces in less than 1 sec.
+ Scope 3: 40 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example32_Petri_Net.mp b/models/Example32_Petri_Net.mp
index 081794ff5bbdf5a730bc39dd6099f452e76c9b76..4515b3bc92e7c3c164fb032868536074d48d4a1d 100644
--- a/models/Example32_Petri_Net.mp
+++ b/models/Example32_Petri_Net.mp
@@ -11,7 +11,7 @@ Modeling Language Manual" (Version 4). 2020. Available
online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: petri net, number attribute, global report
+Search terms: petri net behavior; event attribute, number; report, global
modeling Petri net behavior
see the Petri net diagram in Sec. 2.16.2 in the MP v.4 Language Manual
@@ -20,6 +20,7 @@ Search terms: petri net, number attribute, global report
extracted from the event traces, run scope 2
Instructions: Run for Scopes 1 and 2.
+ Scope 1: 2 traces in less than 1 sec.
Scope 2: 4 traces in approx. 6.6 sec.
==========================================================*/
diff --git a/models/Example33_ATMWithdrawal_StatechartView.mp b/models/Example33_ATMWithdrawal_StatechartView.mp
index b58e8f033dec977ed216820da35c4d2734d4834d..59af9f274a551c05fd50d1b38397c8b894767cc9 100644
--- a/models/Example33_ATMWithdrawal_StatechartView.mp
+++ b/models/Example33_ATMWithdrawal_StatechartView.mp
@@ -11,11 +11,14 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: ATM withdrawal, statechart view, ATM system, data base, global report
+Search terms: ATM withdrawal; statechart view; ATM system; database; report, global
Extracting Statechart view from MP model.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 4 traces in less than 1 sec.
+ Scope 2: 13 traces in less than 1 sec.
+ Scope 3: 40 traces in approx. 20 sec.
==========================================================*/
diff --git a/models/Example34_FiniteStateDiagram_PathAnnotation.mp b/models/Example34_FiniteStateDiagram_PathAnnotation.mp
index d07e19c50f3134d966e10bab7397d23f2af5a9b1..910a59d1ea69e5286444539060fed35de8ac698c 100644
--- a/models/Example34_FiniteStateDiagram_PathAnnotation.mp
+++ b/models/Example34_FiniteStateDiagram_PathAnnotation.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: finite state diagram, path annotation, state visit, state transition, finite state machine
+Search terms: finite state diagram; path annotation; state transition; finite state machine behavior
example of finite state diagram behavior model,
contains non-deterministic transitions (from S1 with symbol a),
@@ -42,7 +42,8 @@ Search terms: finite state diagram, path annotation, state visit, state transiti
1) Event Si_to_Sj contains the symbol triggering the transition.
2) Si_to_Sj is shared by corresponding state behavior roots.
-Instructions: Run for Scopes 1 and 2.
+Instructions: Run for Scopes 1 and 2.
+ Scope 1: 4 traces in less than 1 sec.
Scope 2: 30 traces in approx. 9.4 sec.
==========================================================*/
diff --git a/models/Example35_FiniteStateDiagram_PathDiagram.mp b/models/Example35_FiniteStateDiagram_PathDiagram.mp
index 834e71c0a2265f57eb2d12041ff18cbfb6d37d4a..d5915720a1ed4c1363521aa96a6a26cff144cb07 100644
--- a/models/Example35_FiniteStateDiagram_PathDiagram.mp
+++ b/models/Example35_FiniteStateDiagram_PathDiagram.mp
@@ -12,7 +12,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: finite state diagram, path diagram, state transition, global report, finite automaton behavior
+Search terms: finite state diagram; path diagram; state transition; report, global; finite automaton behavior
Adding path and state transition diagrams to
the Finite Automaton behavior model.
diff --git a/models/Example36_Authentication_SystemReuse.mp b/models/Example36_Authentication_SystemReuse.mp
index 5f6b1438cde421b358895f5188dcdea841a80245..8e7bbcab21d62a6121723b3d1cc94aa6c1debb3e 100644
--- a/models/Example36_Authentication_SystemReuse.mp
+++ b/models/Example36_Authentication_SystemReuse.mp
@@ -12,13 +12,18 @@ Architecture and Workflow Modeling Language Manual"
(Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: authentication system, system reuse, subsystem, MAP operation, data base
+Search terms: authentication system behavior; system reuse; subsystem; MAP operation; database
Instructions: Run for Scopes 1 and up. Viewing of traces
also includes a "Swim Lanes" option. At Scope 3 and above,
the attempts_exhausted event can be seen. You may hide the
Requestor node in the event trace graph, since the User
will copy all Requestor's behavior.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 6 traces in less than 1 sec.
+ Scope 3: 9 traces in less than 1 sec.
+ Scope 4: 9 traces in less than 1 sec.
+ Scope 5: 9 traces in less than 1 sec.
============== reused MP code starts here ==================*/
diff --git a/models/Example37_Compiler1_ComponentReuse.mp b/models/Example37_Compiler1_ComponentReuse.mp
index 085be255be168704f098075ef467da41f01b9279..bf0c74796a7f865c9f97665ccc6922207ab36529 100644
--- a/models/Example37_Compiler1_ComponentReuse.mp
+++ b/models/Example37_Compiler1_ComponentReuse.mp
@@ -11,13 +11,14 @@ Architecture and Workflow Modeling Language Manual" (Version 4).
2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: compiler, component reuse, front end, batch mode, bottom-up, parser, isomorphic behavior
+Search terms: compiler behavior; component reuse; batch mode; lexer behavior; parser behavior; isomorphism
Compiler front end,
bottom-up parser
Lexer and parser in batch mode
Instructions: Run for Scopes 1 and 2.
+ Scope 1: 2 traces in less than 1 sec.
Scope 2: 147 traces in approx. 1.8 sec.
==========================================================*/
diff --git a/models/Example38_Compiler2_ComponentReuse.mp b/models/Example38_Compiler2_ComponentReuse.mp
index 440cf55a3f8f3c295acd2afc978970880ec0c2e9..a1ce631f7b131e0a013153c50c54867df08063b5 100644
--- a/models/Example38_Compiler2_ComponentReuse.mp
+++ b/models/Example38_Compiler2_ComponentReuse.mp
@@ -11,13 +11,15 @@ Architecture and Workflow Modeling Language Manual"
(Version 4). 2020. Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: compiler, component reuse, front end, incremental mode, interaction mode, bottom-up, parser, isomorphic behavior
+Search terms: compiler behavior; component reuse; incremental mode; lexer behavior; parser behavior; isomorphism
Compiler front end,
bottom-up parser
Lexer and parser in interaction mode
Instructions: Run for Scopes 1, 2, and 3.
+ Scope 1: 2 traces in less than 1 sec.
+ Scope 2: 111 traces in approx. 1.1 sec.
Scope 3: 4860 traces in approx. 1.6 min.
==========================================================*/
diff --git a/models/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp b/models/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp
index 9aac4fddc111188e228f8966722343115c20a4ff..f22bbd724caa52873ce34d338ec91c30a283d594 100644
--- a/models/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp
+++ b/models/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: merging root events, reduce run time, layered derivation, trace segment derivation
+Search terms: merging root events; reduce run time; layered derivation; trace segment derivation
Complex MP models may have large number of root events with several
coordination operations performed on clusters of roots. This may be
@@ -40,6 +40,8 @@ encapsulate the trace segment derivation (including the coordination)
for B and C.
Instructions: Run for Scopes 1 and 2.
+ Scope 1: 53 traces in less than 1 sec.
+ Scope 2: 1150 traces in less than 1 sec.
==========================================================*/
diff --git a/models/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp b/models/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp
index 94dc27d6fc80f823ab5031e0179521efc79c4f3e..f2bd8f2ccde07af5bafd436c2be690ac856497e2 100644
--- a/models/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp
+++ b/models/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp
@@ -11,7 +11,7 @@ Workflow Modeling Language Manual" (Version 4). 2020.
Available online:
https://wiki.nps.edu/display/MP/Documentation
-Search terms: application process, partitioning large schema, separate schemas
+Search terms: application process behavior; partitioning large schema; separate schemas
An applicant submits application and needs to get it approved by
the bureaucratic chain of two officials. If the first official approves,
@@ -22,6 +22,9 @@ Rework and resubmit events may be repeated several times. Each rejection
is final and cannot be followed by rework and resubmit events.
Instructions: Run for Scopes 1 and up.
+ Scope 1: 3 traces in less than 1 sec.
+ Scope 2: 9 traces in less than 1 sec.
+ Scope 3: 18 traces in less than 1 sec.
==========================================================*/