Managing External Innovation: The Case of Platform Extensions

More documents

Recommendations

Info

In a modular architecture, the modules developed have to be composed because a single closed software component offers less value than one that can be combined with other components to achieve greater functionality. Composability requires two properties: interoperability and complementarity. Interoperability means that modules must be able to communicate by having communicating infrastructure, a protocol used to communicate, and mutual communicating encoding. The communication mechanism enables the modules to complement each other in terms of what functions and capabilities they provide and how they provide them. Performance is an important aspect of software composition because we can have two separately fast components, but they can be very slow when combined. So integrating different components affects the overall system performance (Messerschmitt & Szyperski, 2003). The platform consists of a core that provides common functionalities and extensions that implement additional functionality. A platform extension is any module that is added after the platform deployment (Messerschmitt & Szyperski, 2003; Bosch, 2009). An extension could be a minor change such as adding a button to the toolbar, or a major change such as adding a new feature that extends the core functionalities (Baldwin & Clark, 2006; Gawer & Henderson, 2007). It is worth mentioning that the application programming interface (API) is an open interface designed to accept a broad class of extensions, where extension means a module or modules added later. Extensions are not 17
only modules added following the modules development but following modules deployment as they extend from the full knowledge of existing modules and add new capabilities to the platform. The quality of the developed modules is measured by performance and usability, both of which are two aspects of module composability (Messerschmitt and Szyperski, 2003). Extensible platform architecture empowers platforms because of the ongoing input from the community to complete and enhance the platform (Hemrajani, 2006b). Platform extensions may have different forms such as plug-ins, add-ons, and modules. Extensions can be classified as: external extensions, internal extensions, and extensions that become part the platform core. Figure 3 represents the platform architecture with different types of the platform extensions. Interface External (or optional) extension Internal (or essential) extension Infrastructure software Extensions became part of the platform core Platform Figure 3. Platform architecture and types of extensions 18 Extension
Page 1: MANAGING EXTERNAL INNOVATION: THE C
Page 4 and 5: ABSTRACT In recent years, high-tech
Page 6 and 7: TABLE OF CONTENTS 1 INTRODUCTION...
Page 8 and 9: 4.9 StarOffice.....................
Page 10 and 11: Figure 22. IBM HTTP Server communit
Page 12 and 13: Table 20. Collaboration modes for M
Page 14 and 15: 1 INTRODUCTION Iyer (2006) describe
Page 16 and 17: 2. How do platform owners encourage
Page 18 and 19: 1.4 Contributions This research con
Page 20 and 21: 2.1 Open innovation strategies and
Page 22 and 23: architecture, production process an
Page 24 and 25: Innovation Mall Elite Circle Innova
Page 26 and 27: platform and extends its functional
Page 28 and 29: Therefore, the platform architectur
Page 32 and 33: The distinction between external an
Page 34 and 35: platform, information, and service
Page 36 and 37: complexity of the platforms, and to
Page 38 and 39: • Contribution of external partie
Page 40 and 41: 3 RESEARCH METHOD This chapter desc
Page 42 and 43: 3.3 Method The research around regu
Page 44 and 45: 1. What are the models used by soft
Page 46 and 47: literature: i) regulatory tools, ii
Page 48 and 49: four projects was chosen using theo
Page 50 and 51: No. Section Description Data source
Page 52 and 53: Information was drawn from the plat
Page 54 and 55: 3.3.7 Identify strategies adopted b
Page 56 and 57: 4 WRITE UPS FOR PLATFORMS IN THE SA
Page 58 and 59: plug-in plugs and declares its depe
Page 60 and 61: Table 9. Collaboration modes for Ec
Page 62 and 63: selection of these new opportunitie
Page 64 and 65: products are based on Java technolo
Page 66 and 67: Table 10. Collaboration modes for I
Page 68 and 69: of that is adapting Firefox for use
Page 70 and 71: While not very prominent, there are
Page 72 and 73: as Extension Developer). There are
Page 74 and 75: Extension module Core module Spring
Page 76 and 77: Community structure Figure 15 shows
Page 78 and 79: The first stage is the extension pr
Page 80 and 81:
The SpringSource.com offers a partn
Page 82 and 83:
modules: set of core modules 4 that
Page 84 and 85:
Table 14. Collaboration mode for th
Page 86 and 87:
Regulatory instruments The Apache H
Page 88 and 89:
modules themselves and the Apache R
Page 90 and 91:
Table 15 represents the collaborati
Page 92 and 93:
Platform architecture The OpenOffic
Page 94 and 95:
Community Council Charter 7 . The c
Page 96 and 97:
Table 16. Collaboration modes for O
Page 98 and 99:
OpenOffice.org also has established
Page 100 and 101:
External Uno Internal Uno OenOffice
Page 102 and 103:
Sun Microsystems developers Extensi
Page 104 and 105:
to each other over the spinal cord
Page 106 and 107:
eceives commit access to the source
Page 108 and 109:
None of the previous cases had that
Page 110 and 111:
development process, the commercial
Page 112 and 113:
Platform architecture MySQL server
Page 114 and 115:
process is restricted to MySQL core
Page 116 and 117:
sandbox, extension development proc
Page 118 and 119:
Table 22. Summary of platform cases
Page 120 and 121:
No 1 2 3 4 5 Platform Spring framew
Page 122 and 123:
Community structure In Table 23, th
Page 124 and 125:
External extension Platform core In
Page 126 and 127:
5.1.3 Model C Table 27 represents t
Page 128 and 129:
Table 28. Collaboration modes for m
Page 130 and 131:
Table 29. Summary of the platforms
Page 132 and 133:
Collaboration Model Model C Advanta
Page 134 and 135:
Table 32.Summary of platform cases
Page 136 and 137:
6 DISCUSSION 6.1 Strategies for man
Page 138 and 139:
4. Regulatory instruments are used
Page 140 and 141:
Platform architecture Governance st
Page 142 and 143:
6.2 Regulatory instruments for mana
Page 144 and 145:
Pricing P10 Toolkits Governance San
Page 146 and 147:
Another key finding was the case of
Page 148 and 149:
Third, conduct a longitudinal study
Page 150 and 151:
Chen, W. J., Kirstein, H., Krook, D
Page 152 and 153:
Hemrajani, A. (2006a). Chapter 6: O
Page 154 and 155:
Herzog, P. (2008). Innovation and t
Page 156 and 157:
Rossi, A., & Zamarian, M. (2006). D
Page 158:
von Hippel, E. (2001). PERSPECTIVE:
show all

Managing External Innovation: The Case of Platform Extensions

Create successful ePaper yourself

Delete template?

Save as template?