Software model refactoring based on performance analysis: better working on software or performance side?

Several approaches have been introduced in the last few years to tackle the problem of interpreting model-based performance analysis results and translating them into architectural feedback. Typically the interpretation can take place by browsing either the software model or the performance model. In this paper, we compare two approaches that we have recently introduced for this goal: one based on the detection and solution of performance antipatterns, and another one based on bidirectional model transformations between software and performance models. We apply both approaches to the same example in order to illustrate the differences in the obtained performance results. Thereafter, we raise the level of abstraction and we discuss the pros and cons of working on the software side and on the performance side.Comment: In Proceedings FESCA 2013, arXiv:1302.478

Software Architecture Risk Containers

Our motivation is to determine whether risks such as im- plementation error-proneness can be isolated into three types of con- tainers at design time. This paper identifies several container candidates in other research that fit the risk container concept. Two industrial case studies were used to determine which of three container types tested is most effective at isolating and predicting at design time the risk of im- plementation error-proneness. We found that Design Rule Containers were more effective than Use Case and Resource Containers

Working out a common task: design and evaluation of user-intelligent system collaboration

This paper describes the design and user evaluation of an intelligent user interface intended to mediate between users and an Adaptive Information Extraction (AIE) system. The design goal was to support a synergistic and cooperative work. Laboratory tests showed the approach was efficient and effective; focus groups were run to assess its ease of use. Logs, user satisfaction questionnaires, and interviews were exploited to investigate the interaction experience. We found that user’ attitude is mainly hierarchical with the user wishing to control and check the system’s initiatives. However when confidence in the system capabilities rises, a more cooperative interaction is adopted

Commentary on: "P&S Requirements for ePartner-supported Astronaut-Rover Teams during Planetary Surface Operations"

The article (Grant, Neerincx, and Wolff 2011) introduces some considerations taken from the experience of the authors participation in the ESA project called MECA (Mission Execution Crew Assistant). The idea of MECA is to form a network of agents (both human and software), in which each unit, called e-partner, is capable of detecting and influencing the physical, cognitive and affective state of its respective human users. The article describes the three stages along which the project evolves and presents a list of system requirements among which authors highlight those that can be classified under the label of Planning and Scheduling (P&S). In addition to the P&S requirements the most interesting contribution of the paper is probably the concept of e-partners and the description of the cognitive workload model on the base of which authors think to build the e-partner agent. We subdivide the commentary in different parts. We first offer a slightly different perspective with respect to the role of planning and scheduling, then sketch an architecture for using planning technology in continuous loop with the humans, and then we formulate some questions to corroborate debate at the workshop.http://www.congrex.nl/11c05/Papers/Grant_commentary.pd

Experimenting the Influence of Numerical Thresholds on Model-based Detection and Refactoring of Performance Antipatterns

Performance antipatterns are well-known bad design practices that lead to software products suffering from poor performance. A number of performance antipatterns has been defined and classified and refactoring actions have also been suggested to remove them. In the last few years, we have dedicated some effort to the detection and refactoring of performance antipatterns in software models.A specific characteristic of performance antipatterns is that they contain numerical parameters that may represent thresholds referring to either performance indices (e.g., a device utilization) or design features (e.g., number of interface operations of a software component). In this paper, we analyze the influence of such thresholds on the capability of detecting and refactoring performance antipatterns. In particular, (i) we analyze how a set of detected antipatterns may change while varying the threshold values and (ii) we discuss the influence of thresholds on the complexity of refactoring actions. With the help of a leading example, we quantify the influence using precision and recall metrics

From software architecture to analysis models and back: Model-driven refactoring aimed at availability improvement

Abstract Context With the ever-increasing evolution of software systems, their architecture is subject to frequent changes due to multiple reasons, such as new requirements. Appropriate architectural changes driven by non-functional requirements are particularly challenging to identify because they concern quantitative analyses that are usually carried out with specific languages and tools. A considerable number of approaches have been proposed in the last decades to derive non-functional analysis models from architectural ones. However, there is an evident lack of automation in the backward path that brings the analysis results back to the software architecture. Objective In this paper, we propose a model-driven approach to support designers in improving the availability of their software systems through refactoring actions. Method The proposed framework makes use of bidirectional model transformations to map UML models onto Generalized Stochastic Petri Nets (GSPN) analysis models and vice versa. In particular, after availability analysis, our approach enables the application of model refactoring, possibly based on well-known fault tolerance patterns, aimed at improving the availability of the architectural model. Results We validated the effectiveness of our approach on an Environmental Control System. Our results show that the approach can generate: (i) an analyzable availability model from a software architecture description, and (ii) valid software architecture models back from availability models. Finally, our results highlight that the application of fault tolerance patterns significantly improves the availability in each considered scenario. Conclusion The approach integrates bidirectional model transformation and fault tolerance techniques to support the availability-driven refactoring of architectural models. The results of our experiment showed the effectiveness of the approach in improving the software availability of the system

Three Performance Models at Work: A Software Designer Perspective

n/

The 2008 Scheduling and Planning Applications Workshop (SPARK'08)

SPARK'08 was the first edition of a workshop series designed to provide a stable, long‐term forum where researchers could discuss the applications of planning and scheduling techniques to real problems. Animated discussion characterized the workshop, which was collocated with the 18th International Conference on Automated Planning and Scheduling (ICAPS‐08) held in Sydney, Australia, in September 2008

Long-term Evaluation of a Mobile Remote Presence Robot for the Elderly

We are currently working on a project, named ExCITE, the goal of which is to intensively evaluate a tele-presence robot against a wide spectrum of requirements of the elderly. This work is at the intersection of two emerging fields, Human-Robot Interaction (HRI) and Ambient Assisted Living (AAL), and involves both long term and cross-cultural user evaluation

Expanded Poetry: Otto Iconopoemi 2006–2018

n/