Model-Driven Development within a Legacy System: An Industry Experience Report

Authors:
Anthony MacDonald;Danny Russell;Brenton Atchison
Affiliations:
University of Queensland;University of Queensland;Invensys Rail Systems Australia
Venue:
ASWEC '05 Proceedings of the 2005 Australian conference on Software Engineering
Year:
2005

Citing 0
Cited 7

A case study on the application of UML in legacy development

Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Where Is the Proof? - A Review of Experiences from Applying MDE in Industry

ECMDA-FA '08 Proceedings of the 4th European conference on Model Driven Architecture: Foundations and Applications
Definitions and approaches to model quality in model-based software development - A review of literature

Information and Software Technology
Adopting model driven software development in industry: a case study at two companies

MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Transition to model-driven engineering: what is revolutionary, what remains the same?

MODELS'12 Proceedings of the 15th international conference on Model Driven Engineering Languages and Systems
Design and evaluation of the ModelHealth toolchain for continuity of care web services

Automated Software Engineering
Relevance, benefits, and problems of software modelling and model driven techniques-A survey in the Italian industry

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

Model-driven development claims to offer the same improvement to developers that the step from assembly to procedural programming languages offered developers in the last century. In this paper we report on a project that assessed the feasibility of applying a model-driven development approach to the evolution of a non-trivial legacy system in an industrial setting. The project focused on whether the promises of model-driven development hold in the real world and whether it possible to adopt model-driven development without losing the investment in existing third generation language code. An existing component from a system was redeveloped and integrated back into the system using a current model-driven development tool at Invensys Rail Systems Australia. From experiences throughout the project, and with the tool, a set of requirements for future model-driven development and model-driven development tools was produced. These requirements are designed to both aid tool developers, and to give companies a way of assessing the maturity of both future model-driven development tools and model-driven development itself.