DeepSoft: A vision for a deep model of software

Although software analytics has experienced rapid growth as a research area, it has not yet reached its full potential for wide industrial adoption. Most of the existing work in software analytics still relies heavily on costly manual feature engineering processes, and they mainly address the traditional classification problems, as opposed to predicting future events. We present a vision for \emph{DeepSoft}, an \emph{end-to-end} generic framework for modeling software and its development process to predict future risks and recommend interventions. DeepSoft, partly inspired by human memory, is built upon the powerful deep learning-based Long Short Term Memory architecture that is capable of learning long-term temporal dependencies that occur in software evolution. Such deep learned patterns of software can be used to address a range of challenging problems such as code and task recommendation and prediction. DeepSoft provides a new approach for research into modeling of source code, risk prediction and mitigation, developer modeling, and automatically generating code patches from bug reports.Comment: FSE 201

Resolving retention polarity: the perceptions of structural steel fabricators

This study aims to understand the perceived polarity between main contractors and subcontractors with a view to resolving problems connected with retentions in an environment where a sliding-retention regime is utilised with a retention rate of 10% for work below NZ $ 200,000. Eight structural steel subcontractors operating in Auckland were interviewed. Contrary to popular belief, subcontractors are not averse to retentions with most taking a middle ground. Nevertheless, the apparently fair practice of using back-to-back contract terms is not seen as fair and reasonable. Most solutions acceptable to subcontractors impact negatively on contractors’ cash flow highlighting the need for some form of reciprocity from subcontractors (price discounts, improved performance, etc.) to induce contractors to offer favourable retention regimes. This highlights the need for a theory on ‘retention reciprocity’ to supplement the five theories on retentions. However, given that not all contractors can be expected to display reciprocity fairness, an interventionist approach may be necessary in order to neutralise any imbalances in power between the contracting parties possibly through amendments to the Construction Contracts Act, and when doing so, there is a need to exercise much caution as the outcome of chaotic systems could be quite unpredictable

Definition of the on-time delivery indicator in rapid software development

Rapid software development (RSD) is an approach for developing software in rapid iterations. One of the critical success factors of an RSD project is to deliver the product releases on time and with the planned features. In this paper, we elaborate an exploratory definition of the On-Time Delivery strategic indicator in RSD based on the literature and interviews with four companies. This indicator supports decision-makers to detect development problems in order to avoid delays and to estimate the additional time needed when requirements, and specifically quality requirements, are considered.Peer ReviewedPostprint (author's final draft

Is It Safe to Uplift This Patch? An Empirical Study on Mozilla Firefox

In rapid release development processes, patches that fix critical issues, or implement high-value features are often promoted directly from the development channel to a stabilization channel, potentially skipping one or more stabilization channels. This practice is called patch uplift. Patch uplift is risky, because patches that are rushed through the stabilization phase can end up introducing regressions in the code. This paper examines patch uplift operations at Mozilla, with the aim to identify the characteristics of uplifted patches that introduce regressions. Through statistical and manual analyses, we quantitatively and qualitatively investigate the reasons behind patch uplift decisions and the characteristics of uplifted patches that introduced regressions. Additionally, we interviewed three Mozilla release managers to understand organizational factors that affect patch uplift decisions and outcomes. Results show that most patches are uplifted because of a wrong functionality or a crash. Uplifted patches that lead to faults tend to have larger patch size, and most of the faults are due to semantic or memory errors in the patches. Also, release managers are more inclined to accept patch uplift requests that concern certain specific components, and-or that are submitted by certain specific developers.Comment: In proceedings of the 33rd International Conference on Software Maintenance and Evolution (ICSME 2017

Hogan vs. Gawker II: A Statutory Solution to Fraudulent Joinder

This Article will first review the intersection of federal jurisdiction and litigation strategy by examining the requirements for diversity jurisdiction in federal court as well as the circumstances that must be present to allow a defendant to remove a case from state court to federal court. The Article will then review the history of the court-created doctrine of fraudulent joinder, and will examine the various tests currently in use by the lower federal courts. The Article will then address whether it makes more sense to create a statutory solution, and will examine and analyze the Fraudulent Joinder Prevention Act of 2016, which was recently passed by the House of Representatives. After analyzing the Act, this Article will conclude that, while a statutory solution to this issue is appropriate, the current proposal needs to be adjusted in various ways

The Fire and Smoke Model Evaluation Experiment—A Plan for Integrated, Large Fire–Atmosphere Field Campaigns

The Fire and Smoke Model Evaluation Experiment (FASMEE) is designed to collect integrated observations from large wildland fires and provide evaluation datasets for new models and operational systems. Wildland fire, smoke dispersion, and atmospheric chemistry models have become more sophisticated, and next-generation operational models will require evaluation datasets that are coordinated and comprehensive for their evaluation and advancement. Integrated measurements are required, including ground-based observations of fuels and fire behavior, estimates of fire-emitted heat and emissions fluxes, and observations of near-source micrometeorology, plume properties, smoke dispersion, and atmospheric chemistry. To address these requirements the FASMEE campaign design includes a study plan to guide the suite of required measurements in forested sites representative of many prescribed burning programs in the southeastern United States and increasingly common high-intensity fires in the western United States. Here we provide an overview of the proposed experiment and recommendations for key measurements. The FASMEE study provides a template for additional large-scale experimental campaigns to advance fire science and operational fire and smoke models