Glossary

· MDA: Model Driven Architecture. This is a model-driven approach, including different definition and transformation stages, which result in a final deliverable.

· MDA component: Autonomous set of services and extensions, used to extend Objecteering UML Modeler to meet the needs of the domain concerned by the MDA component. MDA components can contain UML extensions, documentation, code or diagram templates, model patterns, user documentation, and so on.

· MDA Modeler: Name of the tool used to build UML extensions, to develop patterns and templates and to model, test and package MDA components.

· MDA Runtime: Name of the tool used in Objecteering UML Modeler to apply patterns, run templates and import RTF files.

· Pattern: Recurrent design elements, providing solutions to repetitive design problems.

· Profile: Structuring unit defined by UML 2.0. Profiles are used to extend UML.

· Profile implementation: Implementation of a profile to define J or Java code and actions on metamodel elements, and to define templates.

· Reference metamodel: Metamodel on which MDA components are based during their development.

· Template: Generic structure of a document, a diagram or code. A template defines the organization of the document, diagram or code's tree structure, by specifying for each node the parts of the model which are used.

· UML extension: A UML extension is used to define new concepts which are not supported by UML. These concepts are structured into profiles, which group new stereotypes and new services depending on the domain in question.