A common architecture for TPS development

Alan Irwin; Joe La Veigne; Brian Nehring

doi:10.1117/12.887297

Translator Disclaimer

9 May 2011 A common architecture for TPS development

Alan Irwin, Joe La Veigne, Brian Nehring

Author Affiliations +

Proceedings Volume 8014, Infrared Imaging Systems: Design, Analysis, Modeling, and Testing XXII; 801417 (2011) https://doi.org/10.1117/12.887297
Event: SPIE Defense, Security, and Sensing, 2011, Orlando, Florida, United States

Abstract

Test Program Set (TPS) software development for Electro-Optical (EO) testing has traditionally been an expensive and lengthy process. A major cause of this has been the development of new test executive software on an ad hoc basis for each program. Furthermore, there have typically been different needs for production versus lab environments with production needing a set of standard tests, while users in a lab environment requiring the capability to modify certain aspects of their tests as needed. At Santa Barbara Infrared, a new architecture for TPS development has been engineered that addresses these concerns. The new architecture can host a complete TPS development environment that eliminates the need for a separate test executive. It supports EO testing in both engineering development and production testing through the use of user editable test scripts along with distinct user accounts and privileges. The new architecture is unit under test (UUT) centric, allowing a user to define UUT parameters once and easily share the results between tests. In this article we will review the new architecture and give examples of TPS development under that architecture.

Citation Download Citation

Alan Irwin, Joe La Veigne, and Brian Nehring "A common architecture for TPS development", Proc. SPIE 8014, Infrared Imaging Systems: Design, Analysis, Modeling, and Testing XXII, 801417 (9 May 2011); https://doi.org/10.1117/12.887297

ACCESS THE FULL ARTICLE