Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Quality Attribute Design Primitives and the Attribute Driven Design Method
PFE '01 Revised Papers from the 4th International Workshop on Software Product-Family Engineering
Software Architecture in Practice
Software Architecture in Practice
The Pragmatics of Model-Driven Development
IEEE Software
Model driven development: the case for domain oriented programming
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
Model-driven development: the good, the bad, and the ugly
IBM Systems Journal - Model-driven software development
Where Is the Proof? - A Review of Experiences from Applying MDE in Industry
ECMDA-FA '08 Proceedings of the 4th European conference on Model Driven Architecture: Foundations and Applications
Automating the Trace of Architectural Design Decisions and Rationales Using a MDD Approach
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Hi-index | 0.00 |
A basic idea of Model Driven Development (MDD) is to capture all important design information in a set of formal or semi formal models that are automatically kept consistent by tools. This paper reports on industrial experience from use of MDD and shows that the approach needs improvements regarding the architecture since there are no suggested ways to formalize design rules which are an important part of the architecture. Instead, one has to rely on time consuming and error prone manual interpretations, reviews and reworkings to keep the system consistent with the architecture. To reap the full benefits of MDD it is therefore important to find ways of formalizing design rules to make it possible to allow automatic enforcement of the architecture on the system model.