EZPetri: A Petri net interchange framework for Eclipse based on PNML Adilson Arcoverde, Jr. 1 , Gabriel Alves Jr. 1 , Ricardo Lima 1 , Paulo Maciel 2 , Meuse Oliveira Jr 2 , and Raimundo Barreto 2 1 {aoaj,gabriel alves}@ezpetri.com, ricardo@upe.poli.br Departamento de Sistemas Computacionais – Universidade de Pernambuco Recife, PE, Brazil 2 {prmm, mnoj, rsb}@cin.ufpe.br Centro de Inform´atica – Universidade Federal de Pernambuco Recife, PE, Brazil Abstract. Petri net community has suffered with the lack of a standard format to represent Petri net models. This situation led to an undesir- able tool incompatibility. In order to solve this drawback, the PNML has been proposed. PNML is an interchange file format for Petri nets based on XML. This paper presents a framework, called EZPetri, based on PNML. The EZPetri framework is a perspective of the Eclipse platform. The union of Eclipse and PNML has demonstrated to be an effective instrument for integrating Petri net tools and applications. The paper discusses the principles of the EZPetri framework, and presents three ap- plications integrated into the EZPetri framework: software power estima- tion ; A SystemC model for Petri nets ; and hard real-time software syn- thesis. Such applications have been developed with no knowledge about EZPetri. This is a demonstration of the integration facilities provided by EZPetri. The framework is a fertile ground for combining existing of Petri net tools and applications into a single environment, offering Petri net community a new perspective of integration. 1 Introduction Petri nets is a powerful specification language useful for modelling concurrent, asynchronous, distributed, parallel, non deterministic, and/or stochastic sys- tems. They are also a formal specification technique with powerful methods for qualitative and quantitative analysis [mur89, rei85]. Since their introduction by C. A. Petri in 1960, Petri nets has been widely applied in many fields of science and industry. There are numerous Petri net tools with support for specific type of net (high- level, low-level, timed, stochastic, etc.). The lack of a standard forced Petri net tools designers to create their own file format. Hereby, a model created through a Petri net tool cannot be read by other tools. This assertion is true even for tools supporting the same Petri net type. This situation has motivated Petri net community towards creating a Petri net interchange format. In order to define a single XML-based file for any Petri