Modeling of Product Software Businesses: Investigation into Industry Product and Channel Typologies
The product software industry lacks a method for describing their products and business models on a high abstraction level. The lack of good methods to model a software product makes it harder to evaluate a business model especially for people with less knowledge of software architectures and more knowledge about the business side of creating software. This chapter presents a model consisting of two diagrams the product context diagram (PCD), which describes the context in which a software product operates and the software supply network (SSN) diagram, which describes the different parties involved in the delivery and deployment of a software product or service. Furthermore, this chapter presents a typology for both diagrams. The proposed diagrams are simple and easy to create therefore providing a quick insight to the core of a business model, creating the diagrams supports the process of evaluating the business model.
KeywordsBusiness Model Software Industry Software Company Product Software Connector Line
The authors thank the companies that participated in this research. Without their help this research would not have been possible. We also thank the students of the Informatics Business course at the Utrecht University. The students provided us with cases and valuable feedback. Furthermore, we thank the students of the Junior College Utrecht for their research into the gaming industry in the Netherlands.
- Booch, G., Rumbaugh, J., Jacobson, I. (1999). The unified modeling language user guide. Redwood City, CA: Addison Wesley Longman Publishing Co., Inc.Google Scholar
- Cusumano, M.A. (2004) The Business of Software. Free Press.Google Scholar
- Farbey, B. and Finkelstein, A. (2001) “Software Acquisition: a business strategy analysis” Proc. Requirements Engineering (RE01).Google Scholar
- Jansen, S., Brinkkemper, S., Finkelstein A. (2007). Providing transparency in the business of software: a modeling technique for software supply networks. Submitted for publication Google Scholar
- Jansen, S. and Rijsemus, W. (2005). Balancing Total Cost of Ownership and Cost of Maintenance Within a Software Supply Network, International Conference on Software Maintenance 2005, industry trackGoogle Scholar
- OECD (2000). The software sector: Growth, structure and policy issues. OECD Report DSTI/ICCP/IE(2000)8/REV2.Google Scholar
- OECD (2001). Highlights of the OECD information technology outlook 2002. OECD Report.Google Scholar
- Osterwalder, A., Pigneur, Y., Tucci, C.L. (2005). Clarifying Business Models: Origins, Present, and Future of the Concept. Communications of AIS, Volume 15, Article 40Google Scholar
- Scheer, A. (2000), ARIS – Business Process Modeling, 3rd ed. Berlin: Springer.Google Scholar
- Soy, S.K. (1997). The Case Study as a Research Method published online athttp://fiat.gslis.utexas.edu/~ssoy/usesusers/l391d1b.htm, retrieved at 6th of March, 2007.
- Vaishnavi, V. and Kuechler, W. (2004/2006). “Design Research in Information Systems” February 20, 2004, last updated January 18, 2005. URL:http://www.isworld.org/Researchdesign/drisISworld.htm
- Weill, P. and Vitale, M.R. (2001). Place to space: Migrating to eBusiness Models, Harvard Business School Press, Boston.Google Scholar
- Xu, L. and Brinkkemper, S. (2005). Concepts of Product Software: Paving the Road for Urgently Needed Research, In: Proceedings of 1st International Workshop on Philosophical Foundations of Information Systems Engineering (PHISE'05). Orlando Belo, Johann Eder, Oscar Pastor and Joao Falcao eCunha (Eds.), FEUP edicoes, Porto, 2005.Google Scholar
- Yin, R.K. (2003) Case study research – design and methods, 3rd ed. SAGE Publications .Google Scholar