Performance by unified model analysis (PUMA)

Abstract

Evaluation of non-functional properties of a design (such as performance, dependability, security, etc.) can be enabled by design annotations specific to the property to be evaluated. Performance properties, for instance, can be annotated on UML designs by using the "UML Profile for Schedulability, Performance and Time (SPT)". However the communication between the design description in UML and the tools used for non-functional properties evaluation requires support, particularly for performance where there are many alternative performance analysis tools that might be applied. This paper describes a tool architecture called PUMA, which provides a unified interface between different kinds of design information and different kinds of performance models, for example Markov models, stochastic Petri nets and process algebras, queues and layered queues.The paper concentrates on the creation of performance models. The unified interface of PUMA is centered on an intermediate model called Core Scenario Model (CSM), which is extracted from the annotated design model. Experience shows that CSM is also necessary for cleaning and auditing the design information, and providing default interpretations in case it is incomplete, before creating a performance model.

KlaperSuite: An Integrated Model-Driven Environment for Reliability and Performance Analysis of Component-Based Systems

“…One of the most widely accepted mathematical models to estimate those properties are Layered Queuing Networks (LQNs) [9,28]. LQNs introduce new modeling concepts to represent software systems.…”

“…The idea is leverage Model Driven Engineering (MDE) [7] techniques to automatically derive, by means of model transformations, performance models from design-oriented models of the system (augmented with additional information related to the non-functional attributes of interest). Existing analysis methodologies [2,[8][9][10] may be in turn applied as is.…”

“…The usage of intermediate modeling languages, which capture relevant information for QoS analyses, has been proposed to mitigate these problems. Intermediate languages in fact bridge design-oriented and analysis-oriented notations, and help in distilling the information needed by performance analysis tools [11,12,9]. Instead of directly transforming design models to performance models, a two-step transformation from the source model to the intermediate model, and from the intermediate model to the target model is proposed.…”

Model Interoperability for Performance Engineering: Survey of Milestones and Evolution

“…and various system performance modeling tools. Woodside et al [11] propose the Core Scenario Model (CSM), claiming that it captures the essence of performance specification and estimation as expressed in the UML SPT profile. Grassi et al [15] focus on the construction of software systems according to the component-based development (CBD) approach.…”

“…Woodside and colleagues developed a tool architecture, PUMA (Performance by Unified Model Analysis) as a framework into which different kinds of software design tools can be plugged as sources, and different kinds of performance tools can be plugged as targets [11].…”