Augmentation Transformation Sample Clauses

Augmentation Transformation. ‌ Next, we introduce algorithms for translating a model with compound, selection, loop, etc. statements into a model with only variable declaration and expression 13 ▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇/bip2nusmv statements. We first describe Algorithm 2, which translates a single transition with an arbitrary statement into a set of states and internal transitions with only variable declaration, expression, and return statements. Then, we describe Algorithm 3, which translates an entire model with the help of Algorithm 2. Our augmentation algorithms are based on the small-step operational semantics of our supported Solidity Statements provided in Appendix A.3. Algorithm 2, called AugmentStatement, takes as input a Solidity statement, an origin, destination, and return state, and it creates a set of states and ▇▇▇▇- sitions that implement the input statement using only variable declaration, ex- pression, and return statements as actions. Note that before invoking this al- gorithm, Algorithm 3 removes the original transition between the origin and destination states; hence, this algorithm creates all transitions (and states) from scratch. If the statement is a variable declaration, event, or expression statement, then the algorithm simply creates a transition from the origin to the destina- tion state without any guards and having the statement as an action. If the statement is a return statement, then it creates a transition from the origin to the return state. Note that the return state is preserved by all recursive calls to AugmentStatement, and it is initialized with the destination of the original transition by Algorithm 3. If the statement is a compound, selection, or loop statement, Algorithm 2 creates a set of states and transitions. For a compound statement (i.e., list of statements), the algorithm creates a set of new states, each of which corre- sponds to the execution stage after an inner statement (except for the last one), and it invokes itself (i.e., AugmentStatement ) for each inner statement. For a selection statement with an else (i.e., false) branch, it creates two states, which correspond to the true and false branches. Then, it creates transitions to these states with the branch condition and its negation as guards, and invokes itself for both the true and false body statements. If the selection statement does not have an else branch, then the false branch is replaced by a simple transition to the destination state with the negation of the condition as a...

Related to Augmentation Transformation

  • Access Toll Connecting Trunk Group Architecture 8.2.1 If Reconex chooses to subtend a Verizon access Tandem, Reconex’s NPA/NXX must be assigned by Reconex to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center subtends as identified in the LERG. 8.2.2 Reconex shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from Reconex’s Customers. 8.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office Reconex utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the Tandem Verizon utilizes to provide Exchange Access in such LATA. 8.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow Reconex’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access tandem.

  • Project Implementation The Borrower shall:

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Disaster Recovery and Business Continuity The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).