Why use such a heavily object-oriented model?
The degree of object orientation used in IEC 61499 is necessary in order to achieve the required level of distributability of encapsulated, reusable software modules (function blocks). • Isn’t this very expensive to implement? Not necessarily; a full object-oriented implementation is not required by the IEC 61499 model – only that the externally visible behaviors of a compliant device conform to the requirements for the device compliance class as defined in subclause 5.2 of IEC 61499-1. The implementation of a “Class 0” device can be quite economical. • Why not use a general-purpose distributed object model, like DCOM or CORBA? • Implementation of the features specified for these information-technology models would be too expensive, and their performance would almost always be too slow, for use in a distributed real-time industrial-process measurement and control system (IPMCS). • There is no standard, easily understood graphical model for representing the interconnections of events an
Related Questions
- How do elementary school programs that rely heavily on a pull-out model compare with inclusion-type programs? What are the pros and cons of ability grouping in an inclusion-type program?
- This model relies heavily on partitioning. How do I handle queries that need to span multiple partitions?
- Why use such a heavily object-oriented model?
