2018
DOI: 10.1016/j.csi.2017.09.010
|View full text |Cite
|
Sign up to set email alerts
|

Spotting and Removing WSDL Anti-pattern Root Causes in Code-first Web Services Using NLP Techniques : A Thorough Validation of Impact on Service Discoverability

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 9 publications
(7 citation statements)
references
References 43 publications
(157 reference statements)
0
7
0
Order By: Relevance
“…Correspondingly, 4 life cycle models were created for these business entities. The validation of these behavioural interface models was performed by invoking the services with the sequences derived, and the results show that the temporal sequences revealed in the models are valid and match with what is described in the FedEx OpenShipping reference 17 .…”
Section: Validation Of Behavioural Interface Synthesismentioning
confidence: 80%
See 1 more Smart Citation
“…Correspondingly, 4 life cycle models were created for these business entities. The validation of these behavioural interface models was performed by invoking the services with the sequences derived, and the results show that the temporal sequences revealed in the models are valid and match with what is described in the FedEx OpenShipping reference 17 .…”
Section: Validation Of Behavioural Interface Synthesismentioning
confidence: 80%
“…This reflected the wider goal of the approach, for WSDL to REST API translation. Other text mining approaches for WSDL specifications focus on detection of anti-patterns by Mateos et al [16] and Hirsch et al [17], and quantification of WSDL specification readability by De Renzis et al [18]. Furthermore, a number of metrics were proposed to demonstrate the quality of service interfaces in the context of legacy systems modernization, through the work of Mateos et al [19] which concerned COBOL to SOA migration.…”
Section: Related Workmentioning
confidence: 99%
“…Anti-patterns could also happen in the design of URIs, which are named as amorphous URIs, CRUD URI, pluralised nodes, contextless recourse names, non-hierarchical nodes and ambiguous names (Alshraiedeh and Katuk, 2019). Hirsch et al (2018) and Mateos et al (2015b) studied ambiguous name anti-patterns in SOAP to define the corresponding definition in RESTful WS through the SOAP description document, such as portTypes, operations and parameters. For the URIs, the corresponding nodes include resources parameters and resources path.…”
Section: Related Workmentioning
confidence: 99%
“…This algorithm addresses the ambiguous names. Checking the meaning of the names of the URI nodes. The algorithm analyses the name of the URI nodes against known unrepresentative names such as param, arg, var, obj, object, foo, input, output, in# and out#, where # might be replaced by a number or nothing (Hirsch et al , 2018; Mateos et al , 2015b). Other characteristics that need to be tackled is to detect unrepresentative name.…”
Section: The Proposed Uniform Resource Identifiers Parsing Technique and Algorithm For Restful Web Services Anti-pattern Detectionmentioning
confidence: 99%
“…Web service is a group of loosely coupled applications, selfdescribing software, that can be published, located and accessed flexibly and smoothly [1]- [3]. It provides a uniform framework to achieve a high level of interaction between the distributed heterogeneous software system and data resource sharing over the Internet [4]- [6]. In a simple word, web service can be described as independent software components that accept requests and return responses over the Internet.…”
Section: Introductionmentioning
confidence: 99%