Software Deliverables. Where the Deliverables include Software
Software Deliverables. A. AMI shall deliver to LICENSEE one (1) copy of AMI Technology following receipt of an executed copy of this Agreement and payment of all fees and other charges due upon execution hereof. The access granted hereby shall be strictly limited to the location(s) and designated individuals specified by Licensee in Exhibit B hereto unless otherwise agreed in writing by AMI.
Software Deliverables. To the extent that Supplier is providing software, including software development services as set forth in a Schedule for JPMC, Supplier shall demonstrate the maturity of controls in its development process by providing JPMC with applicable documentation and/or artifacts that the following software development controls are in place for the scope of the Deliverables being provided to JPMC hereunder which may include, to the extent agreed in the Schedule, the following: (i) security requirements in the requirements phase of the software development life cycle; (ii) application architectural framework(s) designed for resiliency; (iii) static code analysis during development; (iv) dynamic scanning in the quality assurance or build process; (v) manual penetration testing, and (vi) security vulnerability management. If Supplier is unable to provide any of the documentation or artifacts described above, then before Supplier delivers any Deliverable to a JPMC Entity or a Recipient, the following shall be required: (x) a dynamic scan of Supplier’s developed code in a JPMC quality assurance environment, or (y) a third party provided scan of the binaries in a run time environment (the cost of such scan to be at Supplier’s sole cost and expense).
Software Deliverables. 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 Nonconformities through repeated testing cycles. As used in this Agreement, “Nonconformity” means a reproducible condition in a Software Deliverable that prevents the Software Deliverable from performing the functions described in its Specifications such that the Software Deliverable does not operate or cannot be used in a production environment. At least forty-five (45) days prior to the date on which CGI is scheduled to deliver any Software Deliverable to Customer, Customer will deliver for CGI’s review proposed testing procedures for the Software Deliverable, including without limitation the detailed test scripts, test cases, test data and expected results. At least thirty (30) days prior to the date on which CGI is scheduled to deliver the Software Deliverable to Customer, the parties will agree upon the testing procedures for the Software Deliverable (the “Acceptance Tests” or “Acceptance Testing”).
Software Deliverables. [******] The Developed Software to be provided under this SOW shall be as follows: [******] 5 Change Request / Change Management [******]
Software Deliverables. Unless expressly addressed elsewhere in this Agreement, with respect to each software deliverable from First Data, First Data represents and warrants that for the Table of Contents FINAL entire Term following acceptance of the deliverable by RCSI, the deliverable will conform to its Specifications, will be properly installed, operate properly and be error free. To the extent a deliverable does not comply with the foregoing, First Data will correct such problem(s) at no cost and at no loss of resources to RCSI.
Software Deliverables. To the extent that Supplier is providing or using deployed software, whether in any JPMC’s, Supplier’s or any other test or production environment, or providing any software development services for JPMC, Supplier shall demonstrate the maturity of controls in its development process. In conjunction with delivery of the software, Supplier agrees to complete a vBSIMM assessment and provide to JPMC applicable documentation and/or artifacts which substantiate that the following software development controls are in place for the scope of the Deliverables being provided to JPMC hereunder: (i) security requirements documented during the requirements phase of the software development life cycle; (ii) architectural framework(s) designed for resiliency and security; (iii) static code analysis during development (secure code review of the entire code base based on, at a minimum, the Open Web Application Security Project (OWASP) Top 10 and SysAdmin, Audit, Networking, and Security Institute (SANS) Top 25 software security risks or comparable replacement); (iv) dynamic scanning of web-facing applications and penetration testing of internal applications, using industry standard testing methodologies during the build process or quality assurance process; (v) open source code used in Supplier-provided applications must be appropriately licensed, inventoried and evaluated for security defects, and (vi) security vulnerability management. If Supplier is unable to substantiate that the software is free of material security defects (i.e., no critical or high risk defects) through the above assessment, Supplier will conduct a software vulnerability scan (using an industry standard tool, e.g., Veracode), or submit to application scanning from a JPMC-approved vendor, and (x) share the detailed results of that scan with JPMC; (y) to the extent that scan identifies any critical or high risk vulnerabilities, Suppler will remediate those vulnerabilities before implementation of the software into production (whether the software is hosted by JPMC, Supplier or a third party on behalf of either); and (z) develop and implement remediation plan(s) to address any other vulnerabilities to JPMC’s reasonable satisfaction (such plan to be provided to JPMC) with the remediation occurring as soon as reasonably practicable, not to exceed six months of the discovery of such vulnerabilities. If Supplier provides an externally facing application as part of the Services (“Externally Facing Applicatio...
Software Deliverables. At least 30 days prior to the date on --------------------- which Cambridge Technology is scheduled to deliver any Software deliverable to Client for testing (or by such other date as the Statement of Work or Task Order may specify), Cambridge Technology will deliver for Client's review proposed testing procedures for the Software deliverable as required by the Task Order. At least 15 days prior to the date on which Cambridge Technology is scheduled to deliver the Software deliverable to Client (or by such other date as the Statement of Work or Task Order may specify), the parties will agree upon the testing procedures for the Software deliverable (the "Acceptance Test Plan"). The purpose of the Acceptance Test Plan will be to determine whether the Software deliverable performs the functions described in its approved specifications and performs the Requirements without any Defects. As used in this Agreement, "Defect" means a reproducible failure of a Software deliverable to conform in all material respects to its specifications and Requirements. Acceptance of Software deliverables will be conducted in accordance with the following procedures.
Software Deliverables. Unless otherwise agreed by the parties under a separate license or technology agreement, if Providing Company supplies Receiving Company with a deliverable that in whole or in part consists of software, firmware, or other computer code (referred to as a "Software Deliverable"), such Software Deliverables will be supplied in object code form only and will be subject to the Technology Cross License Agreement.
Software Deliverables. Contractor shall provide the following software systems:
