Escaping Method Prison – On the Road to Real Software Engineering
The way we develop software has changed dramatically over time. As an industry we have followed a zig-zag path moving from paradigm to paradigm and from method to method, changing very much like the fashion industry changes clothes. In this paper we will show that with every new method adoption, we walk into a method prison; a prison that is generally very expensive and demoralizing to escape. Like the fashion industry with the latest styles for the season, companies decide to chase the latest exciting method, only to end up in another method prison. And the cycle repeats.
We will discuss method prisons and what characterizes them. We will also show this has led to a method war. A war that has been going on for 50 years or more, and there is still no end in sight.
How foolish is this? How can we software development professionals continue letting this happen? Have we given up and can’t we see a way to put an end to this story? In this article we will show you a way to dramatically change how we deal with methods. A way, which shows the path to a more successful software world, a world based on sustainable change free of method prisons. A smarter way going forward.
- 0.Hastle S., Linders B., McIntosh S., Ferreira R.M., Smith C. “Opinion: What 2017 Has in Store for Culture & Methods”, https://www.infoq.com/news/2017/01/2017--culture-methods, InfoQ, 2017.
- 1.Jacobson I., Meyer B. Methods need theory. Dr. Dobb's Journal, 2009.Google Scholar
- 2.Jacobson I, Spence I. 2009. Why we need a theory for software engineering. Dr. Dobb's Journal, 2009.Google Scholar
- 3.Jacobson I., Meyer B., Soley R. 2009. Call for Action: The Semat Initiative. Dr. Dobb's Journal, 2009.Google Scholar
- 4.Ivar Jacobson, Bertrand Meyer, Richard Soley. “Software Engineering Method and Theory – a Vision Statement”, Feb 2010.Google Scholar
- 5.Object Management Group, “Essence - Kernel And Language For Software Engineering Methods”, November 2014. (http://www.omg.org/spec/Essence/).
- 6.Ivar Jacobson, Pan-Wei Ng, Paul E. McMahon, Ian Spence and Svante Lidman, “The Essence of Software Engineering: The SEMAT Kernel,” Communications of the ACM, Volume 55, Issue 12, December 2012.Google Scholar
- 7.Ivar Jacobson, Pan-Wei Ng, Paul E. McMahon, Ian Spence and Svante Lidman, “The Essence of Software Engineering: Applying the SEMAT Kernel”, Addison-Wesley, 2013Google Scholar
- 8.Ivar Jacobson, Ian Spence and Pan-Wei Ng. “Agile and SEMAT: Perfect Partners”, Communications of the ACM, Volume 11, Issue 9, Oct. 2013Google Scholar
- 9.Ivar Jacobson and Ed Seidewitz, “A New Software Engineering,” Communications of the ACM, Volume 57, Issue 12, Pages 49-54. December 2014.Google Scholar
- 10.Ivar Jacobson, Ian Spence, Ed Seidewitz. “Industrial-scale agile: from craft to engineering”, Communications of the ACM: Volume 59 Issue 12, December 2016.
<SimplePara><Emphasis Type="Bold">Open Access</Emphasis> This chapter is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made.</SimplePara> <SimplePara>The images or other third party material in this chapter are included in the chapter's Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the chapter's Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder.</SimplePara>