Understanding software development: Processes, organisations and technologies

Our primary goal is to understand what people do when they develop software and how long it takes them to do it. To get a proper perspective on software development processes we must study them in their context — that is, in their organizational and technological context. An extremely important means of gaining the needed understanding and perspective is to measure what goes on. Time and motion studies constitute a proven approach to understanding and improving any engineering processes. We believe software processes are no different in this respect; however, the fact that software development yields a collaborative intellectual, as opposed to physical, output calls for careful and creative measurement techniques. In attempting to answer the question "what do people do in software development? " we have experimented with two novel forms of data collection in the software development field: time diaries and direct observation. We found both methods to be feasible and to yield useful information about time utilization. In effect, we have quantified the effect of these social processes using the observational data. Among the insights gained from our time diary experiment are 1) developers switch between developments to minimize blocking and maximize overall throughput, and 2) there is a high degree of dynamic reassignment in response to changing project and organizational priorities. Among the insights gained from our direct observation experiment are 1) time diaries are a valid and accurate instrument with respect to their level of resolution, 2) unplanned interruptions constitute a significant time factor, and 3) the amount and kinds of communication are significant time and social factors.- 2-1

Deltoid, triceps, or both responses improve the success rate of the interscalene catheter surgical block compared with the biceps response

Background The influence of the muscular response elicited by neurostimulation on the success rate of interscalene block using a catheter (ISC) is unknown. In this investigation, we compared the success rate of ISC placement as indicated by biceps or deltoid, triceps, or both twitches. Methods Three hundred (ASA I-II) patients presenting for elective arthroscopic rotator cuff repair were prospectively randomized to assessment by biceps (Group B) or deltoid, triceps, or both twitches (Group DT). All ISCs were placed with the aid of neurostimulation. The tip of the stimulating needle was placed after disappearance of either biceps or deltoid, triceps, or both twitches at 0.3 mA. The catheter was advanced 2-3 cm past the tip of the needle and the block was performed using 40 ml ropivacaine 0.5%. Successful block was defined as sensory block of the supraclavicular nerve and sensory and motor block involving the axillary, radial, median, and musculocutaneous nerves within 30 min. Results Success rate was 98.6% in Group DT compared with 92.5% in Group B (95% confidence interval 0.01-0.11; P<0.02). Supplemental analgesics during handling of the posterior part of the shoulder capsule were needed in two patients in Group DT and seven patients in Group B. Three patients in Group B had an incomplete radial nerve distribution anaesthesia necessitating general anaesthesia. One patient in Group B had an incomplete posterior block extension of the supraclavicular nerve. No acute or late complications were observed. Conclusions Eliciting deltoid, triceps, or both twitches was associated with a higher success rate compared with eliciting biceps twitches during continuous interscalene bloc

Dynamic and quantitative evaluation of degenerative mitral valve disease: A dedicated framework based on cardiac magnetic resonance imaging

Background: Accurate quantification of mitral valve (MV) morphology and dynamic behavior over the cardiac cycle is crucial to understand the mechanisms of degenerative MV dysfunction and to guide the surgical intervention. Cardiac magnetic resonance (CMR) imaging has progressively been adopted to evaluate MV pathophysiology, although a dedicated framework is required to perform a quantitative assessment of the functional MV anatomy. Methods: We investigated MV dynamic behavior in subjects with normal MV anatomy (n=10) and patients referred to surgery due to degenerative MV prolapse, classified as fibro-elastic deficiency (FED, n=9) and Barlow's disease (BD, n=10). A CMR-dedicated framework was adopted to evaluate prolapse height and volume and quantitatively assess valvular morphology and papillary muscles (PAPs) function over the cardiac cycle. Multiple comparison was used to investigate the hallmarks associated to MV degenerative prolapse and evaluate the feasibility of anatomical and functional distinction between FED and BD phenotypes. Results: On average, annular dimensions were significantly (P < 0.05) larger in BD than in FED and normal subjects while no significant differences were noticed between FED and normal. MV eccentricity progressively decreased passing from normal to FED and BD, with the latter exhibiting a rounder annulus shape. Over the cardiac cycle, we noticed significant differences for BD during systole with an abnormal annular enlargement between mid and late systole (LS) (P < 0.001 vs. normal); the PAPs dynamics remained comparable in the three groups. Prolapse height and volume highlighted significant differences among normal, FED and BD valves. Conclusions: Our CMR-dedicated framework allows for the quantitative and dynamic evaluation of MV apparatus, with quantifiable annular alterations representing the primary hallmark of severe MV degeneration. This may aid surgeons in the evaluation of the severity of MV dysfunction and the selection of the appropriate MV treatment

A Review of Software Inspections

For two decades, software inspections have proven effective for detecting defects in software. We have reviewed the different ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost-effectiveness of different methods. We detect a disturbing pattern in the evaluation of inspection methods. Although there is universal agreement on the effectiveness of software inspection, their economics are uncertain. Our examination of several empirical studies leads us to conclude that the benefits of inspections are often overstated and the costs (especially for large software developments) are understated. Furthermore, some of the most influential studies establishing these costs and benefits are 20 years old now, which leads us to question their relevance to today's software development processes. Extensive work is needed to determine exactly how, why, and when software inspections work, and whether some defect detection techniques might be more cost-effective than others. In this article we ask some questions about measuring effectiveness of software inspections and determining how much they really cost when their effect on the rest of the development process is considered. Finding answers to these questions will enable us to improve the efficiency of software development. (Also cross-referenced as UMIACS-TR-95-104

Transparency and (no) more in the Political Advertising Regulation

The EU has taken its first steps into a sensitive space by proposing a new Regulation on Political Advertising (RPA). Simply put, the RPA does two things, which this commentary will address in turn. First, it replaces national laws on the transparency of political advertising with a single set of rules. These provide progressively more information to citizens who see an ad, to the public through ad libraries, and to regulators and private actors who are authorised to request information. Second, the RPA tightens the GDPR’s ban on using sensitive data for targeted political advertising. It leaves member states free, however, to further regulate the use of political advertising.The RPA takes a number of important steps in political advertising law. It strengthens the transparency of the (so far largely unregulated) online political advertising environment. It expands ad libraries with information on targeting and funding. And it allows a broad range of private actors (including civil society and journalists) to request data from a broad range of companies (including ad agencies and small platforms). At the same time, the RPA not only represents the EU’s most significant effort to address concerns about political advertising’s democratic impact, but (because it fully harmonises transparency) also shapes how individuals, researchers, and national regulators can scrutinise political advertising. It is therefore important to determine whether the regulation lives up to the Commission’s hype

An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development

We are conducting a long-term experiment (in progress) to compare the costs and benefits of several different software inspection methods. These methods are being applied by professional developers to a commercial software product they are currently writing. Because the laboratory for this experiment is a live development effort, we took special care to minimize cost and risk to the project, while maximizing our ability to gather useful data. This article has several goals: (1) to describe the experiment's design and show how we used simulation techniques to optimize it, (2) to present our preliminary results and discuss their implications for both software practitioners and researchers, and (3) to discuss how we expect to modify the experiment in order to reduce potential risks to the project. For each inspection we randomly assign 3 independent variables: (1) the number of reviewers on each inspection team (1, 2 or 4), (2) the number of teams inspecting the code unit (1 or 2), and (3) the requirement that defects be repaired between the first and second team's inspections. The reviewers for each inspection are randomly selected without replacement from a pool of 11 experienced software developers. The dependent variables for each inspection include inspection interval (elapsed time), total effort, and the defect detection rate. To date we have completed 34 of the planned 64 inspections. Our preliminary results challenge certain long-held beliefs about the most cost-effective ways to conduct inspections and raise some questions about the feasibility of recently proposed methods. (Also cross-referenced as UMIACS-TR-95-14