Event-B Trace Semantics Sample Clauses

Event-B Trace Semantics. In this section we briefly present how traces of an Event-B model are constructed. Much more detailed treatment of the subject is given in [10] and [11]. An elementary step of a machine interpretation is the computation of the set of next states for some current event. For some event e the next states are found by selecting a set of suitable values for the event parameters and using them to characterise the possible next states vr. An Event-B ∃ · ∧ ∀ · ∧ ⟨⟩ ⟨ ⟩ machine may be understood as a relation T : Event S S : T =df pe (Ge(pe, v) Se(pe, v, vr)). Here pe, Ge, Se are the event parameters, guard and before-after predicate. T is a predicate character- ising a relation on system states: it is a total function from events to relations on states. A next event would start from a state produced by a previous event. This is expressed with the sequential composition operator ";": e1; e2 = v1 T (e1)[v1/vr] T (e2)[v1/v]. v1 is a vector of fresh names used to record the final state of e1 and pass it on to e2. The concept of sequential composition can be generalised to a chain of events. Operator seq performs a sequential composition over an event list: seq( ) = id(S) and seq( e t) = T (e); seq(t). From these definitions, the traces of a machine are formulated as all possible traces reachable from the initial machine state Init: traces(M) = {t | seq(t)[Init] /= } In the next section we use the traces semantics of flows and Event-B to define the consistency conditions for a model combining a flow expression and an Event-B machine.
Sample 1
AutoNDA by SimpleDocs
Event-B Trace Semantics. In this section we briefly present how traces of an Event-B model are constructed. Much more detailed treatment of the subject is given in [11] and [12]. An elementary step of a machine interpretation is the computation of the set of next states for some current event. For some event e the next states are found by selecting a set of suitable values for the event parameters and using them to characterise the possible next states vj. An Event-B machine may be e e e e e understood as a relation T : Event↔ S ↔ S: T =df ∃p · (G (p , v) ∧ S (p , v, vj)). ∀ · ∧
Sample 1
Event-B Trace Semantics. In this section we briefly present how traces of an Event-B model are constructed. Much more detailed treatment of the subject is given in [11] and [12]. An elementary step of a machine interpretation is the computation of the set of next states for some current event. For some event e the next states are found by selecting a set of suitable values for the event parameters and using them to characterise the possible next states v′. An Event-B machine may be e e e e e understood as a relation T : Event↔S ↔S: T =df ∃p · (G (p , v) A S (p , v, v′)). ∀ · A ⟨⟩ ⟨ ⟩ Here pe, Ge, Se are the event parameters, guard and before-after predicate. T is a predicate characterising a relation on system states: it is a total function from events to relations on states. A next event would start from a state produced by a previous event. This is expressed with the sequential composition operator ”;”: e1; e2 = v1 T (e1)[v1/v′] T (e2)[v1/v]. v1 is a vector of fresh names used to record the final state of e1 and pass it on to e2. The concept of sequential composition can be generalised to a chain of events. Operator seq performs a sequential composition over an event list: seq( ) = id(S) and seq( e t) = T (e); seq(t). From these definitions, the traces of a machine are formulated as all possible traces reachable from the initial machine state Init: traces(M ) = {t | seq(t)[Init] /= } In the next section we use the traces semantics of flows and Event-B to define the consistency conditions for a model combining a flow expression and an Event-B machine.
Sample 1

Related to Event-B Trace Semantics

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Unbundled Network Element Combinations 4.1 For purposes of this Section, references to “Currently Combined” Network Elements shall mean that the particular Network Elements requested by NewPhone are in fact already combined by BellSouth in the BellSouth network. References to “

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Unbundled Sub-Loop Concentration System (USLC 2.9.1 Where facilities permit and where necessary to comply with an effective Commission order, BellSouth will provide <<customer_name>> with the ability to concentrate its sub-loops onto multiple DS1s back to the BellSouth Central Office. The DS1s will then be terminated into <<customer_name>>’s collocation space. TR-008 and TR303 interface standards are available.

  • Loop Provisioning Involving IDLC 2.16.1 Where TWTC has requested an Unbundled Loop and AT&T uses IDLC systems to provide the local service to the customer and AT&T has a suitable alternate facility available, AT&T will make such alternative facilities available to TWTC. If a suitable alternative facility is not available, then to the extent it is technically feasible, AT&T will implement one of the following alternative arrangements for TWTC (e.g., hairpinning):

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Unbundled Sub-Loop Feeder 2.8.4.1 Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and cross-box (or other access point) that serves an end user location.

  • Interconnection Product Options Interconnection Customer has selected the following (checked) type of Interconnection Service:

  • Jointly Provided Switched Access Services 7.5.1 Jointly Provided Switched Access Service is described and governed by the FCC and state access Tariffs, Multiple Exchange Carrier Access Billing (MECAB) and Multiple Exchange Carrier Ordering and Design (MECOD) Guidelines and based on LERG routing, and is not modified by any provisions of this Agreement. Both Parties agree to comply with such guidelines. CenturyLink and CLEC agree that the originating, intermediate, and terminating LECs for switched access will cooperatively determine the Jointly Provided Switched Access arrangements in which all parties concur.

Time is Money Join Law Insider Premium to draft better contracts faster.