Model Checking for Multi-Models Sample Clauses

Model Checking for Multi-Models. ‌ The behavior of a single (discrete-event) system component depends on its definition of internal actions, its input variables and its internal state. Intu- itively, the component resides in some internal state until inputs arrive. It then executes one or more actions, which may potentially alter the internal state and some changes become visible at the output interfaces. This simple understanding of a component’s behavior directly leads to a straightforward representation of multi-models, which cannot interactive via shared states, but only through their interfaces. We define a system component formally as a tuple C = (O, S, II), where: • O denotes the operational semantics of the system component, • S = {s1, . . . , sn} denotes the internal state of the system component, • II denotes the set of input variables of the system component, and • IO denotes the set of output variables of the system component. The most import part of the representation of multi-models is the handling of interface variables. Input variables usually can freely be assigned values by the model checker. This is not necessarily the case when the system components are combined, because the outputs of one component may now serve as the inputs of another. Output variables of all system components thus become part of the internal system state; the occurrences of these xxxx- xxxxx as inputs in the operational semantics of a component are likewise replaced.