Applied statistics: A review

The main phases of applied statistical work are discussed in general terms. The account starts with the clarification of objectives and proceeds through study design, measurement and analysis to interpretation. An attempt is made to extract some general notions.Comment: Published at http://dx.doi.org/10.1214/07-AOAS113 in the Annals of Applied Statistics (http://www.imstat.org/aoas/) by the Institute of Mathematical Statistics (http://www.imstat.org

Automated Analysis of Diverse Variability Models with Tool Support

Over the past twenty years, there have been many contributions in the area of automated analysis of variability models. However, the majority of these researches are focused on feature models. We propose that the knowledge obtained during recent years on the analysis of feature models can be applied to automatically analyse different variability models. In this paper we present FaMa OVM and FaMa DEB, which are prototypical implementations for the automated analysis of two distinct variability models, namely Orthogonal Variability Models and Debian Variablity Models, respectively. In order to minimise efforts and benefit from the feature model know–how, we use FaMa Framework which allows the development of analysis tools for diverse variability modelling languages. This framework provides a well tested system that guides the tool development. Due to the structure provided by the framework, FaMa OVM and FaMa DEB tools are easy to extend and integrate with other tools. We report on the main points of both tools, such as the analysis operations provided and the logical solvers used for the analysis.Comisión Interministerial de Ciencia y Tecnología (CICYT) TIN2012-32273Junta de Andalucía TIC-5906Junta de Andalucía P12-TIC-186

A Product Line Systems Engineering Process for Variability Identification and Reduction

Software Product Line Engineering has attracted attention in the last two decades due to its promising capabilities to reduce costs and time to market through reuse of requirements and components. In practice, developing system level product lines in a large-scale company is not an easy task as there may be thousands of variants and multiple disciplines involved. The manual reuse of legacy system models at domain engineering to build reusable system libraries and configurations of variants to derive target products can be infeasible. To tackle this challenge, a Product Line Systems Engineering process is proposed. Specifically, the process extends research in the System Orthogonal Variability Model to support hierarchical variability modeling with formal definitions; utilizes Systems Engineering concepts and legacy system models to build the hierarchy for the variability model and to identify essential relations between variants; and finally, analyzes the identified relations to reduce the number of variation points. The process, which is automated by computational algorithms, is demonstrated through an illustrative example on generalized Rolls-Royce aircraft engine control systems. To evaluate the effectiveness of the process in the reduction of variation points, it is further applied to case studies in different engineering domains at different levels of complexity. Subject to system model availability, reduction of 14% to 40% in the number of variation points are demonstrated in the case studies.Comment: 12 pages, 6 figures, 2 tables; submitted to the IEEE Systems Journal on 3rd June 201

Modeling used for Software Product Line Engineering

Software product line is the separation of variant features of all the products which belong to same line. Modeling is the basic foundation of Software Product Line Engineering, that is used for collection of what is similar and what is different between products, but products of same line. Here Line means a set of products those are related and share some commonalities like data structures, software components, some features and architecture etc.In order to managing the variability and commonalties in product line we use modeling in Software product line.So that SPLE is the most powerful approach to which we can use for to increase the efficiency of the software engineering process and we can develop variety of software from a single software product line, that’s why if we implement low design that can ripple through many generated software systems.In this paper I represent the relationship between Orthogonal Variability model and various different qualities attributes affecting them., I will also describe some existing metrics which we use to measure these quality attributes

An Automated Technique for Analysis of Orthogonal Variability Models based on Anti-patterns Detection using DL reasoning

During a Software Product Line (SPL) variability management, model validation is crucial so as to detect faults in early development stages and avoid affecting derived products quality. Therefore, the automated variability analysis has emerged for translating and validating variability models. In this work, we present a catalogue of anti-patterns, which describes scenarios associated to the detection of problems in a SPL. Moreover, we extend crowd-variability, a novel graphical tool designed for modelling and validating Orthogonal Variability Models (OVM), for detecting such anti-patterns using Description Logics (DL)-based reasoning services.XI Workshop Innovación en Sistemas de Software.Red de Universidades con Carreras en Informátic

An Automated Technique for Analysis of Orthogonal Variability Models based on Anti-patterns Detection using DL reasoning

During a Software Product Line (SPL) variability management, model validation is crucial so as to detect faults in early development stages and avoid affecting derived products quality. Therefore, the automated variability analysis has emerged for translating and validating variability models. In this work, we present a catalogue of anti-patterns, which describes scenarios associated to the detection of problems in a SPL. Moreover, we extend crowd-variability, a novel graphical tool designed for modelling and validating Orthogonal Variability Models (OVM), for detecting such anti-patterns using Description Logics (DL)-based reasoning services.XI Workshop Innovación en Sistemas de Software.Red de Universidades con Carreras en Informátic

An Automated Technique for Analysis of Orthogonal Variability Models based on Anti-patterns Detection using DL reasoning

During a Software Product Line (SPL) variability management, model validation is crucial so as to detect faults in early development stages and avoid affecting derived products quality. Therefore, the automated variability analysis has emerged for translating and validating variability models. In this work, we present a catalogue of anti-patterns, which describes scenarios associated to the detection of problems in a SPL. Moreover, we extend crowd-variability, a novel graphical tool designed for modelling and validating Orthogonal Variability Models (OVM), for detecting such anti-patterns using Description Logics (DL)-based reasoning services.XI Workshop Innovación en Sistemas de Software.Red de Universidades con Carreras en Informátic

Review of Requirement Engineering Approaches for Software Product Lines

The Software Product Lines (SPL) paradigm is one of the most recent topics of interest for the software engineering community. On the one hand, the Software Product Lines is based on a reuse strategy with the aim to reduce the global time-to-market of the software product, to improve the software product quality, and to reduce the cost. On the other hand, traditional Requirement Engineering approaches could not be appropriated to deal with the new challenges that arises the SPL adoption. In the last years, several approaches have been proposed to cover this limitation. This technical report presents an analysis of specific approaches used in the development of SPL to provide solutions to model variability and to deal with the requirements engineering activities. The obtained results show that most of the research in this context is focused on the Domain Engineering, covering mainly the Feature Modeling and the Scenario Modeling. Among the studied approaches, only one of them supported the delta identification; this fact implies that new mechanisms to incorporate new deltas in the Domain specification are needed. Regarding the SPL adoption strategy, most of the approaches support a proactive strategy. However, this strategy is the most expensive and risk-prone. Finally, most of the approaches were based on modeling requirements with feature models giving less support to other important activities in the requirements engineering process such as elicitation, validation, or verification of requirements. The results of this study provide a wide view of the current state of research in requirements engineering for SPL and also highlight possible research gaps that may be of interest for researchers and practitioners.Blanes Domínguez, D.; Insfrán Pelozo, CE. (2011). Review of Requirement Engineering Approaches for Software Product Lines. http://hdl.handle.net/10251/1023

Debian Packages Repositories as Software Product Line Models. Towards Automated Analysis

The automated analysis of variability models in general and feature models in particular is a thriving research topic. There have been numerous contributions along the last twenty years in this area including both, research papers and tools. However, the lack of realistic variability models to evaluate those techniques and tools is recognized as a major problem by the community. To address this issue, we looked for large– scale variability models in the open source community. We found that the Debian package dependency language can be interpreted as software product line variability model. Moreover, we found that those models can be automatically analysed in a software product line variability model-like style. In this paper, we take a first step towards the automated analysis of Debian package dependency language. We provide a mapping from these models to propositional formulas. We also show how this could allow us to perform analysis operations on the repositories like the detection of anomalies (e.g. packages that cannot be installed).CICYT TIN2009- 07366Junta de Andalucía TIC-253