ABSTRACT
Basic Petri nets need two slight enhancements to become event-driven Petri nets (EDPNs). The first enables them to express more closely event-driven systems, and the second deals with Petri net markings that express event quiescence, an important notion in object-oriented applications. Taken together, these extensions result in an effective, operational modeling view of software requirements.
