Domains: UML

This metamodel fragment describes an abstract syntax for stereotypes in UML 1.4

This metamodel fragment has been extracted from information available in the following article: Article "Analysis of UML Stereotypes within the UML Metamodel" by Martin Gogolla, Brian Henderson-Sellers Page 85, Section 1, Fig. 1. Abstract Syntax for Stereotypes in UML 1.4 Lecture Notes in Computer Science 2460 Jean Marc J�z�quel, Heinrich Hussman, Stephen Cook UML 2002 - The Unified Modeling Language

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains: Developping new architectural design and analysis tools

ACME is a simple and generic software architecture description language (ADL)

This metamodel has been extracted from information available on the ACME site : http://www.cs.cmu.edu/~ACME/.

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains: Multi-Agent

ADELFE (Atelier de D�veloppement de Logiciels � Fonctionnalit� Emergente) is a methodology devoted to software engineering of adaptive multi-agent systems.

A Study of some Multi-Agent Meta-Models Authors: Carole Bernon, Massimo Cossentino, Marie-Pierre Gleizes, Paola Turci, Franco Zambonelli http://www.jamesodell.com/AOSE04-proceedings/AOSE04-08.pdf, p4

Authors: SIMON Eric(simon.eric3_NOSPAM gmail.com)

• Source file

Domains: Architecture Description, SoS (System of System), View, Viewpoint

A metamodel of AGATE (Atelier de Gestion de l Architecture des Systemes d Information). AGATE is a framework for Information systems architecture management. This framework was designed by the french DGA (D?l?gation G?n?rale pour l?Armement in english General delegation for the Armament). The currently version is 3.0.

http://www.ixarm.com/Referentiel-AGATE

Authors: Albin Jossic (jossic.albin gmail.com)

• Source file

Domains: Distributed programs, Objective Caml library

This metamodel describes Amble which is a distributed programming language based on Objective Caml. Amble enables to specify a distributed program in terms of processes that run concurrently. These processes are designed as states machines that are connected to each other by means of networks. Each network specifies a set of channels. The source process of a channel is allowed to write to its target process. An Amble program is composed of a single ".ml" file that includes the definition of the different process types that are involved in the program, as well as a set of ".topo" files (one for each considered network) that specifies the topology of the defined networks.

http://home.gna.org/amble/

Authors: David Touzet (david.touzet_NOSPAM univ-nantes.fr)

• Source file

Domains: Building tool

A metamodel describing Ant: Apache Ant is a Java-based build tool. It is similar to make, without make s wrinkles. It is configured with a build file that is an XML document. The build files are generally platform independent. It is extended using Java classes not scripts or shell-based commands. It can take care of archiving, compilation, execution, documentation, deployment, and much more.

http://ant.apache.org/

Authors: Julien Ruchaud, Pauline Brunel (pabrunel_NOSPAM numericable.fr)

• Source file

Domains: Apache Ant

This generic metamodel simply describes Ant scripts structure and content independently of the tasks which may be called in.

http://ant.apache.org/manual/index.html

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com)

• Source file

Domains: Simulation

This metamodel describes simulation models for AnyLogic, a tool which is a simulation engine that can run simulations in order to analyze systems and provides visual representation of the running simulation.

XJ Technologies: AnyLogic � multi-paradigm simulation software (June 2007). http://www.xjtek.com/anylogic

Authors: Jendrick Johannes (jendrick.johannes tu-dresden.de)

• Source file

Domains: Software Architecture Description

This metamodel fragment describes an Architectural Description

This metamodel has been extracted from information available in the following article: Article "Towards a UML Profile for Software Architecture Descriptions" by Mohamed Mancona Kand�, Alfred Strohmeier Page 519, Section 4.1, Fig. 4. Extended P1471 Conceptual Model of Architectural Description Lecture Notes in Computer Science 1939 Andy Evans, Stuart Kent, Bran Selic UML 2000 - The Unified Modeling Language

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains:

This is a metamodel for XASM (eXtensible Abstract State Machine) an Abstract State Machines (ASMs) based language

http://www.xasm.org http://www.eecs.umich.edu/gasm/

Authors: Davide Di Ruscio (diruscio_NOSPAM di.univaq.it)

• Source file

Domains: Microsoft DotNET

Abstract State Machine Language

Authors: Albin Jossic (albin.jossic gmail.com)[1] ;[1] ATLAS team (Nantes, France)

• Source file

Domains:

This metamodel describes ATOM. Atom is an XML-based document format for the syndication of web content such as weblogs and news headlines, and an HTTP-based protocol for editing weblogs based on the format.

http://www.atomenabled.org/developers/syndication/ http://en.wikipedia.org/wiki/Atom_%28standard%29

Authors: David Touzet (david.touzet_NOSPAM univ-nantes.fr)

• Source file

Domains:

This metamodel describes a finite automaton. An automaton is a finite state input/output device. An automaton that as an initial state, (initialState), a set of available states (stateSet), a set of transitions (transitionSet), an alphabet, an a set of final states (finalStateSet).

http://www.irisa.fr/triskell/publis/2005/Muller05c.pdf

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: programming language

This metamodel describes programs in AWK which is a Unix utility designed for processing text based data, either in files or data streams. The name AWK is derived from the surnames of its authors - Alfred V. Aho, Peter J. Weinberger, and Brian W. Kernighan.

The GNU Awk Webpage, http://www.gnu.org/software/gawk/gawk.html

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Bibliography

This is a partial Bibtex metamodel. It does not contain constraint on Bibtex fields. This metamodel is used in the Bibtex Management project to inject Bibtex files into Bibtex models.

http://www.ecst.csuchico.edu/~jacobsd/bib/formats/bibtex.html

Authors: Guillaume Hillairet (g.hillairet_NOSPAM gmail.com)

• Source file

Domains: bibliography, XML

This is a metamodel of BibTeXML which is an XML-based format for the BibTeX bibliographic tool system for use with LaTeX. A bibliography is modelized by a BibTeX File element. This element is composed of BibTeX Entries which are each associated with an id. All entries inherit, directly or indirectly, of the abstract BibTeX Entry element. The abstract classes Authored Entry, Dated Entry, Titled Entry and Book Titled Entry, as well as the Misc entry, directly inherit of BibTeX Entry. There are 13 possible entry types: PhD Thesis, Master Thesis, Article, Tech Report, Unpublished, Manual, In Proceedings, Proceedings, Booklet, In Collection, Book, In Book and Misc. Concrete BibTeX entries inherits from some of these abstract classes according to their set of mandatory fields.

http://bibtexml.sourceforge.net

Authors: David Touzet (david.touzet_NOSPAM univ-nantes.fr), Guillaume Hillairet (g.hillairet_NOSPAM gmail.com)

• Source file

Domains: bibliography, XML

This is a partial metamodel of BibTeXML which is an XML-based format for the BibTeX bibliographic tool system for use with LaTeX. A bibliography is modelized by a BibTeX File element. This element is composed of BibTeX Entries which are each associated with an id. All entries inherit, directly or indirectly, of the abstract BibTeX Entry element. The abstract classes Authored Entry, Dated Entry, Titled Entry and Book Titled Entry, as well as the Misc entry, directly inherit of BibTeX Entry. There are 13 possible entry types: PhD Thesis, Master Thesis, Article, Tech Report, Unpublished, Manual, In Proceedings, Proceedings, Booklet, In Collection, Book, In Book and Misc. Concrete BibTeX entries inherits from some of these abstract classes according to their set of mandatory fields. This metamodel only deals with the mandatory fields of each BibTeX entries (for instance, author, year, title and journal for an article entry). But it has been designed in such a way that it should be easily extensible to handle optional fields (with minor modifications).

http://bibtexml.sourceforge.net

Authors: David Touzet (david.touzet_NOSPAM univ-nantes.fr)

• Source file

Domains: Bibliography

In the simple metamodel Book, the class Book contains an ordered set of Chapters. Each Book has a title and a set of chapters. Each Chapter has a title and a number of pages. This very simple metamodel is mainly used for illustrative purposes.

Authors: Fr�d�ric Jouault (frederic.jouault_NOSPAM univ-nantes.fr)

• Source file

Domains:

This metamodel describes Bossa. Bossa is a kernel-level event-based framework to facilitate the implementation and integration of new scheduling policies.

http://www.emn.fr/x-info/bossa/grammar3.pdf http://www.emn.fr/x-info/bossa/

Authors: SROUR Youssef (srour.youssef_NOSPAM gmail.com)

• Source file

Domains: business process

This metamodel was semi-automatically derived from the BPEL metamodel used by the Eclipse BPEL project (http://www.eclipse.org/bpel/), which uses the XSD (from http://www.eclipse.org/xsd/), and WSDL (from http://www.eclipse.org/webtools/) metamodels. Elements from XSD and WSDL are therefore included in the KM3 version. Moreover, some Ecore artefacts remain (see ecore package).

http://www.eclipse.org/bpel/

Authors: Fr�d�ric Jouault (frederic.jouault_NOSPAM univ-nantes.fr)

• Source file

Domains: business process

This metamodel was semi-automatically derived from the BPMN metamodel used by the BPMN editor that Intalio contributed to Eclipse.

http://www.eclipse.org/stp/bpmn/index.php

Authors: Fr�d�ric Jouault (frederic.jouault_NOSPAM univ-nantes.fr), Freddy Allilaire (freddy.allilaire_NOSPAM univ-nantes.fr)

• Source file

Domains: Bibtex Query Language

This metamodel is used to express query over Bibtex models. It uses a textual syntax to simplify the writing of querys. This metamodel is used in the Bibtex Management project.

http://wiki.eclipse.org/index.php/AMMA

Authors: Guillaume Hillairet (g.hillairet_NOSPAM gmail.com)

• Source file

Domains: Software bug tracking

This metamodel describes the structure used by Bugzilla to import/export bugs in XML format. Bugzilla is a free "Defect Tracking System" or "Bug-Tracking System" which allows individual or groups of developers to keep track of outstanding bugs in their product effectively.

bugzilla.dtd, http://www.mantisbt.org/mantis/view.php?id=4024 at the bottom of the page

Authors: Hugo Bruneliere (hugo.bruneliere_NOSPAM gmail.com)

• Source file

Domains: Business

This metamodel fragment describes a Business Entity Model

This metamodel has been extracted from information available in the following article: Article "Processes, Roles, and Events : UML Concepts for Entreprise Architecture" by Alistair Barros, Keith Duddy, Michael lawley, Zoran Milosevic, Kerry Raymond, Andrew Wood Page 71, Section 4, Fig. 4. Business Entity Model Lecture Notes in Computer Science 1939 Andy Evans, Stuart Kent, Bran Selic UML 2000 - The Unified Modeling Language

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains: Business

This metamodel fragment describes a Business Process Model

This metamodel has been extracted from information available in the following article: Article "Processes, Roles, and Events : UML Concepts for Entreprise Architecture" by Alistair Barros, Keith Duddy, Michael lawley, Zoran Milosevic, Kerry Raymond, Andrew Wood Page 66, Section 2.4, Fig. 1. Business Process Model Lecture Notes in Computer Science 1939 Andy Evans, Stuart Kent, Bran Selic UML 2000 - The Unified Modeling Language

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains: Programming language

This metamodel describes C which is a standardized imperative computer programming language developed in the early 1970s by Ken Thompson and Dennis Ritchie for use on the UNIX operating system. It has since spread to many other operating systems, and is one of the most widely used programming languages. C is prized for its efficiency, and is the most popular programming language for writing system software, though it is also used for writing applications. It is also commonly used in computer science education, despite not being designed for novices. This simplified metamodel describes a subset of the C language.

The C ANSI/ISO Specification, http://www.nirvani.net.nyud.net:8090/docs/ansi_c.pdf

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Architecture Description, SoS (System of System), View, Viewpoint

CADM (C4ISR Architecture Data Moodel) metamodel is an overview of the key entities and relationships for the C4ISR Core.

http://www.afcea.org/education/courses/archfwk2.pdf http://www.government.popkin.com/frameworks/c4isr.htm http://www.c4isrjournal.com/ DoDAF official site http://www.defenselink.mil/nii/global_Info_grid.html

Authors: Albin Jossic (albin.jossic gmail.com), ATLAS team (Nantes, France)

• Source file

Domains: Component modeling

This metamodel describes a subset of the Component Description Model (CDE) which is a set of generic component-related UML extensions describing run-time (executable) components and their specifications. It is part of the Open Information Model (OIM) supplied with the Microsoft Repository. OIM is no more available since Microsoft stopped supporting it.

MICROSOFT REPOSITORY VERSION 2 AND THE OPEN INFORMATION MODEL, http://research.microsoft.com/~philbe/Info%20Sys%20on%20MS%20Repository%20for%20Web.pdf

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Object-oriented programming

This metamodel describes simple class schema models (OOP). It consists of classes having a name which they inherit from the abstract class NamedElt. The principal class is the class Class, which contains a set of attributes of the type Attribute and has the super references pointing to superclasses for modelling inheritance trees. The class DataType models primitive data types. Class and DataType inherit from Classifier which serves to declare the type of Attributes. Attributes can be multivalued.

Authors: Fr�d�ric Jouault (frederic.jouault_NOSPAM univ-nantes.fr)

• Source file

Domains: Database, Eclipse, Business reporting, BIRT

This metamodel simply describes the "ClassicModels" BIRT Sample database which is a simple example of typical business data such as customers, orders, order line items, products and so on.

The Eclipse BIRT project: http://www.eclipse.org/birt/phoenix/

Authors: Hugo Bruneliere (hugo.bruneliere univ-nantes.fr)

• Source file

Domains: Chemical, XML

This metamodel describes CML (Chemical Markup Language). It is based on the 1.0 DTD of CML. CML deliberately does not cover all chemistry but concentrates on "molecules" (discrete entities representatable by a formula and usually a connection table). It supports a hierarchy for compound molecules (clathrates, macromolecules, etc.). It also supports reactions, and macromolcular strucures/sequences (though it can interoperate with other macromolecular XML languages as they are developed). It has no specific support for physicochemical concepts, but can support labelled numeric datatypes of several sorts which can cover a wide range of requirements. It allows quantities and properties to be specifically attached to molecules, atoms or bonds.

http://www.xml-cml.org/

Authors: Pierrick Guyard (pierrick.guyard_NOSPAM gmail.com)

• Source file

Domains: Programming language

This metamodel describes COBOL (Common Business Oriented Language) which is a programming languages still used in business programming . It has been developed for building business, finance, and administrative systems for companies and governments in 1959 by a group of computer professionals called the Conference on Data Systems Languages (CODASYL).

http://cobol.com/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: UML

This metamodel fragment describes collaborations and interactions in UML metamodel

This metamodel fragment has been extracted from information available in the following article: Article "Supporting Disciplined Reuse and Evolution of UML Models" by Tom mens, Carine Lucas, Patrick Steyaert Page 384, Section 3.3, Fig. 3 Collaborations and Interactions in UML Metamodel Lecture Notes in Computer Science 1618 Jean B�zivin, Pierre-Alain Muller The Unified Modeling Language UML 98: Beyond the notation

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains: Business, Management

This metamodel fragment describes a Company Structure

This metamodel has been extracted from information available in the following article: Article "The Role of "Roles" in use case Diagrams" by Alain Wegmann, Guy Genilloud Page 212, Section 2, Fig. 1. Class diagram describing Company structure Lecture Notes in Computer Science 1939 Andy Evans, Stuart Kent, Bran Selic UML 2000 - The Unified Modeling Language

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains:

This metamodel describes ComponentUML.

http://delivery.acm.org/10.1145/1130000/1125810/p39-basin.pdf?key1=1125810&key2=6220095511&coll=GUIDE&dl=&CFID=15151515&CFTOKEN=6184618

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains:

This metamodel describes simple contacts which are persons (firstname and surname) with several phone numbers. Many systems like Outlook offer support for contact handling.

Authors: Antoine Pigeau (antoine.pigeau_NOSPAM univ-nantes.fr)

• Source file

Domains:

This metamodel describes ControllerUML.

http://delivery.acm.org/10.1145/1130000/1125810/p39-basin.pdf?key1=1125810&key2=6220095511&coll=GUIDE&dl=&CFID=15151515&CFTOKEN=6184618

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: Software engineering, software component, distributed computing

This metamodel describes a subset of CORBA (Common Object Request Broker Architecture) which is a standard for software componentry. The CORBA standard is created and controlled by the Object Management Group (OMG). It defines APIs, communication protocol, and object/service information models to enable heterogeneous applications written in various languages running on various platforms to interoperate. CORBA therefore provides platform and location transparency for sharing well-defined objects across a distributed computing platform.

The OMG�s CORBA Website, http://www.corba.org/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains:

This metamodel describes CPL (Call Processing Language). It is a standard scripting language for the SIP protocol. It offers a limited set of language constructs. CPL is supposed to be simple enough so that it is safe to execute untrusted scripts on public servers.

http://www.faqs.org/rfcs/rfc3880.html

Authors: Frederic Jouault

• Source file

Domains: Programming language

This metamodel simply describes C++ which is a general-purpose computer programming language. This is a statically typed language supporting procedural programming, data abstraction, object-oriented programming, and generic programming. During the 1990s, C++ became one of the most popular commercial programming languages. The C++ programming language standard was ratified in 1998 as ISO/IEC 14882:1998, the current version of which is the 2003 version, ISO/IEC 14882:2003.

http://www.cplusplus.com/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Ontology

This metamodel describes a subset of the Core Plan Representation (CPR) which is an effort to construct a general plan ontology. It has been developed to support the common plan representation of military planning, workflow and simulation. CPR is a DARPA project that mainly focuses on planning (specifying an action list in order to deal with a set of objectives) as well as on foreseeing (specifying moments at which activities will be realized and resource quantities will be used).

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains:

This metamodel describes CRISTAL. The CRISTAL system is being developed to control the production and assembly process of the CMS Electromagnetic Calorimeter (ECAL) detector.

http://chep2000.pd.infn.it/paper/pap-a010.pdf

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: Programming language, object-oriented programming

This metamodel simply describes C# which is a simple, modern, object-oriented, and type-safe programming language that has its roots in the C family of languages. It has been developped by Microsoft. This simplified metamodel corresponds to a small subset of the language.

http://msdn.microsoft.com/vcsharp/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains:

This metamodel describes "CSM", that is a metamodel developed from the Real-Time and Distributed Systems Group at Carleton University to integrate performance annotations into software models.

V. Cortellessa, How far are we from the definition of a common software performance ontology? (http://delivery.acm.org/10.1145/1080000/1071044/p195-cortellessa.pdf?key1=1071044&key2=4930095511&coll=&dl=ACM&CFID=15151515&CFTOKEN=6184618) D.B. Petriu, M. Woodside, A Metamodel for Generating Performance Models from UML Designs, Proc. of UML Conference, LNCS 3273, pp 41-53, (2004)

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: Data Warehousing, MOF

This metamodel describes a subset of the core of the Common WareHouse Metamodel (CWM) which is a specification that describes metadata interchange among data warehousing, business intelligence, knowledge management and portal technologies.

The Data Warehousing, CWM and MOF Resource Page, http://www.omg.org/technology/cwm/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Data Warehousing, MOF

This metamodel describes a subset of the "relational data" part of the Common WareHouse Metamodel (CWM) which is a specification that describes metadata interchange among data warehousing, business intelligence, knowledge management and portal technologies.

The Data Warehousing, CWM and MOF Resource Page, http://www.omg.org/technology/cwm/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: DSI, SDM Deployment Report Metamodel, XML

This metamodel corresponds to the Deployment Report metamodel of the Microsoft SDM (System Definition Model). It is derived from the XML Schema "DeploymentReport.xsd" which is the metamodel for describing the error messages that may occur during the deployment s simulation on a model (that conforms to the SDM metamodel) designed in Visual Studio 2005 Beta2.

DeploymentReport.xsd, SDM.km3

Authors: Albin Jossic (jossic.albin_NOSPAM gmail.com), Microsoft

• Source file

Domains: UML, Diagrams

This metamodel describes a subset of Diagram Interchange which is an extension of the UML meta-model and is currently based on UML 2.0. The existing mechanism of XMI[UML] for exchanging models includes only the logical information but not the graphical presentation information. The diagram interchange extension allows graphical information to be included for diagrams used in UML models.

UML 2.0 Diagram Interchange Specification, http://www.omg.org/docs/ptc/03-09-01.pdf

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Document composition, XML

This metamodel describes a limited subset of DocBook, an XML-based format for document composition. Within this metamodel, a DocBook document is associated with a DocBook element. Such an element is composed of several Books that, in their turn, are composed of several Articles. An Article is composed of Sections that are ordered. A Section is composed of Paragraphs that are also ordered within each section. Both Article and Section inherit from the TitledElement abstract class.

DocBook: The Definitive Guide. Norman Walsh. O Reilly & Associates, Inc. October 1999.

Authors: David Touzet (david.touzet_NOSPAM univ-nantes.fr)

• Source file

Domains: Architecture Description, SoS (System of System)

A Metamodel of DoDAF (Department of Defense Architecture Framework). This metamodel describes DoDAF OV5 (Operational View) Operational Activity Model. DoDAF AV5 is designed to represent capabilities and operations activities.

http://www.defenselink.mil/nii/global_Info_grid.html http://www.defenselink.mil/nii/doc/DoDAF_v1_Volume_II.pdf Tailoring DODAF to Support a Service Oriented Architecture, Fatma Dandashi, Huei-Wan Ang, Christopher Bashioum Mitre Corp. 12-7-2004 "Recommended Practice for Architectural description of Softwrare-Intensive Systems", IEEE Std 1471-2000, IEEE, 2000. IEEE1471ConceptualModel.km3 and IEEE1471ViewpointM2.km3 DoDAF.km3 DoDAF-SV4.km3 DoDAF-SV5.km3

Authors: Albin Jossic (jossic.albin gmail.com)

• Source file

Domains: Architecture Description, SoS (System of System)

A Metamodel of DoDAF (Department of Defense Architecture Framework). This metamodel describes DoDAF SV4 (Structural View) Systems Functionalities Description. This part of DoDAF is used to represent system functional hierarchies and system functions.

http://www.defenselink.mil/nii/global_Info_grid.html http://www.defenselink.mil/nii/doc/DoDAF_v1_Volume_II.pdf Tailoring DODAF to Support a Service Oriented Architecture, Fatma Dandashi, Huei-Wan Ang, Christopher Bashioum Mitre Corp. 12-7-2004 "Recommended Practice for Architectural description of Softwrare-Intensive Systems", IEEE Std 1471-2000, IEEE, 2000. IEEE1471ConceptualModel.km3 and IEEE1471ViewpointM2.km3 DoDAF.km3 DoDAF-OV5.km3 DoDAF-SV5.km3

Authors: Albin Jossic (jossic.albin gmail.com)

• Source file

Domains: Architecture Description, SoS (System of System)

A Metamodel of DoDAF (Department of Defense Architecture Framework). This metamodel is a model for DoDAF SV5 (Structural View) "Operational Activity to Systems Function Traceability Matrix". This DoDAF part is in correlation with OV5 and SV4 parts with the aim to provide a traceability matrix. This matrix has two axes. The first one represents the capabilities and operation activities from an OV5 model. The second one represents systems and their system functions. Each matrix elements represents the level of the relationship between Operational Activities and System Functions. They are three level: "red" means functionality planned but no developed, "yellow" means partial functionality provided or full but system has not been yet fielded, and "green" means full functionality provided and system has been fielded.

http://www.defenselink.mil/nii/global_Info_grid.html http://www.defenselink.mil/nii/doc/DoDAF_v1_Volume_II.pdf Tailoring DODAF to Support a Service Oriented Architecture, Fatma Dandashi, Huei-Wan Ang, Christopher Bashioum Mitre Corp. 12-7-2004 "Recommended Practice for Architectural description of Softwrare-Intensive Systems", IEEE Std 1471-2000, IEEE, 2000. IEEE1471ConceptualModel.km3 and IEEE1471ViewpointM2.km3 DoDAF.km3 DoDAF-OV5.km3 DoDAF-SV4.km3

Authors: Albin Jossic (jossic.albin gmail.com)

• Source file

Domains: Architecture Description, SoS (System of System), View, Viewpoint

A Metamodel of DoDAF (Department of Defense Architecture Framework). In the metamodel, we have included SV-1, SV-4, OV-4, OV-7 and SV-11.

http://www.defenselink.mil/nii/global_Info_grid.html Tailoring DODAF to Support a Service Oriented Architecture, Fatma Dandashi, Huei-Wan Ang, Christopher Bashioum Mitre Corp. 12-7-2004 "Recommended Practice for Architectural description of Softwrare-Intensive Systems", IEEE Std 1471-2000, IEEE, 2000. IEEE1471ConceptualModel.km3 and IEEE1471ViewpointM2.km3 MoSAF-AV.km3

Authors: Albin Jossic (jossic.albin gmail.com)

• Source file

Domains: Graphviz Tools

Dot is an automatic graph layout program from Graphviz. It can be used to create graphical files, such as PS, PNG... out of its layout.

http://www.graphviz.org

Authors: Jean Pali�s

• Source file

Domains: Microsoft DotNET

The Sytem.Reflection namespace from DotNET framework

Authors: Jean-Marc Prieur (j-m.prieur wanadoo.fr), R�gis Chevrel (chevrel.regis gmail.com) [1], Hugo Bruneli�re (hugo.bruneliere gmail.com)[1] ; Albin Jossic (albin.jossic gmail.com)[1] ;[1] ATLAS team (Nantes, France)

• Source file

Domains: MDE

This metamodel represents domain models (or metamodels in MDA) used by Microsoft DSL Tools (May 2005 CTP release for Visual Studio 2005 Beta 2). With DSL Tools you can create your own designer for a visual domain specific language that is represent by a domain model. The tools generate the code of a graphical editor for the language you defined in a domain model.

http://lab.msdn.microsoft.com/teamsystem/workshop/dsltools/

Authors: Guillaume Hillairet (g.hillairet_NOSPAM gmail.com), William Piers (willaim.piers_NOSPAM gmail.com)

• Source file

Domains: MDE, DSL models

This metamodel represents DSL models used by Visual Studio DSL Tools to represent models for a domain model. Those models are stored in an xml file. This metamodel captures informations about the logic domain but not about the graphical representation.

Authors: Hillairet Guillaume (g.hillairet_NOSPAM gmail.com)

• Source file

Domains: XML

This metamodel describes external DTD (Document Type Definition). The purpose of a DTD is to define the legal building blocks of an XML document. It defines the document structure with a list of legal elements. A DTD can be declared inline in your XML document, or as an external reference.

Authors: Pierrick Guyard (pierrick.guyard_NOSPAM gmail.com)

• Source file

Domains:

This metamodel describes DTMP. It stands for discrete time Markov processes and describes the process at successive transition epochs.

http://delivery.acm.org/10.1145/1080000/1071024/p25-grassi.pdf?key1=1071024&key2=9340095511&coll=GUIDE&dl=&CFID=15151515&CFTOKEN=6184618

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: DataBase

This metamodel describes geometrical data in DXF (Drawing eXchange Format) which is the native vector file format of Autodesk s AutoCAD CAD application. This simplified DXF metamodel has an aggregation hierarchy. It consists of one DXF element that contains a number of Meshes (a 3D object based on a set of contiguous lines) which in turn consist of a number of Points (two consecutive points represent a line). Meshes and Points have names. Points have three coordinates, namely x, y and z.

DXF - Autodesk Drawing eXchange Format, http://www.faqs.org/faqs/graphics/fileformats-faq/part3/section-45.html

Authors: Peter Rosenthal

• Source file

Domains: Programming paradigms

This metamodel describes the structure of EAI (Enterprise Application Integration). The goal of EAI is the interoperability and the organization of the information flow between heterogeneous applications. An EAI project consists in setting up an architecture in which different applications communicate with one another. This has to do with developing connections (e.g. middleware) enabling the applications to interface, using different communication protocols. Nevertheless, EAI spans beyond interoperability between applications: it allows to define a workflow between applications and constitute therefore an alternative to the ERP with a more modular approach. It provides a metadata interchange standard for information about accessing application interfaces. The goal is to simplify application integration by standardizing application metadata for invoking and translating application information. The FCM composition model unifies the composition and coordination needs for factual or other styles. This model is at a higher abstraction level than the one of the flows of the messages, sources, targets, adapters and other operators.

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: XML

ebXML (Electronic Business using eXtensible Markup Language), is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet. Using ebXML, companies now have a standard method to exchange business messages, conduct trading relationships, communicate data in common terms and define and register business processes. ebXML was started in 1999 as an initiative of OASIS and the United Nations/ECE agency CEFACT. The original project envisioned and delivered five layers of substantive data specification, including XML standards for: Business processes , Core data components, Collaboration protocol agreements, Messaging, Registries and repositories.

http://www.ebxml.org/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Eclipse, Launch configuration

This generic metamodel simply describes Eclipse launch configurations (i.e. ".launch" files).

http://www.eclipse.org

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Freddy Allilaire (freddy.allilaire gmail.com)

• Source file

Domains: IDE

This metamodel describes the structure of Eclipse plug-in. The Eclipse Platform is designed for building integrated development environments (IDE) that can be used to create applications as diverse as Web sites, embedded Java programs, C++ programs, and Enterprise JavaBeans. Although the Eclipse Platform has a lot of built-in functionality, most of that functionality is very generic. It takes additional tools to extend the Platform to work with new content types, to do new things with existing content types, and to focus the generic functionality on something specific. The Eclipse Platform is built on a mechanism for discovering, integrating, and running modules called plug-ins. A tool provider writes a tool as a separate plug-in that operates on files in the workspace and surfaces its tool-specific UI in the workbench. When the Platform is launched, the user is presented with an integrated development environment (IDE) composed of the set of available plug-ins. The quality of the user experience depends significantly on how well the tools integrate with the Platform and how well the various tools work with each other.

http://www.eclipse.org/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains:

This metamodel describes EG. EG stands for Execution Graphs. In EG, nodes represent software workload components, and edges the transfer of control. Each Node in the EG metamodel is characterized by attributes such as name, time-demand, resource-type and service-name (demand vector). The node type (control, basic, etc.) derives directly from the EG terminology.

http://delivery.acm.org/10.1145/1080000/1071024/p25-grassi.pdf?key1=1071024&key2=9340095511&coll=GUIDE&dl=&CFID=15151515&CFTOKEN=6184618

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains:

This metamodel describes EQN (Extended Queueing Network). It is an extension of QN (as LQN). EQN has been introduced in order to represent several interesting features of real systems, such as synchronization and concurrency constraints, finite capacity queues, memory and population constraints and simultaneous resource possession.

http://delivery.acm.org/10.1145/1080000/1071024/p25-grassi.pdf?key1=1071024&key2=9340095511&coll=GUIDE&dl=&CFID=15151515&CFTOKEN=6184618

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: Information Modeling Language

This EXPRESS metamodel was created from the EXPRESS UML model RFC (http://www.omg.org/cgi-bin/doc?mantis/2007-09-02). The EXPRESS information modeling language is widely used in the scope of the ISO 10303 Standard for Exchange of Product Data (STEP).

http://www.omg.org/cgi-bin/doc?mantis/2007-09-02

Authors: Freddy Allilaire

• Source file

Domains: UML

This metamodel fragment describes extended UML core package metamodel

This metamodel fragment has been extracted from information available in the following article: Article "On Using UML Class Diagrams for Object-Oriented Database Design" by Yongzhen Ou Page 177, Section 3, Fig. 1 Extended UML Core Package Lecture Notes in Computer Science 1618 Jean B�zivin, Pierre-Alain Muller The Unified Modeling Language UML 98: Beyond the notation

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains: Family

This basic metamodel allows to represent families. A family, which has a name, is composed of several persons identified by their firstname. Each person (member of a family) has a closest friend which is also a person. It can have several email addresses.

Authors: Antoine Pigeau (antoine.pigeau_NOSPAM univ-nantes.fr)

• Source file

Domains: GME, domain-specific modeling

This metamodel describes feature diagrams which are a part of the GME (Generic Modeling Environment). The Generic Modeling Environment is a configurable toolkit for creating domain-specific modeling and program synthesis environments. The configuration is accomplished through metamodels specifying the modeling paradigm (modeling language) of the application domain. The modeling paradigm contains all the syntactic, semantic, and presentation information regarding the domain; which concepts will be used to construct models, what relationships may exist among those concepts, how the concepts may be organized and viewed by the modeler, and rules governing the construction of models. The modeling paradigm defines the family of models that can be created using the resultant modeling environment. The metamodeling language is based on the UML class diagram notation and OCL constraints.

The GME official site, http://www.isis.vanderbilt.edu/Projects/gme/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains:

This metamodel describes the concepts of a finite state machine.

http://repository.escherinstitute.org/Plone/tools/suites/mic/great/

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains:

This metamodel describes Flat Signal Flow.

http://www.isis.vanderbilt.edu/publications/archive/Sprinkle_JM_11_4_2002_Domain_Evo.doc

Authors: Youssef Srour (srour.youssef_NOSPAM gmail.com)

• Source file

Domains: Multi-Agent

This metamodel describes the concepts of Gaia. It is a methodology for agent-oriented analysis and design.

A Study of some Multi-Agent Meta-Models Authors: Carole Bernon, Massimo Cossentino, Marie-Pierre Gleizes, Paola Turci, Franco Zambonelli http://www.jamesodell.com/AOSE04-proceedings/AOSE04-08.pdf, p6

Authors: SIMON Eric(simon.eric3_NOSPAM gmail.com)

• Source file

Domains: IDE

This metamodel describes the notion editor. A generic editor is composed of blocks (e.g. CommentsLine or String) and GroupElement (e.g. Keyword, Constant or Symbol).

Authors: Julien Bernier, Manuel Boillod, Joanny Christ and Sylvain Leduby

• Source file

Domains: IDE

This metamodel describes a generic outline. In Eclipse, editors often have corresponding content outliners that provide a structured view of the editor contents and assist the user in navigating through the content of the editor.

Authors: Julien Bernier, Manuel Boillod, Joanny Christ and Sylvain Leduby

• Source file

Domains: DataBase

This metamodel describes basic geometrical operations (rotate, move, explode) that can be executed in sequence or parallel. The GeoTrans metamodel has an aggregation hierarchy. GeoTransfo can be put in a tree structure through subGeoTransfos and superGeoTransfos. GeoTransfo may have Params (parameters). GeoTransfo represents a geometrical operation. The actual operation is determined from its name attribute. Freeze means that the output of the operation has to be captured. A Param has a name, a Double value param and a back reference to the operation it belongs to.

Authors: Peter Rosenthal (peter.rosenthal_NOSPAM univ-nantes.fr)

• Source file

Domains: GRAFCET

This basic metamodel describes GRAFCET. Grafcet is a french discrete system modeling notation close to Petri nets. The GRAFCET represents graphically the operation of an automatism by: Steps with associated action, transitions between steps, Directed connections between the steps and the transitions.

Authors: Pierrick Guyard (pierrick.guyard_NOSPAM gmail.com)

• Source file

Domains: IDE

This metamodel describes the notion of Graphical User Interface (GUI).

Authors: Anas Abouzahra, Pierre-Yves Baudouin, Thomas Broussaud, Gr�gory Pouliquen

• Source file

Domains:

This metamodel is presented by Guido Wachsmut in the paper "Metamodel Adaptation and Model Co-adaption". The metamodel captures a Petri net. A Petri net is composed of several places and transitions. Each transition has at least one input and one output place.

http://metrik.informatik.hu-berlin.de/grk-wiki/images/8/8a/Metamodel_Adaptation_and_Model_Co-adaptation.pdf

Authors: Kelly Garces (kellygarce gmail.com)

• Source file

Domains:

This metamodel is presented by Guido Wachsmut in the paper "Metamodel Adaptation and Model Co-adaption". The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place.

http://metrik.informatik.hu-berlin.de/grk-wiki/images/8/8a/Metamodel_Adaptation_and_Model_Co-adaptation.pdf

Authors: Kelly Garces (kellygarce_NOSPAM gmail.com)

• Source file

Domains:

This metamodel is presented by Guido Wachsmut in the paper "Metamodel Adaptation and Model Co-adaption". The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit.

http://metrik.informatik.hu-berlin.de/grk-wiki/images/8/8a/Metamodel_Adaptation_and_Model_Co-adaptation.pdf

Authors: Kelly Garces (kellygarce_NOSPAM gmail.com)

• Source file

Domains:

This metamodel is presented by Guido Wachsmut in the paper "Metamodel Adaptation and Model Co-adaption". The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit. PTArc and TPArc are respectively representing place-to-transition arcs and transition-to-place ones.

http://metrik.informatik.hu-berlin.de/grk-wiki/images/8/8a/Metamodel_Adaptation_and_Model_Co-adaptation.pdf

Authors: Kelly Garces (kellygarce_NOSPAM gmail.com)

• Source file

Domains:

This metamodel is presented by Guido Wachsmut in the paper "Metamodel Adaptation and Model Co-adaption". The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit. PTArc and TPArc are respectively representing place-to-transition arcs and transition-to-place ones. Arcs are annotated with weight.

http://metrik.informatik.hu-berlin.de/grk-wiki/images/8/8a/Metamodel_Adaptation_and_Model_Co-adaptation.pdf

Authors: Kelly Garces (kellygarce_NOSPAM gmail.com)

• Source file

Domains:

This metamodel is presented by Guido Wachsmut in the paper "Metamodel Adaptation and Model Co-adaption". The metamodel captures a Petri net. A Petri net is composed of several places and transitions (at least one place and one transition). Each transition has at least one input place and one output place. Arcs between places and transitions are explicit. PTArc and TPArc are respectively representing place-to-transition arcs and transition-to-place ones. Arcs are annotated with weight. In order to model dynamic aspects, places need to be marked with tokens.

http://metrik.informatik.hu-berlin.de/grk-wiki/images/8/8a/Metamodel_Adaptation_and_Model_Co-adaptation.pdf

Authors: Kelly Garces (kellygarce_NOSPAM gmail.com)

• Source file

Domains: Bibliography

This is HAL import metamodel. This metamodel is used to import bibliography into HAL (Hyper Article en Ligne). HAL is a tool for direct scientific communication between researchers. Documents deposited in HAL are not subjected to any peer evaluation; but they should, however, be of sufficient quality to rate submission for publication in a specialized scientific journal. They should be uploaded either by one of the co-authors with the permission of the others or by an authorized person (e.g. librarian) who takes responsibility.The free access to these documents is intended to provide the widest possible diffusion of research work, but the intellectual property remains that of the authors. The users should conform to the usual standards of good academic usage, in the same way as in paper publications: respect of original work, citation of previous work, no plagiarism, etc.

http://hal.ccsd.cnrs.fr/, http://import.ccsd.cnrs.fr/doc/

Authors: Guillaume Hillairet (g.hillairet_NOSPAM gmail.com)

• Source file

Domains:

This metamodel describes hierarchical signal flow concepts.

http://www.isis.vanderbilt.edu/publications/archive/Sprinkle_JM_11_4_2002_Domain_Evo.doc

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains:

This metamodel describes hierarchical state machine concepts.

http://repository.escherinstitute.org/Plone/tools/suites/mic/great/

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: HTML

This basic metamodel describes HyperText Markup Language. HTML is the lingua franca for publishing hypertext on the World Wide Web. It is a non-proprietary format based upon SGML, and can be created and processed by a wide range of tools, from simple plain text editors - you type it in from scratch- to sophisticated WYSIWYG authoring tools. HTML uses tags such as

and

http://www.w3.org/MarkUp/

Authors: Freddy Allilaire (freddy.allilaire_NOSPAM univ-nantes.fr)

• Source file

Domains:

This metamodel describes Hybrid Automata System.

http://chess.eecs.berkeley.edu/conferences/03/presentations/sprinkle_chess_03.ppt

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: SoS

Metamodel of IEEE 1471-2000

IEEE1471ViewpointM2.km3 "IEEE Std 1471 and Beyond" Rich Hilliard, ConsentCache, January 1 2001 "ANSI/IEEE 1471 and Systems Engineering", Mark W. Maier David, Emery Rich Hilliard "Recommended Practice for Architectural description of Softwrare-Intensive Systems", IEEE Std 1471-2000, IEEE, 2000.

Authors: Albin Jossic (jossic.albin_NOSPAM gmail.com)

• Source file

Domains: SoS

Metamodel of IEEE 1471-2000

IEEE1471ConceptualModel.km3 "IEEE Std 1471 and Beyond" Rich Hilliard, ConsentCache, January 1 2001 "ANSI/IEEE 1471 and Systems Engineering", Mark W. Maier David, Emery Rich Hilliard "Recommended Practice for Architectural description of Softwrare-Intensive Systems", IEEE Std 1471-2000, IEEE, 2000.

Authors: Albin Jossic (jossic.albin_NOSPAM gmail.com)

• Source file

Domains: Transactions

This metamodel describes a subset of IMS OTMA (Open Transaction Manager Access) which is an IBM transaction-based and connectionless client/server protocol within an OS/390 sysplex environment. IMS Transaction Message meta-model captures the metadata associated with sending and receiving messages to and from IMS transaction applications.

IBM IMS Product webpage, http://www-306.ibm.com/software/data/ims/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: UML

This metamodel describes the Integration of OCL Expressions into the UML Core and Data Types Packages

This metamodel has been extracted from information available on this book: Article "A Metamodel for OCL" by Mark Richters and Martin Gogolla Page 160, Section 3, Fig. 3 Integration of OCL Expressions into the UML Core and Data Types Packages Lecture Notes in Computer Science 1723 Robert France, Bernhard Rumpe (Eds.) The Unified Modeling Language UML 99: Beyond the standard

Authors: Julien Baudry (jul.baudry_NOSPAM gmail.com)

• Source file

Domains:

IRL is a formal rule language designed by ILOG with several implementations build on the top of very powerful and effective resolution engines.

Authors: Anas Abouzahra

• Source file

Domains: Object-oriented programming, Java

This metamodel describes all the structural concepts of Java 5 source code (from packages up to method invocations and comments) and links between code elements (method invocations, variables usage, class inheritance, ...). The aim of this metamodel is to provide support in reverse-engineering Java applications or migrating existing applications to Java.

Authors: Fabien Giquel (fgiquel_NOSPAM mia-software.com)

• Source file

Domains: Object-oriented programming, Java

This simplified metamodel of Java consists principally of JavaElements which all have a name. A JavaClass has Methods and Fields and belongs to a Package. Methods, Fields and JavaClasses are subclasses of Modifiers and therefore indicate whether they are public, static or final. JavaClasses and Methods declare with the isAbstract attribute whether they are abstract or not. PrimitiveTypes and JavaClasses are Types. A Method has a Type as return Type and parameters of certain Types. A Field has also a Type.

Authors: Fr�d�ric Jouault (frederic.jouault_NOSPAM univ-nantes.fr)

• Source file

Domains: Object-oriented programming, Java

This basic metamodel describes JAVA. The Java language is an object-oriented programming language created by James Gosling and other engineers at Sun Microsystems. It was developed in 1991, as part of the Green Project, and officially announced on May 23 1995, at SunWorld; being released in November. Gosling and friends initially designed Java, which was called Oak at first (in honor of a tree outside Gosling s office), to replace C++ (although the feature set better resembles that of Objective C). The Java specifications are community-maintained through the Sun-managed Java Community Process. Sun holds a trademark on the Java name. The Java software plays three crucial roles or identities in the field of software: as a programming language, as middleware, as a platform. A crucial component of Java is the Java Virtual Machine (JVM). The availability of the JVM on almost all types of device, chips and software package enables Java to function both as middleware and a computing platform. The JVM enables Java to be "platform independent" since the JVM on each device/chip interprets the standard Java bytecode. This means you can develop code on your PC and expect it to run on Java-enabled phones as well as on mainframes equipped with Java without any adjustments. Hence the expression "Write once, run anywhere." This also represents a huge amount of savings for software developers as code can be developed locally and cheaply.

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com), Pierrick Guyard (pierrick.guyard gmail.com)

• Source file

Domains: Object-oriented programming, Java

This metamodel describes a full abstract syntax tree (AST) of the code (statements, expressions, annotations and Javadoc) taken from a Java compilation unit (typically a Class). It is based upon the Eclipse JDT API specification.

The "Eclipse JDT API Specification" : http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.jdt.doc.isv/reference/apt/overview-summary.html

Authors: Mika�l Barbero univ-nantes.fr>

• Source file

Domains: Object-oriented programming, Java

This basic metamodel represent Java source code. Java sources are modelized by a JavaSource element. This element is composed of ClassDeclarations. Each ClassDeclaration is composed of MethodDefinitions. Both ClassDeclaration and MethodDefinition inherit from the abstract NamedElement class (which provides a name). A MethodDefinition is composed of MethodInvocations (a call to a method). Each MethodInvocation is, in its turn, associated with a one and only MethodDeclaration (the called method).

http://www.cs.washington.edu/research/constraints/web/badros-javaml-www9/

Authors: David Touzet (david.touzet_NOSPAM univ-nantes.fr)

• Source file

Domains: Object Management Group (OMG), Architecture-Driven Modernization (ADM), Model-Driven Reverse Engineering

This metamodel describes the whole Knowledge Discovery Meta-Model (KDM), KDM being the first part of the work of the OMG Architecture-Driven Modernization (ADM) Task Force. KDM specifies the core concepts required for understanding existing software in preparation for its modernization and provides infrastructure to support more detailed definitions of Knowledge Discovery.

http://www.kdmanalytics.com/kdm/

Authors: KM3 version auto-generated using ATL by the ATLAS Group (INRIA & LINA) from the Ecore version provided within the KDM Eclipse Plugin (KDM Analytics, Inc).

• Source file

Domains: Object Management Group (OMG), Architecture-Driven Modernization (ADM), Model-Driven Reverse Engineering

This metamodel describes the main concepts of the Core and Kdm packages of the Knowledge Discovery Meta-Model (KDM) by the OMG Architecture-Driven Modernization (ADM) Task Force. KDM specifies the core concepts required for understanding existing software in preparation for its modernization and provides infrastructure to support more detailed definitions of Knowledge Discovery. This metamodel defines the basic abstractions of KDM and so was designed to be extended.

http://www.kdmanalytics.com/kdm/

Authors: Hugo Bruneliere (hugo.bruneliere gmail.com)

• Source file

Domains:

This metamodel describes KLAPER ((Kernel LAnguage for PErformance and Reliability analysis). It is a kernel language whose aim is to capture the relevant information for the analysis of non-functional attributes of component-based systems, with a focus on performance and reliability attributes, abstracting away unnecessary details.

http://delivery.acm.org/10.1145/1080000/1071024/p25-grassi.pdf?key1=1071024&key2=0400095511&coll=GUIDE&dl=&CFID=15151515&CFTOKEN=6184618

Authors: Youssef Srour (Srour.youssef_NOSPAM gmail.com)

• Source file

Domains: KM3 language

KM3, the Kernel MetaMetaModel, provides a textual concrete syntax that eases the coding of metamodels. Its syntax is simple, straight forward and has some similarities with the Java notation. KM3 resembles Ecore terminology and has the notion of package, class, attribute, reference and primitive datatype.

"KM3 User Manual", http://www.eclipse.org/gmt/atl/doc/

Authors: Fr�d�ric Jouault (frederic.jouault_NOSPAM univ-nantes.fr)