MPD 575 Design for Testability. Jonathan Weaver. Development History. This material was prepared by Cohort 3 students in the Fall of 2002: Ron Anger Jim Gregoire Guillermo Jimenez Bob Ognjanovski Rob Spinks. Need for Testing. High Complexity Mass Production
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
“ Testing is painful, Not Testing is suicidal.”
The IEEE Standard Glossary of Software Engineering Terminology (1990) defines testability as:
"(1) the degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met, and (2) the degree to which a requirement is stated in terms that permit establishment of test criteria and performance of tests to determine whether those criteria have been met."
Test Coverage (%)
Number of Test Steps
B= Design made without Testability
in mind by a good fault coverage due
to large effort in making test steps
C=Design very difficult to test
A=Design done with testability in mind
Four Levels of testing
The IEEE Standard Glossary of Software Engineering Terminology (1990) defines software verification to be the
“Process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase."
Software testability can be defined as “the probability that a piece of software will fail on its next execution during testing (with a particular assumed input distribution) if the software includes a fault.”
SOFT (degraded performance to an unacceptable level)
HARD (product function ceases)
http://www.teamqsi.com/: Qualtech System Inc WEB Page.
Electronic News: Decreasing the Cost of Testing with Automatic Test Pattern Generation
Integrated Diagnostics Toolset. IEEE Autotest Conference (1997).
Integrated Process for Fault Diagnosis. IEEE Aerospace Conference (1999).
S. Deb, K.R. Pattipati, V. Raghavan, M. Shakeri, and R. Shrestha, “Multi-signal Flow Graphs: A Novel Approach for System Testability Analysis and Fault Diagnosis,” IEEE Aerospace and Electronics Magazine, May 1995, pp. 14-25. (Winner of the Best Technical Paper Award at the 1994 IEEE AUTOTEST Conference, Anaheim, CA, September 1994).
IEEE Standard Glossary of Software Engineering Terminology (1990)