2023-01-13 - Weekly Update

Jan 13, 2023

About this document: Agenda and notes are kept in the same document, a separate copy of the document is maintained for each meeting. Please add agenda points before the meeting. Action items created in previous meeting and all other unresolved action items are kept in the document. Please tick off any completed items.

Meeting link: https://meet.google.com/rsf-cqaq-eyq at 09:00am CET

Attendees

  • @Ain Aaviksoo (Deactivated) (meeting facilitator)

  • @Philippe Page

  • @Lal Chandran (out)

  • @Benjamin Balder Bach (weekly note keep and time keeper)

  • @sasi

  • @PSRAMKUMAR

Meeting Note

Agenda

Presenter

Discussion

Agenda

Presenter

Discussion

Action points from last week

@Ain Aaviksoo (Deactivated)

 

Updates from TC meeting

@Ain Aaviksoo (Deactivated)

Feedback on Compliance Concept and Integration. Scenarios (link to Confluence page) (by Digit). Any impact on our API development?

Feedback on “Architecture and Non-Functional Requirement” document (link in GitBook). A dedicated team is looking for volunteers to work on it over next 2 months.

Tech Committee action items to all wave 1&2 BBs.

New UX for compliance of API testing has been presented. We will go over it in another meeting.

  • Feedback and remarks to send back.

  • What metrics for compliance comparison to Consent BB?

Gherkin scenario

@Benjamin Balder Bach @Ain Aaviksoo (Deactivated)

Status update based on scenario drafting document: https://govstack-global.atlassian.net/wiki/spaces/GH/pages/120946795

Consent BB Spec 2.0 planning

@Ain Aaviksoo (Deactivated) @sasi

Must move forward with next version of spec. First task: identify reference usecases

  • Unconditional Social Cash Transfer as the next use-case proposed by Product Team

  • Other potential sources for real world use-cases

  • Sasi may add more here from his experience

  • Ramkumar: There aren’t any GovStack-wide administrative use-cases. We can build up to this. It’s an overarching layer that has not been done yet, but it will come. Work is done with a blueprint for templetizing use-cases. Wes is writing this. This use-case template contains examples that reference scenarios that can be administrative functions. We can already start capturing these scenarios.
    Layer 1: Basic use case documents (cross-BB)
    Layer 2: Use case scenario definitions (BB)
    Layer 3: BB specifications (API, Gherkin etc)

  • To align with Ramkumar’s description of the state of affairs, we can start to deliver specifications for administrative practices by defining scenarios.

Tenders:

  • There might be additional features for tenders/applications that can add 20% to their score.

  • We should look at our own reference with the eyes of the tenders.

  • If a vendor discovers gaps in the specification, they are free to suggest and can get a boost in their score.

“Consent management” definition

@Ain Aaviksoo (Deactivated)
pushed to next meeting

We renamed “Consent Management BB” to “Consent BB”. Is there a useful definition of “consent management” that we can apply?

AOB

all hands

New potential member(s) to Consent BB

Consent BB tender out around end of January

New Action Items

@Benjamin Balder Bach will participate in non-functional requirement reviewing
@Ain Aaviksoo (Deactivated) will discuss with @sasi around links with IDBB
Everyone: Consider reading the use-case INST-1 Unconditional Social Cash Transfer - @Ain Aaviksoo (Deactivated) share link to GitBook page on Slack.
@Ain Aaviksoo (Deactivated) to reschedule the weekly meeting for 9:30 AM and call for a meeting on ID BB and a Spec 2.0 planning meeting.

Action Items from previous meetings

@Benjamin Balder Bach update Tracking Pipeline document
@Ain Aaviksoo (Deactivated) Introduce the Gherkin working document
@Ain Aaviksoo (Deactivated) catch up with Yolanda re: new use cases
@Benjamin Balder Bach and @Lal Chandran add latest IMAGE renditions of sequence diagrams.
@Ain Aaviksoo (Deactivated) and @Benjamin Balder Bach come up with major themes / features for Gherkin work
Presentation of API endpoints, mocks and tests for technical committee meeting Thursday @Ain Aaviksoo (Deactivated) Everyone: Read email forwarded from Jaume about new IMBB
Book Consent working group for an extended hour of Gherkin Scenario writing for next Friday’s meeting. @Ain Aaviksoo (Deactivated)
Next meeting: Feedback on API test reporting UX
Compliance concept - @Ain Aaviksoo (Deactivated)
Finish the first full draft of Gherkin scenario service APIs - @Ain Aaviksoo (Deactivated)

Decision