Abstract
The article focuses on the transformation of the behavioural UML diagrams modelled by the authors, which reflect the emergent manifestations of the life cycles of working with graph databases (GDB), to models in the form of Petri nets. Such a transformation process was carried out for the diagrams of objects, states, sequences, and activities. The extended UML 2.5 notation and Enterprise Architect 14.0 CASE tool were used in the formation of the project architecture. Modelling of the emergent parallel processes of working with GDBs in the form of a Petri net might initially seem to make the sequence more complicated for the designer to perceive than while using UML modelling, in which the relationships between entities on a diagram are obvious to the user. Conversely, the representation of behavioural models in the form of Petri nets facilitates the reflection of other important emergent points, in particular, by demonstrating objects relationship, dynamic information updates, components, or other necessary information concerning parallel GDB design.
Acknowledgments
The authors would like to express their gratitude to BRL-CAD corporation for the opportunity to openly use and test the source files and plugins and the provided support for the cross-platform methodology. The authors also thank James Lyle Peterson, the author of the monograph [Citation10], which contains the basics of Petri nets theory and has been the core reading for the author of this article for more than 25 years. Additionally, the authors thank Professor Dmitry Zaitsev for providing, by personal example, the motivation to perform the research presented in the article.
Disclosure statement
No potential conflict of interest was reported by the author(s).
Correction Statement
This article has been republished with minor changes. These changes do not impact the academic content of the article.