Aim of Prototype A Sample Clauses

Aim of Prototype A. The Prototype A of WP5 was realized as an explorative piece of software. The aim was to validate requirements (use cases and the derived workflow presented in Section 1.1.2) and to check the feasibility of the proposed architecture. Almost as important as the aims of the prototype we have to state what the prototype was not planned to be: • a fully functional software for a regional host • a first version of a host, which only must be adapted to have a product ready.
AutoNDA by SimpleDocs

Related to Aim of Prototype A

  • ADB’s Review of Procurement Decisions 11. All contracts procured under international competitive bidding procedures and contracts for consulting services shall be subject to prior review by ADB, unless otherwise agreed between the Borrower and ADB and set forth in the Procurement Plan.

  • Prescription Drug Plan Retail and mail order prescription drug copays for bargaining unit employees shall be as follows:

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

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