Home > Research > Publications & Outputs > The state of practice in model-driven engineering

Research

Associated organisational units

Electronic data

Links

Text available via DOI:

View graph of relations

The state of practice in model-driven engineering

Research output: Contribution to Journal/Magazine › Journal article › peer-review

Published

Standard

The state of practice in model-driven engineering. / Whittle, Jon; Hutchinson, John; Rouncefield, Mark.
In: IEEE Software, Vol. 31, No. 3, 21.04.2014, p. 79-85.

Research output: Contribution to Journal/Magazine › Journal article › peer-review

Harvard

Whittle, J, Hutchinson, J & Rouncefield, M 2014, 'The state of practice in model-driven engineering', IEEE Software, vol. 31, no. 3, pp. 79-85. https://doi.org/10.1109/MS.2013.65

APA

Whittle, J., Hutchinson, J., & Rouncefield, M. (2014). The state of practice in model-driven engineering. IEEE Software, 31(3), 79-85. https://doi.org/10.1109/MS.2013.65

Vancouver

Whittle J, Hutchinson J, Rouncefield M. The state of practice in model-driven engineering. IEEE Software. 2014 Apr 21;31(3):79-85. Epub 2013 Apr 23. doi: 10.1109/MS.2013.65

Author

Whittle, Jon ; Hutchinson, John ; Rouncefield, Mark. / The state of practice in model-driven engineering. In: IEEE Software. 2014 ; Vol. 31, No. 3. pp. 79-85.

Bibtex

@article{b5c928a0fa2a4f11b305cd7f86fa2bbe,
title = "The state of practice in model-driven engineering",
abstract = "Despite lively debate over the last decade on the benefits or drawbacks of model-driven engineering (MDE), there have been very few industry-wide studies of MDE in practice. We present a new study, covering a broad range of experiences and ways of applying MDE: we surveyed 450 MDE practitionersand carried out in-depth interviews with 22 more. Findings suggest that MDE may be more widespread than commonly believed, but developers rarely use it to generate whole systems; rather, they apply it to develop key parts of a system often using domain-specific modeling languages developed specifically forthe purpose. Our findings also suggest reasons why some efforts to adopt MDE fail and some succeed. As is usually the case in software engineering, adoption largely depends on social and organizational factors, some of which we describe in this paper.",
author = "Jon Whittle and John Hutchinson and Mark Rouncefield",
year = "2014",
month = apr,
day = "21",
doi = "10.1109/MS.2013.65",
language = "English",
volume = "31",
pages = "79--85",
journal = "IEEE Software",
issn = "0740-7459",
publisher = "IEEE Computer Society",
number = "3",

}

RIS

TY - JOUR

T1 - The state of practice in model-driven engineering

AU - Whittle, Jon

AU - Hutchinson, John

AU - Rouncefield, Mark

PY - 2014/4/21

Y1 - 2014/4/21

N2 - Despite lively debate over the last decade on the benefits or drawbacks of model-driven engineering (MDE), there have been very few industry-wide studies of MDE in practice. We present a new study, covering a broad range of experiences and ways of applying MDE: we surveyed 450 MDE practitionersand carried out in-depth interviews with 22 more. Findings suggest that MDE may be more widespread than commonly believed, but developers rarely use it to generate whole systems; rather, they apply it to develop key parts of a system often using domain-specific modeling languages developed specifically forthe purpose. Our findings also suggest reasons why some efforts to adopt MDE fail and some succeed. As is usually the case in software engineering, adoption largely depends on social and organizational factors, some of which we describe in this paper.

AB - Despite lively debate over the last decade on the benefits or drawbacks of model-driven engineering (MDE), there have been very few industry-wide studies of MDE in practice. We present a new study, covering a broad range of experiences and ways of applying MDE: we surveyed 450 MDE practitionersand carried out in-depth interviews with 22 more. Findings suggest that MDE may be more widespread than commonly believed, but developers rarely use it to generate whole systems; rather, they apply it to develop key parts of a system often using domain-specific modeling languages developed specifically forthe purpose. Our findings also suggest reasons why some efforts to adopt MDE fail and some succeed. As is usually the case in software engineering, adoption largely depends on social and organizational factors, some of which we describe in this paper.

U2 - 10.1109/MS.2013.65

DO - 10.1109/MS.2013.65

M3 - Journal article

VL - 31

SP - 79

EP - 85

JO - IEEE Software

JF - IEEE Software

SN - 0740-7459

IS - 3

ER -