Computation Constraint Sample Clauses

Computation Constraint. Computation constraints provide support for the declarations of computation restrictions. They are useful for defining the required logical transformations from input data to output data, as well as the expected causal sequences across such data transformations. Computation constraints are comparable with the UML activity and sequence behavior specification. See Figure 13 for an overview of the related meta-model definitions. A specification of computation constraints is based on the following constructs:  ComputationConstraint – the modeling construct for grouping the transformation and transformation path declarations in a behavior constraint.  LogicalTransformation – the modeling construct for the declarations of logical computation transformations that determine some out-data (out) by processing some in- data (in) and local-data (contained). Such data are defined in terms of behavior attributes (Attribute). The corresponding value bounds of such data that must be hold before, after, and during the executions of a logical transformation are given by pre-, post-, and invariant conditions respectively. A logical transformation can also have time invariants (timeInvariants), stating the duration bounds when the transformation takes place. If a logical transformation is externally accessible (isClientServerInterface == true), it represents the operations declared in client-server interfaces (clientServerInterfaceOperation). A logical transformation can also have subordinate computation constraints (subComputationConstraint). (The expression attribute (expression) is a placeholder for the upcoming support for expressions of computation logics)  TransformationOccurrence – the modeling construct for the declarations of invocations of logical transformations as the effects of state transitions and control flows. A transformation occurrence can also have a time condition (timeCondition), stating the time instances when the invocation happens. If a logical transformation is invoked, its in-data will be assigned with particular values by the invocation context (inQuantification). As the consequence of transformation, the out-data will also be assigned with particular value (outQuantification). class ComputationConstraint EAElement ehaviorConstraint 0..* FunctionModeling::Operation BehaviorInstantiationParameter EAElement Attribute + isExternVisible :boolean = false +clientServerInterfaceOperation 0..* +compuationConstraint 0..* * +out * +in {ordered} {ordered} ...
Sample 1
AutoNDA by SimpleDocs

Related to Computation Constraint

  • Computation of Overtime In computing overtime a period of thirty (30) minutes or less shall be counted as one-half (½) hour and a period of more than thirty (30) minutes but less than sixty (60) minutes shall be counted as one (1) hour.

  • DAF Construction The DAF shall be designed and constructed in accordance with Good Utility Practice. Within one hundred twenty (120) Calendar Days after the Commercial Operation Date, unless the Developer and Connecting Transmission Owner agree on another mutually acceptable deadline, the Developer shall deliver to the Connecting Transmission Owner and NYISO “as- built” drawings, information and documents for the DAF, such as: a one-line diagram, a site plan showing the Large Generating Facility and the DAF, plan and elevation drawings showing the layout of the DAF, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Developer’s step-up transformers, the facilities connecting the Large Generating Facility to the step-up transformers and the DAF, and the impedances (determined by factory tests) for the associated step-up transformers and the Large Generating Facility. The Developer shall provide to, and coordinate with, Connecting Transmission Owner and NYISO with respect to proposed specifications for the excitation system, automatic voltage regulator, Large Generating Facility control and protection settings, transformer tap settings, and communications, if applicable.

  • Governing Law; Construction This Agreement and any claim, counterclaim or dispute of any kind or nature whatsoever arising out of or in any way relating to this Agreement (“Claim”), directly or indirectly, shall be governed by, and construed in accordance with, the laws of the State of New York. The section headings in this Agreement have been inserted as a matter of convenience of reference and are not a part of this Agreement.

  • During Construction Upon request of the Owner the Contractor shall submit written proposals for unit prices to be applied in the event Change Order Work is authorized by the Owner to be performed under Case (b).

  • ICIF Construction The ICIF shall be designed and constructed in accordance with Good Utility Practice. Within one hundred twenty (120) Calendar Days after the Commercial Operation Date, unless the Parties agree on another mutually acceptable deadline, Interconnection Customer shall deliver to Transmission Provider and Transmission Owner “as-built” drawings, information and documents for the ICIF, such as: a one-line diagram, a site plan showing the Generating Facility and the ICIF, plan and elevation drawings showing the layout of the ICIF, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer’s step-up transformers, the facilities connecting the Generating Facility to the step-up transformers and the ICIF, and the impedances (determined by factory tests) for the associated step-up transformers and the Generating Facility. Interconnection Customer shall provide Transmission Provider and Transmission Owner with Interconnection Customer’s specifications for the excitation system, automatic voltage regulator, Generating Facility control and protection settings, transformer tap settings, and communications, if applicable.

  • Interpretation; Construction The headings set forth in this Agreement are for convenience only and shall not be used in interpreting this Agreement. This Agreement has been drafted by legal counsel representing Company, but Executive has participated in the negotiation of its terms. Furthermore, Executive acknowledges that Executive has had an opportunity to review and revise the Agreement and have it reviewed by legal counsel, if desired, and, therefore, the normal rule of construction to the effect that any ambiguities are to be resolved against the drafting party shall not be employed in the interpretation of this Agreement.

  • Advice on Construction Progress To each Change Order which grants an extension in the Contract Time, the Design Professional shall attach its Advice on Construction Progress, in the format provided in the Forms Packet, and provide a copy to the CM/GC.

  • Special Construction If, after an order is placed, Xxxxxxx finds that third-party special construction services are needed to build, configure or install any additional facilities and/or equipment necessary for Verizon to provide Access service, Verizon will notify the Customer of any such special construction charges. If Customer does not accept the special construction charges, Customer may terminate the order(s) affected by the special construction charges, with no cancellation fee(s).

  • Cost of Construction 1. During the Schematic Design, Design Development, and Construction Document Phases, the ARCHITECT’s estimates of Construction Cost shall be reconciled against the Budget approved by the DISTRICT pursuant to Article IV, Section 2.

  • General Construction Obligations (a) Without limiting Section 10.3:

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