Success factors influencing requirements change management process in global software development

Akbar, Muhammad Azeem; Sang, Jun; Nasrullah, .; Khan, Arif Ali; Mahmood, Sajjad; Qadri, Syed Furqan; Hu, Haibo; Xiang, Hong

doi:10.1016/j.cola.2018.12.005

Cited by 92 publications

(98 citation statements)

References 48 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The given analysis shows that the selected primary studies are sufficiently effective to address the objective of this study. Similar to existing studies, 40,41 we have considered a 50% QA score as the threshold value. The detailed results of the QA are presented in Appendix .…”

Section: Methodsmentioning

confidence: 99%

Readiness model for requirements change management in global software development

Akbar

Mahmood

Huang

et al. 2020

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

Requirements Change Management (RCM) is one of the challenges faced by Global Software Development (GSD) organisations as requirements evolution is inevitable due to dynamic business and operating environments. GSD organisations face issues when dealing with RCM because many organisations embark on GSD without understanding their readiness to undertake such an initiative. Currently, there is no readiness model to assess the RCM process in the context of GSD. The objective of this study is to develop a requirements change management readiness model (RCMRM) for GSD organisations. A Systematic Mapping Study (SMS) was conducted to identify the primary studies related to RCM in the GSD projects. By using SMS, 109 primary studies were selected and 73 RCM practices were identified which were used to design the readiness levels of the proposed RCMRM. To validate the RCMRM, initially, two case studies were conducted in two GSD organisations. Based on the suggestions and recommendations of the case study participants,the RCMRM was further modified. The updated version of RCMRM was further validated by two different GSD organisations. The results of the second case study indicate that RCMRM is effective in assessing the readiness of the RCM process in the context of GSD. K E Y W O R D S global software development, readiness model, requirements change management, requirements engineering, systematic mapping study 1 | INTRODUCTION Requirements change management (RCM) is an important and complex phase of the software development life cycle (SDLC). 1,2 For example, Nurmuliani et al. 3 stated that a change in requirements may occur due to an increase in stakeholder understanding and change in the organizational work environment. The factors causing the change in requirements include a change in customer needs, a change in market demand, global market compaction, and a change in government rules and policies. 1 RCM during SDLC is not merely significant, it is critical to ensure the production of quality software. 1,2 Communication and collaboration play a major role in the overall success of RCM. 4 According to Khan et al. 5 requirements collection and management demand rich communication between the client and the development team. Due to the role of communication and collaboration in the requirements process, RCM is considered challenging in the context of a collocated (single site) software development environment, and it becomes more complicated when adopting global software development (GSD). 2-4 Recently, several software organizations have transited their businesses from collocated to geographically distributed development environments. 1,6 A survey study conducted by the Standish Group indicated that 20% of client software organizations are outsourcing their development activities to vendor countries. 7 Šmite et al. 8 argue that the GSD environment assists software firms to develop quality software at a

show abstract

Section: Methodsmentioning

confidence: 99%

Readiness model for requirements change management in global software development

Akbar

Mahmood

Huang

et al. 2020

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

show abstract

“…This approach will assist to collect responses from industrial practitioners working to secure DevOps activities. The questionnaire approach provides the best opportunity to collect practitioner's opinion from large population [31][32][33][34][35].…”

Section: B Empirical Studymentioning

confidence: 99%

“…Based on their recommendations, we rearrange the position of some factors, the final mapping is presented in Table 3. We have followed a formal mapping approach to categories the challenges, applied in other research studies as well [31][32][33]44]. To avoid uncertainty and vagueness during prioritization we have been introducing a PROMETHEE II approach.…”

Section: Application Of Promethee II Approachmentioning

confidence: 99%

“…To reduce this threat, we have developed the search strings to collect data from targeted digital libraries and performed QA steps to verify the quality of research material. The same approach has been adopted by other existing literature review studies [31,33,42]. An internal threat to validity is that there might be researcher's biases while finding literature.…”

Section: Threats To Validitymentioning

confidence: 99%

See 1 more Smart Citation

Prioritization Based Taxonomy of DevOps Security Challenges Using PROMETHEE

Rafi

Akbar

et al. 2020

IEEE Access

Self Cite

View full text Add to dashboard Cite

DevOps is a combination of collaborative and multidisciplinary efforts of an organization to control continuous delivery and updates of new software while guaranteeing their reliability and correctness. In the software industry, the implementation of DevOps (development and operations units) faces many challenges that are specifically associated with the security. This study aims to develop a prioritization based taxonomy of DevOps security challenges using PROMETHEE-II approach. The total of eighteen DevOps security challenges were extracted from the literature and were further evaluated with experts using questionnaire survey study. In the third stage, multi criteria decision making PROMETHEE-II approach was used to prioritize and develop the taxonomy of identified factors and their categories. The implications of PROMETHEE-II approach are novel in this research domain as it has been used successfully in various other domains e.g. medical, banking, internet techniques and management etc. The contribution of this study is not limited to develop the taxonomy based structure of DevOps security challenges, but also the proper prioritization of these challenges by introducing PROMETHEE-II approach in the research field of DevOps. The study results will assist the practitioners to remove the uncertainty and vagueness in the opinion of DevOps experts to secure DevOps implementation for better and continuous software development process.

show abstract

“…In addition, we have map the investigated factors by following the framework developed by Akbar et al [33,35]. This mapping process is conducted based on the frequency analysis.…”

Section: A Organization Size Based Analysismentioning

confidence: 99%

An empirical Study Investigation of Task Allocation Process Barriers in the Context of Offshore Software Development Outsourcing: An Organization Size Based Analysis

al.¹

2019

IJCDS

View full text Add to dashboard Cite

Planning and managing the task allocation process in offshore software development outsourcing environment plays an important role in order to develop the good quality software with in time and budget. In this study we investigate the berries that negatively affect the task allocation process in geographically distributed development environment. A literature review and questionnaire survey approach was adopted in order to investigate the barriers of task allocation process. The investigated barriers were further classified into four core categories i.e. team, coordination, project administration and technology. A total of 14 barriers were identified from the literature and validated with organizational experts by using questionnaire survey. The findings revolved that all the survey respondents are agree with the findings of literature review. We further analyze the investigated barriers based on organizations size, to check the significant difference between the barriers with respect to organization size (small, medium and large). Moreover the categorization of the investigated barriers indicate that the project administration is the most significant category of investigated barriers of task allocation process. The findings of this study may helpful for researcher and practitioners to consider the most significant barriers of task allocation process in the context of offshore software development outsourcing environment.

show abstract

Success factors influencing requirements change management process in global software development

Cited by 92 publications

References 48 publications

Readiness model for requirements change management in global software development

Readiness model for requirements change management in global software development

Prioritization Based Taxonomy of DevOps Security Challenges Using PROMETHEE

An empirical Study Investigation of Task Allocation Process Barriers in the Context of Offshore Software Development Outsourcing: An Organization Size Based Analysis

Contact Info

Product

Resources

About