WinVMJ on FeatureIDE 101

We strongly recommend visiting the FeatureIDE GitHub Page and the WinVMJ-AISCO GitLab Repository to learn more about the respective framework's usage.

WinVMJ FeatureIDE Structure

root
├── [src]
│   ├── pl.corefeature1.core/
│   ├── pl.corefeature1.delta1/
│   ├── ...
│   └── pl.product.productx/
├── src-gen
│   ├── pl.product.product1/
│   ├── pl.product.product2/
│   ├── ...
│   └── pl.product.productn/
├── [config]
│   ├── config1.xml
│   ├── config2.xml
│   ├── ...
│   └── confign.xml
├── external
│   ├── lib1.jar
│   ├── lib2.jar
│   ├── ...
│   └── libn.jar
├── modules
│   ├── pl.corefeature1.core/
│   ├── pl.corefeature1.delta1/
│   ├── pl.corefeature1.delta2/
│   ├── ...
│   └── pl.corefeaturem.deltan/
├── db.properties
├── feature_to_module.json
└── model.uvl
        

Each component can be explained as:

• root: Project root.
• [src]: Generated product directory consisting of selected modules (including from other SPLs) and a generated product module. Its name can be defined by the user when creating the project. Its content changes depending on the selected configuration.
• src-gen: Compiled generated product directory. All compiled products will be preserved in this directory.
• [config]: Directory where product configurations are defined. Its name can be defined by the user when creating the project and it will determine the product's name.
• external: Directory where additional libraries are stored. Make sure the library's name is the same as its package name when declared in module-info.
• modules: Directory where all implementation modules are stored.
• db.properties: A file that defines the database credentials. This is an example of its content:

  db.username=postgres
  db.password=postgres
                  

  As seen above, it consists of two properties: db.username that defines your Postgresql username and db.password that defines your Postgresql password. Please adjust it to match your current credentials.

• feature_to_module.json: A file that defines the Feature-Module mapping. This is an example of its content:

  {
      "Program": ["aisco.program.core"],
      "Activity": ["aisco.program.activity"],
      "Operational": ["aisco.program.operational"],
      "Income | Expense": ["aisco.chartofaccount.core","aisco.financialreport.core"]
  }
                  

  As seen above, it consists of key-value pairs. The key is the feature condition required to apply a set of modules defined as value. The key can be a single feature or a mathematical logic with a set of features as its atoms.

• model.uvl: A file that defines the feature model.