Behavioral domain

Studies with the 5-HTu agonist sumatriptan demonstrated that altered neuroendocrine response reflecting 5-HTid sensistivity significantly correlates with severity of the repetitive behavior domain (Hollander et al., 2000). In addition, there is evidence for improvement in global severity as well as improvements in both social deficits and decreased repetitive behavior in autistic individuals with serotonin reuptake inhibitor (SRI) treatment (Gordon et al., 1993, McDougle et al., 1996, Hollander et al, 1998). There is substantial evi-... 

Generally, several different models of anxiety that target different domains (e.g., locomotion/exploration, risk assessment, defensive responses) are necessary in order to more fully characterize drug effects or a mutant mouse phenotype. The use of a single model, or only models targeting one particular behavioral domain, may not be sufficient. 

States Are quantities (numerical or categorical) of the behavioral domain (e.g., heat transfer, fluid dynamics, psychology). States change with respect to time, implying the dynamics of the system. For example, in Fig. 1, the states of the structure are represented by the distance Lq between the electric motor and the piston, the torque T of the electric motor, or the displacement of the pistons. 

In the above representation, the starting point for high-level synthesis is a behavioral domain specification at levels above the logic level. We will assume that the behavior is specified in a sequential (procedural, imperative) Hardware Description Language (HDL) such as sequential VHDL. Synchronous systems can be described in terms of a simple model of time using basic time units called control steps (cycles, or states of a finite automaton). The initial design... 

The Behavioral Domain describes the behavior, or functionality, of the design, either as a complete, program-like description, or as set of behavioral descriptions. For example, at the Algorithmic level, the Behavioral Domain might be represented by a description of the algorithm to be implemented. Variables and the operations on them... 

The Structural Domain describes the hierarchical logical implementation of the design in an abstract, technology independent fashion. For example, at the Register-Transfer Level the Structural Domain describes the design in terms of an abstract set of functional units, multiplexors, and registers needed to implement the register transfers required by the Behavioral Domain, plus a controller and control ROM. 

Non-isomorphism. The hierarchical decompositions in each of the three domains of description may be non-isomorphic, meaning that there is not a one-to-one mapping between the decomposition structures. For example. Figure 2-2 shows the synthesis of two operators in the Behavioral Domain, an add operator and a subtract operator, with a single Structural Domain components, an arithmetic-logic unit that... 

System Level. At the System Level, the Behavioral Domain describes the behavior of a system as a set of performance specifications, or gross operational characteristics. It is concerned with operations that manipulate data and store results, without being concerned with the algorithms describing the details of how this occurs. The Structural Domain components that correspond to these performance specifications are processors, memory units, switches, busses, and device controllers. In the Physical Domain, high-level physical partitioning of the design (e.g. onto cabinets, boards or chips) may be described. 

In the Structural Domain, hardware subsystems (e.g., separate data paths and controllers) represent the processes of the Behavioral Domain. These hardware subsystems are thought of as operating concurrently with each other, although their internal operation may include both sequential behavioral and statement-level parallelism. 

Language Usage. Following the conventions described in our model of representation, the ISPS behavioral domain description is maintained as a pure behavior, represented separately from the structure or physical information. That is, the use of a "+", or operator in ISPS only specifies that the operation must take place on the named values. It does not specify the actual functional units to be used for each of the operations, the memory units in which the values are to be stored, nor does it specify the order in which the operations will take place. Thus, the Workbench has the freedom to design any hardware and control sequence implementation with the proviso that the final implementation s behavior match that specified by the lexical data-flow ordering and the required (NEXT) ordering of the original behavior. 

This is within the behavioral domain, including factors such as actions, words, demeanor, dexterity, motor coordination, and ph) sical capabflities. Skills are a major consideration in the training/leaming process, where the major goal is to prepare people to do something, to perform specific tasks. 

---