%$Id: conclusion.tex 14757 2008-10-10 15:02:59Z amoghk $
%\sqzsmall
\sqzlarge
\section{Conclusions}
\label{sec:conclusion}
\sqzsmall
This paper presented MTS (Model-transformation Templatization and
Specialization), which is an enabling technology that seamlessly
integrates with existing model transformation tools to support reusable
model transformations for application families.  
% Existing model transformation tools lack support for reusable
% transformations which force developers to reinvent transformation
% rules.  MTS overcomes these limitations while requiring no change to
% contemporary tools.  
MTS defines templatized transformations to factor out the commonalities,
and uses the notion of a generated variability metamodel to capture the
variabilities in the transformation process across variants of an
application family.  MTS defines two higher order transformations
to specialize the transformations for different variants. Although our
existing prototype is implemented in GReAT, it can be easily
extended for other model transformation toolchains as long as they
provide means to develop higher order transformations. Results of
evaluating MTS indicate that it enhances developer
productivity and effectiveness of model-based software development for
application families. MTS is available in open source as part of the CoSMIC MDE tool suite
from \url{www.dre.vanderbilt.edu/cosmic}. 
\sqzsmall
\sqzsmall

%
% Our results from applying MTS to 
% two diverse set of application families (for the given number of 
% structural and qualitative variabilities) indicate upto a 90\% reduction 
% in execution time, when compared with the non-templatized approach.

% Amogh, I commented this out
%
% Andy, OK.
% In the future we are interested in studying the usability of the 
% constraint specification language, and the higher order 
% transformations in MTS.  As such, several user studies have been 
% planned to measure the quality value of our toolchain. Additionally, we 
% have also planned on extending and applying MTS to scenarios
% where a single source DSML must be mapped to multiple target DSMLs. 
% Amogh, I reincluded this.
%
% OK, sure.
