Cellier, F. (1996). Object-Oriented Modeling: Means for Dealing With System Complexity. In Proc. 15th Benelux Meeting on Systems and Control, pages 53-64, Mierlo, The Netherlands.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....only the public interface of an object affects its interconnections with other objects. The same principle can be applied to modeling by making a clear distinction between the physical interactions of an object with its environment (interface) and its internal behavior (implementation)[20, 21]. The advantage of encapsulation is that a system can be modeled by composing (connecting) the interfaces of its sub systems, independently of the future implementations of these subsystems [4, 21, 22] To take full advantage of composable simulation, it is also essential to equip composable ....

F. E. Cellier, "Object-oriented modeling: means for dealing with system complexity," presented at 15th Benelux Meeting on Systems and Control, Mierlo, Netherlands, 1996.

....for the components and connections. Copyright 2001 by ASME of the underlying implementation. The same principle can be applied to modeling by making a clear distinction between the physical interactions of an object with its environment (interface) and its internal behavior (implementation) [12 14]. The advantage of encapsulation is that a system can be modeled by composing and connecting the interfaces of its sub systems, independently of the future implementations of these subsystems [13, 14] We build on these ideas by defining a taxonomy and an inheritance hierarchy of ports and ....

Cellier, F. E., "Object-Oriented Modeling: Means for Dealing with System Complexity," 15th Benelux Meeting on Systems and Control, Mierlo, Netherlands, 1996.

....only the public interface of an object affects its interconnections with other objects. The same principle can be applied to modeling by making a clear distinction between the physical interactions of an object with its environment (interface) and its internal behavior (implementation) [19, 20]. The advantage of encapsulation is that a system can be modeled by composing (connecting) the interfaces of its sub systems, independently of the future implementations of these subsystems [4, 20, 21] A second important principle of object oriented programming is inheritance: objects that are ....

F. E. Cellier, "Object-oriented modeling: means for dealing with system complexity," presented at 15th Benelux Meeting on Systems and Control, Mierlo, Netherlands, 1996.

....Language (CSSL) 12] Models were written as sequential procedures, which implied a fixed mathematical causality. They were implemented as monolithic pieces of software with no separation between model and solver. Subsequently, object oriented principles have been applied to systems modeling [2, 3, 6], with the result that models are easier to create, reuse and share. Causality assignment is performed automatically, and the solver is independent of the model. However, the product design methodology was not closely coupled with the modeling methodology. We further the evolution towards a ....

....be accessed through its public interface, which is independent of the underlying implementation. The same principle can be applied to modeling by making a clear distinction between the physical interactions of an object with its environment (interface) and its internal behavior (implementation) [3, 13]. The advantage of encapsulation is that a system can be modeled by composing and connecting the interfaces of its sub systems, independently of the future implementations of these subsystems [13] In our framework, interaction models can be selected automatically, depending on the ports that are ....

Cellier, F. E., "Object-oriented modeling: means for dealing with system complexity," presented at 15th Benelux Meeting on Systems and Control, Mierlo, Netherlands, 1996.

....be accessed through its public interface, which is independent of the underlying implementation. The same principle can be applied to modeling by making a clear distinction between the physical interactions of an object with its environment (interface) and its internal behavior (implementation) [31, 32]. A model interface consists of ports that discretize the exchange of energy, mass, or information to a finite number of points on the component s interface. When connecting ports, Kirchhoff s network laws are imposed on the port variables. As for the equations describing the internal behavior of ....

Cellier, F. E., "Object-Oriented Modeling: Means for Dealing with System Complexity," 15th Benelux Meeting on Systems and Control, Mierlo, Netherlands, 1996.

....like objects, data encapsulation, generic classes, inheritance or polymorphic operations from the object oriented programming methodology. On the other side, sometimes a simple modular hierarchical approach has already been called object oriented modeling ( Sch95] In accordance with [Pra96] and [Cel96] the authors are of the opinion that modular hierarchical modeling is not inevitable object oriented modeling. Both share various concepts, for instance data encapsulation, but they also show major differences, for instance in making use of inheritance and polymorphic operations by means of ....

F.E. Cellier. Object-oriented modeling: Means for dealing with system complexity. In Proc. of 15th Benelux Systems and Control Conf., Mierlo, March 1996. 12 pp. (http://www.ece.arizona.edu:8001/ cellier /mierlo.html).

No context found.

Cellier, F. (1996). Object-Oriented Modeling: Means for Dealing With System Complexity. In Proc. 15th Benelux Meeting on Systems and Control, pages 53-64, Mierlo, The Netherlands.

No context found.

Cellier, F. (1996). Object-Oriented Modeling: Means for Dealing With System Complexity. In Proc. 15th Benelux Meeting on Systems and Control, pages 53-64, Mierlo, The Netherlands.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC