By Topic

Elimination of duplicate labels in Petri-net-based system specification

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
K. S. Cheung ; Hong Kong Baptist Univ., Kowloon, China ; K. O. Chow

Labelled Petri nets are commonly used for system specification where the locations of conditions are denoted as places with condition labels and the locations of events as transitions with event labels. It is often in a Petri-net-based specification that the same condition label or event label appears in multiple locations. As every condition is finally implemented as a unique state and every event as a unique operation, in order for the system specification to become useful for implementation, all duplicate condition labels and event labels must be eliminated. In this paper, we propose a method for eliminating the duplicate labels. Firing sequences are preserved so that the intended system behaviours will not be altered.

Published in:

The Fifth International Conference on Computer and Information Technology (CIT'05)

Date of Conference:

21-23 Sept. 2005