Experiences from Representing Software Architecture in a Large Industrial Project Using Model Driven Development

  • Authors:
  • Anders Mattsson;Bjorn Lundell;Brian Lings;Brian Fitzgerald

  • Affiliations:
  • Combitech AB, Sweden;University of Skovde, Sweden;University of Skovde, Sweden;University of Limerick, Ireland

  • Venue:
  • SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
  • Year:
  • 2007

Quantified Score

Hi-index 0.00

Visualization

Abstract

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.