Software Deliverable Sample Clauses
The Software Deliverable clause defines the specific software products, components, or functionalities that a party is obligated to provide under the agreement. It typically outlines the scope, format, and delivery timeline for the software, and may include requirements such as documentation, source code, or compatibility standards. By clearly specifying what constitutes an acceptable deliverable, this clause ensures both parties have a mutual understanding of expectations and helps prevent disputes over the quality or completeness of the software provided.
POPULAR SAMPLE Copied 1 times
Software Deliverable. OpGen grants to HHT a limited, non-transferable, non-sublicenseable (except as set forth in Section 4.4(d)), and worldwide license, co-exclusive with OpGen, to use, practice, exploit, reproduce, distribute, perform, display, develop, make, have made, sell, offer for sale, and import the Software Deliverable in connection with Products in the Field. OpGen shall provide HHT with the object code and documentation of the Software Deliverable as may be amended from time to time, for use in the Product development and commercialization activities contemplated under this Agreement, and OpGen shall provide all assistance necessary to customize the Software Deliverable for use on the HHT cloud solution, including, if necessary, the source code required for such customization. OpGen shall not transfer or assign the copyright of the Software Deliverable and/or the copyright of a derivative work based on the Software Deliverable without HHT’s prior written consent, except as permitted in Section 10.7.
Software Deliverable. Acceptance testing is an iterative process designed to determine whether the Software deliverable performs the functions described in its approved Specifications and to discover and remove defects through repeated testing cycles. In the event of conflicts between Specifications and Software Documentation the Specifications will prevail.
2.8.3 The Contractor will work with the City and make a good faith effort to develop a test plan with the requisite details, understanding the level of detail required may change depending on the complexity of the requested software deliverable and to test each software deliverable.
Software Deliverable. The personal lines insurance policy management system to be developed by AmTrust as contemplated by the Initial Work Statement required to be delivered to GMACI.
Software Deliverable. (a) Provided that at the expiration of the Agreement as of the end of the Initial Term or thereafter (i) the total Development Fees and License Fees paid by GMACI pursuant to this Agreement exceed $100 million and (ii) GMACI is not in material breach of any provisions of this Agreement or any Work Statement and GMACI has paid and continues to pay in full all amounts due under this Agreement and all Work Statements, AmTrust shall (x) be deemed to have granted to GMACI a fully paid-up, perpetual, non-exclusive, non-transferable unlimited user and site license: (i) to use and interact with (solely as provided for in Section 2.2) the Software Deliverable for the Intended Purpose; (ii) to permit the usage of (solely as provided for in Section 2.2) the Software Deliverable by GMACI Affiliates and GMACI Authorized Users for the Intended Purpose; (iii) to use (solely as provided for in Section 2.2) the Documentation solely in connection with the operation of the Software Deliverable; (iv) the Source Code for the Software Deliverable and (v) subject to 9.4, ensure that, upon such expiration, that GMACI shall be able to continue to use the personal lines system for its Intended Purpose. To the extent that AmTrust provides GMACI software consisting of Other AmTrust Systems, AmTrust (x) shall be deemed to have granted to GMACI a fully paid-up, perpetual, non-exclusive, non transferable unlimited user and site license to such Other AmTrust Systems and (y) shall not be required to provide GMACI the Source Code for the Other AmTrust Systems.
(b) In the event of a Change of Control of ACAC, the license granted to GMACI in accordance with Section 4.2 (a) above shall be limited to the business of GMACI as it existed at the time of such Change of Control. For the purposes of this Section 4.2(b), the “business of GMACI as it existed at the time of such Change of Control” means the continuation of the business in a scope and manner consistent with the conduct of the business prior to such Change of Control.
Software Deliverable. Acceptance testing is an iterative process designed to determine whether the Software Deliverable performs the functions described in its approved Specifications and to discover and remove Defects through repeated testing cycles. “Specification” means the Requirements found at Exhibit E and any other written specifications delivered to the City by the Vendor during the course of the project or the Application Software Documentation. In the event of conflicts between Specifications and Application Software Documentation the Specifications will prevail. Vendor will work with the City and make a good faith effort to develop a test plan with the requisite details, understanding the level of detail required may change depending on the complexity of the requested software deliverable and to test each software deliverable (the “Acceptance Tests” or “Acceptance Testing”).
Software Deliverable. Acceptance testing is an iterative process designed to determine whether the Software Deliverable performs the functions described in its approved Specifications and to discover and remove Defects through repeated testing cycles. “Specification” means the Project Scope and Requirements found at Exhibit < >¸ and any other written specifications delivered to the County by the Independent Contractor during the course of the project or the Application Software Documentation. In the event of conflicts between Specifications and Application Software Documentation the Specifications will prevail. Independent Contractor will work with the County and make a good faith effort to develop a test plan with the requisite details, understanding the level of detail required may change depending on the complexity of the requested software deliverable and to test each software deliverable (the “Acceptance Tests” or “Acceptance Testing”).