Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Behavior description language

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

S.Kato, T.Sasaki, FDL A Structural Behavior Description Language , CHDL 83,pp 137-152,1983... [Pg.151]

Figure 3.1 compares the characteristics of SFL with conventional functional or behavioral description languages. [Pg.206]

The SFL behavioral simulator, named SECONDS, directly interprets the SFL source. Since it does not require an expansion process into connective description, SECONDS can begin simulation very quickly. Most conventional behavioral simulators require expansion processes, because their basic behavioral description languages allow the use of connective description mixed with behavioral description. [Pg.210]

The Verilog Hardware Description Language, often referred to as Verilog HDL, is an IEEE standard (IEEE Std 1364). The language can be used to describe the behavior, sequential and concurrent, or structure of a model. It can support the description of a design at multiple levels of ab-... [Pg.227]

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. [Pg.42]

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... [Pg.10]

R. Camposano and R.M. Tabet, "Design Representation for the Synthesis of Behavioral VHDL Models , in Computer Hardware Description Languages and their AppUcations (Proc. of the 9th Int. Conf. on CHDLs), John A. Darringer and FVanz J. Rammig (Editors), pages 4958-205, North Holland, June 1989. [Pg.97]

W. Rosenstiel and R. Camposano, Synthesizing Circuits form Behavioral Level Specifications , in Computer Hardware Description Languages and their Applications (Proc. of the 7th Int. [Pg.155]

As described in Chapter 2, when the ISPS behavioral description is mapped onto the VT, procedures and labeled blocks of operations are mapped onto VT subgraphs called vtbodies. CALL and LEAVE operations are used to transfer the flow of control between these vtbodies, similar to the CALL and RETURN operations in many programming languages. [Pg.46]

DuCH91] N.D. Dutt, J.Cho and T. Hadley, A User Interface for VHDL Behavioral Modeling, Symp. on Computer Hardware Description Languages, Marseille, 1991. [Pg.24]

K.Wakabayashi, An Algorithmic Behavior and Function Description Language and a Logic Synthesis Technique , Proc. of the 35th IPSJ,... [Pg.151]

Another problem with existing high-level description languages is that they usually have a built-in timing methodology that makes it difficult to express interfaces that include both synchronous and asynchronous behavior. These are quite common at the boundary between circuits, for example, when connecting two synchronous units that have different clocks or when connecting a synchronous device to an asynchronous communication bus. [Pg.156]

T. Amon, G. Borriello, C. Sequin. Operation/Event Graphs A Design Representation for Timing Behavior. Proceedings of the 10th IFIP International Conference on Computer Hardware Description Languages (CHDL 91), April 1991. [Pg.175]

Wolfgang Rosentiel and Raul Camposano. Synthesizing circuits from behavioral level specifications. In C. J. Koomen and T. Moto-oka, editors. Computer Hardware Description Languages and their Applications, pages 391-403. Elsevier Science blishers B. V., 1985. [Pg.251]

The system model can describe the vehicle interfaces and the aspects described under the vehicle system models would be valid. The components interfaces could be defined the same way so that the behavior of the components and their functions or functionalities can be described, analyzed, or verified. Furthermore, a model of the microcontroller could be used in order to describe, analyze or verify the hardware-software-interface and the behavior of the software within the microcontroller (environment). Nowadays even in the silicon models are widely used to describe the functionalities of semiconductors and validate those against the different realized samples. This means that a system approach is used in order to display the inner behavior of the silicon. ADL (architecture description languages) are widely used for that purpose. [Pg.242]

The Universal Modeling Language is used to describe a software system [4, 5], Several kinds of diagrams exist to model the diverse properties of the system. Thus a description of the system can be developed that enables the systematic and uniform documentation of the system. The class diagram, for example, represents the classes and their relationships. But also interacting diagrams exist, to describe the dynamic behavior of the system and its objects. [Pg.628]


See other pages where Behavior description language is mentioned: [Pg.130]    [Pg.205]    [Pg.206]    [Pg.283]    [Pg.130]    [Pg.205]    [Pg.206]    [Pg.283]    [Pg.18]    [Pg.27]    [Pg.37]    [Pg.235]    [Pg.60]    [Pg.65]    [Pg.66]    [Pg.238]    [Pg.276]    [Pg.12]    [Pg.806]    [Pg.985]    [Pg.985]    [Pg.5]    [Pg.28]    [Pg.92]    [Pg.22]    [Pg.2]    [Pg.10]    [Pg.178]    [Pg.181]    [Pg.382]    [Pg.4]    [Pg.19]    [Pg.20]    [Pg.61]    [Pg.237]    [Pg.256]   
See also in sourсe #XX -- [ Pg.130 ]




SEARCH



Behavior language

Behavioral description

© 2024 chempedia.info