D2.2 Generic, federated OOP architecture (2nd version)
Creators: name: Grandry, Eric
name: Brandt, Paul
name: Dimitriou, Jerry
name: Fieten, Sander
name: Rotuna, Carmen
name: Tepandi, Jaak
name: Täks. Ermo
name: Verhoosel, Jack
name: Zeginis, Dimitrios
Publisher: name: Zenodo
Year: 2018
Subjects: subject: TOOP
subject: Architecture
subject: FOS: Civil engineering
subject: FOS: Civil engineering

description: This document presents the second official version of the generic federated OOP architecture. It develops further and extends the deliverable “D2.1. Generic federated OOP architecture (1st version)” (D2.1). The architecture supports interconnection and interoperability of national registries at the EU level, is in line with existing EU frameworks (EIRA, EIF), takes into account the forthcoming regulation about the Single Digital Gateway (SDGR), and uses results of the e-SENS European Interoperability Reference Architecture. It provides support for future developers of OOP projects and is based on the Connecting Europe Facility (CEF) Digital Service Infrastructures (DSIs), the Building Blocks consolidated by the e-SENS project, and in justified cases, on the new building blocks. Compared to the first version D2.1, this deliverable develops the architecture further, aligns it with the provisions of the forthcoming regulation about the Single Digital Gateway, and focusses on the motivation, domain, and business views of the architecture. Summaries of the main characteristics of the applicable Building Blocks provided in D2.1 establish a starting point for the technology architecture. Detailed description of changes is provided in the section “Changes between D2.1 and D2.2”. The architecture description in the current deliverable is organized along the business view, concerned with the business operations of the TOOP system. As the project is itself defining the Cross-Border Once Only and is required to support the development of the SDG Regulation, two preliminary views are added: the domain view, concerned with the definition of the Once Only domain (the problem domain), and the requirements view, concerned with the objectives, needs, legal obligations and principles driving the architecture. The architecture is oriented towards reusing existing frameworks and building blocks provided by CEF, e-SENS, and other initiatives. The key concepts underlying the architecture, including the main principles of the Generic Once-Only Principle Reference Architecture (GOOPRA) are analysed in Ch 2. Chapter 3 presents the domain view, concerned with the definition of the Once-Only domain in which the TOOP project is situated. Requirements to the architecture, including the requirements stemming from the Single Digital Gateway Regulation, are proposed in Ch 4. The business view is designed in Ch 5, focussing on the description of the business operationalization of the Once Only Principles by the business actors. Summaries of the main characteristics of applicable Building Blocks provided in Ch 6, including rationale for their inclusion in the architecture, usage, maintenance, gap analysis, and need for further development, form a basis for the Technology Architecture to be developed further deliverable D2.3. This deliverable is a work in progress. The next steps are to develop the architecture in more detail, to provide the information system architecture, to complement the technology architecture with how the BB are actually used to support the IS architecture and potential new BBs or extensions, as well as to continue the exploratory and agile approach, together with cooperation with the TOOP pilots and other TOOP tasks. The forthcoming official deliverables are D2.3 (M21, September 2018), and D2.4 (M30, June 2019).