On the Sustained Use of a Test-Driven Development Practice at IBM

@article{Sanchez2007OnTS,
  title={On the Sustained Use of a Test-Driven Development Practice at IBM},
  author={Julio Cesar Sanchez and Laurie A. Williams and E. Michael Maximilien},
  journal={Agile 2007 (AGILE 2007)},
  year={2007},
  pages={5-14}
}
Test-driven development (TDD) is an agile practice that is widely accepted and advocated by most agile methods and methodologists. [...] Key Result As a result, our data indicate that the TDD practice can aid in the production of high quality products. This quality improvement would compensate for the moderate perceived productivity losses. Additionally, our data indicates that the use of TDD may decrease the degree to which code complexity increases as software ages, as measured by cyclomatic complexity metric…Expand
Cost-Effectiveness of test-driven development
Test-Driven Development (TDD) is a software development practice in which test cases are written before code implementation. ISM eCompany, who specializes in web solutions, is adapting theirExpand
Long-Term Effects of Test-Driven Development A Case Study
TLDR
TDD has been found to improve the team confidence in the code quality and simplify significantly the software maintenance and is eager to continue improving the practice application. Expand
Factors Limiting Industrial Adoption of Test Driven Development: A Systematic Review
TLDR
A systematic literature review on empirical studies explicitly focusing on TDD as well as indirectly addressing TDD identified seven limiting factors viz., increased development time, insufficient TDD experience/knowledge, lack of upfront design, domain and tool specific issues, and legacy code. Expand
The effectiveness of test-driven development: an industrial case study
TLDR
The results indicate that the TDD developers produced higher quality code that is easier to maintain, although the productivity of the developers did observe a reduction in productivity. Expand
A Family of Experiments on Test-Driven Development
TLDR
The goal of this paper is to increase the accuracy and generalizability of the results achieved in isolated experiments on TDD, provide joint conclusions on the performance of TDD across different industrial and academic settings, and assess the extent to which the characteristics of the experiments affect the quality-related performance ofTDD. Expand
Obtaining better software product by using test first programming technique
  • Nidhi Agarwal, P. Deep
  • Engineering
  • 2014 5th International Conference - Confluence The Next Generation Information Technology Summit (Confluence)
  • 2014
Test driven development (TDD) is one of the basic practices of agile software development and wasproposed by Kent Beck. The developers produce automated unit tests first, even before writing theExpand
Continuous Test-Driven Development - A Novel Agile Software Development Practice and Supporting Tool
TLDR
In this article, the CTDD practice and the tool that is intended to use to support and evaluate theCTDD practice in a real world software development project are described and described. Expand
A brief report on working smarter with Agile software development
TLDR
A brief high-level overview and record of the adoption of these practices and methods across a large company, i.e., the IBM Corporation, is provided. Expand
A longitudinal cohort study on the retainment of test-driven development
TLDR
The use of TDD has a statistically significant effect neither on the external quality of software products nor on the developers' productivity, but it is observed that participants using TDD produced significantly more tests than those applying a non-TDD development process. Expand
A successful application of a Test-Driven Development strategy in the industrial environment
  • R. Latorre
  • Computer Science
  • Empirical Software Engineering
  • 2013
TLDR
The main conclusions drawn from this project are that ATDD contributes to clearly capture and validate the business requirements, but it requires an extensive cooperation from the customer; and that UTDD has not a significant impact neither on productivity nor on software quality. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 30 REFERENCES
An initial investigation of test driven development in industry
TLDR
It is found that the TDD developers produced higher quality code, which passed 18% more functional black box test cases, however, TDD developer pairs took 16% more time for development, which supports that TDD has the potential of increasing the level of testing in the industry. Expand
On the Influence of Test-Driven Development on Software Design
TLDR
Results from this study indicate that TDD can be an effective software design approach improving both code-centric aspects such as object decomposition, test coverage, and external quality, and developer-centric aspect including productivity and confidence. Expand
Test-driven development as a defect-reduction practice
TLDR
This case study found that the code developed using a test-driven development practice showed, during functional verification and regression tests, approximately 40% fewer defects than a baseline prior product developed in a more traditional fashion. Expand
Analysis and Quantification of Test Driven Development Approach
TLDR
This thesis is concerned with a set of structured TDD experiments on very small programs with pair programmers, where both student and professional TDD developers appear to achieve higher code quality, as measured using functional black box testing. Expand
Evaluating the efficacy of test-driven development: industrial case studies
TLDR
A significant increase in quality of the code is observed for projects developed using TDD compared to similar projects developed in the same organization in a non-TDD fashion. Expand
On agile performance requirements specification and testing
TLDR
An evolutionary model for performance requirements specifications and corresponding validation testing is proposed and a post hoc examination of a development effort at IBM that had a high focus on performance requirements is provided. Expand
Assessing test-driven development at IBM
TLDR
A non-trivial software system based on a stable standard specification is built using a disciplined, rigorous unit testing and build approach based on the test-driven development (TDD) practice, which reduces the defect rate by about 50 percent. Expand
A prototype empirical evaluation of test driven development
TLDR
An experiment was devised to investigate the distinction between test-driven development and traditional, test-last development from the perspective of developer productivity and software quality and indicates that while there is little or no difference in developer productivity in the two processes, there are differences in the frequency of unplanned test failures. Expand
The Economics of Software Development by Pair Programmers
Abstract Evidence suggests that pair programmers–two programmers working collaboratively on the same design, algorithm, code, or test–perform substantially better than the two would working alone.Expand
Evaluating advantages of test driven development: a controlled experiment with professionals
TLDR
The results suggest that TDD improves the unit testing but slows down the overall process, which is an alternative to the testing after coding (TAC), which is the usual approach to run and execute unit tests after having written the code. Expand
...
1
2
3
...