search query: @instructor Raatikainen, Mikko / total: 19
reference: 9 / 19
« previous | next »
Author:Dal Bianco, Vittorio
Title:Third-party developer experience: Using the platform boundary resources of a software ecosystem
Publication type:Master's thesis
Publication year:2013
Pages:ix + 90      Language:   eng
Department/School:Perustieteiden korkeakoulu
Main subject:Tietojenkäsittelyoppi   (T-76)
Supervisor:Kauppinen, Marjo
Instructor:Raatikainen, Mikko
OEVS:
Electronic archive copy is available via Aalto Thesis Database.
Instructions

Reading digital theses in the closed network of the Aalto University Harald Herlin Learning Centre

In the closed network of Learning Centre you can read digital and digitized theses not available in the open network.

The Learning Centre contact details and opening hours: https://learningcentre.aalto.fi/en/harald-herlin-learning-centre/

You can read theses on the Learning Centre customer computers, which are available on all floors.

Logging on to the customer computers

  • Aalto University staff members log on to the customer computer using the Aalto username and password.
  • Other customers log on using a shared username and password.

Opening a thesis

  • On the desktop of the customer computers, you will find an icon titled:

    Aalto Thesis Database

  • Click on the icon to search for and open the thesis you are looking for from Aaltodoc database. You can find the thesis file by clicking the link on the OEV or OEVS field.

Reading the thesis

  • You can either print the thesis or read it on the customer computer screen.
  • You cannot save the thesis file on a flash drive or email it.
  • You cannot copy text or images from the file.
  • You cannot edit the file.

Printing the thesis

  • You can print the thesis for your personal study or research use.
  • Aalto University students and staff members may print black-and-white prints on the PrintingPoint devices when using the computer with personal Aalto username and password. Color printing is possible using the printer u90203-psc3, which is located near the customer service. Color printing is subject to a charge to Aalto University students and staff members.
  • Other customers can use the printer u90203-psc3. All printing is subject to a charge to non-University members.
Location:P1 Ark Aalto     | Archive
Keywords:software ecosystems
third-party developer experience
platform boundary resources
Abstract (eng): Software ecosystems are an increasingly common setting in which software organizations operate.
A software ecosystem refers to a context where a keystone player, or platform owner, provides a software platform and platform boundary resources.
These resources allow third-party developers to build software applications on top of the platform.
These applications target end-users who selected to adopt the software platform.
The relationships among the entities we introduced are the engine of a software ecosystem.

After selecting the software platform, much of the interaction the end-users have with the software ecosystem happens by selecting and using the software applications that are available in the software ecosystem.
Hence, software applications play a crucial role in the success of the software ecosystem.
Attracting third-party developers to build software applications is, therefore, a key issue.

In this sense, a fundamental technical concern is third-party developer experience.
In fact, minimizing developer's effort is recognized as one of the key success factors; and it requires acting on the platform boundary resources.
We understand this as enabling third-party development.
We investigated these issues in the specific context of F-Secure's Content Anywhere (CAN) Ecosystem.
We conducted a case study in a hackathon event, where F-Secure used the CAN Ecosystem.

We found out that enablement can occur to different degrees.
We concluded that the minimum requirement is to ensure technical feasibility through APIs and access to basic resources, While, for example, addressing issues of learnability and abstraction levels helps to raise the degree of enablement; thus increasing the software ecosystem's attractiveness to third-party developers.
Additionally, the third-party developer experience is affected by met or unmet expectations: the expectations depend on the mental model that the developer constructs,
ED:2013-09-26
INSSI record number: 47254
+ add basket
« previous | next »
INSSI