Paket: profile

As I've said in the metamodel info, I won't need my own metamodels so much. I will work with an UML2 sample model. But it may be useful to have a little "domain specific" annotation. So it may be useful to have an UML profile. At least I want to show how to model a profile. Again this one, UMLEJB, is really simple. I only want to demonstrate how to work with a profile in transformation. This UMLEJB-profile is modeled with TOPCASED UML model using a profile template.

Hyperlinks
-

Owner
package   Project-Organization

Relationships
In package  profile going 
from Source Relation

From package  profile coming 
Relation to target
  relation     package   model