skip to main content
10.1145/2593882.2593883acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
Article

Software process

Published:31 May 2014Publication History

ABSTRACT

This paper is a travelogue of Software Process research and practice in the past 15 years. It is based on the paper written by one of the authors for the FOSE Track at ICSE 2000. Since then, the landscape of Software Process research has significantly evolved: technological breakthroughs and market disruptions have defined new and complex challenges for Software Engineering researchers and practitioners.

In this paper we provide an overview of the current status of research and practice, highlight new challenges, and provide a non-exhaustive list of research issues that, in our view, need to be tackled by future research work.

References

  1. G. Allmendinger and R. Lombreglia. Four strategies for the age of smart services. Hardward Business Review, pages 131–145, October 2005.Google ScholarGoogle Scholar
  2. V. Ambriola, R. Conradi, and A. Fuggetta. Assessing process-centered software engineering environments. ACM Trans. Softw. Eng. Methodol., 6(3):283–328, July 1997. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. R. Balzer. Tolerating inconsistency. In L. Belady, D. R. Barstow, and K. Torii, editors, ICSE, pages 158–165. IEEE Computer Society / ACM Press, 1991. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. K. Blincoe, G. Valetto, and D. Damian. Do all task dependencies require coordination? the role of task properties in identifying critical coordination needs in software projects. In Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering, ESEC/FSE 2013, pages 213–223, New York, NY, USA, 2013. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. K. Blincoe, G. Valetto, and S. Goggins. Proximity: A measure to quantify the need for developers’ coordination. In Proceedings of the ACM 2012 Conference on Computer Supported Cooperative Work, CSCW ’12, pages 1351–1360, New York, NY, USA, 2012. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. L. Briand, D. Falessi, S. Nejati, M. Sabetzadeh, and T. Yue. Research-based innovation: A tale of three projects in model-driven engineering. In Model Driven Engineering Languages and Systems - 15th International Conference, MODELS 2012, Innsbruck, Austria, September 30 - October 5, 2012. Proceedings, volume 7590 of Lecture Notes in Computer Science, pages 793–809. Springer Berlin Heidelberg, 2012. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. G. Canfora, L. Cerulo, M. Cimitile, and M. Di Penta. How changes affect software entropy: an empirical study. Empirical Software Engineering, pages 1–38, 2012. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. M. Cataldo, J. D. Herbsleb, and K. M. Carley. Socio-technical congruence: A framework for assessing the impact of technical and work dependencies on software development productivity. In Proceedings of the Second ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM ’08, pages 2–11, New York, NY, USA, 2008. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. D. Chappel. What is Application Lifecyle Management? Technical report, David Chappel & Associates, http://www.davidchappell.com/whatisalm–– chappell.pdf, 2008.Google ScholarGoogle Scholar
  10. V. Clerc. Do architectural knowledge product measures make a difference in gsd? In ICGSE, pages 382–387. IEEE, 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. M. Cristal, D. Wildt, and R. Prikladnicki. Usage of scrum practices within a global company. In Global Software Engineering, 2008. ICGSE 2008. IEEE International Conference on, pages 222–226, 2008. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. G. Cugola and C. Ghezzi. Software processes: a retrospective and a path to the future. In Software Process Improvement and Practice, pages 101–123, 1998.Google ScholarGoogle ScholarCross RefCross Ref
  13. G. Cugola, E. D. Nitto, A. Fuggetta, and C. Ghezzi. A framework for formalizing inconsistencies and deviations in human-centered systems. ACM Trans. Softw. Eng. Methodol., 5(3):191–230, 1996. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. P. Debois. Devops: A software revolution in the making? The Journal of Information Technology Management, 24(8):3–5, August 2001.Google ScholarGoogle Scholar
  15. P. Deemer, G. Benefield, C. Larman, and B. Vodde. A lightweight guide to the theory and practice of scrum (version 2.0). Technical report, http://www.scrumprimer.org, 2012.Google ScholarGoogle Scholar
  16. E. Di Nitto and D. Rosenblum. Exploiting adls to specify architectural styles induced by middleware infrastructures. In Proceedings of the 21st International Conference on Software Engineering, ICSE ’99, pages 13–22, New York, NY, USA, 1999. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. M. Fowler. Continous integration. http://martinfowler.com/articles/continuousIntegration.html, 2006.Google ScholarGoogle Scholar
  18. A. Fuggetta. Software process: A roadmap. In Proceedings of the Conference on The Future of Software Engineering, ICSE ’00, pages 25–34, New York, NY, USA, 2000. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  19. J. D. Herbsleb. Global software engineering: The future of socio-technical coordination. In L. C. Briand and A. L. Wolf, editors, FOSE, pages 188–198, 2007. Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. J. Humble and J. Molesky. Why enterprises must adopt devops to enable continous delivery. The Journal of Information Technology Management, 24(8):6–12, August 2001.Google ScholarGoogle Scholar
  21. F. Lanubile, C. Ebert, R. Prikladnicki, and A. Vizcaino. Collaboration tools for global software engineering. Software, IEEE, 27(2):52–55, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  22. K. Manikas and K. M. Hansen. Software ecosystems - a systematic literature review. J. Syst. Softw., 86(5):1294–1306, May 2013. Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. J. Mukerji and J. Miller. MDA Guide Version 1.0.1. omg/2003-06-01, June 2003.Google ScholarGoogle Scholar
  24. L. Osterweil. Software processes are software too. In Proceedings of the 9th International Conference on Software Engineering, ICSE ’87, pages 2–13, Los Alamitos, CA, USA, 1987. IEEE Computer Society Press. Google ScholarGoogle ScholarDigital LibraryDigital Library
  25. R. K. Panesar-Walawege, M. Sabetzadeh, and L. C. Briand. Supporting the verification of compliance to safety standards via model-driven engineering: Approach, tool-support and empirical validation. Information & Software Technology, 55(5):836––864, 2013. Google ScholarGoogle ScholarDigital LibraryDigital Library
  26. J. F. Smart. Jenkins The Definitive Guide. O’Reilly, 2011. Google ScholarGoogle ScholarDigital LibraryDigital Library
  27. M.-A. Storey, L. Singer, B. Cleary, F. Figueira Filho, and A. Zagalsky. The (r)evolution of social media in software engineering. In Proceedings of the 36th International Conference on Software Engineering, Future on Software Engineering Track, 2014. Google ScholarGoogle ScholarDigital LibraryDigital Library
  28. M. Striebeck. Ssh! we are adding a process... In Proceedings of the Conference on AGILE 2006, AGILE ’06, pages 185–193, Washington, DC, USA, 2006. IEEE Computer Society. Google ScholarGoogle ScholarDigital LibraryDigital Library
  29. J. Sutherland, C. Jakobsen, and K. Johnson. Scrum and cmmi level 5: The magic potion for code warriors. In Agile Conference (AGILE), 2007, pages 272–278, 2007. Google ScholarGoogle ScholarDigital LibraryDigital Library
  30. D. A. Tamburri. Supporting Networked Software Development. PhD thesis, Vrije University Amsterdam, 2014.Google ScholarGoogle ScholarDigital LibraryDigital Library
  31. D. A. Tamburri, R. De Boer, E. Di Nitto, P. Lago, and H. v. Vliet. Dynamic networked organizations for software engineering. In Proceedings of the 2013 International Workshop on Social Software Engineering, SSE 2013, pages 5–12, New York, NY, USA, 2013. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  32. D. Tamburrri, P. Lago, and H. Van Vliet. Organizational social structures for software engineering. ACM Computing Suveys, 46(1), 2014. Google ScholarGoogle ScholarDigital LibraryDigital Library
  33. E. Trist and K. Bamforth. Some social and psychological consequences of the longwall method of coal getting. Human Relations, 4:3–38, 1951.Google ScholarGoogle ScholarCross RefCross Ref
  34. L. G. Votta and A. Porter. Experimental software engineering: A report on the state of the art. In Proceedings of the 17th International Conference on Software Engineering, ICSE ’95, pages 277–279, New York, NY, USA, 1995. ACM. Google ScholarGoogle ScholarDigital LibraryDigital Library
  35. J. Whittle, J. Hutchinson, M. Rouncefield, H. Burden, and R. Heldal. Industrial adoption of model-driven engineering: Are the tools really the problem? In Model-Driven Engineering Languages and Systems - 16th International Conference, MODELS 2013, Miami, FL, USA, September 29 - October 4, 2013. Proceedings, volume 8107 of Lecture Notes in Computer Science, pages 1–17. Springer Berlin Heidelberg, 2013.Google ScholarGoogle Scholar
  36. C. Wohlin, M. Höst, and K. Henningsson. Empirical research methods in software engineering. In R. Conradi and A. I. Wang, editors, ESERNET, volume 2765 of Lecture Notes in Computer Science, pages 7–23. Springer, 2003.Google ScholarGoogle Scholar
  37. W. Wu, W.-T. Tsai, and W. Li. An evaluation framework for software crowdsourcing. Frontiers of Computer Science, 7(5):694–709, 2013. Google ScholarGoogle ScholarDigital LibraryDigital Library
  38. L. Yilmaz. Modelling software processes as human-centered adaptive work systems. In P. Abrahamsson, N. Baddoo, T. Margaria, and R. Messnarz, editors, Software Process Improvement, volume 4764 of Lecture Notes in Computer Science, pages 148–159. Springer Berlin Heidelberg, 2007. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Software process
          Index terms have been assigned to the content through auto-classification.

          Recommendations

          Comments

          Login options

          Check if you have access through your login credentials or your institution to get full access on this article.

          Sign in

          PDF Format

          View or Download as a PDF file.

          PDF

          eReader

          View online with eReader.

          eReader