\uD83D\uDDD3 Date
🐶 Homework
Please try to do the homework, but you are still more than welcome to attend even if you don’t have time!
In the section below, add any and all questions you have about Application Formalization as it related to Cross App SIG. We will use our meeting to sort through which of these problems are ours, and which are being handled by other groups.
...
2024 Meeting and topic calendar
Tara Barnett, Owen Stephens Kristin Martin Martina Schildt Laura Daniels Kimberly Pamplin Kimberly Smith Lloyd Chittenden Dung-Lan Chen Charlotte Whitt
\uD83E\uDD45 Goals
Gather questions about Application Formalization
...
Add Application Formalization Questions Here ⤵️ | Name | |||
|---|---|---|---|---|
How are dependencies being documented between apps? What are implications for dependencies across applications vs dependencies within applications? Is there a difference? If so, what is it?
| Tara+Laura | |||
Is it better for applications to be more modular or more “Integrated”? What does “better” actually mean here? | Tara | |||
Will most end users actually see or care about any of this? If executed perfectly (and if nothing is missed), does this affect functionality as we experience it at all? | Tara | |||
What is the relationship between Eureka and Application Formalization? | Tara | What are implications for dependencies across applications vs dependencies within applications? Is there a difference? If so, what is it? | Laura | |
Related to “Will most end users actually see or care…” – does the bundling into functional areas have any impact on how those functional areas are defined by users? (e.g., if I think all the MARC modules should be separated from the Inventory modules, and others think they should be together, does the formalization affect how we are able to work?) | Laura | |||
Is it better to start out with larger bundles? How much of the decision-making happening now affects what we are and are not able to ask for or do in the future? | Laura | |||
Is the aim that ultimately modules that are part of the same application will have access to a common database schema or set of database schema? If so, how do we get from the “formalisation” in terms of a definition of an app made up of multiple modules, to that more integrated sharing of data? | Owen | |||
Will the mechanisms of app-to-app communication/messaging remain the same as the current module-to-module options (i.e. Kafka message queues)? | Owen | |||
What specifically should the App interaction group be considering in relation to app formalisation (e.g. as opposed to POs or SIGs or Devs) | Owen | |||
What is the timing for Application Formalization and how could App Interaction provide feedback in a meaningful way? | Kristin | |||
Can app formalization follow a plugin model that allows the expansion of the core apps without spinning up a new container? | Thomas | |||
...