Emulation Abstraction through Middleware - Emulation 102

In my last Emulation 101 post, I talked about why we use emulation instead of expensive real-world systems testing or abstracted software-only simulation. This time, we're talking about the design of our emulation testbed and the software under test.

Emulation Testbed

Our emulation testbed has three main components:

1. The emulation software / framework
2. The software (or system) under test, and
3. The middleware abstraction boundary that makes it possible

I talked about the emulation software and framework in the last post. The software or system under test is the software we're writing that needs to be tested - and emulation is the means we've chosen to do it. The "middleware" is the important part I'd like to discuss today.

Caught Somewhere in Worcester

Last night I took the family to see Iron Maiden - my favorite band of all time and quite possibly the best band in the world, ever.

I saw Iron Maiden in Providence, RI back in January, 1991 - my first concert. Fitting that this was my both of my kids' first concert. They grew up with me playing Maiden in the car, in the house - they knew some songs and even sang along with the chorus to Heaven Can Wait, Fear of the Dark, The Trooper and Wasted Years.