m saved Figure 7.42 The Organizer showing the observer obs D. In the Organizer, select the SDL system V76test and press the Validate button. E. In the Validator, enter the command: define-observer obs1 This command tells the Validator to execute obs1 as an observer instead of a regular process. F. Select Options1 > Report : Abort, and choose Assertion. After one observer report, the simulation will stop. G. Press on Bit State, the Validator displays: Search depth : 100 Hash table size : 1000000 bytes Exhaustive Simulation 221 Bit state exploration statistics * No of reports: 2. Generated states: 195. Truncated paths: 0. Unique system states: 147. Size of hash table: 8000000 (1000000 bytes) The simulation is terminated because the Validator has encountered a global state where the observer process obs1 has called the procedure Report. The Report Viewer appears, as illustrated in Figure 7.43, showing two reports. To view the corresponding MSC trace, double-click on the lower box in the Report Viewer. Report Viewer 2 reports 1 MaxQueueLength 1 Assertion Assertion is false: uData in A= 55 Depth: 94 Figure 7.43 The Report Viewer showing that the assertion is reached 7.4 CASE STUDY WITH OBJECTGEODE You will run the exhaustive simulation on the V.76 SDL model to discover errors auto- matically, and much faster and with much better dynamic coverage than with interactive or random simulation. 7.4.1 One second to detect missing save of v76frame 7.4.1.1 Start the Simulator A. Open the model contained in v76.pr with the SDL Editor. Be sure to use the last version of v76.pr, including the two corrections mentioned in the previous chapters: Input signal DLCstopped added under state waitUA in process dispatch. Process dispatch goes to state ready instead of state waitUA after transmitting L_Release- B. With a text editor, open the file v76. startup and remove the comment delimiter - -- before the line source v76_feed.wri, preventing the feed commands execution, mentioned in Chapter 6. 222 Validation of Communications Systems wi