Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Announcements



overview of the re-architecting proposal

Craig and Vince will attend the meeting to discuss and answer any questions that may arise.

All: Please watch the recording in advance:


My unsorted questions (Felix):

  1. Applications:
    1. Slide 9: Are there any disadvantages when several BE modules use the same storage? Would there be an advantage, e.g. better performance for read/write accesses?
    2. Slide 10: Merge mod-inventory and mod-inventory-storage into one module? What are the advantages and disadvantages of this?
    3. Slide 11: Independent application development lifecycles. How exactly is this supposed to work? As I understand it, the flower release is also intended to check the interaction between what Vince calls applications. Not only the interaction of BE/FE modules inside one application.
  2. Platform:
    1. Slide 16: I understand Core+Functional to be like the iOS operating system and the Extended part are like applications I can install from the App Store. Would that be a reasonable analogy?
    2. Slide 18: Example ERM: The local KB is part of the Agreements modules, but is not used by the US libraries. How should something like this be handled? You can't simply separate the pieces (AFAIK).
    3. Can one switch from one platform to another, e.g. ERM platform first, then ERM+acquisition platform? Or would one start with ERM platform, stay on it and install the acquisition apps afterwards (as extended)?
    4. Who decides which application belongs in Functional or Extended when it is in dispute?

Questions by Former user (Deleted) 

Who will decide in general (not only when in dispute) which Apps are "common sense" and must be included in "Functional"? What will be the criteria for this decision?
Who will take the resposibility for the "Extended" Apps and that they are capable of running throughout all platforms and all releases and that they are interacting with other apps properly?














PC update

2023-10-19 Product Council Agenda and Meeting Notes

Announcements:

Current state of FOLIO Quality Assurance testing - presenter: Yogesh Kumar, and Oleksii Petrenko. Link to slidedeck here (when available)

Testing methodology: In Sprint Testing by development teams and Release testing (Bugfest - 3000+ testrail cases)



Example on a UAT survey (Poppy, 2023)

Definitions of Smoke test, Critical path, and Extended 

Release planningtime planning:

Image Added

Release roadmap/time line - e.g. Poppy.example


Follow up on Re-architecting Impact on the Product Council report: Link to the report here.

...