Tags » Model Driven Architecture

WICSA/CompArch 2015 Call for Workshop Papers

WICSA/CompArch 2015 – 12th Working IEEE / IFIP Conference on Software Architecture and 9th Federated Conference Series Component-Based Software Engineering and Software Architecture
Call for Workshop Papers… 946 more words

Software Architecture

Effective Use Of Model-Driven Development

The original promise of Object Management Group’s Model-Driven Architecture (OMG MDA) initiative, and its realization in Model-Driven Development (MDD) methods and tools, was to be able to separate conceptual business design, from platform independent logical solution design, from platform specific solution implementation, and to use model-to-model and model-to-code transforms to automatically transform one from the other. 1,436 more words

Solution Architecture



It is the model used for showing the organization of the system through the components of that system as well as the relation between the components themselves. 780 more words

Chapter 5 – System Modeling

Why do we need model driven architecture (MDA)?

Many organizations have been developing IT software without modeling but there have been various problems in realizing the “requirements to implementation”.

Primary issue continues to be that of communication. 787 more words


"Model-Based Engineering with AADL" Selected for Intel Recommended Reading List

To help developers make the most of the Architecture Analysis and Design Language (AADL), two SEI researchers published Model-Based Engineering with AADL (Addison-Wesley Professional 2012), about which… 158 more words

Architecture-Centric Practices

Applying TOGAF principles with MDA

TOGAF is an international standard to build and maintain an enterprise consortium and adopt the right Architecture Development Method, and though we talk a lot about it, very little is put into practice.   256 more words


Model Driven Architecture (MDA)

MDA guides architects and developers to more effectively define models at various levels of abstraction and to develop transformations among models, code, and other artifacts of the software lifecycle.