Abstract
The work described in this article supports the view that distributed-system component behavior can be captured during system design and directly used to drive the system at runtime. The authors present methods for achieving this one step design and implementation of system behavior through the use of a Petri-net-based executable modeling language. This language provides a direct mapping between modeling constructs and executable code. The work is set in an industrial context through a real problem in electronics-manufacturing shop-floor system design. Through a description of the proposed facilities and their application in an industrial case study, the authors conclude that the decomposition of function, behavior, and system interaction better supports rapid distributed-system development and the required modification of systems to support business-process change.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
