Architecture-driven modernization: Difference between revisions

Content deleted Content added
+verygencat
No edit summary
Line 1:
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 extending the modeling approach to the existing software systems. Existing (or ''legacy'') software has been one of biggest obstacles for adoption of the modeling approach. With some irony, the acronym for Architecture-Driven Modernization, ADM looks like ''MDA in reverse'', where MDA is the acronym for OMG's Model-Driven Architecture, or using modeling to deliver new software. ADM is related to the concept of [[reverse engineering]]. [[software modernization|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>
 
== History of ADM ==