Architecture-driven modernization: Difference between revisions

Revision as of 20:22, 9 May 2018

Revision as of 06:46, 2 October 2019

Line 4:

== History ==

* In June 2003, The Object Management Group (OMG) formed a task force 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 (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 (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.

Line 17:

== Relationship to MDA ==

Existing (or ''legacy'') software has been one of 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 ==