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

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.

References

1. {1} B. Selic, "The pragmatics of model-driven development," IEEE Software, vol. 20, pp. 19- 25, Sep-Oct 2003.
2. {2} D. C. Schmidt, "Model-driven engineering," IEEE Computer, vol. 39, pp. 25-31, Feb 2006.
3. {3} K. Balasubramanian, A. Gokhale, G. Karsai, J. Sztipanovits, and S. Neema, "Developing applications using model-driven design environments," IEEE Computer, vol. 39, pp. 33- 40, 2006.
4. {4} B. Hailpern and P. Tarr, "Model-driven development: The good, the bad, and the ugly," IBM Systems Journal, vol. 45, pp. 451-461, 2006.
5. {5} MDA, "MDA Guide version 1.0.1," OMG, 2003.
6. {6} T. Dave and M. B. Brian, "Model driven development: the case for domain oriented programming," in Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications Anaheim, CA, USA: ACM Press, 2003.
7. {7} J. Greenfield and K. Short, Software factories : assembling applications with patterns, models, frameworks, and tools. Indianapolis, IN, USA: Wiley Pub., 2004.
8. {8} L. Bass, P. Clements, and R. Kazman, Software architecture in practice, 2nd ed. Boston: Addison-Wesley, 2003.
9. {9} F. Buschmann, Pattern-oriented software architecture : a system of patterns. Chichester; New York: Wiley, 1996.
10. {10} J. Bosch, Design and use of software architectures : adopting and evolving a product-line approach. Reading, MA: Addison-Wesley, 2000.
11. {11} L. Bass, M. Klein, and F. Bachmann, "Quality attribute design primitives and the Attribute Driven Design Method," Software Product Family Engineering 4th International Workshop, PFE 2001 Revised Papers Lecture Notes in Computer Science Vol. 2290, vol. 2290, pp. 169- 86, 2002.
12. {12} E. Gamma, Design patterns : elements of reusable object-oriented software. Reading, Mass.: Addison-Wesley, 1995.

Index Terms

• Social and professional topics

  • Professional topics

    • Management of computing and information systems

      • Project and people management

        • Systems analysis and design

      • Software management

• Software and its engineering

  • Software creation and management

    • Software development process management

  • Software organization and properties

    • Software system structures

      • Software architectures