Interactive Refactoring of Web Service Interfaces Using Computational Search

Wang, Hanzhang; Kessentini, Marouane; Ouni, Ali

doi:10.1109/tsc.2017.2787152

Cited by 7 publications

(9 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Further, modifications and changes in web services increase users' complexity to perform relevant operations by the unnecessarily complex interfaces. The latter study is aimed at fixing the design anti-patterns of web services [56].…”

Section: Related Workmentioning

confidence: 99%

Benchmark Dataset Selection of Web Services Technologies: A Factor Analysis

et al. 2020

View full text Add to dashboard Cite

Web services have emerged as an accessible technology with the standard 'Extensible Mark Up' (XML) language, which is known as 'Web Services Description Language' WSDL. Web services have become a promising technology to promote the interrelationship between service providers and users. Web services users' trust is measured by quality metrics. Web service quality metrics vary in many benchmark datasets used in the existing studies. The selection of a benchmark dataset is problematic to classify and retest web services. This paper proposes a method to rank web services quality metrics for the selection of benchmark web services datasets. To measure the diversity in quality metrics, factor analysis with Varimax rotation and scree plot is a well-established method. We use factor analysis to determine percentage variance among principal factors of four benchmark datasets. Our results showed that the two-factor solution explained 94.501, 76.524, and 45.009% variances in datasets A, B, and D, respectively. A three-factor solution explained 85.085% variance in dataset C. Reliability, and response time quality metrics were predicted as the most dominating quality metrics that contributed to explain the percentage variance in four datasets. Our proposed web metric ranking (WMR) method resulted in reliability as the topmost web metric with (57.62%) score and latency web metric at the bottom-most with (3.60%) score. The proposed WMR method showed a high (96.17%) ranking precision. Obtained results verified that factor solutions after reducing the dimensions could be generalized and used in the quality improvement of web services. In future works, the authors plan to focus on a dataset with dominating quality metrics to perform regression testing of web services. INDEX TERMS Factor analysis, quality metrics, rotated loading, reliability, response time, regression testing, web services.

show abstract

Section: Related Workmentioning

confidence: 99%

Benchmark Dataset Selection of Web Services Technologies: A Factor Analysis

et al. 2020

View full text Add to dashboard Cite

show abstract

“…This anti-pattern occurs when a set of operations are required to execute single abstraction [20], [58]. Consequently, web services often have many compact operations that increase response time; therefore, limiting the web services performance [83].…”

Section: Chatty Web Service (Cws)mentioning

confidence: 99%

“…This anti-pattern occurs when web services consist of getters and setters' operations (i.e., accessor operation) [83]. DWS anti-pattern in distributed environment refers to web services that only execute data access operations or simple information retrieval [20], [58]. DWS may negatively impact web service usability because it commonly handles small messages of primitive data types with strong data cohesion [10].…”

Section: Data Web Service (Dws)mentioning

confidence: 99%

“…This anti-pattern occurs when a web service supports remote procedure call [20] that allows Create, Read, Update and Delete (CRUD) operations from databases [10], [58]. The CRUD operations require several methods to be accomplished which increases the complexity of web services [10].…”

Section: Crud Interface (Ci)mentioning

confidence: 99%

“…Like other computer-based systems, anti-patterns problems are found in web services due to inappropriate programming practices, designs, and implementations [19]. It caused accessibility issues in which the function of the services is difficult to comprehend [20], [21]; thus, making the process of designing interface complex and low quality. Eventually, the web service becomes abandoned due to low usage [22].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

SOAP and RESTful web service anti-patterns: A scoping review

Alshraiedeh¹

2019

IJATCSE

View full text Add to dashboard Cite

Web services provide a uniform framework to achieve a high level of interaction between distributed heterogeneous software systems and data resources shared over the Internet. Producing a well-designed web service is significant because it leads to a more understandable service and a higher level of interaction and leads to effective software maintainability. However, web service is suffering from a poor design problem named anti-patterns. Analysis of the literature returned a plethora of studies on anti-patterns that caused difficulties for developers to synthesize and summarized the possible types of anti-patterns and further comprehend each of them. Due to this limitation, this paper aims to provide organized literature on the types of anti-patterns found in web services. A scoping review was conducted by searching scholarly documents, analyzing, and classified them based on their anti-pattern types. The review provided in this paper could be used as a guide for developers to identify the antipatterns that could be found in web services.

show abstract

Model‐based source code refactoring with interaction and visual cues

Hemati Moghadam,

Ó Cinnéide,

Sardarian

et al. 2023

J Software Evolu Process

View full text Add to dashboard Cite

Refactoring source code involves the developer in a myriad of program detail that can obscure the design changes that they actually wish to bring about. On the other hand, refactoring a UML model of the code makes it easier to focus on the program design, but the burdensome task of applying the refactorings to the source code is left to the developer. In an attempt to obtain the advantages of both approaches, we propose a refactoring approach where the interaction with the developer takes place at the model level, but the actual refactoring occurs on the source code itself. We call this approach model‐based source code refactoring and implement it in this paper using two tools: (1) Design‐Imp enables the developer to use interactive search‐based design exploration to create a UML‐based desired design from an initial design extracted from the source code. It also provides visual cues to improve developer comprehension during the design‐level refactoring process and to help the developer to discern between promising and poor refactoring solutions. (2) Code‐Imp then refactors the original source so that it has the same functional behavior as the original program, and a design close to the one produced in the design exploration phase, that is, a design that has been confirmed as “desirable” by the developer. We evaluated our approach involving interaction and visual cues with industrial developers refactoring three Java projects, comparing it with an approach using interaction without visual cues and a fully automated approach. The results show that our approach yields refactoring sequences that are more acceptable both to the individual developer and to a set of independent expert refactoring evaluators. Furthermore, our approach removed more code smells and was evaluated very positively by the experiment participants.

show abstract

Interactive Refactoring of Web Service Interfaces Using Computational Search

Cited by 7 publications

References 32 publications

Benchmark Dataset Selection of Web Services Technologies: A Factor Analysis

Benchmark Dataset Selection of Web Services Technologies: A Factor Analysis

SOAP and RESTful web service anti-patterns: A scoping review

Model‐based source code refactoring with interaction and visual cues

Contact Info

Product

Resources

About