March 17, 2023 Architecture Team Meeting Notes

Attendees

@PSRAMKUMAR

@Wes Brown

@Jukka Aaltonen (Deactivated)

@Satyajit Suri

@Steve Conrad

Apologies

 

Agenda

Presenter

Duration

Discussion

Introductions

@Steve Conrad

 5 minutes

Introduction of all architecture team members

 

Arch group members and mandate

@Steve Conrad

10 minutes

Who is the architecture team and what is our mandate

  • Take on issues that cross multiple building blocks

  • Resolve questions from BB groups that cannot be resolved internally. Be the group that makes binding decisions.

  • Bring in people to support on specific topics (ie. Uwe Wahser)

  • Is our mandate related only to specifications or also with sandbox and reference implementations?

  • Ownership of documents/specifications that are cross-cutting (security, UI/UX guidelines?)

  • Sub-committee of Technical Committee

Decision making process

  • Majority rule of voting members (we will seek to be unified in decisions where possible)

  • Voting members:

    • Ramkumar, Steve, Jukka, Aare ?, Wes, Satya, Nico ?

Develop our mandate/priorities to present to GC

Links to resources

@Steve Conrad

5 minutes

Walk through various resources: Jira, Confluence, GitBook

Overview of Architecture team work

@Steve Conrad

15 minutes

  • Review and rework the GovStack non-functional and security requirements

  • Review specifications from BB working groups

  • Review Use Case example implementations

  • Provide recommendations on specificity and standards for GovStack

  • Identify a process and examples for onboarding existing products and creating adaptors: https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements/6-onboarding

  • Coordinating BB specification and testing work with the sandbox team and implementation

  • Review and provide input to the GovStack compliance concept (Software Compliance Concept )

  • Respond to specific questions coming from BB working groups that cannot be resolved in Technical Committee (primarily focused on architecture)

  • Identifying and prioritizing Building Blocks to be developed and what is a BB

  • Review GERA document from Open Group and integrate any guidance that is relevant

  • Develop/own FAQ and terminology documents

Prioritize and assign leads

@Steve Conrad

20 minutes

Review of Building Block specifications: @PSRAMKUMAR

  • All arch team members to review and provide feedback. Focus on technical content.

  • First review to be done by March 31

Review of non-functional requirements and security requirements: @Jukka Aaltonen (Deactivated) @Satyajit Suri

  • Initial review and feedback by March 31

Develop functional requirements for adaptors:

  • Ramkumar to present current state on March 24

Next steps/AOB

 

10 minutes

Link any existing review tasks from Jira, create any new tasks that are needed for review

Any notes/lists of changes can be tracked in Confluence (in Publication Planning section: Publication Planning ). New tasks can be created for work that needs to be done on the BB specs based on reviews