PCM Development/Palladio Concall/Minutes 20200811
Agenda Suggestions
Please add things you want to discuss to the agenda below.
- JIRA issues status Dev Board
- StoEx-Xtext fully integrated in master; please create new issues if any problems occur
- SIMUCOM-97
- SIMUCOM-94
- Palladio strategic meeting report
- Future direction of Palladio: discussion about Palladio as a platform for various analysis, ...
- The existing Jira system should be used more for the coordination of the development task.
- Not only bugs or improvements should be entered there, but also all implementations of new features and other ongoing tasks.
- For communication between several partners (FZI, KIT, US, ...) it is not sufficient to communicate via a repository (commit message, readme, ...) in the Palladio Simulator GitHub organization.
- Track students work on separate board (e.g. Kanban), supervisor is responsible to track progress and coordinate the work
- Initial experience with suggested Palladio Review process
- Meta Model
- Extending Parameter with Identifier (Frederik)
- Semantics of unrestricted upper bound of parent data types (Stephan; postphoned until next ConCall)
- shouldn't this be 0..1?
- what is the semantics of multiple parent data types?
Protokoll
Tickets
- EXPAUTOM-1
- Old fix is not available anymore. Check archive code SVN, but initial look by Dominik doesn't seem to promising.
- Fix might work like this: clear whiteboard before starting the simulation.
- SIMUCOM-97
- ask Kim Truong again
- SIMUCOM-94
- ask Sebastian, probably WON'T FIX if it is only a design optimization
- might be code that is used by SimuLizar, then reopen as SimuLizar bug
Strategy Meeting
- Track student work on JIRA board?
- Advantage of a board would be overview, but that could also be done by a suitable query
- Code changes should be tracked in issues should be tracked and marked after students are done (either WON'T FIX, DONE, ...). That is more important.
- Add lightweight description / schema to Wiki that code changes should be tracked in an issue with supervisor / end date.
- Maybe add a field for tracking who is responsible (custom field in JIRA) after we see that the process works sensibly this way. TODO: add here: https://sdqweb.ipd.kit.edu/wiki/Hinweise_zu_Abschlussarbeiten#Implementierungsarbeiten
Initial Experience with suggested Palladio Review process
- First impression (Dominik) is okay
- Ask again next time
Meta Model
Parameter -> Identifier
- No problem apparent. Check old protocols if there is a problem. Document in the ticket.
- Test (example) old models / code
- add constraint for unique name between parameters
Upper bound for parent data types
- Is probably a bug, so it can be changed to 0..1