Date of Publication :30th November 2017
Abstract: This paper proposes an idea. The idea is to first express a requirement specification using a formal method. The second step is to work out an implementation of the specification in the form of running code in a standard contemporary programming language. The other step is to identify frequently occurring patterns in the formal specifications. And then direct the conversion from the formal specification to the running code. Intermediate steps shall include the development of a computer-based tool for expressing the requirement specifications. we require another tool that shall develop the conversion of the specifications expressed this way into running code. The steps and process are explained with a hypothetical example.
Reference :
-
- Peterson, James L. (1977) Petri nets ACM computing surveys
- Peterson, james L. (1981), petri net theory and the modeling of systems, prentice Hall
- Matthias Jungel,Ekkart Kindler, and Michael Weber, ―The petri net markup language September 2002
- I. Low, Y. Yang, and H. Lin, ―Validation of Petri net apoptosis models using p-invariant analysis,‖ in Control and Automation, 2009. ICCA 2009. IEEE International Conference on, 2009, pp. 416 –421.
- A. Yakovlev, L. Gomes, and L. Lavagno, Eds., Hardware Design and Petri Nets. Kluwer Academic Publishers, 2000, ‖ISBN0-7923-7791-5, 331 pgs‖
- C.Giraud and R.Valk, Petri Nets for Systems Engineering. A Guide to Modeling, Verification, and Applications. Berlin - Heidelberg - New York: Springer, 2003
- Bernd Grahlmann and Eike Best. PEP — more than a Petri net tool. In Tiziana Margaria and Bernhard Steffen, editors, Tools and Algorithms for the Construction and Analysis of Systems, volume 1055 of Lecture Notes in Computer Science, pages 397–401. Springer Verlag, 1996