Non-Functional Requirements meeting 2018-08-02

Date

02 Aug 2018

Attendees

• Sam Im (Deactivated)

• Nikodem Graczewski (Unlicensed)

• Chongsun Ahn (Unlicensed)
• Łukasz Lewczyński (Deactivated)
• Joanna Szymańska (Deactivated)
• Sebastian Brudziński
• Mateusz Kwiatkowski
• Klaudia Pałkowska (Deactivated)
• Paulina Buzderewicz

Goals

• Discuss any questions about the Non-Functional Requirements
• Compared to current 3.4 performance, what do we need to do to meet the NFR?
  • What is the approach we should take?
    • Represent what the system currently supports, current working data should reflect what the system actually supports
      • We don't want to keep using Malawi data set, we want our own performance data that has the same data as Malawi
      • Malawi data is only on perftest, doesn't have any stock management data, some fulfillment data
      • Audit the demo data to determine how much more we need to add, if we need to take a different approach to pulling data from other implementations and scrubbing
    • Propose what we want to get to (stock management)
      • For stock management, is offline support important?
      • Automated tests to track performance against targets

  • OLMIS-4658 - Getting issue details... STATUS

  • Get feedback from other things to include in the NFR

Action items

• Sebastian Brudziński to create stub tickets and have Wesley Brown review