BPELDebugger: An effective BPEL-specific fault localization framework

Sun, C.T.; Zhai, Yi Meng; Shang, Yan; Zhang, Zhenyu

doi:10.1016/j.infsof.2013.07.009

Cited by 10 publications

(7 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Real-life programs such as grep was utilised by 11 studies. Moreover, real-time systems and programs such as helicopter control system, BPEL programs, VLC, Firework, MYSQL database, and Wireshark were used as well [56,57,[64][65][66]. Hence, from 2014-2016, Siemens suite programs were considerably used by many studies with few relevant studies utilising the others.…”

Section: Rq3 Which Datasets Are Used For Software Fault Localisation?mentioning

confidence: 99%

Software fault localisation: a systematic mapping study

et al. 2019

View full text Add to dashboard Cite

Software fault localisation (SFL) is recognised to be one of the most tedious, costly, and critical activities in program debugging. Due to the increase in software complexity, there is a huge interest in advanced SFL techniques that aid software engineers in locating program bugs. This interest paves a way to the existence of a large amount of literature in the SFL research domain. This study aims to investigate the overall research productivity, demographics, and trends shaping the landscape of SFL research domain. The research also aims to classify existing fault localisation techniques and identify trends in the field of study. Accordingly, a systematic mapping study of 273 primary selected studies is conducted with the adoption of an evidence-based systematic methodology to ensure coverage of all relevant studies. The results of this systematic mapping study show that SFL research domain is gaining more attention since 2010, with an increasing number of publications per year. Three main research facets were identified, i.e. validation research, evaluation research, and solution research, with solution research type getting more attention. Hence, various contribution facets were identified as well. In totality, general demographics of SFL research domain were highlighted and discussed.

show abstract

Section: Rq3 Which Datasets Are Used For Software Fault Localisation?mentioning

confidence: 99%

Software fault localisation: a systematic mapping study

et al. 2019

View full text Add to dashboard Cite

show abstract

“…• semantic service matching mechanism [89] • analytical technique for BPEL's advances composition features [111] • CTMCs using redundant systems [88] security and privacy [68,69,104,105,120,121] • invalid access control [68,104,105] • detect vulnerability [120] • enforce security in SLAs [121] • security patterns [69] • three-phase composition protocol [104] • SOA-scanner tool [120] • fuzzy authentication with past interactions and linguistic policies [68] • security controls enforcement and allocation [121] • mathematical model based on fuzzy-set theory and fuzzy fault trees [69] • policy-based segmentation technique [105] fault localisation [73,124] to detect the location of the fault and root cause institutions making it harder to perform true rollback [26] which is the major challenge for failure recovery. It is suitable for database technologies but as far as SOA is concerned it would not be due to its unique features such as interoperability and platformindependent distributed systems.…”

Section: Summary Of Reviewed Studiesmentioning

confidence: 99%

Fault analysis of service‐oriented systems: a systematic literature review

Bhandari

Gupta

2018

IET softw.

View full text Add to dashboard Cite

Due to the increasing scale and complexity of service-oriented systems (SOSs) understanding fault and its recovery mechanism is a tedious task so there is a strong demand for a summary of the SOSs fault analysis knowledge that can assist further developers and researchers to plan appropriate action and guidelines for SOSs development. The objective of this systematic literature review (SLR) is to summarise the current state-of-the-art of fault analysis in SOSs. The authors have used the predefined SLR method employing a manual search of 11 highly reputed international journals and three conference proceedings. The categorisation and organisation were done according to the research questions regarding approaches, fault types, current issues and challenges and tools of fault analysis on SOSs. After applying selection criteria, this SLR includes 123 papers published between January 2008 and April 2017, 65 papers address SOSs-fault handling approaches, 35 papers report SOS-specific faults and 51 papers address SOS issues, challenges, and testing and 17 papers are of tooling. They have discussed the main approaches, techniques, concepts, contributions and research methods used for fault analysis of SOSs. Through the paper, a comprehensive review work has been presented that provides empirical evidence for establishing future research agendas.

show abstract

“…Although WS-BPEL has standard control structures, such as sequences, branches, and loops, WS-BPEL programs are significantly different from the traditional programs in the following aspects [35]: (i) WS-BPEL provides an explicit integration mechanism to compose Web services into large-scale systems, while such integrations in traditional programs are implicit; (ii) Web services used by WS-BPEL programs may be implemented in different programming languages, while modules in the traditional programs are usually implemented in the same programming language; (iii) WS-BPEL programs are represented as XML files, and the statements are not the same as those in the traditional programs; (iv) WS-BPEL supports concurrency among activities via flow activities and synchronization via link tags within flows, which is not common in traditional programs. When implementing such WS-BPEL programs, people may introduce new types of faults that are different from those in traditional programs due to these new features of WS-BPEL programs.…”

Section: Business Process Execution Language For Web Services (Ws-bpel)mentioning

confidence: 99%

“…Since a WS-BPEL program is represented as an XML file, we use the number of XML lines to represent the size of the WS-BPEL program. In the SupplyChain program [35], the customer is required to input the name and number of products, and the retailer will provide feedback based on the order and the status of warehouse. For the SmartShelf program [35], the input is some information of commodity, such as name and number, and the output includes the quantity in warehouse, the location of shelf, and the status of commodity.…”

Section: Subject Programsmentioning

confidence: 99%

“…In the SupplyChain program [35], the customer is required to input the name and number of products, and the retailer will provide feedback based on the order and the status of warehouse. For the SmartShelf program [35], the input is some information of commodity, such as name and number, and the output includes the quantity in warehouse, the location of shelf, and the status of commodity. In the SupplyCusomter program [29], the customer inputs the items and address of the order, and the system replies the validation result.…”

Section: Subject Programsmentioning

confidence: 99%

See 1 more Smart Citation

An Empirical Study on Mutation Testing of WS-BPEL Programs

Sun

Lin

Wang

et al. 2016

The Computer Journal

Self Cite

View full text Add to dashboard Cite

Nowadays, applications are increasingly deployed as Web services in the globally distributed cloud computing environment. Multiple services are normally composed to fulfill complex functionalities. Business Process Execution Language for Web Services (WS-BPEL) is an XML-based service composition language that is used to define a complex business process by orchestrating multiple services. Compared with traditional applications, WS-BPEL programs pose many new challenges to the quality assurance, especially testing, of service compositions. A number of techniques have been proposed for testing WS-BPEL programs, but only a few studies have been conducted to systematically evaluate the effectiveness of these techniques. Mutation testing has been widely acknowledged as not only a testing method in its own right, but also a popular technique for measuring the fault-detection effectiveness of other testing methods. Several previous studies have proposed a family of mutation operators for generating mutants by seeding various faults into WS-BPEL programs. In this study, we conduct a series of empirical studies to evaluate the applicability and effectiveness of various mutation operators for WS-BPEL programs. The experimental results provide insightful and comprehensive guidance for mutation testing of WS-BPEL programs in practice. In particular, our work is the systematic study in the selection of effective mutation operators specifically for WS-BPEL programs.

show abstract

BPELDebugger: An effective BPEL-specific fault localization framework

Cited by 10 publications

References 30 publications

Software fault localisation: a systematic mapping study

Software fault localisation: a systematic mapping study

Fault analysis of service‐oriented systems: a systematic literature review

An Empirical Study on Mutation Testing of WS-BPEL Programs

Contact Info

Product

Resources

About