J. Voas, K. Miller, and J. Payne. PISCES: A tool for predicting software testability. In Proceedings of the Symposium on Assessment of Quality BIBLIOGRAPHY 85 Software Development Tools, pages 297--309. IEEE Computer Society, May 1992. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
An Approach to Identifying and Understanding.. - Kapfhammer.. (2000) (1 citation) (Correct)
....not reasonable to use black box behavioral specifications to determine which COTS components in a candidate system might behave anomalously. Another approach to finding problematic COTS components and understanding their anomalous actions relies upon source access. Software testability analysis [16] and software component dependability assessment [14] could be used to measure different aspects of COTS component quality. Software testability analysis employs a white box, dynamic, failure based approach to component assessment. Instead of attempting to reveal the existence of faults, ....
Jeffrey M. Voas, Keith W. Miller, and Jeffrey E. Payne. Pisces: A tool for predicting software testability. In Proceedings of the Symposium on Assessment of Quality Software Development Tools, pages 297--309, New Orleans, LA, May 1992. IEEE Computer Society. 11
The VOCAL Test Methodology - Pemberton (1998) (Correct)
....inclusion of test scaffolding in the program unit. Observability relates to how that specific input sequence manifests itself as output from the program component. Improvement of both these factors will increase overall software testability. Voas [Voas, 92] describes a technique and tool support [Voas et al. 92] for the automated discovery of low testability program code. Such a method is particularly useful as it can point towards sections of code that are difficult to test, so that they may be reviewed, or redesigned to help improve reliability. This technique is particularly valuable during the ....
VOAS, J.; MILLER, K., and PAYNE, J.: "PISCES: A Tool For Predicting Software Testability" Proceedings of the Symposium On Assessment of Quality Software Development Tools, May 1992, New Orleans, LA, USA, pp. 297 - 309
An Empirical Comparison of a Dynamic Software Testability.. - Voas, Miller, Payne Self-citation (Voas Miller Payne) (Correct)
....and the program counter) Thus an assignment statement, if, and while statement define a location. The probability of execution for each location is determined by repeated executions of the code with inputs selected at random from the input distribution. An automated testability system, PiSCES [11], controls the instrumentation and bookkeeping. If a location contains a fault, and if the location is executed, the data state after the fault may or may not be changed adversely by the fault. If the fault does change the data state into an incorrect data state, we say the data state is infected. ....
J. VOAS, K. MILLER, AND J. PAYNE. PISCES: A Tool for Predicting Software Testability. In Proc. of the Symp. on Assessment of Quality Software Development Tools, pages 297--309, New Orleans, LA, May 1992. IEEE Computer Society TCSE.
Testability of Object-Oriented Systems: a Metrics-based Approach - Bruntink (Correct)
No context found.
J. Voas, K. Miller, and J. Payne. PISCES: A tool for predicting software testability. In Proceedings of the Symposium on Assessment of Quality BIBLIOGRAPHY 85 Software Development Tools, pages 297--309. IEEE Computer Society, May 1992.
Testability of Object-Oriented Systems: a Metrics-based Approach - Bruntink (2003) (Correct)
No context found.
J. Voas, K. Miller, and J. Payne. PISCES: A tool for predicting software testability. In Proceedings of the Symposium on Assessment of Quality BIBLIOGRAPHY 85 Software Development Tools, pages 297--309. IEEE Computer Society, May 1992.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC