March 31, 2023 Architecture Team Meeting Notes

Attendees

@Aare Laponin

@Jukka Aaltonen (Deactivated)

@PSRAMKUMAR

@Wes Brown

Apologies

@Steve Conrad

@Aleksander Reitsakas

@Uwe Wahser

 

Agenda

Presenter

Duration

Discussion

Update on Review Process

@Wes Brown

 15 minutes

Review tasks are assigned here:

https://govstack-global.atlassian.net/browse/TECH-394

https://govstack-global.atlassian.net/browse/TECH-393

All comments to be logged here: Architecture Team Review

 

Steve: Consent and Workflow reviews here: Consent Feedback Consent Feedback

Can Steve/Ramkumar merge any changes from these reviews into the specs, so we don’t have to wait on BB teams? Any technical questions/clarifications can go directly to the BB teams as we work through the reviews.

Comments:

  • Wes: There are still major differences between how the BBs are written and the template. Most BBs have not changed their format/structure to match the template, though I’m not sure if they had been instructed to do so.

  • Ramkumar: (Paraphrasing) The template needs some changes to be more helpful and to present information in a way that is easily consumable

Not discussed

 

 

 

Adaptor Conversation

@PSRAMKUMAR

40 minutes

Recap and comments on current approach for onboarding existing tools: https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/6-onboarding

Discussion on adaptors and phased approach

  • Is the current approach correct? What is missing?

    • Clear definitions of the various components, such as Information mediator

      • When we talk about Information Mediator, what do we mean? Are there separate components that should be described, such as service discovery, API Gateway, payload transformation?

      • When is a Workflow orchestration needed and when can BBs simply call other BBs (either with or without IM)?

    • Clearly defining interactions between UX/UI and services provided by BBs

    • Do we need to address Authentication/SSO/tokens

    • If a DPG encapsulates multiple BB functionality, how do we handle that?

    • Are the phases that are currently defined correct?

  • Updating the current documentation and publishing new guidance for DPGs and implementers

  • After we develop guidance, work with testing and sandbox team to validate. Identify first products to work with and build adaptors for

Next steps/AOB

 

5 minutes

What should we prioritize?

Can we spin off small groups to work through specific tasks?

Action Items

All to review comments (on Confluence and GitBook) and mark which things need to be done for the 1.0 publication (Now) versus in the future (Next)
All to review the BB specification template and suggest changes (comments in GitBook is fine) so that we can make any required changes for Valeria (and others) to align the BB spec to