Agenda

Presenter

Duration

Discussion

Review pending action items

 @Esther Ogunjimi

 10 minutes

TECH-654: Updates based on technical reviewDone

TECH-670: Candidate ProductsDone

TECH-742: TC Action Items - From 08.06.2023In Progress

Status Update

Leads

30 minutes

https://govstack-global.atlassian.net/jira/plans/reports/6EFAz

 USCT UC USCT-01-Registration

Finalising the data verification step

Written an adaptor for the openIMIS which is in review. BBs are being integrated into the openIMIS

Steve - example implementation should live in GitBook here.

Wes - for the Djibouti online construction permit Use Case, there should be more collaboration between the sandbox team and testing team.

Ensure the testing team has visibility when APIs changes and the changes should reflect in GitBook, MiFos etc ,Published API Documentation - Delivery Milestone 7 . This will be discussed in the testing meeting.

Dominika - there should be an automated ways to get notification when there are changes to the APIs.

Testing

The first version of the testing app is available and all changes are visible on the app GitHub - GovStackWorkingGroup/testing-webapp: Frontend web application for the GovStack test platform.

Sandbox team

Working on the initial version of the USCT Use Case implementation.

Having emulator implementation for payment BB.

Working on demo application for Djibouti Use Case

Providing guidelines on the best approach to install big BBs e.g., IMS, fine rack etc. The proposed direction will be to request the providers to have separate installation of the BBs and work with the sandbox adaptors. Otherwise, the sandbox cannot be agile and provide proper playground without consuming an enormous resources.

BBs living in one infrastructure is good, but there are multiple implementations which are too heavy to coexist in one infrastructure. The sandbox is not a production environment, so there is no way for some of the applications to minify their footprint and lose services. This will be discussed with the partners.

How can we feed the sandbox with real data and implementation?

Architecture team

Continuing working through the UX switching concepts.

Discussing deployment footprint for existing DPGs

Will be talking through the cross BB authentication

Capabilities

@Steve Conrad

Jaume has developed this presentation on ‘Capabilities’: GovStack release capabilities

How can GovStack adopt and use the idea of Capabilities. Core question: Are capabilities related to business processes or technical processes?

Where do we see gaps in the framework between UCs and BBs?

Jaume is proposing to take the building block specs and the functionality that are called out there and then build another layer on top which would expose these capabilities as a kind of business processes.

Artun - there is also gap between design aspects and the development aspects. The focus will not only be for BB but also service design BB.

Wes - There is value in having something that is defined as a capability that allows sharing processes across UCs.

We need to define what capability is and what pieces it needs to have to be considered done?

Steve - There is a clear need for capabilities. We need to define these lower level technical blocks that are used across multiple UCs that are closely tied to UC steps.

How do we architect an application or a UI and have reusable components or common workflows that can be repurposed?

Alek - What is the difference between capability and UC in our terminology?

Ramkumar - The two are clearly two distinguishable levels of abstraction. One is reusable by the upper layer (also called capabilities) and the workflow is reusable.

Taylor - As we move forward with capabilities, we should be specific about where these concepts are coming from because there is overlap with UCs, functional requirements in the specifications and the BBs.

How to handle first BB candidates for test harness?

@Nico Lueck

Connect to BB WG, Soldevelo or rather don't support?

Steve - We can have a quick call with the interested parties and send them the resources that has been documented.