Package de.armax.ax.devtools.uml

This package contains our UML abstraction layer specification.

See:
Description

Interface Summary

AXabstraction	Metamodel for an UML abstraction.
AXassociation	Metamodel for am UML association.
AXassociationEnd	Metamodel for am UML association end.
AXattribute	Metamodel for UML attribute
AXclass	Metamodel for UML class and UML interface
AXclassifier	Metamodel for an UML classifier
AXdependency	Metamodel for an UML dependency.
AXgeneralization	Metamodel for an UML generalization.
AXmodel	This is the root of any model.
AXmodelCheckerListener	Listener for model checker events.
AXmodelElement	Metamodel for UML model elements.
AXoperation	Metamodel for an UMP operation.
AXpackage	Metamodel for an UML package.
AXparameter	Metamodel of an UML parameter.
AXstructuralFeature	Metamodel for UML structural feature

Class Summary

AXclassifierVoid	Convenience class representing a void type.
AXmodelBundle	This class represents a bundle consisting of several models that may reference each other using a specific stereotype.
AXmodelChecker	Abstract base class for model checkers.
AXmodelElementAbstract	Abstract base class of all model elements.
AXmodelFactory	Factory for AXmodel.
AXmultiplicity	Class representing the multiplicity of association ends.
AXpackageBundle	This class represents an implementation of AXpackage used by model bundles (AXmodelBundle).
AXvisibility	Class representing the visibility of a model element.

Exception Summary

AXmodelException

General purpose exception.

Package de.armax.ax.devtools.uml Description

This package contains our UML abstraction layer specification.

It is not a complete abstraction layer for UML. Only the elements we needed for our purpose are included. In particular, only class diagram elements are modeled in this abstraction layer.

There were principally two reasons to creare our own abstraction layer rather than using existing uml meta classes. The first reason is that we needed some more sophisticated logic in the meta classes than most existing implementations provide. As we use these classes for code generation with Velocity templates (see AXgen), it seemed to be far more comprehensive and comfortable to implement this logic in java classes rather than directly in the templates. The second reason is different versions of UML/XMI. Our own abstraction layer allows to leave our templates unchanged and provide different implementation of the abstraction layer instead.