Managing External Innovation: The Case of Platform Extensions

Managing External Innovation: The Case of Platform Extensions Managing External Innovation: The Case of Platform Extensions

www3.carleton.ca
from www3.carleton.ca More from this publisher
18.04.2014 Views

3 RESEARCH METHOD This chapter describes the method used to produce the deliverables of this research. It is organized in three sections. Section 3.1 describes the unit of analysis. Section 3.2 identifies the study period. Section 3.3 describes the research method and the steps undertaken to answer the research 3.1 Unit of Analysis The unit of analysis is a software platform that provides the ability for external parties to extend its functionalities. Platform extensions can take several forms, for example plugins, add-ons, modules and new features are considered extensions. The research focus is on extension that adds a new feature to the platform and as a result will affect the integrity and over all performance of the platform. Firefox tabbed browser or Apache Application Server new core module are examples of extensions affect the core functionality of the platform. 3.2 Study period The data were collected from March to July 2009. The cases covered in this research are between the years 2000 and 2009. The reason behind the decision of choosing this time period is that several platforms that provided extensibility were launched (e.g. Eclipse platform, OpenOffice.org, and SpringSource.org), some platforms were re-factored or rewritten to support extensibility (e.g. Apache, IBM WebSphere, and MySQL) (See Figure 4, the case platforms timeline). Platforms up to June 2009 were covered in this research to establish a limit for the researcher’s data collection. 27

Figure 4. Case platform timeline 28

Figure 4. <strong>Case</strong> platform timeline<br />

28

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!