Designing Software Ecosystems: How to Develop Sustainable Collaborations?

Sadi, Mahsa Hasani; Dai, Jiaying; Yu, Eric

doi:10.1007/978-3-319-19243-7_17

Cited by 17 publications

(7 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Today, only the more radical approaches still pursue this line of inquiry (e.g., Vercellone, 2015;Morozov, 2019). For more mainstream economists, the relationship between commons-based and market-oriented production has become more central, as many commercial firms both contribute to the digital commons and are using Common Pool Resources in their commercial strategies (Sadi et al, 2015). The aim is to develop "open strategies", which is integrating commons-based production and various kinds of crowd-based inputs into company management (Birkinshaw, 2017).…”

Section: Economics New Models Of Productionmentioning

confidence: 99%

Digital commons

Rosnay¹,

Stalder²

2020

Internet Policy Review

View full text Add to dashboard Cite

Commons are holistic social institutions to govern the (re)production of resources, articulated through interrelated legal, socio-cultural, economic and institutional dimensions. They represent a comprehensive and radical approach to organise collective action, placing it "beyond market and state" (Bollier & Helfrich, 2012). They form a third way of organising society and the economy that differs from both market-based approaches, with their orientation toward prices, and from bureaucratic forms of organisation, with their orientation toward hierarchies and commands. This governance model has been applied to tangible and intangible resources, to local initiatives (garden, educational material), and to resources governed by global politics (climate, internet infrastructure). Digital commons are a subset of the commons, where the resources are data, information, culture and knowledge which are created and/or maintained online. The notion of the digital commons is an important concept for countering legal enclosure and fostering equitable access to these resources. This article presents the history of the movement of the digital commons, from free software, free culture, and public domain works, to open data and open access to science. It then analyses its foundational dimensions (licensing, authorship, peer production, governance) and finally studies newer forms of the digital commons, urban democratic participation and data commons. Issue 4This article belongs to Concepts of the digital society, a special section of Internet Policy Review guest-edited by Christian Katzenbach and Thomas Christian Bächle.

show abstract

Section: Economics New Models Of Productionmentioning

confidence: 99%

Digital commons

Rosnay¹,

Stalder²

2020

Internet Policy Review

View full text Add to dashboard Cite

show abstract

“…In addition, the work does not focus on developers. Sadi et al (2015) proposed a generic approach based on Android and iOS ecosystems to identify types of developers and derive alternative solutions to design appropriate collaboration. For example, the authors have found that Android platform developers choose an open source platform to cultivate intrinsic motivations such as skill development and reputation enhancement.…”

Section: Stack Overflowmentioning

confidence: 99%

Supporting governance of mobile application developers from mining and analyzing technical questions in stack overflow

Fontão

Ábia

Wiese

et al. 2018

J Softw Eng Res Dev

View full text Add to dashboard Cite

There is a need to improve the direct communication between large organizations that maintain mobile platforms (e.g. Apple, Google, and Microsoft) and third-party developers to solve technical questions that emerge during the project and development of developers' contributions in a Mobile Software Ecosystem (MSECO). In this context, those organizations may not know how to define and evolve strategies to govern their developers towards achieving their organizational goals. Such organizations use an infrastructure to support developers, for example, questions and answers (Q&A) portals such as Stack Overflow. Interactions among developers in these portals feed a Q&A repository that can serve as a mechanism to understand and define strategies to support developers. In this paper, we mined 1,568,377 technical questions from Stack Overflow related to Android, iOS, and Windows Phone platforms. Next, we performed comparisons among those MSECO regarding: (i) developers' activity intensity, (ii) hot-topics (using Latent Dirichlet allocation algorithm) from all and more commented/viewed questions, (iii) "What" and "How to" questions, (iv) hot-topics from more viewed unanswered questions, and (v) relationship among questions and official developer events. From the results, we identified four key insights: recruiting, educating, and monitoring strategies; barrier reduction; management of technology insertion; and fostering of relationships. The relevance of the four key insights to support developer governance was evaluated by practitioners through a survey. Finally, for each key insight we associated a total of 10 strategies to support developer governance activities. Such strategies were extracted from 65 studies identified through a systematic mapping of the literature. IntroductionIn Software Engineering, the relationship among mobile application developers and an organization responsible for a technological platform (keystone) which involves cooperation and competition has been investigated as a Software Ecosystem (SECO) (Bosch, 2009). In the mobile application (app) scenario, this context refers to a specific type of SECO, known as Mobile Software Ecosystem (MSECO) (Lin & Ye, 2009;Fontão et al., 2015). The developer is an essential actor to sustain MSECO contributions, such as apps and technical documentation (Fontão et al., 2016;Koch & Kerschbaum, 2014). Such contributions are usually stored in an official, internal MSECO repository, such as Android 1 and Apple 2 Developers repositories. Moreover, there are links between MSECO and external repositories, such as code (e.g. GitHub) (Casalnuovo et al., 2015) and questions and answers (Q&A) repositories. As an example of an external Q&A repository, Stack Overflow has a set of technical questions/answers that arise from the use of APIs, SDKs, and development tools (Ahmad et al., 2018). Such external repositories help to maintain the interaction among developers over a common platform, resulting in a set of contributions and influencing directly or indirectly the...

show abstract

“…Emergent stakeholders play a major role in driving requirements discussion and decision making. To our knowledge, however, research has so far mainly investigated emergent developers [46,24,51] and emergent knowledge [59], while only few works exist that start to investigate the effect of emergent contributors on requirements [35]. This is however an important aspect, as software ecosystems facilitate communication between the various levels of involved organizations and the role of emergent collaboration spans beyond developers and software teams [33].…”

Section: Related Workmentioning

confidence: 99%

Continuous clarification and emergent requirements flows in open-commercial software ecosystems

et al. 2016

View full text Add to dashboard Cite

Software engineering practice has shifted from the development of products in closed environments toward more open and collaborative efforts. Software development has become significantly interdependent with other systems (e.g. services, apps) and typically takes place within large ecosystems of networked communities of stakeholder organizations. Such software ecosystems promise increased innovation power and support for consumer-oriented software services at scale and are characterized by a certain openness of their information flows. While such openness supports project and reputation management, it also brings requirements engineering-related challenges within the ecosystem, such as managing dynamic, emergent contributions from the ecosystem stakeholders, as well as collecting their input while protecting their IP. In this paper, we report from a study of requirements communication and management practices within IBM Ò 's Collaborative Lifecycle Management Ò product development ecosystem. Our research used

show abstract

Designing Software Ecosystems: How to Develop Sustainable Collaborations?

Cited by 17 publications

References 13 publications

Digital commons

Digital commons

Supporting governance of mobile application developers from mining and analyzing technical questions in stack overflow

Continuous clarification and emergent requirements flows in open-commercial software ecosystems

Contact Info

Product

Resources

About