...
- No documentation on how to get OpenLMIS up and running
- This is true for an implementer. Developer steps are decently documented
- Insufficient developer documentation
- Please clarify. Agree, for example, little guidance on domain, solution design, etc.
- No database documentation
- What is required? ERD, for example, is now part of a build job
- Average BA/non-dev type can't get started - hard to install (vs OpenMRS, etc.)
- Scant API & documentation
- Monolithic app tightly coupled with UI:
- Not extensible and causes lots of forking/toggling (e.g. new screens)
- A lot of the variation is in reporting
- No way to contribute without stepping on the toes of others.
- No CI Server/no Continuous Delivery:
- Update (3/16): We now have Jenkins running to exercise unit tests and DB integration, but functional testing is weak and needs enhancement (e.g. JS tests are not enabled).
- Successful build are not being deployed to Demo
- Insufficient test coverage
- Supportability: inadequate error handling – lots of errors are caught and swallowed; logging is insufficient.
- Older tech stack – Some outdated tools and approaches:
- For those that we want to keep, we need to update to latest/later versions
- Large number of tools & shared libraries that overlap &/or duplicative: Security is a concern and burden
- Poor architectural choices (eg: use of Lombok and approach to exception-handling)
- Using the APIs requires first doing an interactive login
- No end-user documentation of test cases for manual/regression testing
...