Architecture-driven modernization: Difference between revisions

Revision as of 14:51, 15 November 2011

Revision as of 14:53, 15 November 2011

Line 1:

{{Context|date=September 2009}}

Architecture-Drivendriven Modernizationmodernization 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 existing systems in order to enable common [[software modernization|modernization activities]] like code analysis and comprehension, and software transformation.

== History of ADM ==

* In June 2003, The Object Management Group (OMG) formed a Tasktask Forceforce to modeling 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 (ADM). ADMTF is co-chaired by Djenana Campara, from KDM Analytics and William Ulrich, from Tactical Strategy Group.<ref>{{cite book| author=Object management Group| title=Why do we need standards for the modernization of existing systems| url= http://www.kdmanalytics.com/kdm/ADM_whitepaper.pdf|[[Object Management Group]]|date=July 15, 2003}}</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 (RFP).

Line 18:

== Knowledge Discovery Metamodel (KDM) ==

The foundation of the Architecturearchitecture-Drivendriven Modernizationmodernization 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]] 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. Company KDM Analytics is maintaining 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 biggest obstacles for adoption of a [[Modelmodel-driven architecture]]. With some irony, the acronym for Architecturearchitecture-Drivendriven Modernizationmodernization, ADM looks like ''MDA in reverse'', where MDA is the acronym for OMG's Modelmodel-Drivendriven Architecturearchitecture, or using modeling 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 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}}</ref>

Line 29:

* [[Object Management Group]]

* [[software modernization]]

* [[Reverse Engineeringengineering]]

* [[software mining]]

* [[Software Metrics Metamodel]]