12th Asia-Pacific Software Engineering Conference (APSEC'05) 2005
DOI: 10.1109/apsec.2005.82
|View full text |Cite
|
Sign up to set email alerts
|

Monitoring with behavior view diagrams for debugging

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2006
2006
2006
2006

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(2 citation statements)
references
References 9 publications
0
2
0
Order By: Relevance
“…The behavior view diagram (BVD) notation was first introduced in our previous work [9] for assisting the debugging of object-oriented programs. In this paper, we adopt this notation for specifying behavior contracts.…”
Section: Behavior View Diagramsmentioning
confidence: 99%
See 1 more Smart Citation
“…The behavior view diagram (BVD) notation was first introduced in our previous work [9] for assisting the debugging of object-oriented programs. In this paper, we adopt this notation for specifying behavior contracts.…”
Section: Behavior View Diagramsmentioning
confidence: 99%
“…The eventsubscription system takes event descriptions from the execution monitors, detects the occurrences of events that match these descriptions, intercepts the program execution, and transfers the control to the appropriate execution monitors. Our previous work [9] used the Java Platform Debugging Architecture (JPDA) 4 for implementing the eventsubscription system to support the use of BVDs for interactive debugging. For testing, this approach of implementation may introduce too much overhead.…”
Section: Monitoring With Behavior Contractsmentioning
confidence: 99%