CONFIGURATION DEVICE FOR THE GRAPHICAL CREATION OF A TEST SEQUENCE

Abstract

A configuration device for the graphical creation of at least one test sequence for controlling a test device having at least one electronic computer. The test device is controllable according to the created test sequence. The configuration device has at least one display device, graphical library functional elements being displayed with the display device in a library field. The test sequence can be created by placing at least one instance of a library functional element in a configuration field. The instance of a library functional element is placed in the configuration field. The graphical library functional element can be provided with a function placeholder, whereby the function placeholder in the instance of the library functional element can be provided with an instance functionality, whereby the reference of the instance of the library functional element to the library functional element is retained.

Description

This nonprovisional application claims priority under 35 U.S.C. §119(a) to European Patent Application No. EP11004526.7, which was filed on Jun. 3, 2011, and which is herein incorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to a configuration device for the graphical creation of at least one test sequence for controlling a test device having at least one electronic computer unit, whereby the test device can be controlled according to the created test sequence, whereby the configuration device has at least one display device, graphical library functional elements being displayed with the display device in a library field, whereby the test sequence can be created by placing at least one instance of a library functional element in a configuration field, whereby the instance of a library functional element, said instance being placed in the configuration field, references the library functional element itself.

2. Description of the Background Art

Configuration devices are known from the conventional art and are used as a technical tool in order to selectively address and control a test device (e.g., “AutomationDesk 3.2, Test and Experiment Software”, Product Description, dSPACE 2011). The test device typically is a high-performance simulation computer, which often has a number of electronic computer units and assigned I/O devices, whereby a device-under-test, such as, e.g., a control device, is connected to the test device; this corresponds to a typical structure of a hardware-in-the-loop system.

The test sequence is a selective control of the test device and the I/O components typically comprising the test device, so that the device-under-test connected to the test device is supplied with specific signals. The response of the device-under-test to the stimulation is then also determined with the test device with the use of measurement techniques and compared with the expected behavior, so that it can be determined whether the device-under-test behaves as desired. Frequently, the test device is equipped with a real-time-capable operating system, so that the time response of the test sequence can also be predefined and the time response of the connected device-under-test can be evaluated.

As in other fields, graphical programming has proven extremely useful for the creation of test sequences as well, whereby this is understood to be the description of the test sequence by block diagrams. The sequence of test events is described by a series of functional elements depicted as blocks.

The configuration device can be implemented in a computer different from the test device and be connected to the test device only via a data connection. It is then possible that the created test sequence is carried out in the configuration device itself and the test device is provided only with corresponding instructions for carrying out the test sequence. It is possible equally well that the graphically created test sequence is converted into an executable program with the aid of the configuration device and this program is run on the test device. It is also possible that the configuration device and the test device coincide in terms of equipment; the precise device-related configuration is not relevant in the present case. Configuration devices known from the state of the art typically have a basic configuration of functions, which can be used during the creation of a test sequence; this basic configuration consists of libraries of graphical functional elements. Examples of such library functional elements are a loop functionality (for/while) or a conditional functionality (if-then-else); also important are corresponding library functional elements, which represent the test device, so that the test device is accessible in terms of hardware via the test sequence.

The aforementioned libraries are not necessarily predefined; such libraries can also be created by the user of the configuration device.

In the graphical creation of a test sequence, the typical approach is to select a graphical library functional element from a library shown in a library field and to place the selected graphical library functional element in a configuration field (“drag-and-drop”). The library functional element placed in the configuration field is not the library functional element of the library itself, but an instance of the graphical library functional element, whereby this instance is connected to the library functional element, in other words, references the library functional element. This means that a subsequent change in the library functional element within the library also has an effect on the instances of this graphical library functional element in the test sequence in which instances of the library functional element are used.

When the instance of a library functional element is to be changed within a test sequence, then this is only possible in that the reference to the library functional element is no longer used and the test sequence receives a copy of the library functional element instead of the reference in the library. In fact, this (modified) copy of the functional element can then be defined again as a library functional element, but this has the consequence that the functional element libraries increase constantly, even if only minor variations of existing functional elements are created. It is disadvantageous here that desired changes of a basic functionality, which is the same in all functional elements, either must occur locally in different test sequences, when there is no longer a reference to the library element, or, the change must be made in each different version of the library functional element, which is also work-intensive.

The work with possibly only very slightly different versions of a library functional element or of copies of these functional elements in test sequences can be worked around in the state of the art only in that a comprehensive library functional element covers all existing versions, whereby there is the risk, however, that a poorly understandable functional structure arises, which contains a complicated case control for the differentiation and selective activation of function modifications.

SUMMARY OF THE INVENTION

It is therefore an object of the present invention to provide a configuration device for the graphical creation of a test sequence, the device enables an improved management and implementation of function modifications in instances of graphical library functional elements.

The configuration device is attained in an embodiment, in that the graphical library functional element can be provided with a function placeholder, whereby the function placeholder in the instance of the library functional element can be provided with an instance functionality, whereby the reference of the instance of the library functional element to the library functional element is retained. It is therefore possible to provide in a graphical library functional element a place that enables individualization of an instance of this graphical library functional element, namely, in that an individual functionality of the instance—the instance functionality—is stored in the place of the function placeholder. This measure makes it possible to realize different versions of a library functional element, whereby the common functionality of all versions or all instances of the library functional element can be changed centrally at one place, namely, in the graphical library functional element itself. The instance functionality of each instance of the graphical library functional element must or should be stored only in an appropriate place such as in a file that contains the corresponding test sequence.

In an embodiment of the configuration device, it is provided that a test sequence created in the configuration field or a partial test sequence can be defined as a library functional element, so that graphical library functional elements can be created that already have a function placeholder.

In another embodiment of the configuration device of the invention, it is provided that in a reduced display of the instance of a graphical library functional element with a function placeholder, only the function placeholder is shown. This is advantageous, because the attention of the user of the configuration device is directed immediately also to the possibility of storing an instance functionality and the—perhaps very extensive—predefined and invariable functionality of the library functional element is moved into the background.

In an embodiment of the configuration device, function placeholders can be used within function placeholders, so that even when by defining an instance functionality and subsequent derivation of a new library functional element from the functional element, individualized in part in each case, a new library functional element results, the new library functional element in turn having a function placeholder.

It is likewise possible to provide a functional element individualized via an instance functionality over and over again with a function placeholder, so that also over generations of library functional elements the possibility of individualizing a functional element by defining an instance functionality is retained; the function placeholder can be used virtually recursively.

In an embodiment of the configuration device, the different versions of the instance functionality of the function placeholder of a graphical library functional element can be determined and displayed in the display device. The configuration device is therefore capable of recognizing different versions—in one test sequence or also from a number of test sequences—of the instance functionality in instances of a graphical library functional element and displaying them to the user, so that a rapid overview of the function versions can be obtained. This is advantageous primarily in association with the configuration device, in which the function placeholder of an instance of a library functional element can be assigned an already existing version of the instance functionality of the function placeholder. This works out especially simply, when the different versions of the instance functionality are shown and a version can be selected and becomes the instance functionality of the instance of the library functional element in question.

Further scope of applicability of the present invention will become apparent from the detailed description given hereinafter. However, it should be understood that the detailed description and specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will become more fully understood from the detailed description given hereinbelow and the accompanying drawings which are given by way of illustration only, and thus, are not limitive of the present invention, and wherein:

FIG. 1 shows a configuration device with a configuration field;

FIGS. 2a-2d show a graphically created test sequence;

FIG. 3 shows an exemplary embodiment of a graphical library functional element provided with a function placeholder;

FIG. 4 shows the use of the library functional element, provided with a function placeholder, in a test sequence; and

FIG. 5 shows the functionally expanded graphical library functional element of FIG. 3.

DETAILED DESCRIPTION

FIG. 1 in an overview first shows part of a configuration device 1 known in principle from the state of the art for the graphical creation of a test sequence 2, which is used in each case to control a test device (not shown) having at least one electronic computer unit.

FIG. 1 shows in particular a display device 3 of configuration device 1, whereby graphical library functional elements 5 are displayed with display device 3 in a library field 4. Test sequence 2 was created by placing instances 6 of a number of library functional elements 5 in a configuration field 7. Instances 6 placed in configuration field 7 of library functional elements 5 reference the corresponding library functional element 5 in the library.

Working with graphical library functional elements 5 or with instances 6 of these library functional elements 5 is shown by way of example in FIGS. 2a-2d, as is known from the conventional art. A library functional element 5, which can be called the “FileContextManager,” is shown in FIG. 2a. In the example, it should be possible with this library functional element 5 to open, write to, and close a file. The opening of the file is realized in the functional element “OpenFileStream” and the closing of the file is implemented by the functional element “CloseFileStream.” What is to be written to the file is to be stored specifically in the functional element “ToDo.” Library functional element 5 shown in FIG. 2a could already be a fixed part of a library, but functional element 5 could also be modeled in configuration field 7 from elementary graphical library functional elements and then be defined as a library functional element.

The use of library functional element 5 from FIG. 2a in a test sequence 2 is shown in FIG. 2b, whereby the test sequence begins with an initial functionality “S1” and is ended with an ending functionality “S2,” whereby between these two functionalities the content of instance 6 of library functional element 5 “FileContextManager” is executed; it is important that functional element “FileContextManager” shown in FIG. 2b is an instance 6 of graphical library functional element 5 “FileContextManager” from FIG. 2a. The fact that instance 6 “FileContextManager” of graphical library functional element 5 “FileContextManager” references library functional element 5 “FileContextManager” in the library means that instance 6 is only a link to the corresponding library functional element 5, with the consequence that a change in the graphical library functional element 5 automatically also affects the—and each—instance 6 of this graphical library functional element 5.

The instance relationship between instance 6 of a library functional element 5 and library functional element 5 should not be maintained when, as shown in FIG. 2c, the functionality of instance 6 of the library functional element 5 is in any way changed, expanded, or shortened. In FIG. 2c, for example, a function addition has been made in that the functional element “Write_it” has been added to the functional element “ToDo.” The functional element “FileContextManager” shown in FIG. 2c therefore is no longer an instance of library functional element 5 “FileContextManager”, but a modified copy, which is independent.

A change in the graphical library functional element 5 “FileContextManager,” as shown in FIG. 2d, is no longer reproduced in the functional element “FileContextManager” shown in FIG. 2c, but must be manually updated, provided this is desired. In fact, the functional element “FileContextManager,” shown in FIG. 2c, can be defined in turn as a graphical library functional element, whereby naturally a name different from “FileContextManager” should be used; such a procedure, however, leads to a plurality of library functional elements, all of which must be updated separately from one another.

A graphical library functional element 5 realized by the invention is shown in FIG. 3; it does not seem to differ at first from an implementation which could be carried out with means already known from the state of the art, for example, therefore by the implementation according to FIG. 2a. The major difference, however, is that here the functional element “ToDo” is not of the type “Serial,” as in the exemplary embodiment according to FIG. 2a, but rather the functional element “ToDo” is realized as function placeholder 8 “OperationSlot,” whereby function placeholder 8 makes it possible to provide an instance functionality in an instance 6 of library functional element 5, whereby the reference of this instance 6 of library functional element 5 to library functional element 5 is retained, in contrast to the behavior in the state of the art. It is therefore possible to create a plurality of instances 6 of graphical library functional element 5, in a test sequence or also in a number of test sequences, and to provide this plurality of instances 6 each with an individual instance functionality, whereby each instance 6 further has a reference to the corresponding library functional element 5. This has the result that graphical library functional element 5 in the corresponding library can be changed, and all instances 6, individualized by its instance functionality, of library functional element 5 make this change and in fact despite the individualization by the instance functionality. This functionality is realized in that the instance functionality stored in the function placeholder is not part of the corresponding library functional element 5.

The use of the graphical library functional element 5 “FileContextFrameWork,” known from FIG. 3, within the scope of a test sequence 2 is shown in FIG. 4, whereby here in a reduced display of instance 6 of library functional element 5, shown in FIG. 3, with function placeholder 8 “ToDo,” only function placeholder 8 “ToDo” is shown (FIG. 4a). In a somewhat expanded display thereto (FIG. 4b), only the instance functionality 9 “Write_it” is shown, but not the more extensive functionality of graphical library functional element 5 according to FIG. 3.

The particular advantage of configuration device 1 of the invention is that a change in a graphical library functional element 5 of instances 6 of graphical library functional element 5 is made in test sequences, although instances 6 of graphical library functional element 5 are individualized by the instance functionality. It is shown in FIG. 5 that graphical library functional element 5 has been expanded by an additional functional element 10; this has the effect that all instances 6 of library functional element 5 reproduce this addition, although they have been individualized by function placeholder 8 and the instance functionality stored there.

Function placeholder 8 and the instance functionality stored there allow the central maintenance of different individual instances 6 of a graphical library functional element 5; there is no need accordingly to make copies of individualized library functional elements in test sequences and to maintain each separately; a new library functional element need not be set up for each individual version of a library functional element; the maintenance of test sequences is thereby greatly simplified, and it is possible to maintain a clear overview of libraries of graphical library functional elements.

The invention being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of the invention, and all such modifications as would be obvious to one skilled in the art are to be included within the scope of the following claims.

Claims

1. A configuration device for graphical creation of at least one test sequence for controlling a test device having at least one electronic computer, the test device being controllable according to the created test sequence, the configuration device comprising:

at least one display device; and

graphical library functional elements displayed with the display device in a library field,

wherein the test sequence is created by placing at least one instance of a library functional element in a configuration field,

wherein the instance of a library functional element references the library functional element itself, said instance being placed in the configuration field,

wherein the graphical library functional element is provided with a function placeholder, the function placeholder, in the instance of the library functional element being provided with an instance functionality, and

wherein the reference of the instance of the library functional element to the library functional element is retained.

2. The configuration device according to claim 1, wherein a test sequence created in the configuration field or a partial test sequence is definable as a graphical library functional element.

3. The configuration device according to claim 1, wherein, in a reduced display of the instance of a graphical library functional element with a function placeholder, only the function placeholder is shown.

4. The configuration device according to claim 1, wherein changes in a graphical library functional element of instances of the graphical library functional element are made in test sequences.

5. The configuration device according to claim 1, wherein function placeholders are configured to be used within function placeholders and/or graphical library functional elements are provided once again over generations of derivations with function placeholders.

6. The configuration device according to claim 1, wherein different versions of the instance functionality of the function placeholder of a graphical library functional element are determined and displayed with the display device.

7. The configuration device according to claim 6, wherein the function placeholder of an instance of a graphical library function element is assigned an already existing version of the instance functionality of the function placeholder by selection of a version from various displayed versions of the instance functionality.