Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some ideas for improvement #10

Open
sebinside opened this issue Jan 27, 2022 · 0 comments
Open

Some ideas for improvement #10

sebinside opened this issue Jan 27, 2022 · 0 comments

Comments

@sebinside
Copy link

sebinside commented Jan 27, 2022

Here are some of the ideas for improvement and feature requests beyond #9:

  • Conditional variations (just what we talked about in the last meeting)
  • Generate an overview CSV file: It's currently hard to determine which alternatives were chosen for each variation. However, this information is of course known at runtime so it could just be stored as a single CSV file while generating
  • New variation type: Data Operations. The approach for data flow analysis allows the modeling of characteristics (already possible to create variations) but also defines manipulations of data labels (can be seen in the graphical editor in usage models and SEFFs). This could be another interesting point to vary. They are at least saved in the .aird file, e.g., here in line 6654, 6662 etc.: https://github.com/FluidTrust/CaseStudies/blob/main/casestudies/PortCaseStudy/representations.aird They are contained in the SEFF-Elements inside the repository
  • Optimizing performance: An option to parallelize the generation would be interesting, however this might conflict with some eclipse internal magic
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant