Estimating footprints of model operations

When performed on a model, a set of operations (e.g., queries or model transformations) rarely uses all the information present in the model. Unintended underuse of a model can indicate various problems: the model may contain more detail than necessary or the operations may be immature or erroneous....

Full description

Saved in:
Bibliographic Details
Published in:2011 33rd International Conference on Software Engineering (ICSE) pp. 601 - 610
Main Authors: Jeanneret, Cédric, Glinz, Martin, Baudry, Benoit
Format: Conference Proceeding
Language:English
Published: New York, NY, USA ACM 21.05.2011
IEEE
Series:ACM Conferences
Subjects:
Analytical models
Computational modeling
Computing methodologies > Modeling and simulation > Model development and analysis
Computing methodologies > Modeling and simulation > Model development and analysis > Model verification and validation
Context modeling
Heuristic algorithms
model footprint
model operation
Object oriented modeling
Petri nets
Software and its engineering > Software creation and management > Designing software > Software implementation planning > Software design techniques
Software and its engineering > Software creation and management > Software development process management
static analysis
Unified modeling language
static analysis
model footprint
model operation
ISBN:9781450304450, 1450304451
ISSN:0270-5257
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:When performed on a model, a set of operations (e.g., queries or model transformations) rarely uses all the information present in the model. Unintended underuse of a model can indicate various problems: the model may contain more detail than necessary or the operations may be immature or erroneous. Analyzing the footprints of the operations - i.e., the part of a model actually used by an operation - is a simple technique to diagnose and analyze such problems. However, precisely calculating the footprint of an operation is expensive, because it requires analyzing the operation's execution trace. In this paper, we present an automated technique to estimate the footprint of an operation without executing it. We evaluate our approach by applying it to 75 models and five operations. Our technique provides software engineers with an efficient, yet precise, evaluation of the usage of their models.
ISBN:9781450304450
1450304451
ISSN:0270-5257
DOI:10.1145/1985793.1985875