Talk:Transaction-level modeling
Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This article is rated Start-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:
It is of interest to the following WikiProjects:
WikiProject icon This article is within the scope of WikiProject Systems , which collaborates on articles related to systems and systems science.SystemsWikipedia:WikiProject SystemsTemplate:WikiProject SystemsSystems
??? This article has not yet received a rating on the project's importance scale.
WikiProject icon This article is within the scope of WikiProject Engineering , a collaborative effort to improve the coverage of engineering on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.EngineeringWikipedia:WikiProject EngineeringTemplate:WikiProject EngineeringEngineering
??? This article has not yet received a rating on the project's importance scale.
"Bingo!"
[edit ]- "Communication mechanisms such as busses or FIFOs are modeled as channels [...]"
- Channels?
- "Transaction requests take place by calling interface functions of these channel models [...]"
- Transaction requests?
Thanks for any explanations. --Abdull (talk) 17:41, 29 January 2010 (UTC) [reply ]
- TLM is basically two things put together and used as a single useful concept: event-driven simulation and choosing the right level of abstraction (what constitutes an event for what you want to simulate?). It is the idea to simulate what you need and not what you do not. In TLM nomenclature, a transaction request is an event (communication packet) that is queued/communicated via a channel. A channel an instance of a defined set of interfaces that connect processing blocks together. Think of them as parameters to an API where specific arguments can be assigned to these parameters during specific events/transactions. Basically it is a messaging system. 50.53.15.59 (talk) 10:38, 28 July 2013 (UTC) [reply ]