Runtime Monitoring of Component Changes with Spy@Runtime
•Télécharger en tant que KEY, PDF•
0 j'aime•1,782 vues
ICSE 2012 Formal Demonstration
Recommandé
Recommandé
Contenu connexe
Dernier
Dernier (20)
En vedette
En vedette (20)
Runtime Monitoring of Component Changes with Spy@Runtime
- 1. Runtime Monitoring of Component Changes with Spy@Runtime Carlo Ghezzi Andrea Mocci Mario Sangiorgio
- 2. OPEN ENVIRONMENT Application Service 2
- 3. ISSUES Lack of formal Services may change specifications behavior 3
- 4. GOALS Recover specifications Detect changes and keep them updated 4
- 5. GOALS Recover specifications Detect changes and keep them updated AT RUNTIME 4
- 6. SPY@RUNTIME DESIGN TIME RUN TIME Specification Update Specification Monitoring Change Detection Inference 5
- 7. MODELS NEEDED Protocol Behavior Model Behavior Equivalence Model Only the protocol of interaction Precise behavior description General validity Valid in a small scope Built via abstraction Built from an exhaustive search Monitoring Violation Interpretation 6
- 8. MODELS NEEDED Protocol Behavior Model Behavior Equivalence Model Only the protocol of interaction Precise behavior description General validity Valid in a small scope Built via abstraction Built from an exhaustive search Monitoring Violation Interpretation 6
- 9. MODELS NEEDED Protocol Behavior Model Behavior Equivalence Model Only the protocol of interaction Precise behavior description General validity Valid in a small scope Built via abstraction Built from an exhaustive search Monitoring Violation Interpretation 6
- 10. MODELS NEEDED Protocol Behavior Model Behavior Equivalence Model Only the protocol of interaction Precise behavior description General validity Valid in a small scope Built via abstraction Built from an exhaustive search Monitoring Violation Interpretation 6
- 11. MODELS NEEDED Protocol Behavior Model Behavior Equivalence Model Only the protocol of interaction Precise behavior description General validity Valid in a small scope Built via abstraction Built from an exhaustive search Monitoring Violation Interpretation 6
- 12. DESIGN TIME Scope API Dynamic selection instrumentation analysis 7
- 13. DESIGN TIME Scope API Dynamic selection instrumentation analysis Service behavior models 7
- 14. DESIGN TIME Scope API Dynamic selection instrumentation analysis Service behavior models 7
- 15. RUN TIME Application Monitor Service 8
- 16. VIOLATION DETECTION Execution Protocol Trace Behavior Model 9
- 17. VIOLATION INTERPRETATION Protocol Behavior Model Behavioral Equivalence Model 10
- 18. LIVE DEMO Update of an incomplete model Detection of an injected fault 11
Notes de l'éditeur
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Soprattutto di’ che la scope selection ha un costo inferiore o al massimo analogo alla scrittura di casi di test.\n
- Soprattutto di’ che la scope selection ha un costo inferiore o al massimo analogo alla scrittura di casi di test.\n
- \n
- \n
- Stress that BEM is used as an oracle to determine whether everything is still behaving correctly.\nExplain clearly how we use it to determine the nature of a violation\n
- \n