Development and Testing Clause Samples

The Development and Testing clause outlines the procedures and standards for creating and evaluating deliverables in a project. It typically specifies the responsibilities of each party during the development phase, the criteria for successful completion, and the process for conducting tests to ensure the deliverables meet agreed-upon requirements. This clause ensures that both parties have a clear understanding of expectations and quality benchmarks, reducing the risk of disputes over performance or acceptance of the final product.
POPULAR SAMPLE Copied 1 times
Development and Testing. First Union has finalized the initial development and testing of its Talking ATM project.
Development and Testing. Eleven has been, and currently is, engaged in the process of developing and testing a POS Pinpad with Integrated Tactually Discernable Keypad for use in 7-Eleven Stores.
Development and Testing. Washington Mutual, in conjunction with its principal ATM vendor, commenced in May 2000 and has developed and tested, in a controlled laboratory setting, Washington Mutual Talking ATMs.
Development and Testing. Wal-Mart has been, and currently is, engaged in the process of developing and testing a POS Terminal with Integrated Tactually Discernable Keypad for use in Wal-Mart Stores. Claimants have provided comments and suggestions to Wal- Mart in connection with the development and testing of this terminal. Claimants agree and acknowledge that installation of POS Terminals with Integrated Tactually Discernable Keypads in the manner set forth in this Agreement satisfies their Claims pursuant to any and all Access Laws.
Development and Testing. Commencing within ten (10) days of the Effective Date, Bank of America, in conjunction with its principal ATM vendor for California, will begin developing and testing, in a controlled laboratory setting, Bank of America Talking ATMs. Because of unique circumstances surrounding the implementation of the Model Bank Platform in California currently scheduled to take place in the third quarter of 2001, the Bank of America Talking ATMs that will be developed, pilot tested and rolled out during Phase I of the California rollout described in section 3.1(d) below will provide Persons with Vision Impairments independent access to the following Functions, to the extent that such Functions are available to sighted persons at the ATM Location where the pilot Talking ATM is to be installed: (i) transfers between a user’s accounts; (ii) deposits to a user’s accounts (iii) cash withdrawals from a user’s accounts; and (iv) cash withdrawals from a user’s credit card account when the ATM is accessed through the user’s credit card. The parties recognize that Bank of America’s principal ATM vendor for California may not have ready the volume control feature (described in section 1.5(1) above) for the California Talking ATM Development and Testing phase or Pilot Project. Bank of America will inform Claimants of the status of this feature at the meetings required by section 3.1(c) herein and will incorporate this feature into Bank of America Talking ATMs promptly after its becoming available from the ATM vendor.
Development and Testing. Prior to the Effective Date, UBOC, in conjunction with Diebold Corporation, its principal ATM vendor, has developed and tested, in a controlled laboratory setting, UBOC Talking ATMs. The UBOC Talking ATMs that have been developed and tested pursuant to this section provide Persons with Vision Impairments independent access to the following Functions: (i) account balance;
Development and Testing. MARIPOSA may consult with COMPANY regarding the development and manufacture of new Products to be governed by the terms of this Agreement. The parties shall separately agree as to the nature and costs for MARIPOSA ’s development and testing services. As MARIPOSA develops new Products for sale to COMPANY, it is understood and agreed that MARIPOSA shall have a period of ninety (90) days following final approval of the new Product by COMPANY to test the new Product for stability. If COMPANY requests MARIPOSA to ship the new Product prior to completion of the testing period, then COMPANY hereby agrees to release, indemnify, defend, and hold MARIPOSA (and its insurer) harmless from and against any and all claims or losses of any nature if a problem develops with the new Product. If this Agreement is terminated by COMPANY, or by MARIPOSA based upon COMPANY’s breach, MARIPOSA may seek reimbursement of the time and labor it expended for product development at the current Development Rate at the time of termination or breach of contract. The current rate at the date of this Agreement is $75.00 per hour.
Development and Testing. (a) ▇▇▇▇▇ Systems shall develop, test, and deliver the deliverables required to implement the capabilities, features and functions described under each Detailed FRD, which includes the Legacy Customizations by performing the tasks and other activities described in the applicable AD&Ds, except to the extent such tasks and activities are assigned to Newco in such AD&Ds. Newco shall perform the tasks and other activities assigned to Newco in the AD&Ds. (b) Each Party shall perform the unit, system, performance, quality assurance and other testing assigned to such Party for each capability, feature and function of the Legacy Customizations in accordance with the Detailed FRD relating to testing and the AD&D applicable to such capability, feature and function and the VRS Project Plan. Unless otherwise stated in the applicable Detailed FRD or the applicable AD&D, Newco shall be responsible for performing user acceptance tests in accordance with the mutually agreed test criteria and timeframes described in the applicable AD&D (which shall reflect the testing criteria and timeframes included in the Detailed FRD relating to testing). No element of the VRS Project will be placed into production until Newco has accepted such element. (c) If Newco is unable to perform any task, including but not limited to develop or testing any deliverable or system, in accordance with the VRS Project Plan because a ▇▇▇▇▇ Systems deliverable or task is delayed (whether due to tardiness or defects), the completion date for such task shall be extended by the number of days by which ▇▇▇▇▇ Systems’ deliverable is delayed. Similarly, if ▇▇▇▇▇ Systems is unable to perform any task in accordance with the VRS Project Plan because a Newco deliverable or task is delayed (whether due to tardiness or defects), the completion date for such task shall be extended by the number of days by which Newco’s deliverable is delayed. Notwithstanding the foregoing, each Party shall use reasonable commercial efforts to mitigate the impact of any such delays on the VRS Project Plan by (i) performing all tasks that do not require the delayed deliverable, and (ii) taking such other actions as are reasonably practicable. (d) Upon completion of testing in accordance with the applicable AD&D and the Detailed FRD relating to testing, ▇▇▇▇▇ Systems shall notify Newco, in writing, that the deliverables required under the VRS Project are complete and ready for testing. Following such notice, Newco’s VRS Project Manage...
Development and Testing. The COM DLL has been developed in Microsoft Visual C++ as a component object model dynamic link library to interface the Third Party Vendor's software with the Purchaser Satellite as per the specifications in Schedule "B". To test the COM DLL it was integrated into a Third Party Vendor's software. The integration was then setup in a live environment to read from and reply to the Purchaser Satellite. Two Third Party Vendors were chosen to complete the testing of the COM DLL: BNW Software (venue for live environment test was UCLA) and CMR Computer (venue for live environment test was a Ron Hemelgarn fitness ▇▇▇▇). ▇▇▇▇ sets of integrations and test installations were successful. Deliverables: - Development of COM DLL as per Schedule B specifications - Successful integration of COM DLL with two Third Party Vendors - Successful installation of Satellite controlled by COM DLL through Third Party Vendors' software PHASE 2: INTEGRATION
Development and Testing. Use of the Software strictly for non-production purposes, including development, evaluation, and internal testing. • Production Use: Deployment of the Software for any live or operational environment beyond development or testing purposes.