Sara Abbaspour Asadollah

10 Years of research on debugging concurrent and multicore software: a systematic mapping study

AbstractDebugging—the process of identifying, localizing and fixing bugs—is a key activity in software development . Due to issues such as non-determinism and difficulties of reproducing failures, debugging concurrent software is significantly more challenging than debugging sequential software. A number of methods, models and tools for debugging concurrent and multicore software have been proposed, but the body of work partially lacks a common terminology and a more recent view of the problems to solve. This suggests the need for a classification, and an up-to-date comprehensive overview of the area. This paper presents the results of a systematic mapping study in the field of debugging of concurrent and multicore software in the last decade (2005–2014). The study is guided by two objectives: (1) to summarize the recent publication trends and (2) to clarify current research gaps in the field. Through a multi-stage selection process, we identified 145 relevant papers. Based on these, we summarize the publication trend in the field by showing distribution of publications with respect to year, publication venues, representation of academia and industry, and active research institutes. We also identify research gaps in the field based on attributes such as types of concurrency bugs, types of debugging processes, types of research and research contributions. The main observations from the study are that during the years 2005–2014: (1) there is no focal conference or venue to publish papers in this area; hence, a large variety of conferences and journal venues (90) are used to publish relevant papers in this area; (2) in terms of publication contribution, academia was more active in this area than industry; (3) most publications in the field address the data race bug; (4) bug identification is the most common stage of debugging addressed by articles in the period; (5) there are six types of research approaches found, with solution proposals being the most common one; and (6) the published papers essentially focus on four different types of contributions, with “methods” being the most common type. We can further conclude that there are still quite a number of aspects that are not sufficiently covered in the field, most notably including (1) exploring correction and fixing bugs in terms of debugging process; (2) order violation, suspension and starvation in terms of concurrency bugs; (3) validation and evaluation research in the matter of research type; (4) metric in terms of research contribution. It is clear that the concurrent, parallel and multicore software community needs broader studies in debugging. This systematic mapping study can help direct such efforts.

A Survey on Testing for Cyber Physical System

Cyber Physical Systems CPS bridge the cyber-world of computing and communications with the physical world and require development of secure and reliable software. It asserts a big challenge not only on testing and verifying the correctness of all physical and cyber components of such big systems, but also on integration of these components. This paper develops a categorization of multiple levels of testing required to test CPS and makes a comparison of these levels with the levels of software testing based on the V-model. It presents a detailed state-of-the-art survey on the testing approaches performed on the CPS. Further, it provides challenges in CPS testing.

Web Service Response Time Monitoring: Architecture and Validation

Web services are used in many Web applications in order to save time and cost during software development process. To peruse Web service response time, a suitable tool is needed to automate the measurement of the response time. However, not many suitable tools are available for automatic measurement of response time. This research is carried out in the context of quality of Web services in order to measure and visualize Web service response time. The method proposed in this research for accomplishing this goal is based on creating a proxy for connecting to the required Web service, and then calculating the Web services response time via the proxy. A software tool is designed based on the proposed method in order to guide the implementation that is still in progress. The tool can be validated through empirical validation using three test cases for three different Web service access situations.

Towards classification of concurrency bugs based on observable properties

In software engineering, classification is a way to find an organized structure of knowledge about objects. Classification serves to investigate the relationship between the items to be classified, and can be used to identify the current gaps in the field. In many cases users are able to order and relate objects by fitting them in a category. This paper presents initial work on a taxonomy for classification of errors (bugs) related to concurrent execution of application level software threads. By classifying concurrency bugs based on their corresponding observable properties, this research aims to examine and structure the state of the art in this field, as well as to provide practitioner support for testing and debugging of concurrent software. We also show how the proposed classification, and the different classes of bugs, relates to the state of the art in the field by providing a mapping of the classification to a number of recently published papers in the software engineering field.

A Study of Concurrency Bugs in an Open Source Software

Concurrent programming puts demands on software debugging and testing, as concurrent software may exhibit problems not present in sequential software, e.g., deadlocks and race conditions. In aiming to increase efficiency and effectiveness of debugging and bug-fixing for concurrent software, a deep understanding of concurrency bugs, their frequency and fixing-times would be helpful. Similarly, to design effective tools and techniques for testing and debugging concurrent software understanding the differences between non-concurrency and concurrency bugs in real-word software would be useful. This paper presents an empirical study focusing on understanding the differences and similarities between concurrency bugs and other bugs, as well as the differences among various concurrency bug types in terms of their severity and their fixing time. Our basis is a comprehensive analysis of bug reports covering several generations of an open source software system. The analysis involves a total of 4872 bug reports from the last decade, including 221 reports related to concurrency bugs. We found that concurrency bugs are different from other bugs in terms of their fixing time and their severity. Our findings shed light on concurrency bugs and could thereby influence future design and development of concurrent software, their debugging and testing, as well as related tools.

Management of Service Level Agreements for Cloud Services in IoT: A Systematic Mapping Study

Cloud computing and Internet of Things (IoT) are computing technologies that provide services to consumers and businesses, allowing organizations to become more agile and flexible. Therefore, ensuring quality of service (QoS) through service-level agreements (SLAs) for such cloud-based services is crucial for both the service providers and service consumers. As SLAs are critical for cloud deployments and wider adoption of cloud services, the management of SLAs in cloud and IoT has thus become an important and essential aspect. This paper investigates the existing research on the management of SLAs in IoT applications that are based on cloud services. For this purpose, a systematic mapping study (a well-defined method) is conducted to identify the published research results that are relevant to SLAs. This paper identifies 328 primary studies and categorizes them into seven main technical classifications: SLA management, SLA definition, SLA modeling, SLA negotiation, SLA monitoring, SLA violation and trustworthiness, and SLA evolution. This paper also summarizes the research types, research contributions, and demographic information in these studies. The evaluation of the results shows that most of the approaches for managing SLAs are applied in academic or controlled experiments with limited industrial settings rather than in real industrial environments. Many studies focus on proposal models and methods to manage SLAs, and there is a lack of focus on the evolution perspective and a lack of adequate tool support to facilitate practitioners in their SLA management activities. Moreover, the scarce number of studies focusing on concrete metrics for qualitative or quantitative assessment of QoS in SLAs urges the need for in-depth research on metrics definition and measurements for SLAs.

Concurrency bugs in open source software: a case study

Concurrent programming puts demands on software debugging and testing, as concurrent software may exhibit problems not present in sequential software, e.g., deadlocks and race conditions. In aiming to increase efficiency and effectiveness of debugging and bug-fixing for concurrent software, a deep understanding of concurrency bugs, their frequency and fixing-times would be helpful. Similarly, to design effective tools and techniques for testing and debugging concurrent software, understanding the differences between non-concurrency and concurrency bugs in real-word software would be useful.This paper presents an empirical study focusing on understanding the differences and similarities between concurrency bugs and other bugs, as well as the differences among various concurrency bug types in terms of their severity and their fixing time, and reproducibility. Our basis is a comprehensive analysis of bug reports covering several generations of five open source software projects. The analysis involves a total of 11860 bug reports from the last decade, including 351 reports related to concurrency bugs. We found that concurrency bugs are different from other bugs in terms of their fixing time and severity while they are similar in terms of reproducibility. Our findings shed light on concurrency bugs and could thereby influence future design and development of concurrent software, their debugging and testing, as well as related tools.

Runtime Verification for Detecting Suspension Bugs in Multicore and Parallel Software

Multicore hardware development increases the popularity of parallel and multicore software, while testing and debugging the software become more difficult, frustrating and costly. Among all types of software bugs, concurrency bugs are both important and troublesome. This type of bugs is increasingly becoming an issue, particularly due to the growing prevalence of multicore hardware. Suspension-based-locking bug is one type of concurrency bugs. This position paper proposes a model based on runtime verification and reflection technique in the context of multicore and parallel software to monitor and detect suspension-based-locking bugs. The model is not only able to detect faults, but also diagnose and even repair them. The model is composed of four layers: Logging, Monitoring, Suspension Bug Diagnosis and Mitigation. The logging layer will observe the events and save them into a file system. The monitoring layer will detect the presents of bugs in the software. The suspension bug diagnosis will identify Suspension bugs by comparing the captured data with the suspension bug properties. Finally, the mitigation layer will reconfigure the software to mitigate the suspension bugs. A functional architecture of a runtime verification tool is also proposed in this paper. This architecture is based on the proposed model and is comprised of different modules.

SLAs for Industrial IoT: Mind the Gap

Cloud computing and Internet of Things (IoT) are computing technologies that provide services to consumers and businesses, allowing organizations to become more agile and flexible. The potential business values that cloud consumers can achieve depend a lot on the quality of service in the provided cloud services. Therefore, ensuring the quality of service through service-level agreements (SLA) for such cloud-based services is crucial for both the service providers and service consumers. As SLA is critical for cloud deployments and wider adoption of cloud services, the management of SLA in cloud and IoT has thus become an important and essential issue. In this paper we provide an understanding of the current status and maturity level of SLA management in industrial IoT and academic efforts in this field. We also conduct a preliminary survey of current research on SLA management in order to identify open challenges and gaps that need to be addressed in future research directions. In particular, we investigate how to provide useful SLA management support adapted to the maturity level and current industrial practices, and shorten the gap between academia and industry.

The pedagogical challenges of creating information literate librarians

Purpose This study aims to investigate the challenges of developing information literacy (IL) competencies and approaches to overcome the challenges among library and information science (LIS) students in Iran. Design/methodology/approach Taking an exploratory approach, the study used semi-structured interviews to gather the data. Using the 2000 ACRL standards as a framework, the fieldwork questions were designed around the five areas of IL competencies. A total of 15 academics teaching 18 different LIS courses from six universities were interviewed. They were asked the challenges they faced in teaching these competencies and the approaches they took or suggested in overcoming the challenge(s). A thematic approach was used to analyze the data. Findings Some of the challenges for students mentioned by the interviewees were ambiguity about the discipline, inability to match subject relevance with appropriate sources of information and lack of familiarity with databases. Research limitations/implications This study is limited to LIS academics; studying students’ reflections can bring broader perspectives to IL education in LIS programs. Owing to the nature of the design of this study, which is a single case study, the teaching experiences of IL are limited to the ones which emerged and were addressed in the context of the case. Although the case selection was made in a way that can be representative of the “general” in the “particular” bounded system of the case (Stake, 1998), studying more cases could certainly have brought broader perspectives to IL which could have been to wider contexts. Originality/value The results of this study contribute to our understanding of challenges in teaching IL in the LIS discipline, an area that has not been researched directly. This contributes to IL teaching in disciplinary areas and it brings new perspectives to the elements of IL teaching which emerged from the experiences of people who are directly experienced in the context of the discipline.