I implemented Feature Modeling support and a generator to produce a feature selection table based on the features specified. Here is an example.

 

 

The language includes some of the “normalization rules”, feature cardinality and the capability to specify binding times as illustrated in the metamodel below. By “normalization” I mean that you can’t specify for example alternative feature selection where some features are optional and some are mandatory: they all need to be mandatory then and now the metamodel takes care of this.

To test and extend the Feature Modeling, login to MetaEdit+, create a new project and import the http://www.metacase.com/forums/uploads/8/FeatureModeling.mxt - FeatureModeling.MXT file (MetaEdit+ Type definition in XML). The MXT includes the language concepts, rules, notations, some model checking and the generator. On model checking side a special rule is added to the language showing if the feature model is not anymore a tree. Shows a special sign related to the feature that belongs to more than one feature. In this way a possibly illegal model can be drawn but the part of model that does not anymore follow tree structure is clearly shown.