Creating an executable configuration

Abstract

The automatization unit used in current test stands is a central system in which various interfaces are connected with the individual test stand components. As a result, an inflexible system is created with limited scalability, as numerous changes are required in the automatization unit, for example, a new interface, processing of data from/to the component, integration into the existing system, etc. in order to integrate new components (SW and HW). This makes a change or an enhancement of the automatization unit, the implementation of specific customer requests or the integration of an external functionality very expensive. In order to solve this problem and primarily, to make a flexible easily scalable system possible it is proposed in accordance with the invention, to create an executable configuration that can be run on a target system by selecting from a library 20 a number of abstracted software components that are independent of the target system that implement individual functions of the target system and that are provided with a specified command interface 22 and a specified interface 21 to data channels are selected, the selected software components that are independent of the target system are interconnected via their data channels for the realization of the automatization task to a model 23, model 23 is automatically transformed by a model transformation into a net list 24 consisting of nodes, attributes and edges, whereby the software components form the nodes, the initial parameters the attributes and the data channels the edges of net list 24, the software components that are independent of the target system are transformed into software components dependent on the target system, the software components that are dependent on the target system are instantiated at the target system and parameterized by their command interface and from net list 24, the processing sequence of the software components is identified for processing in correct information flow.

Dependencies are inferred from the claim text.