![](bg6.png)
5 CONCLUSIONS AND FUTURE
WORK
The first contribution of this article is the
construction of a conceptual framework based on
established research, which allows the expected
changes to be categorised. Furthermore, it analyses
what changes are to be expected as a result of
transformations within and between model levels
from the requirements model to the platform-
independent models. This allows for better
evaluation and planning of the expected
consequences when future changes take place.
As a future work, it is promising to investigate
impact analysis for transformations on the PIM
level, such as by the transformation in PIM4Agents,
which was proposed in the SHAPE project.
Likewise, the impact of transformations on the PSM
and the code level are also worth consideration.
An automatic process of impact analysis should
be considered as the potential final goal of the
research. This would enable it to deliver very early
in an information change process, in which all
business sectors are involved. In combination with
the actually defined importance of observed effects,
this would constitute a complete recommender
system for deciding whether a change is reasonable
or not feasible at all. Such a system, however, would
require a lot of effort to be implemented in such a
way that the impact analysis would produce accurate
and reliable results in the real world. Before this
point can be reached, however, there is still an
enormous amount of research and development
effort that needs to be done. This especially relates
to the research that has to be carried out regarding
ranking functions for model transformation
alternatives and the alignment of multiple ranking
criteria.
ACKNOWLEDGEMENTS
This research was co-funded by the European Union
in the frame of the SHAPE FP7 project (ICT- 2007-
216408). The authors would like to express their
acknowledgments to SHAPE colleagues.
REFERENCES
Arnold, S. R.; Bohner, A. S., 1993. Impact Analysis –
Towards A Framework for Comparison. In: Card, N.
D.: Proceedings of the Conference on Software
Maintenanc. IEEE Computer Society, Washington DC.
Balzert, H., 1999. Lehrbuch der Objektmodellierung –
Analyse und Entwurf. Spektrum Akademischer
Verlag, Heidelberg et al.
Becker, J.; Mathas, C.; Wilkmann, A., 2009.
Geschäftsprozessmanagement. Springer, Berlin et al.
Beltran, J. C. F., 2007. Modellgetriebene Software-
entwicklung: MDA und MDSD in der Praxis. J.
Trompeter (Ed.). Entwickler. Press.
van den Berg, K., Tekinerdogan, B., & Nguyen, H. (2006,
July). Analysis of crosscutting in model
transformations. In ECMDA-TW Traceability
Workshop Proceedings (No. A219, pp. 51-64).
Bohlen, M., & Starke, G., 2003. MDA entzaubert.
OBJEKTspektrum, 3, 52-56.
Brown, A. W., 2004. Model driven architecture: Principles
and practice. Software and Systems Modelling, 3(4),
314-327.
Czarnecki, K., & Helsen, S. (2006). Feature-based survey
of model transformation approaches. IBM Systems
Journal, 45(3), 621-645.
Frankel, D. S., 2003: Model Driven Architecture –
Applying MDA to Enterprise Computing. Wiley,
Indianapolis.
Fowler, M., 2008: Refactoring – Improving the Design of
Existing Code. Addison-Wesley, Boston et al., 22
nd
edition.
Greenfield, J.; Short, K., 2006: Software Factories –
Moderne Software-Architekturen mit SOA, MDA,
Patterns und agilen Methoden. moderne industrie
Buch, Bonn.
Gruhn, V.; Pieper, D.; Rötters, C., 2006: MDA® –
Effektives Software-Engineering mit UML 2® und
EclipseTM. Springer, Berlin et al.
Jouault, F., & Kurtev, I., 2006. Transforming models with
ATL. In Satellite Events at the MoDELS 2005
Conference (pp. 128-138). Springer Berlin Heidelberg.
Kleppe, A.; Warmer, J.; Bast, W., 2003: MDA Explained –
The Model Driven Architecture: Practice and
Promise. Addison-Wesley, Boston.
Mellor, S.; Scott, K.; Uhl, A.; Weise, D., 2004: MDA
Distilled – Principles of Model-Driven Architecture.
Addison-Wesley, Boston et al.
Mens, T,; Van Gorp, Pieter, 2006: A Taxonomy of Model
Transformation. Electr. Notes Theor. Comput. Sci.
152: 125-142.
Object Management Group (Ed.), 2003. MDA-Guide
Version 1.0.1. http://www.omg.org/cgi-bin/doc?omg/
03-06-01, Retrieved on 2013-11-04.
Object Management Group (Ed.), 2011a. OMG Unified
Modelling Language® (OMG UML), Infrastructure
Version 2.4.1. http://www.omg.org/spec/UML/2.4.1/
Infrastructure/PDF/, Retrieved on 2013-11-04.
Object Management Group (Ed.), 2011b. Query/View/
Transformation Specification – 1.1. http://www.omg.
org/spec/QVT/1.1/PDF/, Retrieved on 2013-11-04.
Object Management Group (Ed.), 2013. Committed Com-
panies and their Products. http://www.omg.org/mda/
committed-products.htm, Retrieved on 2013-11-04.
Pohl, K., 2008: Requirements Engineering – Grundlagen,
RecommendationsforImpactAnalysisofModelTransformations-FromtheRequirementsModeltothe
Platform-independentModel
433