t in state ready. Select View > Command Window: you see that the processes AtoB:1 and BtoA:1 are in state start. F. Press the Navigator button. In the Navigator window, double-click two times on Next 1 to execute the start transitions of AtoB and BtoA, as shown in Figure 5.7. Navigator Navigator Navigator No up node Up 1: Up 1: Transition START Transition START Pld : AtoB:1 Pld : BtoA:1 Next 1: State : start state State : start state Transition START Pld : AtoB:1 State : start state Next 1: Next 1: Transition START Transition START Pld : BtoA:1 Pld <<Block DLCa>> State : start state dispatch:1 State : start state Figure 5.7 Starting processes AtoB and BtoA Automatic Observation of Simulations 117 G. In the Validator command line, enter: Evaluate-Rule state (AtoB: 1) =ready and state (BtoA: 1) =ready As expected, the Validator answers: Evaluating rule: ( ( state ( AtoB:1 ) = ready) and (state ( BtoA:1 ) = ready ) ) User-defined rule satisfied. You can check in the Command Window that the processes AtoB and BtoA are in state ready. We have executed the transitions manually using the Navigator; we will see later that the transitions can also be executed automatically by the Validator, using several algorithms such as exhaustive simulation: then reports are automatically generated each time the user-defined rule is satisfied. 5.2.1.3 More user-defined rules Here are some more user-defined rules that you can enter in the Validator as indicated previously. To detect that variable fool in process AtoB contains 4: Define-Rule AtoB: 1->fool = 4 To detect when the first signal in the input queue of process AtoB is v76frame: Define-Rule sitype (signal (AtoB:1) =V76frame To detect if process AtoB has exactly one instance: Define-Rule instno (AtoB) = 1 To detect if a process input queue contains more than one signal: Define-Rule maxlen ( ) > 1 To detect that process AtoB has not created any process instance (rule always satisfied in our model): Define-Rule offspring (AtoB:1) = Null As you can see, several conditions in the SD