...
- diagram needs to make it clear what a system integration would be (to ODK2 or OpenSRP) as opposed to a direct mobile app interfacing directly with OpenLMIS REST API over HTTP with JSON.
- what does 100+ mean? Should we define workflows based on the volume of data?
- Should we explicitly call out "shipping a mobile library" rather shipping an OpenLMIS app as a possible strategy?
Action Items
- Paweł Albecki (Deactivated): take the feedback from the DDD and package name improvements and show through a diagram and/or use of the example service what it'd look like given that feedback
- Josh Zamor: re-write the key requirements section to address the workflow to non-functional requirements (the what does 100+ products mean)?
- To the group: bring up what you'd like to see as part of the technical mobile strategy in the dev forum (Product Committee may look at some of this feedback)
...