| Table of Contents |
|---|
Use Cases
Common Use Cases the solution must address. Assumes definition of terms, like "Reference Distribution"
...
- Reference UI - how to build, compose
- Do modules package UI into the same repo as module code, or a separate repo?
- Still need reference UI solution that pulls together various web components, both "core" and additional modules
- Database - how to extend core domains, or even new module domains?
- Domain model areas that need more attention:
- Products, especially for packaging (GTIN/GS1), "kits" and some concept of "product Types" to satisfy scenarios such as, "I need 100 doses of BCG (not "BCG 10" or "BCG 20")"
- Hierarchies, such as supervisor nodes, Requisition Groups, etc.
- Design for Program Data
- Should Programs have different supply models enabled for different parts of the supply chain, e.g. requisitions for one portion, informed push for another
- What to call these docker image boundaries...Feature? Vertical? Service?
- Extending domains, e.g. adding attributes to Facilities
- Upfront cost of creating docker images?
- build, deploy, logging, etc. Also, remember this needs to run on (Windows) laptops. Minimum hardware requirements?
- Promotes vertical development amongst different teams
Thought Experiment - Add New Module
Use case: as an implementer, I want to create a module for Informed Push in OpenLMIS 3.x. Team started this thought experiment, but was never finished as evidenced by the sparse content below
Need:
- description of delivery routes (e.g. Delivery Zones)
- Calculating distribution quantities for each Facility on a route
- based on ISA, Consumption, or other means