A Model-Based Service Customization Framework for Consumer Variability Management in Service-Oriented Architectures
Sandile Wilmoth Dlamini · 2014
ion and model: according to Kramer (2007), abstraction is ―the mapping from one representation of a problem to another which preserves certain desirable properties and which reduces complexity‖. In other words, the purpose of abstraction is to decrease the number of elements and focus on the important points rather than details. Approaches centered on the use of models (e.g., model-driven engineering, aspect-oriented modeling, generative programming) have been proposed in order to effectively represent, define, and use abstractions for any part of a software system. Models have been used for many years in various research disciplines including mathematical sciences, biology, economics, house building, and geography (Bezivin, 2005). In the context of software engineering, several definitions of the notion of model have been given, for example, nine definitions are reported in Muller et al. (2012), but, in essence, a model is an abstraction of some aspect of a system under study. A system under study can be an actual existing system, or a system under development. A model is an abstraction since some details are hidden and/or