Overview

Date: 09.02.2023

Objective: Weekly space for deep dive topics

Participants: (kindly only add your own names, not those of other participants)

• @Uwe Wahser

• @Dragos Dobre

• @Marco Kalin

Topic Proposals:

• GovStackSandbox:

  • Damian: Introduction into SolDevelo's work with Govstack and where he sees technical implications for openIMIS (based on SolDevelo experience as developers in both worlds)

  • Patrick Delcroix: Explain the necessary steps to get the Universal Cash Transfer example running, that we had worked on last year

  • Heidi Kuum: Introduction on her work on around the UCT use case

Presentations / Attachments

Minutes

• Soldevelos GovStack work (Test harness):

  • BB template: GitHub - GovStackWorkingGroup/bb-template: A template, used to create a new repository, issue queue and supporting toolset for a Building Block specification

  • Registry BB example: GitHub - GovStackWorkingGroup/bb-digital-registries: Digital Registries Building Block for GovStack

  • Overview of tests: govstack

• Revamping the openIMIS wireframe example on Universal Cash Transfer

  • https://docs.google.com/presentation/d/1IZh5FQIqgmVkk7KU0ui8ETVaFawfsT-DFO8Zql6G-mU/edit#slide=id.p1 (slide 32 ff)

Questions

• What compliance testing means?

• What score (% of tests passed) makes a BB compliant to GovStack?

• Which BB is tested during a compliance testing?

• Who makes the requests and who execute the business during the compliance testing?

• Is there a standardized integration protocol (i.e. for payment systems) or each system has its own integration protocol (has different test cases/gherkin per protocol or there is a mediator that makes some standard ETL to custom)?

• How the testing is managed (one-by-one or globally with one run)?

• What’s the periodicity/limit of compliance testing (every new version of BB or once per period/year)?

Additional Resources