Demo Data from EDBT 2026 / reviewers in the wild / expert
M. M. Kamal Hashmi
dblp:43/2244
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 2006
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 2
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
2 papers |
Electronic design automation · 100% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Electronic design automation › hardware verification and test
hardware verification |
0.1 | 2 | 2006 | Maintaining consistency between systemC and RTL system designs · DAC 2006 Application of High Level Interface-Based Design to Telecommunications System Hardware · DAC 1999 |
Electronic design automation › system-level design
interface-based design |
0.0 | 1 | 1999 | Application of High Level Interface-Based Design to Telecommunications System Hardware · DAC 1999 |
Electronic design automation
system-level design |
0.0 | 1 | 1999 | Application of High Level Interface-Based Design to Telecommunications System Hardware · DAC 1999 |
Electronic design automation
high-level synthesis |
0.0 | 1 | 2006 | Maintaining consistency between systemC and RTL system designs · DAC 2006 |
Electronic design automation › hardware description language
systemc |
0.0 | 1 | 2006 | Maintaining consistency between systemC and RTL system designs · DAC 2006 |
Methods — techniques the papers use, named apart from their topics
verification IP · 0.1transaction-based interfaces · 0.1VHDL+ · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2006 | Maintaining consistency between systemC and RTL system designsabstractWe describe how system design consistency can be maintained across multiple levels of design abstraction using a modular verification IP strategy. This strategy involves delivery of verification IP in an environment independent manner, utilizing a standard system verification architecture that leverages re-usable component verification drivers, transaction-based interfaces, and synchronization through a system-verification master. This enables a single test-bench to be applied for systems modeled both in SystemC, as well as at the RT level. The configuration of the verification testbench is kept consistent with the design by using system-design meta-data described using the specifications of The SPIRIT Consortium. Alistair C. Bruce, M. M. Kamal Hashmi, Andrew Nightingale, Steve Beavis, Nizar Romdhane, Christopher K. Lennard |
DAC | 2 |
| 1999 | Application of High Level Interface-Based Design to Telecommunications System HardwareabstractThe assumption in moving system modelling to higher levels is that this improves the design process by allowing exploration of the architecture, providing an unambiguous specification and catching system errors early.We used the interface-based high level abstractions of VHDL+ in a real design, and in parallel with the actual project to investigate the validity of these claims. Dyson Wilkes, M. M. Kamal Hashmi |
DAC | 2 |