4.3 Architecture Scope

Defines the three layers of architecture that GovStack distinguishes and clarifies where this specification applies and where to look for broader governance guidance.

The GovStack Architecture Specification with its Principles and Cross-Functional Requirements are applicable to what is commonly referred to as system and component architecture to support digital government interoperability. GovStack differentiates between:

• Government Architecture describes structure, behaviour, and views of the whole of government on governance, legal and digital layers. GovStack has published PAERA (Public Administration Ecosystem Reference Architecture) that covers these aspects and it is a highly recommended reading for leaders of government IT. More: PAERA

• System Architecture describes structure, behaviour, and views of the technology, data and application layer across multiple entities or within one entity of a government. In GovStack, this usually refers to the interaction between multiple Building Blocks, service applications, micro services or other components. The C4 system context diagram or C4 container diagram can be used for visualization.

• Component Architecture describes structure, behaviour and views of one system component. In GovStack, this usually refers to the inner architecture of one Building Block, service application or a microservice. The C4 component view can be used for visualization.