Architecture Driven Modernization - Revision history

User at 10:34, 16 March 2024

2024-03-16T10:34:48Z

User at 09:40, 16 March 2024

2024-03-16T09:40:35Z

User at 15:12, 21 February 2023

2023-02-21T15:12:45Z

User at 11:46, 17 January 2023

2023-01-17T11:46:24Z

User at 18:16, 21 November 2022

2022-11-21T18:16:22Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T13:50:45Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 16:13, 29 May 2020

2020-05-29T16:13:46Z

User: Architecture Driven Modernization is the name of the initiative of the Object Management Group related to building and promoting standards that can be applied to modernize legacy systems.

2018-12-03T23:29:59Z

Architecture Driven Modernization is the name of the initiative of the Object Management Group related to building and promoting standards that can be applied to modernize legacy systems.

User: Created page with "'''Content Coming Soon'''"

2018-12-03T16:10:03Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

← Older revision		Revision as of 10:34, 16 March 2024
Line 51:		Line 51:

	==See Also==		==See Also==
		+	Architecture Driven Modernization (ADM) is the process of understanding and evolving existing software systems into modern environments using model-driven approaches based on the architecture of these systems. It aims to improve software systems' structure, technology stack, and functionalities while preserving their essential features and minimizing disruption to business operations. ADM focuses on leveraging the best practices in software architecture to guide the modernization process, ensuring that systems are more adaptable, scalable, and aligned with current and future business needs. To gain a comprehensive understanding of ADM and its critical aspects, including methodologies, tools, and strategies for effective modernization, exploring the following topics is highly beneficial:
		+
		+	*[[Software Architecture]] and Design Principles: Examines the fundamental principles of software architecture and design, including modularity, separation of concerns, and architectural patterns, which are crucial for planning modernization projects.
		+	*[[Model Driven Engineering (MDE)]]: Discusses using models as the primary means of information exchange during the software development process, a core aspect of ADM, facilitating the understanding and transformation of legacy systems.
		+	*[[Legacy Systems]] Assessment and Analysis: Covers methods for evaluating existing systems to identify their strengths, weaknesses, and areas for improvement, including static and dynamic analysis techniques.
		+	*Refactoring and Reengineering: Explores strategies for improving software's internal structure and design without altering its external behavior, which is essential for incrementally modernizing systems.
		+	*Technology Migration and Platform Modernization: Discusses the process of moving legacy systems to newer, more efficient platforms or technologies, including cloud migration, service-oriented architecture (SOA) adoption, and microservices.
		+	*Database Modernization: Addresses the challenges and strategies for updating legacy databases to enhance performance, scalability, and integration with modern applications and services.
		+	*Software Quality Assurance for Modernized Systems: Covers the methods and practices for ensuring that modernized systems meet specified requirements and quality standards, including testing strategies, performance evaluation, and compliance checks.
		+	*Integration of Emerging Technologies: Explores how emerging technologies such as cloud computing, artificial intelligence (AI), and the Internet of Things (IoT) can be integrated into modernized systems to enhance capabilities and address new business requirements.
		+	*[[Enterprise Architecture Framework\|Enterprise Architecture Frameworks]]: Discusses the role of enterprise architecture frameworks, such as TOGAF and Zachman, in guiding the modernization process, ensuring alignment between IT strategy and business goals.
		+	*[[Change Management]] and Governance: Addresses the organizational aspects of modernization projects, including managing stakeholder expectations, governance structures, and the cultural change required to embrace modernized systems.
		+	*Security Considerations in Modernization: Highlights the importance of incorporating security considerations into the modernization process, ensuring that updated systems are protected against current and emerging threats.
		+	*Case Studies and Best Practices: Reviews real-world examples of successful ADM projects, drawing lessons on effective practices, common pitfalls, and strategies for overcoming challenges.
		+	*Tool Support for ADM: Explores the tools and technologies available to support various stages of the ADM process, from analysis and modeling to transformation and deployment.
		+
		+	Delving into these topics provides a rich foundation for understanding Architecture-Driven Modernization, which emphasizes a structured and strategic approach to upgrading legacy systems. This exploration highlights the methodologies and technologies involved and addresses the organizational and cultural aspects critical to the success of modernization efforts.
	*[[Knowledge Discovery Metamodel (KDM)]]		*[[Knowledge Discovery Metamodel (KDM)]]

@@ Line 1: / Line 1: @@
 == What is Architecture Driven Modernization? ==
-'''Architecture Driven Modernization''' is the name of the initiative of the Object Management Group 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>[https://en.wikipedia.org/wiki/Architecture-driven_modernization Defining Architecture Driven Modernization]</ref>
+'''Architecture Driven Modernization''' is the name of the initiative of the [[Object Management Group (OMG)]] 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>[https://en.wikipedia.org/wiki/Architecture-driven_modernization Defining Architecture Driven Modernization]</ref>
 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 (KDM) defines an ontology for the software assets and their relationships for the purpose of performing knowledge discovery of existing code. <ref>[https://en.wikipedia.org/wiki/Architecture-driven_modernization Architecture Driven Modernization KDM]</ref>

@@ Line 1: / Line 1: @@
 == What is Architecture Driven Modernization? ==
-'''Architecture Driven Modernization''' is the name of the initiative of the Object Management Group 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>[https://en.wikipedia.org/wiki/Architecture-driven_modernization DefiningArchitecture Driven Modernization]</ref>
+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 (KDM) defines an ontology for the software assets and their relationships for the purpose of performing knowledge discovery of existing code. <ref>[https://en.wikipedia.org/wiki/Architecture-driven_modernization Architecture Driven Modernization KDM]</ref>
+Architecture-Driven Modernization is the process of understanding and evolving existing software assets for the purpose of software improvement, modifications, interoperability, refactoring, restructuring, reuse, porting, migration, language translation, enterprise application integration, SOA, and MDA migration.<ref>[http://adm.omg.org/ Architecture Driven Modernization - Mission]</ref>
 [[File:Architecturedrivenmodernization.png|500px|Architecture Driven Modernization]]<br />
-source: [http://www.tsri.com/files/BM%20TSRI%20Ask%20The%20Expert.pdf TSRI]
+source: TSRI
-Using architecture-driven modernization, many huge and complex mission critical information systems, whose modernization could not have been attempted just a few years ago, can now be modernized affordably and in astonishingly shortened time frames. Due to significantly improved hardware capacity and new technology innovations, information system transformation is now being applied routinely on an unprecedented scale using repeatable, perfective, adaptive processes in conformance with OMG best practices. Automated modernization has become a proven commodity. Architecture driven modernization plays a strategic role in building agility and competitive advantage for a growing number of organizations and industries.The realization is dawning that modernization should no longer be regarded as a one-time fix to deal with a one-time legacy problem. To ensure IT infrastructures are perpetually agile and support rapid enactment of business strategies, organizations are learning they must adopt continuous modernization as a vehicle for future competitiveness. Applying modernization options to existing software systems is no longer a tactical luxury or last gasp measure. For many organizations continuous modernization is now an essential and strategic necessity for competitive survival. Architecture-driven modernization has emerged just in time to provide enterprises with a wide variety of options for understanding, evolving and ultimately transforming critical software assets.While modernization has long been regarded as a cost to be avoided, the advent of architecture driven-modernization creates a vast array of new options for executives considering the best way to revitalize their IT architectures.<ref>Architecture Driven Enterprise Modernization [http://www.tsri.com/files/BM%20TSRI%20Ask%20The%20Expert.pdf tsri.com]</ref>
+Using architecture-driven modernization, many huge and complex mission-critical information systems, whose modernization could not have been attempted just a few years ago, can now be modernized affordably and in astonishingly shortened time frames. Due to significantly improved hardware capacity and new technology innovations, information system transformation is now being applied routinely on an unprecedented scale using repeatable, perfective, adaptive processes in conformance with OMG best practices. Automated modernization has become a proven commodity. Architecture driven modernization plays a strategic role in building agility and competitive advantage for a growing number of organizations and industries. The realization is dawning that modernization should no longer be regarded as a one-time fix to deal with a one-time legacy problem. To ensure IT infrastructures are perpetually agile and support the rapid enactment of business strategies, organizations are learning they must adopt continuous modernization as a vehicle for future competitiveness. Applying modernization options to existing software systems is no longer a tactical luxury or last-gasp measure. For many organizations, continuous modernization is now an essential and strategic necessity for competitive survival. Architecture-driven modernization has emerged just in time to provide enterprises with a wide variety of options for understanding, evolving, and ultimately transforming critical software assets. While modernization has long been regarded as a cost to be avoided, the advent of architecture driven-modernization creates a vast array of new options for executives considering the best way to revitalize their IT architectures.
-'''Essential Principles of Architecture Driven Modernization (ADM)'''<ref>Essential Principles of Architecture Driven Modernization (ADM) [https://delta-software.com/en/our-offer/services/documentation/amelio-modernization-platform/send/14-amelio-modernization-platform/76-architecture-driven-modernization-goals-concepts-benefits.html delta software]</ref><br />
+== Essential Principles of Architecture Driven Modernization (ADM)<ref>[https://delta-software.com/en/our-offer/services/documentation/amelio-modernization-platform/send/14-amelio-modernization-platform/76-architecture-driven-modernization-goals-concepts-benefits.html Essential Principles of Architecture Driven Modernization (ADM)]</ref> ==
-*1.Model-based :
+#Model-based:
-**All information on the artefacts to be processed are stored in standardized models. This also applies to derived knowledge
+#*All information on the artefacts to be processed is stored in standardized models. This also applies to derived knowledge
-**Using MOF and XML (XMI) as the conceptual and technical base reduces the tool-dependency and allows third-party products to be used
+#*Using MOF and XML (XMI) as the conceptual and technical base reduces the tool dependency and allows third-party products to be used
-**It is only by defining meta-models that the use of automated discovery and analysis tools really becomes reasonable
+#*It is only by defining meta-models that the use of automated discovery and analysis tools really becomes reasonable
-*2. Abstraction and platform-independency
+#Abstraction and platform-independency
-**Primary sources are just the starting point for the population of the models that are to serve as the basis for all subsequent operations
+#*Primary sources are just the starting point for the population of the models that are to serve as the basis for all subsequent operations
-**Wherever possible, the derived knowledge is a
+#*Wherever possible, the derived knowledge is a
-*3. PSM-PIM-PSM transformation
+#PSM-PIM-PSM transformation
-**This method has proved its value for all cases in which modernization deals with the creation or modification of software (migration, transformation, integration)
+#*This method has proved its value for all cases in which modernization deals with the creation or modification of software (migration, transformation, integration)
-**The significantly reduced complexity associated with this method increases transparency, reduces the error rate and therefore leads to higher efficiency
+#*The significantly reduced complexity associated with this method increases transparency, reduces the error rate and therefore leads to higher efficiency
-**By the way, using this method makes platform decisions less crucial because changing the definition of the target platform is rather easy
+#*By the way, using this method makes platform decisions less crucial because changing the definition of the target platform is rather easy
-*4. Target-oriented and selective
+#Target-oriented and selective
-**"The more the better” surely does not apply to the effective support of modernization measures
+#*"The more the better” surely does not apply to the effective support of modernization measures
-**Meta-data are to be collected and analyzed as target-oriented as possible
+#*Meta-data are to be collected and analyzed as target-oriented as possible
-*5. Adaptive “Factory”
+#Adaptive “Factory”
-**Modernization tasks are so diverse that there is no out-of-the-box “all singing and dancing” solution
+#*Modernization tasks are so diverse that there is no out-of-the-box “all singing and dancing” solution
-**Likewise, you cannot expect a specific tool for each modernization scenario
+#*Likewise, you cannot expect a specific tool for each modernization scenario
-**What is really needed are tool components that are based on one common model and that can be assembled into a specific modernization factory
+#*What is really needed are tool components that are based on one common model and that can be assembled into a specific modernization factory
-'''Benefits of Using Architecture Driven Modernization (ADM)'''<ref>Benefits of Using Architecture Driven Modernization (ADM) [http://www.ijser.org/researchpaper%5CA-REVIEW-ON-ARCHITECTURE-DRIVEN-MODERNIZATION-ADM.pdf ijser.org]</ref><br />
+== Benefits of Using Architecture Driven Modernization (ADM)<ref>[http://www.ijser.org/researchpaper%5CA-REVIEW-ON-ARCHITECTURE-DRIVEN-MODERNIZATION-ADM.pdf Benefits of Using Architecture Driven Modernization (ADM)]</ref> ==
-*Enabling business agility by creating software agility<br />
+*Enabling business agility by creating software agility
-*Improving ROI in existing software<br />
+*Improving ROI in existing software
 **Improving productivity of software development
 **Reducing maintenance effort and cost
-*Interoperability <br />
+*Interoperability
-*Adoption of new technologies, Practices and paradigms <br />
+*Adoption of new technologies, Practices, and paradigms
-*Modernization is done on the basis of prior experiences and best practices<br />
+*Modernization is done on the basis of prior experiences and best practices
-*Standardization in modernization can lead to<br />
+*Standardization in modernization can lead to
-**Integration and interoperability between different vendors and tools by creating open framework
+**Integration and interoperability between different vendors and tools by creating an open framework
 **Encourage collaboration among complementary vendors
 **End users will get better operational cost
-*Reduces the time, cost and risk of software transformations
+*Reduces the time, cost, and risk of software transformations
-===References===
+==References==
 <references />
 ===Further Reading===
-*Architecture-Driven Modernization 101:Concepts, Strategies & Justification Concepts, Strategies & Justification [http://www.omg.org/news/meetings/workshops/ADM_2005_Proceedings_FINAL/T-1_Ulrich.pdf omg.org]
+*[http://www.omg.org/news/meetings/workshops/ADM_2005_Proceedings_FINAL/T-1_Ulrich.pdf Architecture-Driven Modernization 101: Concepts, Strategies & Justification Concepts, Strategies & Justification]
-*How Architecture Driven Modernization Is Changing the Game in Information System Modernization [http://www.dtic.mil/dtic/tr/fulltext/u2/a558512.pdf DTIC]
+*[http://www.dtic.mil/dtic/tr/fulltext/u2/a558512.pdf How Architecture Driven Modernization Is Changing the Game in Information System Modernization]

@@ Line 1: / Line 1: @@
 '''Architecture Driven Modernization''' is the name of the initiative of the Object Management Group 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>[https://en.wikipedia.org/wiki/Architecture-driven_modernization DefiningArchitecture Driven Modernization]</ref>
-The foundation of the architecture-driven modernization initiative is the OMG specification [[Knowledge_Discovery_Metamodel_(KDM)|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_(KDM)|Knowledge Discovery Metamodel (KDM)]] defines an [[ontology]] for the software assets and their relationships for the purpose of performing knowledge discovery of existing code. <ref>Architecture Driven Modernization KDM [https://en.wikipedia.org/wiki/Architecture-driven_modernization Wikipedia]</ref>
+The foundation of the architecture-driven modernization initiative is the OMG specification [[Knowledge_Discovery_Metamodel_(KDM)|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 (KDM) defines an [[ontology]] for the software assets and their relationships for the purpose of performing knowledge discovery of existing code. <ref>Architecture Driven Modernization KDM [https://en.wikipedia.org/wiki/Architecture-driven_modernization Wikipedia]</ref>
-Architecture-Driven Modernization is the [[process]] of understanding and evolving existing software assets for the purpose of software [[improvement]], modifications, [[interoperability]], refactoring, [[restructuring]], reuse, porting, migration, language translation, enterprise [[application]] integration, SOA, and MDA migration.<ref>Architecture Driven Modernization - [[Mission]] [http://adm.omg.org/ OMG]</ref>
+Architecture-Driven Modernization is the process of understanding and evolving existing software assets for the purpose of software improvement, modifications, [[interoperability]], refactoring, restructuring, reuse, porting, migration, language translation, enterprise application integration, SOA, and MDA migration.<ref>Architecture Driven Modernization - Mission [http://adm.omg.org/ OMG]</ref>
@@ Line 12: / Line 14: @@
-Using architecture-driven modernization, many huge and complex mission critical information systems, whose modernization could not have been attempted just a few years ago, can now be modernized affordably and in astonishingly shortened time frames. Due to significantly improved [[hardware]] capacity and new technology innovations, information [[system]] transformation is now being applied routinely on an unprecedented scale using repeatable, perfective, adaptive processes in conformance with OMG best practices. Automated modernization has become a proven commodity. Architecture driven modernization plays a strategic role in building [[agility]] and competitive advantage for a growing number of organizations and industries.The realization is dawning that modernization should no longer be regarded as a one-time fix to deal with a one-time legacy problem. To ensure IT infrastructures are perpetually agile and support rapid enactment of [[business]] strategies, organizations are learning they must adopt continuous modernization as a vehicle for future competitiveness. Applying modernization options to existing software systems is no longer a tactical luxury or last gasp measure. For many organizations continuous modernization is now an essential and strategic necessity for competitive survival. Architecture-driven modernization has emerged just in time to provide enterprises with a wide variety of options for understanding, evolving and ultimately transforming critical software assets.While modernization has long been regarded as a cost to be avoided, the advent of architecture driven-modernization creates a vast array of new options for executives considering the best way to revitalize their IT architectures.<ref>Architecture Driven Enterprise Modernization [http://www.tsri.com/files/BM%20TSRI%20Ask%20The%20Expert.pdf tsri.com]</ref>
+Using architecture-driven modernization, many huge and complex mission critical information systems, whose modernization could not have been attempted just a few years ago, can now be modernized affordably and in astonishingly shortened time frames. Due to significantly improved hardware capacity and new technology innovations, information system transformation is now being applied routinely on an unprecedented scale using repeatable, perfective, adaptive processes in conformance with OMG best practices. Automated modernization has become a proven commodity. Architecture driven modernization plays a strategic role in building agility and competitive advantage for a growing number of organizations and industries.The realization is dawning that modernization should no longer be regarded as a one-time fix to deal with a one-time legacy problem. To ensure IT infrastructures are perpetually agile and support rapid enactment of business strategies, organizations are learning they must adopt continuous modernization as a vehicle for future competitiveness. Applying modernization options to existing software systems is no longer a tactical luxury or last gasp measure. For many organizations continuous modernization is now an essential and strategic necessity for competitive survival. Architecture-driven modernization has emerged just in time to provide enterprises with a wide variety of options for understanding, evolving and ultimately transforming critical software assets.While modernization has long been regarded as a cost to be avoided, the advent of architecture driven-modernization creates a vast array of new options for executives considering the best way to revitalize their IT architectures.<ref>Architecture Driven Enterprise Modernization [http://www.tsri.com/files/BM%20TSRI%20Ask%20The%20Expert.pdf tsri.com]</ref>
@@ Line 24: / Line 26: @@
 **Wherever possible, the derived knowledge is a
 *3. PSM-PIM-PSM transformation
-**This method has proved its [[value]] for all cases in which modernization deals with the creation or modification of software (migration, transformation, integration)
+**This method has proved its value for all cases in which modernization deals with the creation or modification of software (migration, transformation, integration)
-**The significantly reduced complexity associated with this method increases transparency, reduces the error rate and therefore leads to higher [[efficiency]]
+**The significantly reduced complexity associated with this method increases transparency, reduces the error rate and therefore leads to higher efficiency
-**By the way, using this method makes platform decisions less crucial because changing the definition of the [[target]] platform is rather easy
+**By the way, using this method makes platform decisions less crucial because changing the definition of the target platform is rather easy
 *4. Target-oriented and selective
 **"The more the better” surely does not apply to the effective support of modernization measures
-**Meta-[[data]] are to be collected and analyzed as target-oriented as possible
+**Meta-data are to be collected and analyzed as target-oriented as possible
 *5. Adaptive “Factory”
 **Modernization tasks are so diverse that there is no out-of-the-box “all singing and dancing” solution
 **Likewise, you cannot expect a specific tool for each modernization scenario
-**What is really needed are tool components that are based on one common [[model]] and that can be assembled into a specific modernization factory
+**What is really needed are tool components that are based on one common model and that can be assembled into a specific modernization factory
@@ Line 39: / Line 41: @@
 *Enabling business agility by creating software agility<br />
 *Improving ROI in existing software<br />
-**Improving [[productivity]] of software development
+**Improving productivity of software development
 **Reducing maintenance effort and cost
 *Interoperability <br />
@@ Line 45: / Line 47: @@
 *Modernization is done on the basis of prior experiences and best practices<br />
 *Standardization in modernization can lead to<br />
-**Integration and interoperability between different vendors and tools by creating open [[framework]]
+**Integration and interoperability between different vendors and tools by creating open framework
-**Encourage [[collaboration]] among complementary vendors
+**Encourage collaboration among complementary vendors
 **End users will get better operational cost
-*Reduces the time, cost and [[risk]] of software transformations
+*Reduces the time, cost and risk of software transformations
 ===See Also===
-[[Architectural_Risk|Architectural Risk]]<br />
-[[Architectural_Pattern|Architectural Pattern]]<br />
-[[Architectural_Principles|Architectural Principles]]<br />
-[[Architecture|Architecture]]<br />

← Older revision		Revision as of 18:16, 21 November 2022
Line 1:		Line 1:
−	'''[[Architecture]] Driven Modernization''' is the name of the initiative of the Object [[Management]] Group 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 modernization activities, such as code analysis and comprehension, and [[software]] transformation. <ref>~~Architecture Driven Modernization Definition~~ [https://en.wikipedia.org/wiki/Architecture-driven_modernization ~~Wikipedia~~]</ref>	+	'''Architecture Driven Modernization''' is the name of the initiative of the Object Management Group 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>[https://en.wikipedia.org/wiki/Architecture-driven_modernization DefiningArchitecture Driven Modernization]</ref>

← Older revision		Revision as of 16:13, 29 May 2020
Line 1:		Line 1:
−	Architecture Driven Modernization is the name of the initiative of the Object Management Group 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>Architecture Driven Modernization Definition [https://en.wikipedia.org/wiki/Architecture-driven_modernization Wikipedia]</ref>	+	'''Architecture Driven Modernization''' is the name of the initiative of the Object Management Group 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>Architecture Driven Modernization Definition [https://en.wikipedia.org/wiki/Architecture-driven_modernization Wikipedia]</ref>

← Older revision		Revision as of 23:29, 3 December 2018
Line 1:		Line 1:
−	'''~~Content Coming Soon~~'''	+	Architecture Driven Modernization is the name of the initiative of the Object Management Group 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 modernization activities, such as code analysis and comprehension, and software transformation. <ref>Architecture Driven Modernization Definition [https://en.wikipedia.org/wiki/Architecture-driven_modernization Wikipedia]</ref>
		+
		+
		+	The foundation of the architecture-driven modernization initiative is the OMG specification [[Knowledge_Discovery_Metamodel_(KDM)\|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_(KDM)\|Knowledge Discovery Metamodel (KDM)]] defines an ontology for the software assets and their relationships for the purpose of performing knowledge discovery of existing code. <ref>Architecture Driven Modernization KDM [https://en.wikipedia.org/wiki/Architecture-driven_modernization Wikipedia]</ref>
		+
		+
		+	Architecture-Driven Modernization is the process of understanding and evolving existing software assets for the purpose of software improvement, modifications, interoperability, refactoring, restructuring, reuse, porting, migration, language translation, enterprise application integration, SOA, and MDA migration.<ref>Architecture Driven Modernization - Mission [http://adm.omg.org/ OMG]</ref>
		+
		+
		+	[[File:Architecturedrivenmodernization.png\|500px\|Architecture Driven Modernization]]<br />
		+	source: [http://www.tsri.com/files/BM%20TSRI%20Ask%20The%20Expert.pdf TSRI]
		+
		+
		+	Using architecture-driven modernization, many huge and complex mission critical information systems, whose modernization could not have been attempted just a few years ago, can now be modernized affordably and in astonishingly shortened time frames. Due to significantly improved hardware capacity and new technology innovations, information system transformation is now being applied routinely on an unprecedented scale using repeatable, perfective, adaptive processes in conformance with OMG best practices. Automated modernization has become a proven commodity. Architecture driven modernization plays a strategic role in building agility and competitive advantage for a growing number of organizations and industries.The realization is dawning that modernization should no longer be regarded as a one-time fix to deal with a one-time legacy problem. To ensure IT infrastructures are perpetually agile and support rapid enactment of business strategies, organizations are learning they must adopt continuous modernization as a vehicle for future competitiveness. Applying modernization options to existing software systems is no longer a tactical luxury or last gasp measure. For many organizations continuous modernization is now an essential and strategic necessity for competitive survival. Architecture-driven modernization has emerged just in time to provide enterprises with a wide variety of options for understanding, evolving and ultimately transforming critical software assets.While modernization has long been regarded as a cost to be avoided, the advent of architecture driven-modernization creates a vast array of new options for executives considering the best way to revitalize their IT architectures.<ref>Architecture Driven Enterprise Modernization [http://www.tsri.com/files/BM%20TSRI%20Ask%20The%20Expert.pdf tsri.com]</ref>
		+
		+
		+	'''Essential Principles of Architecture Driven Modernization (ADM)'''<ref>Essential Principles of Architecture Driven Modernization (ADM) [https://delta-software.com/en/our-offer/services/documentation/amelio-modernization-platform/send/14-amelio-modernization-platform/76-architecture-driven-modernization-goals-concepts-benefits.html delta software]</ref><br />
		+	*1.Model-based :
		+	**All information on the artefacts to be processed are stored in standardized models. This also applies to derived knowledge
		+	**Using MOF and XML (XMI) as the conceptual and technical base reduces the tool-dependency and allows third-party products to be used
		+	**It is only by defining meta-models that the use of automated discovery and analysis tools really becomes reasonable
		+	*2. Abstraction and platform-independency
		+	**Primary sources are just the starting point for the population of the models that are to serve as the basis for all subsequent operations
		+	**Wherever possible, the derived knowledge is a
		+	*3. PSM-PIM-PSM transformation
		+	**This method has proved its value for all cases in which modernization deals with the creation or modification of software (migration, transformation, integration)
		+	**The significantly reduced complexity associated with this method increases transparency, reduces the error rate and therefore leads to higher efficiency
		+	**By the way, using this method makes platform decisions less crucial because changing the definition of the target platform is rather easy
		+	*4. Target-oriented and selective
		+	**"The more the better” surely does not apply to the effective support of modernization measures
		+	**Meta-data are to be collected and analyzed as target-oriented as possible
		+	*5. Adaptive “Factory”
		+	**Modernization tasks are so diverse that there is no out-of-the-box “all singing and dancing” solution
		+	**Likewise, you cannot expect a specific tool for each modernization scenario
		+	**What is really needed are tool components that are based on one common model and that can be assembled into a specific modernization factory
		+
		+
		+	'''Benefits of Using Architecture Driven Modernization (ADM)'''<ref>Benefits of Using Architecture Driven Modernization (ADM) [http://www.ijser.org/researchpaper%5CA-REVIEW-ON-ARCHITECTURE-DRIVEN-MODERNIZATION-ADM.pdf ijser.org]</ref><br />
		+	*Enabling business agility by creating software agility<br />
		+	*Improving ROI in existing software<br />
		+	**Improving productivity of software development
		+	**Reducing maintenance effort and cost
		+	*Interoperability <br />
		+	*Adoption of new technologies, Practices and paradigms <br />
		+	*Modernization is done on the basis of prior experiences and best practices<br />
		+	*Standardization in modernization can lead to<br />
		+	**Integration and interoperability between different vendors and tools by creating open framework
		+	**Encourage collaboration among complementary vendors
		+	**End users will get better operational cost
		+	*Reduces the time, cost and risk of software transformations
		+
		+
		+	===See Also===
		+	[[Architectural_Risk\|Architectural Risk]]<br />
		+	[[Architectural_Pattern\|Architectural Pattern]]<br />
		+	[[Architectural_Principles\|Architectural Principles]]<br />
		+	[[Architecture\|Architecture]]<br />
		+	[[Architecture_Description_Language_(ADL)\|Architecture Description Language (ADL)]]<br />
		+	[[Architecture_Development_Method_(ADM)\|Architecture Development Method (ADM)]]<br />
		+	[[Service_Oriented_Architecture_(SOA)\|Service Oriented Architecture (SOA)]]<br />
		+	[[Software_Architecture\|Software Architecture]]<br />
		+	[[The_Open_Group_Architecture_Framework_(TOGAF)\|The Open Group Architecture Framework (TOGAF)]]<br />
		+	[[Design_Pattern\|Design Pattern]]<br />
		+	[[Enterprise_Architecture\|Enterprise Architecture]]<br />
		+	[[Adaptive_Enterprise_Framework_(AEF)\|Adaptive Enterprise Framework (AEF)]]<br />
		+	[[Architectural_Style\|Architectural Style]]
		+
		+
		+	===References===
		+	<references />
		+
		+
		+	===Further Reading===
		+	*Architecture-Driven Modernization 101:Concepts, Strategies & Justification Concepts, Strategies & Justification [http://www.omg.org/news/meetings/workshops/ADM_2005_Proceedings_FINAL/T-1_Ulrich.pdf omg.org]
		+	*How Architecture Driven Modernization Is Changing the Game in Information System Modernization [http://www.dtic.mil/dtic/tr/fulltext/u2/a558512.pdf DTIC]