Domain-Specific Modeling: The Killer App for Method Engineering?
The method creation heyday of the 1980s was characterized by convivial chaos, leading to the idea of a discipline of method engineering. Before it could grow, the unification and marketing machine of UML crushed method development into “one size fits all” design by committee in the 1990s. A scattering of brave souls went against the current, creating modeling languages specific to their own problem domain, and were rewarded with significantly higher productivity. As they seek to scale their solutions, they need help from the research world to analyze their results, and to bring to bear the learning from the early days of method engineering.
- 1.DSM Case Studies and Examples, 26.5.2007; http://www.dsmforam.org/cases.html
- 2.M. Burber and D. Herst, Productivity Analysis — Model-Driven, Pattern-based development with OptimalJ, 26.5.2007 http://www.theserverside.com/tt/articles/article.tss?1=SymposiumCoverage
- 3.J. Warmer, Case Study: Building a Flexible Software Factory using Small DSLs and Small Models, (unpublished discussion from talk), Code Generation 2007Google Scholar
- 4.R.B. Kieburtz, L. McKinney, J.M. Bell, J. Hook, A. Kotov, J. Lewis, D.P. Oliva, T. Sheard, I. Smith and L. Walton, A software engineering experiment in software component generation, 18th International Conference on Software Engineering (ICSE’96), 1996Google Scholar
- 5.Nokia case study, MetaCase, 1999; www.metacase.com/papers/MetaEdit_in_Nokia.pdfGoogle Scholar
- 6.J. Luoma, S. Kelly and J-P. Tolvanen, Defining Domain-Specific Modeling Languages: Collected Experiences, 4th OOPSLA Workshop on DSM, TR-33, University of Jyväskylä, 2004Google Scholar