Object-Oriented Model Views

Static To explain what is there And it comes under two factors structure and topology. Structure represents the subcomponents of the object, while topology represents the interconnection among the different obiects. 

Dynamic Or behavior, to explain what happened and when it happened  

Function Or operational, to show the algorithm or the computations of how it happened 

The main purpose of developing plant lifecycle model is to understand and analyze the different aetivities within the plant lifecycle and also to develop the different systems to automate the different funetions within the plant lifecycle. As the plant lifecycle is complex so it is essential to have a simple approaeh to develop such complex model. Our proposal in this book is to use the simple 00 modeling coneept to construct the plant lifeeycle models. By representing the plant model in UML-based repository will enable converting P ID into active plant object-oriented model, which is informative about all attributes and specifications of each model element i.e. pump, reactor, etc. 

A process plant has a static dimension that can be represented as structure and topology (Pohjola et al., 1997). The structure expresses the decomposition of a plant unit. The topology reflects the connectivity between units within the same level of abstraction. The plant can be divided into control group units (CGUs). The concept of CGU is described by Naka (1999). 

---

HLA has an object-oriented world-view, which is not to be confused with OOP (object-oriented programming) because it doesn t specify the methods of objects, since in the common case this is not info to be transferred between federates. This view does only define how a federate must communicate with other federates, while it doesn t consider the internal representation of each federate. So, a simulation object model (SOM) is built, which defines what kind of data federates have to exchange with each other. Furthermore, a meta-object model, the federation object model (FOM), collects all the classes defined by each participant to the federation in order to give a description of all shared information [56]. 

It is important to note that none of the flows (organization, function, output, and information flow, respectively) illustrated above is capable of completely modeling the entire business process. We must therefore combine all these perspectives. To this end, one of the views should be selected as a foundation and then be integrated into the others. The function view is closest to the definition of a business process and is therefore typically used as a starting point. However, in the context of object-oriented enterprise modeling information, flows can serve as a starting point as well. 

We can equate the term method used in object-oriented analysis with the term function. Due to the fact that classes are frequently data classes (such as customers, suppliers, orders, etc.), they represent the link between data and function view. We have already experienced object-oriented class design when we discussed the levels of abstraction and the examples of the modeling views (see Section 1.2 as well as Section 3.1), so we can skim the properties of creating object-oriented classes. 

History of Computational Chemistry A Personal View Molecular Models Visualization Object-oriented Programming. 

Through recent research, we have learned that humans are easily overburdened if information in writing or pictures etc., is offered in a linear, unstructured way. Information needs to be structured in order to be useful and usable. This view is particularly important in education. One model structure of information is offered by the approach of object-orientation cutting-up complex information into smaller entities which are better comprehensible for the human mind. Furthermore, similar components of information can be summarised in order to correspond to view-orientation approaches. Other information can be modelled to correspond to the approach of process-orientation (see fig. 2). 

DIS), an extensible object-oriented database model, which has also been used for VLSI/CAD application environments (see and ). The 3DIS provides an approach in which data and the descriptive information about the data are handled in a uniform framework. It is especially suited to represent information objects of various levels of abstraction and modality, and supports various views of the same data which is essential for this type of engineering database. In addition to that, the EDEN system supports a number of novel modeling constructs, one of which makes it possible to interpret parts of the data as graphs and to express retrievals, constraints and updates in terms of graph operations. 

The solid-flame model, presented in Section 3.5.2, is more realistic than the point-source model. It addresses the fireball s dimensions, its surface-emissive power, atmospheric attenuation, and view factor. The latter factor includes the object s orientation relative to the fireball and its distance from the fireball s center. This section provides information on emissive power for use in calculations beyond that presented in Section 3.5.2. Furthermore, view factors applicable to fireballs are discussed in more detail. 

Cholesterol not only has more atoms and more connectivity than does pentane, but it differs in another important way. Physical models tell us that all of the carbon atoms of pentane could lie in one plane, but those of cholesterol carmot. Therefore, our drawing for cholesterol must have some way to indicate not only connectivity but also the orientation of the various parts of the molecule. We view the drawing as a projection (a shadow, in effect) of a real object, and we often use angles and line thicknesses to convey three-dimensional information. Objects in the distance (behind the plane of the main scene) are reduced in size and/or angled to give an effect of distance, while objects in the front of the main scene are large and bold. 

---