The Integrated Functional Tests (JET) Approach

Abstract

In today's Space industry the role of the verification and validation (V&V) process has taken center stage. This is primarily due to the fact that in the ever more competitive market where the reality of harsh competitive conditions forces projects to cut down time to market, the systems engineer's job of fully verifying and validating the integrity of the system has become an almost "impossible mission". We are well aware of the fact that no project is going to suddenly spend time and money, in order to ease the systems engineer's mind and add more tests so as to enable him to fully validate and verify the system. Hence we offer a new and slightly modified V&V plan, such that will enable the system's engineer to actually fully validate and verify the system while taking into consideration his minimal and dwindling resources. This approach has it's roots in what is known in the industry as the IFT (Integrated Functional Testing), where the functionality of the fully integrated system is tested. The testing is performed against a testing matrix which is a combination of the requirements matrix and the system's software capabilities. The approach is based on the theory that the requirements matrix does not encompass the entire functionality of the system, and hence there might be some capabilities which shall not be tested if we adhere only to it (traditional approach). Here comes the mapping of the system's capabilities as implemented in the system's software to the rescue. We believe that the entire functionality of the system is implemented in and by the software. Hence, if we perform the V&V against the system requirements (Top level) and the system's software capabilities (Bottom level) we assure that the entire system's functionality and capability shall be tested. Furthermore this approach takes a different perspective in the creation of the V&V scenarios. The premise is that building system V&V scenarios from nominal system operation, hence most probable activities will confirm that most of the requirements are fulfilled and checked. A set of "Themes" for the V&V scenarios are created from the perspective of the OPERATOR daily operation. Further "themes" are then added to the V&V plan, but always from the OPERATOR aspect and not of the DEVELOPER. The IFT approach as presented in this paper was developed during the Integration of AMOS-1 (1995 to 1996), developed during the integration of AMOS-2 (2003) and further evolved to incorporate the LEO family (OFEQ) V&V heritage. During the integration of TECSAR (today).