How to Check If It Is Safe Not to Retest a Component
MetadataShow full item record
This paper focuses on ways to reduce testing effort and costs associated with technology-advancement upgrades to systems with open architectures. This situation is common in Navy and DoD contexts such as submarine, aircraft carrier, and airframe systems, and accounts for a substantial fraction of the testing effort. This paper describes methods for determining when testing of unmodified components can be reduced or avoided, and it outlines some methods for choosing test cases efficiently to focus retesting where it is needed, given information about past testing of the same component. Changes to the environment of a system can affect its reliability, even if the behavior of the system remains unchanged. The new capabilities added by a technology upgrade can interact with previously existing capabilities, changing the frequency of their usage as well as the range of input values and, hence, changing their effect on overall system reliability.
Proceedings Paper (for Acquisition Research Program)Approved for public release; distribution unlimited.
NPS Report NumberNPS-AM-09-022
Showing items related by title, author, creator and subject.
Davis, Edward V., Jr. (Monterey, California: Naval Postgraduate School, 1990-12);Rapid prototyping is emerging as a promising software development paradigm. It provides a systematic and automatable means of developing a software system under circumstances where initial requirements are not well known ...
Eatinger, Christopher J. (Monterey, California. Naval Postgraduate School, 2007-06);Software testing is a crucial step in the development of any software system, large or small. Testing can reveal the presence of logic errors and other flaws in the code that could cripple the system's effectiveness. Many ...
Le, BeEm V. (Monterey, California. Naval Postgraduate School, 2009-12);Many U.S. Navy systems were built on the fly and have encountered interoperability problems at sea, such as erroneous dual/multiple track designations, misidentification/track identity conflicts, report responsibility ...