Other Arkitekturstyring

Other Arkitekturstyring ()


Etablere/få på plass felles arkitekturstyring
Avoid the risk of creating new digital barriers for administrations, businesses, and citizens
Need for a common terminology to design, assess, and communicate about e-Government solutions
Need for a stable interfaces for digital public services
Need for an overview of already existing solution building blocks
Reference architecture for delivering digital public services
Common terminology to achieve a minimum level of coordination
Technology- and product-neutral and a service-oriented architecture (SOA) style
Alignment with EIF and TOGAF
Designing: accelerate the design of e-Government solutions that support the delivery of interoperable digital public services (across borders and sectors);
Assessing: provide a reference model for comparing existing architectures in different policy domains and thematic areas, to identify focal points for convergence and reuse;
Communicating and sharing: help documenting the most salient interoperability elements of complex solutions and facilitate the sharing of (re)usable solutions.
Discovering and reusing: ease the discovery and reuse of interoperability solutions.
Business analysts
Architects
Portfolio managers


		Etablere/få på plass felles arkitekturstyring	Avoid the risk of creating new digital barriers for administrations, businesses, and citizens
		Need for a common terminology to design, assess, and communicate about e-Government solutions	Avoid the risk of creating new digital barriers for administrations, businesses, and citizens
		Need for a stable interfaces for digital public services	Avoid the risk of creating new digital barriers for administrations, businesses, and citizens
		Need for an overview of already existing solution building blocks	Avoid the risk of creating new digital barriers for administrations, businesses, and citizens
		Reference architecture for delivering digital public services	Need for a stable interfaces for digital public services
		Common terminology to achieve a minimum level of coordination	Need for a common terminology to design, assess, and communicate about e-Government solutions
		Technology- and product-neutral and a service-oriented architecture (SOA) style	Need for an overview of already existing solution building blocks
		Alignment with EIF and TOGAF	Avoid the risk of creating new digital barriers for administrations, businesses, and citizens