Development and Operations (DevOps) is a methodology that aims to establish collaboration between programmers and operators to automate the continuous delivery of new software to reduce the development life cycle and produce quality software. Development, Security, and Operations (DevSecOps) is developing the DevOps concept, which integrates security methods into a DevOps process. DevSecOps is a software development process where security is built in to ensure application confidentiality, integrity, and availability. This paper aims to identify and prioritize the challenges associated with implementing the DevSecOps process. We performed a multivocal literature review (MLR) and conducted a questionnaire-based survey to identify challenges associated with DevSecOps-based projects. Moreover, interpretive structure modeling (ISM) was applied to study the relationships among the core categories of the challenges. Finally, we used the fuzzy technique for order preference by similarity to an ideal solution (TOPSIS) to prioritize the identified challenges associated with DevSecOps projects. We identified 18 challenges for the DevSecOps process and mapped them to 10 core categories. The ISM results indicate that the “standards” category has the most decisive influence on the other nine core categories of the identified challenges. Moreover, the fuzzy TOPSIS indicates that “lack of secure coding standards,” “lack of automated testing tools for security in DevOps,” and “ignorance in static testing for security due to lack of knowledge” are the highest priority challenges for the DevSecOps paradigm. Organizations using DevOps should consider the identified challenges in developing secure software.

Abstract Healthcare systems face various issues related to complex networks of intermediaries and a lack of transaction traceability. The most critical issues are the fragmentation of healthcare data, obstacles in providing efficient research and services, lack of clinical trial reporting, high cost and mismanagement of the drug supply chain, patient data security, and fake drugs. Blockchain technology has the potential to address these criticalities as it has in build traceability mechanisms and promises new business models by enabling incentive structures. This potential of blockchain gathers a high interest in the health industry. However, the implementation of blockchain in healthcare faces various issues as well. Currently, there are no practice‐oriented maturity models to improve such an implementation. In this paper, we present a roadmap to develop a maturity model for blockchain in healthcare (MMBH) based on critical barriers (CBs), critical success factors (CSFs), and the best practices for blockchain implementation in healthcare systems. As a first step to develop the MMBH, in this paper, we present the initial results of a systematic literature review (SLR) to identify critical success factors for implementing blockchain in healthcare systems. We also applied fuzzy technique order preference by similarity to ideal solution (TOPSIS) to prioritize the identified CSFs.

Abstract Testing is a complex phase in DevOps process due to need of an automated process that provides feedback at different strategies of continuous development and operations pipeline. Software organization face several challenges during the testing phase due to lack of understanding on testing best practices for the DevOps paradigm. The objective of this study is to prioritize DevOps best testing practices, which can facilitate the selection of testing practices during DevOps process. To perform this research, we have extended the work done by Hornbeek, using the 15 DevOps testing practices discussed in his study. First, we categorize the test practices against culture, automation, lean, measurement, and sharing (CALMS) pillars of DevOps adoption principles. Next, a questionnaire‐based survey was conducted to collect feedback from industry practitioners on the DevOps test practices and their categorization against CALMS criteria. Finally, we applied Interpretive Structure Modeling (ISM) to find the interrelationship between CALMS criteria, and fuzzy TOPSIS was used to prioritize the DevOps test practices that will assist practitioners to better manage the testing activities during DevOps process.

Abstract Software industry is adopting global software development (GSD) due to its potential to produce quality products at a lower cost. However, the GSD firms face many challenges that make development activities more complicated, especially related to the requirements engineering (RE) process. The objectives of this article are to investigate and prioritize the barriers faced by the GSD organizations during the RE process. First, we identified 17 barriers related to the RE process in the GSD projects. Next, the identified barriers were further validated with real‐world GSD practitioners using a questionnaire survey. Finally, we applied the analytical hierarchy process to prioritize the investigated barriers with respect to their significance for the RE process in the GSD domain. The results show that coordination is the most significant barrier category for the RE process in GSD projects. Lack of standard and procedure for RE in GSD, lack of synchronized communication infrastructure, and lack of mutual understanding between the overseas RE teams are also high‐ranked barriers for the RE process in GSD. The authors believe that the findings of this study will assist practitioners and researchers in developing effective strategies and plans for the successful implementation of the RE process in the GSD context.

Abstract Managing the cloud‐based software development outsourcing (CSDO) activities across the geographically distributed development sites are much challenging. This study aims to identify the success factors (SFs) for CSDO and prioritize them based on their significance. To achieve this objective, we conducted a systematic literature review (SLR) and survey study with industrial and academic experts. Finally, we applied the analytical hierarchy process (AHP) to develop the framework based on the prioritization of the identified SFs. We believe that the findings of this study will assist the industry practitioners and researchers in developing effective strategies for the successful implementation of CSDO activities.

Abstract Planning and managing of requirement change management (RCM) process in global software development (GSD) are a complicated task, but the RCM plays a significant role in developing the quality software within time and budget. The key aim of this study is to prioritize the factors that could positively influence the RCM program in GSD context. To achieve the study objective, the questionnaire survey study was conducted to get the feedback of the practitioners concerning the success factors of RCM in GSD context. Moreover, the fuzzy analytical hierarchy process (FAHP) was applied. The application of FAHP is novel in this research domain as it has been effectively applied previously in various other research areas, for example, supplier selection, electronics and electrical, personnel selection, and agile software development. The results of this study will provide the prioritization‐based taxonomy of RCM success factors and also contribute by introducing the novel FAHP approach in the research domain of RCM in GSD. The FAHP approach assists the practitioners to reduce the uncertainty and vague opinions of RCM experts.

Abstract DevOps is a new software engineering paradigm adopted by various software organizations to develop the quality software within time and budget. The implementation of DevOps practices is critical, and there are no guidelines to assess and improve the DevOps activities in software organizations. Hence, there is a need to develop a readiness model for DevOps (RMDevOps) with an aim to assist the practitioners for implementation of DevOps practices in software firms. To achieve the study objective, we conducted a systematic literature review (SLR) study to identify the critical challenges and associated best practices of DevOps. A total of 18 challenges and 73 best practices were identified from the 69 primary studies. The identified challenges and best practices were further evaluated by conducting a survey with industry practitioners. The RMDevOps was developed based on other well‐established models in software engineering domain, for example, software process improvement readiness model (SPIRM) and software outsourcing vendor readiness model (SOVRM). Finally, case studies were conducted with three different organizations with an aim to validate the developed model. The results show that the RMDevOps is effective to assess and improve the DevOps practices in software organizations.

The economic and strategic gain attracts the software industry to adopt the global software development (GSD) phenomenon. Besides the significant advantages, the GSD firms also face certain critical challenges mainly related to security and management perspective. Blockchain is the new revolutionary technology that offers over the globe secure storage via distributed databases. The objective of this study is to investigate how the adoption of blockchain is beneficial for the GSD project. We have conducted interviews with academic researchers and case studies with industry practitioners to identify the impact of blockchain on GSD projects. We have identified ten key critical areas of GSD the effectively addressed by using the blockchain technology in GSD context. A comparative analysis is conducted with the finding of academic researcher and industry practitioners, and the results ((W=0.86, p=0.005) shows that there is a strong agreement between the understanding of academic researchers and industry practitioners. Besides, we have developed a hypothetical model based on the findings of both studies that shows the positive relationship of blockchain implementation in the GSD domain. We believe that the findings of this study will encourage the practitioners and researchers to develop the new plan and strategies for the adoption of blockchain in GSD.

Offshore software development outsourcing (OSDO) is one of the popular development paradigms in the software industry. There are a number of challenges associated with OSDO including the challenges related to requirements engineering (RE) process. The objective of this study is to identify success factors (SFs) associated with RE processes in the OSDO context. A total of 25 SFs were identified using systematic literature review (SLR) and the identified SFs were further validated with practitioners using a questionnaire-based survey. The authors also examined the identified RE challenges with respect to their relevance for different organisation types (client and vendor) and sizes (small, medium, and large) with an aim to provide a clear understanding of the RE process and its SFs in the context of various OSDO organisations. They also conducted a comparative analysis between the SLR and questionnaire findings and the results indicate that there is a moderately positive correlation between the data sets. They believe that the findings of this study will provide a comprehensive model to help OSDO organisations assess and improve the effectiveness and efficiency of their RE activities.

Abstract Software development is a complex task, and the introduction of multi‐site development teams spread across the globe makes it even harder. Requirement changes during the software development process are inevitable, and failing to manage evolving requirements is one of the contributors to project failures. Requirements change management (RCM) becomes difficult in global software development (GSD) projects due to the need to communicate and coordinate between stakeholders in a distributed environment. This research work aims to identify the factors that have positive impacts on RCM activities in GSD. We conducted a multi‐vocal literature review (MLR) and a questionnaire survey study to identify the RCM success factors. The results of the t‐test (ie, t = 0.0347 and P = .700 > .05) and correlation (rs (25) = 0.573, P = .003) indicates that there is no significant difference between the findings of MLR and the questionnaire survey. The identified factors were further analyzed in the context of client and vendor organizations to better understand the RCM success factors in both types of GSD firms. The findings of this study can provide a useful framework for tackling problems associated with RCM in a GSD environment that is significant to the progression of GSD firms.

Recent advances in cooperative multiple-input-multiple-output (CMIMO) techniques have encouraged interest in the development of intelligent transportation systems (ITS). They have the potential for use in the infrastructure to vehicle (I2V) and infrastructure to infrastructure (I2I) communications in ITS networks where the energy consumption of wireless sensor nodes embedded on the road infrastructure is constraint. Therefore, how to reduce the energy consumption becomes a hot research topic . In this paper, applications of cooperative communications in ITS networks are proposed for reducing the total energy consumption . At first, the ITS model is established based on the cooperative multiple-input-multiple-output spatial modulation (CMIMO-SM). A detailed energy consumption analysis of the proposed scheme compared with the traditional single-input-single-output (SISO) based scheme is then presented. The comparison conducted between these communication schemes helps us select the optimal one for energy reduction in energy constrained ITS networks. Additionally, under the guidance of the proposed scheme we consider the multi-hop transmission scenario where the energy efficiency improvement is achieved by finding the optimal hop number with the equal hop-length scheme. As a result, we analyze the energy consumption in different situations, and discuss the requirements on the hop-length and hop number in ITS networks. It shows that the optimal results are dependent on the ITS scenarios and choosing the appropriate transmission scheme will provide a good energy consumption performance in ITS.