Reverse engineer a XML schema and storing the results as UML 1.3 objects. The model produced is in fact a Platform Specific Model, which might need additional processing and tuning.

Conventions for the model produced:

• The model elements (classes, association names) that represent elements in the output XML are marked with <<element>> stereotype
• For representation purposes local types (UML classes) could be introduced for XSD groups, unions, local / inlined types. All of them are marked with <<local type>> stereotype
• The column types are converted to DataType instances named: <type name>[_<column size>[_<column precision>]]. Additionally as tagged values named TAG_VALUE_DATA_TYPE_SIZE and TAG_VALUE_DATA_TYPE_PRECISION these values are bound to the concrete data type.
• The TAG_VALUE_DATA_TYPE_PRECISION tagged value is optional. When not provided, the precision should be treated as 0
• Any comments found while reverse engineering the XSD are bound as 'documentation' tagged values. These tagged values are compatible with the Rose's approach to documentation. They are optional.