Separation of concerns in model-driven development

Abstract

0 7 4 0 -7 4 5 9 / 0 3 / $ 1 7 . 0 0 © 2 0 0 3 I E E E For more information on this or any other computing topic, please visit our Digital Library at http://computer.org/publications/dlib. S e p t e m b e r / O c t o b e r 2 0 0 3 I E

Modelling and Enterprises - The Past, the Present and the Future

“…Models-as-high-level-specifications has recently witnessed increased following among practitioners (Hailpern and Tarr, 2006;Hutchinson et al, 2011). Multiple variants of this usage are noticed, for instance, Models are automatically transformed to derive partial implementation to be taken to completion using code-centric development processes (known as code completion) with models forgotten hereafter or maintained so that changes introduced during code-completion can be taken back automatically to models (known as round-tripengineering) (Medvidovic et al, 1999); and complete implementation is derived from models through model-transformation with models remaining primary SDLC artefacts (Kulkarni and Reddy, 2003). Models-as-executable-artefacts is the least common of all usages and that too in niche domains of life-critical systems (Rumpe, 2004).…”

“…The idea is to identify what changes where and when in system functionality -the what leads to the variations, the where leads to the variation points, and the when leads to internally consistent set of what-to-where bindings. However, IT systems tend to vary along multiple dimensionsfunctionality, business process, extra-functional characteristics, and implementation platform to name only a few (Kulkarni and Reddy, 2003). Therefore, the notion of 'what changes where and when' needs to be addressed along every dimension and then across them all at the application level.…”

Generating CAM aspect-oriented architectures using Model-Driven Development

“…As clearly stated in [38][39][40], the main motivation for applying AOSD to MDD is to solve the problem that MDD presents regarding the lack of specific mechanisms for the separation of crosscutting concerns within each level of abstraction. If all concerns can be modelled separately at a certain level, that level will become more manageable, extensible and maintainable.…”

Construction and Execution of Adaptable Applications Using an Aspect-Oriented and Model Driven Approach

“…MDE is used by Kulkarni et al [16] for providing separation of concern between system concerns at both model and code level using templates and code weaving. This is similar to the AOM approach we employ, except that we use parameterized UML to specify aspects and perform model level composition avoiding the need for code level weaving.…”