Update/Change Condition and Inference Rule Sample Clauses

Update/Change Condition and Inference Rule. Given a change contract (ϕ, ψ, θ ; ϕr,ψr,θ r) and two versions of a program that satisfy c1 c2, (σ1, h1, σ2, h2) c (σ1r , hr1, σ2r , h2r ), we check whether the given change contract is satisfied using the inference rule shown in Figure 5(d). We write c1 c2, (σ1, h1, σ2, h2) (ϕ, ψ, θ ; ϕr,ψr,θ r) in the conclusion part of the inference rule to mean that change contract (ϕ, ψ, θ ; ϕr,ψr,θ r) is satisfied in the context of configuration c1 c2, (σ1, h1, σ2, h2) .
AutoNDA by SimpleDocs
Update/Change Condition and Inference Rule. Given a change contract (ϕ, ψ, θ ; ϕr,ψr,θ r) and two versions of a program that satisfy c1 c2, (σ1, h1, σ2, h2) c (σ1r , hr1, σ2r , hr2), we check whether the given change contract is satisfied using the inference rule shown in Figure 5(d). We write c1 c2, (σ1, h1, σ2, h2) (ϕ, ψ, θ ; ϕr,ψr,θ r) in the conclusion part of the inference rule to mean that change contract (ϕ, ψ, θ ; ϕr,ψr,θ r) is satisfied in the context of configuration c1 c2, (σ1, h1, σ2, h2) . ▶ ▶ In order for a change contract to be satisfied, the precondition of the previous version must be satisfied beforehand at the pre-state of the previous version. Such a condition is expressed in the premise part of the rule as (σ1, h1) ϕ; we write (σ1, h1) ϕ if predicate ϕ is satisfied at state (σ1, h1). ▶ v ▶ In addition, one of postconditions of the previous version (recall that there are two kinds of postconditions, depending on whether the target method terminates normally) must also be satisfied at the post-state of the previous version. Such a condition is denoted in the inference rule as (σ1r , hr1) ψ (σ1r , hr1) θ . We say that the update condition is satisfied if the preceding two conditions hold true, as described in the second line of the inference rule. If the update condition holds, it means that a given input state (σ1, h1) triggers in the previous version an execution whose behavior is intended to be changed in the updated version. Once the update condition holds, we next check another condition we call the change condition to see whether the behavior of the execution of interest changes as intended. The change condition is described in the third line of the inference rule. To see whether the change condition is satisfied, we check the following two conditions. First, we ACM Transactions on Software Engineering and Methodology, Vol. 24, No. 3, Article 18, Pub. date: May 2015. 18:12 X. Xx et al. Table I. Rules to Fill in Omitted Clauses with Default Predicates Omitted clause Context Default predicate when ensured / Ewhen signaled false Ewhen signaled true when signaled / Ewhen ensured false Ewhen ensured true / E when required Erequires ϕr ϕr requires requires true always true ensures always true signals always true For explanation, refer to Section 3.2.4. ▶ ( || ⟩ ↓ ▶ check whether the precondition of the updated version is satisfied at the pre-state of the updated version (i.e., (σ2, h2) ϕr of the rule). Note we can assume that (σ2, h2) is isomorphic to (σ1, h1) because this is impli...

Related to Update/Change Condition and Inference Rule

  • - ISSUE IDENTIFICATION AND INFORMAL DISCUSSION The employee shall discuss the issue with the immediate supervisor on an informal basis to identify and attempt resolution of the employee’s issue within ten (10) business days following the day the issue arose. The employee shall have the affirmative responsibility to inform the supervisor that the issue is being raised pursuant to this grievance procedure. The immediate supervisor shall meet with the employee, secure clarification of the issue, consider the employee’s proposed solution, and discuss possible alternative solutions and/or other administrative remedies. The immediate supervisor shall inform the department’s personnel office, and the personnel director shall inform the union of the grievance. The immediate supervisor shall respond verbally within ten (10) business days following the meeting with the employee. Failure of the supervisor to respond within the time limit shall entitle the employee to process the issue to the next step.

  • Certification Regarding Debarment, Suspension, and Ineligibility (i) Paragraph 16.2, Governing Law;

  • Request for Redacted Information In the event of a public records or other disclosure request pursuant to Chapter 119, Florida Statutes, the Florida Constitution or other authority, to which documents that are marked as “Confidential” are responsive, the Department will provide the Contractor- redacted copies to the requestor. If a requestor asserts a right to the Confidential Information, the Department will notify the Contractor such an assertion has been made. It is the Contractor’s responsibility to assert that the information in question is exempt from disclosure under Chapter 119 or other applicable law. If the Department becomes subject to a demand for discovery or disclosure of the Confidential Information of the Contractor under legal process, the Department shall give the Contractor prompt notice of the demand prior to releasing the information labeled “Confidential” (unless otherwise prohibited by applicable law). The Contractor shall be responsible for defending its determination that the redacted portions of its response are confidential, proprietary, trade secret, or otherwise not subject to disclosure.

  • Progress Reports and Information When required, the Contractor shall submit to the Owner such schedule of quantities and costs, payrolls, bills, vouchers, correct copies of all subcontracts, statements, reports, correct copies of all agreements, correspondence, and written transactions with the surety on the performance bond that have any relevance to the Work, estimates, records, and other data as the Owner may request that concerns the Work performed or to be performed under this Contract. When requested by the Owner, the Contractor shall give the Owner access to its records relating to the foregoing. (See also Article 1.2.3, Audits.) The above reports shall include, but are not limited to, (a) written notice of dates by which specified Work will have been completed, (b) written notice of dates by which Non-Compliant Work will be made good, (c) written notice that Non-Compliant Work has been made good, (d) written notice as to the date or dates by which Work that has not been performed with equal steps and at the same rate required by the Overall Project Schedule shall have been brought into conformity with the Overall Project Schedule, (e) date by which any undisputed claim of a Subcontractor, Supplier, or laborer shall have been paid, (f) written advice regarding the nature and amount of any disputed claim of a Subcontractor, Supplier, or laborer, and (g) information regarding Work performed under Change Orders.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Reports and Information 17.1 At such times and in such forms as the CITY may require, there shall be furnished to the CITY such statements, records, reports, data and information as the CITY may request pertaining to matters covered by this Agreement.

  • Response/Compliance with Audit or Inspection Findings A. Grantee must act to ensure its and its Subcontractors’ compliance with all corrections necessary to address any finding of noncompliance with any law, regulation, audit requirement, or generally accepted accounting principle, or any other deficiency identified in any audit, review, or inspection of the Contract and the services and Deliverables provided. Any such correction will be at Grantee’s or its Subcontractor's sole expense. Whether Xxxxxxx's action corrects the noncompliance shall be solely the decision of the System Agency.

  • Certification Regarding Debarment, Suspension, Ineligibility and Voluntary Exclusion - Lower Tier Covered Transactions (a) The prospective lower tier participant certifies, by submission of this proposal, that neither it nor its principals is presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation in this transaction by any federal department or agency.

  • HHSC SPECIAL CONDITIONS The terms and conditions of these Special Conditions are incorporated into and made a part of the Contract. Capitalized items used in these Special Conditions and not otherwise defined have the meanings assigned to them in HHSC Uniform Terms and Conditions -Grant- Version 2.16.1

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