BibSonomy :: publication ::

tag user group author concept BibTeX key search:all search:neilernst

The blue social bookmark and publication sharing system.

(0)

This publication has not been reviewed yet.

rating distribution

average user rating

The average rating is computed over all reviews. However, some of them may be invisible to you due to the visibility setting chosen by the reviewers.

(0.0 of 5.0 based on 0 reviews)

Linking Model Driven Development and Software Architecture: A Case Study

by: Anders Mattsson, Bjorn Lundell, Brian Lings, and Brian Fitzgerald

In: IEEE Transactions on Software Engineering, Vol. 99, Nr. 1 Los Alamitos, CA, USA: IEEE Computer Society (2009) .

Resources (URL, PDF, PS...)

URL:	http://doi.ieeecomputersociety.org/10.1109/TSE.2008.87

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.

BibTeX record

@article{mattson08pre,
  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.},
  added-at = {2008-12-18T18:25:31.000+0100},
  address = {Los Alamitos, CA, USA},
  author = {Mattsson, Anders and Lundell, Bjorn and Lings, Brian and Fitzgerald, Brian},
  biburl = {http://www.bibsonomy.org/bibtex/2b4f3c81a3a875867c01fad7e64131c5a/neilernst},
  interhash = {7e45d48f86d22d297d2b72a659263491},
  intrahash = {b4f3c81a3a875867c01fad7e64131c5a},
  issn = {0098-5589},
  journal = {IEEE Transactions on Software Engineering},
  keywords = {imported},
  number = 1,
  publisher = {IEEE Computer Society},
  timestamp = {2008-12-18T18:25:31.000+0100},
  title = {Linking Model Driven Development and Software Architecture: A Case Study},
  url = {http://doi.ieeecomputersociety.org/10.1109/TSE.2008.87},
  volume = 99,
  year = 2009
}

Endnote record

%0 Journal Article
%1 mattson08pre
%A Mattsson, Anders
%A Lundell, Bjorn
%A Lings, Brian
%A Fitzgerald, Brian
%C Los Alamitos, CA, USA
%D 2009
%I IEEE Computer Society
%J IEEE Transactions on Software Engineering
%K 
%N 1
%T Linking Model Driven Development and Software Architecture: A Case Study
%U http://doi.ieeecomputersociety.org/10.1109/TSE.2008.87
%V 99
%X 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.

BibSonomy :: publication ::

Linking Model Driven Development and Software Architecture: A Case Study

Resources (URL, PDF, PS...)

Abstract

BibTeX record

Endnote record