Ready.

Page 37. This page is in the page-by-page raw-dumps section.



((Continued from page 36.))

And next, with E-nets, a transition procedure may be associated with any transition, for accessing/modifying the data (as encoded in the token-attributes). The copycat82 (on p.37), tells the similar: "(vi) Each component is associated with a data transfer specification which represents the data flow through the component. The last three items do not exist in Petri nets and are added to represent the data aspects of design." - the "first" of those "last three" being the advertised but un-integrated abstract-data-types, also associated with the places, similar to the data objects. In other words, this is E-nets, except a bit of make-up.





Further Reading

(page-by-page raw-dumps section) . . . . . previous . . . . . next




Any Questions?: . . (Request Content . . . . . Correct Errors . . . . . Submit Case Study . . . . . Report Content Similarity.)

LastUpdated: June 10, 2004
Page-version: 0_0_1 (Links-update: June 18, 2004)
Written by: Ahmed Ferzen/Ferzan R Midyat-Zilan (or, Earth)
Copyright (c) [2002,] 2003, 2004 Ferzan Midyat. All rights reserved.