CHANGE CONTRACT LANGUAGE Clause Samples

CHANGE CONTRACT LANGUAGE. To express intended program changes, we extend a subset of JML [▇▇▇▇▇ 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.
View SourceView Similar (2)

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.

  • Change Control All systems processing and/or storing PHI COUNTY discloses to 14 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 15 must have a documented change control procedure that ensures separation of duties and protects the 16 confidentiality, integrity and availability of data.

  • Sample Language The following provides a sample contract clause: Compliance with the ▇▇▇▇▇▇▇▇ “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.