Software Validation Sample Clauses

Software Validation. 3.9.10.7 Software Verification
Sample 1Sample 2
AutoNDA by SimpleDocs
Software Validation. Triple G shall, at the Programming Rate,
Sample 1Sample 2
Software Validation. Definition: The PO-6 metric measures software validation for major releases affecting FairPoint’s CLEC OSS interface where FairPoint offers a test deck in the CLEC Test Environment (CTE). FairPoint tests the software release functionality, by executing a test deck of transactions, to validate that the functionality in a software release works as designed. FairPoint will execute the test deck in the test environment at the start of the User Acceptance Testing (UAT) and at the completion of UAT. Within one (1) business day, following a non-emergency software release to production as communicated through Change Management, FairPoint will begin to execute the test deck in production. Upon completion of the test, FairPoint will report the number of test deck transactions that were rejected or otherwise failed during execution of the test deck in production. A transaction is considered failed if the request cannot be submitted or processed, or results in incorrect or improperly formatted data. This software validation metric is reported as a percentage calculated as the number of failed test deck transactions in production divided by the total number of all transactions in the test deck in production. For those months that FairPoint does not execute the test deck, the WPP report is populated with the notation NA. Exclusions: Transactions that fail due to CLEC error. Report Dimensions: Company: • CLEC Aggregate Geography: • FairPoint NNE Sub-Metric: PO-6-01 Software Validation Metric Type Percent (Numerator/Denominator x 100) Numerator Sum of failed test deck transactions in production. Denominator Sum of all test desk transactions in production. Metric # Product Title Performance Standard Performance Credit Status PO-6-01-6000 VFO ≤ 5% Failed Transactions Eligible Function:
Sample 1
Software Validation. Software development is an important activity with the D4Sciece-II project. Consequently it cannot fall outside the quality assurance plans. The goal of the software validation procedure is to verify the quality of the software developed by the project. The execution of the procedure should however be straightforward and do not bring extra work on the development teams of the project. The procedure is based on the fact that, a developer who, according to the software architecture, is responsible for “consuming” a given component must state the degree that the component met his/her expectancies and requirements upon its release. More information about this procedure can be found at: xxxxx://xxxxxxx.xxxx.x0xxxxxxx-xx.xxxxxxxx- xxxxxxxxxxxxxxx.xx/xxxxxxx/xxxxx.xxx/Xxxxxxxxx_Xxxxxxxx_Xxxxxxxxxx D4Science – No. 239019 xxx.x0xxxxxxx.xx
Sample 1
Software Validation. Neoprobe shall be responsible for the software validation of any embedded product software and the validation of all Neoprobe-supplied test equipment or test software, Neoprobe supplied production equipment or software, and Neoprobe supplied firmware. Plexus is responsible for the validation of any Plexus software used in production or as part of the Quality System. The responsibilities described in this Section 7.04 also apply to any revisions of any software. Upon the request by Plexus, Neoprobe will provide Plexus with written certification that the validations in required by this Section 7.04 have been performed.
Sample 1
Software Validation. The Contractor shall validate that the contracted software provides the specified function(s) and does not impact other functional areas in the software.
Sample 1
Software Validation. GenMark is responsible for the validation of any software embedded in the Products and the validation of all GenMark-supplied: (1) test equipment or software; (2) production equipment or software; and (3)
Sample 1
AutoNDA by SimpleDocs

Related to Software Validation

  • 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.

  • 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.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Software License Subject to the terms of this Agreement, Viasat grants to you a personal, non-exclusive, non-assignable and non-transferable license to use and display the software provided by or on behalf of Viasat (including any updates) only for the purpose of accessing the Service ("Software") on any computer(s) on which you are the primary user or which you are authorized to use. Our Privacy Policies provide important information about the Software applications we utilize. Please read the terms very carefully, as they contain important disclosures about the use and security of data transmitted to and from your computer. Unauthorized copying of the Software, including, without limitation, software that has been modified, merged or included with the Software, or the written materials associated therewith, is expressly forbidden. You may not sublicense, assign, or transfer this license or the Software except as permitted in writing by Viasat. Any attempt to sublicense, assign or transfer any of the rights, duties or obligations under this license is void and may result in termination by Viasat of this Agreement and the license. You agree that you shall not copy or duplicate or permit anyone else to copy or duplicate any part of the Software, or create or attempt to create, or permit others to create or attempt to create, by reverse engineering or otherwise, the source programs or any part thereof from the object programs or from other information made available under this Agreement.

  • 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.

  • 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.

  • Software Maintenance Subrecipient shall apply security patches and upgrades in a timely manner and keep virus software up-to-date on all systems on which State data may be stored or accessed.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!