Issue No. 01 - January/February (2009 vol. 35)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/TSE.2008.87
Anders Mattsson , Combitech AB, Jönköping
Björn Lundell , University of Skövde, Skövde
Brian Lings , University of Skövde, Skövde
Brian Fitzgerald , Univerity of Limerick, Limerick
A basic premise of Model Driven Development (MDD) is to capture all important design information in a set of formal or semi-formal models which are then automatically kept consistent by tools. The concept however is still relatively immature and there is little by way of empirically validated guidelines. In this paper we report on the use of MDD on a significant real-world project over several years. Our research found the MDD approach to be deficient in terms of modelling architectural design rules. Furthermore, the current body of literature does not offer a satisfactory solution as to how architectural design rules should be modelled. As a result developers have to rely on time-consuming and error-prone manual practices to keep a system consistent with its architecture. To realise the full benefits of MDD it is important to find ways of formalizing architectural design rules which then allow automatic enforcement of the architecture on the system model. Without this, architectural enforcement will remain a bottleneck in large MDD projects.
Software Architecture, Model-Driven Development, Case Study Research
B. Fitzgerald, B. Lundell, B. Lings and A. Mattsson, "Linking Model-Driven Development and Software Architecture: A Case Study," in IEEE Transactions on Software Engineering, vol. 35, no. , pp. 83-93, 2008.