Agenda

Presenter

Duration

Discussion

Review Process

@Wes Brown

@Steve Conrad

 30 minutes

Discuss Updates to BB template (in process): GitBook

• Section 4: Move the components (section 2) over to section 6. No need for 4.1 header - just provide a brief description and simplify the KDFs (still grouped by functional area). Less prose - just quickly show the key functionality that should be available. Some of the extra technical description currently in section 4 can be moved to section 6 as well.

  • Try to structure as a simple list (4.1, 4.2, 4.3) where each item has a title and brief description

• Section 6: First section will define the components of the building block. Use diagram and brief description of each component

  • Second section will reference each KDF from section 4 and outline functional requirements needed to implement (defined a bit more broadly than is currently shown). No need for technical details here. Should be able to define UATs from this section. Reference section 6 from scheduler for content - keep format the same

• Section 7: Remove standards from the table - reference any standards at the beginning of the section

  • Find standard method for rendering the resource model (.drawio format)

Steve, Wes, Valeria will work to migrate existing specs to the template format.

Review tasks are assigned here:

TECH-394: Review of BB specificationsDone

TECH-393: Review of non-functional and security requirementsDone

All comments to be logged here: Architecture Team Review

• Consent and Workflow reviews here: Consent Feedback Consent Feedback

We need to create Jira tasks for work that needs to be done by BB teams - put link to specific GitBook comment in Jira ticket.

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.

GERA Document Review

@Steve Conrad

10 minutes

Purpose of the Document

Open

Can architecture team review this document as well?

Adaptor Conversation

@PSRAMKUMAR

30 minutes

Proposal from Nico to work with Sandbox team on Adaptors

Recap and comments on current approach for onboarding existing tools: 6 Onboarding Products | GovStack Specification

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?