Advertisement

Trials and Tribulations of the Global Software Engineering Process: Evolving with Your Organisation

  • Oisín CawleyEmail author
Chapter

Abstract

This chapter will provide the reader with a firsthand account of the trials and tribulations of working in and managing a Global Software Engineering (GSE) function. By describing the move from a distributed collection of self-sufficient manufacturing plants with locally managed software engineering resources, to a GSE function as a shared service, the focus will be on how the management of that group had to fundamentally change in order to satisfy the complex projects and customer base which resulted. In parallel it will discuss the effect of regulation on the software engineering management process. Tracing the introduction of financial systems regulations, it will discuss the issues this brought to the GSE process and how they were successfully overcomed. These topics will be augmented by research that the author has carried out into regulated software development.

Keywords

Business Process Software Development Software Development Process Information Tech Global Software Development 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    107th Congress: Sarbanes-Oxley Act of 2002. Technical report. Enrolled Bill: H.R. 3763, Congress of the United State of America (2002)Google Scholar
  2. 2.
    Ågerfalk, P.J., Fitzgerald, B., Holmström, H., Lings, B., Lundell, B., Conchúir, E.Ó.: A framework for considering opportunities and threats in distributed software development. In: Proceedings of the International Workshop on Distributed Software Development, pp. 47–61. Austrian Computer Society (2005)Google Scholar
  3. 3.
    Bank for international settlements: Basel II: international convergence of capital measurement and capital standards: a revised framework. http://www.bis.org/publ/bcbs107.htm (2004)
  4. 4.
    BBC: enron scandal at a glance. http://news.bbc.co.uk/2/hi/business/1780075.stm (2002)
  5. 5.
    Borrás, C.: Overexposure of radiation therapy patients in panama: problem recognition and follow-up measures. Pan Am. J. Public Health 20(2–3), 173–187 (2006)Google Scholar
  6. 6.
    Campbell, M.: Regulations. IEEE Potentials 23(2), 14–15 (2004)CrossRefGoogle Scholar
  7. 7.
    Carmel, E.: Global Software Teams: Collaborating Across Borders and Time Zones. Prentice Hall, Upper Saddle River (1999)Google Scholar
  8. 8.
    Carmel, E., Sawyer, S.: Packaged software development teams: what makes them different? Inf. Technol. People 11(1), 7–19 (1998)CrossRefGoogle Scholar
  9. 9.
    Casey, V., Richardson, I.: Practical experience of virtual team software development. In: Proceedings of the EuroSPI 2004 Industrial Proceedings. Trondheim (2004). http://ulir.ul.ie/handle/10344/2149
  10. 10.
    Casey, V., Richardson, I.: Virtual teams: understanding the impact of fear. Softw. Process.: Improv. Pr. 13(6), 511–526 (2008)CrossRefGoogle Scholar
  11. 11.
    Cawley, O.: The application of a lean software development methodology within the regulated domain of medical device software. Ph.D. thesis, University of Limerick (Computer Science and Information Systems) (2013)Google Scholar
  12. 12.
    Cawley, O., Richardson, I.: Lessons in global software development – local to global transition within a regulated environment. In: European Systems and Software Process Improvement and Innovation (2010)Google Scholar
  13. 13.
    Cawley, O., Wang, X., Richardson, I.: Lean/agile software development methodologies in regulated environments - state of the art. In: Abrahamsson, P., Oza, N. (eds.) Lean Enterprise Software and Systems. Lecture Notes in Business Information Processing, vol. 65, pp. 31–36. Springer, Heidelberg (2010)Google Scholar
  14. 14.
    Cawley, O., Wang, X., Richardson, I.: Regulated software development - an onerous transformation. In: Weber, J., Perseil, I. (eds.) Foundations of Health Information Engineering and Systems. Lecture Notes in Computer Science, vol. 7789, pp. 72–86. Springer, Heidelberg (2013)Google Scholar
  15. 15.
    Cawley, O., Richardson, I., Wang, X., Kuhrmann, M.: A conceptual framework for lean regulated software development. In: Proceedings of the 2015 International Conference on Software and System Process, pp. 167–168. ACM, New York, USA (2015)Google Scholar
  16. 16.
    DeLone, W., Espinosa, J., Lee, G., Carmel, E.: Bridging global boundaries for is project success. In: Proceedings of the 38th Annual Hawaii International Conference on System Sciences, p. 48 ff. IEEE Computer Society, Washington, DC (2005)Google Scholar
  17. 17.
    Deshpande, S., Beecham, S., Richardson, I.: Global software development coordination strategies - a vendor perspective. In: Kotlarsky, J., Willcocks, L., Oshri, I. (eds.) New Studies in Global IT and Business Service Outsourcing. Lecture Notes in Business Information Processing, vol. 91, pp. 153–174. Springer, Heidelberg (2011)Google Scholar
  18. 18.
    Duranton, M., Black-Schaffer, D., De Bosschere, K., Maebe, J.: The hipeac vision for advanced computing in horizon 2020 (2013)Google Scholar
  19. 19.
    European Union: Medical Device Directive 2007/47/EC of the European Parliament and of the council. Official Journal of the European Union (2007)Google Scholar
  20. 20.
    FDA: General Principles of Software Validation; Final Guidance for Industry and FDA Staff. FDA Standard, U.S. Food and Drug Administration – Center for Devices and Radiological Health (2002)Google Scholar
  21. 21.
    FDA: Code of Federal Regulations 21 CFR Part 820 - Quality System Regulation. FDA Standard Part 820, U.S. Food and Drug Administration (2015)Google Scholar
  22. 22.
    Friedman, T.L.: The World Is Flat: A Brief History of the Twenty-First Century. Holtzbrinck Publishers (2005)Google Scholar
  23. 23.
    IEEE Reliability Society: Annual technical report 2008. Transactions on Reliability 57(3), 398–425 (2008)CrossRefGoogle Scholar
  24. 24.
    ISO: Medical devices – quality management systems – requirements for regulatory purposes. International Standard ISO 13485:2003, International Organisation for Standardisation (2003)Google Scholar
  25. 25.
    ISO/TC 210: Medical device software – software lifecycle processes. International Standard IEC 62304:2006, International Standards Organization (2006)Google Scholar
  26. 26.
  27. 27.
    Kettunen, P., Laanti, M.: How to steer an embedded software project: Tactics for selecting the software process model. Information and Software Technology 47(9), 587–608 (2005)CrossRefGoogle Scholar
  28. 28.
    Kotter, J.P.: Leading change: why transformation efforts fail. Harvard Business Review 73 (1995)Google Scholar
  29. 29.
    Lewis, M., Slack, N.: Operations Strategy. Prentice Hall, Upper Saddle River (2002)Google Scholar
  30. 30.
    Markides, C.C.: A dynamic view of strategy. Sloan Manag. Rev. 40(3), 55–63 (1999)Google Scholar
  31. 31.
    Richardson, I., Avram, G., Deshpande, S., Casey, V.: Having a foot on each shore - bridging global software development in the case of smes. In: Proceedings of the International Conference on Global Software Engineering, pp. 13–22. IEEE, Washington, DC (2008)Google Scholar
  32. 32.
    Richardson, I., Casey, V., Mccaffery, F., Burton, J., Beecham, S.: A process framework for global software engineering teams. Inf. Softw. Technol. 54(11), 1175–1191 (2012)CrossRefGoogle Scholar
  33. 33.
    The Free Dictionary: regulations. http://www.thefreedictionary.com/regulate (2015)

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  1. 1.Department of ComputingInstitute of Technology CarlowCarlowIreland

Personalised recommendations