Software Test Sample Clauses

Software Test. The Contractor shall generate and use test plans, procedures, and reports to verify that each software configuration item (SWCI) performs in accordance with individual SWCI test specifications and the CI interface requirements. TerreStar shall have the right to observe and monitor the CI tests. Following completion of testing, the Contractor shall document the test results, deviations from test procedures, and all software anomalies and submit a report to TerreStar. The Contractor shall support Chipset integration and test with the UE and the S-BSS. The Contractor shall provide all necessary test tools and equipment to support Chipset integration and test with the UE and the S-BSS.
Sample 1Sample 2
AutoNDA by SimpleDocs
Software Test. Execution Monitoring
Sample 1
Software Test. Plan (STP) (CDRL A026) This report shall reflect both prime and Subcontractor data if applicable at the same level of detail. The CDRL shall be submitted via hard copy and electronic media of contractor’s choosing, and agreed to by the Government. The STP must address all software testing that shall be performed and how the software will be tested with the hardware as an integrated package. The STP must be approved upon completion of the baseline SRS by the Government. The approved STP will be considered the baseline and will be followed throughout the program unless a revised version is approved by the Government.
Sample 1
Software Test. The Contractor shall generate and use test plans, procedures, and reports to verify that each software configuration item (SWCI) performs in accordance with individual SWCI test specifications and the CI interface requirements. TerreStar shall have the right to observe and monitor the CI tests. Following completion of testing, the Contractor shall document the test results, deviations from test procedures, and all software anomalies and submit a report to TerreStar. The Contractor shall provide all necessary test tools and equipment to support S-BSS integration and test and Technical and Operational Verification. Confidential treatment has been requested for portions of this exhibit and such portions have been filed separately with the Commission. The copy filed herewith omits the information for which confidential treatment has been requested and replaces it with [***]. AMENDMENT 4 TerreStar Satellite Base Station Subsystem SOW
Sample 1
Software Test. The Contractor shall generate and use test plans, procedures, and reports to verify that each software configuration item (SWCI) performs in accordance with individual SWCI test specifications and the CI interface requirements. TerreStar shall have the right to observe and monitor the CI tests. Following Exhibit A Use or disclosure of the data contained on this sheet is subject to the restriction on the title page. TerreStar Satellite Base Station Subsystem SOW completion of testing, the Contractor shall document the test results, deviations from test procedures, and all software anomalies and submit a report to TerreStar. The Contractor shall provide all necessary test tools and equipment to support S-BSS integration and test and Technical and Operational Verification.
Sample 1

Related to Software Test

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

  • Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.

  • Software Warranty We warrant that the Tyler Software will perform without Defects during the term of this Agreement. If the Tyler Software does not perform as warranted, we will use all reasonable efforts, consistent with industry standards, to cure the Defect in accordance with the maintenance and support process set forth in Section C(9), below, the SLA and our then current Support Call Process.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Product Testing Upon request, Customer shall provide Operator a laboratory report for each Product delivery by Customer or Customer’s supplier. Operator will not be obligated to receive Contaminated Product for throughput across the Berths, nor will Operator be obligated to accept Product that fails to meet the quality specifications set forth in the arrival notice.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

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