Husika Early Warning - Objective, scope, roadmap

Objective

Provide proof for a backend architecture enabling the Husika App to scale in terms of geographically and organizational distributed users (information providers and consumers) and in terms of useability by end users (esp. back channel to provide feedback)

(users = organisations/stakeholders/persons on all 4 levels)

Scope

A) Preparing the architecture for additional users by re-factoring the backend:

  • Co-design future Husika 2.0 technical architecture

  • Serve selected APIs with Building Blocks (e.g. Registry, Messaging)

  • Rebuild the handling of "warnings" with an event-driven/pub-sub architecture

    • Important requirement: Allow for adding use cases modules (e.g. Climate Data, Conflict Data, Pest Movement, Rangeland / Plant Health, Water, Migratory Data)

    • Possibly, two different frontend dummy applications subscribe and act upon an event in the pub-sub room

  • Integrate Information Mediator BB (X-Road) to enable secure data exchange among multiple users (Level 1-3) (delisted on 20.09.2024, agreed target architecture doesnt use X-Road)

  • De-normalize data to increase system performance (to be discussed in development)

B) Increasing the usability and value for end users by adding bi-directional communication:

  • Use the Messaging Building Block to enable bi-directional communication for end users (add user-friendly channel to send feedback)

  • Design a communication flow for end user issued SMS-responses

C) Planning towards production based on architecture document and prototype

  • Based on the evaluation of the current app, the to-be-architecture and the prototype the teams (Husika and Gofore) co-design a path towards production

 

Further "Areas of improvement" mentioned in ch. 4.2. are scheduled in the backlog for later development sprints and remaining time resources

Assumptions

  • ICPAC is joining and providing feedback through out the development process.

  • The Husika application code (frontend and backend) will be made available to the developer team.

  • The developer team's selection of software for the prototype is not a prescription for the Husika team’s way forward to production. Software selection should be done by the Husika team again for production based on technical environment.

  • The existing frontend will be used as much as possible. A additional API layer might be needed to properly orchestrate the API calls to the Building Blocks.

Roadmap

Husika GS prototype - roadmap.png