[Meta] Scope and requirements for the "Technischer Durchstich"

In Scope

Priority 1

  • Define demo use-case and example messages used in our presentation on friday.

    • Something we can show during our presentation
    • Scenario: User submits application via an online service and follow-up communication.
    • 1 message from Fachbehörde to web/mobile app. (Plain text message are the top priority for implementation.)
    • 1 message to send back
    • 1 Bescheid (government decision)
    • @KristinHaenelt will help creating the slides for the demo on Friday.
  • Login: user name and password. -> #36 #207 (closed) #200 #223 #224

    • Citizens can log in using the BundID username and password authentication mechanism.
    • Use BundID Integration Environment (Fallback: BundID Simulator) as an authentication provider against the Matrix server.
    • @OC000089264938 will start deploying Keycloak in our DEV environment.
  • Sending a Matrix-based message from a demo Fachverfahren (Element Web) to the Web and iOS apps. -> #205 #227 (closed)

    • Plain text message (not structured data!) is the top priority (if possible, also send end-to-end encrypted messages).
    • Verification is out-of-scope.
    • Matrix path only: Demo Fachverfahren (Element Web) -> Government Synapse -> Citizen Synapse -> Citizen Client (app/web app)
    • There are no other requirements from the Fachverfahren side. Authentication against the Matrix home server can be performed in any way possible. We thus select stock Element Web as Demo Fachverfahren for this project phase.
  • Sending a reply from the web and iOS app to the demo Fachverfahren. -> #205 #227 (closed)

    • Plain text message (not structured data!) is the top priority (if possible, also send encrypted messages).
  • Deployment in DEV environment -> #252

    • It should run on the Dev environment: app.dev.neo.fitko.dev
    • Authenticate MAS against the BundID in any way possible (see "Login" above) - this may need additional components to connect the current setup with these surrounding systems
  • Minimal documentation how to run our software components.

  • Create issues for things that come up during the workshop.

Priority 2

  • encrypted messages
  • Consistent list of messages in iOS and web app (no UI required, log files are just fine). -> #228
  • eID-based authentication via BundID against Matrix server -> #225 #226
  • simple UI (polish for demo)

Out of scope

  • Push notifications -> #229
  • Polished UI
  • X509-based device verification #2
  • eID-based device verification #186
  • self-service registration -> #230
  • documentation -> #231
  • ZBP path and migration -> #17
  • Citizen registration -> #232

Goals

Edited by Marco Holz