By Topic

A lean approach to designing for software testability

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

4 Author(s)
Anthony L. Alwardt ; The Boeing Company, P.O. Box 516, M/C 034-3366, St. Louis, MO, 63156, USA ; Nathan Mikeska ; Richard J. Pandorf ; Philip R. Tarpley

It is common practice for military hardware to be designed for testability; however, the testability of software is rarely considered. When software testability is addressed, the resultant design often does not readily support full coverage automated testing. Since software products must be tested to verify requirements are met, it only makes sense to consider software testability from day one of a project. Once the decision has been made to embrace the concept of designing testable software, there are best practices that enable a lean software development process. This paper will discuss 1) designing for software testability; 2) the automated software regression testing approach; 3) the correlation to Extreme Programming (XP); 4) Lean 123 costs and benefits; 5) an example of how to create an automated software regression test; and 6) the applicability of this approach to all software efforts.

Published in:


Date of Conference:

14-17 Sept. 2009