- abstracting mapping
A mapping that intentionally omits information contained in a more concrete model that's considered irrelevant detail in the more abstract model.
- abstraction
A modeling technique that involves ignoring information that is not of interest in a particular context. Abstraction involves choosing how to think about a problem and its solution, which also requires creativity and analysis.
- abstraction hierarchy
A graph within which the nodes are metamodels that factor out all commonalities of the subject matters from which they abstract.
- abstract syntax
The structure of a language separate from its concrete notational symbols.
- agile MDA
An approach in which models are linked together and then mapped to a single combined model that is then translated into code according to a single system architecture.
- bridge
At construction time, the combination of mapping functions, marks, and marking models that serves to link two models together.
- classification
A modeling technique that involves grouping important information based on common properties, even though the things under study are, of course, different from one another.
- composed realization
A realization of a platform that's comprised of one or more other realizations.
- constraint
A specification of a condition that must hold true in order for a model to be "well-formed."
- design-time interoperability
The type of interoperability that is achieved when gluing the various layers of abstraction together and combining models is deferred to the last minute during design.
- domain chart
A diagram that shows problem domains and the bridges among those domains.
- entity bean
An object that can live for the lifetime of the software system and whose state is stored in and loaded from an underlying database.
- executable model
A model that is complete in that it has everything required to produce the desired functionality of a single problem domain.
- Executable UML
A UML profile that defines an execution semantics for a carefully selected streamlined subset of the UML.
- generalization
A relationship between a general class (the superclass or parent) and a more specific version of that class (the subclass or child).
- horizontal mapping
A mapping that results in a target model at the same level of subject-matter abstraction as the level at which the source model resides.
- invariant
A condition that must hold true for all instances of a particular model element (such as all objects that belong to a given class).
- join point
A correspondence between a problem domain that is created and maintained separately from the model of that domain.
- long-hop mapping
A mapping that results in a significant change in abstraction level between the source model and the target model.
- M0 layer
The layer in the four-level metamodel hierarchy that contains the data of the application (for example, the instances populating an object-oriented system at runtime, or rows in relational database tables).
- M1 layer
The layer in the four-level metamodel hierarchy that contains the metadata of the application (for example, the classes of an object-oriented system, or the table definitions of a relational database).
- M2 layer
The layer in the four-level metamodel hierarchy that contains the metametadata that describes the properties that metadata may exhibit (for example, UML elements such as Class, Attribute, and Operation).
- M3 layer
The layer in the four-level metamodel hierarchy that contains metametametadata that describes the properties that metametadata can exhibit.
- mapping
The application or execution of a mapping function in order to transform one model to another.
- mapping chain
Two or more mappings linked together, where the outputs of one mapping serve as the inputs for another mapping.
- mapping function
A collection of mapping rules that defines how a particular mapping works.
- mapping rule
A rule that describes one aspect of how a mapping function works.
- mark
A lightweight, nonintrusive extension to a model that captures information required for model transformation without polluting that model.
- marking model
A model that defines the structure of, and types for, a set of marks, as well as default values and rules that construct default values when a value for a mark is absent.
- MDA
- See [model-driven architecture (MDA)]
- MDA process
A specific process that one applies on an MDA project.
- merge conflict
A collision between two or more changes to a common element, usually requiring human intervention to resolve.
- merging mapping
A mapping that combines more than one source model into a single target model.
- metadata
Data about data.
- metamodel
A model that defines the structure, semantics, and constraints for a family of models.
- Meta-Object Facility (MOF)
A language that defines a set of modeling constructs that a modeler can use to define and manipulate a set of interoperable metamodels.
- migrating mapping
A mapping that results in a target model expressed in a different form from the source model.
- model
A simplification of something so we can view, manipulate, and reason about it, and so help understand the complexity inherent in the subject under study.
- model compiler
A tool that takes a set of Executable UML models and weaves them together according to a consistent set of rules.
- model-driven architecture (MDA)
A set of technologies and techniques that enable model-driven development.
- model elaboration
The idea that a target model can be modified after it has been generated.
- MOF
- See [Meta-Object Facility (MOF)]
- Object Constraint Language (OCL)
A formal language that modelers can use to express conditions that must hold true for the system being modeled.
- OCL
- See [Object Constraint Language (OCL)]
- PIM
- See [platform-independent model (PIM)]
- platform
The specification of an execution environment for a set of models.
- platform-independent model (PIM)
A model of a subject matter whose metamodel represents abstractions from one or more platform models.
- platform-specific model (PSM)
A model that incorporates details about platforms.
- postcondition
A condition that must hold true at the moment that execution of an operation has just ended.
- precondition
A condition that must hold true at the moment that execution of a particular operation is about to begin.
- primitive realization
A realization of a platform that stands on its own.
- problem domain
A subject matter that can be understood independently of other subject matters.
- profile
A UML mechanism for adapting an existing metamodel with constructs that are specific to a particular domain, platform, or method.
- PSM
- See [platform-specific model (PSM)]
- refining mapping
A mapping that allows the modeler to express detail in the target model that doesn't apply in the more abstract source model.
- representing mapping
A mapping that allows the representation of a model to be edited and the changes mapped back to the original model.
- session bean
An object with state that is transaction-aware and lives for the life of a client session.
- short-hop mapping
A mapping that results in a small change in abstraction level between the source model and the target model.
- stateful session bean
An object that lives for the life of a client session.
- stereotype
Something that extends the basic vocabulary of the UML.
- tagged value
Something that extends the properties of an element of a UML model, but not instances of that element.
- type
A group of model elements with common properties.
- vertical mapping
A mapping that results in a target model at a different level of subject-matter abstraction than the level at which the source model resides.
- well-formedness rule
A rule that specifies a condition that a model must satisfy in order to be "well-formed."
- XMI
- See [XML Model Interchange (XMI)]
- XML Model Interchange (XMI)
A protocol that defines rules for deriving an XML Document Type Definition (DTD) from a MOF-compliant modeling language as well as rules for rendering a compliant model into a compliant XML document.
|
