Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Contents |
Prev | Next |
~M~
Terms starting with M
Name |
Detail |
See also |
---|---|---|
Maintenance |
The support of a software system after it is deployed. |
|
Manifest |
A relationship that indicates that the artifact source embodies the target model element. Stereotypes can be added to Enterprise Architect to classify the type of manifestation of the model element. |
|
Message |
Messages indicate a flow of information, or transition of control, between elements. Messages are used by Communication diagrams, Sequence diagrams, Interaction Overview diagrams and Timing diagrams. |
|
Message Endpoint |
An element that defines an endpoint of a Lifeline, such as a State or Value Lifeline in a Timing diagram. |
|
Message Label |
Used for messages sent between Lifelines to make the diagram appear less cluttered. Labels with the same name indicate that a message can be interrupted. |
|
Metaclass |
A Class whose instances are Classes. Metaclasses are typically used to construct metamodels. |
|
Metafile |
A vector-based image format native to Windows. Supports high detail and excellent scaling. Typically used for saving diagram images for placement in documents. Comes in Placeable (an older format) and Enhanced (current standard format). |
|
Meta-Metamodel |
A model that defines the language for expressing a metamodel. The relationship between a meta-metamodel and a metamodel is analogous to the relationship between a metamodel and a model. |
|
Metamodel |
A model that defines the language for expressing a model. |
|
Meta-Object |
A generic term for all meta-entities in a meta-modeling language. For example, meta-types, meta-classes, meta-attributes, and meta-associations. |
|
Meta-Object Facility (MOF) |
An Object Management Group (OMG) standard. MOF originated in the UML, when the OMG required a Meta-Modeling architecture to define the UML. MOF is designed as a four-layered architecture. |
|
Method |
The implementation of an operation. It specifies the algorithm or procedure associated with an operation. |
|
Model (MOF) |
An abstraction of a physical system with a certain purpose.Usage note: In the context of the MOF specification, which describes a meta-metamodel, the meta-metamodel is for brevity frequently referred to simply as the model. |
Physical System |
Model Aspect |
A dimension of modeling that emphasizes particular qualities of the metamodel. For example, the structural model aspect emphasizes the structural qualities of the metamodel. |
|
Model Elaboration |
The process of generating a repository type from a published model. Includes the generation of interfaces and implementations which enables repositories to be instantiated and populated based on, and in compliance with, the model elaborated. |
|
Model Element (MOF) |
An element that is an abstraction drawn from the system being modeled. In the MOF specification model elements are considered to be meta-objects. |
View Element |
Model Library |
A stereotyped Package containing model elements that are intended to be reused by other Packages. A model library differs from a profile in that a model library does not extend the metamodel using stereotypes and tagged definitions. A model library is analogous to a Class library in some programming languages. |
|
Modeling Time |
Refers to something that occurs during the modeling phase of the software development process. It includes analysis time and design time.Usage note: When discussing object systems, it is often important to distinguish between modeling-time and run-time concerns. |
Compile Time Design Time Analysis Time Run Time |
Module |
A software unit of storage and manipulation. Modules include source code modules, binary code modules and executable code modules. |
Component |
MOF |
Meta-Object Facility, an Object Management Group (OMG) standard. MOF originated in the UML, when the OMG required a Meta-Modeling architecture to define the UML. MOF is designed as a four-layered architecture. |
|
Multiple Classification |
A semantic variation of Generalization in which an object can belong directly to more than one classifier. |
Dynamic Classification Static Classification |
Multiple Inheritance |
A semantic variation of Generalization in which a type can have more than one supertype. |
Single Inheritance |
Multiplicity |
A specification of the range of enableable cardinalities that a set can assume. Multiplicity specifications can be given for roles within Associations, Parts within Composites, repetitions and other purposes. Essentially a multiplicity is a (possibly infinite) subset of the non-negative integers. |
Cardinality |
Multi-Valued (MOF) |
A model element with multiplicity defined whose Multiplicity Type:: upper attribute is set to a number greater than one. The term multi-valued does not pertain to the number of values held by, for example, an attribute or parameter, at any point in time. |
Single-Valued |