Reference architecture and workflow of PREFORMA Sample Clauses

Reference architecture and workflow of PREFORMA. The DIRECT Evaluation Infrastructure and the Performance Visualization Widgets already exist from previous project PROMISE Network of Excellence. They will be used to assess the new tools developed by the supplies of the tender (which are in fact the results expected from the CP part of the project), i.e.: “Abstract Conformance Checker”, “Scorer”, “Reporter”, and “Abstract Fixes Suggester/Correcter”. In addition, the software features of the DIRECT Evaluation Infrastructure and of the Performance Visualization Widgets will also be offered to the suppliers for storing and visualizing the outcomes of the new tools. It will be then a decision of the suppliers if they want to use these features or prefer to use different software. The final artefact resulting from tender will be a Web application which coordinates the overall workflow from acquiring documents, analysing them, storing the outcomes of the evaluation (possibly, into the existing DIRECT infrastructure), to suggesting possible fixes, trying corrections, and generating reports. The figure above is provided for illustrative purposes, only. It will be a task of WP2 to provide precise reference specifications for the tender and then tasks of WP5 and WP6 to develop the full technical architecture. The architecture will be required to be designed as modular and as flexible as possible, allowing for clear extension points and plug ability. The “Abstract Conformance Checker” and “Abstract Fix Suggester” will be requested to provide a high-level interface for dealing with these two tasks while the actual implementation for a specific standard is then delegated to “drivers” specific for that standard. Moreover, to facilitate building alternative applications and/or re-use of the produced data, the Validator Web Application will exploit a series of lightweight RESTful Web services which expose data in XML and/or JSON. This allows not only for building other Web 2.0 applications but also for exploiting alternative devices such as tablets. The above two design choices will extend the reach and impact of the project beyond its specific objectives, since they turn PREFORMA into a more general framework for checking the conformity to document format standards, suggesting fixes and applying corrections, and reporting results of the test which can be extended to other domains than memory institutions and used as base for building innovative applications. The basic workflow will be: - the user selects a set of docume...
Sample 1
AutoNDA by SimpleDocs

Related to Reference architecture and workflow of PREFORMA

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Limitations on Reverse Engineering, Decompilation, and Disassembly You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • Measurement and Monitoring Tools Contractor shall implement measurement and monitoring tools and procedures reasonably designed to measure its performance of the Services and assess such performance against any applicable service levels. Contractor shall provide LAUSD with a monthly report of service level performance under any applicable Work Order. Upon LAUSD’s request, Contractor shall provide LAUSD with access to the measurement and monitoring tools described herein, and to any information that they generate.

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Firmware The Contractor shall deliver firmware required for production acceptance testing in accordance with CDRL A009 Contractor’s Supplier Configuration Management Plan. The Contractor shall use Government furnished software for testing. Deliverable Data Item (See DD-1423): CDRL A009: “Contractor’s Supplier Configuration Management Plan”

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Reverse Engineering The Customer must not reverse assemble or reverse compile or directly or indirectly allow or cause a third party to reverse assemble or reverse compile the whole or any part of the software or any products supplied as a part of the Licensed System.

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