ModelLAND: Where Do Models Come from?

International audienceSoftware is increasingly produced according to a certain goal and by integrating existing software produced by third-parties, typically black-box, and often provided without a machine readable documentation. This implies that development processes of the next future have to explicitly deal with an inherent incompleteness of information about existing software, notably on its behaviour. Therefore, on one side a software producer will less and less know the precise behaviour of a third party software service, on the other side she will need to use it to build her own application. In this paper we present an innovative development process to automatically produce dependable software systems by integrating existing services under uncertainty and according to the specied goal. Moreover, we (i) discuss important challenges that must be faced while producing the kind of systems we are targeting, (ii) give an overview of the state of art related to the identied challenges, and finally (iii) provide research directions to address these challenges

show abstract

“…A more complete discussion about the state of the art in elicitation techniques might be found in [4].…”

Section: State Of the Artmentioning

confidence: 99%

Producing software by integration: challenges and research directions (keynote)

Inverardi

Autili

Ruscio

et al. 2013

Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…An important aspect is that the elicit phase produces models that, although partial, are still good enough to achieve G. Goal driven elicitation can be very effective, e.g., as observed on the Amazon E-commerce WS (AEWS) where we apply the approach in [11] to elicit the AEWS interaction protocol. The experiment considered a goal-independent elicitation versus a goaldriven one [5]. Starting from the AEWS WSDL consisting of 85 XML schema type definitions and 23 WSDL operation definitions, the goal independent elicitation resulted in an interaction protocol made of 24 states and 288 transitions by using 10 6 test cases, each executed in 10 −2 secs, e.g., few hours of testing.…”

Section: The Elicit Phasementioning

confidence: 99%

“…The experiment considered a goal independent elicitation versus a goal driven one [5]. Starting from the AEWS WSDL consisting of 85 XML schema type definitions and 23 WSDL operation definitions, the goal independent elicitation resulted in an interaction protocol made of 24 states and 288 transitions by using 10 6 test cases, each executed in 10 −2 secs, e.g., few hours of testing.…”

Section: The Elicit Phasementioning

confidence: 99%

Automated Integration of Service-Oriented Software Systems

Autili

Inverardi

Tivoli

2015

Fundamentals of Software Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. In the near future we will be surrounded by a virtually infinite number of software applications that provide services in the digital space. This situation radically changes the way software will be produced and used: (i) software is increasingly produced according to specific goals and by integrating existing software; (ii) the focus of software production will be shifted towards reuse of third-parties software, typically blackbox, that is often provided without a machine readable documentation. The evidence underlying this scenario is that the price to pay for this software availability is a lack of knowledge on the software itself, notably on its interaction behaviour. A producer will operate with software artefacts that are not completely known in terms of their functional and non-functional characteristics. The general problem is therefore directed to the ability of interacting with the artefacts to the extent the goal is reached. This is not a trivial problem given the virtually infinite interaction protocols that can be defined at application level. Different software artefacts with heterogeneous interaction protocols may need to interoperate in order to reach the goal. In this paper we focus on techniques and tools for integration code synthesis, which are able to deal with partial knowledge and automatically produce correct-by-construction serviceoriented systems with respect to functional goals. The research approach we propose builds around two phases: elicit and integrate. The first concerns observation theories and techniques to elicit functional behavioural models of the interaction protocol of black-box services. The second deals with compositional theories and techniques to automatically synthesize appropriate integration means to compose the services together in order to realize a service choreography that satisfies the goal.

show abstract

“…Over the last years, several approaches for extracting models from software artifacts have been proposed even though the optimal solution, which can be used for any situation, does not exist yet . They represent different observations of the system that are consistent with the effective behavior of the system itself.…”

Section: An Overview Of the Evoss Approachmentioning

confidence: 99%

“…They represent different observations of the system that are consistent with the effective behavior of the system itself. These approaches range from machine learning ones to static and dynamic analysis to running traces observations . However, the case of Evoss is much simpler.…”

Section: An Overview Of the Evoss Approachmentioning

confidence: 99%

A model‐driven approach to detect faults in FOSS systems

Ruscio

2015

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

Free and Open-Source Software (FOSS) Linux distributions are among the most complex modern software systems. They are made of thousands of components (software packages) evolving rapidly without centralized coordination. The upgrade of FOSS systems is managed by meta-installers, which solve package dependencies and conflicts and lead the system to a new system configuration by installing or removing packages. Current tools are able to predict a very limited set of upgrade faults before deployment, and this leaves a wide range of faults unpredicted. In this paper, we focus on faults that remain unpredicted, for example, missing packages, packages that are not properly installed, and missing services, with the aim of providing a solution for them. Specifically, in this paper, we propose a model-driven approach and supporting tools to prevent specific classes of system configuration faults before performing the real upgrade. Once the system configuration is represented as a model, the configuration model is evaluated by means of queries, each devoted to discover a specific class of faults. The approach is intrinsically extensible so that user communities can add new queries when new classes of faults are identified. The approach has been validated by executing the fault detector on configuration models in which faults have been intentionally injected and by analyzing produced results.

show abstract

ModelLAND: Where Do Models Come from?

Cited by 4 publications

References 33 publications

Producing software by integration: challenges and research directions (keynote)

Producing software by integration: challenges and research directions (keynote)

Automated Integration of Service-Oriented Software Systems

A model‐driven approach to detect faults in FOSS systems

Contact Info

Product

Resources

About