r, testlops.msc and xid1.msc. E. Press the Build button: this checks your SDL model and the two MSCs and translates the SDL model and the MSCs into C code, to produce the executable file v76.sim. 5.3.3.3 Replay the simulation scenario test1 A. Press the Execute button to start the Simulator. The Simulator main window appears. B. In the Simulator, select View > Hierarchy: as depicted in Figure 5.58, you now get a third area containing observation. It corresponds to the MSCs xid_a and v76_and contained in the files xid1.msc and testlops.msc. C. Unfold the observation part as in Figure 5.58, select xid_a and press the button Track: the Editor opens a window showing the MSC xid_a. Double-click if necessary in the Editor to display the content of xid D. Do the same for the MSC v76_and, double-click on data_a2b in the Framework area, and select Window > Tile Horizontally to obtain the disposition shown in Figure 5.59. E. Replay a Simulation scenario: select File > Scenario > Load, choose testl.scn, and press the Redo: All Simulator button15: at Step 23, the simulation should stop, and display: SUCCESS state reached in scenario xid_a It proves that the SDL simulation performed is identical to the behavior described in the observer MSC xid_a. 15 In case the step number and SO on are no longer displayed in the Simulator trace area, press on Traces: Defaults. Automatic Observation of Simulations 149 Hierarchy Browser Locate observation Track xid_a v76_and Create Watch Add to Watch Stop if Print v76test Reset Coverage Figure 5.58 The Simulator Hierarchy Browser with two observers Important: if the MSC tracking does not work or no success is reached, unload the MSC from the Editor, open the .msc file with a text editor and remove all the occurrences of VIA <some_name>. F. Continue replaying the scenario: press the redo Simulator button to reach Step 26, where you should see the same situation as in Figure 5.59. In this figure, the bold horizontal bar shows that the next SDL event expected by the MSC data_a2b_0 is an output o