BookRags.com Literature Guides Literature
Guides
Criticism & Essays Criticism &
Essays
Questions & Answers Questions &
Answers
Lesson Plans Lesson
Plans
My Bibliography Periodic Table U.S. Presidents Shakespeare Sonnet Shake-Up
Research Anything:        
History | Encyclopedias | Films | News | Create a Bibliography | More... Login | Register | Help
Not What You Meant?  There are 6 definitions for TLM.

Transaction-level modeling

Print-Friendly
About 1 pages (361 words)

Bookmark and Share Know this topic well? Help others and get FREE products!

Transaction-level modeling (TLM) is a high-level approach to modeling digital systems where details of communication among modules are separated from the details of the implementation of functional units or of the communication architecture. Communication mechanisms such as busses or FIFOs are modeled as channels, and are presented to modules using SystemC interface classes. Transaction requests take place by calling interface functions of these channel models, which encapsulate low-level details of the information exchange. At the transaction level, the emphasis is more on the functionality of the data transfers - what data are transferred to and from what locations - and less on their actual implementation, that is, on the actual protocol used for data transfer. This approach makes it easier for the system-level designer to experiment, for example, with different bus architectures (all supporting a common abstract interface) without having to recode models that interact with any of the buses, provided these models interact with the bus though the common interface.[1]

History

Roots of the term TLM, or "Where is the Level in TLM?": TLM was supposed to come out as TBM (= transaction-based modeling). In 2000, Thorsten Grötker, R&D Manager at Synopsys was preparing a presentation on the communication mechanism in what was to become the SystemC 2.0 standard. Gilles Baillieu, then a corporate application engineer at Synopsys, insisted that the new term had to contain "level", as in "register transfer level" or "behavioral level". The fact that TLM does not denote a single level of abstraction but rather a modeling technique didn't make him change this mind. It had to be "level" in order to make it stick. So it became "TLM", and it stuck. Footnote: The use of "transaction-based" was quite normal at that time. Examples include TestBuilder ("transaction-based verification") or IKOS ("transaction-based interface").

References

  1. ^ T. Grötker, S. Liao, G. Martin, S. Swan, System Design with SystemC. Springer, 2002, Chapter 8., pp. 131. ISBN 1402070721 (quoted with permission)

External links

  • SystemC.org - SystemC home page.
  • ESCUG - Prof. Rosenstiel's European SystemC Users Group (ESCUG) webpage.
  • NASCUG - North American SystemC User's Group.
  • LASCUG - Latin American SystemC User's Group.

View More Summaries on Transaction-level modeling
 
Ask any question on Transaction-level modeling and get it answered FAST!
Answer questions in BookRags Q&A and earn points toward
discounted or even FREE Study Guides and other BookRags products!
Learn more about BookRags Q&A
Copyrights
Transaction-level modeling from Wíkipedia. ©2006 by Wíkipedia. Licensed under the GNU Free Documentation License. View a list of authors or edit this article.

Article Navigation
Join BookRagslearn moreJoin BookRags




About BookRags | Customer Service | Report an Error | Terms of Use | Privacy Policy