JP6272168B2 - Search device and search program - Google Patents

Description

  The present invention relates to a search device and a search program for searching for programs and settings.

  Industrial equipment operates with programs and settings, which are developed using software on a computer. The program uses a command for controlling the movement of the device, a storage destination address for temporary or permanent storage of data, or a label that is an alias for the address, etc., and is created in a predetermined notation. There are a number of notations in the program depending on the purpose and application. There are various notations such as circuit diagrams as well as character strings. The program creator creates a program by selecting an appropriate one from the selectable notations. At that time, a plurality of notations may be used together, and a program for operating the device by combining them may be created.

  On the other hand, in the setting, a value determined by the device is set by inputting and selecting. At this time, there is a case where the device is set using an address and a label as in the program. In addition, settings and items differ for each device. In the case of a highly functional device, multiple setting values may be related to each other, and a screen specific to the device is provided in a form that can be easily understood by humans in order to enter the settings in a wizard format. There is also a case.

  In this way, the program and settings are created over a long period of time. Even after the creation is completed once, it may be used in conjunction with changes in maintenance, factories, plants, etc., and there are cases in which previously created programs and settings are referred to. In addition, there are cases where programs and settings that have been created once are diverted when used for other purposes. On the other hand, depending on the scale of a device, factory, or plant that uses industrial equipment, the amount of programs and settings is often enormous.

  In this situation, programs and settings are often performed while checking how data such as instructions and addresses and labels are used, and this is consistent with what is used elsewhere. It is effective to perform a data search to check whether it has been taken.

  However, in industrial equipment programs and settings, the input method differs depending on the location of use, so there are cases where it is not effective to display a list as text information, and a mechanism is provided that allows searching while displaying the location of use sequentially. There are many cases. (For example, patent document 1).

JP 2010-157155 A

  Such data retrieval is provided only for data managed by software for creating programs and settings. However, equipment, factories, plants, etc. are rarely composed of a single industrial device, and there are cases where multiple software is used to create programs and settings for such industrial devices. To do.

  At this time, if you try to search for data managed by software that is different from the software that searches for data from the same search screen, for the data search software that sequentially checks the data search results while displaying the usage location, the search results are displayed. When sequentially confirming, it is necessary to switch between a confirmation screen display of data managed by software for searching and a confirmation screen display of data managed by different software. However, due to the general specifications of OSs that employ a window system, the confirmation screen display of data managed by different software is displayed on the front of the software screen that performs data search. In order to display, it was necessary to return to the original search screen once, and there was a difficulty in operability.

  It is an object of the present invention to provide a means for confirming operability without a sense of incongruity even when sequentially confirming search results for data managed by a plurality of related software.

The search device of this invention
The search condition is received, and whether the matching data that matches the search condition exists in the first search target data managed by the first software or the second search target data managed by the second software A search unit that sequentially executes search processing for searching for, based on index data commonly used for searching the first search target data and the second search target data;
When the search unit determines that the match data is present in the first search target data, the match data is extracted from the first search target data using the first software, and the search If the match data is determined to be present in the second search target data in a search process subsequent to the search process in which the match data is determined to be present in the first search target data by the unit, A display information generation unit that generates display information for displaying a use location of the match data in the second search target data using the software of 1;
And a display unit for displaying the display information.

  According to the present invention, it is possible to provide means capable of confirming operability without a sense of incongruity when sequentially confirming search results for data managed by a plurality of related software.

FIG. 3 is a diagram illustrating the software configuration of the data search device 1001 according to the first embodiment. 2 is a block diagram of a data search device 1001 in the first embodiment. FIG. FIG. 4 is a diagram showing the display screen by the search condition input / result display operation unit 110 in the first embodiment. 5 is a flowchart of processing in which the search software processing unit 101 stores search target data in the diagram of the first embodiment. FIG. 5 is a flowchart when the search software processing unit 101 executes a search in the diagram of the first embodiment. 5 is a flowchart when a data confirmation request is notified to the other software processing unit 201 in the diagram of the first embodiment. 5 is a flowchart when the search software processing unit 101 regenerates the index data in the diagram of the first embodiment. FIG. 5 is a flowchart when the index data regeneration request is notified to the other software processing unit 201 in the diagram of the first embodiment. FIG. 10 is a diagram illustrating the software configuration of the data search device 1001 according to the second embodiment. 5 is a block diagram of a data search device 1002 according to the second embodiment. FIG. FIG. 10 is a diagram showing a display screen by a search condition input / result display operation unit 110 in the second embodiment. FIG. 10 is a flowchart of processing in which another software processing unit 201 stores search target data in the diagram of the second embodiment. FIG. 10 is a flowchart when the search software processing unit 101 executes a search in the diagram of the second embodiment. FIG. 11 is a flowchart when an index data regeneration request is notified to the other software processing unit 201 in the diagram of the second embodiment. FIG. 9 is a diagram illustrating the setting information in the second embodiment. The figure of Embodiment 2, The figure which shows the screen image 35. FIG. FIG. 9 is a diagram illustrating the hardware configuration of the data search device 1001 according to the third embodiment.

Embodiment 1 FIG.
FIG. 1 is a diagram illustrating a software configuration of the data search apparatus 1001 targeted in the first embodiment. In FIG. 1, a data search apparatus 1001 includes a search software 100 (first software), other software 200 (second software), an index, and an index that operate on an operating system 10 (hereinafter referred to as OS 10) that employs a window system. It has data 300. The search software 100 manages the search target data 130A (first search target data), and the other software 200 manages the search target data 230B (second search target data).

  FIG. 2 is a block configuration diagram of the data search apparatus 1001. The search software processing unit 101 is realized by the search software 100, a CPU, and the like, and the other software processing unit 201 is realized by the other software 200, the CPU, and the like. That is, the entities of the search software processing unit 101 and the other software processing unit 201 are the search software 100 and the other software 200, respectively. The search target data 130A, the index data 300, and the search target data 230B in FIG. 2 are stored in a storage unit (not shown). The storage unit is, for example, the magnetic disk device according to the third embodiment.

As shown in FIG. 2, the data search apparatus 1001 includes a search software processing unit 101, another software processing unit 201, index data 300, a display unit 500, and the like.
(1) The search software processing unit 101 is mainly used when a user inputs search conditions and confirms search results, and manages search target data.
(2) The other software processing unit 201 is a processing unit configured based on other software 200 that manages data to be searched but is different from the search software 100 that performs the search.
(3) The index data 300 is data that the search software processing unit 101 refers to when executing a search. In FIG. 2, the other software processing unit 201 (other software 200) is shown for one case, but the number is not limited and two or more may be used. In this example, the search software processing unit 101 (search software 100) manages the search target data 130A. However, the search software processing unit 101 may perform only the search. In this case, it is assumed that only data managed by the other software 200 is to be searched, and a plurality of other software 200-1, 200-2, etc. exist. In this case, the other software 200-1 is the first software, and the other software 200-2 is the second software.

In FIG. 2, the search software processing unit 101 includes a search condition input / result display operation unit 110, an index data regeneration request unit 120, search target data 130A (corresponding to a storage unit), a data confirmation / input unit 140A, and index data generation. 150A, a data confirmation requesting unit 160, and an index data generation requesting unit 170.
(1) The search condition input / result display operation unit 110 (search unit) performs a search process based on a search condition input by the user when searching for data or using the index data 300. Performs operations for displaying and confirming execution and search results in sequence.
(2) The index data regeneration request unit 120 performs processing for discarding the current index data and generating index data again at some timing when the search software 100 is used.
(3) The search target data 130A is data to be searched among data managed by the search software processing unit 101.
(4) The data confirmation / input unit 140A inputs data that becomes the search target data 130A when the search target data 130A managed by the search software 100 is searched or when the search software 100 is used.
(5) The index data generation unit 150A generates the index data 300 used at the time of search based on the contents of the search target data 130A.
(6) The data confirmation requesting unit 160 can confirm data to the other software processing unit 20 when performing data confirmation when the search target data 230B managed by the other software processing unit 201 is retrieved. Request display.
(7) The index data generation request unit 170 requests the other software processing unit 201 to generate the index data 300 based on the content of data managed by the other software processing unit 201.
(8) The search condition input / result display operation unit 110, the data confirmation / input unit 140A, and the data confirmation request unit 160 constitute a display information generation unit.

  In FIG. 2, the search target data 130A, the data confirmation / input unit 140A, the index data generation unit 150A, the data confirmation request unit 160, and the index data generation request unit 170 are each shown as a single case. Regardless, it may be two or more. However, one data confirmation / input unit 140A and one index data generation unit 150A are required for each search target data 130A. Further, one data confirmation requesting unit 160 and one index data generation requesting unit 170 are required for each of the search target data 230B managed by the other software 200 or the other software 200. In this case, for different search target data, the data confirmation / input unit 140A, the index data generation unit 150A, the data confirmation request unit 160, and the index data generation request unit 170 are shared, and a plurality of search target data 130A- 1, 130A-2,... 130A-N may be managed. The search target data 130A-1, 130A-2, etc. are different in data type, for example.

  Although the index data generation request unit 170 makes an index data generation request to the other software processing unit 201, the index data generation request unit 170 may generate index data by itself, like the index data generation unit 150A. There are various ways to regenerate the index data depending on the nature of the search software 100, such as when all management data is initialized or overwritten with data managed by another device. It is the same regardless of the cause.

  FIG. 3 is an example of display information (information indicating the location where the hit data is used) displayed on the display unit 500 by the search condition input / result display operation unit 110. The display information includes a “search string column 31” for inputting a search condition, a “search next” button 32 for displaying and confirming a location where the next search result is used, and a next search result. When the data is managed by the software 200, a balloon having the summary information and link information 34 (example of extraction instruction display) used when the other software 200 actually displays and confirms the use location. It consists of help 33. Although the example shown in FIG. 3 is used here, any method may be used as long as summary information and link information can be confirmed while maintaining the display of the search condition input / result display operation unit 110.

(Configuration of other software processing unit 201)
In FIG. 2, the other software processing unit 201 includes a data confirmation request distribution unit 280, an index data generation request distribution unit 290, search target data 230B, a data confirmation / input unit 240B, and an index data generation unit 250B.
(1) The data confirmation request distribution unit 280 receives the data confirmation request from the data confirmation request unit 160 of the search software processing unit 101 and delegates the processing to the corresponding data confirmation / input unit 240B.
(2) The index data generation request distribution unit 290 receives the index data generation request from the index data generation request unit 170 of the search software processing unit 101, and delegates the processing to the corresponding index data generation unit 250b.
(3) The search target data 230B is data to be searched among data managed by the other software processing unit 201.
(4) The data confirmation / input unit 240 </ b> B inputs data to be searched when the search target data 230 </ b> B managed by the other software processing unit 201 is searched or data to be searched while using the other software 200. .
(5) The index data generation unit 250B generates the index data 300 used at the time of search based on the contents of the search target data 1230B.

  The other software processing unit 201 is the same as the search software processing unit 101. That is, in FIG. 2, the search target data 230B, the data confirmation / input unit 240B, and the index data generation unit 250B are shown for one case, but the number is not limited and two or more may be used. However, one data confirmation / input unit 240B and one index data generation unit 250B are required for each search target data 230B. In this case, the data confirmation / input unit 240B and the index data generation unit 250B may be shared for different search target data 230B.

  FIG. 4 shows a processing flow (storage process) when data to be searched (programs and setting information (FIGS. 15 and 16 described later)) is input to the search software processing unit 101. This processing flow is the same when inputting data to be searched to the other software processing unit 201.

  The user inputs data to the data confirmation / input unit 140A of the search software processing unit 101. This input method differs depending on the data characteristics, but the method is not limited. Note that the data targeted here is data that will eventually become the search target data. The data confirmation / input unit 140A accepts this request (S5a), and updates the contents of the search target data 130A (S5b). Next, the data confirmation / input unit 140A makes an index data generation request to the index data generation unit 150A together with information on the input data (S5c). Upon receiving the request, the index data generation unit 150A updates the information of the index data 300 so that it matches the current state of the search target data 130A based on the information about the input data and the information of the search target data 130A. (S5d). At this time, a method of partially adding / deleting / changing, a method of generating all after deletion, and the like can be considered.

  Here, a case where index data is generated immediately after input is shown. In addition, there is a method of performing when the CPU usage rate is low after the input, but it does not matter which method is used to generate the index data.

  FIG. 5 shows a case where the search software processing unit 101 executes a search and confirms the use location of the next search result among the search results (presses the “next search” button 32 in FIG. 2). A processing flow is shown. The parentheses indicating the components in each step in FIG. 5 indicate the operating subject in that step. The same applies to the flowcharts in FIG.

  The user inputs a search condition (example: address) to the search condition input / result display operation unit 110 of the search software processing unit 101 (inputs to the search character string column 31), and executes a search execution request and a search result. Request usage confirmation. Specifically, the user inputs the search condition input / result display operation unit 110 on the screen of FIG. 3 displayed on the display unit 500, and clicks the “search next” button 32.

  The search condition input / result display operation unit 110 accepts this request (S6a), refers to the information in the index data 300, and searches for the first use location that matches the input condition (extracts the use location information) (S6b). ).

  At that time, information for determining which use location is the next best use location is also provided. This information is none when searching for the first time (search from the beginning), and when searching after searching once (for example, when clicking the second “next search” button), Use location information (previous use location information).

  At this time, when the use location is not found, the search condition input / result display operation unit 110 notifies the user to that effect (S6c) and ends the process.

  Next, the search condition input / result display operation unit 110 uses “information about which search target data” included in “current use location information” (match data) found as a result of the search of the index data 300. The information of the data confirmation processing unit (data confirmation / input unit 140A, data confirmation request unit 160) corresponding to the search target data is acquired (S6d).

(Correspondence information)
Here, for all search target data (assuming that there are a plurality of search target data 130 as search target data 130-1, 130-2,... 130-N for each type), which data confirmation processing It is assumed that information on whether the units (data confirmation / input unit 140A, data confirmation request unit 160) correspond is managed centrally. Therefore, it is possible to acquire correspondence information between the data confirmation processing unit and the search target data 130-k (k = 1, 2,... N) using the information. This centrally managed information may be configured as the search software 100 in advance, or may be generated as internal information by the data confirmation / input unit 140A or the data confirmation request unit 160 when the search software 100 is activated. It doesn't matter how.

  As a result of the search, if the corresponding one is the data confirmation / input unit 140A, the search condition input / result display operation unit 110 passes the current use location information to the data confirmation / input unit 140A and confirms the data. A request is made (S6e).

(Search target data 130A)
Upon receiving the request from the search condition input / result display operation unit 110, the data confirmation / input unit 140A uses the search target data 130A to display the corresponding data (extract matching data) for the user. Then, by using “information on where the data is used” included in the current usage location information passed from the search condition input / result display operation unit 110, where is the usage location portion found in the corresponding data? The display position is changed so that it can be understood, and the used part is highlighted (S6f).

  On the other hand, if the corresponding one is the data confirmation request unit 160, the search condition input / result display operation unit 110 is based on “information on where it is used” included in the current use location information (match data). Then, summary information (an example of display information) is generated (S6g).

  Next, based on the summary information, the search condition input / result display operation unit 110 uses the balloon help 33 or the like to display a used part that cannot be used by the search software processing unit 101 (when hit data is management data of the other software 200). ) Is displayed on the display unit 500 (S6h).

  At this time, the balloon help 33 is provided with a link (link information 34 in FIG. 3) for performing an action of confirming the use location using the other software 200. When the user operates a link or the like and an action (processing request) for confirming the use location is performed using the other software 200 (other software processing unit 201) ("confirm use location" in FIG. 3) When the link display is clicked), the search condition input / result display operation unit 110 accepts this processing request and sends it to the data confirmation request unit 160 together with the search result information held by the other software 200 (others). A “data confirmation request” is transmitted to the software processing unit 201). This data confirmation request will be described with reference to FIG.

(Continued from S6h)
FIG. 6 shows a processing flow when a data confirmation request is notified from the data confirmation requesting unit 160 to the other software processing unit 201.

  The data confirmation request from the data confirmation request unit 160 of the search software processing unit 101 is received by the data confirmation request distribution unit 280 (S8a).

  The data confirmation request allocating unit 280 that has received the request uses the “information on which search target data” included in the passed use location information, and the data confirmation processing unit (data confirmation unit) corresponding to the search target data. -The information of the input unit 240B) is acquired (S8b). At this time, information on which data confirmation processing unit corresponds to all the search target data is centrally managed as in the case of the search software processing unit 101 (search software 100). For this reason, correspondence information can be acquired using the information. The centrally managed information may be configured in advance as the other software 200, or may be generated by the data confirmation / input unit 240B as internal information when the other software 200 is activated, but the method is not limited.

  Next, the data confirmation request distribution unit 280 makes a data confirmation request to the data confirmation / input unit 240B based on the acquired information of the data confirmation / input unit 240B (S8c). The data confirmation / input unit 240B that has received the request displays the corresponding data for the user using the search target data 230B, and uses the information on where the data is used included in the used usage information. The display position is changed so that the location of the used portion found in the corresponding data is known and the used portion is highlighted (S8d). The processes of S8c and S8d described above correspond to S6e and S6f of FIG.

  FIG. 7 shows a processing flow when it is necessary to regenerate the index data 300 by processing in the search software 100.

  When it is necessary to regenerate the index by the user operation, the index data regeneration requesting unit 120 accepts the request (S7a).

  Receiving the request, the index data regeneration requesting unit 120 clears the index data 300 and prepares for regeneration (S7b).

  Next, the index data regeneration request unit 120 acquires all information of the index data generation processing unit (index data generation unit 150A, index data generation request unit 170) corresponding to the search target data (S7c). Note that the information of the index data generation processing unit is centrally managed in the same manner as the information of the data confirmation processing unit.

  Next, the index data regeneration request unit 120 sequentially issues an index data regeneration request to the index data generation processing unit (S7d).

  When the index data generation unit 150A accepts the index data regeneration request, the index data generation unit 150A updates the index data 300 to the search target data 130A targeted by itself (S7e). At this time, there may be a plurality of pieces of search target data 130A, but the processing is sequentially performed.

  On the other hand, when the index data generation request unit 170 accepts the index data regeneration request, the index data generation request unit 170 determines which search target data to the index data generation request distribution unit 290 of the other software processing unit 201. An index data regeneration request is made together with information on whether or not it is targeted (S7f).

  As for the index data regeneration, it does not matter which method is used to regenerate the index data, as in the index data generation (S5d).

  FIG. 8 shows a processing flow when an index data regeneration request is notified to the other software processing unit 201 (S7f).

  The index data re-generation request (S7f) from the index data generation request unit 170 of the search software processing unit 101 is received by the index data generation request distribution unit 290 (S9a).

  The index data generation request distribution unit 290 that has received the index data regeneration request uses the passed “information about which search target data is targeted” to generate index data generation processing corresponding to the search target data. Information (index data generation unit 250B) is acquired (S9b). At this time, information on which index data generation processing unit (index data generation unit 250B) corresponds to all the search target data is managed in the same manner as the information of the data confirmation processing unit. For this reason, correspondence information can be acquired using the information.

  Next, the index data generation request distribution unit 290 makes an index data regeneration request to the index data generation unit 250B based on the acquired information of the index data generation unit 250B (S9c).

  Receiving the request, the index data generation unit 250B updates the index data 300 to the search target data 230B targeted by itself (S9d). At this time, there may be a plurality of search target data 230B. In this case, the processing is sequentially performed.

  As described above, the search software 100 (search software processing unit 101) for sequentially checking the data search results while displaying the use location is different from the software (search software 100) for searching for data from the same search screen. When searching for data managed by the other software 200, without using the screen of the other software 200, the search software 100 is used to check the information on the use location of the search target data managed by the other software 200 in advance. It can be made possible (S6h in FIG. 5). Therefore, the operability at the time of searching is improved, and the merit that it is possible to quickly reach the target information at the time of searching can be enjoyed.

Embodiment 2. FIG.
In the first embodiment, when the data managed by the other software 200 is retrieved by the retrieval software processing unit 101 (retrieval software 100), the information on the use location can be confirmed. In the second embodiment, it is possible to confirm up to “how to use in the use location” of hit data.

  FIG. 9 is a diagram illustrating a software configuration of the data search apparatus 1002 according to the second embodiment. In FIG. 9, the data search device 1002 includes screen image data 400 in addition to the configuration of the data search device 1001 of the first embodiment. The screen image data 400 is stored in a storage unit (not shown).

  The configurations of the search software processing unit 101 and the other software processing unit 201 are the same as those in the first embodiment.

  FIG. 10 shows a block diagram of the data search apparatus 1002 of the second embodiment. The search software processing unit 101 is omitted because it is the same as that of the first embodiment. In FIG. 10, in the other software processing unit 201, the data confirmation / input unit 240B and the index data generation unit 250B of the first embodiment are the data confirmation / input unit 240B-2 and the index data generation unit 250B-2. The point is different. The data confirmation / input unit 240B-2 and the index data generation unit 250B-2 have different functions from the data confirmation / input unit 240B and the index data generation unit 250B of the first embodiment.

  FIG. 11 is an example of a display screen displayed by the search condition input / result display operation unit 110 and corresponds to FIG. 3 of the first embodiment. On the display screen of FIG. 11, a screen image 35 indicating the use location of the searched data is displayed. The screen image of FIG. 11 is information obtained by searching the record of the element 6 shown as the screen image 35 in FIG. 16 among the setting information shown in FIG. 15 is a diagram showing the setting information, and FIG. 16 is a diagram showing the record of the element 6 as the screen image 35 in the setting information of FIG. FIG. 16 is a screen image 35 displayed in the balloon help 33 of FIG.

In the display screen of FIG.
(1) “Character string column 31” for inputting a search condition;
(2) a “next search” button 32 for displaying and confirming the use location of the next search result;
(3) If the next search result is data managed by the other software 200, the screen image of the use location or the link information 34 used when the other software 200 actually displays and confirms the use location. Balloon help 33 having
(4) Consists of (1), (2), (3), and (4) of the screen image 35 that is displayed in the balloon help 33 and indicates the use location of the searched data.

  Here, the example shown in FIG. 11 is used, but any method may be used as long as it is possible to confirm the screen image and link information while maintaining the display of the search condition input / result display operation unit 110.

(Input search target data to search software processing unit 101)
In the second embodiment, the processing flow when data to be searched is input to the search software processing unit 101 is the same as that in FIG. 4 of the first embodiment.

(Input data to be searched into other software processing unit 201)
FIG. 12 shows a processing flow when data to be searched is input to the other software processing unit 201. S13a to S13c are the same as S5a to S5c in FIG.

  Upon receipt of the request, the index data generation unit 250B-2 obtains information on the use location that can be matched with the current state of the search target data 230B based on the information about the input data and the information of the search target data 230B. Generate (S13d).

  Next, the index data generation unit 250B-2 requests the data confirmation / input unit 240B-2 to obtain a screen image that allows confirmation of how the usage is used (S13e).

  Upon receipt of the request, the data confirmation / input unit 240B-2 generates screen image data that can display the used usage location information and provides the screen image data to the index data generation unit 4250B-2 (S13f).

  Next, the index data generation unit 250B-2 uses the index data 300 and the screen image data 400 based on the information on the use location generated by the index data generation unit 250B-2 and the screen image data acquired from the data confirmation / input unit 240B-2. Is updated (S13g).

  At this time, a method of partially adding / deleting / changing, a method of generating all after deletion, and the like can be considered, but any method can be used as long as it is generated so as to be consistent.

(Perform search)
FIG. 13 shows a processing flow when a search is performed by the search software processing unit 101, and the use location of the next search result is checked among the search results. FIG. 13 corresponds to FIG. 5 of the first embodiment.

  13, S14a to S14f are the same as S6a to S6f in FIG. 5, and S14g and S14f are unique.

  The search condition input / result display operation unit 110 acquires the corresponding screen image data from the screen image data 400 based on “information on where used” included in the usage location information (S14g).

  Next, the search condition input / result display operation unit 110 uses the acquired screen image data to display an actual use image of a use location that cannot be used by the search software processing unit 101 using balloon help or the like (S14h). ). At this time, the links provided in the balloon help are the same as those in FIG.

  In the second embodiment, the processing flow when the index data needs to be regenerated by the processing in the search software processing unit 101 is the same as that in FIG. 7 of the first embodiment.

  In the second embodiment, the processing flow when the data confirmation request is notified to the other software processing unit 201 is the same as that in FIG. 6 of the first embodiment.

  FIG. 14 shows a processing flow when an index data regeneration request is notified to the other software 200.

  S15a to S15c are the same as S9a to S9c in FIG.

  Receiving the request, the index data generation unit 250B-2 generates information on the use location for the search target data 230B targeted by itself (S15d).

  Next, the index data generation unit 250B-2 requests the data confirmation / input unit 240B-2 to acquire a screen image that allows confirmation of how the usage is used (15e).

  Receiving this acquisition request, the data confirmation / input unit 240B-2 generates screen image data in which the used usage location information can be displayed, and provides the screen image data to the index data generation unit 250B-2 (S15f).

  Next, the index data generation unit 250B-2 creates information on the index data 300 and the screen image data 400 on the basis of the information on the use location generated by itself and the screen image data acquired from the data confirmation / input unit 240B-2. Is updated (S15g).

  At this time, a plurality of pieces of data to be searched 4c may exist, but the processing is sequentially performed.

  As described above, with respect to the search software 100 that sequentially confirms the data search result while displaying the use location, the data managed by the other software 200 different from the search software 100 that searches for data from the same search screen is searched. In this case, it is possible to confirm in advance how to use the software at the place of use without displaying the screen of the other software 200 (S14h). As a result, there is an advantage that it is not necessary to display the actual usage location depending on the purpose at the time of search or the usage at the usage location, and the confirmation can be completed immediately.

Embodiment 3 FIG.
Embodiment 3 will be described with reference to FIG. In the third embodiment, a hardware configuration of a data search apparatus 1001 that is a computer will be described. The hardware configuration of the data search device 1002 is the same as that of the data search device 1001.

  FIG. 17 shows a hardware configuration of the data search apparatus 1001. In FIG. 17, the data search apparatus 1001 includes a CPU 950 (Central Processing Unit) that executes a program. The CPU 950 includes a ROM (Read Only Memory) 951, a RAM (Random Access Memory) 952, a display device 953 (an example of a display unit), a keyboard 954, a mouse 955, a communication board 956, a CDD 957, and a magnetic disk device 960 via a bus 958. And control these hardware devices. Instead of the magnetic disk device 960, a storage device such as an optical disk device or a flash memory may be used.

  The RAM 952 is an example of a volatile memory. Recording media such as the ROM 951, the CDD 957, and the magnetic disk device 960 are examples of nonvolatile memories. These are examples of a storage device or a storage unit, a storage unit, and a buffer. The communication board 956, the keyboard 954, and the like are examples of an input unit and an input device. The communication board 956, the display device 953, and the like are examples of an output unit and an output device. The communication board 956 may be connected to a network.

  The magnetic disk device 960 stores an operating system 961 (OS) (including OS 10), a program group 962, and a file group 963. The programs in the program group 962 are executed by the CPU 950 and the operating system 961.

  The program group 962 stores programs (search software 100, other software 200, etc.) that execute the functions described as “˜units” in the description of the above embodiments. The program is read and executed by the CPU 950.

  The file group 963 includes information such as “determination result”, “calculation result”, “extraction result”, “generation result”, “processing result”, data, signal values, Variable values, parameters, and the like are stored as items of “˜file” and “˜database”. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. In addition, information, data, signal values, variable values, and parameters stored in a recording medium such as a disk or memory are read out to the main memory or cache memory by the CPU 950 via a read / write circuit, and extracted, searched, referenced, and compared. Used for CPU operations such as calculation, calculation, processing, output, printing, display, etc. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during CPU operations such as extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Memorized.

  In the description of the embodiment described above, data and signal values are stored in the memory of the RAM 952, the compact disk of the CDD 957, the magnetic disk of the magnetic disk device 960, other optical disks, mini disks, DVDs (Digital Versatile Disk), and the like. Recorded on a recording medium. Data and signals are transmitted online via a bus 958, signal lines, cables, or other transmission media.

  In the above description of the embodiment, what has been described as “to part” may be “to means”, and “to step”, “to procedure”, and “to processing”. May be. That is, what has been described as “˜unit” may be implemented by software alone, a combination of software and hardware, or a combination of firmware.

  Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 950 and executed by the CPU 950. That is, the program causes the computer to function as the “˜unit” described above. Alternatively, the computer executes the procedure and method of “to part” described above.

  In the above embodiment, the data search devices 1001 and 1002 have been described, but it is obvious from the above description that these operations can be grasped as a program. Further, it is apparent from the above description that the operation of each “˜unit” of the data search apparatus 1001 can be grasped as a method.

  10 OS, 100 search software, 101 search software processing unit, 110 search condition input / result display operation unit, 120 index data regeneration request unit, 130A search target data, 140A data confirmation / input unit, 150A index data generation unit, 160 Data confirmation request unit, 170 Index data generation request unit, 200 Other software, 201 Other software processing unit, 280 Data confirmation request distribution unit, 290 Index data generation request distribution unit, 240B Data confirmation / input unit, 250B Index data generation Section, 300 index data, 400 screen image data, 500 display section, 1001, 1002 data retrieval device.

Claims (5)

The search condition is received, and whether the matching data that matches the search condition exists in the first search target data managed by the first software or the second search target data managed by the second software A search unit that sequentially executes search processing for searching for, based on index data commonly used for searching the first search target data and the second search target data;
When the search unit determines that the match data is present in the first search target data, the match data is extracted from the first search target data using the first software, and the search If the match data is determined to be present in the second search target data in a search process subsequent to the search process in which the match data is determined to be present in the first search target data by the unit, A display information generation unit that generates display information for displaying a use location of the match data in the second search target data using the software of 1;
And a display unit for displaying the display information. The display information generation unit
The display information is generated including an extraction instruction display that instructs the second software to extract the matching data existing in the second search target data from the second search target data by being selected. The search device according to claim 1, wherein: The display information generation unit
When the extraction command display included in the display information displayed by the display unit is selected, the second software searches the second software for the matching data existing in the second search target data. The search device according to claim 2, wherein the search device is extracted from target data. The display information generation unit
When it is determined by the search unit that the match data is present in the second search target data in the search process subsequent to the search process in which the match data is determined to be present in the first search target data, Using the first software, from among a plurality of screen images corresponding to the index data, a screen image representing a usage mode of the match data at a location where the match data is used in the second search target data. The search device according to claim 1, wherein the display information is generated including the specified screen image. The search condition is received, and whether the matching data that matches the search condition exists in the first search target data managed by the first software or the second search target data managed by the second software A process of sequentially executing a search process for searching for data based on index data commonly used for searching the first search target data and the second search target data;
When it is determined that the match data exists in the first search target data, the match data is extracted from the first search target data using the first software, and the match data is the first search target data. When it is determined that the matching data is present in the second search target data in the search processing subsequent to the search processing determined to be present in the one search target data, the first software is used to A process of generating display information for displaying a use location of the matching data in the second search target data;
Processing for displaying the display information;
Search program to make computer execute.

Images