Software process models: a review and analysis

  • Abstract
  • Keywords
  • References
  • PDF
  • Abstract

    Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.

  • Keywords

    Software Process; Software Development Life Cycle; Traditional Models; Agile Models; Process Metrics; Model Evaluation.

  • References

      [1] W. W. Royce, “Managing the development of large software systems,” in Proceedings of IEEE WESCOM. IEEE Computer Society Press, 1970, pp. 328–338.

      [2] B. Boehm, “A spiral model of software development and enhancement,”IEEE Computer, vol. 21, no. 5, pp. 61–72, 1988.

      [3] K. Forsberg and H. Mooz, “The relationship of system engineering to the project cycle,” in Proceedings of the First Annual Symposium of National Council on System Engineering, Chattanooga, TN, USA, 1991, pp. 57–65.

      [4] P. Herzlich, “The politics of testing,” in Proceedings of 1st EuroSTAR conference, London, UK, 1993, pp. 47–50.

      [5] Agile Alliance, “Manifesto for agile software development,”, 2001.

      [6] K. Beck and C. Andres, Extreme Programming Explained: Embrace Change. Addison-Wesley, 2004.

      [7] K. Schwaber, “Scrum development process,” in Proceedings of OOPSLA’95 Workshop on Business Object Design and Implementation, 1995.

      [8] P. Deemer, G. Benefield, C. Larman, and B. Vodde, “A lightweight guide to the theory and practice of Scrum (version 2),” http://www., 2012.

      [9] M. Poppendieck and T. Poppendieck, Lean Software Development: An Agile Toolkit. Boston, MA, USA: Addison-Wesley, 2003.

      [10] D. J. Anderson and A. Carmichael, Essential Kanban Condensed. LeanKanban University Press, 2016.

      [11] F. Wagner, R. Schmuki, T. Wagner, and P. Wolstenholme, Modeling Software with Finite State Machines: A Practical Approach. CRC Press, 2006.

      [12] D. Andriani, “Analysis of software development processes,”, 2012.

      [13] B. Boehm, J. A. Lane, S. Koolmanojwong, and R. Turner, The incremental commitment spiral model: principles and practices for successful systems and software. Addison-Wesley, 2014.

      [14] Federal Highway Administration, “Systems engineering for intelligent transportation systems,” seitsguide/section6.htm.

      [15] A. Spillner, “The W-MODEL – strengthening the bond between development and test,” in Proceedings of International Conference on Software Testing, Analysis and Review, 2002.

      [16] K.-K. Lau, F. M. Taweel, and C. M. Tran, “The W model for component-based software development,” in Proceedings of 37th EUROMICRO Conference on Software Engineering and Advanced Applications, 2011, pp. 47–50.

      [17] J. Highsmith, “History: The Agile Manifesto,” http://agilemanifesto. Org/history.html, 2001.

      [18] M. S. Palmquist, M. A. Lapham, S. Miller, T. Chick, and I. Ozkaya, “Parallel worlds: Agile and waterfall differences and similarities,” Software Engineering Institute, Carnegie Mellon University, Tech. Rep. CMU/SEI-2013-TN-021, October 2013.

      [19] MIT Media, “Software development life cycle (Lecture 6 GSL Peru 2014),” materials/t04- software development life cycle.pdf, 2014.

      [20] XP Org, “Extreme programming: A gentle introduction,” http://www.

      [21] D. Rosenberg and M. Stephens, Extreme Programming Refactored: The Case against XP. Berkeley, CA: Apress, 2003.

      [22] H. Takeuchi and I. Nonaka, “The new new product development game,” Harvard Business Review, vol. January-February, pp. 137–148, 1986. [23] K. Schwaber and J. Sutherland, “The Scrum guide,” 2017-Scrum-Guide-US.pdf#zoom=100, 2017.

      [23] P. Middleton, “Lean software development: Two case studies,”Software Quality Journal, vol. 9, pp. 241–252, 2001.

      [24] J. Pernsta˚l, R. Feldt, and T. Gorschek, “The lean gap: A review of lean approaches to large-scale software systems development,” Journal of Systems and Software, vol. 86, no. 11, pp. 2797–2821, 2013.

      [25] E. Kupiainen, M. Ma¨ntyla¨, and J. Itkonen, “Using metrics in agile and lean software development – A systematic literature review of industrial studies,” Information & Software Technology, vol. 62, pp. 143–163, 2015.

      [26] [27] J. S. Cardoso, J. Mendling, G. Neumann, and H. A. Reijers, “Adiscourse on complexity of process models,” in Proceedings of Business Process Management 2006 Workshops. Vienna, Austria: Springer-Verlag, 2006, pp. 115–126.

      [27] Standish, “Standish group 2015 chaos report,” articles/standish-chaos-2015, 2015.

      [28] Safari Books Online, “Case study: The FBI’s Sentinel project,” 106b6df7-7b31-425e-a539-e02c3ec13fb4&cid=shareLink.

      [29] P. Elwer, “Agile project development at Intel: A scrum odyssey,” Intel, Tech. Rep., 2008, studies/Intel case study.pdf.

      [30] G. Benefield, “Rolling out agile in a large enterprise,” Yahoo, Tech. Rep., 2014, studies/Intel case study.pdf.

      [31] M. Striebeck, “Ssh! we are adding a process...” in Proceedings of AGILE 2006 Conference. Minneapolis, MN, USA: IEEE Computer Society Press, 2006, pp. 185–193.

      [32] P. Middleton and D. Joyce, “Lean software management: BBC Worldwide case study,” IEEE Transactions on Engineering Management, vol. 59, no. 1, pp. 20–32, 2012.

      [33] TechBeacon, “Survey: Is agile the new norm?” https://techbeacon. com/survey-agile-new-norm, 2015.

      [34] VersionOne, “State of agile report,” state-of-agile.

      [35] M. McMurtrey, “A case study of the application of the systems development life cycle (SDLC) in 21st century health care: Something old, something new?” Journal of the Southern Association for Information Systems, vol. 1, no. 1, pp. 14–25, 2013.




Article ID: 14537
DOI: 10.14419/ijet.v7i2.28.14537

Copyright © 2012-2015 Science Publishing Corporation Inc. All rights reserved.