Source Data for the Focus Area Maturity Model for Software Ecosystem Governance

We define a software ecosystem as a set of organizations collaboratively serving a market for software and services. Typically these ecosystems are underpinned by a common technology, such as an extendable software platform. This data set supports the article that describes the Software Ecosystem Governance Maturity Model (SEG−M2) [50]. The model has the goal to support software ecosystem orchestrators in the management and governance of the actors in their ecosystems in a structured way. Through a critical structured literature review, 168 practices have been collected. These practices have been evaluated through six case studies at software ecosystem orchestrators. The practices are described with a practice code, a practice name, a practice description, required success conditions, the person responsible for the practice, and the associated literature where the practice was identified

Software release and deployment at Exact: a case study report

For vendors of product software it is becoming more and more difficult to manage and control the software configurations of all their users at the customer\'s site. It is labour intensive and error-prone to (semi)automatically register detailed lists of the software artefacts in use by each customer. To alleviate this problem the Deliver project proposes an Intelligent Software Knowledge Base that contains all facts about all artefacts together with their relevant attributes, relations and constraints. In this way, high-quality software configurations can be calculated automatically from a small set of key parameters. It also becomes possible to pose what-if questions about necessary or future upgrades of a customer\'s configuration. This document describes a case study performed at Exact Software into the processes of release and deployment. The results of the case study are presented, existing of process descriptions of the development, release and deployment processes at Exact Software, a comparison to the Intelligent Software Knowledge Base, and an analysis of the result

A process framework and typology for software product updaters.

Product software is constantly evolving through extensions, maintenance, changing requirements, changes in configuration settings, and changing licensing information. Managing evolution of released and deployed product software is a complex and often underestimated problem that has been the cause of many difficulties for both software vendors and customers. This paper presents a framework and typology to characterize techniques that support product software update methods. The framework is based on a detailed process model of software updating. Finally, this paper assesses and surveys a variety of existing techniques against the characterisation framework and lists unsolved problems related to software product updater

Release and deployment at Planon: a case study

This case study report describes the research results of a case study at Planon into the processes of development, release, and deployment. The research was done to document the release and deployment processes at Planon, to uncover strengths and weaknesses in these processes, and to compare Planon to other product software vendors. The case study was performed by doing interviews and examining development documentation, Planon software, and internally used tools. The results of the case study are organizational descriptions, Planon software descriptions, and the descriptions of the development, release, and deployment processes. The main conclusions of the case study are twofold. First the case study shows that striving for more integrated software knowledge management can relieve the processes of release and deployment. Secondly, the case study displays that extensive variation management can effectively increase the customer base for a software vendo

Integrated SCM/PDM/CRM and delivery of software products to 160.000 customers

The release and deployment of enterprise application software is a potentially complex task for software vendors. This complexity can unfortunately result in a significant amount of work and risk. This paper presents a case study of a product software vendor that tries to reduce this complexity by integrating product data management (PDM), software configuration management (SCM), and customer relationship management (CRM) into one system. The case study shows that by combining these management areas in a single intelligent software knowledge base, software release and deployment processes can be automated and improved, thereby enabling a software vendor of enterprise software to serve a large number of customers with different product configuration

A process framework and typology for software product updaters.

Product software is constantly evolving through extensions, maintenance, changing requirements, changes in configuration settings, and changing licensing information. Managing evolution of released and deployed product software is a complex and often underestimated problem that has been the cause of many difficulties for both software vendors and customers. This paper presents a framework and typology to characterize techniques that support product software update methods. The framework is based on a detailed process model of software updating. Finally, this paper assesses and surveys a variety of existing techniques against the characterisation framework and lists unsolved problems related to software product updater

Integrated SCM/PDM/CRM and delivery of software products to 160.000 customers

The release and deployment of enterprise application software is a potentially complex task for software vendors. This complexity can unfortunately result in a significant amount of work and risk. This paper presents a case study of a product software vendor that tries to reduce this complexity by integrating product data management (PDM), software configuration management (SCM), and customer relationship management (CRM) into one system. The case study shows that by combining these management areas in a single intelligent software knowledge base, software release and deployment processes can be automated and improved, thereby enabling a software vendor of enterprise software to serve a large number of customers with different product configuration

Complementor embeddedness in platform ecosystems : the case of google apps

Platforms and their marketplaces with complementarities are prominent in the software industry. As the proprietary platform itself exhibits elementary or generic functionality, platform owners depend on a complementor ecosystem populated by third-parties. At present, little is known about mechanisms at play in proprietary ecosystems. Addressing this deficiency, this paper investigates the Google Apps ecosystem through statistical and network analysis. Results show that the Google Apps ecosystem is sparsely connected, the majority of complementors develops one application (83%) and does not have visible relationships (73%). Furthermore, there is a positive relationship between the number of applications a complementor develops and the number of relationships it establishes. The research method and results presented can be used by practitioners as a reference to evaluate their structural position in the ecosystem, while it provides researchers with a quantification of ecosystem characteristics