JP2008262473A - Equipment maintenance management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an equipment maintenance management system capable of retesting the content tested once even in a system for dynamically generating and operating instance using class such as object-oriented system. <P>SOLUTION: A fixed parameter adding means 21 adds a parameter of a unique component identifier to the component, a unique input/output signal identifier when the component is input/output or a screen identifier given as fixed information in units of screens on which the component is displayed, to a component constituting software. By this parameter, a trace record write means 22 stores operation information at testing and display information as the test result in a predetermined part of a trace record DB11 and uses them when the changed software is retested. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an equipment maintenance management system having a test function constructed by an object-oriented technique in order to manage the time and contents of inspection, maintenance, repair, etc. of equipment and parts constituting the equipment using a computer. Is.

  In a facility maintenance management system configured by a computer in recent years, the software is configured by object-oriented technology. On the other hand, as described in Patent Document 1, for example, as a software test other than object-oriented technology, the test input is recorded and the test result is recorded, thereby improving the efficiency of the test again. Has been done.

JP-A-9-81415 (3rd page, FIG. 1)

However, the software of the object-oriented technology cannot improve the efficiency of the test again by recording the test input and recording the test result as in Patent Document 1.
In a system to which object orientation is applied, a software function (hereinafter referred to as an instance) that dynamically operates dynamically using a class is generated and operated in an empty area on a memory. In this system, not only when the class is modified, but also when a program of another class is modified, the instance generation order or resource allocation changes each time. This causes a problem that a test input cannot be given to the instance or a test result cannot be compared.
Further, when a plurality of instances are simultaneously generated from one class, there is a problem that it is often difficult to distinguish which instance is being tested in the test.
In particular, in the facility maintenance management system, since there are a large number of similar functions related to database search and display, a large amount of labor and cost are required in the test for confirming that the search results are correctly displayed.
As described above, in the facility maintenance management system that dynamically generates an instance from a class and operates it, the retest after the retest of the program after the first test has to be performed again by the human being the same test as the first test. In addition, retesting that there is no adverse effect other than the refurbished part requires a great deal of labor due to the large amount of data handled, and has a problem in terms of cost and quality. .

  The present invention has been made to solve the above-described problems, and has been tested once even in a system that dynamically generates and operates an instance using a class, such as an object-oriented system. The purpose is to obtain an equipment maintenance management system that can automatically retest the contents.

In the equipment maintenance management system according to the present invention, in the equipment maintenance management system for dynamically generating the operating software from the object-oriented class constituting the function for maintenance management of equipment,
Generates software and stores a server having a trace mode and a test mode for testing the generated software, operation information used for software testing by the server, and software display information as a test result A trace recording device for
The server gives the component constituting the generated software as fixed information to the component identifier unique to this component, the unique input / output signal identifier when the component is input / output operated, and the screen unit on which the component is displayed on the screen. A parameter adding means for adding a parameter of the displayed screen identifier, a trace recording writing means for writing the operation information and display information of the parts in a predetermined storage unit of the trace recording device based on the parameters in the trace mode, and a test mode A trace record reading means for reading out the operation information and display information of the component based on the parameters from a predetermined storage unit of the trace recording device,
In the trace mode, the part is tested based on the operation information obtained by performing the operation input, the display information as the test result is obtained, and the operation information and the display information input by the trace record writing means are trace recording device. Write on the
In the test mode, the part is tested using the operation information read from the trace recording device by the trace record reading means, and the display information obtained as a result of the test is compared with the display information stored in the trace recording device. is there.

As described above, the present invention provides an equipment maintenance management system that dynamically generates operating software from an object-oriented class that constitutes a function for maintenance management of equipment.
Generates software and stores a server having a trace mode and a test mode for testing the generated software, operation information used for software testing by the server, and software display information as a test result A trace recording device for
The server gives the component constituting the generated software as fixed information to the component identifier unique to this component, the unique input / output signal identifier when the component is input / output operated, and the screen unit on which the component is displayed on the screen. A parameter adding means for adding a parameter of the displayed screen identifier, a trace recording writing means for writing the operation information and display information of the parts in a predetermined storage unit of the trace recording device based on the parameters in the trace mode, and a test mode A trace record reading means for reading out the operation information and display information of the component based on the parameters from a predetermined storage unit of the trace recording device,
In the trace mode, the part is tested based on the operation information obtained by performing the operation input, the display information as the test result is obtained, and the operation information and the display information input by the trace record writing means are trace recording device. Write on the
In the test mode, the part is tested using the operation information read from the trace recording device by the trace record reading means, and the display information obtained as a result of this test is compared with the display information stored in the trace recording device. Even in a system in which an instance is dynamically generated and operated using an object-oriented class, the contents tested once can be automatically retested.

Embodiment 1 FIG.
A first embodiment of the present invention will be described below with reference to FIG.
FIG. 1 is a system configuration diagram showing an equipment maintenance management system according to Embodiment 1 of the present invention.
In the present invention, an instance constituting an object-oriented program is called a part. In addition, in order to test an object-oriented program, the equipment maintenance management system performs a test using a trace mode in which operation information that is input and display information that is a test result are recorded, and the recorded operation information. The display mode is a test mode function for comparing the display information with the recorded display information.
In the trace mode, the operation information of the component identified by the component identifier is recorded, and the display information of the component identified by the component identifier is recorded.
In the test mode, the operation information of the component identified by the component identifier is output from the record, and the display information of the component identified by the component identifier is compared with the recorded display information.
In FIG. 1, a terminal 1 and a server 3 are connected to a LAN 2. The terminal 1 is connected to input means for inputting operation information and display means for outputting display information. The server 3 is connected via the LAN 2 to a trace record DB 11 in which trace information including operation information recorded in the trace mode and display information is stored. For example, as shown in FIG. 5, the trace record DB 11 stores the hour / minute / second that occurred, a component identifier that identifies the component, a screen identifier that identifies the screen to which the component belongs, operation information and display information, and input / output signals. .
The server 3 is configured as follows.
For example, as shown in FIG. 2, the server DB 4 stores the type of component, the component identifier, the screen identifier for identifying the screen to which the component belongs, and the input / output signal identifier of the component. The storage area 5 stores whether or not the trace mode is set. The storage area 6 stores whether or not the test mode is set.
The program 10 is an object-oriented program of the equipment maintenance management system. The fixed parameter adding unit 21 (parameter adding unit) adds a component identifier, a screen identifier, and an input / output signal identifier as parameters to the instance when generating the instance (component).
The trace record writing unit 22 writes the trace record into the trace record DB 11. The trace record reading unit 23 reads the trace record from the trace record DB 11. The comparison determination unit 24 performs comparison determination between the component display information that is the result of the test mode and the component display information in the trace recording.

FIG. 2 is a diagram showing an example of the contents of the server DB of the equipment maintenance management system according to Embodiment 1 of the present invention.
In FIG. 2, the server DB 4 includes, for each type 31 of screen components displayed on the screen, a component identifier 32 of the component, a screen identifier 33 for each screen on which the component is displayed on the screen, and a component correspondence. An input / output signal identifier 34 group is defined and stored. Here, the component identifier 32 and the input / output signal identifier group 34 corresponding to the component are uniquely fixed to each component, and the screen identifier is fixed to be the same for components belonging to the same screen.

FIG. 3 is a flowchart showing the trace mode processing of the facility maintenance management system according to the first embodiment of the present invention. FIG. 3A shows the operation information input process, and FIG. 3B shows the display information output process.

FIG. 4 is a flowchart showing processing in the test mode of the facility maintenance management system according to Embodiment 1 of the present invention. FIG. 4A shows the operation information input process, and FIG. 4B shows the display information output process.

FIG. 5 is a diagram showing the contents of the trace record DB of the equipment maintenance management system according to Embodiment 1 of the present invention.
In FIG. 5, the hour / minute / second that occurred, the operation information and display information for the component are recorded, and the component identifier and screen identifier shown in FIG. 2 are given.

Next, the operation will be described.
FIG. 2 shows the contents of the server DB 4. For each component type 31, a component identifier 32 of a screen component displayed on the screen, a screen identifier 33 for each screen displayed on the screen, and an input / output signal identifier corresponding to the component. In this example, the component identifier 32 and the component corresponding input / output signal identifier 34 group are uniquely fixed for each component, and the screen identifier 33 is fixed for the components belonging to the same screen. . These are added to the instance by the fixed parameter addition means 21 as parameters when generating the instance (part).

Next, the operation of the instance (part) generated in this way will be described.
FIG. 3 is a flowchart showing processing for storing the input of the component and the output of the component.
In FIG. 3A, input operation information (for example, pressing or character input, for example, FIG. 5) from the mouse or keyboard of the terminal 1 is captured (processing S1), and the trace mode of the storage area 5 is significant. In this case (process S2), this is recorded in a predetermined location (predetermined storage unit) determined by the identifier of the input signal in the input / output signal identifier of the trace recording DB 11 (process S3), and the component process S4 (for example, mouse operation) Button processing for accepting input or input window processing for accepting keyboard input).

In FIG. 3B, component processing S5 (for example, list display of DB search results) is performed according to the contents received by the component processing S4, and for example, component display information (for example, characters XX, If the trace mode of the storage area 5 is significant (process S7), this is displayed in the input / output signal identifiers of the trace record DB 11 (shown in FIG. 5 as an example) (process S6). Is recorded at a predetermined location determined by the identifier of the output signal (step S8).
By operating in this way, the input operation information of the process S1 and the output display information of the process S6 are recorded at fixed predetermined locations in the trace recording DB 11 for the component to be tested.

FIG. 4 is a means for giving the previous input operation information to the component and comparing and determining the coincidence with the previous display information output of the component.
In FIG. 4A, when the test mode of the storage area 6 is significant (processing S11), a predetermined location determined by the input signal identifier in the input / output signal identifier of the trace recording DB 11 in the trace recording reading process S12. Is read, and the component processing S14, which is an operation information input process, is performed. If the test mode of the storage area 6 is not significant in the process S11, operation information (for example, pressing or character input. An example is shown in FIG. 5) from the mouse or the keyboard is fetched (process S13), and the component process S14. I do.

In FIG. 4B, in accordance with the content of the component processing S14, the component processing S15 (for example, list display of DB search results) is performed, component display information for screen display is generated (processing S16), and the storage area 6 is tested. If the mode is significant (process S17), the process compares the component display information with the component display information recorded at a predetermined location determined by the identifier of the output signal in the input / output signal identifier of the trace record DB 11 in process S18. Make a decision.
As a result, the component program can be tested in the test mode using the information recorded in the trace mode.

  According to the first embodiment, the recording location in the trace recording DB 11 is fixed even in an object-oriented operation that dynamically generates an instance using a component identifier, a screen identifier, and an input / output signal identifier. The same procedure as the operated procedure can be automatically reproduced, and the instance can be retested very easily.

The above contents have the same effect even if not an object-oriented language.
The number of terminals 1 and installation locations may be configured according to the user, and the number of LANs 2 and servers 3 and their installation locations are determined by the scale of equipment, the number of users, reliability, and the like.
Further, the location of the server DB 4, the trace recording DB 11, the storage areas 5 and 6, the facility maintenance system program 10, and the fixed parameter addition means 21 is not limited to that shown in FIG. 1, but is determined by the configuration determined by the size of the system. By doing so, the same effect is produced.
Further, the method of writing the significant / ineffective values in the storage area 5 and the storage area 6 may be by a normal means (for example, controlled by screen information).

Embodiment 2. FIG.
FIG. 6 is a diagram showing an example of the contents of the server DB of the facility maintenance management system according to Embodiment 2 of the present invention.
FIG. 6A shows the screen specification before the change, and FIG. 6B shows the screen specification after the change. In FIG. 6, reference numerals 31 to 34 are the same as those in FIG.

FIG. 7 is a diagram showing the contents of the trace record DB of the facility maintenance management system according to Embodiment 2 of the present invention.
FIG. 7A shows a screen before the screen specification is changed, and FIG. 7B shows a screen after the change. FIG. 7 shows the contents of the trace record DB similar to FIG.

The actual program is formed so that the parts described in the first embodiment gather together and operate in a chained manner. The part of the program change is usually partial, and it is efficient if the previous test results can be used for the part without change. The second embodiment deals with this, and the program is changed in units of screens.
A record in the trace record DB 11 corresponding to FIG. 6A showing the contents of the server DB 4 is shown in FIG.
The recording in FIG. 7A is recorded in units of screen identifiers. When there is a specification change on the screen of the screen identifier B and the contents of the server DB 4 are as shown in FIG. 6B, FIG. 7A, which is the recorded contents of the trace recording DB 11, shows only the portion of the screen identifier B. As a result, the trace record DB 11 becomes as shown in FIG.
Thereby, even when a screen specification change occurs for a specific screen, if the operation of FIG. 3 of Embodiment 1 is performed only once for the screen for which the screen specification change has occurred, for other screens, The test of FIG. 4 according to the first embodiment can be performed as it is to perform a test.

  According to the second embodiment, even when the screen specification is changed for a specific screen, if the trace mode is executed only for the screen on which the screen specification has changed, the test mode is executed for the entire screen specification after the change. Since the display information can be compared and determined, there is an effect that the retest can be performed very easily.

Embodiment 3 FIG.
FIG. 8 is a system configuration diagram showing an equipment maintenance management system according to Embodiment 3 of the present invention.
In FIG. 8, 1 to 6, 10, 11, 21 to 24 are the same as those in FIG. In FIG. 8, the server 3 is provided with interruption means 25 for interrupting the process, and also provided with a storage area 7 for storing the screen identifier and component identifier of the screen for interrupting the process.

FIG. 9 is a diagram showing an example of the contents of the server DB of the facility maintenance management system according to Embodiment 3 of the present invention.
FIG. 9 is configured to store the screen identifier (A in this case) of the screen for interrupting the process, with the same configuration as FIG. In FIG. 9, reference numerals 31 to 34 are the same as those in FIG. In FIG. 9, a part mark 35 that is a mark of the part that operates last in one screen is provided.

FIG. 10 is a flowchart showing a test mode process of the facility maintenance management system according to the third embodiment of the present invention.
FIG. 10A shows an operation information input process, and FIG. 10B shows a display information output process.

When testing a program, it may be necessary to change the external input of the system under test. In addition, it may be necessary to check the status of the value of the storage unit such as a program immediately after execution of a specific screen or each database memory. For this reason, the interruption means 25 which interrupts a process is provided.
As means for storing the screen identifier, as shown in FIG. 9, the part mark 35 which is the mark of the last part to be operated in one screen is made significant (1 in FIG. 9), and the operation of FIG. 10 is executed. Accordingly, when the processes S21 and S23 of FIG. 10 are executed for the part with the part mark 35 shown in FIG. 9, the execution of the processes is interrupted in the processes S22 and S24 shown in FIG.
That is, in FIG. 10A, as in FIG. 4A, after S11 to S14 are processed, the test mode is significant, and the process is the last part in the interruption screen (processing S21). In step S22, the process is interrupted.
Further, in FIG. 10B, similarly to FIG. 4B, after S15 to S18 are processed, the test mode is significant and the process is the last part in the interruption screen (processing S23). In step S24, the process is interrupted.
Further, the screen identifier (A in FIG. 9) of the screen to be interrupted with the component mark 35 and the component identifier of the last operating component are stored in the storage area 7 in advance, and this is referred to in FIG. When executed, the same effect can be achieved and the processing speed can be increased.

  According to the third embodiment, the external input of the system under test is changed during this interruption, the status of the storage processing values such as the program and each database memory is examined, the processing is canceled and the processing is restarted. There is an effect that the test can be performed very easily.

Embodiment 4 FIG.
FIG. 11 is a system configuration diagram showing an equipment maintenance management system according to Embodiment 4 of the present invention.
In FIG. 11, 1 to 6, 10, 11, 21 to 25 are the same as those in FIG. In FIG. 11, a storage area 8 for storing a component identifier of a component whose processing is to be interrupted is provided.

FIG. 12 is a flowchart showing a test mode process of the equipment maintenance management system according to the fourth embodiment of the present invention.
FIG. 12A shows the operation information input process, and FIG. 12B shows the display information output process.

When testing a program, it may be necessary to change the external input of the system under test. In addition, it may be necessary to examine the status of storage processing values such as a program immediately after execution of a specific screen and each database memory.
In the fourth embodiment, as a means for storing a part identifier, the part mark 35 as a mark for a part to be interrupted is made significant by the same method as in FIG. 9, and the part mark is obtained by executing the flowchart of FIG. When the processes S31 and S32 in FIG. 12 are executed for the part 35 to be interrupted, the execution of the process is interrupted as in FIG.
That is, in FIG. 12A, as in FIG. 4A, after processing S11 to S14, when the test mode is significant and the process is interrupted (processing S31), processing S22 is performed. To interrupt the process.
Also, in FIG. 12B, as in FIG. 4B, after the processing in S15 to S18, if the test mode is significant and the processing is interrupted (processing S32), the processing is performed in processing S24. Interrupt.
In addition, if the part identifier of the part to be interrupted with the part mark 35 is stored in advance in the storage area 8 and executed with reference to this in FIG. 12, the same effect can be achieved and the processing speed can be increased. .

According to the fourth embodiment, the external input of the system under test is changed during the interruption, the status of the storage processing value of the program, each database memory, etc. is checked, and the processing is resumed by solving the interruption. There is an effect that the test can be performed very easily.
In addition, by providing part marks for all parts, a so-called single-step operation that is interrupted and released every time a part is executed can be realized and the operation can be confirmed, and the test can be performed very easily. is there.

Embodiment 5. FIG.
FIG. 13 is a system configuration diagram showing an equipment maintenance management system according to Embodiment 5 of the present invention.
In FIG. 13, 1 to 6, 10, 11, 21 to 25 are the same as those in FIG. In FIG. 13, a storage area 9 for storing input / output signal identifiers and storage data is provided.

  FIG. 14 is a flowchart showing display information output processing in the test mode of the equipment maintenance management system according to Embodiment 4 of the present invention.

When conducting a program test, if the data of the system under test is unscheduled, it may be necessary to analyze various data on the cross section to identify the cause.
In the fifth embodiment, input / output signal identifiers and predetermined data are stored in the storage area 9 in advance, and predetermined data for the input / output signal identifiers in the storage area 9 are executed by executing the flowchart of FIG. If it is detected in step S41 that the actual data is different, the execution is interrupted in step S24.
That is, in FIG. 14, as in FIG. 4B, after processing S <b> 15 to S <b> 18, when the test mode is significant and the stored data of the input / output signal identifier does not match the actual data content (processing S <b> 41). In step S24, the process is interrupted.

According to the fifth embodiment, there is an effect that the cause can be identified very easily by analyzing the necessary data during the interruption.

BRIEF DESCRIPTION OF THE DRAWINGS It is a system block diagram which shows the equipment maintenance management system by Embodiment 1 of this invention. It is a figure which shows the example of the content of DB for servers of the equipment maintenance management system by Embodiment 1 of this invention. It is a flowchart which shows the input and output process of the components of the equipment maintenance management system by Embodiment 1 of this invention. It is a flowchart which shows the process which gives the last input to the components of the equipment maintenance management system by Embodiment 1 of this invention, and compares and determines the coincidence with the last output of components. It is a figure which shows the content of trace record DB of the equipment maintenance management system by Embodiment 1 of this invention. It is a figure which shows the example of the content of DB for servers of the equipment maintenance management system by Embodiment 2 of this invention. It is a figure which shows the content of trace record DB of the equipment maintenance management system by Embodiment 2 of this invention. It is a system block diagram which shows the equipment maintenance management system by Embodiment 3 of this invention. It is a figure which shows the example of the content of DB for servers of the equipment maintenance management system by Embodiment 3 of this invention. It is a flowchart which shows the process which gives the last input to the components of the equipment maintenance management system by Embodiment 3 of this invention, and compares and determines the coincidence with the last output of components. It is a system block diagram which shows the equipment maintenance management system by Embodiment 4 of this invention. It is a flowchart which shows the process which gives last input to the components of the equipment maintenance management system by Embodiment 4 of this invention, and compares and determines the coincidence with the last output of components. It is a system block diagram which shows the equipment maintenance management system by Embodiment 5 of this invention. It is a flowchart which shows the process which gives the last input to the components of the equipment maintenance management system by Embodiment 5 of this invention, and compares and determines the coincidence with the last output of components.

Explanation of symbols

1 Terminal 2 LAN
3 Server 4 Server DB
5-9 Storage area 10 Program 11 Trace record DB
21 Fixed parameter adding means 22 Trace record writing means 23 Trace record reading means 24 Comparison determining means 25 Interrupting means

Claims (5)

In an equipment maintenance management system that dynamically generates operating software from an object-oriented class that constitutes functions for maintenance management of equipment,
A server having a trace mode and a test mode for generating the software and testing the generated software, and operation information used for testing the software by the server and display information of the software as a test result And a trace recording device for storing
The server includes a component that constitutes the generated software, a component identifier unique to the component, a unique input / output signal identifier when the component is input / output operated, and a screen unit on which the component is displayed on the screen. Parameter adding means for adding a parameter of a screen identifier given as fixed information, and a trace for writing operation information and display information of the component to a predetermined storage unit of the trace recording device based on the parameters in the trace mode Recording and writing means; and trace record reading means for reading operation information and display information of the component based on the parameters in the test mode from a predetermined storage unit of the trace recording device;
In the trace mode, the part is tested based on the operation information obtained by performing the operation input, the display information which is a test result is obtained, and the operation information input by the trace recording / writing means and the Write the display information to the trace recording device,
In the test mode, the part is tested using the operation information read from the trace recording device by the trace record reading means, display information obtained as a result of the test, and display information stored in the trace recording device, Equipment maintenance management system characterized by comparing 2. The facility maintenance management system according to claim 1, wherein the software test is performed in units of screens identified by the screen identifier. The server stores a screen identifier for interrupting the processing in the test mode, and has an interrupting means for interrupting the processing when the last operation of the screen that matches the stored screen identifier is completed. The facility maintenance management system according to claim 1. The server stores a component identifier for interrupting the processing in the test mode, and has an interrupting means for interrupting the processing when the operation of a component that matches the stored component identifier is completed. The equipment maintenance management system according to claim 1. The server stores an input / output signal identifier for interrupting processing in the test mode and data corresponding thereto, data processed by a component that matches the stored input / output signal identifier, the stored data, The facility maintenance management system according to claim 1, further comprising interrupting means for interrupting the processing according to the comparison result.

Images