2013 20th Working Conference on Reverse Engineering (WCRE) 2013
DOI: 10.1109/wcre.2013.6671307
|View full text |Cite
|
Sign up to set email alerts
|

Improving SOA antipatterns detection in Service Based Systems by mining execution traces

Abstract: Abstract-Service Based Systems (SBSs), like other software systems, evolve due to changes in both user requirements and execution contexts. Continuous evolution could easily deteriorate the design and reduce the Quality of Service (QoS) of SBSs and may result in poor design solutions, commonly known as SOA antipatterns. SOA antipatterns lead to a reduced maintainability and reusability of SBSs. It is therefore important to first detect and then remove them. However, techniques for SOA antipattern detection are… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
14
0
2

Year Published

2014
2014
2018
2018

Publication Types

Select...
4
2
1

Relationship

2
5

Authors

Journals

citations
Cited by 17 publications
(16 citation statements)
references
References 29 publications
0
14
0
2
Order By: Relevance
“…A few contributions are available on the detection of SOA (anti)patterns for various SOA standards, e.g., SCA (Service Component Architecture) [3,[9][10][11] and Web services [13]. To the best of our knowledge, the detection of REST (anti)patterns, in the literature deserves yet to receive attention.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…A few contributions are available on the detection of SOA (anti)patterns for various SOA standards, e.g., SCA (Service Component Architecture) [3,[9][10][11] and Web services [13]. To the best of our knowledge, the detection of REST (anti)patterns, in the literature deserves yet to receive attention.…”
Section: Related Workmentioning
confidence: 99%
“…Despite the presence of several technologyspecific approaches in SCA (Service Component Architecture) and Web services (e.g., [3,[9][10][11]13]), they are not applicable for detecting (anti)patterns in REST. Indeed, the key differences between REST architecture and other SOA standards prevents the application of these approaches because: (1) traditional serviceorientation is operations-centric, whereas REST is resources-centric, (2) RESTful services are on top of JSON (or XML) over HTTP, whereas traditional Web services are on top of SOAP over HTTP or JMS (Java Message Service), (3) Web services use WSDL (Web Service Definition Language) as their formal contracts; REST has no standardised contract except the human-readable documentations, (4) traditional services are the set of self-contained software artefacts where operations are denoted using verbs; resources in REST are denoted by nouns and are directlyaccessible objects via URIs, and (5) REST clients use the standard HTTP methods to interact with resources; Web services clients implement separate client-stubs to consume services.…”
Section: Introductionmentioning
confidence: 99%
“…Most state of the art techniques focused on detection of anti-patterns from object oriented software applications but these techniques are not capable of detecting anti-patterns from SOA. We identified only a few representative approaches on specification and detection of SOA anti-patterns from Web-services [9,12,13,14,15,16,18]. To the best of our knowledge, most authors used different metrics and static/ dynamic analysis methods for the detection of anti-patterns from web-services.…”
Section: Introductionmentioning
confidence: 99%
“…A manutenção de software ainda possui um alto custo e as empresas gastam muito tempo tentando entender e implementar mudanças nos sistemas (SEACORD; PLAKOSH; LEWIS, 2003; DIT; REVELLE; POSHYVANYK, 2013;MEYER, 2000). Mesmo as abordagens úteis existentes baseadas no código fonte (que detectam mudanças estruturais) e em históricos de versões (que detectam mudanças lógicas), carecem de informações comportamentais e não capturam satisfatoriamente mudanças associadas a funcionalidades específicas.…”
Section: Standardserverunclassified
“…Abordagens baseadas em análise dinâmica são usadas para medir o acoplamento dinâ-mico (ARISHOLM; FOYEN, 2004), implementar novas funcionalidades (SILVA et al, 2011), tratamento de bug (ROEHM; NOSOVIC; BRUEGGE, 2015), reconstrução da arquitetura (RIVA; RODRIGUEZ, 2002) e em projetos SOA (NAYROLLES; MOHA; VALTCHEV, 2013;PAUW et al, 2005). Um algoritmo foi proposto para remover detalhes de implementação (SILVA et al, 2011).…”
Section: Análise Dinâmicaunclassified