Deprecated refer to https://github.com/Universal-Variability-Language/uvl-parser2.0
This is a small default library used to parse and print the Universal Variability Language (UVL). It is written in Clojure, but can also be used from any JVM language, as it exposes a Java API.
Under the hood it uses instaparse as the parsing library.
The grammar in EBNF form is located in resources/uvl.bnf
On a high level, each feature model in UVL consists of four optional separated elements:
- A namespace which can be used for references in other models
- A list of imports that can be used to reference external feature models The models are referenced by their file name and can be given an alias using a Java import like syntax. External models in subdirectories can be referenced like this: subdir.filename as fn
- The tree hierarchy consisting of: features, group types, and attributes whose relations are specified using nesting (indendation) The children of a feature are either groups (or, alternative, mandatory, optional, cardinality) or feature attributes. Groups may have an arbitrary number of features as child nodes. Attributes consist of a key-value pair whose key is always a string and its value may be a boolean, number, string, a list attributes, a vector, or a constraint.
- Cross-tree constraints Cross-tree constraints may be arbitrary propositional formulas with the following symbols: => (implies), <=> (iff), & (and), | (or), ! (not), or brackets.
For our tool, we specified the language as context-free grammar (CFG) in EBNF notation as seen below.
FeatureModel = Ns? Imports? Features? Constraints?
Ns = <'namespace'> REF
Imports = <'imports'> (<indent> Import+ <dedent>)?
Import = REF (<'as'> ID)? (<'refer'> Refer)?
Refer = (<'['> (ID <','?>)* <']'>) | 'all'
Features = <'features'> Children?
<Children> = <indent> FeatureSpec+ <dedent>
FeatureSpec = REF Attributes? Groups?
Attributes = (<'{'> <'}'>) |
(<'{'> Attribute (<','> Attribute)* <'}'>)
Attribute = Key Value?
Key = ID
Value = Boolean|Number|String|Attributes|Vector|Constraint
Boolean = 'true' | 'false'
Number = #'[+-]?(0|[1-9]\d*)(\.\d*)?([eE][+-]?\d+)?'
String = #'"(?:[^"\\\n]|\\.)*"'
Vector = <'['> (Value <','?>)* <']'>
Groups = <indent> Group* <dedent>
Group = ('or' | 'alternative' | 'mandatory' |
'optional' | Cardinality)
Children?
Cardinality = <'['> (int <'..'>)? (int|'*') <']'>
Constraints = <'constraints'> (<indent> Constraint+ <dedent>)?
<Constraint> = disj-impl | Equiv
Equiv = Constraint <'<=>'> disj-impl
<disj-impl> = disj | Impl
Impl = disj-impl <'=>'> disj
<disj> = conj | Or
Or = disj <'|'> conj
<conj> = term-not | And
And = conj <'&'> term-not
<term-not> = term | Not
Not = <'!'> term
<term> = REF | <'('> Constraint <')'>
indent = '_INDENT_'
dedent = '_DEDENT_'
<strictID> = #'(?!alternative|or|features|constraints|
true|false|as|refer)[a-zA-Z][a-zA-Z_0-9]*'
<ID> = #'(?!true|false)[a-zA-Z][a-zA-Z_0-9]*'
REF = (ID <'.'>)* strictID
<int> = #'0|[1-9]\d*'
The following snippet shows a simplified server architecture in UVL. We provide more examples (e.g., to show the composition mechanism) in examples/language.
namespace Server
features
Server {abstract}
mandatory
FileSystem
or // with cardinality: [1..*]
NTFS
APFS
EXT4
OperatingSystem {abstract}
alternative
Windows
macOS
Debian
optional
Logging {
default,
log_level "warn" // Feature Attribute
}
constraints
Windows => NTFS
macOS => APFS
In this snippet, we can recognize the following elements:
- The feature
Server
is abstract (i.e., corresponds to no implementation artifact. - Each
Server
requires aFileSystem
and anOperatingSystem
denoted by the mandatory group - The
Server
may haveLogging
denoted by the optional group - A
FileSystem
requires at least one type ofNTFS
,APFS
, andExt4
denoted by the or group - An
OperatingSystem
has exactly one type ofWindows
,macOS
, andDebian
denoted by the alternative group Logging
has the feature attributelog_level
attached which is set to "warn"Windows
requiresNTFS
denoted by the first cross-tree constraintmacOS
requiresAPFS
To create a Java-consumable jar, the Leiningen build tool is used.
lein
will compile first the Clojure source, and then the Java source.
Both compiled Java and Clojure source will be packaged into a jar.
This is achieved through the uberjar task:
$ lein uberjar
Compiling de.neominik.uvl.ast
Compiling de.neominik.uvl.parser
Compiling de.neominik.uvl.transform
Compiling 1 source files to uvl-clj/target/classes
Created uvl-clj/target/uvl-parser-0.1.0-SNAPSHOT.jar
Created uvl-clj/target/uvl-parser-0.1.0-SNAPSHOT-standalone.jar
The standalone.jar
includes all dependencies, while the other jar ships only the code of the uvl-parser itself, without Clojure or instaparse.
The class de.neominik.uvl.UVLParser
exposes the static method parse(String)
which will return an instance of a de.neominik.uvl.UVLModel
on success or a de.neominik.uvl.ParseError
when the input didn't comply to the grammar.
Printing is implemented in the toString()
methods of the different model elements in the UVLModel
.
The following snippet shows a minimal example to read and write UVL models using the jar. More usage examples that also show how to use the acquired UVLModel object can be found in examples/java
UVLModel model;
// Read
String content = new String(Files.readAllBytes(Paths.get("file")), StandardCharsets.UTF_8);
Object result = UVLParser.parse(content);
if (result instanceof UVLModel) {
model = (UVLModel) result;
} else {
System.out.println("Faulty input");
model = null;
}
// Write
BufferedWriter writer = new BufferedWriter(new FileWriter(model.getNamespace() + ".uvl"));
writer.write(model.toString());
writer.close();
UVL models:
Other parsers:
- https://github.com/diverso-lab/uvl-diverso/ Under development, Antlr4 Parser Diverso Lab
Usage of UVL:
- https://github.com/FeatureIDE/FeatureIDE Feature modelling tool
- https://github.com/SECPS/TraVarT Tool for transforming variability models
- https://github.com/diverso-lab/core Under development, Tool for analysis of variability models
Copyright © 2020 Dominik Engelhardt
This software is released under the MIT License (see the file LICENSE for details). Integrating it into your tool by reusing any part of it is strongly encouraged!