As a MetaCASE tool, MetaEdit+ can support a wide variety of
different modeling languages covering
 | GOPRR:
The graphical variant of MetaEdit+’s GOPPRR metamodeling language. These
graphical metamodels can be exported as XML document importable back to
MetaEdit+ as language definitions. More detailed description about the usage of
the GOPRR modeling language can be found from a separate ‘The Graphical
Metamodeling Example’
manual. |
| Unified
Modeling Language (UML): An implementation of OMG’s Unified Modeling
Language 2.0. For more information about UML, see www.uml.org. |
| Digital
Watch: A complete example of full-fledged DSM environment for development of
digital wristwatch applications. For more information about the Watch example,
please see ‘The Watch Example’
manual. |
| S60
phone: The S60 phone example illustrates how smart phone applications can be
modeled and automatically generated. For more detailed description of the S60
language and example, please see ‘S60 Phone Example’
manual. |
| S60
phone C++: This example demonstrates the language for modeling of
applications for mobile phones, for generation of S60 native C++. This example
has been described in more detail in the book "Domain-Specific Modeling" by
Steven Kelly and Juha-Pekka Tolvanen (Wiley-IEEE Computer Society Press, 2008,
http://www.dsmbook.com) |
| Call
Processing Language (CPL): A language for describing and control Internet
telephony services. For more information about CPL, see xml.coverpages.org/cpl.html. |
| EAST-ADL:
A language to design the technical information needed for development of
automotive electronic systems. For more information about EAST ADL, see
www.east-adl.info. |
| Car
infotainment: A language for defining car infotainment systems. This example
demonstrates MetaEdit+’s ability to create dynamic interactive models
which automatically update based on changes to the existing
design. |
| Home
automation: The Home automation example demonstrates the modeling of voice
menus for a Home Automation system. More information about this example can be
found from the book "Domain-Specific Modeling" by Steven Kelly and Juha-Pekka
Tolvanen (Wiley-IEEE Computer Society Press, 2008, http://www.dsmbook.com) |
| Insurance:
An example of modeling language designed for defining variants of various
insurance products like car insurance, health insurance, etc. More detailed
description of this language can be found from the book "Domain-Specific
Modeling" by Steven Kelly and Juha-Pekka Tolvanen (Wiley-IEEE Computer Society
Press, 2008, http://www.dsmbook.com) |
| Business
Process Modeling Notation (BPMN): An implementation of BPMN v1.0, as
presented at http://www.bpmn.org. |
| Structured
Analysis and Design: An implementation of the traditional SA/SD as presented
in Edward Yourdon’s “Modern Structured Analysis” (Yourdon
Press, Prentice-Hall, Englewood Cliffs,
1989) |
| Value
chains and value systems: An implementations of value chains as presented in
Michael Porter’s “Competitive Advantage” (Free Press, New
York,
1985) |
| Activity
Analysis: An implementation of activity analysis models as presented in
Goran Goldkuhl’s “Contextual Activity Modeling of Information
Systems”, in: Proceedings of the Third International Working Conference on
Dynamic Modeling of Information Systems, Noordwijkerhout, June 9-10,
1992. |
| Business
Systems Planning: An implementation of IBM’s BSP
language. |
MetaEdit+ can offer such flexible
modeling language support because it is based on metamodels. A
metamodel
is a model of a modeling language. By specifying
a metamodel of a language into MetaEdit+, you promptly get a CASE tool support
for that specific language. You can view all existing (and new) metamodels by
using the language development tools. The metamodel-based architecture also
makes it very easy to modify existing languages in MetaEdit+.
One of the most powerful features regarding MetaEdit+
language support is that you can use them all, even at the same time.
Multi-language features allow you to link and reuse data across different
languages, maintaining a flow of information between them. These features are
explained in Section
6.3.
