Please use this identifier to cite or link to this item:
https://dair.nps.edu/handle/123456789/487
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Valdis Berzins | |
dc.contributor.author | Paul Dailey | |
dc.date.accessioned | 2020-03-16T17:29:00Z | - |
dc.date.available | 2020-03-16T17:29:00Z | - |
dc.date.issued | 2009-04-01 | |
dc.identifier.citation | Published--Unlimited Distribution | |
dc.identifier.uri | https://dair.nps.edu/handle/123456789/487 | - |
dc.description | Acquisition Management / Grant-funded Research | |
dc.description.abstract | 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. | |
dc.description.sponsorship | Acquisition Research Program | |
dc.language | English (United States) | |
dc.publisher | Acquisition Research Program | |
dc.relation.ispartofseries | Open Architecture (OA) | |
dc.relation.ispartofseries | NPS-AM-09-022 | |
dc.subject | Open Architecture | |
dc.subject | Reducing Regression Testing | |
dc.subject | Automated Testing | |
dc.subject | Statistical Testing | |
dc.subject | Dependency Analysis | |
dc.subject | Reuse | |
dc.subject | Technology Upgrades | |
dc.title | How to Check If It Is Safe Not to Retest a Component | |
dc.type | Article | |
Appears in Collections: | Annual Acquisition Research Symposium Proceedings & Presentations |
Files in This Item:
File | Size | Format | |
---|---|---|---|
NPS-AM-09-022.pdf | 158.71 kB | Adobe PDF | View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.