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

Owned by Nico Lueck
Last updated: Apr 19, 2023
1 min read

 Date

Apr 19, 2023

 Participants

@Nico Lueck

@Steve Conrad

@Wes Brown

@Dominika Bieńkowska (Deactivated)

 

 Discussion topics

Item

Notes

Item

Notes

 

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

 

 Action items

Rework compliance concept @Nico Lueck

 Decisions

  1. Continue this discussion in the Product Committee