Offshore Challenges Affecting Design Phase

As mentioned in an earlier post that there are four key challenges in offshore software development such as:

• Trust
• Socio-cultural
• Communication and Coordination
• Knowledge Transfer

In the presentation below we have shown how these challenges effect the design phase of software development.

Reference: 

Bosch, J., and Bosch-Sijtsema, P. (2010). From integration to composition: On the impact of software product lines, global development and ecosystems. J. Syst. Softw. 83, 1 (January 2010), 67-76

Cataldo, M., Bass, M., Herbsleb, J.D., Bass, L. (2007). On Coordination Mechanisms in Global Software Development. In Proceedings of the International Conference on Global Software Engineering (ICGSE '07). IEEE Computer Society, Washington, DC, USA, 71-80.

  

Clerc, V. (2008). Towards architectural knowledge management practices for global software development. In Proceedings of the 3rd international workshop on Sharing and reusing architectural knowledge (SHARK '08). ACM, New York, NY, USA, 23-28. 

Herbsleb, James D., Audris Mockus, Thomas A. Finholt, and Rebecca E. Grinter (2001). "An empirical study of global software development: distance and speed." In Proceedings of the 23rd international conference on software engineering, pp. 81-90. IEEE Computer Society, 2001.

Jaakkola, H., Heimbürger, A., and Linna, P. (2010). Knowledge-oriented software engineering process in a multi-cultural context. Software Quality Control 18, 2 (June, 2010). 299-319.

Kausar, Maryam and Adil Al-Yasiri (2015).“Distributed Agile Patterns for Offshore Software Development” 12th International Joint Conference onComputer Science and Software Engineering (JCSSE), IEEE 2015 

Ovaska, P., Rossi, M. and Marttiin, P. (2003). Architecture as a coordination tool in multi-site software development. Softw. Process: Improve. Pract. 8(2003) 233–247.

Sengupta, B., Chandra, S., and Sinha, V. (2006). A research agenda for distributed software development. In Proceedings of the 28th international conference on Software engineering (2006). ACM, New York, NY, USA, 731-740. DOI=http://doi.acm.org/10.1145/1134285.1134402. 

Research Methodology

Research methodology can be defined as something people undertake in order to find out things in a systematic way thereby increasing their knowledge (Saunders et al., 2007).  There are many ways in which research methods can be explained. 

The research onion was developed by Saunders et al. (2007) to illustrate the stages that must be covered when undertaking research. Each outer layer in the research onion describes a more detailed stage of research process and contains different ways in which a layer of research can be conducted. This approach provides an effective progression through which a research methodology can be designed and its usefulness lies in the fact that it can adapt to almost any type of research methodology and can be used in a wide range of contexts (Bryman, 2012).

The presentation below shows each stage of the research onion: 

Reference:

Bryman, Alan (2012). Social research methods (5th ed.). Oxford: Oxford University Press.

Flick,Uwe. (2011). Introducing research methodology: A beginner's guide to doing a research project. London: Sage.

Goddard, W. & Melville, S. (2004). Research Methodology: An Introduction, (2nd ed.) Oxford: Blackwell Publishing.

Hussey, Jill, and Roger Husse (1997)y. "Business research." Hampshire: Palgrave(1997).

May, Tim (2011). Social research. McGraw-Hill Education (UK), 2011.

Saunders, M., P Lewis (2007)- Research methods for business students, 2007

Yin, R. K. (2003) Case Study Research Design and Methods, Thousand Oaks, 3^rdEdition, Sage Publications, Inc. 

Offshore Challenges Affecting Requirement Phase

There are four key challenges in offshore software development such as:

• Trust
• Socio-cultural
• Communication and Coordination
• Knowledge Transfer

In the presentation below we have shown how these challenges effect the requirement phase of software development.

References:

Alnuem, Mohammed Abdullah, Arshad Ahmad, and Hashim Khan (2012). "Requirements Understanding: A Challenge in Global Software Development, Industrial Surveys in Kingdom of Saudi Arabia." In 2012 IEEE 36th Annual Computer Software and Applications Conference, pp. 297-306. IEEE, 2012).

Berenbach, B. (2006). Impact of organizational structure on distributed requirements engineering processes: lessons learned. In Proceedings of the 2006 international workshop on Global software development for the practitioner (GSD '06). ACM, New York, NY, USA, 15-19. 

Bhat, J.M., Gupta, M., Murthy, S.N. (2006). Overcoming Requirements Engineering Challenges: Lessons from Offshore Outsourcing. IEEE Softw. 23, 5 (September 2006), 38-44. 

Bird, C., Nagappan, N., Devanbu, P., Gall, H., and Murphy, B. (2009). Does distributed development affect software quality? An empirical case study of Windows Vista. In Proceedings of the 31st International Conference on Software Engineering (ICSE '09). IEEE Computer Society, Washington, DC, USA, 518-528. 

Damian, Daniela E., and Didar Zowghi (2003). "RE challenges in multi-site software development organisations." Requirements engineering8, no. 3 (2003): 149-160.

Herbsleb, James D., Audris Mockus, Thomas A. Finholt, and Rebecca E. Grinter (2001). "An empirical study of global software development: distance and speed." In Proceedings of the 23rd international conference on software engineering, pp. 81-90. IEEE Computer Society, 2001.

Niazi, M., El-Attar, M., Usma, M., and Ikram, N. (2012). GlobReq: A framework for improving requirements engineering in global software development projects: Preliminary results. In proceedings of the 16th International Conference on Evaluation & Assessment in Software Engineering (EASE 2012). (May 14-15, 2012) 166-170.

Sengupta, B., Chandra, S., and Sinha, V. (2006). A research agenda for distributed software development. In Proceedings of the 28th international conference on Software engineering (2006). ACM, New York, NY, USA, 731-740. DOI=http://doi.acm.org/10.1145/1134285.1134402.