Driver behavior impacts traffic safety, fuel/energy consumption and gas emissions. Driver behavior profiling tries to understand and positively impact driver behavior. Usually driver behavior profiling tasks involve automated collection of driving data and application of computer models to generate a classification that characterizes the driver aggressiveness profile. Different sensors and classification methods have been employed in this task, however, low-cost solutions and high performance are still research targets. This paper presents an investigation with different Android smartphone sensors, and classification algorithms in order to assess which sensor/method assembly enables classification with higher performance. The results show that specific combinations of sensors and intelligent methods allow classification performance improvement.

No abstract

One of the reasons why large-scale software development is difficult is the number of dependencies that software engineers need to face: e.g., dependencies among the software components and among the development tasks. These dependencies create a need for communication and coordination that requires continuous effort by software developers. Empirical studies, including our own, suggest that technical dependencies among software components create social dependencies among the software developers implementing these components. Based on this observation, we developed Ariadne, a Java plug-in for Eclipse. Ariadne analyzes a Java project to identify program dependencies and collects authorship information about the project by connecting to a configuration management repository. Through this process, Ariadne can "translate" technical dependencies among software components into social dependencies among software developers. This paper describes the design of Ariadne, how it identifies technical dependencies among software components, how it extracts information from configuration management systems and, finally, how it translates this into social dependencies. Ariadne's purpose is to create a bridge between technical and social dependencies.

Software Ecosystems are comprised of a technology platform, business models, internal and external developers, and engaging users. The popularity of smartphones brought along the mobile software ecosystems, such as iOS and Android, which are composed of a platform, a community of users and developers, mobile applications, and online application store, and evangelists that often promote the ecosystem. Given the recent nature of the topic, this paper aims to revisit the state-of-the-art through a systematic literature mapping. We found 63 publications on the topic of mobile software ecosystems that were categorized by year (almost 50% of the publications are from 2015 and on), by author (a few collaboration clusters were identified), and by the mobile ecosystems characteristics (most publications discuss business or technical aspects) and elements (applications and the platform are the most discussed topics followed by the developers and the users). Our results provide an up-to-date map of the topic for those interested in mobile software ecosystems.

No abstract

Global software development (GSD) has been an important research topic in the CSCW community for more than two decades. CSCW has helped identify a significant number of challenges and solutions for handling distances in time, space and culture in distributed software engineering environments. However, no comprehensive collected body of knowledge concerning research on GSD from a CSCW perspective exists yet. The goal of this workshop is to bring together researchers and practitioners who have studied GSD from a CSCW perspective, and provide an overview of current findings and future challenges. In the workshop, we will facilitate group discussions across the diverse groups of researchers coming from ethnographic studies of software development practices and design studies of CSCW tools and processes for GSD. The goal is to provide an overview of current research, which in turn may form the basis for joint publications or an edited book

The new coronavirus pandemic has forced companies around the world to adopt measures to stop the spread of this virus and the associated COVID-19 disease. In Brazil, this was no different with software development professionals having to work from home (WFH) due to the need of social isolation. WFH was an imposition and was a new experience for many professionals, generating unpredictable impacts. In this article, we present the results of a survey to understand the impacts of social isolation on the perceived productivity of Brazilian software developers. Data were collected during March and April/2020 with a sample of 413 respondents. The results indicate developers' perceived productivity has increased, mainly because there are fewer interruptions throughout the day. In addition, most respondents informed that they wish to continue working most of the time remotely. We contrast our results with another study published on this topic. CCS CONCEPTS• Software and its engineering → Visual languages; Agile software development.

Ariadne is a novel visualization tool that allows end users to explore the socio-technical relationships in software development projects. Essentially the visualization is a variant of a social network graph. It is based on the observation that dependencies between software components create dependencies between the developers implementing those components. This relationship emerged in our own and other researchers' field studies of software projects. Large software development projects require management of dependencies by managers and developers to ensure the smooth coordination of work. We sought to evaluate our visualization to assess its utility. Although we had some informal trials with potential end users, we sought a deeper analysis before further refinement of the tool and evaluation on a larger scale. Usability inspection methods provided one potential avenue. Moreover, such inspection methods yield a kind of rationale not directly derived from human subjects evaluations. We report on the application of these inspection methods and discuss the implications of their results in the context of usability evaluations for visual interfaces.