Interface | Description |
---|---|
Abstraction |
Abstraction v0.0.9054
An Abstraction is a relationship that relates two Elements or sets of Elements that represent the same concept at different levels of abstraction or from different viewpoints.
|
AbstractProject |
AbstractProject v3.6.00
|
AbstractResource |
AbstractResource v2.1.00
null
|
Constraint |
Constraint v0.0.9054
Constraints can express restrictions and relationships that cannot be expressed using UML notation.
|
Dependency |
Dependency v0.0.9054
|
Document |
Document v2.1.00
|
Element |
Element v0.0.9054
|
ExternElement |
ExternElement vnull
null
|
ExternProcessor |
ExternProcessor v0.0.9054
Represents an external processor.
|
IResourceHandle | |
MetaclassReference |
MetaclassReference v2.1.00
|
MethodologicalLink |
MethodologicalLink v2.1.01
A methodological link allows drawing semantic relationships between elements originating from the same or different metamodels.
|
ModelElement |
ModelElement v3.6.00
|
ModelTree |
ModelTree v0.0.9054
The ElementOwnerShip association provides a hierarchy of ModelElements that can be managed by the model explorer or by the teamwork facility.
|
Note |
Note v0.0.9054
|
NoteType |
NoteType v0.0.9054
|
Profile |
Profile v3.6.00
|
Resource |
Resource v2.1.00
null
|
ResourceType |
ResourceType v2.1.00
|
Stereotype |
Stereotype v2.1.00
|
Substitution |
Substitution v0.0.9054
|
TaggedValue |
TaggedValue v0.0.9054
In Modelio, TaggedValues can have parameters, and must comply with TagTypes that define which kind of TaggedValues may exist.
|
TagParameter |
TagParameter v0.0.9054
TaggedValues are a powerful mechanism in Modelio.
|
TagType |
TagType v0.0.9054
|
UmlModelElement |
UmlModelElement v0.0.9054
A ModelElement describes every element that can exist in a model.
|
Usage |
Usage v0.0.9054
A Usage is a relationship in which one element requires another element (or set of elements) for its full implementation or operation.
|