Behavior Models Object Types and Operations

Chapter 2, Static Models Object Attributes and Invariants, describes how attributes abstract variations in the implementation of object state. Chapter 3, Behavior Models Object Types and Operations, describes how operation specifications describe externally visible behavior of an object, independently of algorithmic and representation decisions. 

Chapter 3 Behavior Models Object Types and Operations... 

We describe an object s behavior using a type, with two parts to its specification the operation specifications (usually pre- and postconditions) defining what it does and the static model, providing the vocabulary of terms for the operation specs. 

UML treats attributes on a type as abstract but does not permit attributes to take parameters instead, you can use an operation that has been marked as read-only. Catalysis encourages a slightly different way of thinking about an object Some things are abstractions of its state, and others are abstractions of its behaviors. Attributes, parameterized attributes, and invariants all help to define the model of state operation specifications define the behaviors. There are no preconditions and postconditions on attributes, because they represent state there can be conditional invariants on an attribute, and there can be syntactic shortcuts for expressing them, but they are not pre- and postconditions ... 

There are as many different types of fire models as there are design and operational objectives for engineers, ranging from macroscopic fire-in-a-room scenarios to the microscopic study of the behavior of structural composite material at the level of resin chemistry. Different models are required depending on the specific aspect of the fire... 

The behavior of anything from a simple object to a large, complex system can be specified with a type specification, which has actions specified in terms of a model. The rules for joining and subtyping can be described as operations that you perform on the specifi-... 

The proposed standard for object-relational database languages is SQL-99. Figure 14 shows how Fig. 4 could be specified in SQL-99. Note the use of ROW TYPE to specify a complex domain, the use of REF to denote tuple identifiers and the use of type constructors such as SET and LIST. Note also that, unlike ODL (cf. Fig. 12), in SQL-99 inverse relationships are not declared. Note, finally, how gene is modeled as including operations, as indicated by the keyword FUNCTION introducing the behavioral part of the specification of gene. 

A data reconciliation model has been built for the plant. This is an optimization model constituted by an objective function that corresponds to the minimization of the weighted errors on measurements and of a list of constraints representing the physics of the process operations. The constraints are mass and energy balances, separation rules, and thermodynamic behaviors. The model has been developed by using the equation solver type data reconciliation software VALI III (Belsim s.a, 2001). 

Modeling these problems require extensive information from key components of supply chain to characterize these components individually and collectively. Depending on the approach and its underlying objective, research effort that has been undertaken to address supply chain operation problems can be classified into two main t5q)es. The first type of supply chain operation research entails process simulation of various supply chain entities to capture the supply chain dynamics. In general, supply chain simulation models involve mathematical representation of the characteristics of these individual supply chain entities as well as behavioral relationships among them. 

---