Skip to end of metadata
Go to start of metadata
| Topic | A. Incremental | B. Rewrite |
|---|
| Time to Completion | Slower | Faster (because of less technical debt to manage, decreased tech risks, and lack of fast-track support) |
| Technical Risks | - Unclear whether 'slice' approach will work and the degree of untangling that will be required.
| - Lack of written business requirements and user stories for OpenLMIS v1 will require reverse engineering requirements from OpenLMIS software
- Lack of any consistent staff from first project working on re-write – possibility things may be missed
|
| Incremental Value | Value available with each release | None until project matches functionality of OpenLMIS 2.0 (with toggle off feature set) |
| Technical Quality | | Likely higher due to ability to start with a clean slate, particularly in regards to test coverage. |
| Migration Path | | |
| Scope | | |
| Cost | | |
| New Implementations During Project | New implementations can take advantage of incremental releases, have possibility of working with community on needed extension points | New implementations before completion will use 2.0 and have to upgrade later. |
| Community Collaboration | | |