Acceptance Testing of Software. Immediately upon completion of each development phase set forth in the Development Plan's delivery schedule, Developer shall deliver and install the Software and shall deliver all documentation and other materials required to be provided in accordance with the delivery schedule. Customer shall have [NUMBER] days from the delivery of the Software to inspect, test and evaluate it to determine whether the Software satisfies the acceptance criteria in accordance with procedures set forth in the Development Plan, or as established by Developer and approved by Customer prior to testing. If the Software does not satisfy the acceptance criteria, Customer shall give Developer written notice stating why the Software is unacceptable. Developer shall have [NUMBER] days from the receipt of such notice to correct the deficiencies. Customer shall then have [NUMBER] days to inspect, test and reevaluate the Software. If the Software still does not satisfy the acceptance criteria, Customer shall have the option of either: (1) repeating the procedure set forth above, or (2) terminating this Agreement pursuant to the section of this Agreement entitled "Termination." If Customer does not give written notice to Developer within the initial [NUMBER]-day inspection, testing and evaluation period or any extension of that period, that the Software does not satisfy the acceptance criteria, Customer shall be deemed to have accepted the Software upon expiration of such period. Upon completion of the final development phase set out in the Development Plan, acceptance testing shall be performed on the Software in its entirety to determine whether the Software satisfies the acceptance criteria and operates with internal consistency. Customer shall have [NUMBER] days to perform such tests. If the completed Software does not satisfy the acceptance criteria, the parties shall follow the acceptance procedures described in the preceding paragraph If and when the acceptance tests establish the Software delivered upon completion of any phase of development complies with the acceptance criteria, Customer shall promptly notify Developer that it accepts the delivered Software.
Acceptance Testing of Software. 11. Training (optional) 12. Maintenance.(optional) 13. Ownership of Software.
Acceptance Testing of Software. 7.1 The Customer will receive fifteen (15) days prior to the agreed date of delivery of the Software in final form for the purposes of inspecting, testing and evaluating the Software in order to determine whether the Software satisfies the acceptance criteria in accordance with procedures set out in Functional Specifications set out in the Development Plan, or as otherwise agreed in writing by between the Developer and the Customer prior to testing.
Acceptance Testing of Software. In accordance with the applicable Schedules, the parties to this Agreement shall execute Acceptance Test Plan(s) which shall set forth the agreed upon acceptance test criteria for the Software’s conformity with the Documentation. Said Acceptance Test Plan(s) shall be PRIMAL MASTER SOFTWARE LICENSE AGREEMENT (Monthly) incorporated by Reference into this Agreement. In the event that the parties have not executed such Acceptance Test Plan within such time frame, Licensee shall have the right to terminate this Agreement with Licensee having no further liability or obligation, in which event Primal shall immediately refund all sums paid by Licensee to Primal under this Agreement. Upon completion of the Installation in the Hosted Environment pursuant to Section 1.5 Primal shall provide a Notice of Installation. Within ten (10) days of Notice of Installation, , Licensee shall start to test and evaluate the Installation, as installed, to determine whether it materially conforms to the to the criteria set forth in the Acceptance Test Plan as so installed. Within twenty (20) days of Notice of Installation, Licensee shall complete Acceptance Testing. If Licensee determines in its sole discretion that the Installation does not pass such acceptance testing, Licensee shall notify Primal in writing that it is rejecting such Installation, specifying sections of the Acceptance Test Plan with which the Installation does not comply and describing the alleged deficiencies in reasonable detail. Within five (5) days of Licensee’s rejection notice to Primal, and at no charge, Primal shall correct any such deficiencies. Licensee shall then re-evaluate such Installation to determine whether the Installation satisfies such acceptance testing (“Correction Process”). If Primal does not, in Licensee’s discretion, remedy the deficiency: (a) Licensee may elect to allow Primal to repeat the Correction Process until Licensee accepts the Installation, or (b) Licensee may terminate this Agreement with Licensee having no further liability or obligation, in which event Primal shall immediately refund all License and hosting fees paid by Licensee to Primal under this Agreement. Upon accepting the Installation, Licensee shall provide a written notice of acceptance to Primal (“Notice of Hosted Software Acceptance”), the form of which shall be set forth in the Acceptance Test Plan. Licensee, at its sole discretion, may provide a Notice of Provisional Acceptance, the form of which shall be set for...
