Merge branch 'Pamela_Branch' into 'master'

Pamela's Merge Request: 07-23-2021

See merge request !24

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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 Scopes 2 and 3. (Scope 1 generates zero traces because
+of the ENSURE constraint on line 29.)
+	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.
 
 ==========================================================*/
 

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; riddles; 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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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 behavior; 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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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; nested iteration
 
-Instructions:
+Instructions: Run for Scope 1.
+	Scope 1: 8 traces in approx. 1.4 min.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/
 

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.
 
 ==========================================================*/