Adequacy of Documentation. All Documentation must include all such information as may be reasonably necessary for the effective installation, testing, use, support, and maintenance of the applicable Software by the Intended User, including the effective configuration, integration, and systems administration of the Software and performance of all other functions set forth in the Specifications.
Adequacy of Documentation. The Technical Documentation includes the source code, system documentation, statements or principles of operation, and schematics for DeltaGraph currently maintained or licensed by DeltaPoint, as well as any pertinent commentary or explanation that may be necessary to render such materials understandable and usable by a trained computer programmer familiar with the relevant compilers, tools and platform.
Adequacy of Documentation. Under the ‘partnership’ arrangement between the FHWA and the DOT for completing the Section 106 process in Iowa, and the formal letter of notification to the SHPO of March 1, 2001, the DOT normally prepares the various items of documentation for each project processed, and the FHWA reviews it for adequacy. As a practical matter, the FHWA does not so review each and every piece of correspondence and report generated between the DOT and its consultants, or the DOT and SHPO. However, under the regulations, the FHWA does have the responsibility to check and ensure that written ‘determinations,’ ‘findings’ or ‘agreements’ prepared by the DOT or its consultants for Section 106 are supported by sufficient documentation to enable any other reviewing party to understand their basis. This requirement is flexible with regard to Historic Property identifications or significance evaluations being conducted on a ‘phased’ basis. That is, the level of detail expected in a Phase 1 report is, by definition (See pages 14 - 15), less than that expected for a Phase 2 report; a Phase 2 is less than for a Phase 3 report. If the Council (or the SHPO, if the Council is not involved), upon review of proje ct documentation, determines that it does not meet the standards of this section, then the Council (or SHPO) will notify the FHWA of the deficiency and proceed to specify what information needs to be added or revised in order to be acceptable. The FHWA, or any involved consulting party, has the option of asking the Council to review any disputes that may arise over the adequacy of documentation that has been prepared. The Council will then review the dispute and offer its views on the situation to the FHWA and/or to the involved consulting parties.
Adequacy of Documentation. The Documentation including system documentation, statements of principles of operation, and schematics for the System, as well as any pertinent commentary or explanation that may be necessary to render such materials understandable and usable by a trained computer programmer, and as of the Closing Date, is complete, accurate and correct, comports with generally accepted industry standards in describing the proper procedures for installing and operating the System, and shall provide sufficient information to enable Company personnel to install and operate the System.
Adequacy of Documentation. 11 2.16 Third-Party Components in Software Programs....................11 2.17 Third-Party Interests or Marketing Rights in Software Programs.11 2.18 No Virus Warranties............................................12 2.19 Purchased Software; Performance; Physical Media................12 2.20
Adequacy of Documentation. The technical documentation for the Data Distilleries Entities' products includes the source code, system documentation, statements or principles of operation, and schematics for all of the software products currently maintained or licensed by the Data Distilleries Entities, as well as any pertinent commentary or explanation that may be necessary to render such materials understandable and usable by a trained computer programmer familiar with the relevant compilers, tools and platform (the "TECHNICAL DOCUMENTATION").
Adequacy of Documentation. The Technical Documentation includes the source code, system documentation, statements or principles of operation, and schematics for VStat currently maintained or licensed by DataStat, as well as any pertinent commentary or explanation that may be necessary to render such materials understandable and usable by a trained computer programmer familiar with the relevant compilers, tools and platform.
Adequacy of Documentation. Except as set forth in Schedule 3.16, the technical documentation includes the source code, system documentation, for all of the software products currently maintained by or licensed to Surveycraft or either Subsidiary, as well as any pertinent commentary or explanation (the "Technical Documentation"), provided, however, that in connection with Surveycraft's ongoing software development, certain Technical Documentation may, in the ordinary course of business, not be current with the corresponding software.
Adequacy of Documentation. All Documentation shall include all such information as may be reasonably necessary for the effective installation, testing, use, support and maintenance of the applicable Proprietary Product by the End User, including the effective configuration, integration, and systems administration of the Proprietary Product and performance of all other functions set forth in the Specifications.
Adequacy of Documentation. 11 2.16 Third-Party Components in Software Programs. . . . . . . . . . 11 2.17 Third-Party Interests or Marketing Rights in Software Programs.. . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.18
