Typical model design and coding practices include structuring the design, iteratively refining a high-level view of the model down to its final form, and organizing the individual model components so that they are loosely coupled (small number of interface signals) and have strong cohesion (keep strongly related functions in the same architectural body). In addition, to aid the reuse of models, even “throw-away” models should be created with care, and with the thought that others may use it. Otherwise, the model may be hard to maintain, even by the person who wrote it. When modeling in VHDL, it is important to follow standard practices of software engineering. At the highest levels of behavioral abstraction, we may even ignore timing. In behavioral modeling, we are vitally interested in the functionality of the circuit and less interested in its structural composition. ![]() describing how the circuit is to perform. In this module we concentrate on the behavioral view, i.e. In prior lessons, we have concentrated on the basic elements and the structural forms of describing models in VHDL. a component or system) at multiple levels of abstraction. These measures are called coupling and cohesion. There are measures by which the quality of a design of modules and their interaction among them can be measured. They are though, considered as single entity but may refer to each other to work together. As we know, modules are set of instructions put together in order to achieve some tasks. Using VHDL, a system designer can model a circuit (i.e. 7.1 The Software Engineering Discipline 7.2 The Software Life Cycle 7.3 Software Engineering. Coupling and Cohesion When a software program is modularized, its tasks are divided into several modules based on some characteristics.
0 Comments
Leave a Reply. |