diff --git a/Example01_SimpleMessageFlow_EventCoordination.mp b/Example01_SimpleMessageFlow_EventCoordination.mp
index 2e0f661857d142468eb10561fd2bc0f79e81a925..314435154a1b5459a2e45d2ed73e074dbeacc37d 100644
--- a/Example01_SimpleMessageFlow_EventCoordination.mp
+++ b/Example01_SimpleMessageFlow_EventCoordination.mp
@@ -1,4 +1,7 @@
/* Example 01. Model of Simple Message Flow
+See also: Example 1: Simple interaction pattern from the Monterey
+Phoenix System and Software Architecture and Workflow Modeling Language
+Manual
Event grammar rules for each root define derivations for event traces,
in this case a simple sequence of zero or more events for each root.
diff --git a/Example01a_UnreliableMessageFlow_VirtualEvents.mp b/Example01a_UnreliableMessageFlow_VirtualEvents.mp
index d7a23e6b5f1144b4783f4a509031829118e4b2e3..49b0b3974ba5e57dcf42a240fa9dba6f5cb846ed 100644
--- a/Example01a_UnreliableMessageFlow_VirtualEvents.mp
+++ b/Example01a_UnreliableMessageFlow_VirtualEvents.mp
@@ -1,4 +1,6 @@
/* Example 01a. Model of Unreliable Message Flow
+See also: Example 8: Unreliable Communication model from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling Language Manual
We may want to specify behaviors when some messages get lost in the transition.
It can be done using ‘virtual’ events.
diff --git a/Example02_DataFlow_EventSharing.mp b/Example02_DataFlow_EventSharing.mp
index 6459a5d3b677f0631b0d74722a8612a7a88dbacc..f553871459226700205a816f40f7ef6bdb150159 100644
--- a/Example02_DataFlow_EventSharing.mp
+++ b/Example02_DataFlow_EventSharing.mp
@@ -1,5 +1,7 @@
/* Example 02. Model of Data Flow
-
+See also: Example 3: Data Flow model from the Monterey Phoenix System and
+Software Architecture and Workflow Modeling Language Manual
+
data items as behaviors
MP employs the Abstract Data Type (ADT) principle introduced by
diff --git a/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp b/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp
index c3433783b448bbdd55064e2685be235d43e17c1f..ac7002fa83a6aea2f39bc946abd7ffc38563c9a3 100644
--- a/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp
+++ b/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp
@@ -1,5 +1,7 @@
/* Example 03. Model of ATM Withdrawal
-
+See also: Example 4: Withdraw money from ATM model from the Monterey Phoenix System and
+Software Architecture and Workflow Modeling Language Manual
+
Integrated system and environment behaviors
MP separates models of component behaviors and component interactions
diff --git a/Example04_StackBehavior_EnsureCondition.mp b/Example04_StackBehavior_EnsureCondition.mp
index 23db1978f378ebf1401c87681cf6e61fa71fc9e1..929b502923d85c8ce7f4bdb904b5eaf086b881f3 100644
--- a/Example04_StackBehavior_EnsureCondition.mp
+++ b/Example04_StackBehavior_EnsureCondition.mp
@@ -1,4 +1,6 @@
/* Example 04. Model of Stack Behavior
+See also: Example 5: Stack behavior model from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling Language Manual
The event trace is a set of events and the Boolean expressions
in MP can embrace the traditional predicate calculus notation. A set
diff --git a/Example04a_StackBehavior_UserDefinedRelations.mp b/Example04a_StackBehavior_UserDefinedRelations.mp
index 0264da3061a11b16261533489e387ed56bc3f86f..2e99070a49b24d7da29a12d8e0504b9d6774d385 100644
--- a/Example04a_StackBehavior_UserDefinedRelations.mp
+++ b/Example04a_StackBehavior_UserDefinedRelations.mp
@@ -1,4 +1,7 @@
/* Example 04a. Model of Stack Behavior
+See also: Example 17: Stack behavior model with pop/push relationship
+visualized from the Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
The event trace is a set of events and the Boolean expression constructs in MP
can support the traditional first order predicate calculus notation.
diff --git a/Example04b_QueueBehavior_UserDefinedRelations.mp b/Example04b_QueueBehavior_UserDefinedRelations.mp
index 61b342ad269cb83bf62ac9f723c146e76dc42f37..89423bca9388221f2e5426ae67ceeb57f6183410 100644
--- a/Example04b_QueueBehavior_UserDefinedRelations.mp
+++ b/Example04b_QueueBehavior_UserDefinedRelations.mp
@@ -1,4 +1,6 @@
/* Example 04b. Model of Queue Behavior
+See also: Example 18: Queue behavior model from the Monterey Phoenix System and
+Software Architecture and Workflow Modeling Language Manual
This rule specifies the behavior of a queue in terms of queue operations
enqueue and dequeue. It is assumed that initially Queue is empty.
diff --git a/Example05_CarRace_NestedComposition.mp b/Example05_CarRace_NestedComposition.mp
index 3c2c0968df3f26ee30368b06dbe0b583882fedb4..61d9cc5a295e71853e314c72931c2fca98b10e2b 100644
--- a/Example05_CarRace_NestedComposition.mp
+++ b/Example05_CarRace_NestedComposition.mp
@@ -1,4 +1,6 @@
/* Example 05. Model of Car Race
+See also: Example 6: Car race model from the Monterey Phoenix System and
+Software Architecture and Workflow Modeling Language Manual
more coordination patterns:
- ordering of selected events in concurrent threads
diff --git a/Example06_UnreliableChannel_AssertionChecking.mp b/Example06_UnreliableChannel_AssertionChecking.mp
index 5bb6667aced8e06846fe7476bb8b702d51a76dca..5744e2f472f4bd7f9da8ebea413bb1dccb2c100f 100644
--- a/Example06_UnreliableChannel_AssertionChecking.mp
+++ b/Example06_UnreliableChannel_AssertionChecking.mp
@@ -1,4 +1,7 @@
/* Example 06. Model of Unreliable Channel
+See also: Example 10: Communicating via unreliable channel model from
+the Monterey Phoenix System and Software Architecture and Workflow
+Modeling Language Manual
Assertion checking, Communicating via unreliable channel.
diff --git a/Example07_UnconstrainedStack_TraceAnnotation.mp b/Example07_UnconstrainedStack_TraceAnnotation.mp
index 270ca3141e365f67e6dd835b0c29144964c998c3..c239a7fd77e9302e9be6b57f2e721cdf6e886859 100644
--- a/Example07_UnconstrainedStack_TraceAnnotation.mp
+++ b/Example07_UnconstrainedStack_TraceAnnotation.mp
@@ -1,4 +1,6 @@
/* Example 07. Model of Unconstrained Stack
+See also: Example 11: Testing/Debugging model’s behavior from the Monterey
+Phoenix System and Software Architecture and Workflow Modeling Language Manual
Trace annotation techniques
diff --git a/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp b/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp
index 436259dc5b0c76d4c77773d0a524d66bdfaa6264..bd35076f28ae4a7b2e04208944e4d3bd13e72616 100644
--- a/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp
+++ b/Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp
@@ -1,4 +1,6 @@
/* Example 08. Model of Employee Employer
+See also: Example 13: Business process model from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling Language Manual
The web site http://www.infoq.com/articles/bpelbpm
“Why BPEL is not the holy grail for BPM “
@@ -20,7 +22,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 Scopes 1 and up. Viewing of traces also includes
+a "Swim Lanes" option. Some box reshuffling may be needed to improve
+the trace layout.
==========================================================*/
diff --git a/Example09_PipeFilter_TraceAnnotationQueries.mp b/Example09_PipeFilter_TraceAnnotationQueries.mp
index e66badbd3f31ccce7da7d28776251ec6e724fde2..2dc69e66a587388a914ef20c38ab3e54a057db0a 100644
--- a/Example09_PipeFilter_TraceAnnotationQueries.mp
+++ b/Example09_PipeFilter_TraceAnnotationQueries.mp
@@ -1,5 +1,8 @@
/* Example 09. Model of Pipe Filter
-
+See also: Example 12: Pipe/Filter architecture model from the Monterey
+Phoenix System and Software Architecture and Workflow Modeling Language
+Manual
+
pipe/filter architecture model with 2 filters
assumptions:
@@ -8,7 +11,8 @@
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. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1, 2, 3, and 4. Viewing of traces
+also includes a "Swim Lanes" option.
Scope 4: 959 traces in approx. 6.1 sec.
==========================================================*/
diff --git a/Example10_PublishSubscribe_EventReshuffling.mp b/Example10_PublishSubscribe_EventReshuffling.mp
index a3ce1cdc4dd409122f8a60381bfe572396362cac..79f5909e5df91596974ca87778649e7c539caf3d 100644
--- a/Example10_PublishSubscribe_EventReshuffling.mp
+++ b/Example10_PublishSubscribe_EventReshuffling.mp
@@ -1,10 +1,15 @@
/* Example 10. Model of Publish Subscribe
+See also: Example 7: Publish/Subscribe architecture model
+from the Monterey Phoenix System and Software Architecture
+and Workflow Modeling Language Manual
Publisher sends a notification to all active Subscribers
when new information is available.
- Instructions: Run for Scopes 1, 2, and 3. Viewing of traces also includes a "Swim Lanes" option.
- Scope 3: 3813 traces in approx. 7.4 min.
+Instructions: Run for Scopes 1, 2, and 3. Viewing of traces
+also includes a "Swim Lanes" option.
+
+Scope 3: 3813 traces in approx. 7.4 min.
==========================================================*/
diff --git a/Example11_RingTopology_UserDefinedRelations.mp b/Example11_RingTopology_UserDefinedRelations.mp
index bc83e67d38fd54fe047346d0c7c9550c1f768a04..40a2234e9c18f373cd3fe657149a2569a21b0c93 100644
--- a/Example11_RingTopology_UserDefinedRelations.mp
+++ b/Example11_RingTopology_UserDefinedRelations.mp
@@ -1,13 +1,17 @@
/* Example 11. Model of Ring Topology
-
+See also: Example 16: User-defined relations from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling Language Manual
+
ring topology
an example of user-defined relation use
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. Viewing of traces also includes a "Swim Lanes" option.
- Scope 3: 1570 traces in approx. 31 sec.
+Instructions: Run for Scopes 1, 2, and 3. Viewing of traces also includes
+a "Swim Lanes" option.
+
+Scope 3: 1570 traces in approx. 31 sec.
==========================================================*/
diff --git a/Example12_CardiacArrestWorkflow_VirtualEvents.mp b/Example12_CardiacArrestWorkflow_VirtualEvents.mp
index 24768d332c373422d518d637a3e1dc4b2a7f093d..13b0b2d4504acd223741a7dd1856c279ab5cea00 100644
--- a/Example12_CardiacArrestWorkflow_VirtualEvents.mp
+++ b/Example12_CardiacArrestWorkflow_VirtualEvents.mp
@@ -1,4 +1,6 @@
/* Example 12. Model of Cardiac Arrest Workflow
+See also: Examples 9 and 14 on Workflow patterns from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling Language Manual
the web site
http://workflowpatterns.com/patterns/control/index.php
@@ -12,7 +14,8 @@ run in parallel. Once the first of these has completed, the triage task
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. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scope 1. Viewing of traces also includes a "Swim
+Lanes" option.
==========================================================*/
diff --git a/Example13_ConsumersSuppliers_DependencyTracking.mp b/Example13_ConsumersSuppliers_DependencyTracking.mp
index a35ac2401b68ca0fcedc1b5526834be87ea75516..ccf73ef9ced905bee67ce2b858ed073b61a1ee84 100644
--- a/Example13_ConsumersSuppliers_DependencyTracking.mp
+++ b/Example13_ConsumersSuppliers_DependencyTracking.mp
@@ -1,12 +1,17 @@
/* Example 13. Model of Consumers Suppliers
+See also: Example 29: Coordinating asynchronous threads and
+tracking event dependency from the Monterey Phoenix System
+and Software Architecture and Workflow Modeling Language Manual
Asynchronous coordination and dependency definition example.
user-defined relation related_to connects events within each
single Request_delivery -> Consume chain
-Instructions: Run for Scopes 1 and 2. Viewing of traces also includes a "Swim Lanes" option.
- Scope 2: 110 traces in approx. 38 sec.
+Instructions: Run for Scopes 1 and 2. Viewing of traces also
+includes a "Swim Lanes" option.
+
+Scope 2: 110 traces in approx. 38 sec.
==========================================================*/
diff --git a/Example14_ShoppingSpree_NumberAttributes.mp b/Example14_ShoppingSpree_NumberAttributes.mp
index d429ae89f03df9bb0a9662e1dc3d1bfad1253597..6fb4c3a08b3807c217e85beb98f295cfed8ddb59 100644
--- a/Example14_ShoppingSpree_NumberAttributes.mp
+++ b/Example14_ShoppingSpree_NumberAttributes.mp
@@ -1,6 +1,10 @@
/* Example 14. Model of Shopping Spree
+See also: Example 21: Attribute use from the Monterey
+Phoenix System and Software Architecture and Workflow
+Modeling Language Manual
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example15_BackpackWeight_IntervalAttributes.mp b/Example15_BackpackWeight_IntervalAttributes.mp
index a291d6a1dbb2db660ec688cf3ace10d49a312e49..2f39d7c8e5c2f1d4380e123dfb967f2f27c44c05 100644
--- a/Example15_BackpackWeight_IntervalAttributes.mp
+++ b/Example15_BackpackWeight_IntervalAttributes.mp
@@ -1,4 +1,7 @@
/* Example 15. Model of Backpack Weight
+See also: Example 22: Use of interval attributes from the
+Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
Use of interval attributes.
@@ -6,7 +9,8 @@
the total weight of 30 units.
There may be several instances of the same item.
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example16_StackBehavior_ProbabilityCalculationsType1.mp b/Example16_StackBehavior_ProbabilityCalculationsType1.mp
index 849e9489bb84ac2411c5c9f9f5e47a8ba8a87893..de9866c0eb038e63a3b77b99e48036ff79cdac81 100644
--- a/Example16_StackBehavior_ProbabilityCalculationsType1.mp
+++ b/Example16_StackBehavior_ProbabilityCalculationsType1.mp
@@ -1,4 +1,7 @@
/* Example 16. Model of Stack Behavior
+See also: Example 30: Type 1 probability from the Monterey
+Phoenix System and Software Architecture and Workflow
+Modeling Language Manual
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
@@ -13,7 +16,8 @@ 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. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also includes
+a "Swim Lanes" option.
==========================================================*/
diff --git a/Example17_SharedEvents_ProbabilityCalculationsType1.mp b/Example17_SharedEvents_ProbabilityCalculationsType1.mp
index 44b8550f5c63760533ba07bd884ac07271041db7..01054b78f256f70abbf1e0d82db56eb52e265f51 100644
--- a/Example17_SharedEvents_ProbabilityCalculationsType1.mp
+++ b/Example17_SharedEvents_ProbabilityCalculationsType1.mp
@@ -1,11 +1,15 @@
/* Example 17. Model of Shared Events
+See also: Example 31: Shared events with probabilities from
+the Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
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
must have c. Additionally, probabilities show how "SHARE ALL" increases
the chances of the shared event.
-Instructions: Run for Scope 1. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scope 1. Viewing of traces also
+includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp b/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp
index a7b421b3b8af3df13012e047558e2b082f949bbe..82ed9d5e5bc94bb6c263d86b007f391e5d1ef308 100644
--- a/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp
+++ b/Example18_RedGreen_BayesianProbabilityCalculationsType2.mp
@@ -1,4 +1,7 @@
/* Example 18. Model of Red Green
+See also: Example 32: Event probability calculations from
+the Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
Bayesian attribute example
@@ -13,7 +16,8 @@
since Type 1 assumes that probability of selecting an alternative is
constant for the whole derivation process.
- Instructions: Run for Scope 1. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scope 1. Viewing of traces also
+includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp b/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp
index 0173c2bc8d9c05e638ae6263b41fe01babcc32a6..a83edbaa673b90fda7c17fd9d3492d3eed5b732b 100644
--- a/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp
+++ b/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp
@@ -1,4 +1,7 @@
/* Example 19. Model of Stack Behavior
+See also: Example 33: Bayesian probability calculation
+from the Monterey Phoenix System and Software Architecture
+and Workflow Modeling Language Manual
An example of Bayesian probability calculation.
@@ -22,7 +25,8 @@
this will require to update the first step in p2 assignment (line 57)
it will become p2 := 1/(M + 1);
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example20_Activity_Diagram.mp b/Example20_Activity_Diagram.mp
index 3aeeb31a6fe7c3a916d0eae61dc68dc0e8b17b63..7220b38387fed8742ae1e1a5d23c842068a23912 100644
--- a/Example20_Activity_Diagram.mp
+++ b/Example20_Activity_Diagram.mp
@@ -1,10 +1,14 @@
/* Example 20. Model of Activity Diagram
+See also: Example 51: Activity diagram of a root event from
+the Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
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. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scope 1. Viewing of traces also
+includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example21_DataFlow_LocalReport.mp b/Example21_DataFlow_LocalReport.mp
index e3a7524961a30d9c4562fd88b6b8b6eaa5bff040..f35c208bf8509312947f2cd9fa988123cad97f7e 100644
--- a/Example21_DataFlow_LocalReport.mp
+++ b/Example21_DataFlow_LocalReport.mp
@@ -1,8 +1,12 @@
/* Example 21. Model of Data Flow
+See also: Example 39: Local Report within a single trace
+from the Monterey Phoenix System and Software Architecture
+and Workflow Modeling Language Manual
Local Report within a trace.
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example22_SimpleMessageFlow_GlobalReport.mp b/Example22_SimpleMessageFlow_GlobalReport.mp
index 0a65ba22a38e440be9f3627748be4b8f386c39c7..8892c171dabc2531a9fb3a30c45161762af07eb6 100644
--- a/Example22_SimpleMessageFlow_GlobalReport.mp
+++ b/Example22_SimpleMessageFlow_GlobalReport.mp
@@ -1,6 +1,11 @@
/* Example 22. Model of Simple Message Flow
+See also: Example 40: Global report assembled from the set
+of all available event traces from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling
+Language Manual
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example23_CarRace_LocalGraph.mp b/Example23_CarRace_LocalGraph.mp
index eb5591339de7eeddbec0ff5668ef84674382330c..19d6ba7dab6dc0d753006cfe0b3bde3ec384fe00 100644
--- a/Example23_CarRace_LocalGraph.mp
+++ b/Example23_CarRace_LocalGraph.mp
@@ -1,8 +1,13 @@
/* Example 23. Model of Car Race
+See also: Example 41: Graph extracted from a particular
+event trace (local trace view) from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling
+Language Manual
Local graph within the event trace.
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example24_Compiler_ComponentDiagram.mp b/Example24_Compiler_ComponentDiagram.mp
index 4a98981cd26d4031243b3a8eaeaaa1ee88649f3f..07d6655df0caed18eba439353b0036f17a874122 100644
--- a/Example24_Compiler_ComponentDiagram.mp
+++ b/Example24_Compiler_ComponentDiagram.mp
@@ -1,4 +1,7 @@
/* Example 24. Model of Compiler
+See also: Example 42: Graph in the Global view from the
+Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
Compiler front end, bottom-up parser
Lexer and parser in interactive mode.
@@ -8,8 +11,10 @@
The MP code for constructing UML-like Component Diagram
is reusable and can be copied/pasted into any MP model.
- Instructions: Run for Scope 1. Viewing of traces also includes a "Swim Lanes" option.
- Scope 1: 20 traces in approx. 3.1 sec.
+Instructions: Run for Scope 1. Viewing of traces also
+includes a "Swim Lanes" option.
+
+Scope 1: 20 traces in approx. 3.1 sec.
==========================================================*/
diff --git a/Example25_Graph_as_Data_Structure.mp b/Example25_Graph_as_Data_Structure.mp
index 40edc33eb8ce4b9eeb01921daf1b79e018a5eb04..542e2376d6d6be5e0cb3aea18b9027aedc3b59bc 100644
--- a/Example25_Graph_as_Data_Structure.mp
+++ b/Example25_Graph_as_Data_Structure.mp
@@ -1,9 +1,13 @@
/* Example 25. Model of Graph as Data Structure
+See also: Example 43: Accumulating and rendering statistics
+from event traces from the Monterey Phoenix System and
+Software Architecture and Workflow Modeling Language Manual
Accumulating and rendering statistics from event traces.
Graphs as container data structures
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example26_UnreliableMessageFlow_GlobalQuery.mp b/Example26_UnreliableMessageFlow_GlobalQuery.mp
index 5acf62d525c5564785d6555d8b85e7da0cc4b4ac..151bfde1fe42111c6bf57559fe003dbdf34319dd 100644
--- a/Example26_UnreliableMessageFlow_GlobalQuery.mp
+++ b/Example26_UnreliableMessageFlow_GlobalQuery.mp
@@ -1,4 +1,8 @@
/* Example 26. Model of Unreliable Message Flow
+See also: Example 46: Global query Model of unreliable
+message flow (related to Example 8) from the Monterey
+Phoenix System and Software Architecture and Workflow
+Modeling Language Manual
GLOBAL query
@@ -16,7 +20,8 @@ for scope 1), like:
ROOT Sender: (+<1..7> send +);
ROOT Receiver: (+<1..7> (receive |<<0.2>> does_not_receive) +);
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp b/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp
index 19bcfec5ca2896288c0ec67ab67a9ca9851fedde..e0552830ac257a2a6624ccb45ff3ca37fc8cee31 100644
--- a/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp
+++ b/Example27_AssemblingStatistics_Table_and_Bar_Chart.mp
@@ -1,9 +1,14 @@
/* Example 27. Model of Table and Bar Chart
-
+See also: Example 48: Assembling statistics about a current
+trace in a table and rendering it as a bar chart from the
+Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
+
Assembling statistics about a current trace in a TABLE and rendering it.
Table and bar chart example.
- Instructions: Run for Scope 1. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scope 1. Viewing of traces also
+includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example28_AssemblingStatistics_Histogram.mp b/Example28_AssemblingStatistics_Histogram.mp
index d7fdc6e3f2d70b1a66235c6f1be9f0b21f8c3ab3..da1f26651cfb46e2d0746a6500d5797f35771d7a 100644
--- a/Example28_AssemblingStatistics_Histogram.mp
+++ b/Example28_AssemblingStatistics_Histogram.mp
@@ -1,8 +1,13 @@
/* Example 28. Model of Histogram
-
+See also: Example 49: Histogram showing number of traces
+with probabilities within certain intervals from the
+Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
+
Histogram example
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example29_AssemblingStatistics_Gantt_Chart.mp b/Example29_AssemblingStatistics_Gantt_Chart.mp
index 305baa042e53481368cfa2d67aa8325058830d75..1689a5073e6526e90bc0b82c274f3af965bd4dca 100644
--- a/Example29_AssemblingStatistics_Gantt_Chart.mp
+++ b/Example29_AssemblingStatistics_Gantt_Chart.mp
@@ -1,8 +1,12 @@
/* Example 29. Model of Gantt Chart
-
+See also: Example 50: Gantt chart from the Monterey Phoenix
+System and Software Architecture and Workflow Modeling
+Language Manual
+
Gantt chart example
- Instructions: Run for Scope 1. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scope 1. Viewing of traces also
+includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example30_MicrowaveOven_ModelingModelChecking.mp b/Example30_MicrowaveOven_ModelingModelChecking.mp
index ddbf74f652ad6dd8bc59caae6051eceb18ef32f2..0c8f033ac9314b7b77df34702e43232c3ba59ef1 100644
--- a/Example30_MicrowaveOven_ModelingModelChecking.mp
+++ b/Example30_MicrowaveOven_ModelingModelChecking.mp
@@ -1,4 +1,7 @@
/* Example 30. Model of Microwave Oven
+See also: Example 27: Microwave oven demonstrating model
+checking from the Monterey Phoenix System and Software
+Architecture and Workflow Modeling Language Manual
example of finite state diagram behavior model,
CTL formula representation in MP, and model checking for a small scope.
@@ -27,8 +30,11 @@
and commands triggering state transitions,
following well known algorithm NFA -> RE.
- Instructions: Run for Scope 1. Viewing of traces also includes a "Swim Lanes" option.
- Scope 1: 28 traces (including 2 counterexamples) in approx. 1.4 sec.
+Instructions: Run for Scope 1. Viewing of traces also
+includes a "Swim Lanes" option.
+
+Scope 1: 28 traces (including 2 counterexamples) in approx.
+1.4 sec.
==========================================================*/
diff --git a/Example31_Aspect_Oriented_Paradigm.mp b/Example31_Aspect_Oriented_Paradigm.mp
index e52b8754f392a968ccf3327f592947740f13905a..38fc640a927366d1e9adac992e8312f460aa7b69 100644
--- a/Example31_Aspect_Oriented_Paradigm.mp
+++ b/Example31_Aspect_Oriented_Paradigm.mp
@@ -1,4 +1,7 @@
/* Example 31. Model of Aspect Oriented Paradigm
+See also: Example 2: Modeling Aspect-Oriented Paradigm from
+the Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
The COORDINATE operation supports a “cause-effect†refinement for
the behavior of two components and it bears a certain similarity
@@ -13,7 +16,8 @@ methods M1 and M2 as join points, and the aspect behavior requires
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. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example32_Petri_Net.mp b/Example32_Petri_Net.mp
index a13f23b97dcfbc2d5ae2ad97c7b8f498b2d17fd0..d3dadcf1fc92836247e768c62c0283d31f122c13 100644
--- a/Example32_Petri_Net.mp
+++ b/Example32_Petri_Net.mp
@@ -1,4 +1,7 @@
/* Example 32. Model of Petri Net
+See also: Example 28: Modeling Petri net from the Monterey
+Phoenix System and Software Architecture and Workflow Modeling
+Language Manual
modeling Petri net behavior
see the Petri net diagram in Sec. 2.16.2 in the MP v.4 Language Manual
@@ -6,8 +9,10 @@
to obtain in the Global view Petri net diagram
extracted from the event traces, run scope 2
- Instructions: Run for Scopes 1 and 2. Viewing of traces also includes a "Swim Lanes" option.
- Scope 2: 4 traces in approx. 6.6 sec.
+Instructions: Run for Scopes 1 and 2. Viewing of traces
+also includes a "Swim Lanes" option.
+
+Scope 2: 4 traces in approx. 6.6 sec.
==========================================================*/
diff --git a/Example33_ATMWithdrawal_StatechartView.mp b/Example33_ATMWithdrawal_StatechartView.mp
index b720314f2bd3b026f3a297a7cf23dffa0f0474be..ffe6639e64ff30f431ea708e7d491f2c4708eb75 100644
--- a/Example33_ATMWithdrawal_StatechartView.mp
+++ b/Example33_ATMWithdrawal_StatechartView.mp
@@ -1,8 +1,12 @@
/* Example 33. Model of ATM Withdrawal
+See also: Example 45: Extracting statechart view from MP
+model from the Monterey Phoenix System and Software
+Architecture and Workflow Modeling Language Manual
Extracting Statechart view from MP model.
- Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example34_FiniteStateDiagram_PathAnnotation.mp b/Example34_FiniteStateDiagram_PathAnnotation.mp
index 06e7dfa55e3f8e672d797a539ad17733760ead05..31c80b696742e8ce0896cb1957ce33d4c4a77ba9 100644
--- a/Example34_FiniteStateDiagram_PathAnnotation.mp
+++ b/Example34_FiniteStateDiagram_PathAnnotation.mp
@@ -1,4 +1,7 @@
/* Example 34. Model of Finite State Diagram with Path Annotation
+See also: Example 26: Modeling finite state machine from
+the Monterey Phoenix System and Software Architecture
+and Workflow Modeling Language Manual
example of finite state diagram behavior model,
contains non-deterministic transitions (from S1 with symbol a),
@@ -29,8 +32,10 @@
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. Viewing of traces also includes a "Swim Lanes" option.
- Scope 2: 30 traces in approx. 9.4 sec.
+Instructions: Run for Scopes 1 and 2. Viewing of traces
+also includes a "Swim Lanes" option.
+
+Scope 2: 30 traces in approx. 9.4 sec.
==========================================================*/
diff --git a/Example35_FiniteStateDiagram_PathDiagram.mp b/Example35_FiniteStateDiagram_PathDiagram.mp
index c2a67b048de3f6440f44b4cb3318739e09b33e4b..154b3d907ed3f21dfee9b9b5f0b354afadb1215b 100644
--- a/Example35_FiniteStateDiagram_PathDiagram.mp
+++ b/Example35_FiniteStateDiagram_PathDiagram.mp
@@ -1,10 +1,16 @@
/* Example 35. Model of Finite State Diagram with Path Diagram
+See also: Example 44: Adding paths and state transition
+diagram to the Finite Automaton behavior model from the
+Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
Adding path and state transition diagrams to
the Finite Automaton behavior model.
- Instructions: Run for Scope 2. Viewing of traces also includes a "Swim Lanes" option.
- Scope 2: 30 traces in approx. 11 sec.
+Instructions: Run for Scope 2. Viewing of traces also
+includes a "Swim Lanes" option.
+
+Scope 2: 30 traces in approx. 11 sec.
==========================================================*/
diff --git a/Example36_Authentication_SystemReuse.mp b/Example36_Authentication_SystemReuse.mp
index d7c98e61ceb4194251800be227b3fbe3926af711..2b92d3ca3c64e85cbf2c189c1b7eba7bc04f3f64 100644
--- a/Example36_Authentication_SystemReuse.mp
+++ b/Example36_Authentication_SystemReuse.mp
@@ -1,8 +1,15 @@
/* Example 36. Model of Authentication System
+See also: Example 36: Reuse of an authentication subsystem
+from the Monterey Phoenix System and Software Architecture
+and Workflow Modeling Language Manual
Authentication system's behavior for reuse with MAP operation.
-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.
+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.
============== reused MP code starts here ==================*/
diff --git a/Example37_Compiler1_ComponentReuse.mp b/Example37_Compiler1_ComponentReuse.mp
index e1282adb171a810d1215dd5d102db324531e1735..54396dff873613eb2941537c9f91d0fabadd94cd 100644
--- a/Example37_Compiler1_ComponentReuse.mp
+++ b/Example37_Compiler1_ComponentReuse.mp
@@ -1,11 +1,17 @@
/* Example 37. Model of Compiler 1
+See also: Example 34: Compiler’s front end in batch
+processing mode from the Monterey Phoenix System and
+Software Architecture and Workflow Modeling Language
+Manual
Compiler front end,
bottom-up parser
Lexer and parser in batch mode
-Instructions: Run for Scopes 1 and 2. Viewing of traces also includes a "Swim Lanes" option.
- Scope 2: 147 traces in approx. 1.8 sec.
+Instructions: Run for Scopes 1 and 2. Viewing of traces
+also includes a "Swim Lanes" option.
+
+Scope 2: 147 traces in approx. 1.8 sec.
==========================================================*/
diff --git a/Example38_Compiler2_ComponentReuse.mp b/Example38_Compiler2_ComponentReuse.mp
index 01d78de382101b83293f8660f341b61b0f3acd40..413e2cc2b07f6067c372369f484749ed44b8c48a 100644
--- a/Example38_Compiler2_ComponentReuse.mp
+++ b/Example38_Compiler2_ComponentReuse.mp
@@ -1,11 +1,16 @@
/* Example 38. Model of Compiler 2
+See also: Example 35: Compiler’s front end in incremental
+mode from the Monterey Phoenix System and Software
+Architecture and Workflow Modeling Language Manual
Compiler front end,
bottom-up parser
Lexer and parser in interaction mode
-Instructions: Run for Scopes 1, 2, and 3. Viewing of traces also includes a "Swim Lanes" option.
- Scope 3: 4860 traces in approx. 1.6 min.
+Instructions: Run for Scopes 1, 2, and 3. Viewing of traces
+also includes a "Swim Lanes" option.
+
+Scope 3: 4860 traces in approx. 1.6 min.
==========================================================*/
diff --git a/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp b/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp
index c585ce4d0dd8f3b9ca4eaefb0db2c8865888c88c..9c6d39ac80054a68568ce003d221303a1142e6fd 100644
--- a/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp
+++ b/Example39_Merging_Root_Events_to_Reduce_Run_Time.mp
@@ -1,4 +1,7 @@
/* Example 39. Model of Merging Root Events to Reduce Run Time
+See also: Example 37: Merging root events model from the
+Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
Complex MP models may have large number of root events with several
coordination operations performed on clusters of roots. This may be
@@ -26,7 +29,8 @@ derivation task we introduce a separate root event B_and_C to
encapsulate the trace segment derivation (including the coordination)
for B and C.
-Instructions: Run for Scopes 1 and 2. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and 2. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/
diff --git a/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp b/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp
index a51fdfb36b837223e16671238cd66a81824488f3..a30e66315ac6199ce7372973ef8f35a70cc07386 100644
--- a/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp
+++ b/Example40_ApplicationProcess_partitioningLargeSchemaIntoSeparateSchemas.mp
@@ -1,4 +1,7 @@
/* Example 40. Model of Application Process
+See also: Example 38: Application process model from the
+Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual
An applicant submits application and needs to get it approved by
the bureaucratic chain of two officials. If the first official approves,
@@ -8,7 +11,8 @@ approve/reject the application or request it reworked and resubmitted.
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. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces
+also includes a "Swim Lanes" option.
==========================================================*/