Are automatically-detected code anomalies relevant to architectural modularity?

Macia, Isela; Garcia, Joshua; Popescu, Dorin; Garcia, Alessandro; Medvidović, Nenad; Staa, Arndt von

doi:10.1145/2162049.2162069

Cited by 98 publications

(168 citation statements)

References 31 publications

Supporting

Mentioning

152

Contrasting

Unclassified

Order By: Relevance

“…In particular, we relied on the documentation produced in previous empirical studies that assessed their software architecture (ARCOVERDE et al, 2013, MACIA et al, 2012a and their exception handling implementation , COELHO et al, 2008, SALES and COELHO, 2011.…”

Section: Data Collection and Analysis Methodsmentioning

confidence: 99%

“…We used the Mobile Media system as the target system because it is a well documented system that has been used in previous empirical studies that assessed its software architecture (ARCOVERDE et al, 2013, MACIA et al, 2012a and its exception handling implementation , COELHO et al, 2008, SALES and COELHO, 2011. Thus, there was su cient information about Mobile Media to infer its exception handling policy.…”

Section: Target Systemmentioning

confidence: 99%

See 1 more Smart Citation

Global-Aware Recommendations for Repairing Exception Handling Violations

BARBOSA¹

View full text Add to dashboard Cite

Exception handling is the most common way of dealing with exceptions in robust software development. Exception handling refers to the process of signaling exceptions upon the detection of runtime errors and taking actions to respond to their occurrence. Despite being aimed at improving software robustness, software systems are still implemented without relying on explicit exception handling policies. Each policy defines the design decisions governing how exception handling should be implemented in a system. These policies are often not documented and are only implicitly defined in the system design. Thus, developers tend to introduce in the source code violations of implicit policies and these violations commonly cause failures in software systems. In this context, the goal of this thesis is to support developers in detecting and repairing exception handling violations. To achieve this goal, two complementary solutions were proposed. The first solution is based on a domain-specific language supporting the detection of violations by explicitly defining exception handling policies to be enforced in the source code. The proposed language was evaluated with a user-centric study and a case study. With the observations and experiences gathered in the user-centric study, we identified some language characteristics that hindered its use and that motivated new language constructs. In addition, the results of the case study showed that violations and faults in exception handling share common causes. Therefore, violations can be used to detect potential causes of exceptionrelated failures. To complement the detection of exception handling violations, this work also proposed a solution for supporting the repair of exception handling violations. Repairing these violations requires reasoning about the global impact that exception handling changes might have in di↵erent parts of the system. Thus, this work proposed a recommender heuristic strategy that takes into account the global context of where violations occur to produce recommendations. Each recommendation produced consists of a sequence of modifications that serves as a detailed blueprint of how an exception handling violation can be removed from the source code. The proposed recommender strategy also takes advantage of explicit policy specifications, although their availability is not mandatory. The results of our empirical assessments revealed that the proposed recommender strategy produced recommendations able to Tratamento de exceçõesé o modo mais comum de lidar com erros no desenvolvimento de software robusto. Tratamento de exceções refere-se ao processo de sinalizar exceções quando erros em tempo de execução são detectados e de tomar ações para responderà ocorrência destas exceções. Apesar de objetivarem a melhoria da robustez de software, sistemas de software ainda são implementados sem se basear em uma política explícita para tratamento de exceções. Cada política define as decisões de projeto que governam como tratamento de exceções deve ser implementado num sis...

show abstract

Section: Data Collection and Analysis Methodsmentioning

confidence: 99%

Section: Target Systemmentioning

confidence: 99%

Global-Aware Recommendations for Repairing Exception Handling Violations

BARBOSA¹

View full text Add to dashboard Cite

show abstract

“…Prior work (Macia, Garcia, Popescu, Garcia, Medvidovic & Staa 2012c) (Macia et al 2012b) (Macia 2013) has shown that each design problem is often realized by various code anomalies scattered in the program. These anomalies interact across the code structure in order to reify a single design problem in the program.…”

Section: Motivating Example and Problemmentioning

confidence: 99%

“…There is growing evidence that code anomalies may be helpful to identify and understand design problems (Macia et al 2012c). Therefore, programmers and researches should be equipped with proper means to reason about code anomalies and their relationships.…”

Section: Objectivementioning

confidence: 99%

See 1 more Smart Citation

Synthesis of Code Anomalies: Revealing Design Problems in the Source Code

Oizumi¹

View full text Add to dashboard Cite

A review of code smell mining techniques

Rasool

Arshad

2015

J. Softw. Evol. and Proc.

View full text Add to dashboard Cite

Over the past 15 years, researchers presented numerous techniques and tools for mining code smells. It is imperative to classify, compare, and evaluate existing techniques and tools used for the detection of code smells because of their varying features and outcomes. This paper presents an up-to-date review on the state-of-the-art techniques and tools used for mining code smells from the source code of different software applications. We classify selected code smell detection techniques and tools based on their detection methods and analyze the results of the selected techniques. We present our observations and recommendations after our critical analysis of existing code smell techniques and tools. Our recommendations may be used by existing and new tool developers working in the field of code smell detection. The scope of this review is limited to research publications in the area of code smells that focus on detection of code smells as compared with previous reviews that cover all aspects of code smells.

show abstract

Are automatically-detected code anomalies relevant to architectural modularity?

Cited by 98 publications

References 31 publications

Global-Aware Recommendations for Repairing Exception Handling Violations

Global-Aware Recommendations for Repairing Exception Handling Violations

Synthesis of Code Anomalies: Revealing Design Problems in the Source Code

A review of code smell mining techniques

Contact Info

Product

Resources

About