Evolving software product lines with aspects

Figueiredo, Eduardo; Cacho, Nélio; Sant’Anna, Cláudio; Monteiro, Mário; Kulesza, Uirá; Garcia, Alessandro; Soares, Sérgio; Ferrari, Fabiano Cutigi; Khan, Safoora Shakil; Filho, Fernando Castor; Dantas, Francisco

doi:10.1145/1368088.1368124

Cited by 239 publications

(59 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Another limitation of this study is the fact that it only considered the exceptions explicitly thrown by SPL code assets -excluding exceptions signaled from libraries and Java runtime environment. There are also the limitations inherent to the use of a static analysis tool (i.e., inheritance, polymorphism and virtual calls) (Robillard and Murphy 2003), however the limitations of this study are similar to the ones imposed on the other empirical studies with similar goals (Figueiredo et al 2008) (Coelho et al 2008(Coelho et al , 2011 (Ferrari et al (2010). Moreover, one may also argue that during the second phase of our study the exception flows of BerkeleyDB were not analyzed, bringing another limitation to the study.…”

Section: Study Limitationsmentioning

confidence: 87%

“…CIDE (Colored IDE) is a tool that enables SPL developers to annotate code with feature information using background colors (similar to #ifdefs). All SPLs were used in several empirical studies (Figueiredo et al 2008) (Kästner et al 2008) (Coelho et al 2008)) (Godil and Jacobsen 2005), and each of them is a representative of different application domains, and heterogeneous realistic ways of incorporating exception handling.…”

Section: The Target Software Product Linesmentioning

confidence: 99%

“…On the other hand, the MobileMedia implementation has explicitly defined the exception handling as one of the primary concerns (Figueiredo et al 2008). The quality of the exception handling policy is also reflected by the considerable number of user-defined exceptions in MM (see Table 1) and specialized handler actions (see Table 2), in contrast with BkDb and PvL on which most the exception handler actions were generic (i.e., catch Throwable or catch Exception clauses) -see Table 2.…”

Section: Uncaught Exception Analysismentioning

confidence: 99%

See 2 more Smart Citations

In-depth characterization of exception flows in software product lines: an empirical study

Melo

Coelho

Kulesza

et al. 2013

Journal of Software Engineering Research and Development

View full text Add to dashboard Cite

Software Product Lines (SPLs) play an essential role in contemporary software development, improving program quality and reducing the time to market. However, despite its importance, several questions concerning SPL dependability did not get enough attention yet, such as: how the exception handling code has been implemented in SPLs? The characteristics of the exception handling code may lead to faulty SPL products? The Exception Handling (EH) is a widely used mechanism for building robust systems and is embedded in most of mainstream programming languages. In SPL context we can find exception signalers and handlers spread over code assets associated to common and variable SPL features. If exception signalers and handlers are added to a SPL in an unplanned way, products can be generated on which variable features may signal exceptions that remain uncaught or are mistakenly caught by common features or other variable features. This paper describes an empirical study that categorizes the possible ways exceptions flow through SPL features and investigates whether some of their characteristics can lead to faulty exception handling behavior. The study outcomes presented in this paper are helpful in several ways, such as: (i) enhancing the general understanding of how exceptions flow through mandatory and variable features; (ii) providing information about the potential problems related to specific kinds of flows detected in this study; and (iii) presenting how a static analysis tool can be used to support the identification of potentially faulty exception handling flows.

show abstract

Section: Study Limitationsmentioning

confidence: 87%

Section: The Target Software Product Linesmentioning

confidence: 99%

Section: Uncaught Exception Analysismentioning

confidence: 99%

See 1 more Smart Citation

In-depth characterization of exception flows in software product lines: an empirical study

Melo

Coelho

Kulesza

et al. 2013

Journal of Software Engineering Research and Development

View full text Add to dashboard Cite

show abstract

“…Na LPS, a POA tem por objetivo trabalhar o encapsulamento de features transversais em novas unidades modulares, sendo os aspectos. A intenção é fazer com que a variação de features transversais se torne mais modulares e evoluídas quando comparadas com mecanismos de variabilidade convencionais, onde o código principal e os pontos de variação ficam unidos (Figueiredo et al, 2008).…”

Section: Implementação Da Variabilidadeunclassified

Uma Linha de Produto de Software para Desenvolvimento de Jogos Educativos

Filho¹,

Domínguez²

2018

RBIE

View full text Add to dashboard Cite

show abstract

“…As for the automation of the division itself, we envision future research on techniques to extract and isolating features in separated applications [19,23,32], going beyond the simple synthesis of feature models [7,12,39,44]. Similarly there is a large amount of approaches to locate concerns, to mine aspects or to automate the refactoring of applications in a more modular way [2,13,16,25,38].…”

Section: Perspectivesmentioning

confidence: 99%

Software Unbundling: Challenges and Perspectives

Filho

Acher²,

Barais³

2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Unbundling is a phenomenon that consists of dividing an existing software artifact into smaller ones. It can happen for different reasons, one of them is the fact that applications tend to grow in functionalities and sometimes this can negatively influence the user experience. For example, mobile applications from well-known companies are being divided into simpler and more focused new ones. Despite its current importance, little is known or studied about unbundling or about how it relates to existing software engineering approaches, such as modularization. Consequently, recent cases point out that it has been performed unsystematically and arbitrarily. In this article, our main goal is to present this novel and relevant concept and its underlying challenges in the light of software engineering, also exemplifying it with recent cases. We relate unbundling to standard software modularization, presenting the new motivations behind it, the resulting problems, and drawing perspectives for future support in the area.

show abstract

Evolving software product lines with aspects

Cited by 239 publications

References 22 publications

In-depth characterization of exception flows in software product lines: an empirical study

In-depth characterization of exception flows in software product lines: an empirical study

Uma Linha de Produto de Software para Desenvolvimento de Jogos Educativos

Software Unbundling: Challenges and Perspectives

Contact Info

Product

Resources

About