University of Limerick Institutional Repository

Linking model-driven development and software architecture: a case study

DSpace Repository

Show simple item record

dc.contributor.author Mattsson, Anders
dc.contributor.author Lundell, Bjorn
dc.contributor.author Lings, Brian
dc.contributor.author Fitzgerald, Brian
dc.date.accessioned 2011-07-20T15:31:58Z
dc.date.available 2011-07-20T15:31:58Z
dc.date.issued 2009
dc.identifier.uri http://hdl.handle.net/10344/1141
dc.description peer-reviewed en_US
dc.description.abstract 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. en_US
dc.language.iso eng en_US
dc.publisher IEEE Computer Society en_US
dc.relation.ispartofseries IEEE Transactions on Software Engineering;35/1/pp. 1-12
dc.rights ©2009 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.
dc.subject model driven development en_US
dc.subject technology architecture en_US
dc.title Linking model-driven development and software architecture: a case study en_US
dc.type Article en_US
dc.type.supercollection all_ul_research en_US
dc.type.supercollection ul_published_reviewed en_US
dc.type.restriction none en
dc.contributor.sponsor SFI
dc.internal.rssid 1404870


Files in this item

This item appears in the following Collection(s)

Show simple item record

Search ULIR


Browse

My Account

Statistics