Generating product variants
As feature selections are made, pure::variants checks their validity and, if necessary, automatically resolves dependency conflicts or highlights conflicts if they cannot be resolved automatically. Once a valid selection has been made, an evaluation of the Family models, containing component definitions, is performed.
This evaluation process produces an abstract (XML) description of the variant in terms of software components (components, modules, files etc.). This description is used to control a transformation process that in-turn generates the finished product variant (source code and other artefacts).
The precise workings of this transformation process can be easily customized and extended by end-users through a variety of customization and extension points if the standard capabilities need to be modified.
Information from other development tools may also be incorporated into the transformation process.
Model-Driven Software Development Training
Learn the fundamentals of model-driven software development on one of our hands-on training workshops.