We construct a pattern composed of a mechanism called an event checker including several software patterns to check scenarios, i.e., the order of events and their timing constraints.
Using this graphic, the relevant scenarios can be determined by checking which scenario(s) is (are) closer to the present situation.
Additional hazards associated with compression system fail-to-check scenarios include risks associated with excessive flare loading and compressor rotor reverse rotation.
This function allows users to monitor and validate prediction results by manually checking the evolutionary scenarios of individual genes.
In order to check this scenario, it is assumed that small-cell BS operates in the location allowing for highest transmit power, i.e., 37.8 dBm.
To evaluate the influence of the repository cache, another measurement has been conducted that represents a more realistic scenario: checking all imported virtual machines for updates.
We did this using different values for Pr RF and RR RF and checking if the scenario tree model produced logical results.
As a consequence of what is discussed at the end of Section 3.1, the effect of metallic walls in the train scenario was first checked using numerical simulations.
These test scenarios allow checking the compliance of the Implementation Under Test (IUT) with specification.
Our focus is on ease of use in specifying, simulating and validating scenarios, and checking their desired properties efficiently.
