Source Code Handling Requirements definition

Source Code Handling Requirements means procedures mutually agreed to by the parties to ensure that all access to Source Code follows reasonable security protocols designed to ensure secure access and accountability for use of the Source Code. The Source Code Handling Requirements may include, for example, the use of source code repository that may only be accessed by named individuals that must use unique identifiers and access credentials.

Examples of Source Code Handling Requirements in a sentence

  • Accordingly, SFX will and shall cause its Contractors and employees to (a) comply with the Source Code Handling Requirements and (b) monitor, maintain and implement prevailing industry standard security controls that are designed to prevent unauthorized access to the Viggle Source Code.

Related to Source Code Handling Requirements

  • Web Site Accessibility Standards/Specifications means standards contained in Title 1 Texas Administrative Code Chapter 206.

  • Web Site Accessibility Standards/Specifications means standards contained in Title 1 Texas Administrative Code Chapter 206.

  • Program Requirements means certain minimum program entry requirements as well as ongoing program requirements, to be fulfilled by Partner, some of which are general PartnerEdge requirements, some of which are specific for the “Sell Engagement” and some of which are specific for the different “Cloud” Product Families, including, without limitation payment of the Program Fee(s), meeting certain minimum annual revenue requirements, upholding a Sell Authorization for at least one “Cloud” Product Family and other requirements as set out in detail in the PartnerEdge Program Guide and the RSPI.

  • Reporting Requirements As defined in Section 11.15.

  • Technical Requirements means the Technical Requirements in Section VII of the tendering documents.

  • Periodic Billing Requirement means, for any Remittance Period, the aggregate amount of Charges calculated by the Servicer as necessary to be billed during such period in order to collect the Periodic Payment Requirement on a timely basis.

  • Functional Specifications means the descriptions of features and functions of the Application as expressly set forth in Quote.

  • Technical Specifications means the detailed requirements for the Work furnished by the Architect and set forth in Book 3 of the Contract Documents.

  • Wastewater treatment system means any equipment, plants,

  • Listing Requirements means the Main Market Listing Requirements of Bursa Securities.

  • Service Specifications means the following documents, as applicable to the Services under Your order:

  • template version has the meaning ascribed to such term in NI 41-101 and includes any revised template version of marketing materials as contemplated by NI 41-101;

  • Monitoring Requirements Schedule means the Schedule containing details of the monitoring arrangements.

  • Reporting Requirement By January 31, 2017, the District will provide for OCR’s review and approval the Web Accessibility Policy drafted consistent with Item 1.

  • Interconnection Regulations means the Telecommunication (Broadcasting and Cable) Services Interconnection (Addressable Systems) Regulations, 2017 (as amended).

  • Pretreatment requirements means any substantive or procedural requirement related to pretreatment, other than a pretreatment standard, imposed on an industrial user.

  • Storage Injection Requirements means all volumes required by the Seller for injection into underground storage, including cushion gas, and for liquification, including fuel used for injection and in liquification plants, or for such other storage projects that may be developed expressly for the protection of supply to high priority users.

  • Applicable Technical Requirements and Standards means those certain technical requirements and standards applicable to interconnections of generation and/or transmission facilities with the facilities of an Interconnected Transmission Owner or, as the case may be and to the extent applicable, of an Electric Distributor, as published by Transmission Provider in a PJM Manual provided, however, that, with respect to any generation facilities with maximum generating capacity of 2 MW or less (synchronous) or 5 MW or less (inverter-based) for which the Interconnection Customer executes a Construction Service Agreement or Interconnection Service Agreement on or after March 19, 2005, “Applicable Technical Requirements and Standards” shall refer to the “PJM Small Generator Interconnection Applicable Technical Requirements and Standards.” All Applicable Technical Requirements and Standards shall be publicly available through postings on Transmission Provider’s internet website.

  • End Client Requirements means the specific requirements of the End Client, as notified to the Supplier in writing;

  • Electronic Subcontracting Reporting System (eSRS) means the Governmentwide, electronic, web-based system for small business subcontracting program reporting. The eSRS is located at http://www.esrs.gov.

  • Contractor Software means software which is proprietary to the Contractor, including software which is or will be used by the Contractor for the purposes of providing the Services.

  • Appendix Information means the information which must be provided for the selected modules as set out in the Appendix of the Approved EU SCCs (other than the Parties), and which for this Addendum is set out in:

  • Information processing system means an electronic system for creating, generating, sending, receiving, storing, displaying, or processing information.

  • technical specification means a document that prescribes technical requirements to be fulfilled by a product, process or service;

  • Application Programming Interface or “API” means the application programming interface materials and related documentation containing all data and information to allow skilled Software developers to create Software interfaces that interface or interact with other specified Software.

  • Interoperability means the ability of a CenturyLink OSS Function to process seamlessly (i.e., without any manual intervention) business transactions with CLEC's OSS application, and vice versa, by means of secure exchange of transaction data models that use data fields and usage rules that can be received and processed by the other Party to achieve the intended OSS Function and related response. (See also Electronic Bonding.)