WP2 Architecture Vision and Framework - Revision history

Ictu mavi.cristache at 14:21, 15 July 2021

2021-07-15T14:21:09Z

Ictu mavi.cristache: BB page link changed

2021-07-15T14:20:03Z

BB page link changed

Ictu mavi.cristache at 13:15, 8 March 2021

2021-03-08T13:15:49Z

Ictu mavi.cristache at 13:15, 8 March 2021

2021-03-08T13:15:31Z

Ictu mavi.cristache at 13:13, 8 March 2021

2021-03-08T13:13:17Z

Ictu mavi.cristache at 13:11, 8 March 2021

2021-03-08T13:11:22Z

Ictu mavi.cristache: Ictu mavi.cristache moved page WP2 to WP2 Architecture Vision and Framework

2021-03-08T13:09:29Z

Ictu mavi.cristache moved page WP2 to WP2 Architecture Vision and Framework

Ictu mavi.cristache at 13:08, 8 March 2021

2021-03-08T13:08:41Z

Ictu mavi.cristache at 13:03, 8 March 2021

2021-03-08T13:03:22Z

Ictu mavi.cristache at 12:59, 8 March 2021

2021-03-08T12:59:29Z

@@ Line 1: / Line 1: @@
 ==Objectives==
-The architecture describes the relevant building blocks of the envisioned systems, their interrelation and the rules and principles that govern these relationships and their evolution over time. The architecture descriptions delivered by work package 2 cover all levels of Enterprise Architecture descriptions: directional (i.e. policy needs and legal compliance (cf. WP7)), organisation (i.e. actors and processes), application (i.e. application functions, main information objects) and technology (i.e. components and infrastructures). The target architectures are described in functional terms with a catalogue (cf. WP1) of existing and emerging [[Building Blocks|building blocks (BB)]] and Digital Service Infrastructures (DSI) incl. maturity assessment. Technical solution architecture descriptions at the logical/technical levels are part of pilot deliverables (cf. [[WP4]]).
+The architecture describes the relevant building blocks of the envisioned systems, their interrelation and the rules and principles that govern these relationships and their evolution over time. The architecture descriptions delivered by work package 2 cover all levels of Enterprise Architecture descriptions: directional (i.e. policy needs and legal compliance (cf. WP7)), organisation (i.e. actors and processes), application (i.e. application functions, main information objects) and technology (i.e. components and infrastructures). The target architectures are described in functional terms with a catalogue (cf. WP1) of existing and emerging [[Building Blocks|Building Blocks (BB)]] and Digital Service Infrastructures (DSI) incl. maturity assessment. Technical solution architecture descriptions at the logical/technical levels are part of pilot deliverables (cf. [[WP4]]).
 WP2 provides a central structure – the architecture framework – to the overall project, which sets the Pilots in context to each other and to the generic reference architecture service patterns. Relating Pilot results, generated from specific technical architectures, to these service patterns provides a tool for the interpretation of findings and formulation of advice for future implementations. Pilots test out different service patterns, set out in the Project Start Architectures. WP2 uses an inductive approach to abstract from the specific results of the Pilots from their logged deviation from the start architectures and from the barriers encountered, successes attained and lessons learned in order to formulate generic target architecture advise.
@@ Line 9: / Line 9: @@
 : i) Provide a reference framework to relate building blocks, solutions, and reference implementations of this and prior projects to each other;
 : ii) Envision different target architecture states at different time horizons (cf. 1.4.1 Concept) that provide guidance to the further development of European governmental interoperability solutions and platforms;
-: iii) Give guidance to the Pilots ([[WP4]]) and the common component delivery ([[WP5]]) in terms of service patterns, existing and emerging [[BB|Building Blocks (BB)]] and Digital Service Infrastructures (DSI) and associated principles;
+: iii) Give guidance to the Pilots ([[WP4]]) and the common component delivery ([[WP5]]) in terms of service patterns, existing and emerging [[Building Blocks|Building Blocks (BB)]] and Digital Service Infrastructures (DSI) and associated principles;
 : iv) Assess quality and maturity measures of BB and DSI in light of the overall vision and principles, taking into account prior work in ISA, such as the Interoperability Maturity Model (IMM) or IMAPS;
 : v) Support future implementation projects with a toolbox of European interoperability solutions and guidance in form of a documented approach for implementations encompassing multiple BB and DSI, based on the DE4A toolbox.

@@ Line 1: / Line 1: @@
 ==Objectives==
-The architecture describes the relevant building blocks of the envisioned systems, their interrelation and the rules and principles that govern these relationships and their evolution over time. The architecture descriptions delivered by work package 2 cover all levels of Enterprise Architecture descriptions: directional (i.e. policy needs and legal compliance (cf. WP7)), organisation (i.e. actors and processes), application (i.e. application functions, main information objects) and technology (i.e. components and infrastructures). The target architectures are described in functional terms with a catalogue (cf. WP1) of existing and emerging [[BB|building blocks (BB)]] and Digital Service Infrastructures (DSI) incl. maturity assessment. Technical solution architecture descriptions at the logical/technical levels are part of pilot deliverables (cf. [[WP4]]).
+The architecture describes the relevant building blocks of the envisioned systems, their interrelation and the rules and principles that govern these relationships and their evolution over time. The architecture descriptions delivered by work package 2 cover all levels of Enterprise Architecture descriptions: directional (i.e. policy needs and legal compliance (cf. WP7)), organisation (i.e. actors and processes), application (i.e. application functions, main information objects) and technology (i.e. components and infrastructures). The target architectures are described in functional terms with a catalogue (cf. WP1) of existing and emerging [[Building Blocks|building blocks (BB)]] and Digital Service Infrastructures (DSI) incl. maturity assessment. Technical solution architecture descriptions at the logical/technical levels are part of pilot deliverables (cf. [[WP4]]).
 WP2 provides a central structure – the architecture framework – to the overall project, which sets the Pilots in context to each other and to the generic reference architecture service patterns. Relating Pilot results, generated from specific technical architectures, to these service patterns provides a tool for the interpretation of findings and formulation of advice for future implementations. Pilots test out different service patterns, set out in the Project Start Architectures. WP2 uses an inductive approach to abstract from the specific results of the Pilots from their logged deviation from the start architectures and from the barriers encountered, successes attained and lessons learned in order to formulate generic target architecture advise.

← Older revision		Revision as of 13:15, 8 March 2021
Line 37:		Line 37:


−	===T2.4 Service interoperability solutions toolbox]]	+	===T2.4 Service interoperability solutions toolbox===

	[[D2.6]]		[[D2.6]]

@@ Line 29: / Line 29: @@
 ===T2.2 Trust Management Models===
- [[D2.2]] and [[D2.3]]
+[[D2.2]] and [[D2.3]]
-T2.3 [[D2.4]] and [[D2.5]]
+===T2.3 Project Start Architecture===
-T2.5 [[D2.7]] and [[D2.8]]
+[[D2.6]]

@@ Line 9: / Line 9: @@
 : i) Provide a reference framework to relate building blocks, solutions, and reference implementations of this and prior projects to each other;
 : ii) Envision different target architecture states at different time horizons (cf. 1.4.1 Concept) that provide guidance to the further development of European governmental interoperability solutions and platforms;
-: iii) Give guidance to the Pilots (WP4) and the common component delivery (WP5) in terms of service patterns, existing and emerging Building Blocks (BB) and Digital Service Infrastructures (DSI) and associated principles;
+: iii) Give guidance to the Pilots ([[WP4]]) and the common component delivery ([[WP5]]) in terms of service patterns, existing and emerging [[BB|Building Blocks (BB)]] and Digital Service Infrastructures (DSI) and associated principles;
 : iv) Assess quality and maturity measures of BB and DSI in light of the overall vision and principles, taking into account prior work in ISA, such as the Interoperability Maturity Model (IMM) or IMAPS;
 : v) Support future implementation projects with a toolbox of European interoperability solutions and guidance in form of a documented approach for implementations encompassing multiple BB and DSI, based on the DE4A toolbox.
@@ Line 27: / Line 27: @@
-T2.2 [[D2.2]] and [[D2.3]]
+===T2.2 Trust Management Models===

@@ Line 3: / Line 3: @@
 The architecture describes the relevant building blocks of the envisioned systems, their interrelation and the rules and principles that govern these relationships and their evolution over time. The architecture descriptions delivered by work package 2 cover all levels of Enterprise Architecture descriptions: directional (i.e. policy needs and legal compliance (cf. WP7)), organisation (i.e. actors and processes), application (i.e. application functions, main information objects) and technology (i.e. components and infrastructures). The target architectures are described in functional terms with a catalogue (cf. WP1) of existing and emerging [[BB|building blocks (BB)]] and Digital Service Infrastructures (DSI) incl. maturity assessment. Technical solution architecture descriptions at the logical/technical levels are part of pilot deliverables (cf. [[WP4]]).
-WP2 Architecture Vision and Framework provides a central structure – the architecture framework – to the overall project, which sets the Pilots in context to each other and to the generic reference architecture service patterns. Relating Pilot results, generated from specific technical architectures, to these service patterns provides a tool for the interpretation of findings and formulation of advice for future implementations. Pilots test out different service patterns, set out in the Project Start Architectures. WP2 uses an inductive approach to abstract from the specific results of the Pilots from their logged deviation from the start architectures and from the barriers encountered, successes attained and lessons learned in order to formulate generic target architecture advise.
+WP2 provides a central structure – the architecture framework – to the overall project, which sets the Pilots in context to each other and to the generic reference architecture service patterns. Relating Pilot results, generated from specific technical architectures, to these service patterns provides a tool for the interpretation of findings and formulation of advice for future implementations. Pilots test out different service patterns, set out in the Project Start Architectures. WP2 uses an inductive approach to abstract from the specific results of the Pilots from their logged deviation from the start architectures and from the barriers encountered, successes attained and lessons learned in order to formulate generic target architecture advise.
 WP2 objectives include: i) Provide a reference framework to relate building blocks, solutions, and reference implementations of this and prior projects to each other; ii) Envision different target architecture states at different time horizons (cf. 1.4.1 Concept) that provide guidance to the further development of European governmental interoperability solutions and platforms; iii) Give guidance to the Pilots (WP4) and the common component delivery (WP5) in terms of service patterns, existing and emerging Building Blocks (BB) and Digital Service Infrastructures (DSI) and associated principles; iv) Assess quality and maturity measures of BB and DSI in light of the overall vision and principles, taking into account prior work in ISA, such as the Interoperability Maturity Model (IMM) or IMAPS; v) Support future implementation projects with a toolbox of European interoperability solutions and guidance in form of a documented approach for implementations encompassing multiple BB and DSI, based on the DE4A toolbox.
 ==Tasks==

← Older revision	Revision as of 13:09, 8 March 2021
(No difference)

@@ Line 1: / Line 1: @@
 ==Objectives==
-The architecture describes the relevant building blocks of the envisioned systems, their interrelation and the rules and principles that govern these relationships and their evolution over time. The architecture descriptions delivered by work package 2 covers all levels of Enterprise Architecture descriptions: directional (i.e. policy needs and legal compliance (cf. WP7)), organisation (i.e. actors and processes), application (i.e. application functions, main information objects) and technology (i.e. components and infrastructures). The target architectures are described in functional terms with a catalogue (cf. WP1) of existing and emerging building blocks (BB) and Digital Service Infrastructures (DSI) incl. maturity assessment. Technical solution architecture descriptions at the logical/technical levels are part of pilot deliverables (cf. WP4). WP2 Architecture Vision and Framework provides a central structure – the architecture framework – to the overall project, which sets the Pilots in context to each other and to the generic reference architecture service patterns. Relating Pilot results, generated from specific technical architectures, to these service patterns provides a tool for the interpretation of findings and formulation of advice for future implementations. Pilots test out different service patterns, set out in the Project Start Architectures. WP2 uses an inductive approach to abstract from the specific results of the Pilots from their logged deviation from the start architectures and from the barriers encountered, successes attained and lessons learned in order to formulate generic target architecture advise.
+The architecture describes the relevant building blocks of the envisioned systems, their interrelation and the rules and principles that govern these relationships and their evolution over time. The architecture descriptions delivered by work package 2 cover all levels of Enterprise Architecture descriptions: directional (i.e. policy needs and legal compliance (cf. WP7)), organisation (i.e. actors and processes), application (i.e. application functions, main information objects) and technology (i.e. components and infrastructures). The target architectures are described in functional terms with a catalogue (cf. WP1) of existing and emerging [[BB|building blocks (BB)]] and Digital Service Infrastructures (DSI) incl. maturity assessment. Technical solution architecture descriptions at the logical/technical levels are part of pilot deliverables (cf. [[WP4]]).
 WP2 objectives include: i) Provide a reference framework to relate building blocks, solutions, and reference implementations of this and prior projects to each other; ii) Envision different target architecture states at different time horizons (cf. 1.4.1 Concept) that provide guidance to the further development of European governmental interoperability solutions and platforms; iii) Give guidance to the Pilots (WP4) and the common component delivery (WP5) in terms of service patterns, existing and emerging Building Blocks (BB) and Digital Service Infrastructures (DSI) and associated principles; iv) Assess quality and maturity measures of BB and DSI in light of the overall vision and principles, taking into account prior work in ISA, such as the Interoperability Maturity Model (IMM) or IMAPS; v) Support future implementation projects with a toolbox of European interoperability solutions and guidance in form of a documented approach for implementations encompassing multiple BB and DSI, based on the DE4A toolbox.
@@ Line 7: / Line 9: @@
 ===T2.1 Architecture Framework===
-Leader: MINBZK /br
+Leader: MINBZK
 Participants: ATOS, MPTFP-SGAD, DIGST SU, DIGG, BRZ
 Planning: M1-M3

@@ Line 5: / Line 5: @@
 ==Tasks==
-T2.1 Architecture Framework (Leader: MINBZK) (Participants: ATOS, MPTFP-SGAD, DIGST SU, DIGG, BRZ) (M1- M3): This Task will develop functional architecture service patterns (e.g. brokered network, user-centric, API lookup, de-central network) including for cross-border exchange of public services and required evidence with a clear focus on, but not restricted to, the SDG implementation and a mid-to long-term vision rendered possible by the transformative power of new technologies, such as procedures (re-)designed for the use of Self Sovereign Identity (cf. T2.2). It will define architecture principles associated with the service patterns and structure them along the pre-established time horizons (cf. 1.4.1 Concept). After the initial delivery, the Architecture Framework (D2.1) becomes integral part of the DE4A toolbox (D2.6) and will be further refined in consecutive deliveries (D2.8, D2.9 and D2.10)
+===T2.1 Architecture Framework===
 Outputs: [[D2.1|D2.1 Architecture Framework]]