Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>UML Activity Diagrams can be expressed as Petri nets (e.g. <a href="http://www.google.ru/url?sa=t&amp;source=web&amp;ct=res&amp;cd=1&amp;ved=0CAkQFjAA&amp;url=http%3A%2F%2Fwww.emis.de%2Fjournals%2FNSJOM%2FPapers%2F30_3%2FNSJOM_30_3_161_171.pdf&amp;ei=IkY1S8zSFsfX-QbF1e2uCg&amp;usg=AFQjCNFGCRGjG-9vdz9JH04DRrcXJkG0KQ&amp;sig2=U_ZLdKojOtxtm74odbWKSw" rel="nofollow noreferrer">see this paper</a>). Unfortunately I don't know any good industrial oriented tools for simulation of Petri Nets or Activity Diagram (but there are many academic projects which you can easily find). </p> <p>Are you sure that you want to simulate your model (by simulation I mean that you actually want to sit and look how your Perti net is being executed)? Usually this type of analysis is applicable for small and simple algorithms. In real world situation you probably would like to do <a href="http://en.wikipedia.org/wiki/Model_checking" rel="nofollow noreferrer">model checking</a> of your algorithm rather than simulation. I would recommend you to check SPIN (used by many companies, e.g. Siemens). Also I have a positive experience with <a href="http://en.wikipedia.org/wiki/Alloy_Analyzer" rel="nofollow noreferrer">Alloy</a> and <a href="http://www.prismmodelchecker.org/casestudies/index.php" rel="nofollow noreferrer">Prism</a>. But if your focus is on verifying parallel algorithms I would suggest you to consider SPIN first.</p> <p>Edit: I checked some tools for simulation and I can advise looking at </p> <p>1) <a href="http://sourceforge.net/projects/visual-petri/" rel="nofollow noreferrer">http://sourceforge.net/projects/visual-petri/</a></p> <p>2) <a href="http://www.renew.de/" rel="nofollow noreferrer">http://www.renew.de/</a></p> <p>3) <a href="http://www.winpesim.de/index.html" rel="nofollow noreferrer">http://www.winpesim.de/index.html</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload