Summary
We have started down the path of using OOP in a verification system. We talked about the main theme, creating roles and responsibilities by using abstraction. We talked about the common design biases used when we design a verification system.
You probably are still surrounded by clouds of uncertainty. This is understandable. The next chapters are more specific, talking about making classes and the different ways to connect them.
For now, however, know that designing with OOP is about defining roles and responsibilities and making levels of abstraction, a “layering” for which there are many examples in our everyday lives. To achieve your own design objectives in silicon, use your experience to guide the process.
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
That’s right!” shouted Vroomfondel. “We demand rigidly defined areas of doubt and uncertainty!” The Hitchhiker’s Guide to the Galaxy, by Douglas Adams
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2006 Springer Science+Business Media, LLC
About this chapter
Cite this chapter
(2006). Designing with OOP. In: Hardware Verification with C++. Springer, Boston, MA. https://doi.org/10.1007/978-0-387-36254-0_10
Download citation
DOI: https://doi.org/10.1007/978-0-387-36254-0_10
Publisher Name: Springer, Boston, MA
Print ISBN: 978-0-387-25543-9
Online ISBN: 978-0-387-36254-0
eBook Packages: EngineeringEngineering (R0)