Architected, Model-Driven Development (AMD) - Revision history

User at 09:48, 17 January 2023

2023-01-17T09:48:47Z

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

2021-02-06T13:49:32Z

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

User at 16:09, 29 May 2020

2020-05-29T16:09:17Z

User: Architected, Model-Driven Development (AMD) is the most sophisticated end of the SOA modeling spectrum. It focuses on quality, performance and reuse. It comes in two “flavors”: AMD composition and AMD development.

2018-12-03T19:36:59Z

Architected, Model-Driven Development (AMD) is the most sophisticated end of the SOA modeling spectrum. It focuses on quality, performance and reuse. It comes in two “flavors”: AMD composition and AMD development.

New page

AMD is the most sophisticated end of the SOA modeling spectrum. It focuses on quality, performance and reuse. It comes in two “flavors”: AMD composition and AMD development. AMD composition presumes that the needed services exist and can be “assembled” into an application (business service), possibly with a new user interface (generally portal-based, using Web services). Organizations can generally use AMD composition models to generate the specifications for use by workflow orchestration technologies in the runtime environment. AMD development assumes that new organizations need to develop software services prior to composition. AMD development tools can reuse the same business models developed by those doing AMD composition. But, generally, IT personnel refine these into more detailed models to generate as much of the code as possible ― 70% to 100% ― depending on the service type. AMD also includes the set of methods that promote “executable” models (that is, where there is no explicit transformation to implementation).<ref>Definition - What does Architected model-driven development (AMD) mean? [https://www.gartner.com/it-glossary/amd-architected-model-driven-development Gartner]</ref>

===References===
<references/>

===Further Reading===
*Next-generation model-driven development [https://www.omg.org/mda/mda_files/GC34-2485-03_LoRes.pdf IBM]
*Model-Driven Architecture: Vision, Standards And Emerging Technologies [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.484.9121&rep=rep1&type=pdf John D Poole]

@@ Line 1: / Line 1: @@
-'''Architected, [[Model]]-Driven Development''' or '''AMD''' is the most sophisticated end of the [[Service Oriented Architecture (SOA)|SOA]] modeling spectrum. It focuses on [[quality]], performance and reuse. It comes in two “flavors”: AMD composition and AMD development. AMD composition presumes that the needed services exist and can be “assembled” into an [[Application|application]] ([[business]] [[service]]), possibly with a new user interface (generally portal-based, using Web services).[[Organization|Organizations]] can generally use AMD composition models to generate the specifications for use by [[Workflow|workflow]] [[orchestration]] technologies in the runtime environment. AMD development assumes that new organizations need to develop [[Software|software]] services prior to composition. AMD development tools can reuse the same business models developed by those doing AMD composition. But, generally, IT personnel refine these into more detailed models to generate as much of the code as possible ― 70% to 100% ― depending on the service type. AMD also includes the set of methods that promote “executable” models (that is, where there is no explicit transformation to implementation).<ref>Definition - What does Architected model-driven development (AMD) mean? [https://www.gartner.com/it-glossary/amd-architected-model-driven-development Gartner]</ref>
+'''Architected, Model-Driven Development''' or '''AMD''' is the most sophisticated end of the [[Service Oriented Architecture (SOA)|SOA]] modeling spectrum. It focuses on quality, performance, and reuse. It comes in two “flavors”: AMD composition and AMD development. AMD composition presumes that the needed services exist and can be “assembled” into an [[Application|application]] (business service), possibly with a new user interface (generally portal-based, using Web services). Organizations can generally use AMD composition models to generate the specifications for use by workflow orchestration technologies in the runtime environment. AMD development assumes that new organizations need to develop software services prior to composition. AMD development tools can reuse the same business models developed by those doing AMD composition. But, generally, IT personnel refine these into more detailed models to generate as much of the code as possible ― 70% to 100% ― depending on the service type. AMD also includes the set of methods that promote “executable” models (that is, where there is no explicit transformation to implementation).<ref>Definition - What does Architected model-driven development (AMD) mean? [https://www.gartner.com/it-glossary/amd-architected-model-driven-development Gartner]</ref>
@@ Line 7: / Line 7: @@
 ===Further Reading===
-*Next-generation model-driven development [https://www.omg.org/mda/mda_files/GC34-2485-03_LoRes.pdf IBM]
+*[https://www.omg.org/mda/mda_files/GC34-2485-03_LoRes.pdf Next-generation model-driven development -IBM]
-*Model-Driven [[Architecture]]: [[Vision]], Standards And Emerging Technologies [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.484.9121&rep=rep1&type=pdf John D Poole]
+*[http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.484.9121&rep=rep1&type=pdf Model-Driven Architecture: Vision, Standards And Emerging Technologies -John D Poole]

@@ Line 1: / Line 1: @@
-'''Architected, Model-Driven Development''' or '''AMD''' is the most sophisticated end of the [[Service Oriented Architecture (SOA)|SOA]] modeling spectrum. It focuses on quality, performance and reuse. It comes in two “flavors”: AMD composition and AMD development. AMD composition presumes that the needed services exist and can be “assembled” into an [[Application|application]] (business service), possibly with a new user interface (generally portal-based, using Web services).[[Organization|Organizations]] can generally use AMD composition models to generate the specifications for use by [[Workflow|workflow]] orchestration technologies in the runtime environment. AMD development assumes that new organizations need to develop [[Software|software]] services prior to composition. AMD development tools can reuse the same business models developed by those doing AMD composition. But, generally, IT personnel refine these into more detailed models to generate as much of the code as possible ― 70% to 100% ― depending on the service type. AMD also includes the set of methods that promote “executable” models (that is, where there is no explicit transformation to implementation).<ref>Definition - What does Architected model-driven development (AMD) mean? [https://www.gartner.com/it-glossary/amd-architected-model-driven-development Gartner]</ref>
+'''Architected, [[Model]]-Driven Development''' or '''AMD''' is the most sophisticated end of the [[Service Oriented Architecture (SOA)|SOA]] modeling spectrum. It focuses on [[quality]], performance and reuse. It comes in two “flavors”: AMD composition and AMD development. AMD composition presumes that the needed services exist and can be “assembled” into an [[Application|application]] ([[business]] [[service]]), possibly with a new user interface (generally portal-based, using Web services).[[Organization|Organizations]] can generally use AMD composition models to generate the specifications for use by [[Workflow|workflow]] [[orchestration]] technologies in the runtime environment. AMD development assumes that new organizations need to develop [[Software|software]] services prior to composition. AMD development tools can reuse the same business models developed by those doing AMD composition. But, generally, IT personnel refine these into more detailed models to generate as much of the code as possible ― 70% to 100% ― depending on the service type. AMD also includes the set of methods that promote “executable” models (that is, where there is no explicit transformation to implementation).<ref>Definition - What does Architected model-driven development (AMD) mean? [https://www.gartner.com/it-glossary/amd-architected-model-driven-development Gartner]</ref>
@@ Line 8: / Line 8: @@
 ===Further Reading===
 *Next-generation model-driven development [https://www.omg.org/mda/mda_files/GC34-2485-03_LoRes.pdf IBM]
-*Model-Driven Architecture: Vision, Standards And Emerging Technologies [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.484.9121&rep=rep1&type=pdf John D Poole]
+*Model-Driven [[Architecture]]: [[Vision]], Standards And Emerging Technologies [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.484.9121&rep=rep1&type=pdf John D Poole]

← Older revision		Revision as of 16:09, 29 May 2020
Line 1:		Line 1:
−	AMD is the most sophisticated end of the SOA modeling spectrum. It focuses on quality, performance and reuse. It comes in two “flavors”: AMD composition and AMD development. AMD composition presumes that the needed services exist and can be “assembled” into an application (business service), possibly with a new user interface (generally portal-based, using Web services). Organizations can generally use AMD composition models to generate the specifications for use by workflow orchestration technologies in the runtime environment. AMD development assumes that new organizations need to develop software services prior to composition. AMD development tools can reuse the same business models developed by those doing AMD composition. But, generally, IT personnel refine these into more detailed models to generate as much of the code as possible ― 70% to 100% ― depending on the service type. AMD also includes the set of methods that promote “executable” models (that is, where there is no explicit transformation to implementation).<ref>Definition - What does Architected model-driven development (AMD) mean? [https://www.gartner.com/it-glossary/amd-architected-model-driven-development Gartner]</ref>	+	'''Architected, Model-Driven Development''' or '''AMD''' is the most sophisticated end of the [[Service Oriented Architecture (SOA)\|SOA]] modeling spectrum. It focuses on quality, performance and reuse. It comes in two “flavors”: AMD composition and AMD development. AMD composition presumes that the needed services exist and can be “assembled” into an [[Application\|application]] (business service), possibly with a new user interface (generally portal-based, using Web services).[[Organization\|Organizations]] can generally use AMD composition models to generate the specifications for use by [[Workflow\|workflow]] orchestration technologies in the runtime environment. AMD development assumes that new organizations need to develop [[Software\|software]] services prior to composition. AMD development tools can reuse the same business models developed by those doing AMD composition. But, generally, IT personnel refine these into more detailed models to generate as much of the code as possible ― 70% to 100% ― depending on the service type. AMD also includes the set of methods that promote “executable” models (that is, where there is no explicit transformation to implementation).<ref>Definition - What does Architected model-driven development (AMD) mean? [https://www.gartner.com/it-glossary/amd-architected-model-driven-development Gartner]</ref>