Feather: A Feature Model Transformation Language

March 16, 2019 Β· Entered Twilight Β· + Add venue

πŸŒ… TWILIGHT: Old Age
Predates the code-sharing era β€” a pioneer of its time

"Last commit was 6.0 years ago (β‰₯5 year threshold)"

Evidence collected by the PWNC Scanner

Repo contents: Case 2: A Static Environment, ConstraintSolver.java, DataTypes.java, EILReader.java, Feather.tokens, FeatherBaseListener.java, FeatherLexer.java, FeatherLexer.tokens, FeatherListener.java, FeatherParser.java, Feather_CodeGenerator.java, Feather_ErrorListener.java, Feather_ErrorStrategy.java, Feather_Lexer.java, Feather_Parser.java, FeatureModel.java, Interpreter.java, InterpreterEngine.java, LICENSE, README.txt, TVLBaseListener.java, TVLLexer.java, TVLListener.java, TVLParser.java, TVL_CodeGenerator.java, TVL_ErrorListener.java, TVL_ErrorStrategy.java, TVL_Lexer.java, TVL_Parser.java, TypeChecker.java, feather.jar, feather.java

Authors Ahmet Serkan Karataş arXiv ID 1903.06965 Category cs.SE: Software Engineering Citations 0 Repository https://github.com/askaratas/Feather ⭐ 1 Last Checked 2 months ago
Abstract
Feature modeling has been a very popular approach for variability management in software product lines. Building a feature model requires substantial domain expertise, however, even experts cannot foresee all future possibilities. Changing requirements can force a feature model to evolve in order to adapt to the new conditions. Feather is a language to describe model transformations that will evolve a feature model. This article presents the structure and foundations of Feather. First, the language elements, which consist of declarations to characterize the model to evolve and commands to manipulate its structure, are introduced. Then, semantics grounding in feature model properties are given for the commands in order to provide precise command definitions. Next, an interpreter that can realize the transformations described by the commands in a Feather script is presented. Finally, effectiveness of the language is discussed using two realistic examples, where one of the examples includes a system from a dynamic environment and the other employs a system that has a large feature model containing 1,227 features.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering