• Published
  • Review - architecture and non-technical requirements

    Sources

    Key Findings

    Item

    Link/source

    Findings/recommendation regarding USCT simulation

    To be considered?

    Comment

    Item

    Link/source

    Findings/recommendation regarding USCT simulation

    To be considered?

    Comment

    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:

    • 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

    https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/6-onboarding

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

    Yes

     

    Standards

    https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/7-standards

    Loose list of standards, not really of interest for us

    No

     

    Types of security

    https://govstack.gitbook.io/specification/security-requirements/2-description

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

    Yes

     

    Security Terminology

    https://govstack.gitbook.io/specification/security-requirements/3-terminology

    Can be used for reference for us internally

    No

     

    Privacy

    https://govstack.gitbook.io/specification/security-requirements/5-cross-cutting-requirements#5.1-privacy

    Briefly mentioned there, more to come according to Steve

    No

     

    Detailed list of security requirements

    https://govstack.gitbook.io/specification/security-requirements/5-cross-cutting-requirements#5.1-privacy

    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