Model-driven application: Difference between revisions

Revision as of 14:06, 24 August 2018

Latest revision as of 17:01, 11 July 2024

(3 intermediate revisions by 3 users not shown)

Line 2:

==History==

The ideal of the architecture for a model-driven application was first put forward by Tong-Ying Yu on ''the Enterprise Engineering Forum'' in 1999, which have been studied and spread through some internet media for a long time. It had influence on the field of enterprise application development in China; there were successful cases of commercial development of enterprise/business applications in the [[Software Architecture styles and patterns|architectural style]] of a model-driven application.<ref>ChinaLabs "''Business system infrastruc-ture platform (Technical report).''" Beijing, China: 2002.</ref> [[Gartner Group]] carried out some studies into the subject in 2008; they defined the ''model-driven packaged applications'' as "enterprise applications that have explicit metadata-driven models of the supported processes, data and relationships, and that generate runtime components through metadata models, either dynamically interpreted or compiled, rather than [[Hard coding|hardcoded]]."<ref>{{Cite web|url=http://www.gartner.com/it-glossary/model-driven-packaged-applications|title=Gartner IT Glossary: Model-Driven Packaged Applications|last=Gartner Group|first=|date=|website=|archive-url=|archive-date=|dead-url=|access-date=}}</ref> The model-driven application architecture is one of few technology trends to driven the next generation of [[Software modernization|application modernization]], that claimed by some industrial researchers in 2012.<ref>Winslow, P., Panigrahi, S. & Morrison, D. “''The Apps Revolution Manifesto —Volume 1: The Technologies.''” Credit Suisse. March 29, 2012.</ref>

==Instance==

[[Business process management]] (BPM) is the significant practice to the model-driven application. According to the definationdefinition, a BPM system is model-driven if the functions are operated based on the business process models which are built and changed at the operational time but not the design or implementation time; the biggest advantage is that it can deal with the continuous changing of business process directly without modifying the code of the software.

==Notes==

Line 14:

[[Category:Software architecture]]

[[Category:Software design|Architecture]]

[[Category:Systems architecture]]