|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Peter C. Mehlitz, John Penix, "Design for Verification with Dynamic Assertions," 2012 35th Annual IEEE Software Engineering Workshop, pp. 285-292, 29th Annual IEEE/NASA Software Engineering Workshop, 2005. | |||
| BibTex | x | ||
| @article{ 10.1109/SEW.2005.23, author = {Peter C. Mehlitz and John Penix}, title = {Design for Verification with Dynamic Assertions}, journal ={2012 35th Annual IEEE Software Engineering Workshop}, volume = {0}, year = {2005}, isbn = {0-7695-2306-4}, pages = {285-292}, doi = {http://doi.ieeecomputersociety.org/10.1109/SEW.2005.23}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - CONF JO - 2012 35th Annual IEEE Software Engineering Workshop TI - Design for Verification with Dynamic Assertions SN - 0-7695-2306-4 SP285 EP292 A1 - Peter C. Mehlitz, A1 - John Penix, PY - 2005 KW - null VL - 0 JA - 2012 35th Annual IEEE Software Engineering Workshop ER - | |||
Completed design and implementation are often regarded as pre-requisites of any verification. While recent development methods establish testability as a design criterion, there is no corresponding design support for other verifi- cation methods like model checking and static analysis. Since these methods have inherent scalability problems, their application becomes more difficult where it is most needed - for complex systems.
Our Design-for-Verification (D4V) approach attempts to close this gap using a variety of techniques, such as design patterns, APIs and source annotations. This paper presents a overview of D4V, and introduces Dynamic Assertions as one of the proposed D4V techniques.
Dynamic Assertions are dedicated, non-intrusive check objects that are dynamically activated, evaluated and deactivated via assertions of their target objects. Since these check objects can have their own state, they can be used to verify a broad range of properties. Properties can be expressed in the target programming language, and checked in a testing environment. In addition, Dynamic Assertions can be configured via call contexts, making them suitable for connector-specific verification of component based systems.
