December 1, 2022 Technical Committee Meeting Notes
Attendees
@Wes Brown
@Karolina Kopacz (Deactivated)
@Steve Conrad
@Dominika Bieńkowska (Deactivated)
@Paweł Gesek
@Damian Szafranek
@Damian Borowiecki (Deactivated)
@Taylor Downs
@Satyajit Suri
@Rachel Lawson (Unlicensed)
@nashcroft (Unlicensed)
@Nico Lueck
Krystian Lider
@Kamil Piotrowski (Deactivated)
@Ain Aaviksoo (Deactivated)
@Martin Karner
@Jaume DUBOIS
@Esther Ogunjimi
Previous Action Items
Action Items |
---|
All wave 1&2 BB to define their core data model (data structure) in GitBook - @BB Leads BB definition template - @Steve Conrad @PSRAMKUMAR @Aleksander Reitsakas to confirm to Steve if he has bandwidth to work on API initial definition for IM BB Get an indicator of when the mock will be ready for compliance - @Satyajit Suri @Nico Lueck Work with BB Leads to build their roadmap in Jira and size up the tasks - @Steve Conrad ONGOING All BB leads yet to, should write their test plan and send to Taylor and Ramkumar (architecture team) to review and sign off. Pending with @Satyajit SuriONGOING Account mapper keeps the ID with payment discussion will be planned with Jaume (IDV BB) to better understand the API - @Mauree, Venkatesen Have focus discussion on role based access control for consent BB and feedback to TC - @Ain Aaviksoo (Deactivated) BB Leads to make a list of existing specification in terms of functionalities (which are the APIs that should be demonstrated) - make a list of what to work on in the specification - send to Ramkumar Collaborate on level 2 testing - @Taylor Downs @PSRAMKUMAR @Aleksander Reitsakas @Ingmar Vali |
Meeting Notes
Agenda | Presenter | Duration | Discussion |
| @Esther Ogunjimi | 10 minutes | |
Use case
| @Wes Brown | 20 minutes |
Wes
Ramkumar The main flow is across BB and continuous flow from various BB. This cross flow can be included in the BB spec Beyond the flow, in an implementation flow - backend flow, screen flow and frontend flow. Do we make assumption that make workflow. |
Update
| BB Leads | 30 minutes | Messaging BB
Workflow BB
Consent BB
ID BB
|
API testing | @Satyajit Suri Soldevelo team | 30 minutes | Satya Readiness to API specification will block the Sodevelo team Pawel
Taylor What is the objective of having already publicly availbale information, password protected? Who wants the public information to be viewable on the website with user name and password, and why? The answers to the above question will justify moving forward with the GS reporting design.
Ramkumar How can metric be generated of people viewing the test result and which?
Satya Traditionally, all reporting engines has some level of authentication because of the different types of users needing different types of dashboards. There will be different types of reports; at BB level, API level and working API to measure the actual versus expected results. It is more of product feature.
Wes The default is open with stats publicly available, and if there are things that need to be restricted, then, there can be user account to support that.
Pawel The team will be implementing authentication (backend). The team will be engaging with designer for mock design, and more informed decision will be taken after the mock requirements is defined. Next Step
|
AOB Sandbox |
|
| Nico Preparing the first UC and checking with BB for which candidate to choose and compliant with most specifications. For mock criteria, which candidate should be put first?
Ramkumar It is only qualified APIs that should get into the sandbox. Suggesting we pipeline the test and integration outcome tack up the APIs that can be handed over to the sandbox.
Taylor The test plan in the various BBs should include the next step proposal - how each BB proposed to carry out functional testing which might differ for each BB- Nico to review the document. Some BBs do not have examples of real software that can implement the spec but they have at least a mock example. We collect example for each BBs.
Satya There needs to be a proper effort for data mining candidate DPGs for BB.
|
Meeting Recording