Weitere Kapitel dieses Buchs durch Wischen aufrufen
Partner networks have proven successful in delivering comprehensive customer offerings. Market leaders of various domains, from industry to online services, leverage the innovative strength and resource capacities of their partners to complement and extend existing offerings or to define completely new offerings. Examples such as Amazon’s sales platform or Google’s Android network are just prominent representatives of a rich universe of digital cooperation strategies. Software ecosystems have emerged as a digital cooperation strategy in partner networks. They leverage a common technological base to coordinate the contributions of multiple software and service providers to a shared market. The technological base may consist of an execution platform such as Android, an open solution framework such as Eclipse, or just a set of standards such as DICOM or PROFINET. For a software ecosystem to flourish, the interests of all members have to be considered and balanced and the common technological base needs appropriate architectural design and engineering practices. Based on an industry-grade system as a running example, we describe an integrated approach that uses ecosystem modeling for both aligning the interests of ecosystem members and for architectural design.
Bitte loggen Sie sich ein, um Zugang zu diesem Inhalt zu erhalten
Sie möchten Zugang zu diesem Inhalt erhalten? Dann informieren Sie sich jetzt über unsere Produkte:
Boehm, B. W. (1991). Software risk management: principles and practices. Software, IEEE, 8(1).
Bosch, J. (2009). From software product lines to software ecosystems. 13th Int. Software Product Line Conf. (SPLC ’09). Pittsburgh, USA.
Gordijn, J., & Akkermans, H. (2001). E3-value: Design and evaluation of e-business models. IEEE Intelligent Systems, 16(4).
Handoyo, E., et al. (2013). Software ecosystems modeling: The value chains. Conference on Management of Emergent Digital Ecosystems (MEDES ’13), New York, USA.
Hedman, J., & Kalling, T. (2003). The business model concept: Theoretical underpinnings and empirical illustrations. European Journal of Information Systems, Palgrave, Vol. 12.
Huemer, C., et al. (2008). A UML profile for the e3-value e-business model ontology, 3rd International Workshop on Business/IT Alignment and Interoperability (BUSITAL’08) Montpellier, France.
Ionita, M. T., et al. (2002). Scenario-based software architecture evaluation methods: An overview. ICSE Workshop on Methods and Techniques for Software Architecture Review and Assessment (ICSE/SARA), Orlando, USA.
Jansen, S., et al. (2012). Defining software ecosystems: A survey of software platforms and business network governance. 4th Int. Workshop on Software Ecosystems (IWSECO ’12), Cambridge, USA.
Jansen, S., et al. (2012). Shades of gray: Opening up a software producing organization with the open software enterprise model. Journal of Systems and Software, Elsevier, 85(7).
Kazman, R., et al. (2012). Scaling up software architecture analysis. Journal of Systems and Software, Elsevier, 85(7).
McGregor, J. D. (2010). A method for analyzing software product line ecosystems. 4th European Conference on Software Architecture: Companion Volume (ECSA ’10), New York, USA.
Popp, K. M. (2011). Hybrid revenue models of software companies and their relationship to hybrid business models, 3rd Int. Workshop on Software Ecosystems (IWSECO ’11), Brussels, Belgium.
Zott, C., & Amit, R. (2010). Business model design: An activity system perspective. Long Range Planning, Elsevier, 43(2–3).
- Modeling Partner Networks for Systematic Architecture Derivation in Software Ecosystems
- Springer Berlin Heidelberg
Neuer Inhalt/© ITandMEDIA, Product Lifecycle Management/© Eisenhans | vege | Fotolia