Every CASE-Tool has its strengths and weaknesses. Of
course, Fujaba is not apart from this rule. Thus, why not
combine the strengths of Fujaba with another application in
a toolchain.
This paper introduces a toolchain covering Fujaba and
UML Lab. Traditionally a toolchain is based on the use
of an im-/export functionality to transfer data between the
dierent tools by persisting this data with a common le
format. As the requirements of the introduced toolchain
cannot be fullled by this mechanism, a synchronization of
models based on the Fujaba respectively UML Lab metamodel
is implemented. One requirement is to ensure that
changing anything in the model of one tool has an immediate
impact on the related model in the other tool. Therefor
the model synchronization handles every change separately
by analyzing change event objects resulting from each model
modication and ensures a (preferably) immediate handling
of changes.
%0 Conference Paper
%1 koch2011toolchain
%A Koch, Andreas
%A Zündorf, Albert
%D 2011
%K Zündorf akoch fujaba myown toolchain uml umllab
%T UML Toolchain - Using Fujaba and UML Lab in a toolchain
%U http://seblog.cs.uni-kassel.de/wp-content/uploads/2011/05/FujabaDays2011_Umltoolchain.pdf
%X Every CASE-Tool has its strengths and weaknesses. Of
course, Fujaba is not apart from this rule. Thus, why not
combine the strengths of Fujaba with another application in
a toolchain.
This paper introduces a toolchain covering Fujaba and
UML Lab. Traditionally a toolchain is based on the use
of an im-/export functionality to transfer data between the
dierent tools by persisting this data with a common le
format. As the requirements of the introduced toolchain
cannot be fullled by this mechanism, a synchronization of
models based on the Fujaba respectively UML Lab metamodel
is implemented. One requirement is to ensure that
changing anything in the model of one tool has an immediate
impact on the related model in the other tool. Therefor
the model synchronization handles every change separately
by analyzing change event objects resulting from each model
modication and ensures a (preferably) immediate handling
of changes.
@inproceedings{koch2011toolchain,
abstract = {Every CASE-Tool has its strengths and weaknesses. Of
course, Fujaba is not apart from this rule. Thus, why not
combine the strengths of Fujaba with another application in
a toolchain.
This paper introduces a toolchain covering Fujaba and
UML Lab. Traditionally a toolchain is based on the use
of an im-/export functionality to transfer data between the
dierent tools by persisting this data with a common le
format. As the requirements of the introduced toolchain
cannot be fullled by this mechanism, a synchronization of
models based on the Fujaba respectively UML Lab metamodel
is implemented. One requirement is to ensure that
changing anything in the model of one tool has an immediate
impact on the related model in the other tool. Therefor
the model synchronization handles every change separately
by analyzing change event objects resulting from each model
modication and ensures a (preferably) immediate handling
of changes.},
added-at = {2012-04-24T18:19:46.000+0200},
author = {Koch, Andreas and Zündorf, Albert},
biburl = {https://www.bibsonomy.org/bibtex/2e081e8f00478d98dbdb4c82dfdfd936e/akoch},
interhash = {0aa46e21c3df02e08bbe44a16455b0b8},
intrahash = {e081e8f00478d98dbdb4c82dfdfd936e},
keywords = {Zündorf akoch fujaba myown toolchain uml umllab},
month = {mai},
timestamp = {2012-04-24T18:20:51.000+0200},
title = {UML Toolchain - Using Fujaba and UML Lab in a toolchain},
url = {http://seblog.cs.uni-kassel.de/wp-content/uploads/2011/05/FujabaDays2011_Umltoolchain.pdf},
year = 2011
}