A comparative analysis of software architecture recovery techniques

Garcia, Joshua; Ivkovic, Igor; Medvidović, Nenad

doi:10.1109/ase.2013.6693106

Cited by 131 publications

(154 citation statements)

References 38 publications

Supporting

Mentioning

142

Contrasting

Unclassified

Order By: Relevance

“…In [30], a comparative analysis is performed between different software architecture recovery techniques. Six techniques are selected for this purpose which are: ACDC [6], BUNCH [7], WCA [18], LIMBO [19], ZoneBased Recovery (ZBR) [31] and Architecture Recovery using Concerns (ARC) [32].…”

Section: Related Workmentioning

confidence: 99%

Supervised Learning For Orphan Adoption Problem In Software Architecture Recovery

Bibi

Maqbool

Kanwal

2016

MJCS

View full text Add to dashboard Cite

Maintenance of architectural documentation is a prime requirement for evolving software systems. New versions of software systems are launched after making the changes that take place in a software system over time. The orphan adoption problem, which deals with the issue of accommodation of newly introduced resources (orphan resources) in appropriate subsystems in successive versions of a software system, is a significant problem. The orphan adoption algorithm has been developed to address this problem. For evolving software systems, it would be useful to recover the architecture of subsequent versions of a software system by using existing architectural information. In this paper, we explore supervised learning techniques (classifiers) for recovering the architecture of subsequent versions of a software system by taking benefit of existing architectural information. We use three classifiers, i.e., Bayesian classifier, k-Nearest Neighbor classifier and Neural Network for orphan adoption. We conduct experiments to compare the performance of the classifiers using various dependencies between entities in a software system. Our experiments highlight correspondence between the orphan adoption algorithm and the classifiers, and also reveal their strengths and weaknesses. To combine strengths of individual classifiers, we propose using a multiclassifier approach in which classifiers work cooperatively to improve classification accuracy. Experiments show that there is significant improvement in results when our proposed multiclassifier approach is used.

show abstract

Section: Related Workmentioning

confidence: 99%

Supervised Learning For Orphan Adoption Problem In Software Architecture Recovery

Bibi

Maqbool

Kanwal

2016

MJCS

View full text Add to dashboard Cite

show abstract

“…We shall use them as ground-truth results in our experiments. MoJoFM [11] is used to measure the similarity degree between the ground-truth and a given module view.…”

Section: Experiments and Evaluationmentioning

confidence: 99%

Adaptive Weighting of Structural Dependency and Textual Similarity in Software Architecture Recovery

Lee

2016

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYSoftware architecture recovery techniques are often adopted to derive a module view of software from its source code in case software architecture documents are unavailable or outdated. The module view is one of the most important perspectives of software architecture. In this paper, we propose a novel approach to derive a module view by adaptively integrating structural dependency and textual similarity. Our approach utilizes Newman modularity and Shannon information entropy to determine the appropriate weights of the dependencies during the integration. We apply our approach to various open-source projects and show the experimental results validating the effectiveness of the approach. key words: software architecture recovery, module view, dependency, Newman modularity, information entropy

show abstract

“…There exist automated techniques that mine exception handling rules from the source code (THUMMALAPENTA and XIE, 2009). Also, exception handling policies are often aligned with architectural design rules, so techniques for recovering architectural design rules from the source code (GARCIA et al, 2013) can also assist developers in extracting exception handling policies from the source code. These solutions could be used to extract exception handling rules that express how exception handling is implemented in the source code.…”

Section: Interview Analysismentioning

confidence: 99%

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

A comparative analysis of software architecture recovery techniques

Cited by 131 publications

References 38 publications

Supervised Learning For Orphan Adoption Problem In Software Architecture Recovery

Supervised Learning For Orphan Adoption Problem In Software Architecture Recovery

Adaptive Weighting of Structural Dependency and Textual Similarity in Software Architecture Recovery

Global-Aware Recommendations for Repairing Exception Handling Violations

Contact Info

Product

Resources

About