Driving Software Quality and Structuring Work Through Test-Driven Development

Test-driven development is a software development method where programmers compose program code by first implementing a set of small-scale tests which help in the design of the system and in the verification of associated code sections. The reversed design and implementation process is unique: traditionally there is no attempt to verify program code that does not yet exist. Applying practices of test-driven design to a software development process-a generally complex activity involving distinct individuals working in an organization-might have an impact not only on the process itself but on the outcome of the process as well. In order to assess whether test-driven development has perceivable effects on elements of software development, a qualitative literature survey, based on empirical studies and experiments in the industry and academia, was performed. The aggregated results extracted from the studies and experiments on eleven different internal and external process, product and resource quality attributes indicate that there are positive, neutral and negative effects. Empirical evidence from the industry implies that test-driven development has a positive, reducing, effect on the number of defects detected in a program. There is also a chance that the code products are smaller, simpler and less complex than equivalent code products implemented without test-driven practices. While additional research is needed, it would seem that the test-driven produced code is easier for the developers to maintain later, too; on average, maintenance duties took less time and the developers felt more comfortable with the code. The effects on product attributes of coupling and cohesion, which describe the relationships between program code components, are neutral. Increased quality occasionally results in better impressions of the product when the test-driven conform better to the end-user tests but there are times when end-users cannot discern the differences in quality between products made with different development methods. The small, unit-level, tests written by the developers increase the overall size of code products since most of the program code statements are covered by the tests if a test-driven process is followed. Writing tests takes time and the negative effects are associated with the effort required in the process. Industrial case studies see negative implications to productivity due to the extra effort but student experiments have not always been able to replicate similar results under controlled conditions

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results: The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.Peer ReviewedPostprint (published version

Enablers and Impediments for Collaborative Research in Software Testing: An Empirical Exploration

When it comes to industrial organizations, current collaboration efforts in software engineering research are very often kept in-house, depriving these organizations off the skills necessary to build independent collaborative research. The current trend, towards empirical software engineering research, requires certain standards to be established which would guide these collaborative efforts in creating a strong partnership that promotes independent, evidence-based, software engineering research. This paper examines key enabling factors for an efficient and effective industry-academia collaboration in the software testing domain. A major finding of the research was that while technology is a strong enabler to better collaboration, it must be complemented with industrial openness to disclose research results and the use of a dedicated tooling platform. We use as an example an automated test generation approach that has been developed in the last two years collaboratively with Bombardier Transportation AB in Sweden

A Scientific Roadmap for Antibiotic Discovery: A Sustained and Robust Pipeline of New Antibacterial Drugs and Therapies is Critical to Preserve Public Health

In recent decades, the discovery and development of new antibiotics have slowed dramatically as scientific barriers to drug discovery, regulatory challenges, and diminishing returns on investment have led major drug companies to scale back or abandon their antibiotic research. Consequently, antibiotic discovery—which peaked in the 1950s—has dropped precipitously. Of greater concern is the fact that nearly all antibiotics brought to market over the past 30 years have been variations on existing drugs. Every currently available antibiotic is a derivative of a class discovered between the early 1900s and 1984.At the same time, the emergence of antibiotic-resistant pathogens has accelerated, giving rise to life-threatening infections that will not respond to available antibiotic treatment. Inevitably, the more that antibiotics are used, the more that bacteria develop resistance—rendering the drugs less effective and leading public health authorities worldwide to flag antibiotic resistance as an urgent and growing public health threat

Has Toxicity Testing Moved into the 21st Century? A Survey and Analysis of Perceptions in the Field of Toxicology.

BackgroundTen years ago, leaders in the field of toxicology called for a transformation of the discipline and a shift from primarily relying on traditional animal testing to incorporating advances in biotechnology and predictive methodologies into alternative testing strategies (ATS). Governmental agencies and academic and industry partners initiated programs to support such a transformation, but a decade later, the outcomes of these efforts are not well understood.ObjectivesWe aimed to assess the use of ATS and the perceived barriers and drivers to their adoption by toxicologists and by others working in, or closely linked with, the field of toxicology.MethodsWe surveyed 1,381 toxicologists and experts in associated fields regarding the viability and use of ATS and the perceived barriers and drivers of ATS for a range of applications. We performed ranking, hierarchical clustering, and correlation analyses of the survey data.ResultsMany respondents indicated that they were already using ATS, or believed that ATS were already viable approaches, for toxicological assessment of one or more end points in their primary area of interest or concern (26-86%, depending on the specific ATS/application pair). However, the proportions of respondents reporting use of ATS in the previous 12 mo were smaller (4.5-41%). Concern about regulatory acceptance was the most commonly cited factor inhibiting the adoption of ATS, and a variety of technical concerns were also cited as significant barriers to ATS viability. The factors most often cited as playing a significant role (currently or in the future) in driving the adoption of ATS were the need for expedited toxicology information, the need for reduced toxicity testing costs, demand by regulatory agencies, and ethical or moral concerns.ConclusionsOur findings indicate that the transformation of the field of toxicology is partly implemented, but significant barriers to acceptance and adoption remain. https://doi.org/10.1289/EHP1435

Improving performance through HEI–industry engagements in the built environment

The poor performance and inefficiencies of the construction industry are well recognized and documented. Through a variety of combined industry and government initiatives there has been a continual expression in the UK over the last decade of the urgent need to address the fragmented nature of the industry to improve its performance. A major challenge is for education and industry stakeholders to create closer and more effective relationships with each other to facilitate greater mutual understanding. ‘Accelerating Change in Built Environment Education’ (ACBEE) is a sponsored initiative designed to encourage the closer working together of industry, education and professional bodies to provide more relevant training and education. This paper introduces ACBEE, along with an evaluation framework for measuring the performance of engagements at various levels. This is followed by an analysis of the application of this performance measurement framework through case studies of industry–education engagement. A number of case studies were identified as operating at the grades of ‘strategic alliance’ and ‘partnership’ (as classified in the ACBEE evaluation framework). The analysis of these cases focuses on the drivers behind and the purpose of the engagement, and how these are aligned with the business strategy of the collaborating organizations and measurement of the activity. Evidence of meeting the explicit business needs and strategic objectives and the contribution to good practice knowledge are also discussed

Open plan and academe: pre- and post-hoc conversations

There now exists a strong body of evidence that creative workplaces can, in certain circumstances, exert beneficial influences on organisational cultures and outputs. Academia tends to resist such spaces and faculty buildings. The reasons are explored but the reactions of staff are not found to be different from those reported in the literature on general creative spaces. The success or failure of team oriented workspaces is in large part a socially constructed perception influenced by the manner of implementation and management. As elsewhere new workplaces are about new conversations. The cases studied lead to a model of the tensions inherent in workplace redesign.</p