VariaMos is a Java-based tool for defining variability modeling languages, modeling (dynamic) product lines and cyber-physical self-adaptive systems, and supporting automated verification, analysis, configuration and simulation of these models.
Home Page: https://github.com/SPLA/VARIAMOS/wiki
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
The operations using the solver stop responding after several calls to the solver.
The solver should not stop responding. It should not be necesary to close and open VariaMos again to execute operations
Execute several calls to the solver. At some point, the executing does not end. Subsequent executions does not end.
Improve the usability of the tool
Variamos version:
1.0.1.20
For Tooling issues:
Platform: Windows
Others:
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ x] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
Missing deploy diagram that shows third-party libraries required by VariaMos and deployment structure
Elaborate the diagram. Put the Draw.io files inside the docs folder and put the png file and their explanation inside the wiki ( Variamos architecture page)
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
On Linux when VariaMos is compiled by using gradle, appears mutilple errors in lines that have accents or special characters
Do not have any compilation error when a gradle building task is excecuted
Open console > gradle build
Variamos version: 1.1.0.1
For Tooling issues:
Platform: Linux
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x ] Improvement request
[ ] Support request => Please do not submit support request here
Hide the following buttons from the menu bar when the model configuration/simulation perspective is active.
Hide cut, copy, undo, redo paste
We can hide these buttons because there is not elements to copy or paste under this perpective. In addition, currently undo and redo options are only available for modeling functionalities, then on this perspective are useless
Variamos version: 1.0.1.20
For Tooling issues:
Platform:
Others:
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
On the prespective "Semantiv and Operations meta-models" the menu "Translation configuration" is not visible anymore we solved the issues #245 and #246.
The menu should be visible.
Open variamos > Window > Show advanced perspectives
Variamos version: 1.1.0.1 ( refactored version)
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x] Improvement request
[ ] Support request => Please do not submit support request here
We have to merge and rename the FileUtils.java and the FileUtilsApache because both files provide similar functionalities.
com.variamos.common\src\main\java\com\variamos\common\core\utilities\FileUtils.java
com.variamos.common\src\main\java\com\variamos\common\core\utilities\FileUtilsApache.java
Variamos version:
Development branch
For Tooling issues:
Platform:
Others:
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[x ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
Building instructions to fix compilation errors and run variamos are missing in the wikidocs
Complete the page "configuring the environment" inside the wiki to add how to compile an run unitary test on variamos by using gradle. Add images if necessary
Documenting current VariaMos architecture modules, main responsabilities and dependencies
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[X ] Improvement request
[ ] Support request => Please do not submit support request here
The menus should not appear, they can't be hidden using the operations metamodel
To clean the window form useless menus
Variamos version: 20
For Tooling issues:
Platform: Mac
Others: none
switching branch is harder than it should as some eclipse files are committed.
nherbaut@hades:~/workspace/VARIAMOS$ git checkout development
error: Your local changes to the following files would be overwritten by checkout:
.settings/org.eclipse.buildship.core.prefs
com.variamos.reasoning/.classpath
could you please remove those files from the repo?
Create diagrams from javasources by using modelio
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
When selecting REFAS model and changing to the Context and Environment View, the menues of the application stop working. This does not happen if the REFAS metamodel are loaded manually from the metamodels shared on the folder.
The menues should continue working.
Variamos version: 1.0.1.20 development branch
For Tooling issues:
Platform:
Windows
Others:
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x ] Improvement request
[ ] Support request => Please do not submit support request here
The ModelExpression requires SWI component to show exception messages
Change the method createExpression to throw a Functional or techcnical exception if any exception is detected instead of write the exception directly in console. Modify the user GUI classes to show exceptions messages in the ConsoleTextArea
Apply the same fix in the following classes:
OverTwoElementsExpressionSet
ModelExpr2HLCL
SolverOpersTask
SolverTasks
ModelExpr
Variamos version: 1.2.0.1
For Tooling issues:
Platform:
Others:
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ x] Improvement request
[ ] Support request => Please do not submit support request here
Unitary test missing
Add unitary test for the class: Hlcl2SWIProlog.
Change deprecated invocations to the JUnit library from the TestHLCL class
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here
The monitor module saves and reads json files which are saved by using the class ConfigurationIO.
Inside the ConfigurationIO class there are methods to handle json files (load, save, read) that could be generalized to be used for other modules (different from the Configuration tasks).
Improve how these methods were developped to obtain a generic design.
The idea is that the IO module does not have any relation with any module that contains business logic. Only the dependency with the common module is allowed.
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[X ] Improvement request
[ ] Support request => Please do not submit support request here
When the user selects the options Page, Width, Actual, the canvas is resized, but it's not possible to access to the rest of the model
Not to offer these options because they don't allow the edition/reading of the model
Variamos version: 1.0.1.20b
For Tooling issues:
Platform: Mac
Others: none
[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
When you save a png file, the application ask if you want a transparent background. No matter your selection, the file is created with a background.
If you select transparent background, the file should be created without a background.
Switch to the syntax metamodel, press the save button, change the extension to png and accept the transparent background. It should also occur in others perspectives.
It is an existing features useful to obtain the models for other destinations
Variamos version:
Most recent development branch. Works of in the master branch.
For Tooling issues:
Platform:
Others:
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ x] Improvement request
[ ] Support request => Please do not submit support request here
Source code is placed in different packages inside the GUI project. It is required to migrate the current source code to place resources such as images and properties files in a predefined place in order to avoid problems with absolute paths when loading images, text messages, resources
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x] Improvement request
[ ] Support request => Please do not submit support request here
Many current source files are disorganized and do not satify the file structure defined in the developer guides
Rearrange the source code to satisfy the structure defined in the developer guides
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x ] Improvement request
[ ] Support request => Please do not submit support request here
create an enum for handling inside the perspectives source code all. In this way, the enumt will be used for each developper to know what perspective is working on instead of use numbers such as 1,2,3 etc.
Complete the section what is variamos for? inside the wiki.
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x ] Improvement request
[ ] Support request => Please do not submit support request here
Review how to handle functional exceptions in the method doInBackground in the class SolverOperTask to avoid dependency with the GUI
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x ] Improvement request
[ ] Support request => Please do not submit support request here
The model/configuration perspective shows the following menus "File, Layout, Simulation scenarios", basic simulation(static), configuration(static), basic simulation ( static), Dash board.
In order to make easy for the final user to interact with the functionalities which area available and well tested ( non experimental ones) in Variamos, we need to hide or reorder the following menu options:
-Layout from the configuration/simulation perspective
-Simulation scenarios
-Configuration ( static) - move options for save partial configuration and export all configurations to the dashboard option.
-Basic simulation ( that uses dynamic operations)
Also move options to save current configuration and save all configurations to the Dashboard menu
Variamos version: 1.0.1.20
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[X] Improvement request
[ ] Support request => Please do not submit support request here
To support multiple views, elements are hidden if they do not belong to the active view. The implementation works but it is not as efficient as possible.
Explore and replace the functionality explained to use GraphLayoutCache. From an early review, this class can replace the need for hidding and showing elements.
Improve efficiency specially when using huge models.
Variamos version:
1.1.0.1
For Tooling issues:
Platform:
Others:
Complete unitary test into com.variamos.common.core.utilities inside the test source code package
Elaborate the javadoc documentation
Complete the Javadoc documentation in the solver module.
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
The behavior is as expected when semantics and syntax metamodels are loaded for the first time because it produces a desired change on the palettes available on the Modeling perspective, but when some different metamodels (syntax and semantics) are loaded for the second time, the Modeling perspective is not updated as expected. The palettes related to the first loaded metamodels remain on the user interface.
Whenever the syntax and semantic metamodels are loaded, the Modeling perspective must be updated in order to be comply with the metamodels specification.
Click on Window file menu -> Show Advanced Perspectives
Click on Semantic and operation Meta-models Perspective
Click on Open icon on tool bar
Choose and load the SEMANTIC metamodel of any paradigm (features, goals, constraint, etc)
Click on Syntax Meta-models Perspective
Click on Open icon on tool bar
Choose and load the SYNTAX metamodel of the same paradigm choosed in step 4.
Click on Modeling Perspective and check the properly visualization
Repeat the steps 1 to 8 for other differente paradigm. In the step 8 you will see the problem.
Variamos version:
For Tooling issues:
Platform:
Others:
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ x] Improvement request
[ ] Support request => Please do not submit support request here
The option inside the menu "dashboard" for exporting all configuration has an error when the file already exists, and given that it does not use a swiworker for saving the file, the main threat is bloqued,
Modify the current action performed to excecute the dynamic operation defined for exporting solutions.
Variamos version: 1.0.1.20
For Tooling issues:
Platform:
Others:
Design how to support utilities for importiing and exporting variability models to VariaMos and from VariaMos. For example, VariaMos should be able of reading models expressed in formats such as SPLOT or FAMA. To the future how to read prolog files should be supported too.
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Improvement request
[ ] Support request => Please do not submit support request here
Variamos version:
For Tooling issues:
Platform:
Others:
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.