 | This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Knowledge Discovery Metamodel" – news ·newspapers ·books ·scholar ·JSTOR(January 2021) (Learn how and when to remove this message) |
Knowledge Discovery Metamodel (KDM) is a publicly available specification from theObject Management Group (OMG). KDM is a commonintermediate representation for existing software systems and their operating environments, that defines commonmetadata required for deepsemantic integration ofApplication Lifecycle Management tools. KDM was designed as the OMG's foundation forsoftware modernization, IT portfolio management and software assurance. KDM uses OMG'sMeta-Object Facility to define anXMI interchange format between tools that work with existing software as well as an abstract interface (API) for the next-generation assurance and modernization tools. KDM standardizes existing approaches toknowledge discovery in software engineering artifacts, also known assoftware mining.
The goal of KDM is to ensure interoperability between tools for maintenance, evolution, assessment and modernization. KDM is defined as ametamodel that can be also viewed as anontology 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-spectrumentity-relationship representation for describing existing software. KDM represents structural and behavior elements of existing software systems. The key concept of KDM is acontainer: 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-calledmicro-KDM. It provides a high-fidelityintermediate representation which can be used, for example, for performing static analysis of existing software systems. micro-KDM is similar in purpose to avirtual 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.
KDM packages are arranged into the following four layers:
The KDM Infrastructure Layer consists of theCore,kdm, andSource 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 the patterns that are reused by other KDM packages. Although KDM is a meta-model that usesMeta-Object Facility, there is an alignment between the KDM Core andResource Description Framework (RDF).
The Program Elements Layer consists of the Code and Action packages.
The Resource Layer represents the operational environment of the existing software system. It is related to the area ofEnterprise Application Integration (EAI).
The Abstraction Layer represents domain and application abstractions.
