Skip to main content
padlock icon - secure page this page is secure

The 3DOM object model for the design of manufacturing systems

Buy Article:

$61.00 + tax (Refund Policy)

Most real-world systems are usually characterized by complex interactions between a variety of components that include distributed and parallel software, hardware and communication components. In particular, a manufacturing system consists of a group of interaction subsystems. However, the architecture of a manufacturing system requires money and time when organization, products market constraints must change. This conclusion is due to the fact that the classical architectures of manufacturing systems is for representing static relationships, but it is not suitable for representing dynamic relationships. Advanced tools for design and simulation are required to help implement such systems. Object-oriented methodologies are becoming the mainstream approach for software development in general because they enable software houses to develop applications in a manpower effective way. This applies all the way down from analysis and design to implementation, testing and maintenance the latter includes the evolution that is caused by ever changing requirements . The increased modularity that is inherent to the use of objects is a crucial advantage when modifying specific parts of the product, when porting applications with respect to varying infrastructure, when isolating errors, etc. However, the design and implementation of concurrent programs has proven to be extremely difficult. Concurrent programs are difficult to design, implement and maintain because changes in a concurrent program adding new components, modification of existing components requires re-implementation of some or all components. The problem can be summarized by the fact that if the interaction constraints are implemented in the methods of an object, these methods may not be inherited because subclasses may not interact in the same way and with the same objects as their super-classes. To solve this problem, we propose to distinguish and to separate two behaviours: the behaviour which specifies the operations performed by a given class of objects during the execution of an application and the behaviour which consists in the interactions with other classes and determines the manner in which a class affects or is affected by other classes or by events. This paper presents an object model 3DOM or threedimensional object model based on the class model to which a part called scenario is added. This part puts the object into a given system or environment and defines the interactions that it has with other objects.
No Reference information available - sign in for access.
No Citation information available - sign in for access.
No Supplementary Data.
No Article Media
No Metrics

Document Type: Research Article

Publication date: January 1, 1997

More about this publication?
  • Access Key
  • Free content
  • Partial Free content
  • New content
  • Open access content
  • Partial Open access content
  • Subscribed content
  • Partial Subscribed content
  • Free trial content
Cookie Policy
Cookie Policy
Ingenta Connect website makes use of cookies so as to keep track of data that you have filled in. I am Happy with this Find out more