Three Sources of Change Contracts Sample Clauses

Three Sources of Change Contracts. Table III shows ten version changes from which we extract change contracts. We prepared change contracts from three different sources: (I) First, to reflect user intentions as faithfully as possible, we transformed bug reports to change contracts as we did in the overview section (Section 2). In fact, the first row of Table III corresponds to the example we used in Section 2. Notice the same bug number (i.e., 51668) shown in the third column. Meanwhile, the first and second columns show the first six Git snapshot IDs of the previous and updated systems, re- spectively. While the the first four rows of the table are collected by transforming bug reports, they are only partially effective in testing our dynamic CCC toolset. Although relevant tests are successfully generated in all four cases, these tests are either passed or abandoned (isomorphic input is not found sometimes due to the limit of our tool; see Section 6.4.4) without reporting a change contract violation. (II) To see the efficacy of our toolset in detecting change contract violations, we used incorrect program changes of Ant found in our previous study [Qi et al. 2012]. These four defective cases are shown between the 5th and 8th rows of the table. (III) Lastly, to see the efficacy of our test repair tool, we additionally collected two structural changes (method parameter 8xxxx://xxx.xxxxxx.xxx/. ACM Transactions on Software Engineering and Methodology, Vol. 24, No. 3, Article 18, Pub. date: May 2015. Table IV. The Experiment Results for Our Dynamic CCC Change Randoop Test generation Test repair Contract checking Old New Tfirst (s) Tfirst (s) # of tests/m # of errors # of fixes # of passes # of violations c39b90 2f95b7 0.4 0.4 1 0 0 0 0 32e66f f0e466 62 9 4 0 0 4 0 a84f2e 1de96b 32 0.9 58 0 0 6 0 cbda11 9a0689 >300 0.2 252 0 0 0 250 dfa59d de3f32 >300 1 79 0 0 0 79 5bee9d 1532f4 1 0.3 762 1239 1239 172 506 1de7b3 626f28c 5 1 183 263 263 0 183 3a1518 aef2f7 0.3 0.2 1209 1832 1832 1209 0 f87075 d17d1f 0.2 0.2 955 2 2 955 0 additions) from Ant. The two last rows of the table correspond to these cases. Note that structural changes were also found in two defective cases.
Sample 1
AutoNDA by SimpleDocs

Related to Three Sources of Change Contracts

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.

  • Deliverables for an Authorized User Agreement (Transaction Deliverables must be identified, as a measure of progress in the Authorized User Agreement. A Deliverable as a bulk number of hours is not permissible under the OGS Centralized Contract. Retainage As part of the Mini-Bid, the Authorized User may elect to retain a percentage of each individual Deliverable payment of no more than 20% until the acceptance of the complete Deliverable or project. This retainage may be reduced as described in the Mini-Bid, when the Contractor substantially reduces the time required from the timeframes negotiated between the Authorized User and the Contractor for the completion and acceptance of a Deliverable.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Housing.

  • Flexible Work Schedules (a) Academic Professional staff members throughout the University may have, as indicated below, flexible work schedules. For example, Academic Professionals often travel on University business and/or work evenings and weekends. A flexible work schedule is defined as having established working hours different from the standard 8:00 a.m. to 5:00 p.m. Monday through Friday schedule, to be followed by an employee for an agreed upon period of time.

  • MASTER CONTRACT TRANSITION Contractor represents and warrants that, in the event this Master Contract or a similar contract, is transitioned to another contractor (e.g., Master Contract expiration or termination), Contractor shall use commercially reasonable efforts to assist Enterprise Services for a period of sixty (60) days to effectuate a smooth transition to another contractor to minimize disruption of service and/or costs to the State of Washington.

  • Alternative Schedules An employee may work an alternative work schedule with the written permission of the employee’s Department Manager. The alternative work schedule may be ended by the Department Manager and the employee’s schedule changed to a different alternative work schedule or the standard work schedule. The District may change the employees work period when an employee begins and/or ends working an alternative schedule. The alternative work schedules are listed in the table below.

  • Transition Plan In the event of termination by the LHIN pursuant to this section, the LHIN and the HSP will develop a Transition Plan. The HSP agrees that it will take all actions, and provide all information, required by the LHIN to facilitate the transition of the HSP’s clients.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Shift Schedule The words "shift schedule" when used in this Agreement shall mean a timetable of the shifts and off days assigned to a position or group of positions which commences at the beginning of a pay period and includes one complete rotation of said shifts.

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