Deriving Component Interfaces after a Restructuring of a Legacy System

2014 IEEE/IFIP Conference on Software Architecture Pub Date : 2014-04-07 DOI:10.1109/WICSA.2014.27

Abderrahmane Seriai, Salah Sadou, H. Sahraoui, Salma Hamza

{"title":"Deriving Component Interfaces after a Restructuring of a Legacy System","authors":"Abderrahmane Seriai, Salah Sadou, H. Sahraoui, Salma Hamza","doi":"10.1109/WICSA.2014.27","DOIUrl":null,"url":null,"abstract":"Although there are contributions on component-oriented languages, components are mostly implemented using object-oriented (OO) languages. In this perspective, a component corresponds to a set of classes that work together to provide one or more services. Services are grouped together in interfaces that are each implemented by a class. Thus, dependencies between components are defined using the semantic of the enclosed classes, which is mostly structural. This makes it difficult to understand an architecture described with such links. Indeed, at an architectural level dependencies between components must represent functional aspects. This problem is worse, when the components are obtained by re-engineering of legacy OO systems. Indeed, in this case the obtained components are mainly based on the consistency of the grouping logic. So, in this paper we propose an approach to identify the interfaces of a component according to its interactions with the other components. To this end, we use formal concept analysis. The evaluation of the proposed approach via an empirical study showed that the identified interfaces overall correspond to the different functional aspects of the components.","PeriodicalId":346971,"journal":{"name":"2014 IEEE/IFIP Conference on Software Architecture","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2014-04-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"12","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2014 IEEE/IFIP Conference on Software Architecture","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/WICSA.2014.27","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 12

Abstract

Although there are contributions on component-oriented languages, components are mostly implemented using object-oriented (OO) languages. In this perspective, a component corresponds to a set of classes that work together to provide one or more services. Services are grouped together in interfaces that are each implemented by a class. Thus, dependencies between components are defined using the semantic of the enclosed classes, which is mostly structural. This makes it difficult to understand an architecture described with such links. Indeed, at an architectural level dependencies between components must represent functional aspects. This problem is worse, when the components are obtained by re-engineering of legacy OO systems. Indeed, in this case the obtained components are mainly based on the consistency of the grouping logic. So, in this paper we propose an approach to identify the interfaces of a component according to its interactions with the other components. To this end, we use formal concept analysis. The evaluation of the proposed approach via an empirical study showed that the identified interfaces overall correspond to the different functional aspects of the components.

查看原文本刊更多论文

在遗留系统重构后派生组件接口

尽管在面向组件的语言方面有一些贡献，但组件主要是使用面向对象(OO)语言实现的。从这个角度来看，组件对应于一组协同工作以提供一个或多个服务的类。服务在接口中分组在一起，每个接口由一个类实现。因此，组件之间的依赖关系是使用封闭类的语义定义的，这主要是结构化的。这使得很难理解用这种链接描述的体系结构。实际上，在体系结构级别上，组件之间的依赖关系必须表示功能方面。如果组件是通过重新设计遗留OO系统获得的，那么这个问题会更糟。实际上，在这种情况下，获得的组件主要基于分组逻辑的一致性。因此，在本文中，我们提出了一种根据组件与其他组件的交互来识别组件接口的方法。为此，我们采用形式概念分析。通过实证研究对该方法的评价表明，所识别的接口总体上对应于组件的不同功能方面。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文求助全文

来源期刊

2014 IEEE/IFIP Conference on Software Architecture

自引率

0.00%

发文量