2023-04-19 - Compliance Concept - Define scope and timeline

https://govstack-global.atlassian.net/wiki/spaces/GH/pages/76906515

Nico

• Objectives: Be ready for candidates testing and for communications

• Presenting status quo of concept

Wes

• Decision by GC “Yes, we want compliance process”

• Run through the process

Steve

• Non-Functional Requirements of Arch Specs are reworked

• BB Specific Requirements: Check functionalities → Deeper compliance check via APIs

• Compliance will be use case dependent since APIs are dependent on Use Cases

Dominika

• APIs are not distinguished between MUST and SHOULD. If we need to, we need to do it ASAP

Discussion result

Change categories to non, partially and full compliance

Non-compliant: Not fulfilling the required (MUST) Key Digital Functionalities

Partially compliant: Key Digital Functionalities + X (some of functional and API, at least one each)

Fully compliant: Key Digital Functionalities + All functional and API