Difference between revisions of "DE4A Service Interoperability Solutions Toolbox"
Line 17: | Line 17: | ||
The [[Architecture Log]] keeps track of deviations from DE4A principles and the reference architecture in general and also records the implications. | The [[Architecture Log]] keeps track of deviations from DE4A principles and the reference architecture in general and also records the implications. | ||
− | == Library of components and building blocks == | + | == [[Library of components and building blocks]] == |
This section contains the collection of technical and semantic common components and candidate Building Blocks that are relevant for eGovernment interoperability in general and digital-by-default procedures and the Once-only Principle in particular. The classification of this library follows the DE4A [[Reference Architecture]], starting on the highest level of architecture components: the Application collaborations. These Application collaborations are aggregations of Application components, Data objects and Interfaces. You will find on each Application component pages a list of relevant DE4A common components, candidate Building Blocks (e.g. CEF) and memberstate solutions that jointly or alternatively realize that Application component. | This section contains the collection of technical and semantic common components and candidate Building Blocks that are relevant for eGovernment interoperability in general and digital-by-default procedures and the Once-only Principle in particular. The classification of this library follows the DE4A [[Reference Architecture]], starting on the highest level of architecture components: the Application collaborations. These Application collaborations are aggregations of Application components, Data objects and Interfaces. You will find on each Application component pages a list of relevant DE4A common components, candidate Building Blocks (e.g. CEF) and memberstate solutions that jointly or alternatively realize that Application component. |
Revision as of 14:17, 26 January 2022
This toolbox is the central, long-term deliverable of the DE4A Architecture work package (WP2) and takes the form of a structured, online architecture repository that extends from the content of the Architecture Framework and prior work of e-SENS. The toolbox includes (pointers to) prior work in CEF, ISA, ISA2 and prior LSPs. It includes new DE4A common components and implementation method and Pilot insights.
Pilots
DE4A includes three cross-border and cross-domain Pilots - Studying Abroad Pilot, Doing Business Abroad Pilot, and Moving Abroad Pilot -, comprising different functional use cases focused on different high-impact and viable administrative procedures, and aimed to realize tangible benefits in fully operational environments to real users (citizens, students, business persons and public servants). The Pilots are delivered by a separate, agile, multi-disciplinary, inter-member state teams of experts. The focus of these teams is on iterative system integration and configuration, hence on making existing building blocks and solutions work together in real life cases.
Reference Architecture
DE4A develops a multi-pattern architecture for eGovernment interoperability with a focus on digital-by default procedures for citizens and businesses and the full implementation of the Once-Only Principle. The DE4A Architecture Framework defines five architecture Time Horizons staring from the pre-SDG baseline (t=0, ~2019) and reaching to a long-term vision (t=4, ~2030+) in order to place different developments in context. More detail on the Architecture Framework is available in the public deliverable D2.1 Architecture Framework.
The development of the DE4A Reference Architecture started in the context of D2.4 Project Start Architecture (PSA) - First iteration and recognizes three distinct Reference Interaction Patterns:
The forthcoming D2.5 Project Start Architecture (PSA) - Second iteration is introducing two additional Reference Interaction Pattern:
The Architecture Log keeps track of deviations from DE4A principles and the reference architecture in general and also records the implications.
Library of components and building blocks
This section contains the collection of technical and semantic common components and candidate Building Blocks that are relevant for eGovernment interoperability in general and digital-by-default procedures and the Once-only Principle in particular. The classification of this library follows the DE4A Reference Architecture, starting on the highest level of architecture components: the Application collaborations. These Application collaborations are aggregations of Application components, Data objects and Interfaces. You will find on each Application component pages a list of relevant DE4A common components, candidate Building Blocks (e.g. CEF) and memberstate solutions that jointly or alternatively realize that Application component.
Application collaborations
- eProcedure Portal
- Information Desk
- Evidence Interchange Management
- Trust Architecture
- Data Logistics
- Evidence Portal
- Evidence Retrieval
- Authority Agent
- User Agent
- Cross-border Subscriptions
- EProcedure Back-office
Building blocks (BB) assessment
The reference architecture description on conceptional/functional level is brought together with a catalogue of candidate building blocks mapped to required Application Services that they are intended to deliver in the context of each pilot. Gaps are identified that need common components and semantic solutions to be developed by WP5 and WP3 respectively.
The BB assessment takes place in two phases:
- In the first phase, as part of the PSA 1st iteration, the approach assessment of the BBs was elaborated and a quick scan was performed.
- In the second phase, after the Pilot's implementation and usage of some of the BBs, the assessment will be continued.
DE4A Solutions
TODO add intro
Semantic Interoperability Solutions
Legal and ethical support
Legal and ethical work under Work Packages 7 and 10 is summarised in a separate Wiki page. Inputs and suggestions can be provided there.
Disclaimer
This DE4A wiki is created, hosted and maintained by and on behalf of the members of the DE4A consortium (see https://www.de4a.eu/consortium). All contents are provided in good faith by persons supporting this consortium, with the common objective of furthering the progress of the DE4A project.
Anyone with appropriate credentials may choose to add or edit contents of the DE4A wiki. Any contributions to the content remain owned by the respective contributor(s), but by submitting any contents, you explicitly authorise the DE4A consortium to publish and disseminate the contents via the wiki. Furthermore, you authorise the members of the DE4A consortium to use your contents for any purposes (including usage outside of this wiki) that would benefit the execution of the DE4A project. Each contributor should apply reasonable care to verify that their contributions are likely to contribute to the progress of the DE4A project, given the expertise and knowledge of the contributor and the state of the project. In case of doubts on this point, the contributor should take care to communicate any applicable constraints or reservations in the contribution. Each contributor is responsible for ensuring that their individual contributions are lawful, including but not limited to ensuring that contributions do not violate any third party intellectual property rights.
Irrespective of the above, contents are provided purely on an ‘as is’ basis, without any guarantees of accuracy, completeness or usability for any particular purpose. Contents do not necessarily reflect a consensus or a shared position of the DE4A consortium as a whole, nor even of any individual member. Anyone who decides to rely on the contents of the DE4A wiki for any reason or purpose should apply their own diligence, and assumes full and exclusive responsibility and liability for any consequences of their reliance on the contents. No assurances are provided with respect to the contents, neither explicitly nor implied.