This Article 
 Bibliographic References 
 Add to: 
Tests: The Architect's Best Friend
May/June 2011 (vol. 28 no. 3)
pp. 7-9
Frank Buschmann, Siemens Corporate Technology
When explicitly considering the testability of software-centric systems, architects tend to be more conscious and thoughtful about their design decisions. In this installment, the author discusses how architects can use tests and test-driven development as a tool for designing, to establish a continuous, immediate, and constructive feedback loop on architecture quality and usability. The goal is to avoid or discover architectural deficiencies before they're realized—when they're less costly to correct.

1. F. Buschmann, "Learning from Failure, Part 1: Scoping and Requirements Woes," IEEE Software, vol. 26, no. 6, 2009, pp. 68–69.
2. F. Buschmann, "Learning from Failure, Part 3: On Hammers and Nails, and Falling in Love with Technology," IEEE Software, vol. 27, no. 2, 2010, pp. 49–51.
3. F. Buschmann, "On Architecture Styles and Paradigms," IEEE Software, vol. 27, no. 5, 2010, pp.
4. P. Clements, R Kazman, and M. Klein, Evaluating Software Architectures, Addison-Wesley, 2002.
5. F. Buschmann, "Learning from Failure, Part 2: Featuritis, Performitis, and Other Diseases," IEEE Software, vol. 27, no. 1, 2010, pp. 10–11.
6. F. Buschmann, "Unusable Software Is Useless, Part 2," IEEE Software, vol. 28, no. 1, 2011, pp. 92–94.

Index Terms:
test-driven development, testability, design for testability
Frank Buschmann, "Tests: The Architect's Best Friend," IEEE Software, vol. 28, no. 3, pp. 7-9, May-June 2011, doi:10.1109/MS.2011.65
Usage of this product signifies your acceptance of the Terms of Use.