2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE)最新文献_第2页

Using a Tool-based Approach to Comply with Smartphone User Manual Regulations in Latin America Countries 在拉丁美洲国家使用基于工具的方法遵守智能手机用户手册规定

2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE) Pub Date : 2020-05-01 DOI: 10.1145/3372787.3390431

Klinsman M. Gonçalves, Yasmine G. Vaz, Eberth F. Cruz, Rafael E. Silva, Lineker Souza, Fábio M. Azevedo, Eduardo D. Sardinha, Paulo Fonseca, Cícero A. L. Pahins

{"title":"Using a Tool-based Approach to Comply with Smartphone User Manual Regulations in Latin America Countries","authors":"Klinsman M. Gonçalves, Yasmine G. Vaz, Eberth F. Cruz, Rafael E. Silva, Lineker Souza, Fábio M. Azevedo, Eduardo D. Sardinha, Paulo Fonseca, Cícero A. L. Pahins","doi":"10.1145/3372787.3390431","DOIUrl":"https://doi.org/10.1145/3372787.3390431","url":null,"abstract":"Developing Android mobile devices with geographically distributed teams can be arduous. SIDIA is an R&D institute that is responsible for research and development for the Brazilian and global market. SIDIA has clients around the world, and one of them is a mobile device manufacturer which embeds the Android operating system into such devices. To sell smartphones in all desired countries, some regulations must be adhered to. In Brazil and Colombia, one of the mandatory regulations by law is that every product must contain a User Instruction Manual (UIM), which helps users to figure out distinctive aspects and features of the product. Currently, the Android OS Version for mobile devices commercialized in America (Latin mobile devices) and UIM are developed and designed in cities from different states (Manaus, Amazonas – Campinas, São Paulo) from Brazil. Moreover, to design the UIM is necessary to have access to the physical device, so it must be shipped across distant cities. Due to logistical problems and bureaucracy in administrative processes, the device may take a long time to be delivered and, consequently, may delay smartphone manufacturing, causing financial damage. This experience report describes the lessons learned on developing and integrating a tool-based approach that allows users to remotely access a device thereby solving the physical device dependency problem and addressing specific requirements of the UIM development.","PeriodicalId":313953,"journal":{"name":"2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134281750","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 2

Developing a Conversational Agent With a Globally Distributed Team: An Experience Report 开发具有全球分布团队的会话代理:一份经验报告

2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE) Pub Date : 2020-05-01 DOI: 10.1145/3372787.3390430

Elayne Ruane, Ross Smith, Dan Bean, M. Tjalve, Anthony Ventresque

引用次数: 3

Understanding Collaborative Software Development: An Interview Study 理解协同软件开发:一项访谈研究

2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE) Pub Date : 2020-05-01 DOI: 10.1145/3372787.3390442

K. Constantino, Shurui Zhou, M. Souza, Eduardo Figueiredo, Christian Kästner

引用次数: 18

Hybrid Sourcing: Novel Combination of Crowdsourcing and Inner-sourcing for Software Developments 混合外包:软件开发中众包和内部外包的新颖结合

2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE) Pub Date : 2020-05-01 DOI: 10.1145/3372787.3389301

Shinobu Saito, Yukako Iimura

{"title":"Hybrid Sourcing: Novel Combination of Crowdsourcing and Inner-sourcing for Software Developments","authors":"Shinobu Saito, Yukako Iimura","doi":"10.1145/3372787.3389301","DOIUrl":"https://doi.org/10.1145/3372787.3389301","url":null,"abstract":"Sourcing the right IT engineers is critical for project success. In recent years, two sourcing strategies have been grabbing attention: crowdsourcing and inner-sourcing. Each has their own good points and bad points. Crowdsourcing allows organizations to recruit IT engineers from outside on demand. However, organizations working on closed-source code with confidential information might be worried about security concerns (e.g., information leak). The other strategy, inner-sourcing, can make any IT engineer in an organization become a member of all projects by adopting open source software development practices. This improves the mobility of IT engineers between projects inside the organization. However, there is a limit to the types of IT engineers that one organization can have. In this report, we propose a hybrid sourcing approach. It integrates the two sourcing strategies to develop software - crowdsourcing and inner-sourcing. This approach distributes the development tasks to either software crowdsourcing or inner-sourcing according to task type. As a case study, we adopt hybrid sourcing approach for an industrial project. The project developed a web application system for a bus company. We evaluate the effectiveness and future issues of hybrid sourcing.","PeriodicalId":313953,"journal":{"name":"2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132509864","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 2

On Value Creation in Developer Relations (DevRel): A Practitioners’ Perspective 开发者关系中的价值创造:一个实践者的视角

2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE) Pub Date : 2020-05-01 DOI: 10.1145/3372787.3390440

A. Fontão, Sergio Cleger-Tamayo, I. Wiese, R. Santos, A. C. Dias-Neto

{"title":"On Value Creation in Developer Relations (DevRel): A Practitioners’ Perspective","authors":"A. Fontão, Sergio Cleger-Tamayo, I. Wiese, R. Santos, A. C. Dias-Neto","doi":"10.1145/3372787.3390440","DOIUrl":"https://doi.org/10.1145/3372787.3390440","url":null,"abstract":"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 roadmapCCS CONCEPTS• Software creation and • Software and its engineering management • Collaboration in software development","PeriodicalId":313953,"journal":{"name":"2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE)","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130911806","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 8

A Case Study on Tool Support for Collaboration in Agile Development 敏捷开发中协作工具支持的案例研究

2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE) Pub Date : 2020-04-01 DOI: 10.1145/3372787.3390436

Fabio Calefato, Andrea Giove, Marco Losavio, F. Lanubile

{"title":"A Case Study on Tool Support for Collaboration in Agile Development","authors":"Fabio Calefato, Andrea Giove, Marco Losavio, F. Lanubile","doi":"10.1145/3372787.3390436","DOIUrl":"https://doi.org/10.1145/3372787.3390436","url":null,"abstract":"We report on a longitudinal case study conducted at the Italian site of a large software company to further our understanding of how development and communication tools can be improved to better support agile practices and collaboration. After observing inconsistencies in the way communication tools (i.e., email, Skype, and Slack) were used, we first reinforced the use of Slack as the central hub for internal communication, while setting clear rules regarding tools usage. As a second main change, we refactored the Jira Scrum board into two separate boards, a detailed one for developers and a high-level one for managers, while also introducing automation rules and the integration with Slack. The first change revealed that the teams of developers used and appreciated Slack differently with the QA team being the most favorable and that the use of channels is hindered by automatic notifications from development tools (e.g., Jenkins). The findings from the second change show that 85% of the interviewees reported perceived improvements in their workflow. Despite the limitations due to the single nature of the reported case, we highlight the importance for companies to reflect on how to properly set up their agile work environment to improve communication and facilitate collaboration.","PeriodicalId":313953,"journal":{"name":"2020 ACM/IEEE 15th International Conference on Global Software Engineering (ICGSE)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132127957","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 11