CHANGE CONTRACT LANGUAGE Sample Clauses

CHANGE CONTRACT LANGUAGE. To express intended program changes, we extend a subset of JML [Xxxxx et al. 2005], the de facto lingua franca when giving checkable formal specifications to Java pro- grams. In fact, one of our goals in designing a change contract language is to be as close to an existing popular specification language as possible to lower the learning bar- rier, and our syntactic extension to JML is very limited. However, JML (or any other specification languages), to the best of our knowledge, is not expressive enough to ex- press program changes across two consecutive versions, and this requires to propose nontrivial semantic extensions. Notes on Expressivity. While the main objective of our change contract language is to specify behavioral changes that occur between two consecutive versions of a method, it is also possible to specify with this language accompanying structural changes such as adding/deleting method parameters or fields. While our change contract language captures the relationship among program variable values at the input/output points of the previous/updated program versions, it is not powerful enough to express temporal properties of changes in variable values, as in temporal logics. Lastly, as in JML, we are concerned only with sequential Java programs and do not consider multithreading. A change contract is specified above the signature of a method m as an annotation between “/*@ changed behavior” and “@*/”. We call such a method m the target method of a given change contract. We require that expressions used in a change contract, including method calls, must be free of side-effects and exceptions. Also, their execution must terminate. A change contract is maintained as a contract file (e.g., XXX.scc) separated from Java files.
AutoNDA by SimpleDocs

Related to CHANGE CONTRACT LANGUAGE

  • Contract Language The following language shall be included in contracts for City projects between the Consultant and any Subcontractors, vendors, and suppliers: Contractor shall not discriminate on the basis of race, gender, gender expression, gender identity, religion, national origin, ethnicity, sexual orientation, age, or disability in the solicitation, selection, hiring, or treatment of subcontractors, vendors, or suppliers. Consultant shall provide equal opportunity for Subcontractors to participate in opportunities. Consultant understands and agrees that violation of this clause shall be considered a material breach of the contract and may result in contract termination, debarment, or other sanctions.

  • Suggested Language The following provides a debarment and suspension clause. It incorporates an optional method of verifying that contractors are not excluded or disqualified. (1) This contract is a covered transaction for purposes of 2 C.F.R. pt. 180 and 2 C.F.R. pt. 3000. As such, the contractor is required to verify that none of the contractor’s principals (defined at 2 C.F.R. § 180.995) or its affiliates (defined at 2 C.F.R. § 180.905) are excluded (defined at 2 C.F.R. § 180.940) or disqualified (defined at 2 C.F.R. § 180.935). (2) The contractor must comply with 2 C.F.R. pt. 180, subpart C and2 C.F.R. pt. 3000, subpart C, and must include a requirement to comply with these regulations in any lower tier covered transaction it enters into. (3) This certification is a material representation of fact relied upon by the Participating Public Agency. If it is later determined that the contractor did not comply with 2 C.F.R. pt. 180, subpart C and 2 C.F.R. pt. 3000, subpart C, in addition to remedies available to the Participating Public Agency, the Federal Government may pursue available remedies, including but not limited to suspension and/or debarment. (4) The bidder or proposer agrees to comply with the requirements of 2 C.F.R. pt. 180, subpart C and 2 C.F.R. pt. 3000, subpart C while this offer is valid and throughout the period of any contract that may arise from this offer. The bidder or proposer further agrees to include a provision requiring such compliance in its lower tier covered transactions.

  • Sample Language The following provides a sample contract clause: Compliance with the Xxxxxxxx “Anti-Kickback” Act.

  • VERSION Each Quote will be governed under the version of this Agreement that is in place as of the “last updated” date indicated at the bottom of this document. For that reason, you should keep a copy of this document and make a note of the date indicated below when you accept a Quote.

  • Languages 20.1 The Proclamation of Sale, these conditions of sale and the Memorandum may have been translated and published in different forms and languages. In the event of any discrepancy, misstatement, omission or error appearing in the various forms or languages, this English version shall prevail.

  • English Language Controls Notwithstanding any translated version of this Agreement and/or specifications that may be provided to Registry Operator, the English language version of this Agreement and all referenced specifications are the official versions that bind the parties hereto. In the event of any conflict or discrepancy between any translated version of this Agreement and the English language version, the English language version controls. Notices, designations, determinations, and specifications made under this Agreement shall be in the English language.

  • Protocol No action to coerce or censor or penalize any negotiation participant shall be made or implied by any other member as a result of participation in the negotiation process.

  • Mandate Letter language The Funder will receive a Mandate Letter from the Ministry annually. Each Mandate Letter articulates areas of focus for the Funder, and the Ministry’s expectation that the Funder and health service providers it funds will collaborate to advance these areas of focus. To assist the HSP in its collaborative efforts with the Funder, the Funder will share each relevant Mandate Letter with the HSP. The Funder may also add local obligations to Schedule D as appropriate to further advance any priorities set put in a Mandate Letter.

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.‌ b. A description or identification of the statistical sampling software package used by the IRO.‌

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!