SluitenHelpPrint
Switch to English
Cursus: INFOMSSE
INFOMSSE
Software ecosystems
Cursus informatie
CursuscodeINFOMSSE
Studiepunten (EC)7,5
Cursusdoelen
The goals of this course are:
  • To get students intimately familiar with the theory of software ecosystems, specifically management, modeling, and simulation
  • To get students acquainted with the academic writing and publication process
  • To contribute to the collection of knowledge on software ecosystems
  • To show students the cutting edge of science in a field and to provoke thought about future developments
The aim of the seminar is to get students familiar with selected topics on software ecosystems but also to get students familiar with the academic publication process.
Inhoud
vendors no longer function as independent units, where all customers are end-users, where there are no suppliers, and where all software is built in-house. Instead, software vendors have become networked, i.e., software vendors are depending on (communities of) service and software component suppliers, value-added-resellers, and pro-active customers who build and share customizations. Software vendors now have to consider their strategic role in the software ecosystem to survive. With their role in the software ecosystem in mind, software vendors can become more successful by opening up their business, devising new business models, forging long-lasting relationships with partnership networks, and overcoming technical and social challenges that are part of these innovations.
software ecosystem is a set of actors functioning as a unit and interacting with a shared market for software and services, together with the relationships among them. These relationships are frequently underpinned by a common technological platform or market and operate through the exchange of information, resources and artifacts. Several challenges lie in the research area of software ecosystems. To begin with, insightful and scalable modeling techniques for software ecosystems currently do not exist. Furthermore, methods are required that enable software vendors to transform their legacy architectures to accommodate reusability of internal common artifacts and external components and services. Finally, methods are required that support software vendors in choosing survival strategies in software ecosystems.
introduce many new research challenges on both a technical and a business level. In a traditionally closed market, software vendors are now facing the challenge of opening up their product interfaces, their knowledge bases, and in some cases even their software. Software vendors must decide how open their products and interfaces are, new business models need to be developed, and new standards for component and service reuse are required. These challenges have been identified but have hardly been picked up by the research community.
In this seminar topics on SECOs are discussed. These topics can range from consultancy oriented for product software companies to highly technical for software engineers. The course is largely dependent on student participation. Some example topics are:
  • Virtualized software enterprises
  • Open source software ecosystems
  • Market-specific domain engineering
  • Software ecosystem orchestration
  • Software development communities
  • Software product lines
  • Software product management
  • Publishing APIs
  • API development
  • Formal modeling of business models
  • Architectural implications of reusability
  • Keystone and niche player survival strategy
  • Software ecosystem creation
  • Economic impact of software ecosystems
  • Communities of practice and software reuse
  • Product software and software licensing
  • Software business models
  • Software ecosystem practices and experience
  • Software ecosystem modeling
  • API related topics: design, development, marketing
  • Software ecosystem models
  • A software ecosystem analysis method
  • Strategic advice for software vendors
  • API compatibility over subsequent releases
SluitenHelpPrint
Switch to English