Productization and Product Structure: Extending The Perspective to Software Business



Volume 7, Issue 2
Akwasi Gyamerah Adusei, MJanne Härkönen, Erno Mustonen

Published online: 30 April 2021
Article Views: 35
 
AbstractReferencesCite

Productization and product structure can be beneficial for companies in various product-related considerations. The focus on software business and software products, however, has been deficient. This study takes a specific software perspective to provide a software business perspective to productization discussion. Productization of software is considered by bringing different perspectives on the software product. Constructive, qualitative approach is used in studying the productization and software product structure of a case company. The empirical study reveals softwarerelated challenges and shows how productization and product structure are beneficial also with software business, including the Software as a Service (SaaS) business model. The results indicate that further focus on product structure and consistent productization logic is also necessary for software business. The basic principles of productization of physical products or services may remain the same, but some software business specifics must be addressed. Hence, software context may influence productization and product structure logic. Companies involved in the software business can benefit from the improved understanding in managing their software offerings. Well productized software offering enables maintaining the scope of the software being developed and the operations of what is being sold, delivered, and invoiced. This study is among the first to consider the productization concept, including product structure in the software business context to indicate the context specifics.

  1. Alajoutsijärvi, K., Mannermaa, K., & Tikkanen, H. (2000). Customer relationships and the small software firm: A framework for understanding challenges faced in marketing. Information & Management, 37(3), 153–159. doi:https://doi.org/10.1016/S0378-7206(99)00039-7
  2. Aldrich, J., Chambers, C., & Notkin, D. (2002). Archjava: Connecting software architecture to implementation. In Proceedings of the 24th International Conference on Software Engineering, Orlando, FL (pp. 187–197). doi:https://doi.org/10.1109/ICSE.2002.1007967
  3. Alves, C., Pereira, S., & Castro, J. (2006). A study in market-driven requirements engineering. Retrieved from https://bit.ly/3h5tCcZ
  4. Alves, V., Niu, N., Alves, C., & Valença, G. (2010). Requirements engineering for software product lines: A systematic literature review. Information and Software Technology, 52(8), 806–820. doi:https://doi.org/10.1016/j.infsof.2010.03.014
  5. Artz, P., Van De Weerd, I., & Brinkkemper, S. (2010). Productization: The process of transforming from customerspecific software development to product software development (Tech. Rep.). Department of Information and Computing Sciences, Utrecht University, Utrecht, The Netherlands.
  6. Asagba, P. O., & Ogheneovo, E. E. (2008). A comparative analysis of structured and object-oriented programming methods. Journal of Applied Sciences and Environmental Management, 12(4), 41-46. doi:https://doi.org/10.4314/jasem.v12i4.55217
  7. Asikainen, T., Soininen, T., & Männistö, T. (2003). A koala-based approach for modelling and deploying configurable software product families. In International Workshop on Software Product-Family Engineering, Springer, Berlin, Heidelberg (pp. 225–249). doi:https://doi.org/10.1007/978-3-540-24667-1_17
  8. Barney, S., Aurum, A., & Wohlin, C. (2008). A product management challenge: Creating software product value through requirements selection. Journal of Systems Architecture, 54(6), 576–593. doi:https://doi.org/10.1016/j.sysarc.2007.12.004
  9. Bhardwaj, S., Jain, L., & Jain, S. (2010). An approach for investigating perspective of cloud Software-as-a-Service (SaaS). International Journal of Computer Applications, 10(2), 40–43. doi:https://doi.org/10.5120/1450-1962
  10. Biernacki, P., & Waldorf, D. (1981). Snowball sampling: Problems and techniques of chain referral sampling. Sociological Methods & Research, 10(2), 141–163. doi:https://doi.org/10.1177/004912418101000205
  11. Choudhary, V. (2007). Software as a service: Implications for investment in software development. In 40th Annual Hawaii International Conference on System Sciences (HICSS’07), Waikoloa, HI (pp. 209a–209a).doi:https://doi.org/10.1109/HICSS.2007.493
  12. Cockburn, A. (2004). Crystal clear: A human-powered methodology for small teams. London, UK: Pearson Education.
  13. Cooper, R., Edgett, S., & Kleinschmidt, E. (2001). Portfolio management for new product development: Results of an industry practices study. r&D Management, 31(4), 361–380. doi:https://doi.org/10.1111/1467-9310.00225
  14. Crnkovic, I., Asklund, U., & Dahlqvist, A. P. (2003). Implementing and integrating product data management and software configuration management. Boston, MA: Artech House.
  15. Cusumano, M. A. (2008). The changing software business: Moving from products to services. Computer, 41(1), 20–27. doi:https://doi.org/10.1109/MC.2008.29
  16. Cusumano, M. A. (2019). ’platformizing’a bad business does not make it a good business. Communications of the ACM, 63(1), 23–25. doi:https://doi.org/10.1145/3372918
  17. Dang, S., Amin, O., Shihada, B., & Alouini, M.-S. (2020). What should 6g be? Nature Electronics, 3(1), 20–29. doi:https://doi.org/10.1038/s41928-019-0355-6
  18. Dubey, A., & Wagle, D. (2007). Delivering software as a service. The McKinsey Quarterly, 6, 1-12.
  19. ElMaraghy, H., Schuh, G., ElMaraghy, W., Piller, F., Schönsleben, P., Tseng, M., & Bernard, A. (2013). Product variety management. Cirp Annals, 62(2), 629–652. doi:https://doi.org/10.1016/j.cirp.2013.05.007
  20. Feller, J., Finnegan, P., Fitzgerald, B., & Hayes, J. (2008). From peer production to productization: A study of socially enabled business exchanges in open source service networks. Information Systems Research, 19(4), 475–493. doi:https://doi.org/10.1287/isre.1080.0207
  21. Flamholtz, E. (1995). Managing organizational transitions: Implications for corporate and human resource management.
  22. European Management Journal, 13(1), 39–51. doi:https://doi.org/10.1016/0263-2373(94)00056-D
  23. Fricker, S., & Kittlaus, H.-B. (2017). Software product management: The ispma-compliant study guide and handbook. Berlin, Heidelberg: Springer-Verlag.
  24. Fricker, S. A. (2012). Software product management. In Software for people (p. 53-81). Berlin, Heidelberg: Springer.
  25. Gbadegeshin, S. A. (2019). The effect of digitalization on the commercialization process of high-technology companies in the life sciences industry. Technology Innovation Management Review, 9(1), 49-63. doi:https://doi.org/10.22215/timreview/1211
  26. Gharbi, M., Koschel, A., & Rausch, A. (2019). Software architecture fundamentals: A study guide for the certified professional for software architecture R –foundation level–isaqb compliant. Heidelberg, Germany: Dpunkt. verlag.
  27. Godse, M., & Mulik, S. (2009). An approach for selecting Software-as-a-Service (SaaS) product. In IEEE International Conference on Cloud Computing, Bangalore, India (pp. 155–158). doi:https://doi.org/10.1109/CLOUD.2009.74
  28. Haines, S. (2014). Product manager’s desk reference. New York, NY: McGraw-Hill Education.
  29. Hanna, K.-V., Harri, H., Olli, J., & Kongkiti, P. (2011). Product configuration management in ict companies: The practitioners’ perspective. Technology and Investment, 2, 273-285. doi:https://doi.org/10.4236/ti.2011.24028
  30. Hannila, H., Tolonen, A., Harkonen, J., & Haapasalo, H. (2019). Product and supply chain related data, processes and information systems for product portfolio management. International Journal of Product Lifecycle Management, 12(1), 1–19. doi:https://doi.org/10.1504/IJPLM.2019.104352
  31. Harkonen, J., Haapasalo, H., & Hanninen, K. (2015). Productisation: A review and research agenda. International Journal of Production Economics, 164, 65–82. doi:https://doi.org/10.1016/j.ijpe.2015.02.024
  32. Harkonen, J., Mustonen, E., & Hannila, H. (2019). Productization and product structure as the backbone for product data and fact-based analysis of company products. In IEEE International Conference on Industrial Engineering and Engineering Management (IEEM), Macao, China (pp. 474–478). doi:https://doi.org/10.1109/IEEM44572.2019.8978845
  33. Harkonen, J., Tolonen, A., & Haapasalo, H. (2017). Service productisation: Systematising and defining an offering. Journal of Service Management, 28(5), 936-971. doi:https://doi.org/10.1108/JOSM-09-2016-0263
  34. Harkonen, J., Tolonen, A., & Haapasalo, H. (2018a). Modelling of manufacturing services and processes for effective productization. In 20th International Working Seminar on Production Economics, Innsbruck, Austria (p. 19-23).
  35. Harkonen, J., Tolonen, A., & Haapasalo, H. (2018b). Modelling of construction products and services for effective productisation. Management (18544223), 13(4), 335-353.
  36. Helferich, A., Schmid, K., & Herzwurm, G. (2006). Product management for software product lines: An unsolved problem? Communications of the ACM, 49(12), 66–67. doi:https://doi.org/10.1145/1183236.1183268
  37. Hietala, J., Kontio, J., Jokinen, J.-P., & Pyysiainen, J. (2004). Challenges of software product companies: Results of a national survey in Finland. In 10th International Symposium on Software Metrics, Chicago, IL (pp. 232–243). doi:https://doi.org/10.1109/METRIC.2004.1357906
  38. Hinings, B., Gegenhuber, T., & Greenwood, R. (2018). Digital innovation and transformation: An institutional perspective. Information and Organization, 28(1), 52–61. doi:https://doi.org/10.1016/j.infoandorg.2018.02.004
  39. Jaakkola, E. (2011). Unraveling the practices of “productization” in professional service firms. Scandinavian Journal of Management, 27(2), 221–230. doi:https://doi.org/10.1016/j.scaman.2011.03.001
  40. Jayasimha, K., Nargundkar, R. V., et al. (2020). Impact of Software as a Service (SaaS) on software acquisition process. Journal of Business & Industrial Marketing, 35(4), 757-770. doi:https://doi.org/10.1108/JBIM-12-2018-0382
  41. Kahn, K. B. (2012). The PDMA handbook of new product development. New York, NY: John Wiley & Sons.
  42. Kasanen, E., Lukka, K., & Siitonen, A. (1993). The constructive approach in management accounting research. Journal of Management Accounting Research, 5(1), 243–264.Kästner, C., Apel, S., & Ostermann, K. (2011). The road to feature modularity? In Proceedings of the 15th International Software Product Line Conference, New York, NY (pp. 1–8). doi:https://doi.org/10.1145/2019136.2019142
  43. Kim, K., Kim, H., & Kim, W. (2007). Building software product line from the legacy systems” experience in the digital audio and video domain”. In 11th International Software Product Line Conference (SPLC 2007), Kyoto, Japan (pp. 171–180). doi:https://doi.org/10.1109/SPLINE.2007.27
  44. Kotler, P., & Keller, K. (2012). Marketing management. New Jersey, NJ: Prentice Hall.
  45. Kropsu-Vehkaperä, H. (2012). Enhancing understanding of company-wide product data management in ICT companies (Vol. 418). Finland: Acta Universitatis Ouluensis, C Technica.
  46. Kumar, G., & Bhatia, P. K. (2012). Impact of agile methodology on software development process. International Journal of Computer Technology and Electronics Engineering (IJCTEE), 2(4), 46–50.
  47. Kuula, S., Haapasalo, H., & Tolonen, A. (2018). Cost-efficient co-creation of knowledge intensive business services. Service Business, 12(4), 779–808. doi:https://doi.org/10.1007/s11628-018-0380-y
  48. Lahtinen, N., Mustonen, E., & Harkonen, J. (2019). Commercial and technical productization for fact-based product portfolio management over lifecycle (just accepted). IEEE Transactions on Engineering Management, 1-13. doi:https://doi.org/10.1109/TEM.2019.2932974
  49. Light, B., & Papazafeiropoulou, A. (2004). Reasons behind ERP package adoption: A diffusion of innovations perspective. In 12th European Conference on Information Systems, Turku, Finland.
  50. Mathur, S. K. (2006). Indian information technology industry: Past, present and future and a tool for national development. Journal of Theoretical and Applied Information Technology, 2(2), 50–79.
  51. McKay, A., Erens, F., & Bloor, M. S. (1996). Relating product definition and product variety. Research in Engineering Design, 8(2), 63–80. doi:https://doi.org/10.1007/BF01607862
  52. MCSI, M. (2009). Configurability in SaaS (Software as a Service) applications. In Proceedings of 2nd Annual Conference on India Software Engineering Conference, New York, NY (p. 19-26). doi:https://doi.org/10.1145/1506216.1506221
  53. Merton, R., Fiske, M., & Kendall, P. (1990). The focused interview: A manual of problems and procedures. New York, NY: The Free Press.
  54. Meyer, M. H., & Webb, P. H. (2005). Modular, layered architecture: The necessary foundation for effective mass customisation in software. International Journal of Mass Customisation, 1(1), 14–36. doi:https://doi.org/10.1504/IJMASSC.2005.007349
  55. Mustonen, E., Harkonen, J., & Haapasalo, H. (2019). From product to service business: Productization of productoriented, use-oriented, and result-oriented business. In IEEE International Conference on Industrial Engineering and Engineering Management (IEEM), Macao, China (pp. 985–989). doi:https://doi.org/10.1109/IEEM44572.2019.8978581
  56. Ostermann, K., Giarrusso, P. G., Kästner, C., & Rendel, T. (2011). Revisiting information hiding: Reflections on classical and nonclassical modularity. In European conference on object-oriented programming, Springer, Berlin, Heidelberg (pp. 155–178). doi:https://doi.org/10.1007/978-3-642-22655-7_8
  57. Pandla, K. (2016). Drivers and characteristics of high performing organizations. International Journal of Business and Administrative Studies, 2(3), 57–61. doi:https://doi.org/https://10.20469/ijbas.2.10001-3
  58. Parry, S., Jones, R., Rowley, J., & Kupiec-Teahan, B. (2012). Marketing for survival: A comparative case study of SME software firms. Journal of Small Business and Enterprise Development, 19(4), 712-728. doi:https://doi.org/10.1108/14626001211277488
  59. Peltonen, H. (2000). Concepts and an implementation for product data management. Espoo, Finland: Finnish Academy of Technology.
  60. Pyron, C., Prado, J., & Golab, J. (1998). Test strategy for the PowerPC 750 microprocessor. IEEE Design & Test of Computers, 15(3), 90–97. doi:https://doi.org/10.1109/54.706039
  61. Ratnayake, R. C., & Markeset, T. (2010). Implementing company policies in plant level asset operations: Measuring organisational alignment. European Journal of Industrial Engineering, 4(3), 355–371. doi:https://doi.org/10.1504/EJIE.2010.033335
  62. Rautiainen, K., Vuornos, L., & Lassenius, C. (2003). An experience in combining flexibility and control in a small company’s software product development process. In International Symposium on Empirical Software Engineering, Rome, Italy (pp. 28–37). doi:https://doi.org/10.1504/10.1109/ISESE.2003.1237962
  63. Saaksvuori, A., & Immonen, A. (2008). Product lifecycle management. Berlin, Germany: Springer Science & Business Media.
  64. Sabin, D., & Weigel, R. (1998). Product configuration frameworks-a survey. IEEE Intelligent Systems and their applications, 13(4), 42–49. doi:https://doi.org/10.1504/10.1109/5254.708432
  65. Sakti, I. W. (2016). The analysis factors of experential marketing, product quality, and customer satisfaction of motor bike as a main transportation mode in Bandung-Indonesia. International Journal of Business and Administrative Studies, 2(1), 6–8.
  66. Salvador, F., Forza, C., & Rungtusanatham, M. (2002). Modularity, product variety, production volume, and component sourcing: Theorizing beyond generic prescriptions. Journal of operations management, 20(5), 549–575. doi:https://doi.org/10.1016/S0272-6963(02)00027-X
  67. Saunders, M., Lewis, P., & Thornhill, A. (2007). Research methods for business students. Hoboken, NJ: Prentice Hall.
  68. Sawyer, S. (2000). Packaged software: Implications of the differences from custom approaches to software development.
  69. European Journal of Information Systems, 9(1), 47–58. doi:https://doi.org/10.1057/palgrave.ejis.3000345
  70. Schwaber, K., & Beedle, M. (2002). Agile software development with scrum. Upper Saddle River, NJ: Prentice Hall.
  71. Solms, F. (2012). What is software architecture? In Proceedings of the South African Institute for Computer Scientists and Information Technologists Conference, New York, NY (p. 363-373). doi:https://doi.org/10.1145/ 2389836.2389879
  72. Srinivasan, S. R., Ramakrishnan, S., & Grasman, S. E. (2005). Identifying the effects of cannibalization on the product portfolio. Marketing Intelligence & Planning, 23(4), 359-371. doi:https://doi.org/10.1108/02634500510603465
  73. Stark, J. (2016). Product lifecycle management. In Product lifecycle management. Cham, Switzerland: Springer.
  74. Subair, S. (2014). The evolution of software process models: From the waterfall model to the Unified Modelling Language (UML). International Journal of Information & Technology Systems, 3(2), 7–14.
  75. Sudarsan, R., Fenves, S. J., Sriram, R. D., & Wang, F. (2005). A product information modeling framework for product lifecycle management. Computer-Aided Design, 37(13), 1399–1411. doi:https://doi.org/10.1016/j.cad.2005.02.010
  76. Suominen, A., Kantola, J., & Tuominen, A. (2009). Reviewing and defining productization. In 20th Annual Conference of the International Society for Professional Innovation Management (ISPIM 2009), Vienna, Austria.
  77. Svensson, D., & Malmqvist, J. (2002). Strategies for product structure management at manufacturing firms. Journal of Computing and Information Science in Engineering, 2(1), 50–58. doi:https://doi.org/https://10.1115/1.1471356
  78. Tolonen, A., Harkonen, J., Haapasalo, H., et al. (2014). Product portfolio management—governance for commercial and technical portfolios over life cycle. Technology and investment, 5(04), 173-183. doi:https://doi.org/10.4236/ti.2014.54016
  79. Tolonen, A., Harkonen, J., Verkasalo, M., & Haapasalo, H. (2015a). Product portfolio management process over horizontal and vertical portfolios. International Journal of Product Lifecycle Management, 8(3), 189–215. doi:https://doi.org/10.1504/IJPLM.2015.074132
  80. Ulrich, K., & S.D., E. (2012). Product design and development. New York, NY: McGraw-Hill.
  81. Vlaanderen, K., Brinkkemper, S., & van de Weerd, I. (2012). On the design of a knowledge management system for incremental process improvement for software product management. International Journal of Information System Modeling and Design (IJISMD), 3(4), 46–66. doi:https://doi.org/10.4018/jismd.2012100103
  82. Wallin, C., Ekdahl, F., & Larsson, S. (2002). Integrating business and software development models. IEEE Software, 19(6), 28–33. doi:https://doi.org/10.1109/MS.2002.1049384
  83. Wu, L., Garg, S. K., & Buyya, R. (2011). SLA-based resource allocation for Software as a Service provider (SaaS) in cloud computing environments. In 11th IEEE/ACM International Symposium on Cluster, Cloud and Grid Computing, Newport Beach, CA (pp. 195–204). doi:https://doi.org/10.1109/CCGrid.2011.51
  84. Xu, L., & Brinkkemper, S. (2007). Concepts of product software. European Journal of Information Systems, 16(5), 531–541. doi:https://doi.org/10.1057/palgrave.ejis.3000703
  85. Youngdahl, W. E., Ramaswamy, K., & Dash, K. C. (2010). Service offshoring: The evolution of offshore operations. International Journal of Operations & Production Management, 30(8), 798-820. doi:https://doi.org/10.1108/01443571011068171
  86.  Zhang, H., & Jarzabek, S. (2004). XVCL: A mechanism for handling variants in software product lines. Science of Computer Programming, 53(3), 381–407. doi:https://doi.org/10.1016/j.scico.2003.04.007
  87. Zhang, S., Shen, W., & Ghenniwa, H. (2004). A review of internet-based product information sharing and visualization. Computers in Industry, 54(1), 1–15. doi:https://doi.org/10.1016/j.compind.2003.09.002

Adusei, A. G., Härkönen, J., & Mustonen, E. (2021). Productization and product structure: Extending the perspective to software business. International Journal of Business and Administrative Studies, 7(2), 89 106. doi: https://dx.doi.org/10.20469/ijbas.7.10004-2