Category	Featured projects
scm	Subversion, Subclipse, TortoiseSVN, RapidSVN
issuetrack	Scarab
requirements	xmlbasedsrs
design	ArgoUML
techcomm	SubEtha, eyebrowse, midgard, cowiki
construction	antelope, scons, frameworx, build-interceptor, propel, phing
testing	maxq, aut
deployment	current
process	ReadySET
libraries	GEF, Axion, Style, SSTree
Over 500 more tools...

Subversion and IDEs
Eclipse
JDeveloper
NetBeans
Visual Studio

Documentation

How to use the module

Launching ArgoPNO

The module comes as a jar archive, you need to put it in your classpath before starting ArgoUML (putting the archive into the ext directory doesn't work for the moment).

You can also download the source archive. This archive must be uncompressed into the modules directory of ArgoUML (this directory is placed at the same level as src_new directory).

Once you've uncompressed the archive, go into modules/argopno directory and type ant run, ArgoUML should launch with ArgoPNO module enabled.

Utilisation of ArgoPNO

ArgoPNO adds to items to ArgoUML menus :

• PN Diagram in Create Diagram menu will create a new diagram, holded by current namespace (packages, classifiers and models are namespaces).
• PNML in the Tools menu provides functions to export files to PNML and to read them back (for now, you will loose some graphic properties such as label placement and curves). Apparently, PNML will become the next Petri Net standard file format.

In the screenshot above, you can see ArgoUML's main window, showing a PN Diagram and the property panel for a place. There is a property panel for every Petri Net element on the diagram (including tokens) where you can watch and change the properties of an element

Simulation

ArgoPNO provides a little manual simulator for the Petri Net you are editing. When you select Transitions (the black rectangles) you can click on the button under the figure to fire the transition. If the transition is fireable (all incoming place must have a number of tokens superior or equal to the number showed on the Arc that leads to the transition), then the tokens in incoming places will be consumed and new tokens will be created in the outgoing places (for each place the number of token that will be created/destroy is equal to the number shown on the arc (by default 1)).

The image above shows a fireable transition (it is the simplest case in fact because there is only one incoming place and one outgoing place and arcs only have a weight of 1).