[Zurück]

A. Kalnins, E. Kalnina, E. Celms, A. Sostaks, H. Schwarz, A. Ambroziewicz, J. Bojarski, W. Nowakowski, T. Straszak, S. Kavaldjian, J. Falb:
"Reusable Case Transformation Rule Specification";
Bericht für EU, ReDSeeDS, Projektnr. IST-2006-033596; Berichts-Nr. D3.3, 2007; 129 S.

This deliverable has a relatively narrow focus on using model transformations for building a software case in ReDSeeDS. These software cases are assumed to be built according to the principles of model-driven software development. According to these principles, several models are built one after another as artefacts of this software case. This building should be performed according to a well defined design methodology, of which we currently are interested only as a set of precisely defined rules, what model elements should be used at which artefacts, what are the naming and structuring rules, what are the desired dependencies between the artefacts and similar issues. It should be specially noted that the starting point of a software case is also a well defined artefact - it is the requirements model in RSL.

Model-driven software development includes as one of the basic principles the use of automatic transformations between design steps whenever this is possible. Thus only the initial version of the next model is obtained, which is then extended manually.

The above mentioned facts on software case development in ReDSeeDS enables the transformations there to have a significantly greater role than in many standard MDSD applications. In many cases the use of automated transformations can be a critical enabler for building a software case according to a strictly defined design methodology in ReDSeeDS.

According to previous deliverables, the SCL includes a special language for defining such transformations - the model transformation language MOLA.

This deliverable illustrates a consistent use of model transformations on an example design methodology, which is based on a 4-layer architecture. For transitions from requirements to architecture model and from architecture to design model initially natural informal transformation rules are provided. Then these rules are implemented in the model transformation language MOLA. For the chosen example methodology, the part of the next model generated by transformations can be especially large. Finally, it is briefly discussed, what is necessary to integrate the model transformations with other tools and support features for software case development. The full solution of these technology issues goes to Workpackage 5.

It should be noted, that transformations developed in this deliverable are not specific to one software case, but to any case built according to the selected example methodology.

Case-based reasoning, model transformation, reuse

http://publik.tuwien.ac.at/files/pub-et_13426.pdf

Projektleitung Hermann Kaindl:
Requirements Driven Software Development System