Development Documentation Sample Clauses

Development Documentation. PalmSource will: • Create, maintain and provide developer documentation for the public PS OS and Application Software APIs. • Provide style guidelines for developer documentation to Licensee. Licensee will: • Provide appropriate developer documentation for its Licensee API’s. PALMSOURCE AND PALMONE CONFIDENTIAL ROM IMAGE LICENSE
AutoNDA by SimpleDocs
Development Documentation. CTI will transfer and assign to Chroma all Development Documentation related to the Product developed under the Development Plan.
Development Documentation. Printed material that relates to source code, including comments, and that incudes a description of the principles of operation of the Development Process and instructions for its use. All copies of Development Documentation shall be numbered and marked by Owner "Development Documentation--Property of Louix X.
Development Documentation. To be developed by the PRB
Development Documentation. All design documentation is included in the CVS tree i. Requirements specs ii. Design specifications iii. Detailed design specification iv. API docs v. All documentation items and items you intend to have in place related to development of the ES and all outstanding components vi. List all the tools used in document control vii. Number of different documentary items User Documentation: Included in top level of /Vault/Legacy/ESProductDoc i. manuals (original format) ii. registration cards shipped with the ES (if applicable) iii. Startup kit (original format) iv. Usability documentation
Development Documentation. All design documentation is included on the /Vault documentation CD in the 'Legacy/DVRProductDoc/DOCS_HTML' viewable through a web browser. The development tool used for documentation, code, debug and integration is Rationale Rose (currently using v5.5). Hence, there may be some viewing issues & the documentation may not be completely current in this format while development continues.

Related to Development Documentation

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Medical Documentation The teacher must supply a letter from a medical 3 doctor, who treated the patient, stating that in his/her opinion, there is a strong 4 probability that the illness was contracted at school.

  • Tax Documentation Xxxxxx agrees to provide a completed IRS 1099 for its payments to, and Xxxxxxx agrees to provide IRS W-9 forms for, each of the following payees under this Settlement Agreement:

  • Documentation License Subject to the terms of this Agreement, Flock hereby grants to Customer a non-exclusive, non-transferable right and license to use the Documentation during the Service Term for Customer’s internal purposes in connection with its use of the Flock Services as contemplated herein.

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