Model-driven generative development of measurement software

Abstract

Metrics offer a practical approach to evaluate properties of domain-specific models. However, it is costly to develop and maintain measurement software for each domain specific modeling language. In this paper, we present a model-driven and generative approach to measuring models. The approach is completely domain-independent and operationalized through a prototype that synthesizes a measurement infrastructure for a domain specific modeling language. This model-driven measurement approach is model-driven from two viewpoints: 1) it measures models of a domain specific modeling language; 2) it uses models as unique and consistent metric specifications, w.r.t. a metric specification metamodel which captures all the necessary concepts for model-driven specifications of metrics. The benefit from applying the approach is evaluated by four case studies. They indicate that this approach significantly eases the measurement activities of model-driven development processes.

Yet another meta-model to specify non-functional properties

“…The main concept underlying our proposal, i.e., specifying metrics as instances of a metric specification meta-model, is common to the work of Monperrus et al [13], in which a generative model driven definition of software metrics is proposed. This work concerns the definition of a domainindependent metrics meta-model, allowing modelers to automatically add measurement capabilities to a domain specific modeling language used during the different phases of a model-driven development process.…”

“…Taking inspiration from the work of Monperrus et al, PMM separates the property and more specifically metrics definition from the application domain. Instead, differently from [13], the PMM meta-model addresses specifically non-functional property and metrics by introducing additional concepts concerning the qualitative and quantitative properties definition and the events modeling that is used to specify the semantics of the metrics/properties for a specific application.…”

“…The key concepts of this meta-model are: Property, MetricsTemplate, Metrics, EventSet, and EventType. As in [13], we separate the property definition from the application domain and its specific ontology. The ontology is linked to the Property meta-model via the EventType entity that models a generic event type where the terms of the application-domain ontology will be used.…”

Automated measurement of models of requirements

“…To implement the metrics listed in Table 1, we have used the model-driven measurement approach (MDM) presented in [16,30]. It means that we have expressed the metrics of Table 1 as an instance of a metric metamodel.…”

Analysis of a metamodel to estimate complexity of using a domain-specific language

“…Complementary metrics for notation (including metrics for visual languages) should be considered alongside those in this paper; where this work is expected to have impact is in reducing the controllable complexity of a metamodel by revealing elements that increase complexity, so that the language designer may take some action. Work has been done in the characterization of constructed models [14], which is different from characterizations of a modeling language (though it may be related to the minimum complexity of any constructed model). The work in this paper is also different from generating instance models for the purpose of testing [4], although the technique suggested in this paper could be an alternative for the graph grammar approach to operationalizing a metamodel developed in that work.…”