An Evidence-based Roadmap for IoT Software Systems Engineering

Context: The Internet of Things (IoT) has brought expectations for software inclusion in everyday objects. However, it has challenges and requires multidisciplinary technical knowledge involving different areas that should be combined to enable IoT software systems engineering. Goal: To present an evidence-based roadmap for IoT development to support developers in specifying, designing, and implementing IoT systems. Method: An iterative approach based on experimental studies to acquire evidence to define the IoT Roadmap. Next, the Systems Engineering Body of Knowledge life cycle was used to organize the roadmap and set temporal dimensions for IoT software systems engineering. Results: The studies revealed seven IoT Facets influencing IoT development. The IoT Roadmap comprises 117 items organized into 29 categories representing different concerns for each Facet. In addition, an experimental study was conducted observing a real case of a healthcare IoT project, indicating the roadmap applicability. Conclusions: The IoT Roadmap can be a feasible instrument to assist IoT software systems engineering because it can (a) support researchers and practitioners in understanding and characterizing the IoT and (b) provide a checklist to identify the applicable recommendations for engineering IoT software systems

Guidelines for conducting interactive rapid reviews in software engineering -- from a focus on technology transfer to knowledge exchange

Evidence-based software engineering (EBSE) aims to improve research utilization in practice. It relies on systematic methods (like systematic literature reviews, systematic mapping studies, and rapid reviews) to identify, appraise, and synthesize existing research findings to answer questions of interest. However, the lack of practitioners' involvement in the design, execution, and reporting of these methods indicates a lack of appreciation for knowledge exchange between researchers and practitioners. Within EBSE, the main reason for conducting these systematic studies is to answer the practitioner's questions and impact practice. However, in many cases, academics have undertaken these studies without any direct involvement of practitioners.This report focuses on the rapid review guidelines and presents practical advice on conducting these with practitioner involvement to facilitate knowledge co-creation.Based on a literature review of rapid reviews and stakeholders engagement in medicine and our experience of using secondary studies in software engineering, we propose extensions to an existing proposal for rapid reviews in software engineering to increase researchers-practitioners knowledge exchange. We refer to the extended method as an interactive rapid review.An interactive rapid review is a streamlined approach to conduct agile literature reviews in close collaboration between researchers and practitioners in software engineering. This report describes the process and discusses possible usage scenarios and some reflections from the proposal's ongoing evaluation.The proposed guidelines will potentially boost knowledge co-creation through active researcher-practitioner interaction by streamlining practitioners' involvement and recognizing the need for an agile process

Industry-academia collaborations in software testing: experience and success stories from Canada and Turkey : Special Issue Industry Academia Collaborations in Software Testing

Collaboration between industry and academia supports improvement and innovation in industry and helps to ensure industrial relevance in academic research. However, many researchers and practitioners believe that the level of joint industry–academia collaborations (IAC) in software engineering (SE) is still relatively very low, compared to the amount of activity in each of the two communities. The goal of the empirical study reported in this paper is to characterize a set of collaborative industry–academia R&D projects in the area of software testing conducted by the authors (based in Canada and Turkey) with respect to a set of challenges, patterns and anti-patterns identified by a recent Systematic Literature Review study, with the aim of contributing to the body of evidence in the area of IAC, for the benefit of SE researchers and practitioners in conducting successful IAC projects in software testing and in software engineering in general. To address the above goal, a pool of ten IAC projects (six completed, two failed and two ongoing) all in the area of software testing, which the authors have led or have had active roles in, were selected as objects of study and were analyzed (both quantitatively and qualitatively) with respect to the set of selected challenges, patterns and anti-patterns. As outputs, the study presents a set of empirical findings and evidence-based recommendations, e.g.: it has been observed that even if an IAC project may seem perfect from many aspects, one single major challenge (e.g., disagreement in confidentiality agreements) can lead to its failure. Thus, we recommend that both parties (academics and practitioners) consider all the challenges early on and proactively work together to eliminate the risk of challenges in IAC projects. We furthermore report correlation and interrelationship of challenges, patterns and anti-patterns with project success measures. This study hopes to encourage and benefit other SE researchers and practitioners in conducting successful IAC projects in software testing and in software engineering in general in the future

A survey on quality attributes in servicebased systems

Service-based systems have become popular in the software industry. In software engineering, it is widely acknowledged that requirements on quality attributes (e.g., performance, security, reliability) significantly impact the design of software systems. This study explores the role of quality attributes during the design of service-based systems. We investigate the significance of quality attributes when designing service-based systems and how quality attributes are addressed through design decisions, across application domains, and related to other aspects of software development, e.g., architecture documentation. We conducted a descriptive survey. The survey was done as an online questionnaire targeting practitioners. Furthermore, we included researchers with practical design experience. We obtained 56 valid responses. Most survey participants consider quality attributes and functionality as equally important and treat quality attributes explicitly rather than implicitly. Furthermore, dependability is the most relevant quality attribute in service-based systems; we do not find quality attributes that are particularly important in specific application domains. Most quality attributes are addressed by ad hoc decisions, rather than established architecture or design patterns or technologies. Only few decision alternatives are considered when making architectural decisions to address quality attributes. Our results partially confirm anecdotal evidence from current literature, but also strengthen previous claims by providing empirical evidence. Our results point to future research directions (e.g., exploring the impact of decision types on how well quality attributes can be achieved) and implications for practitioners (e.g., training makes a difference to how quality attributes are treated).Peer ReviewedPostprint (author’s final draft

Needs and challenges for a platform to support large-scale requirements engineering: a multiple-case study

Background: Requirement engineering is often considered a critical activity in system development projects. The increasing complexity of software as well as number and heterogeneity of stakeholders motivate the development of methods and tools for improving large-scale requirement engineering. Aims: The empirical study presented in this paper aim to identify and understand the characteristics and challenges of a platform, as desired by experts, to support requirement engineering for individual stakeholders, based on the current pain-points of their organizations when dealing with a large number requirements. Method: We conducted a multiple case study with three companies in different domains. We collected data through ten semi-structured interviews with experts from these companies. Results: The main pain-point for stakeholders is handling the vast amount of data from different sources. The foreseen platform should leverage such data to manage changes in requirements according to customers' and users' preferences. It should also offer stakeholders an estimation of how long a requirements engineering task will take to complete, along with an easier requirements dependency identification and requirements reuse strategy. Conclusions: The findings provide empirical evidence about how practitioners wish to improve their requirement engineering processes and tools. The insights are a starting point for in-depth investigations into the problems and solutions presented. Practitioners can use the results to improve existing or design new practices and toolsPeer ReviewedPostprint (published version

Evidence-Based Information Systems: A New Perspective and a Road Map for Research-Informed Practice

Despite the increasing sophistication and quality of published work, the development of a cumulative body of knowledge and an evidence-base for information systems (IS) research still represents a major challenge. IS research is still predominantly undertaken by IS researchers for other IS researchers and not utilized to its full extent by IS practitioners or policy-makers. We focus on this problem and express the need for a new evidence-based research perspective. It is argued that it is time to refocus the efforts of IS academics (and practitioners) to develop a new evidence-base for IS research whereby it can more routinely inform, develop, improve and support IS practice. We contribute to this debate by defining evidence-based practice (EBP), its relevance to IS, and the need to develop an evidence-based approach. We look in particular at its brief history, and its subsequent evolution, development and widespread acceptance in Medicine; making reference to recent arguments and critiques of EBP in other disciplines such as software engineering and management. We espouse the need to develop a similar evidence-based movement and infrastructure within the IS research and practitioner communities and then put forward a possible road map for the development of Evidence-Based Information Systems (EBIS) that comprises 9 key initiatives. We conclude our argument by stating that the current extent, severity and impact of IS failures are unacceptable, emphasizing the need for a new perspective for IS research that encourages and incorporates EBP as a guiding principle to inform better IS practice

Evidence in Requirements Engineering: A Systematic Literature Review Protocol

Requirements Engineering (RE) is recognized as one of the critical phases in software development. RE has its own journals and conferences where lots of work has been published. As the area is maturing, increasingly large numbers of empirically supported studies have been reported in RE. There is a need to synthesize evidence based RE literature. We plan to systematically investigate evidence based RE studies to see and report state of the art in evidence based RE reported research. This paper aims at providing a systematic literature review (SLR) protocol to describe a process for synthesizing the empirically supported work in the area of RE that will eventually present a state of the art of the field. This SLR intends to not only summarize the empirical data regarding RE but will also be helpful for various practitioners in this field to find out areas of RE rich in terms of tools, techniques, frameworks, models and guidelines to aid in their work. It will also facilitate RE researchers to identify knowledge gaps to recognize needs and chances for future research directions in this field