...
| Item | OpenSRP Orderables | Upgrade SIGLUS |
|---|---|---|
| Stock On Hand Interface (Stock Cards in OpenSRP) | Requires redesign of the interface to accept dynamic list of orderables | Does not require major redesign |
| Stock Card Interface Design | Already Available | Recommending usability redesign |
| Stock Card Immutable Ledger | Already Available | Already Available |
| Stock Event Business Logic | Already Available | Needs to be modified |
| Stock Management Business Logic | Needs to be rewritten for Orderables data model | Needs to be rewritten for orderables data model |
| Orderable Data Model | Needs to be created from scratch | Needs to be created from scratch |
| Mobile to server authentication | Already available | Needs to be rewritten to accept V3 oauth2 process |
| Mobile to server syncing | Already available | Needs to be added to OpenLMIS as a microservice |
| OpenSRP to OpenLMIS server syncing | Needs to be created from scratch in Nifi | N/A |
| Bulk inventory business logic | Needs to be created from scratch | Already Available, needs to be modified for orderables data model |
| Bulk inventory user interface | Needs to be created from scratch | Already Available |
| Intents and activities to link OpenSRP app to SIGLUS | N/A | Needs to be created from scratch |
| Ability to add trade items in Android app (The plan is to have this ability in OpenLMIS in the future) | Will not develop. All trade items will be defined server side and synced to the app. | Current feature of SIGLUS. We could block this activity if we state that it's out of scope. |
| Ability to add lots in Android app (The plan is to have this ability in OpenLMIS in the future) | Will not develop. All lots will be defined server side and synced to the app. | Current feature of SIGLUS. We could block this activity if we state that it's out of scope |
Ability to add commodityTypes in Android app | Will not develop. | Will not develop. |
Major areas of risk for the Ona teamUpgrade SIGLUS:
- Generally, there's a schedule and cost risk of having to develop OpenLMIS microservices for this project:
- Authentication upgrade to work with OpenLMIS v3 may require Auth microservice development
- We will need to create a microservice from scratch to manage the mobile deployment syncing, which is a huge undertaking
- Schedule Risks:
- Ramping up on SIGLUS to be proficient in development will take 2-3 weeks for the full time Android developers who are already proficient with OpenSRP, Nifi and the OpenLMIS APIs