his.sePublications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Linking Model-Driven Development and Software Architecture: A Case Study
Combitech AB, Jönköping, Sweden.
University of Skövde, School of Humanities and Informatics. University of Skövde, The Informatics Research Centre.
University of Skövde, School of Humanities and Informatics. University of Skövde, The Informatics Research Centre.
Lero-the Irish Software Engineering Research Centre, University of Limerick, Limerick, Ireland.
2009 (English)In: IEEE Transactions on Software Engineering, ISSN 0098-5589, E-ISSN 1939-3520, Vol. 35, no 1, 83-93 p.Article in journal (Refereed) Published
Abstract [en]

A basic premise of model-driven development (MDD) is to capture all important design information in a set of formal or semiformal models, which are then automatically kept consistent by tools. The concept, however, is still relatively immature and there is little by way of impirically 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 modeling architectural design rules. Furthermore, the current body of literature does not offer a satisfactory solution as to how architectural design rules should be modeled. As a result developers have to rely on time-consuming and error-prone manual practices to keep a system consistent with its architecture. To realize 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.

Place, publisher, year, edition, pages
IEEE Computer Society, 2009. Vol. 35, no 1, 83-93 p.
Keyword [en]
Case study, model-driven development, software architecture
National Category
Computer and Information Science
Research subject
Technology
Identifiers
URN: urn:nbn:se:his:diva-2913DOI: 10.1109/TSE.2008.87ISI: 000265089400005Scopus ID: 2-s2.0-60449116881OAI: oai:DiVA.org:his-2913DiVA: diva2:209713
Available from: 2009-03-26 Created: 2009-03-26 Last updated: 2016-01-13Bibliographically approved

Open Access in DiVA

No full text

Other links

Publisher's full textScopus

Search in DiVA

By author/editor
Lundell, BjörnLings, Brian
By organisation
School of Humanities and InformaticsThe Informatics Research Centre
In the same journal
IEEE Transactions on Software Engineering
Computer and Information Science

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

Total: 76 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf