An ideal TPS relational analysis

The collection and analysis of Test Program Set (TPS) historical data has been a need for developers looking to reduce call-out and cost; and improve diagnostics test times. This paper will discuss the ideal TPS and runtime data required in order to reduce development cost and speed End to End (ETE) runtime by having a simple TPS results historic database. This historic database that we introduce is an alternative to Smart TPS.