Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Mario Sangiorgio

dblp:26/11211 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2012
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Program analysis · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

Topics — the 3 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Program analysis › specification mining
behavioral model inference
0.112012
Runtime monitoring of component changes with Spy@Runtime · ICSE 2012
Program analysis
dynamic analysis
0.112012
Runtime monitoring of component changes with Spy@Runtime · ICSE 2012
Program analysis › dynamic analysis
runtime monitoring
0.112012
Runtime monitoring of component changes with Spy@Runtime · ICSE 2012

Methods — techniques the papers use, named apart from their topics

black-box dynamic inference · 0.3
YearPublicationVenuePosition
2012 Runtime monitoring of component changes with Spy@Runtime
abstract
We present Spy@Runtime, a tool to infer and work with behavior models. Spy@Runtime generates models through a dynamic black box approach and is able to keep them updated with observations coming from actual system execution. We also show how to use models describing the protocol of interaction of a software component to detect and report functional changes as soon as they are discovered. Monitoring functional properties is particularly useful in an open environment in which there is a distributed ownership of a software system. Parts of the system may be changed independently and therefore it becomes necessary to monitor the component's behavior at run time.
Carlo Ghezzi, Andrea Mocci, Mario Sangiorgio
ICSE3