diff --git a/Example01_SimpleMessageFlow_EventCoordination.mp b/Example01_SimpleMessageFlow_EventCoordination.mp index c3eaa806dd0a1d2bc5b648b9e48211c0e3b1d946..2e0f661857d142468eb10561fd2bc0f79e81a925 100644 --- a/Example01_SimpleMessageFlow_EventCoordination.mp +++ b/Example01_SimpleMessageFlow_EventCoordination.mp @@ -8,7 +8,8 @@ a modified event trace, merging behaviors of Sender and Receiver and adding the PRECEDES relation for the selected send/receive pairs. The coordination operation behaves as a "cross-cutting" derivation rule. -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/Example01a_UnreliableMessageFlow_VirtualEvents.mp b/Example01a_UnreliableMessageFlow_VirtualEvents.mp index a76c3027a2fe5f95cdee6da8b007c762552f8f7e..d7a23e6b5f1144b4783f4a509031829118e4b2e3 100644 --- a/Example01a_UnreliableMessageFlow_VirtualEvents.mp +++ b/Example01a_UnreliableMessageFlow_VirtualEvents.mp @@ -3,7 +3,8 @@ 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. 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/Example02_DataFlow_EventSharing.mp b/Example02_DataFlow_EventSharing.mp index c83da70d44d59e5dad2f361f244bfba9990113fd..6459a5d3b677f0631b0d74722a8612a7a88dbacc 100644 --- a/Example02_DataFlow_EventSharing.mp +++ b/Example02_DataFlow_EventSharing.mp @@ -18,9 +18,10 @@ only event traces where corresponding event sharing is implemented. Event traces specified by the schema represent system’s emergent behavior, where behaviors of subsystems are influenced by the coordination. -This is a toy example of System_of_Systems emerging behavior modeling. +This is a toy example of System of Systems emerging behavior modeling. -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/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp b/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp index 455436bb9d8e410e97ff1bc5c4bbcd4c66686e13..c3433783b448bbdd55064e2685be235d43e17c1f 100644 --- a/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp +++ b/Example03_ATMWithdrawal_BehaviorOfEnvironment.mp @@ -21,7 +21,8 @@ By selecting a representative enough trace (containing all events and interactio like traces 2 or 3 for scope 1), and then collapsing root event, it becomes possible to view a traditional "box-and-arrow" architecture diagram, i.e. to visualize an architecture view. -Instructions: Run for Scopes 1 and up. "Sequence" mode yields views very similar to the UML or SysML Sequence Diagrams. Viewing of traces also includes a "Swim Lanes" option. +Instructions: Run for Scopes 1 and up. "Sequence" mode yields views very similar to the UML or SysML +Sequence Diagrams. Viewing of traces also includes a "Swim Lanes" option. ==========================================================*/ diff --git a/Example04_StackBehavior_EnsureCondition.mp b/Example04_StackBehavior_EnsureCondition.mp index edea262d9025701bf95036cccbcfaf87c3cc1fec..23db1978f378ebf1401c87681cf6e61fa71fc9e1 100644 --- a/Example04_StackBehavior_EnsureCondition.mp +++ b/Example04_StackBehavior_EnsureCondition.mp @@ -27,7 +27,8 @@ and demonstrates an example of combining imperative (event grammar) and declarative (Boolean expressions) constructs for behavior specification. -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/Example04a_StackBehavior_UserDefinedRelations.mp b/Example04a_StackBehavior_UserDefinedRelations.mp index 7ab3565dd4d6832c4644cd33750d2282e0335c97..b03b45dc1a3581dee2e5f6edf6599f49d9df40fe 100644 --- a/Example04a_StackBehavior_UserDefinedRelations.mp +++ b/Example04a_StackBehavior_UserDefinedRelations.mp @@ -17,7 +17,8 @@ as yet another kind of behavior composition, and demonstrates an example of combining imperative (event grammar) and declarative (Boolean expressions) constructs for behavior specification. -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/Example04b_QueueBehavior_UserDefinedRelations.mp b/Example04b_QueueBehavior_UserDefinedRelations.mp index 718e4065ba01ba217ed3dcec3aed07f30fee7d1e..7d9b8d31365f891eed81a4b031f9f8768107ee69 100644 --- a/Example04b_QueueBehavior_UserDefinedRelations.mp +++ b/Example04b_QueueBehavior_UserDefinedRelations.mp @@ -25,7 +25,8 @@ as yet another kind of behavior composition, and demonstrates an example of combining imperative (event grammar) and declarative (Boolean expressions) constructs for behavior specification. -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/Example05_CarRace_NestedComposition.mp b/Example05_CarRace_NestedComposition.mp index 3e7f545e1dc3927d369ab7631a276a70eaa64412..3c2c0968df3f26ee30368b06dbe0b583882fedb4 100644 --- a/Example05_CarRace_NestedComposition.mp +++ b/Example05_CarRace_NestedComposition.mp @@ -6,7 +6,8 @@ more coordination patterns: - one-many coordination. -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/Example06_UnreliableChannel_AssertionChecking.mp b/Example06_UnreliableChannel_AssertionChecking.mp index 956c49f6cc6c9b6c2bfa0167e43ac99311aa738c..5bb6667aced8e06846fe7476bb8b702d51a76dca 100644 --- a/Example06_UnreliableChannel_AssertionChecking.mp +++ b/Example06_UnreliableChannel_AssertionChecking.mp @@ -20,7 +20,8 @@ if the property should always hold, it makes sense to convert it into the ENSURE condition. - 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/Example07_UnconstrainedStack_TraceAnnotation.mp b/Example07_UnconstrainedStack_TraceAnnotation.mp index a8ac6e47fcdc4b506c07d45d6b93b89aa462cdb5..270ca3141e365f67e6dd835b0c29144964c998c3 100644 --- a/Example07_UnconstrainedStack_TraceAnnotation.mp +++ b/Example07_UnconstrainedStack_TraceAnnotation.mp @@ -17,7 +17,8 @@ might violate certain property, and how to annotate these particular 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. 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. ==========================================================*/