Software Ecosystems

Software Ecosystems

Analyzing and Managing Business Networks in the Software Industry

Edited by Slinger Jansen, Sjaak Brinkkemper and Michael Cusumano

This book describes the state-of-the-art of software ecosystems. It constitutes a fundamental step towards an empirically based, nuanced understanding of the implications for management, governance, and control of software ecosystems.

Chapter 6: The challenge of heterogeneously-licensed systems in open architecture software ecosystems

Thomas A. Alspaugh, Hazeline U. Asuncion and Walt Scacchi

Subjects: business and management, organisational innovation, organisation studies, strategic management, innovation and technology, organisational innovation

Extract

A substantial number of development organizations are adopting a strategy in which a software-intensive system is developed with an open architecture (OA) (Oreizy, 2000), whose components may be open source software (OSS) or proprietary with open application programming interfaces (APIs). Such systems evolve not only through the evolution of their individual components, but also through replacement of one component by another, possibly from a different producer or under a different license. With this approach, the organization becomes an integrator of components largely produced elsewhere that are interconnected through open APIs as necessary to achieve the desired result. An OA development process results in an ecosystem in which the integrator is influenced from one direction by the goals, interfaces, license choices, and release cycles of the component producers, and in another direction by the needs of its consumers. As a result the software components are reused more widely, and the resulting OA systems can achieve reuse benefits such as reduced costs, increased reliability, and potentially increased agility in evolving to meet changing needs. An emerging challenge is to realize the benefits of this approach when the individual components are heterogeneously licensed, each potentially with a different license, rather than a single OSS license as in uniformly-licensed OSS projects, or a single proprietary license when acquired from a vendor employing a proprietary development scheme.

You are not authenticated to view the full text of this chapter or article.

Elgaronline requires a subscription or purchase to access the full text of books or journals. Please login through your library system or with your personal username and password on the homepage.

Non-subscribers can freely search the site, view abstracts/ extracts and download selected front matter and introductory chapters for personal use.

Your library may not have purchased all subject areas. If you are authenticated and think you should have access to this title, please contact your librarian.

Further information