SYSTEM AND SOFTWARE TECHNICAL DOCUMENTATION Sample Clauses

SYSTEM AND SOFTWARE TECHNICAL DOCUMENTATION. Existing Technical Data Package (TDP) documentation shall be updated and maintained under this contract under CDRL A015. The contractor shall provide technical documentation that clearly documents simulation and training system software architecture and implementation. This documentation shall include physical system architecture to include hardware and networking interfaces, dependencies, and configurations. This documentation shall also include all software subsystem architecture, functionality, internal, and external interfaces. The contractor shall provide technical documentation for new training system configurations developed under this contract at a level to allow Government modification and configuration management of existing and future software upgrades. Each new training system configuration developed under this contract shall require a new delta TDP to define any changes in system or software design and implementation from the baseline and current TDP packages for that training system variant. The contractor engineering team shall provide TDP content and the contractor shall provide appropriate technical writing, technical editing, graphics, and desktop publishing by the editing team to complete the documentation package and maintain format consistency with existing TDP documents. Delivery schedules for TDP package updates shall be specified in the TOs and, in order to support “as-built” documentation, shall follow the initial installation of a new training system configuration. An average delta TDP package for a new training system configuration can be estimated at 185 pages and an average of six TDP packages per year are expected based on historical estimates and anticipated build schedules across the five types of trainer configurations supported under this contract. The TDP for each Trainer Build shall provide the Technical Product details with design and implementation documented at the system and subsystem level to provide sufficient insight into the system and software architecture to allow new developers to support future maintenance and updates of these complex training systems. TDP documents shall reference the government-furnished baseline documentation, and TDPs for subsequent builds shall document the differences which are specific to the updated build or platform configuration as compared to the reference. Only the differences to the referenced TDP need to be documented. The referenced material does not need to be included in eith...
View SourceView Similar (2)

Related to SYSTEM AND SOFTWARE TECHNICAL DOCUMENTATION

  • 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.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

  • 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