Members
Accountable Person (only one person)
Responsible Person(s) (“team members doing the work”)
PSRAMKUMAR Steve Conrad Wes Brown Aare Laponin Aleksander Reitsakas Taylor Downs Oleksii Danyliuk
Informed (“keep in the loop”)
Nico Lueck Technical Committee
Product Committee
Team Properties
Status |
| ||||||
Start Date | |||||||
End Date (Anticipated date of last deliverable) | Ongoing | ||||||
Belongs to Committee (only one) |
|
Mission
The GovStack Architecture team’s mission is to provide technical recommendations and guidance to the Technical Committee, Building Block Working Groups, Testing, and Sandbox teams. The architecture team will review questions from these groups and provide decisions, recommended processes, and examples for other GovStack technical teams to leverage.
Deliverables and Maintained Assets
| Info |
|---|
List here the all tangible goods, the Team is working on or maintaining. Please do not list all activities. Find here (Sharepoint Link) the overview of the GovStack Initiative’s overall deliverables. |
Name of the Asset | Link to the Asset (if already existing) | Date or Frequency of expected delivery/update |
|---|---|---|
Non-Functional Requirements Document | https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements | Updated with each GovStack release |
Security Requirements Document |
|
|
Further Activities
https://govstack.gitbook.io/specification/security-requirements | Updated with each GovStack release |
Further Activities
Weekly Architecture team meetings - topics to be determined
Development of Guidance documents for BB working groups, Testing Team and Sandbox team. These will be stored in Confluence (ie. Adaptor Concept and Authentication and Cross-BB Authorization )
Other Information
Link to Work Plan | https://govstack-global.atlassian.net/jira/software/c/projects/TECH/boards/27/backlog?view=detail&issueLimit=100 (Jira or sharepoint) this Jira backlog is also shared with the testing team) |
Founding Partner holding the mandate for the deliverables | e.g. ITU, GIZ, DIAL, Estonia |
Frequency of informing the respective Committee on progress | Weekly updates to Technical Committee |
Obligations to involve Governance Committee | Technical decisions that impact the |
Architecture Team
timelines or scope of GovStack deliveries (specifications, sandbox, or testing) |
Meetings |
Meeting Day/Time: Fridays, 2pm - 3pm UTC Meeting Link: Join the meeting |
Mandate |
The architecture team will be responsible for providing guidance and making decisions about key technology questions related to GovStack. The specific areas that the architecture team is responsible for are:
|
Decision Making and Voting Members |
The architecture team is a sub-committee of the GovStack Technical committee. It is comprised of voting members, and additional non-voting members may be brought in to the architecture team to provide support and guidance on specific issues. On issues where a decision is required, the architecture team will seek to develop a unified consensus. However, decisions may be made by a simple majority vote of the members of the architecture team. The voting members of the architecture team are:
|
Current Work |
Over the next 6 months, the architecture team will be focusd on the following tasks, in addition to any requests that come from other GovStack Groups:
|