PCM Development/Palladio Concall/Minutes 20240611

Aus SDQ-Wiki

Participants:

Nicolas, Yves, Nils, Sarah, Floriment, Sebastian, Larissa, Bahareh, Anne, Steffen

Standup

  • Nicolas: Palladio and Dataflow Analysis, student supervision
  • Yves: Investigating Palladio build page, aggregation site: the GMF which was archived is used by others. Java environment is broken in our build.
  • Nils: continuous effort for the dataflow analysis, + Nicolas supervising students
  • Sarah: Fixing stuff on Slingshot.
  • Floriment: Minor devs for Slingshot e.g., refactoring usage simulation, student supervisions w. Sarah.
  • Sebastian: Data flow analysis. Moving steady to the next big release. Next paper for SSP Linz. Think about it while the deadline may be in August!
  • Larissa: Practical course supervision, migrating information from the wiki to the website.
  • Bahareh: transformation between Palladio and Montiarc. Supervising a student to work on composition of analysis, compose Palladio with a static code analyser.
  • Anne: Palladio related: nothing to add.
  • Steffen: Reviewing Florimen’t thesis.
  • Nicolas: Paper with Larissa on ZTA modeling with Palladio and analyzing different kind of quality attributes (accepted in ECSA)

Nicolas: Screencasts in the new Website:

  • 1. problem: deprecated,
  • 2. problem: they were hosted in the typo3 instance. Q: Is it okay to upload them in Yt?
  • Anne: it would be great to upload them. Yt? turning off ads?
  • Yve: copyrights, should not be problematic. KIT bib have a video service too (could be an alternative) 3) bwsyncshare?

Larissa: Workflow engine? Identify which projects are used and which not.

  • Example: Is Workflow engine used?
  • Yve: PerOpteryx uses a workflow engine; SoMox is using it, currently using it.
  • AI @all: check Github Readme whether the repo is being used and the information is still correct.

Misc

  • Advice @all: Students shall not write directly to Nicolas, should try to solve things with their supervisors or prepare the questions better with specifics.

SSP

  • Next time: prepare Dev meeting @SSP, Q: in person in Linz or hybrid?.
  • Anne @all: recheck SSP whether it fits for some small workpackages you were doing.