Update on Review Process | Wes Brown | 15 minutes | Review tasks are assigned here: Jira Legacy |
---|
server | System JIRA |
---|
serverId | f5c6bdaf-d23e-347d-a1e8-579e20a81dda |
---|
key | TECH-394 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | f5c6bdaf-d23e-347d-a1e8-579e20a81dda |
---|
key | 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? |
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
|