Merge branch 'Pamela_Branch_4' into 'master'

Pamela's Merge Request: 12-26-2021

See merge request !53

models/Application_examples/Agile_Production_Platform_Customer_Interactions.mp

@@ -18,7 +18,7 @@
 │*│ │ Platform" (APP). Here the order is for face        │ │
 │*│ │ shields in response to the COVID-19 pandemic.      │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates using MP to find both      │ │
 │*│ │ desired and undesired scenarios of Personal        │ │

models/Application_examples/Agile_Production_Platform_Supply_Chain_Interaction.mp

@@ -15,7 +15,7 @@
 │*│ │ material on-hand to produce the component          │ │
 │*│ │ correctly.                                         │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates using MP to find both      │ │
 │*│ │ desired and undesired scenarios resulting from     │ │

models/Application_examples/Application_Process.mp

@@ -9,7 +9,7 @@
 │*│ │ To provide a template for an application approval  │ │
 │*│ │ process involving multiple levels of approval.     │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ An applicant submits application and needs to get  │ │
 │*│ │ it approved by the bureaucratic chain of two       │ │

models/Application_examples/Aspect_Oriented_Paradigm.mp

@@ -9,7 +9,7 @@
 │*│ │ To demonstrate the Aspect-Oriented Programming     │ │
 │*│ │ paradigm in MP.                                    │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Aspect-Oriented Programming (AOP) [Kiczales et al. │ │
 │*│ │ 1997] is a programming approach that separates the │ │

models/Application_examples/Authentication.mp

@@ -14,7 +14,7 @@
 │*│ │ To demonstrate how to reject unwanted behaviors    │ │
 │*│ │ with ENSURE constraints.                           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates how to correctly model a   │ │
 │*│ │ simple user authentication system with ENSURE      │ │

models/Application_examples/Autonomous_Car.mp

@@ -11,7 +11,7 @@
 │*│ │ To illustrate the use of COORDINATE statements to  │ │
 │*│ │ improve the quality of trace analysis.             │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This is a model of an autonomous car that was      │ │
 │*│ │ developed as part of a student project to support  │ │

models/Application_examples/Beginner_Use_of_MP.mp

@@ -15,7 +15,7 @@
 │*│ │ 2) the modeling process of formalizing a previously│ │
 │*│ │    unstated assumption.                            │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model provides an orientation for those just  │ │
 │*│ │ getting started using MP-Firebird. The text editor │ │
@@ -27,12 +27,12 @@
 │*│ │ scope slider bar next to the Run button to control │ │
 │*│ │ the number of loop iterations.                     │ │
 │*│ │                                                    │ │
-│*│ │ ROOT A: B C;	A is a root event that includes      │ │
+│*│ │ ROOT A: B C;     A is a root event that includes   │ │
 │*│ │               events B followed by C               │ │
 │*│ │ ( B | C )	    Alternative events B or C (but not   │ │
 │*│ │               both together in the same trace)     │ │
-│*│ │ (* B *) 		iterate B zero or more times         │ │
-│*│ │ { B , C } 	B and C are unordered                │ │
+│*│ │ (* B *)       iterate B zero or more times         │ │
+│*│ │ { B , C }     B and C are unordered                │ │
 │*│ └────────────────────────────────────────────────────┘ │
 │*│                                                        │
 │*│ ┌─[ References ]─────────────────────────────────────┐ │

models/Application_examples/CargoScreening.mp

@@ -12,7 +12,7 @@
 │*│ │ logic, in this case outlining a cargo screening    │ │
 │*│ │ process.                                           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates using composite statements │ │
 │*│ │ under roots to make a long chain of logic. This    │ │

models/Application_examples/Commercial_Flight.mp

@@ -13,7 +13,7 @@
 │*│ │ statements to make a web of actions linked         │ │
 │*│ │ together through phases.                           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates the interlacing of root    │ │
 │*│ │ events as Phases and as Actors, in order to model  │ │

models/Application_examples/Correlation_and_Fusion_Process_Ungoverned.mp

@@ -11,7 +11,7 @@
 │*│ │ reporting data flows showing existing data path    │ │
 │*│ │ behaviors.                                         │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Models the data flow from sensors all the way to   │ │
 │*│ │ the human analyst at a tactical location. The      │ │

models/Application_examples/Correlation_and_Fusion_Process_with_Data_Governance.mp

@@ -12,7 +12,7 @@
 │*│ │ data path behaviors with the application of a data │ │
 │*│ │ governance framework.                              │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Models the data flow from sensors all the way to   │ │
 │*│ │ the human analyst at a tactical location           │ │

models/Application_examples/Cycle_Pattern.mp

@@ -12,9 +12,9 @@
 │*│ │ can be modeled in MP, and to show how rule-based   │ │
 │*│ │ comments can be added to the traces.               │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
-│*│ │ The model below describes a cyclein terms of a     │ │
+│*│ │ The model below describes a cycle in terms of a    │ │
 │*│ │ series of one or more steps, each step either      │ │
 │*│ │ moving the system "forward" or "backward" as the   │ │
 │*│ │ process unfolds. "Forward" and "backward" are      │ │

models/Application_examples/Dining_Philosophers.mp

@@ -11,7 +11,7 @@
 │*│ │ solving capabilities of MP, using the dining       │ │
 │*│ │ philosophers problem as the topic.                 │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates using COORDINATE, ENSURE,  │ │
 │*│ │ and IF statements to come up with an answer to a   │ │

models/Application_examples/Elevator.mp

@@ -11,17 +11,17 @@
 │*│ │ be beneficial, because it can lead to emergent     │ │
 │*│ │ behavior showing up in the traces.                 │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This demonstrates the modeling of situations and   │ │
 │*│ │ consequential events in MP. The pattern is:        │ │
 │*│ │                                                    │ │
-│*│ │ ( 	SituationA do_one_thing 	|                │ │
+│*│ │ (         SituationA do_one_thing     |            │ │
 │*│ │ SituationB do_another_thing )                      │ │
 │*│ │                                                    │ │
 │*│ │ in the case of this model,                         │ │
 │*│ │                                                    │ │
-│*│ │ ( 	Elevator_works_fine Get_Off |                │ │
+│*│ │ (         Elevator_works_fine Get_Off |            │ │
 │*│ │ Emergency_Situation Call_for_help )                │ │
 │*│ │                                                    │ │
 │*│ │ Ultimately, this is a simple model of an emergency │ │

models/Application_examples/Falcon_9_Launch_with_Gantt.mp

@@ -13,7 +13,7 @@
 │*│ │ and first stage booster recover through system     │ │
 │*│ │ behavior modeling.                                 │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ A Falcon 9 Rocket is a two booster stage rocket    │ │
 │*│ │ that is designed to carry payloads into space      │ │

models/Application_examples/FindAdvisor.mp

@@ -10,7 +10,7 @@
 │*│ │ To show that human interaction and organizational  │ │
 │*│ │ processes can be modeled using MP.                 │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Alternate behaviors for humans are described in    │ │
 │*│ │ terms of possible decisions they could make. This  │ │

models/Application_examples/First_Responder.mp

@@ -12,7 +12,7 @@
 │*│ │ administation of a rescue medication (Narcan) to   │ │
 │*│ │ an overdose victim.                                │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates the administration of      │ │
 │*│ │ Narcan by bystanders in order to determine the     │ │

models/Application_examples/Knapsack_Weight_Limit.mp

@@ -11,7 +11,7 @@
 │*│ │ optimal solutions in a certain scope, with a limit │ │
 │*│ │ set for the weight of the knapsack.                │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This is a case of well-known Knapsack Dynamic      │ │
 │*│ │ Programming Problem. In general it is NP-hard and  │ │

models/Application_examples/MP_Architecture_Specification.mp

@@ -11,7 +11,7 @@
 │*│ │ MP compiler/trace generator components built from  │ │
 │*│ │ the component behaviors.                           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates how a user might use an MP │ │
 │*│ │ IDE to extract a component diagram from an MP      │ │

models/Application_examples/Manufacturing_Process.mp

@@ -10,7 +10,7 @@
 │*│ │ To demonstrate a model of a system manufacturing   │ │
 │*│ │ process.                                           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates application of Monterey    │ │
 │*│ │ Phoenix Modeling to Manufacturing Product Systems. │ │