2018
DOI: 10.20532/cit.2017.1003569
|View full text |Cite
|
Sign up to set email alerts
|

Extended Fault Taxonomy of SOA-Based Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
4
2

Relationship

2
4

Authors

Journals

citations
Cited by 9 publications
(3 citation statements)
references
References 59 publications
0
3
0
Order By: Relevance
“…Wang et al [7] have categorised fault types on the basis of four contexts such as functional context, QoS context, domain context and platform context faults. The fault taxonomy is presented in [7, 16, 48, 51, 97–99]. In these taxonomies, faults of SOS are categorised into two major categories such as SOA cycle‐specific faults and distributed system faults.…”
Section: Results Of the Systematic Reviewmentioning
confidence: 99%
“…Wang et al [7] have categorised fault types on the basis of four contexts such as functional context, QoS context, domain context and platform context faults. The fault taxonomy is presented in [7, 16, 48, 51, 97–99]. In these taxonomies, faults of SOS are categorised into two major categories such as SOA cycle‐specific faults and distributed system faults.…”
Section: Results Of the Systematic Reviewmentioning
confidence: 99%
“…Fault recovery plays a crucial role in testing web service composition, enabling the creation of a more resilient and smoothly functioning system that can promptly recover from encountered faults [1,21] This, in turn, enhances availability, scalability, and composition quality, while minimizing costs and efforts under expected operational conditions [22,23]. Numerous studies have addressed fault tolerance and recovery strategies for Service-Oriented Computing (SOC) systems [1,13,14,21,22,24,25]. However, the majority of these studies focus on proposing recovery approaches for substituting the faulty service rather than considering any other recovery strategy.…”
Section: Related Workmentioning
confidence: 99%
“…One fault can escalate another serious fault or multiple faults and bring the systems to failure. Injecting a fault at the program level can be associated with the multiple faults at the application level, as specified in Bhandari and Gupta (2018a, b). For example, a fault in a method’s parameter can cause a messaging error, communication failures, invalid method invocation faults, etc.…”
Section: Research Backgroundmentioning
confidence: 99%