ClaferMooVisualizer

v0.4.4

Visualizes a set of non-dominated optimal variants (Pareto Front) and allows for exploration and trade-off analysis. Read more in the paper Visualization and Exploration of Optimal Variants in Product Line Engineering. The current version can be used outside the product line domain: various design optimization problems, architecture exploration, packaging problems are supported.

ClaferMooVisualizer is part of Clafer Tools. Read more in the paper Clafer Tools for Product Line Engineering.

Live demo

• Master branch (stable and released): ClaferMooVisualizer
• Develop branch (with newest features, but not guaranteed to be stable): ClaferMooVisualizer (development)

If the demo is down or you encounter a bug, please email Michał Antkiewicz.

Background

See clafer.org.

Functions

1. Displays all the non-dominated optimal product configurations as a Bubble Front Graph (up to 4 dimensions), a Feature and Quality Matrix, a Spider Chart, and as Parallel Coordinates Chart.
2. Allows to compare and analyze product configurations.
3. Allows for filtering by feature and by quality range.
4. Supports multiple solver backends.

Nature

ClaferMooVisualizer is a web-based application. Its server side (implemented with Node.js) processes requests, runs the chosen back-end, and passes back its output. The client-side is implemented using JavaScript/HTML and handles the visualization and exploration functionality.

Contributors

• Alexandr Murashkin. Original developer.
• Eldar Khalilov. Developer. Upgrade to 0.4.2 (replace XML with JSON, test suites).
• Michał Antkiewicz. Research Engineer. Requirements, development, architecture, testing, technology transfer.
• Neil Vincent Redman. co-op student Jan-Apr 2013. Many improvements.

Installation and running

Dependencies for running

• Java Platform (JDK) v8+
• Clafer v0.4.4
  • can be from the binary distribution
• Node.js Framework, v4.2.3 LTS
• Redis Server, v2:2.*
  • On Ubuntu, execute sudo add-apt-repository ppa:chris-lea/redis-server && apt-get install redis-server
• Backends' dependencies must be satisfied. See the backend installation steps below.

Installation

Core

1. Download (git clone) ClaferMooVisualizer to some directory <target directory>
2. Go to <target directory>/ClaferMooVisualizer and execute

git submodule init
git submodule update

This will install the platform.

When working with a branch other then master, you need to additionally checkout that branch (e.g., develop):

git submodule foreach git checkout develop

3. Go to <target directory>/ClaferMooVisualizer/Server and execute

npm install

This will download all the required Node.js modules.

4. Install the necessary backends into some location <bin> found on PATH. The default configuration in <target directory>/ClaferIDE/Server/Backends/backends.json assumes /home/clafertools040/bin.

The fastest way is to unzip a binary distribution into the folder <bin>.

See Installing Backends for detailed steps.

Settings

1. Make sure the port 8092 is free, or change the value of the key port in Server/config.json: "port" = "8092" to any free one.

2. Make sure clafer, node, and java are in PATH environment variables, so they can be executed without any path prefixes.

3. Running the following commands should produce the following results or later version:

clafer --version

Clafer v0.4.4

java -version

java version 1.8.0_102

node -v

v4.2.3 LTS

4. Make sure uploads folder is accessible for writing, since temporary files will be stored there.

5. If you use Shell scipts (.sh) for running, make sure the scripts have Execute permissions.

Running

• To run the server in a standard mode, execute

cd <target directory>/ClaferMooVisualizer/Server/

node ClaferMooVisualizer.js

• If you use Node Supervisor under Linux, you can execute

cd <target directory>/ClaferMooVisualizer/Server/commons
chmod +x start.sh
./start.sh

Then you can go to any browser and type http://localhost:[port]/ and open any Clafer file with objectives in it.

Trying an Example

• Choose Mobile Phone Example (2 objectives) example in the dropdown box in the upper-left corner of the tool window.
• Press Optimize button right in the front of the drop down list.
• The views will be populated with generated optimal instances.

Important: Branches must correspond

All related projects are following the simultaneous release model. The branch master contains releases, whereas the branch develop contains code under development. When building the tools, the branches should match. Releases from branches master are guaranteed to work well together. Development versions from branches develop should work well together but this might not always be the case.

Need help?

• Visit language's website.
• Report issues to issue tracker