2011
DOI: 10.1007/978-3-642-19829-8_3
|View full text |Cite
|
Sign up to set email alerts
|

Runtime Verification for Generic Classes with ConGu 2

Abstract: Abstract. Even though generics became quite popular in mainstream objectoriented (OO) languages, approaches for checking at runtime the conformance of such programs against formal specifications still lack appropriate support. In order to overcome this limitation within CONGU, a tool-based approach we have been developing to support runtime conformance checking of Java programs against algebraic specifications, we recently proposed a notion of refinement mapping that allows to define correspondences between pa… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2012
2012
2022
2022

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(1 citation statement)
references
References 13 publications
0
1
0
Order By: Relevance
“…It verifies that implementations conform to specifications by monitoring method executions in order to find any violation of automatically generated pre and post-conditions. The ConGu tool [7] picks a module of axiomatic specifications, together with a Java implementation and a refinement that maps specifications to Java types, and responds to an erroneous implementation by outputing the specification constraint that was violated; this is often insufficient to find the faulty method, because all methods involved in the violated constraint become equally suspect.…”
Section: Introductionmentioning
confidence: 99%
“…It verifies that implementations conform to specifications by monitoring method executions in order to find any violation of automatically generated pre and post-conditions. The ConGu tool [7] picks a module of axiomatic specifications, together with a Java implementation and a refinement that maps specifications to Java types, and responds to an erroneous implementation by outputing the specification constraint that was violated; this is often insufficient to find the faulty method, because all methods involved in the violated constraint become equally suspect.…”
Section: Introductionmentioning
confidence: 99%