- Area
|
- A repository is composed of areas, each corresponding to a project. Each
area has its own set of files in a subdirectory of the repository’s
‘areas’ directory. The files of one area cannot be manipulated
separately: the repository must always be treated as a whole on the file
level.
|
- Binding
|
- An assembly of a relationship, roles, and objects (and possibly their
ports). An instance binding in a graph instance holds instances; a type binding
in a graph type holds types (and possibly static port instances), and can also
specify cardinality for roles.
|
- Browsers
|
- Tools for inspecting and editing model and metamodel elements by project:
Type Browser, Graph Browser, Metamodel Browser, Object Browser.
|
- Decomposition
|
- A subgraph link from an object to a graph representing the contents of that
object. Each object may have zero or one decomposition.
|
- Default project
|
- Project in which new graphs and types will be stored. New graph
representations and design elements are automatically stored into the same
project as their graphs.
|
- Design element
|
- Any conceptual design information in MetaEdit+: a graph, object,
relationship, role, port or property.
|
- Editor
|
- Modeling tool that allows you to specify the contents of a graph: Diagram
Editor, Matrix Editor, Table Editor.
|
- Explosion
|
- A subgraph link from an object, relationship or role in a certain graph to
another graph. A given object, relationship or role can have several explosions
in a given graph, and a different set of explosions in another graph.
|
- Graph
|
- Graph is a conceptual design element that contains objects, relationships
and roles. Graphs can be represented as diagrams, matrices or tables.
|
- Metamodel
|
- Specification of a modeling language: the types of that language.
|
- Model
|
- Corresponds to a graph, or loosely to a set of interlinked graphs.
|
- n-ary relationship
|
- A relationship that has more than two roles.
|
- Object
|
- A design element that can exist on its own in a graph; e.g. a class or an
entity.
|
- Patch file
|
- A binary file for updating MetaEdit+, metamodel types, or models. There are
three types of patches; .mep for the MetaEdit+ program, .met for types and .mec
for the combination of models with their types. Users can make patches with the
Type or Graph Manager; program patches can only be made by MetaCase.
|
- Port
|
- A design element that defines or constrains how roles can connect to an
object. A static port is defined in the object type’s symbol; a dynamic
port is an object from elsewhere in the model, revealed as a port through a
template in the symbol.
|
- Project
|
- A group of models and/or metamodels that are used together. Corresponds to
an area in the repository. In the demo repository each language has its own
project (written with initial capital letters) and users can create their own
projects for storing models.
|
- Property
|
- A design element that characterizes other design elements, e.g. the name of
a class. A property is often just a string, but may also contain one or several
design elements.
|
- Property sharing
|
- A reuse approach for sharing a property value between two or more design
elements, e.g. an attribute name ‘customerID’ can be used as both an
attribute of a class and an attribute of an entity.
|
- Relationship
|
- A design element that connects objects through roles; e.g. inheritance or
message between objects. Graphically, a relationship is at the midpoint or
meeting point of the role lines.
|
- Repository
|
- A database consisting of models and metamodels organized into
projects.
|
- Role
|
- A design element that connects an object to a relationship in a binding;
e.g. subclass or ‘owner’ role in an aggregation structure.
Graphically, a role is a line from a relationship to an object.
|
