Days: Thursday, November 9th Friday, November 10th
View this program: with abstractssession overviewtalk overview
09:30 | An empirical analysis of FLOSS repositories to compare One-Time Contributors to Core and Periphery Developers ( abstract ) |
10:30 | Code churn: A neglected metric in effort-aware Just-In-Time defect prediction ( abstract ) |
11:00 | Security Vulnerabilities in Categories of Clones and Non-Cloned Code: An Empirical Study ( abstract ) |
11:30 | Early Phase Cost Models for Agile Software Processes in the US DoD ( abstract ) |
10:30 | Automatic Building of Java Projects in Software Repositories: A Study on Feasibility and Challenges ( abstract ) |
11:00 | Coding in Your Browser: Characterizing Programming Behavior in Cloud Based IDEs ( abstract ) |
11:30 | (Journal First) Improving the delivery cycle: A multiple-case study of the toolchains in Finnish software intensive enterprises ( abstract ) |
10:30 | An Empirical Examination of the Relationship Between Code Smells and Merge Conflicts ( abstract ) |
11:00 | On the Influence of Human Factors for Identifying Code Smells: A Multi-Trial Empirical Study ( abstract ) |
11:30 | What if I had no smells? ( abstract ) |
13:00 | Introducing automated GUI testing and observing its benefits: an industrial case study in the context of law-practice management software ( abstract ) |
13:30 | (Journal First) Maintenance of automated test suites in industry: An empirical study on Visual GUI Testing ( abstract ) |
14:00 | Would You Like to Motivate Software Testers? Ask Them How ( abstract ) |
13:00 | Characterizing Software Developers by Perceptions of Productivity ( abstract ) |
13:30 | Beyond Continuous Delivery: An Empirical Investigation of Continuous Deployment Challenges ( abstract ) |
14:00 | (Journal First) Benefits and drawbacks of software reference architectures: A case study ( abstract ) |
13:00 | Where is the Road for Issue Reports Classification Based on Text Mining? ( abstract ) |
13:30 | Predicting the Vector Impact of Change - An Industrial Case Study at Brightsquid ( abstract ) |
14:00 | Managing Hidden Dependencies in OO Software: a Study Based on Open Source Projects ( abstract ) |
15:00 | STRESS: A Semi-Automated, Fully Replicable Approach for Project Selection ( abstract ) |
15:15 | Change-Aware Build Prediction Model for Stall Avoidance in Continuous Integration ( abstract ) |
15:30 | Delta-Bench: Differential Benchmark for Static Analysis Security Testing Tools ( abstract ) |
15:45 | An Ontology-based Approach to Automate Tagging of Software Artifacts ( abstract ) |
16:00 | REACT: An Approach for Capturing Rationale in Chat Messages ( abstract ) |
15:00 | Describing What Experimental Software Engineering Experts Do When They Design their Experiments – A Qualitative Study ( abstract ) |
15:15 | Using a Visual Abstract as a Lens for Communicating and Promoting Design Science Research in Software Engineering ( abstract ) |
15:30 | Member Checking in Software Engineering Research: Lessons Learned from an Industrial Case Study ( abstract ) |
15:45 | Investigating the Use of a Hybrid Search Strategy for Systematic Reviews ( abstract ) |
16:00 | Notifying and Involving Users in Experimentation: Ethical Perceptions of Software Practitioners ( abstract ) |
16:15 | Reporting Ethics Considerations in Software Engineering Publications ( abstract ) |
15:00 | Analysis of the understanding of the concepts of Task and Skill Variety by software engineering professionals ( abstract ) |
15:15 | Understanding the Heterogeneity of Contributors in Bug Bounty Programs ( abstract ) |
15:30 | Autonomy in Software Engineering: A Preliminary Study on the Influence of Education Level and Professional Experience ( abstract ) |
15:45 | Team Maturity in Software Engineering Teams ( abstract ) |
16:00 | Towards an Approach to Prevent Social Loafing in Software Development Teams ( abstract ) |
View this program: with abstractssession overviewtalk overview
Abstract: Researchers in software engineering must communicate with industry practitioners, both engineers and managers. Communication may be about collaboration buy-in, problem identification, empirical data collection, solution design, evaluation, and reporting. In order to gain mutual benefit of the collaboration, ensuring relevant research and improved industry practice, researchers and practitioners must be good at communicating. The basis for a researcher to be good at industry-academia communication is firstly to be “bi-lingual”. The terminology in each domain is often different and the number of TLA:s (Three Letter Abbreviations) in industry is overwhelming. Understanding and being able to translate between these “languages” is essential. Secondly, it is also about being “bi-cultural”.Understanding the incentives in industry and academia respectively, is a basis for being able to find balances between e.g. rigor and relevance in the research. Time frames is another aspect that is different in the two cultures. Thirdly, the choice of communication channels is key to reach the intended audience.A wide range of channels exist, from face to face meetings, via tweets and blogs, to academic journal papers and theses; each having its own audience and purposes. The keynote speech will explore the challenges of industry-academia communication, based on two decades of collaboration experiences, both successes and failures. It aims to support primarily the academic side of the communication to help achieving industry impact through rigorous and relevant empirical software engineering research.
Bio: Dr.Per Runeson is a professor of software engineering at Lund University, Sweden, Head of the Department of Computer Science, and the Leader of its Software Engineering Research Group (SERG) and the Industrial Excellence Center on Embedded Applications Software Engineering (EASE). His research interests include empirical research on software development and management methods, in particular for software testing and open innovation, and cross disciplinary topics on the digital society. He has contributed significantly to software engineering research methodology by the books on case studies and experimentation in software engineering.He serves on the editorial boards of Empirical Software Engineering and Software Testing, Verification and Reliability, and is a member of several program committees.
10:00 | Multi-objective regression test selection in practice: an empirical study in the defense software industry ( abstract ) |
10:30 | Estimating Energy Impact of Software Releases and Deployment Strategies: the KPMG Case Study ( abstract ) |
11:00 | Graphical vs. Tabular Notations for Risk Models: On the Role of Textual Labels and Complexity ( abstract ) |
11:30 | The Influence of Requirements in Software Model Development in an Industrial Environment ( abstract ) |
10:30 | An Industry Perspective to Comparing the SQALE and Quamoco Software Quality Models ( abstract ) |
11:00 | Formative Evaluation of a Tool for Managing Software Quality ( abstract ) |
11:30 | The Impact of Coverage on Bug Density in a Large Industrial Software Project ( abstract ) |
10:30 | Quantifying the Transition from Python 2 to 3: An Empirical Study of Python Applications ( abstract ) |
11:00 | Which Version Should be Released to the App Store? ( abstract ) |
11:30 | Mining Logs to Model the Use of a System ( abstract ) |
13:00 | File-Level Defect Prediction: Unsupervised vs. Supervised Models ( abstract ) |
13:30 | Training data selection for cross-project defection prediction: which approach is better? ( abstract ) |
14:00 | The Significant Effects of Data Sampling Approaches on Software Defect Prioritization and Classification ( abstract ) |
13:00 | Eliciting Strategies for the GQM+Strategies Approach in IT Service Measurement Initiatives ( abstract ) |
13:30 | Looking for Peace of Mind? Manage your (Technical) Debt - An Exploratory Field Study ( abstract ) |
14:00 | Characterizing Software Engineering Work with Personas Based on Knowledge Worker Actions ( abstract ) |
13:00 | Common Bug-fix Patterns: A Large-Scale Observational Study ( abstract ) |
13:30 | (Journal First) Towards an understanding of change types in bug fixing code ( abstract ) |
14:00 | Mining Version Control System for Automatically Generating Commit Comment ( abstract ) |
15:00 | House of Cards: Code Smells in Open-source C# Repositories ( abstract ) |
15:15 | How Does Machine Translated User Interface Affect User Experience? A Study on Android Apps ( abstract ) |
15:30 | An exploratory analysis of a hybrid OSS company's forum in search of sales leads ( abstract ) |
15:45 | On Software Productivity Analysis with Propensity Score Matching ( abstract ) |
15:00 | What the Job Market Wants from Requirements Engineers? An Empirical Analysis of Online Job Ads from the Netherlands ( abstract ) |
15:15 | Agile Quality Requirements Engineering Challenges: First Results from a Case Study ( abstract ) |
15:30 | Issues and Opportunities for Human Error-based Requirements Inspections: An Exploratory Study ( abstract ) |
15:45 | Assessing the Intuitiveness of Qualitative Contribution Relationships in Goal Models: an Exploratory Experiment ( abstract ) |
15:00 | Identifying Software Decays: A System Usage Perspective ( abstract ) |
15:00 | An Empirical Study of Open Source Virtual Reality Software Projects ( abstract ) |
15:00 | Beyond Boxes and Lines: Designing and Evaluating Alternative Visualizations for Requirements Conceptual Models ( abstract ) |
15:00 | A Comparison of Dictionary Building Methods for Sentiment Analysis in Software Engineering Text ( abstract ) |
15:00 | Structured Synthesis Method: the Evidence Factory Tool ( abstract ) |