ABSTRACT
This chapter discusses the continuing comparison of behavioral issues modeled by Event-Driven Petri Nets (EDPNs). EDPN were invented to explicitly clarify the representation of events. Both input and output events do not "just happen" as they do in finite state machines, decision tables, and flowcharts. Separate Event-Driven Petri Nets can easily be composed, either visually in a drawing, or better, in a specially designed database. Token movement and creation in an EDPN requires closer attention. There are only two ways a data place can be marked: either by an initial marking, or by firing a transition. One important difference between EDPNs and traditional Petri nets is that event quiescence can be broken by creating a token in a port input event place. An EDPN engine needs a definition of all input events, output events, places, and the input and output functions relating these to transitions, and an initial marking.
