Abstract Software Ecosystem (SECO) comprises third‐party developers cooperating and competing when contributing to a platform provided by a central organization (keystone). There are keystones investing in Developer Relations (DevRel) internal team as a global business strategy to attract and engage a critical mass of third‐party developers in producing and evolving contributions. For this reason, the DevRel team should promote social relationships among SECO actors and synergy among keystone' goals and developers' expectations to survive to inherit changes. However, the understanding of DevRel structure and the way DevRel team can act on a SECO to better engage the developers' communities establishing a robust VCN (Value Creation Network) remain a challenge. In this article, we advance on the structure for developers' governance from DevRel by proposing and refining a model because of the following research methods: grey literature review, opinion survey, and interviews. The model is called DevGo (DEVeloper GOVernance) and consists of four focus areas, three developer advancement phases, six stages, enablers, and value transfer objects. In addition, a set of 62 lessons learned from DevRel practitioners is associated with DevGo stages.

Software Ecosystem (SECO) comprises third-party developers cooperating and competing when contributing to a platform provided by a central organization (keystone). A keystone has invested in a Developer Relations (DevRel) internal team as a global business strategy to attract and engage a critical mass of third-party developers in producing and evolving contributions. For this reason, the DevRel team should promote social relationships among SECO actors and synergy among keystone' goals and developers' expectations. It can help to establish and sustain a competitive value creation network (VCN) within a SECO that must survive to inherit changes. However, it is still a challenge the way DevRel team can act on a SECO to better engage the developers' communities aiming to establish a robust VCN. In this paper, we advance on investigating the perceptions of 31 DevRel practitioners from large, medium and small-size companies based on seven countries about value creation in DevRel. We found 55 elements of value creation distributed in retention, efficiency, innovation, and complementarity. Based on our analysis, we contribute with a set of seven insights (feedback loop, loyalty program, roadmap enhancement, technical training, processes restructuring, innovative products, cost reducing) and a DevRel VCN that involves elements, suppliers and consumers. It fosters a common perspective for DevRel practitioners, keystones and researchers for designing strategies and a research roadmap.

This paper presents an interdisciplinary approach designed to join theoretical foundations required in software engineering with practice required for professional performance in software industry. Although this is a recurring issue on software engineering education, students still have difficulties in dealing with software development environments that are usually more complex than any software projects they have worked at university courses. We developed an approach aligned with market demands and theoretical requirements in software engineering education that incorporates principles of Project Based Learning (PBL) and Agile Methods. It aims to support development of student technical and soft skills in three different, but related, disciplines: Software Engineering Practice, Database Practice and Software Project Management. We describe a set of seven recommendations on how we used largely adopted tools in software development industry in order to develop student technical and soft skills. We describe two case studies: (1) an exploratory case study with three professors and 24 students involving multiple projects; and (2) a confirmatory case study with three professors and 15 students involving a large-scale project. As a result, we point seven recommendations for tool adoption on capstone courses based on lessons learned.

Testing is a very essential activity for software development. It is the act of executing a software product in order to validate whether it behaves as intended and identify possible malfunctions. Studies have shown that testing makes up more than 50% of the development cost. Besides, much effort and emphasis have now been placed on tasks related to automation with the purpose of reducing cost and the participation of the human element in software testing activities. Testing is still a human-based activity. Therefore, efficient ways of testing software products for quality assurance will require a better and more comprehensive understanding of testers' feelings, perceptions and motivations, in this paper referred to as Tester Experience (TX). Thus, the better the tester's experience during the software testing process, the better the result. TX can be defined as a means of capturing how testers think and feel about their activities within the software testing environment, with the assumption that an improvement of the tester's experience has positive impact on quality assurance. This paper motivates the importance of TX, highlights related approaches from other domains, proposes a definition based on similar concepts in other domains, and proposes future research activities.

In a Mobile Software Ecosystem (MSECO), the central organization (keystone), must restructure processes to aid external developers to produce mobile applications.The external developer helps the keystone to reach goals, such as growing number of mobile applications.However, there is no process in this context to support developers in the development aligned with the keystone's goals.This paper presents MSECO-DEV, a process to support external developers in reaching keystone's goals by developing mobile applications.MSECO-DEV comprises 8 activities, 7 artifacts, 8 recommendations, and 17 practices.Activities, recommendations, and practices were evaluated by 65 Brazilian developers (experts and novices).Such developers acted within the main MSECOs (Android, iOS and Windows Phone) to assess their benefits for the mobile applications development routine.As result, we stated that developers have difficulties to perform marketing activities, as well as to find materials that support development.Practices, activities, and recommendations were also evolved and adjusted for the definition of MSECO-DEV.

The development of mobile applications around a central software platform has been impacting the software industry. Software solutions are collaboratively built within a dynamic market, often requiring adaptation of software development processes. This trend has been broadly studied as Software Ecosystem (SECO) - in the mobile platform domain, named as Mobile Software Ecosystem (MSECO). In this paper, we share the results of a systematic mapping study on the MSECO field that analyzed 28 papers identified as relevant to answer our research questions. The results indicate the growing interest in this research field as well as the main software platforms and trending topics. We confirmed the three main MSECOs as Android (Google), iOS (Apple) and Windows Phone (Microsoft). We observed the more investigated area is mobile app development. Finally, we highlighted the main benefits: the attracting and supporting developers, then helping developers to learn and create content and the app store that allows selling and buying processes.

Sink nodes are responsible for aggregating data gathered by a Wireless Sensor Network (WSN) and transmitting them to a monitoring facility. Usually, these are static nodes that serve as gateways to infrastructured networks. In some applications, these sink nodes move around the monitoring area, usually in lower speeds (e.g., robots, dirigibles). In this work, we go further and study WSN scenarios in which sink nodes can move at higher speeds, such as an Unmanned Aerial Vehicle (UAV) or even an airplane. In these cases, propagated queries cannot be answered by using the sink's position when the query was sent, since the sink will be elsewhere due to its high speed. Thus, we propose and evaluate the performance of three algorithms for data query in WSNs when the sink is moving at a high speed. Our results show clearly the need for new algorithms for these scenarios as well as the good performance of our proposed algorithms.