Review - architecture and non-technical requirements

BB description from GovStack “perspective”

https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/introduction#2.3-building-blocks

• very insightful graphic for role of IM:

  Open

  

• more on the role and proposed usage of the IM is here

• there’s also a BB definition, though the one from DIAL ist just fine and straighter to the point for our audience

• section for BB - UX/UI relation is to be considered

• some definitions for the terms in context of BB that could be useful:

  • Registration

  • Authentication

  • Authorization

  • Workflow Terminology

Yes

Implementation considerations (additionally to Principles for Digital Development)

https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/3-considerations

List of factors which should be considered up front

No

BB Design Principles

4 Building Block Design Principles and Considerations | GovStack Specification

May come in handy if we want to touch on how BBs were designed

No

Onboarding Products

6 Onboarding Products | GovStack Specification

How to connect to existing applications and environments in touched on here

Yes

Standards

7 Standards | GovStack Specification

Loose list of standards, not really of interest for us

No

Types of security

2 Description | GovStack Specification

Build-time Security and Deployment time Security are the types of security - good to know!

Yes

Security Terminology

3 Terminology | GovStack Specification

Can be used for reference for us internally

No

Privacy

5 Cross-Cutting Requirements | GovStack Specification

Briefly mentioned there, more to come according to Steve

No

Detailed list of security requirements

5 Cross-Cutting Requirements | GovStack Specification

https://govstack.gitbook.io/specification/security-requirements/6-security-building-block-modules

Extensive lists of general security related requirements - too niche for our primary users

No