2020-01-14 Requirements Review

Date

Jan 14, 2020

Participants / Stakeholders

• @Felimone Amone Junior

• @Matthew Kumbuyo (Deactivated)

• @Chongsun Ahn (Unlicensed)

• @Christine Lenihan

• @Ben Leibert

• @Sebastian Brudziński

• @Aleksandra Ciesińska

• @Mateusz Kwiatkowski

Notes

• Many of the desired Portuguese updates are applicable to the global version of OpenLMIS as well. Given that such changes would effect Angola, @Felimone Amone Junior will review them with @Dércio Duvane to get his approval.
  
  
  

• Dercio can potentially offer guidance regarding how to update Portuguese translations. Alternatively, @Matthew Kumbuyo (Deactivated) and @Felimone Amone Junior are welcome to ask Ben and the rest of the dev team to make them. In that case, a screenshot of the relevant OpenLMIS page would be helpful, and would inclusion of the original Portuguese in text format. While the screenshot would give us visual context for the change, the separately included Portuguese text would help us find and replace it within the appropriate project.
  
  
  

• Because making translation changes should be relatively quick and easy, they needn’t be our focus at the moment. Reports will likely take much longer. Depending on their requirements, we may need to start work on them asap in order to have a chance of completing them by month’s end. We therefore need to finalize their requirements as asap.
  
  
  

• Because they involve new data, there’s particularly high uncertainty regarding the Volume Capacity reports. They could take 1 - 3.5 weeks to implement. The dev team should therefore likely deprioritize them and instead focus on the:

  • Stock availability report (which show stock on hand and stockouts)

  • Cold chain allocation report

  • Requisition related reports. (There are two of them: a timely submission of requisitions report and a fulfillment report, the latter of which presents the ratio between requested and supplied quantities.)
    
    
    

• OpenLMIS v3 supports Jasper alongside the new Superset reports.
  
  
  

• @Matthew Kumbuyo (Deactivated) and @Felimone Amone Junior ultimately have the best sense for what the reports should look like. They’ll work together this week to:

  • Identify which pre-existing reports within the Angola, Malawi, SIGLUS, and the default versions of OpenLMIS can be reused within SELV to fulfill its needs.

  • Create mockups of any necessary reports which aren’t already offered within a pre-existing system. They’ll indicate within each mockup whether Jasper or Superset should be used for the implementation.
    
    
    

• Offering the above guidance by the end of Friday, 1/17, would allow the dev team two weeks to work on the reports.