Knowledge Discovery Metamodel Article Index for
Knowledge 		Website Links For
Knowledge Discovery 		 

Information About

Knowledge Discovery Metamodel
  CATEGORIES ABOUT KNOWLEDGE DISCOVERY METAMODEL
   
software engineering
   
APPAREL
BABY
BEAUTY
BOOKS
CAR TOYS
CELL PHONES
DVD'S
ELECTRONICS
GOURMET FOOD
GROCERIES
HEALTH & PERSONAL
HOME & GARDEN
JEWELRY
MUSIC
MUSIC INSTRUMENTS
OFFICE PRODUCTS
SOFTWARE
SPORTING GOODS
TOOLS & HARDWARE
TOYS
VIDEO GAMES
SHOPPING HOME
MORE SHOPPING...




HISTORY OF KDM


  • In November 2003, the OMG's Architecture-Driven Modernization Task Force recommended, and the Platform Technical Committee issued, the Knowledge Discovery Metamodel (KDM) RFP. The objective of this RFP was to ''provide a common repository structure to represent information about existing software assets and their operating environment.'' The goal of KDM was defined as ''exchanging information related to transformation of existing software assets''. The RFP stated that KDM shall provide ''the ability to document existing systems, discover reusable components in existing software, support transformations to other languages and to MDA, or enable other potential transformations. The Knowledge Discovery Metamodel will also enable information about existing software artifacts to be exchanged among different tools. This will enable vendors that specialize on certain languages, platforms or types of transformations to deliver customer solutions in conjunction with other vendors.''



  • Throughout 2004 and 2005 12 companies collaborated to prepare a joint response to the KDM RFP. More than 30 organizations from 5 countries have contributed to the development and review of the KDM specification.


  • In May 2006, the Team's submission -- the Knowledge Discovery Metamodel (KDM) -- moved into the finalization stage of the OMG's standards adoption process. The OMG adopted Specification for KDM became publicly available (OMG document ptc/06-06-07).


  • In March 2007 the KDM Finalization Task Force finished the finalization stage of the OMG's standards adoption process. The recommended KDM specification KDM 1.0 is available from OMG ( document ptc/2007-03-15 ), and will soon become a formal standard.




OVERVIEW OF KDM

The goal of KDM is to ensure interoperability between tools for maintenance, evolution, assessment and modernization. KDM is defined as a Metamodel that can be also viewed as an Ontology for describing the key aspects of knowledge related to the various facets of enterprise software. KDM support means investment into the KDM ecosystem - a growing open-standard based cohesive community of tool vendors, service providers, and commercial components.

KDM represents entire enterprise software systems, not just code. KDM is a wide-spectrum Entity-relationship representation for describing existing software. KDM represents structural and behavior elements of existing software systems. The key concept of KDM is a ''container'': an entity that owns other entities. This allows KDM to represent existing systems at various degrees of granularity.

KDM defines precise semantic foundation for representing behavior, the so-called ''micro-KDM''. It provides a high-fidelity Intermediate Representation which can be used, for example, for performing static analysis of existing software systems. micro-KDM is similar in purpose to a Virtual Machine for KDM, although KDM is not an executable model, or a constraint model, but a representation of existing artifacts for analysis purposes.

KDM facilitates incremental analysis of existing software systems, where the initial KDM representation is analyzed and more pieces of knowledge are extracted and made explicit as KDM to KDM transformation performed entirely within the KDM technology space. The steps of the knowledge extraction process can be performed by tools, and may involve the analyst.

KDM is the uniform language- and platform- independent representation. Its extensibility mechanism allows addition of domain-, application- and implementation-specific knowledge.


ARCHITECTURE OF KDM


KDM packages are arranged into the following four layers:


Infrastructure Layer

The KDM Infrastructure Layer consists of the Core, '''kdm''', and '''Source''' packages which provide a small common core for all other packages, the inventory model of the artifacts of the existing system and full traceability between the meta-model elements as links back to the source code of the artifacts, as well as the uniform extensibility mechanism. The Core package determines several of patterns that are reused by other KDM packages. Although KDM is a meta-model that uses Meta-Object Facility , there is an alignment between the KDM Core and Resource Description Framework (RDF).


Program Elements Layer

The Program Elements Layer consists of the Code and Action packages.

  • The Code package represents programming elements as determined by programming languages, for example data types, procedures, classes, methods, variables, etc. This package is similar in purpose to the Common Application Meta-model (CAM) from another OMG specification, called Enterprise Application Integration (EAI). KDM Code package provides greater level of detail and is seamlessly integrated with the architecturally significant views of the software system. Representation of datatypes in KDM is aligned with ISO Standard ISO/IEC 11404 (see also General Purpose Datatypes ).


  • The Action package captures the low level behavior elements of applications, including detailed control- and data flow between statements. Code and Action package in combination provide a high-fidelity intermediate representation of each component of the enterprise software system



Resource Layer

The Resource Layer represents the operational environment of the existing software system. it is related to the area of Enterprise Application Integration (EAI).

  • Platform package represents the operating environment of the software, related to the operating system, middleware, etc. including the control flows between components as they are determined by the runtime platform


  • UI package represents the knowledge related to the user interfaces of the existing software system


  • Event package represents the knowledge related to events and state-transition behavior of the existing software system


  • Data package represents the artifacts related to persistent data, such as indexed files, relational databases, and other kinds of data storage. These assests are key to enterprise software as they represent the enterprise Metadata . The KDM Data package is aligned with another OMG specification, called Common Warehouse Metamodel (CWM)



Abstractions Layer

The Abstraction Layer represents domain and application abstractions.

  • Conceptual package represent business domain knowledge and business rules, insofar as this information can be mined from existing applications. These packages are aligned with another OMG specification, called Semantics Of Business Vocabulary And Rules (SBVR)


  • Structure package describes the meta-model elements for representing the logical organization of the software system into subsystems, layers and components


  • Build package represents the engineering view of the software system



SEE ALSO

Object Management Group


EXTERNAL LINKS


[http://www.omg.org/technology/documents/modernization_spec_catalog.htm KDM 1.0 specification]

Object Management Group (OMG)

Open KDM portal and tools from KDM Analytics

OMG Architecture-Driven Modernization Task Force

DSTC initial submission

SBVR link