On the Formalisation of an Application Integration Language Using Z Notation

Mauri J. Klein, Sandro Sawicki, Fabricia Roos-Frantz, Rafael Z. Frantz

Abstract

Companies rely on applications in their software ecosystem to provide IT support for their business processes. It is common that these applications were not designed taking integration into account, which makes hard their reuse. Enterprise Application Integration (EAI) focuses on the design and implementation of integration solutions. The demand for integration has motivated the rapid growing of tools to support the construction of EAI solutions. Guaraná is a proposal that can be used to design and implement EAI solutions, and different from other proposals includes a monitoring system that can be configured using a rule-based language to endow solutions with fault-tolerance. Although Guaraná is available, it has not been formalised yet. This is a limitation since it is not possible to validate the rules written by software engineers, using the rule-based language, to ensure that all possibilities of failure in a given EAI solution are covered. Besides, it is not possible to generate automatically these rules based on the semantics of the EAI solution. In this paper we provide a formal specification of the language provided by Guaraná to design EAI solutions, using Z notation.

References

  1. Bowen, J. P. and Hinchey, M. G. (2006). Ten Commandments of Formal Methods ...Ten Years Later. IEEE Computer, 39(1):40-48.
  2. Dijkstra, E. W. (1975). Guarded Commands, Nondeterminacy and Formal Derivation of Programs. Commun. ACM, 18(8):453-457.
  3. Dossot, D. and D'Emic, J. (2009). Mule in Action. Manning.
  4. Fisher, M., Partner, J., Bogoevici, M., and Fuld, I. (2010). Spring Integration in Action. Manning.
  5. Floyd, R. W. (1967). Assigning meanings to programs. In Proceedings of a Symposium on Applied Mathematics, volume 19 of Mathematical Aspects of Computer Science, pages 19-31.
  6. Frantz, R. Z., Quintero, A. M. R., and Corchuelo, R. (2011). A Domain-Specific Language to Design Enterprise Application Integration Solutions. Int. J. Cooperative Inf. Syst., 20(2):143-176.
  7. Goodenough, J. B. (1975). Exception handling: Issues and proposed notation. Communications of the ACM, 18(12):683-696.
  8. Harel, D. and Rumpe, B. (2004). Meaningful modeling: What's the semantics of "semantics"? Computer, 37(10):64-72.
  9. Hohpe, G. and Woolf, B. (2003). Enterprise Integration Patterns - Designing, Building, and Deploying Messaging Solutions. Addison-Wesley.
  10. Hong, S. N. and Mannino, M. V. (1995). Formal semantics of the unified modeling language {LU} . Decision Support Systems, 13(3-4):263-293.
  11. Ibsen, C. and Anstey, J. (2010). Camel in Action. Manning.
  12. Kaliappan, P. S. and König, H. (2012). On the Formalization of UML Activities for Component-based Protocol Design Specifications. In Proceedings of the 38th International Conference on Current Trends in Theory and Practice of Computer Science, SOFSEM'12, pages 479- 491.
  13. Kim, S.-K. and Carrington, D. (1999). Formalizing the UML Class Diagram Using object-Z. In Proceedings of the 2Nd International Conference on The Unified Modeling Language: Beyond the Standard, UML'99, pages 83-98.
  14. Messerschmitt, D. and Szyperski, C. A. (2003). Software Ecosystem: Understanding an Indispensable Technology and Industry. MIT Press.
  15. Mostafa, A. M., Ismail, M. A., Bolok, H. E., and Saad, E. M. (2007). Toward a Formalization of UML2.0 Metamodel using Z Specifications. In Software Engineering, Artificial Intelligence, Networking, and Parallel/Distributed Computing, 2007. SNPD 2007. Eighth ACIS International Conference on, volume 1, pages 694- 701.
  16. OMG (2011). UML 2.4 Superstructure Specification.
  17. OMG (2012). OCL 2.3.1 Object Constraint Language.
  18. Shroff, M. and France, R. B. (1997). Towards a formalization of UML class structures in Z. In COMPSAC, pages 646-651. IEEE Computer Society.
  19. Spivey, J. M. (1992). The Z Notation: A Reference Manual. Prentice Hall.
  20. van Lamsweerde, A. (2000). Formal specification: a roadmap. In ICSE - Future of SE Track, pages 147-159.
  21. Vidal, J. C., Lama, M., and BugarÃn, A. (2012). Toward the use of Petri nets for the formalization of OWL-S choreographies. Knowledge and Information Systems, 32(3):629-665.
  22. Wing, J., Woodcock, J., and Davies, J. (1999). In FM'99 - Formal Methods: World Congress on Formal Methods in the Development of Computing Systems, volume 1708- 1709 of LNCS. Springer-Verlag.
Download


Paper Citation


in Harvard Style

J. Klein M., Sawicki S., Roos-Frantz F. and Z. Frantz R. (2014). On the Formalisation of an Application Integration Language Using Z Notation . In Proceedings of the 16th International Conference on Enterprise Information Systems - Volume 1: ICEIS, ISBN 978-989-758-027-7, pages 314-319. DOI: 10.5220/0004967003140319


in Bibtex Style

@conference{iceis14,
author={Mauri J. Klein and Sandro Sawicki and Fabricia Roos-Frantz and Rafael Z. Frantz},
title={On the Formalisation of an Application Integration Language Using Z Notation},
booktitle={Proceedings of the 16th International Conference on Enterprise Information Systems - Volume 1: ICEIS,},
year={2014},
pages={314-319},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0004967003140319},
isbn={978-989-758-027-7},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 16th International Conference on Enterprise Information Systems - Volume 1: ICEIS,
TI - On the Formalisation of an Application Integration Language Using Z Notation
SN - 978-989-758-027-7
AU - J. Klein M.
AU - Sawicki S.
AU - Roos-Frantz F.
AU - Z. Frantz R.
PY - 2014
SP - 314
EP - 319
DO - 10.5220/0004967003140319