Behavioral description

The term model-based can be a source of confusion because descriptions of any aspects of reality can be considered to be models. Any KBS is model based in this sense. For some time, researchers in KBS approaches (Venkatasubramanian and Rich, 1988 Finch and Kramer, 1988 Kramer and Mah, 1994 McDowell and Davis, 1991,1992) have been using model-based to refer to systems that rely on models of the processes that are the objects of the intent of the system. This section will avoid confusion by using the term model to refer to the type of model in which the device under consideration is described largely in terms of components, relations between components, and some sort of behavioral descriptions of components (Chandrasekaran, 1991). In other words, model-based is synonymous with device-centered. Figure 27 shows a diagram displaying relationships among components. The bubble shows a local model associated with one of the components that relates input-output relationships for flow, temperature, and composition. 

This was the first documented study of exposure of a military volunteer to a threshold dose of both i.m. BZ and oral LSD, given together. It included a careful baseline for each measurement used. Clinical observations were scheduled at 1, 2, 3, 4, 5, 6, 10, 24, 48 and 72 hours after administration of drug. Vital signs and neurological status were recorded at approximately the same intervals. The examining physician frequently documented mental status. These data were less than optimal due to the relative infrequency of observations and the sparseness of behavioral descriptions. Even in combination, the doses used were too small to cause more than minimal effects. 

Documents have a rich internal structure with mutual relations between their parts, called increments. For example, the behavioral description of an apparatus consists of terms with mutual syntactic and semantical relations. 

Especially, there are many fine-grained relationships between increments of different documents (see again Fig. 1.4). E.g., parts of the behavioral description of a plant are in close relation to the structural description. These fine-grained relations are needed to estimate the effort of changes, to carry out changes, to check consistency of the changes, etc. 

Functionality Interaction human-model, operating / behavior Description language, feedback, intuitive user interaction... 

Elements Knowledge/ Behavior Descriptions Knowledge introductory Knowledge introductory Knowledge introductory... 

Based on the Taxonomy Head-Heart-Hands Elements Behavior Descriptions... 

Behavior Descriptions Knowledge deep level comprehension of any one or all aspects or dimensions of sustainability (such as the managing the complexity of elements of the natural environment system, how renewable energy will impact society, regional solutions for fair water use), and... 

The behavioral descriptions at this level are purely black-box They describe the inputs and outputs of each component and their relationships only in terms of externally visible behavior. Essentially it represents the transfer function across the component. Any of these components (except the humans, of course) could be implemented either in hardware or software. Some of the TCAS surveillance... 

Boussebha, D. Giambiasi, N. and Magnier, J. (1992) Temporal Verification of Behavioral Descriptions in VHDL. EURO-VHDL 92 169-176. 

To evaluate the AG driven hardware compiler, a representative example d an automatically synthesized design is presented, hi figure 4, the behavioral description d the differential equation sdver presmted in (Dutt, 1992) is given. The description passes through YACC for scheduling and then through the... 

For defining the state space of a module, we exactly one so-called behavior description (Behavior) for each dimension of the state space. A behavior description can also be represented graphically by equivalent behavior diagrams, as exemplified below in the case studies. Behavior descriptions are finite state... 

Within amodule. Boolean conditions, depending on the states of this module and of aU its sub-modules, can be specified. These Boolean conditions, in turn, are used to guard transitions of the behavior descriptions, i.e. a transition may only take place if the corresponding guard condition is satisfied. Furthermore in each module, single instances or containers of instances of the modules types within the scope can be defined to express the internal structure of a module. 

The name beh name of a behavior will be referred to in the behavior hst of those modules implementing this kind of behavior. Internally, the behavior description defines the set of states and aU possible state transitions. It is also possible that a behavior inherits from another behavior. 

Such conditions are used to guard transitions of behavior descriptions. 

The procedural model for functional units used by ProcVhdl are well matched by the behavioral descriptions in Vhdl, whereas the functional descriptions of many older hardware definition languages have insufficient expressive power. 

The capabilities of a primitive hardware unit are specified by a number of behavior descriptions corresponding to each of its states. The behavior can change from state to state (e.g., an ALU may in one state execute a logic function and in another an arithmetic operation). Therefore, we say that an AST node has a temporal behavior. 

It has been demonstrated that the proposed design script for regular array synthesis leads to efficiently designed architectures. The script has been developed in the context of the Cathedral project. The re-indexing and localization tools, developed respectively at IMEC and IRISA, can be used to allow a higher input behavioral description of an application. The transformations provided by these tools can also be useful in other architecture synthesis areas. 

As shown in figure 1, behavioral synthesis starts with two kinds of information a behavioral description and an external library of functional units (FUs). The external library of FUs may include standard execution units (adders, multipliers, ALUs, etc.) as well as more complex units defined by the designer. These may be large, complex blocks such as cache memories, I/O units, and so on. 

---