Transformation to useable products

A model is a well designed image of the domain, from a particular perspective. Conceptual models introduce Persons and Addresses, logical models introduce Identifiers and Datatypes, physical models introduce Rows and Columns. But models only model these constructs. They should be serialized, transformed to useable code, in order to integrate it into the actual world of databases, webservices, print/web publication and so on.

Many modeling tools provide these features: java code may be created from a class diagram. But in that case the class diagram must be created exacly in line with the tools. The tool has a particular serialization technique. This is okay when this is the only application of the model: it was designed for that purpose. However, models may be "emanicipated" from these fixed tool profiles.

Imvertor takes the information recorded in the model, and applies any type of transfomation rules to create any type of product. Different documentation formats, different types of XML schema, and so on, all based on the same model.

Also, as the technical Imvertor format of the model is very open (it is actually an XML file with an associated XML schema), and as all types of models all use the same XML format, it is very well feasible to focus on that format and develop a range of products. There is a small learning curve.