Structuring UML profiles

Overview

For obvious reasons related to structure stability and backward compatibility, Objecteering is delivered with a preliminary fixed hierarchy of UML profiles. This hierarchy will be developed when new UML profiles are created, but the structure paradigm will be respected.

UML profile structure

Figure 4 presents the default UML profile hierarchy delivered with Objecteering.

Figure 4. The UML profiles delivered by default in a project

UML profiles

The ... UML profile	represents ...
internal	J rules developed internally, not accessible by the user.
external	generators and rules the user can access. The new user UML profiles must be created in "external".
Code	all code generators (C++, Java, SQL, etc.) which must be defined in this UML profile. Tagged values of general interest (NoCode, external) are defined at this level.
documentation	documentation generation.
Make	the generation of Makefiles (used with "Cxx" by the "GenC++" module).
Cxx	The C++ generator. The adaptation of the generator for new rules must be in this UML profile.
Platform	The characteristics of the platforms on which Objecteering is available. The production String generation (Make) especially uses this UML profile. "PC", "UNIX", etc. UML profiles are found there.