1. The Simplified TPS Encoding Process
- Author
-
Nicholas Herbert, Casey Bynum, Jacob Spencer, Mark Oblander, and Ngai Nguyen
- Subjects
Source code ,business.industry ,Interface (Java) ,Programming language ,Process (engineering) ,Computer science ,Plain text ,media_common.quotation_subject ,computer.file_format ,Software maintenance ,computer.software_genre ,Modularity ,Automatic test equipment ,Software engineering ,business ,Automatic programming ,computer ,media_common - Abstract
The process of TPS development is an increasingly complicated endeavor. As Units Under Test become more and more complex, a greater investment of time for analysis and simulation is required than ever before. Additionally, traditional TPS software development environments are monolithic, necessitating costly training time for the engineer to learn the environment as well as forcing tedious and difficult development interfaces on the engineer. The Simplified TPS Encoding Process (STEP), developed by the 76 SMXG at Tinker AFB, is a novel process for the development of TPSs that removes dependency on specific programming languages from the TPS engineer. STEP reduces the up-front time required to train new engineers and provides the TPS engineer with an easy-to-use development environment that can be modularly extended to work with any programming language or hardware interface. In addition, STEP uses plain text files to contain program code and store data results. The ease-of-use, modularity, and plain text source code provided by STEP result in the TPS engineer spending more time analyzing the Unit Under Test instead of spending that time struggling to develop in a particular programming language.
- Published
- 2009
- Full Text
- View/download PDF