Differentiate between deliverable types:

• Use Case Simulation → Learn

• Use Case Vertical Prototype → Demonstrate

• Use Case Replicable Vertical Prototype (Emulators only?) → Test and Use

Design + Frontend 11-12 2023

see High-School Certificate for reference

Version 06.11.2023 (update 15.11.2023)

Focus until EOY 2023 @Meelis Zujev (Deactivated) @Vasil Kolev

1. Documentation (improve and test with users)

   1. Instruction how to build the full stack system with BB implementations, not only USCT DIY Package

   2. GovStack Internally: How to add new BB (with own use case UI, not part of USCT). Guide to Open up Sandbox (or DIY Minikube) for additional BB

2. Infra (finalize)

3. Middleware RPC

4. Use Cases (Construction + High School)

5. Presentation of stack components (infra, APIs, admin UIs) Requirements for Presentation Purposes and DYI Offeringarchived

6. Consent BB

7. Visual suggestions for examples on future iterations: e.g. sandbox portal, government portal, centralized admin UI

8. Conceptual suggestions for architectural contributions: e.g. Unified Testing Capabilities, Self-Compliance Testing, Unified Data Loading Interface

Version 13.09.2023

Sandbox Documentation/Guidance

• Infrastructure

• Build and Deploy (multiple BB in one place)

• Architecture

• Project management and how to work - methodology

• Use Case Design and Development

USCT 1.5

Simulation

• ---

Vertical Prototype

• Horizontal coverage (steps) are flexible but should at least

  • MOSIP Integration (e.g. Foundational ID Creation)

  • XRoad Integration

  • Citizen Portal Screen (to choose the USCT case)

• Gitbook portal to access use case

• Documentation/Guidance

  • As-Is: Architecture, Use Case diagrams, Design of Backend App, Authentication & Authorization, CI/CD, Infra and any other interesting configs, Deployment and Hosting Scenarios (in same env or externally),

  • Example: https://core.digit.org/guides/installation-guide (We have someone, Neil, who worked for that organization. We can interview him on their documentation strategy, if needed)

Replicable Vertical Prototype

• Packaged version of vertical prototype (similar to Oleksiis Presentation in Egypt)

• Documentation/Guidance

  • How to deploy/recreate Infra and CI Layer

  • How to exchange Emulators with BB

USCT 2.0

Simulation

• Maintenance, Smaller Changes + Google Analytics

• Documentation/Guidance

  • Our Service Design Journey: Use of Playbook and Service BLueprint

  • For GovStack: How to reuse with new use cases

Vertical Prototype

• Horizontal coverage (steps) are flexible but should at least

  • Any IAM Integration (not hard coded but as a BB)

  • Mifos Integration

  • OpenIMIS Integration

  • Ready for Ukraine Platform of Registries Integration in 2024

  • Ready for Consent BB Grant.io Integration in late 2023 or early 2024

  • Use of the Xroad PubSub functionality

  • Optional: Integration of a OS Workflow Software

Production ready version of simple use case (USCT 2.0)

The USCT is virtual use case. It’s purpose is to demonstrate the infrastructure capabilities to build some meaningful piece of software that adheres to the most recent industry standards and can be used as example implementation for productionized development. We need to enhance in this direction, so whatever code we provide in the repository to be reusable at least as development strategy in production environment.

• In case of using real implementations for BBs then the expectation is that they are production ready

• The front end of an BP use case is currently showing one of the best practices for UI development and can be considered close to production quality (should be enhanced to this). Learnings to be adopted to USCT

• The orchestration backend must be improved to production readiness in terms of:

  • Security

  • Authentication

  • Authorization

  • Scalability

• Infrastructure is already scalable, however we did not have any load balancing implemented on the orchestration backend (TBD and implemented)

• Current BB setup is missing key implementations for building blocks (should be acquired and used as BB not as libraries or standalone installations)

• The USCT needs to showcase at least one example per BB integration, so it can be used as starting point from adopting partners

• The use case to provide capabilities to showcase the interchengability of BBs with the same interface

Online Construction Permit

• Service Blueprint (and BPMN?)

• Vertical Prototype reusing USCT Backend

Somalia or Health Use Case Simulation

• Service Blueprint (and BPMN?)

• Use Case Simulation

General

• Service Blueprint part of Implementation Playbook

• Be ready for new assignments in the future:

  • Every part will documented and assets are stored to continue development at some point in 2024/25

  • CI: Procedure to integrate new BB

• Internally: Write down all learnings from the project to later create a document which gives advise to goverments doing similar projects

Version 01.08.2023

USCT Use Case

Use Case Simulation

• Maintenance, Smaller Changes + Google Analytics

• Documentation/Guidance

  • Our Service Design Journey: Use of Playbook and Service BLueprint

  • For GovStack: How to reuse with new use cases

Vertical Prototype

• Horizontal coverage (steps) are flexible but should at least

  • One feature/function for BB Pay, ID, Registry, Consent and IM PubSub

  • BB Integration: Mifos, MOSIP, XRoad, [Consent BB]

  • Optional: Integration of OpenIMIS once Soldevelo finished Adapter, Integration of a OS Workflow Software

  • 2024: Integration of Ukraine Platform of Registry

• Portal to access use case

  • Show that BBs can be selected. e.g. BB Pay: Mifos or BB Pay Emulator

• Documentation/Guidance

  • As-Is: Architecture, Use Case diagrams, Design of Backend App, Authentication & Authorization, CI/CD, Infra and any other interesting configs, Deployment and Hosting Scenarios (in same env or externally),

  • Example: https://core.digit.org/guides/installation-guide (We have someone, Neil, who worked for that organization. We can interview him on their documentation strategy, if needed)

Replicable Vertical Prototype

• Packaged version of vertical prototype with Xroad and Emulators to deploy in own Environment

• Documentation/Guidance

  • How to deploy/recreate Infra and CI Layer

  • How to exchange Emulators with BB

Need more conceptualization!

Online Construction Permit

• Service Blueprint (and BPMN?)

• Vertical Prototype reusing USCT Backend

Somalia or Health Use Case Simulation

• Use Case Simulation or Vertical Prototype

General

• Service Blueprint part of Implementation Playbook

• Be ready for new assignments in the future:

  • Every part will documented and assets are stored to restart development at some point in 2024/25 → Find client and together continue prototyping

  • CI: Procedure to integrate new BB

• Internally: Write down all learnings from the project to later create a document which gives advise to goverments doing similar projects

What I would like to achieve with the end results?

• Explain GovStack to Non-Techs with Simulation

• Showcase Feasibility and How we brought GovStack approach to live with the vertical prototypes

• Make recreation of sandbox as easy as possible. If not packaged deployment version, then describe steps and point out resuable assets on github