Skip to main content
Article thumbnail
Location of Repository


By Irmantas Katilius, Ignas Skučas and Vida Melninkaitė


Abstract. This paper reviews the most archetypal features of UML and Petri nets. Formed modeling structural scheme reflects the trends of designing modern information systems. This paper also overviews the possibility of converting UML net into Petri net. At the end, the paper gives a conclusion, and also a prospective of further research – using methods presented here. Development of organizational information systems (IS) recently becomes an important subject. Lately, the Unified Modeling Language (UML) became the standard in creating software, and in designing relatively simple organizational information systems. Some UML diagrams are also used for organizational sectional modeling, reengineering of business processes, and process analysis. By current view UML is used for specification of task sequences, and in the process of creating software for generation of program code class diagrams are being used. Class diagrams are sourced using activity diagrams, which are based on empirical reasoning and are not described by mathematical methods. UML methodology only allows very limited modeling of simple systems, to say nothing of the possibilities to evaluate process dynamics. That’s why Petri nets are often tried to use for designing of systems. High development of IS is determined by formal mathematical methods. Petri nets are formalism for performing process characterized by parallel links analysis. Petri nets characterize parallel structures, flexible modeling, and highly developed mathematica

Year: 2009
OAI identifier: oai:CiteSeerX.psu:
Provided by: CiteSeerX
Download PDF:
Sorry, we are unable to provide the full text but you may find it at the following location(s):
  • (external link)
  • (external link)
  • Suggested articles

    To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.