Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

MoDisco/KDM

< MoDisco
Revision as of 09:06, 13 February 2009 by Unnamed Poltroon (Talk)

Knowledge Discovery Metamodel (KDM) is a publicly available specification from the Object Management Group (OMG). KDM is a common intermediate representation for existing software systems and their operating environments, that defines common metadata required for deep semantic integration of Application Lifecycle Management tools. KDM is designed as the OMG's foundation for software modernization, IT portfolio management and software assurance. KDM is a metamodel for knowledge discovery in software. It defines a common vocabulary of knowledge related to software engineering artifacts, regardless of the implementation programming language and runtime platform - a checklist of items that a software mining tool should discover and a software analysis tool can use. KDM is designed to enable knowledge-based integration between tools. More specifically, KDM uses Meta-Object Facility (MOF) to define an interchange format between tools that work with existing software as well as an abstract interface (API) for the next-generation assurance and modernization tools.

See more on dedicated web site : OMG KDM

Requirements

To use the plug-in you need:

  • JDK 1.5 or above
  • a version of Eclipse 3.3 or above with the following set of plugins installed
  • EMF 2.3.0 or higher


Install

You will find a version of this plug-in attached in following bug.

As IP review of this plugin is not finished, here is installation instructions :

  • Extract archive file in your Eclipse workspace, then use "import" menu to import this project.
  • Use "export" menu to export this project as a plugin (Deployable plugins and fragments) in your Eclipse installation. Don't forget to choose "Package plug-ins as individual jar archives" option.
  • re-start your Eclipse to take in account this plug-in

Back to the top