Index Catalog // ScholarsArchive@OSU

Creator:: Dilhara, Malinda, Ketkar, Ameya, and Dig, Danny
Abstract:: Enabled by a rich ecosystem of Machine Learning (ML) libraries, programming using learned models, i.e., Software-2.0, has gained substantial adoption. However, we do not know what challenges developers encounter when they use ML libraries. With this knowledge gap, researchers miss opportunities to contribute to new research directions, tool builders do...
Resource Type:: Research Paper

Creator:: Hilton, Michael, Nelson, Nicholas, Dig, Danny, Tunnell, Timothy, Marinov, Darko, and Oregon State University. Department of Computer Science
Abstract:: Continuous integration (CI) systems automate the compilation, building, and testing of software. Despite CI being one of the most widely used processes in software engineering, we do not know what motivates developers to use CI, and what barriers and unmet needs they face. Without such knowledge developers make easily avoidable...
Resource Type:: Technical Report

Creator:: Bogdanas, Denis, Nelson, Nicholas, and Dig, Danny
Abstract:: To protect user’s privacy and system’s integrity, mobile platforms use permission models to control accesses to protected resources such as GPS location, Contacts, etc. The previous major version of Android used a static permission model, which compromised the security and privacy of apps. Android 6 overhauled its permission model to...
Resource Type:: Technical Report

Creator:: Hilton, Michael, Tunnell, Timothy, Huang, Kai, Marinov, Darko, and Dig, Danny
Abstract:: Continuous integration (CI) systems automate the compilation, building, and testing of software. Despite CI rising as a big success story in automated software engineering, it has received almost no attention from the research community. For example, how widely is CI used in practice, and what are some costs and benefits...
Resource Type:: Technical Report

Creator:: Codoban, Mihai, Srinivasa Ragavan, Sruti, Dig, Danny, and Bailey, Brian
Abstract:: Despite software history being indispensable for developers, there is little empirical knowledge about how they examine software history. Without such knowledge, researchers and tool builders are in danger of making wrong assumptions and building inadequate tools. In this paper we present an in-depth empirical study about the motivations developers have...
Resource Type:: Technical Report

ScholarsArchive@OSU