Reducing the verification cost of evolving product families using static analysis techniques

Sabouri, Hamideh; Khosravi, Ramtin

doi:10.1016/j.scico.2013.06.009

Cited by 9 publications

(6 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Furthermore, static analyses have been proposed [Ribeiro et al 2010;Tartler et al 2011;Adelsberger et al 2014;Sabouri and Khosravi 2014] that do not scale an existing static analysis known from single-system engineering, but rather focus on an analysis that is specific to product lines -to which we refer to as family-specific analyses. Interestingly, most approaches for family-based static analysis are designed for annotation-based implementations and domain-independent specifications.…”

Section: Family-based Static Analysismentioning

confidence: 99%

“…Interestingly, most approaches for family-based static analysis are designed for annotation-based implementations and domain-independent specifications. As an exception, Adelsberger et al [2014] focus on composition-based implementations with feature-oriented programming, and Sabouri and Khosravi [2014] propose a family-wide specification. Overall, these analyses support product lines implemented in C [Tartler et al 2011;Liebig et al 2013] and Java [Ribeiro et al 2010;Brabrand et al 2013;Bodden et al 2013;Adelsberger et al 2014].…”

Section: Family-based Static Analysismentioning

confidence: 99%

“…They exemplify their approach by means of constant propagation analysis. Sabouri and Khosravi [2014] propose a static analysis to identify features that are irrelevant for a given temporal property. These irrelevant features are then ignored during familybased model checking to reduce the state space.…”

Section: Family-based Static Analysismentioning

confidence: 99%

“…The majority of approaches for family-based model checking apply abstract model checking. Abstract models have been defined using I/O automata , labeled transition systems Sabouri and Khosravi 2012;ter Beek et al 2013;Sabouri and Khosravi 2014], modal transition systems Asirelli et al 2012], featured transition systems Cordy et al 2012a;Cordy et al 2012b;Classen et al 2013;Sabouri and Khosravi 2013a;Cordy et al 2013b;Cordy et al 2013a;Classen et al 2014], featured timed automata , modal sequence diagrams , and actor models [Sabouri and Khosravi 2013b]. In contrast, several authors proposed approaches for family-based software model checking.…”

Section: Family-based Model Checkingmentioning

confidence: 99%

See 3 more Smart Citations

A Classification and Survey of Analysis Strategies for Software Product Lines

et al. 2014

View full text Add to dashboard Cite

Software-product-line engineering has gained considerable momentum in the recent years, both in industry and in academia. A software product line is a family of software products that share a common set of features. Software product lines challenge traditional analysis techniques, such as type checking, model checking, and theorem proving, in their quest of ensuring correctness and reliability of software. Simply creating and analyzing all products of a product line is usually not feasible, due to the potentially exponential number of valid feature combinations. Recently, researchers began to develop analysis techniques that take the distinguishing properties of software product lines into account, for example, by checking feature-related code in isolation or by exploiting variability information during analysis. The emerging field of product-line analyses is both broad and diverse, so it is difficult for researchers and practitioners to understand their similarities and differences. We propose a classification of product-line analyses to enable systematic research and application. Based on our insights with classifying and comparing a corpus of 123 research articles, we develop a research agenda to guide future research on product-line analyses.

show abstract

Section: Family-based Static Analysismentioning

confidence: 99%

Section: Family-based Static Analysismentioning

confidence: 99%

Section: Family-based Static Analysismentioning

confidence: 99%

Section: Family-based Model Checkingmentioning

confidence: 99%

See 2 more Smart Citations

A Classification and Survey of Analysis Strategies for Software Product Lines

et al. 2014

View full text Add to dashboard Cite

show abstract

“…A number of researchers [CHS + 10, GLS08, LPT09, CCP + 12] use model checking techniques [CGP99] to verify products lines. Sabouri and Khosravi [SK14] try to tackle the well-known state space explosion problem by statically analyzing product family models, before checking them against properties (expressed in linear temporal logic [Eme90]), to avoid re-verifying products by using previous results. This work is related to ours, since in both proposals, not all products are verified.…”

Section: Pfofe Et Al [Pts + 16] Proposementioning

confidence: 99%

Partially safe evolution of software product lines

Sampaio

Borba

Teixeira

2019

Journal of Systems and Software

View full text Add to dashboard Cite

À minha família, que me apoia incondicionalmente. Faço um agradecimento especial aos meus pais, Augusto e Claudia, que me motivam sempre a não desistir dos meus sonhos, e à minha irmã (e melhor amiga) Débora, que mesmo nos dias mais tristes e cansativos consegue me fazer sorrir. Obrigada por sempre me convencer de que eu sou capaz de conquistar meus objetivos.Ao meu namorado Roberto, que é meu companheiro de todas as horas. Obrigada por aguentar meus dramas diários e por me fazer enxergar o lado bom de tudo.Ao meu orientador Paulo Borba, que passei a admirar (ainda mais) depois de me tornar sua aluna. Sempre muito paciente comigo e presente na minha vida, tem guiado meus passos da melhor forma possível. Serei eternamente grata pelos ensinamentos. Agradeço também ao meu co-orientador Lepoldo Teixeira, que é uma inspiração para mim como profissional. Sua constante presença e apoio foram essenciais.Aos meus amigos, que torcem tanto por mim e sempre me colocam pra cima, obrigada por tudo.Aos membros do SPG, pelos comentários e feedbacks a respeito do meu trabalho. Em especial, gostaria de agradecer às minhas irmãs de pesquisa Klissiomara, Paola e Thaís, que se tornaram amigas. Nossa convivência e momentos de descontração são de extrema importância pra mim. À Nicolas Dintzner, que desenvolveu uma ferramenta bastante útil no meu trabalho e estava sempre à disposição para me ajudar. Esta interação contribuiu bastante para o meu aprendizado. À Coordenação de Aperfeiçoamento Pessoal de Nível Superior (CAPES), por ter financiado esta pesquisa."Mathematical reasoning may be regarded rather schematically as the exercise of a combination of two facilities, which we may call intuition and ingenuity. AbstractSoftware product lines (SPLs) are sets of related systems that are built based on reusable artifacts. They have three elements: a variability model, that has feature declarations and dependencies among them; implementation artifacts and a configuration knowledge, that maps features to their implementation. SPLs provide several advantages, like software quality and reuse improvements, productivity gains and the capacity to customize a system depending on customers needs. There are several challenges in the SPL development context. To build customizable software and meet all customer needs, SPLs tend to increase over time. The larger a SPL becomes, the higher is the complexity to evolve it. Therefore, it is not trivial to predict which products are affected by a change, specially in large SPLs. One might need to check if products had their behaviour preserved to avoid inadvertently affecting existing users in an evolution scenario. In refactoring and conservative extension scenarios, we can avoid this problem by checking for behavior preservation, either by testing the generated products or by using formal theories. Product line refinement theories support that by requiring behavior preservation for all existing products. This happens in a number of situations, such as code refinements. For instance, in function renaming tran...

show abstract