Definition of Software Specification Sample Clauses

Definition of Software Specification. Define "Software Specification". NB in many cases it will not be appropriate to include a reference to documentation in this definition. May the specification for the software be varied by the written agreement of the parties? Definition of Term Define "Term", the period during which the contract will subsist. Clause 2: Credit Clause: Free documents licensing warning Optional element. Although you need to retain the credit, you should remove the inline copyright warning from this document before use. Clause 3: Term Clause 3.2 Is the term of the contract indefinite, or will it come to an end upon some agreed date, or upon the occurrence of a defined event? Upon what date will the contract terminate? Upon the occurrence of what event will the contract terminate? Clause 4: Supply of Software Optional element. Clause 4.1 Within what period must the Licensor make the software available to the Licensee for download?
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Definition of Software Specification. Define "Software Specification". NB in many cases it will not be appropriate to include a reference to documentation in this definition. May the specification for the software be varied by the written agreement of the parties? Definition of Source Code Consider whether to adapt the definition of source code. Definition of Term Define "Term", the period during which the contract will subsist. Definition of Third Party Materials Must all third party materials incorporated into the software be specifically identified in the specification of the software or included subject to the parties' agreement? Clause 2: Credit Clause: Free documents licensing warning Optional element. Although you need to retain the credit, you should remove the inline copyright warning from this document before use. Clause 3: Term Clause 3.2 Is the term of the document indefinite, or will it automatically come to an end after all services and software have been provided and all amounts due have been paid? Clause 4: Development Services Clause 4.2 Will the Developer have an absolute or qualified obligation to meet the timetable for the provision of the development services? What exactly will be delivered to the Customer? Clause 4.3 Optional element. Clause 4.4 Optional element. Specify the subject of the coding standard obligations. What obligations will the Developer have in relation to the software code itself? Clause 4.5
Sample 1Sample 2Sample 3

Related to Definition of Software Specification

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • CLARIFICATION OF SPECIFICATION DOCUMENTS 4.1 Bidders shall promptly notify the Purchasing Agent of any ambiguity, inconsistency or error which they may discover upon examination of the specification documents.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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