| 31. |
- Abbasi, Shirin, et al.
(författare)
-
Internet of Vehicles : Architecture, services, and applications
- 2021
-
Ingår i: International Journal of Communication Systems. - : John Wiley and Sons Ltd. - 1074-5351 .- 1099-1131. ; 34:10
-
Tidskriftsartikel (refereegranskat)abstract
- The connection between objects and information exchange has been possible in recent years, with the advent of the Internet of Things (IoT) in different industries. We can meet different requirements in each industry utilizing this feature. Intelligent transportation uses the Internet of Vehicles (IoV) as a solution for communication among vehicles. It improves traffic management applications and services to guarantee safety on roads. We categorize services, applications, and architectures and propose a taxonomy for IoV. Then, we study open issues and challenges for future works. We highlighted applications and services due to drivers' requirements and nonfunctional requirements, considering the qualitative characteristic. This paper summarizes the current state of the IoV in architectures, services, and applications. It can be a start view to provide the solutions for challenges in traffic management in cities. The present study is beneficial for smart city developments and management. According to this paper's result, the services and applications evaluate performance with 34% frequency, safety and data accuracy, and security with a 13% frequency in selected papers. These measurements are essential due to the IoV characteristics such as real-time operation, accident avoidance in applications, and complicated user data management.
|
|
| 32. |
- Abbaspour Asadollah, Sara, et al.
(författare)
-
10 Years of research on debugging concurrent and multicore software : a systematic mapping study
- 2017
-
Ingår i: Software quality journal. - : Springer Science and Business Media LLC. - 0963-9314 .- 1573-1367. ; 25:1, s. 49-82
-
Tidskriftsartikel (refereegranskat)abstract
- Debugging – 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 type most common one.We can further conclude that there is 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.
|
|
| 33. |
- Abbaspour Asadollah, Sara, et al.
(författare)
-
A Model for Systematic Monitoring and Debugging of Starvation Bugs in Multicore Software
- 2016
-
Ingår i: Proceedings of the 1st International Workshop on Specification, Comprehension, Testing, and Debugging of Concurrent Programs (SCTDCP 2016). - New York, NY, USA : ACM. - 9781450345101 ; , s. 7-11
-
Konferensbidrag (refereegranskat)abstract
- With the development of multicore hardware, concurrent, parallel and multicore software are becoming increasingly popular. Software companies are spending a huge amount of time and resources to nd and debug the bugs. Among all types of software bugs, concurrency bugs are also important and troublesome. This type of bugs is increasingly becoming an issue particularly due to the growing prevalence of multicore hardware. In this position paper, we propose a model for monitoring and debugging Starvation bugs as a type of concurrency bugs in multicore software. The model is composed into three phases: monitoring, detecting and debugging. The monitoring phase can support detecting phase by storing collected data from the system execution. The detecting phase can support debugging phase by comparing the stored data with starvation bug's properties, and the debugging phase can help in reproducing and removing the Starvation bug from multicore software. Our intention is that our model is the basis for developing tool(s) to enable solving Starvation bugs in software for multicore platforms.
|
|
| 34. |
|
|
| 35. |
- Abbaspour Asadollah, Sara, et al.
(författare)
-
A Runtime Verification Tool for Detecting Concurrency Bugs in FreeRTOS Embedded Software
- 2018
-
Ingår i: Proceedings - 17th International Symposium on Parallel and Distributed Computing, ISPDC 2018. - : Institute of Electrical and Electronics Engineers Inc.. - 9781538653302 ; , s. 172-179
-
Konferensbidrag (refereegranskat)abstract
- This article presents a runtime verification tool for embedded software executing under the open source real-time operating system FreeRTOS. The tool detects and diagnoses concurrency bugs such as deadlock, starvation, and suspension based-locking. The tool finds concurrency bugs at runtime without debugging and tracing the source code. The tool uses the Tracealyzer tool for logging relevant events. Analysing the logs, our tool can detect the concurrency bugs by applying algorithms for diagnosing each concurrency bug type individually. In this paper, we present the implementation of the tool, as well as its functional architecture, together with illustration of its use. The tool can be used during program testing to gain interesting information about embedded software executions. We present initial results of running the tool on some classical bug examples running on an AVR 32-bit board SAM4S.
|
|
| 36. |
- Abbaspour Asadollah, Sara, et al.
(författare)
-
A Study on Concurrency Bugs in an Open Source Software
- 2016
-
Ingår i: IFIP Advances in Information and Communication Technology, vol. 472. - Cham : Springer International Publishing. - 9783319392240 ; , s. 16-31
-
Konferensbidrag (refereegranskat)abstract
- 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 fixingtimes 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.
|
|
| 37. |
- Abbaspour Asadollah, Sara, et al.
(författare)
-
A Survey on Testing for Cyber Physical System
- 2015
-
Ingår i: Testing Software and Systems. - Cham : Springer International Publishing. - 9783319259444 ; , s. 194-207
-
Konferensbidrag (refereegranskat)abstract
- 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.
|
|
| 38. |
|
|
| 39. |
- Abbaspour Asadollah, Sara
(författare)
-
Concurrency Bugs : Characterization, Debugging and Runtime Verification
- 2018
-
Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Concurrent software has been increasingly adopted in recent years, mainly due to the introduction of multicore platforms. However, concurrency bugs are still difficult to test and debug due to their complex interactions involving multiple threads (or tasks). Typically, real world concurrent software has huge state spaces. Thus, testing techniques and handling of concurrency bugs need to focus on exposing the bugs in this large space. However, existing solutions typically do not provide debugging information to developers (and testers) for understanding the bugs.Our work focuses on improving concurrent software reliability via three contributions: 1) An investigation of concurrent software challenges with the aim to help developers (and testers) to better understand concurrency bugs. We propose a classification of concurrency bugs and discuss observable properties of each type of bug. In addition, we identify a number of gaps in the body of knowledge on concurrent software bugs and their debugging. 2) Exploring concurrency related bugs in real-world software with respect to the reproducibility of bugs, severity of their consequence and effort required to fix them. Our findings here is that concurrency bugs are different from other bugs in terms of their fixing time and severity, while they are similar in terms of reproducibility. 3) A model for monitoring concurrency bugs and the implementation and evaluation of a related runtime verification tool to detect the bugs. In general, runtime verification techniques are used to (a) dynamically verify that the observed behaviour matches specified properties and (b) explicitly recognize understandable behaviors in the considered software. Our implemented tool is used to detect concurrency bugs in embedded software and is in its current form tailored for the FreeRTOS operating system. It helps developers and testers to automatically identify concurrency bugs and subsequently helps to reduce their finding and fixing time.
|
|
| 40. |
- Abbaspour Asadollah, Sara, et al.
(författare)
-
Concurrency bugs in open source software : a case study
- 2017
-
Ingår i: Journal of Internet Services and Applications. - : Springer London. - 1867-4828 .- 1869-0238. ; 8:1
-
Tidskriftsartikel (refereegranskat)abstract
- 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.
|
|
