Architecture-driven modernization: Difference between revisions

Revision as of 20:22, 9 May 2018

Latest revision as of 15:07, 24 November 2022

(3 intermediate revisions by 3 users not shown)

Line 1:

{{Short description|Inititative of Object Management Group}}

{{Context|date=September 2009}}

'''Architecture-driven modernization''' in [[computing]] and [[computer science]], is the name of the initiative of the [[Object Management Group]] (see [http://adm.omg.org/ OMG ADM Task Force website]) related to building and promoting standards that can be applied to modernize [[legacy systems]]. The objective of this initiative is to provide standard representations of views of existing systems, in order to enable common [[software modernization|modernization activities]], such as code analysis and comprehension, and software transformation.

'''Architecture-driven modernization''' is the name of the initiative of the [[Object Management Group]] (see [http://adm.omg.org/ OMG ADM Task Force website]) related to building and promoting standards that can be applied to modernize [[legacy systems]]. The objective of this initiative is to provide standard representations of views of existing systems in order to enable common [[software modernization|modernization activities]], such as code analysis and comprehension, and software transformation.

== History ==

* In June 2003, The Object Management Group (OMG) formed a task force to modelingmodel in the context of existing software systems. Initially, the group was called Legacy Transformation Task Force, but then the name was unanimously changed to Architecture-Driven Modernization Task Force (ADMTF). ADMTF is co-chaired by Djenana Campara, from KDM Analytics and William Ulrich, from Tactical Strategy Group.<ref>{{cite book| title=Why do we need standards for the modernization of existing systems| url= http://www.kdmanalytics.com/kdm/ADM_whitepaper.pdf|publisher publisher= [[Object Management Group]]| date=July 15, 2003| access-date=May 9, 2007| archive-url=https://web.archive.org/web/20070928133101/http://www.kdmanalytics.com/kdm/ADM_whitepaper.pdf| archive-date=September 28, 2007| url-status=dead}}</ref>

* In November 2003, the OMG's Architecture-Driven Modernization Task Force recommended, and the Platform Technical Committee issued, the Knowledge Discovery Metamodel [[Request for proposal|Request For Proposal]] (RFP).

* In February 2005, the OMG's Architecture-Driven Modernization Task Force recommended, and the Platform Technical Committee issued, the Abstract Syntax Tree Metamodel (ASTM) Request For Proposal (RFP). This work is still in progress. OMG has not yet adopted this specification.

* In May 2006, the Team's submission—the Knowledge Discovery Metamodel—was adopted by the OMG and 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).

Line 13 ⟶ 12:

== Knowledge Discovery Metamodel (KDM) ==

The foundation of the architecture-driven modernization initiative is the OMG specification [[Knowledge Discovery Metamodel]] (KDM). Usually the knowledge obtained from existing software is presented in the form of models to which specific queries can be made when necessary. An [[entity relationship]] diagram is a frequent format of representing knowledge obtained from existing software. Knowledge Discovery Metamodel defines an ontology for the software assets and their relationships for the purpose of performing knowledge discovery of existing code. The KDM Analytics company maintains an open portal for the Knowledge Discovery Metamodel (see [http://www.kdmanalytics.com/kdm KDM Portal]).

The foundation of the architecture-driven modernization initiative is the OMG specification [[Knowledge Discovery Metamodel]] (KDM).

Usually the knowledge obtained from existing software is presented in the form of models to which specific queries can be made when necessary. An [[entity relationship]] diagram is a frequent format of representing knowledge obtained from existing software. Knowledge Discovery Metamodel defines an ontology for the software assets and their relationships for the purpose of performing knowledge discovery of existing code. The KDM Analytics company maintains an open portal for the Knowledge Discovery Metamodel (see [http://www.kdmanalytics.com/kdm KDM Portal]).

== Relationship to MDA ==

Existing (or ''legacy'') software has been one of the biggest obstacles for applying [[model-driven architecture]]. The acronym for architecture-driven modernization (ADM) is coincidentally ''MDA in reverse''. MDA is the acronym for OMG's model-driven architecture, which purports the use of models and transformations to deliver new software. ADM is related to the concept of [[reverse engineering]]. [[Software modernization]] is ''architecture-driven'' when there is the need to capture and retool various architectural aspects of existing application environments. This modernization does not preclude source-to-source migrations (where appropriate), but encourages user organizations to consider modernization from an analysis and design based perspective. In doing so, project teams will ensure that obsolete concepts or designs are not propagated into modern languages and platforms. The bottom-line results deliver modernized systems that conform more effectively to current business practices and strategic requirements.<ref>{{cite book |author=Object Management group | title=Second Architecture-Driven Modernization workshop | url= http://www.omg.org/news/releases/pr2005/08-30-05.htm |date=October 24, 2005 |access-date=May 9, 2007 |archive-url=https://web.archive.org/web/20070205161621/http://www.omg.org/news/releases/pr2005/08-30-05.htm |archive-date=February 5, 2007 |url-status=dead }}</ref>

== Vendors ==