%0 Book Section %1 anastasakis_07_uml2alloy %A Anastasakis, Kyriakos %A Bordbar, Behzad %A Georg, Geri %A Ray, Indrakshi %D 2007 %J Model Driven Engineering Languages and Systems %K \_to\_print 2007 \_hardcopy alloy model\_transformation \_pdf uml %P 436--450 %R http://dx.doi.org/10.1007/978-3-540-75209-7\_30 %T UML2Alloy: A Challenging Model Transformation %U http://dx.doi.org/10.1007/978-3-540-75209-7\_30 %X Alloy is a formal language, which has been applied to modelling of systems in a wide range of application domains. It is supported by Alloy Analyzer, a tool, which allows fully automated analysis. As a result, creating Alloy code from a UML model provides the opportunity to exploit analysis capabilities of the Alloy Analyzer to discover possible design flaws at early stages of the software development. Our research makes use of model based techniques for the automated transformation of UML class diagrams with OCL constraints to Alloy code. The paper demonstrates challenging aspects of the model transformation, which originate in fundamental differences between UML and Alloy. We shall discuss some of the differences and illustrate their implications on the model transformation process. The presented approach is explained via an example of a secure e-business system.

@incollection{anastasakis_07_uml2alloy, abstract = {Alloy is a formal language, which has been applied to modelling of systems in a wide range of application domains. It is supported by Alloy Analyzer, a tool, which allows fully automated analysis. As a result, creating Alloy code from a UML model provides the opportunity to exploit analysis capabilities of the Alloy Analyzer to discover possible design flaws at early stages of the software development. Our research makes use of model based techniques for the automated transformation of UML class diagrams with OCL constraints to Alloy code. The paper demonstrates challenging aspects of the model transformation, which originate in fundamental differences between UML and Alloy. We shall discuss some of the differences and illustrate their implications on the model transformation process. The presented approach is explained via an example of a secure e-business system.}, added-at = {2009-03-10T04:37:20.000+0100}, author = {Anastasakis, Kyriakos and Bordbar, Behzad and Georg, Geri and Ray, Indrakshi}, biburl = {https://www.bibsonomy.org/bibtex/2231d6139a9a78c72bb8c73a74ae198b2/leonardo}, citeulike-article-id = {1822586}, doi = {http://dx.doi.org/10.1007/978-3-540-75209-7\_30}, interhash = {abd49c861a78350f1cd3a28942eebdbb}, intrahash = {231d6139a9a78c72bb8c73a74ae198b2}, journal = {Model Driven Engineering Languages and Systems}, keywords = {\_to\_print 2007 \_hardcopy alloy model\_transformation \_pdf uml}, pages = {436--450}, posted-at = {2007-10-25 23:59:49}, priority = {4}, timestamp = {2009-03-10T04:37:20.000+0100}, title = {UML2Alloy: A Challenging Model Transformation}, url = {http://dx.doi.org/10.1007/978-3-540-75209-7\_30}, year = 2007 }