Mismatches between Industry Practice and Teaching of Model-Driven Software Development
EAMDE was a 12 month research project, investigating how industry uses model-driven software development (MDSD). Using quantitative and qualitative research techniques, experiences were collected on the adoption and application of MDSD in 17 companies. The study highlighted examples of good and bad practice that lead to success or failure with MDSD. Some of these practices appear to have ramifications on the way that MDSD, and software modeling more generally, is taught within universities. This paper presents three of the key findings relevant to education: (1) A significant number of successful MDSD companies build their own modeling languages and generators, suggesting a re-orientation of education away from UML notation to fundamental modeling principles; (2) MDSD is generally taught top-down, whereas industry success is more likely when MDSD is applied bottom-up; (3) successful application of MDSD requires skills both in abstract modeling and compilers/optimization; however, these skills tend to be separated in standard CS curricula.
Keywordsmodel-driven software development education
Unable to display preview. Download preview PDF.
- 1.Hutchinson, J., Whittle, J., Rouncefield, M., Kristoffersen, S.: Empirical assessment of MDE in industry. In: ICSE 2011, pp. 471–480 (2011)Google Scholar
- 2.Hutchinson, J., Rouncefield, M., Whittle, J.: Model-driven engineering practices in industry. In: ICSE 2011, pp. 633–642 (2011)Google Scholar
- 3.Clark, T., Sammut, P., Willans, J.: Applied Metamodelling, A Foundation for Language Development, 2nd edn., Ceteva (2008)Google Scholar
- 7.Kelly, S., Tolvanen, J.-P.: Domain-Specific Modeling: Enabling Full Code Generation. John Wiley & Sons (2008)Google Scholar
- 8.The Middleware Company, Model Driven Development for J2EE Utilizing a Model Driven Architecture (MDA) Approach: Productivity Analysis, http://www.omg.org/mda/mda_files/MDA_Comparison-TMC_final.pdf (accessed September 2011)