JP2006277660A - Conversion rule creation program and conversion rule evaluation program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a conversion rule creation program and a conversion rule evaluation program reducing a work burden concerning the creation of conversion rule definition information of a data format. <P>SOLUTION: The conversion rule creation program for allowing a computer to carry out the creation of conversion rule definition information between data formats composed of a plurality of elements having values respectively, has reproduction procedure of creating at least partial reproduction of definition information of the first data format as definition information of the second data format; association procedure of associating each element constituting the second data format, with each element constituting the first data format corresponding to the reproduction source of each element; and first conversion rule creation procedure of using either one of the associated elements as the conversion source and the other as the conversion destination to create setting of the value of the element of the conversion source as the value of the element of the conversion destination, as conversion rule definition information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a conversion rule creation program and a conversion rule evaluation program, and more particularly to a conversion rule creation program that causes a computer to create or evaluate conversion rule definition information between data formats each composed of a plurality of elements each having a value. The present invention relates to a conversion rule evaluation program.

  In a company, a large number of computer systems are operating, and each system generally has its own database. When it is necessary to perform data linkage between a plurality of systems, it is inefficient to create a linkage tool for each combination of systems. Therefore, conventionally, there is a method of defining an intermediary or common database (hereinafter referred to as “integrated DB”), and attempting data linkage between a plurality of systems via the integrated DB.

  FIG. 1 is a conceptual diagram for explaining data linkage between systems via an integrated DB. As shown in FIG. 1, the following format conversion is performed between each system (system A, system B, and system C) and the integrated DB in order to absorb the difference in the respective data formats.

  First, when data managed in each system is input to the integrated DB, an input format conversion file 501 is used, and the data format for each system is converted into a common integrated DB data format. On the other hand, when data managed in the integrated DB is output to each system, an output format conversion file 502 is used, and the data format in the integrated DB is converted into a data format for each system.

  Here, the format conversion file refers to a file in which data format conversion rules are defined. As a language for describing this transformation rule, there is XSLT (XSL Transformations) that transforms an XML (eXtensible Markup Language) format data format.

  FIG. 2 is a conceptual diagram for explaining format conversion by XSLT. As shown in FIG. 2, according to XSLT, data structure conversion (521), element name or attribute name conversion (522), and element value between the conversion source XML document 511 and the conversion destination XML document 512 Alternatively, attribute value conversion (523) or the like can be defined. Therefore, by expressing the contents of the database and integrated DB of each system in XML, a file described in XSLT can be used as a format conversion file.

  By the way, in order to link a system using a new data format to the integrated DB, it is necessary to create a new format conversion file. In order to create a new format conversion file with a small number of man-hours, one method is to effectively reuse the existing format conversion file. When there are a plurality of existing format conversion files, it is necessary to determine which format conversion file is best reused.

  The main evaluation items in determining the format conversion file that is most suitable for reuse are (1) data items output from the format conversion file, (2) conversion processing speed (performance), and (3) file usage status. Etc.

  Regarding the data items output from the format conversion file of (1), it is necessary to evaluate whether or not the data items to be linked depend on the data items output from the format conversion file. The Conventionally, this evaluation has been performed by visual inspection of each format conversion file. Or it was performed by visually checking the actual conversion result using test data.

  The conversion processing speed of (2) needs to be evaluated from the viewpoint that the processing speed of the format conversion file may vary greatly depending on the description method. This evaluation has been conventionally performed by measuring the actual conversion speed using test data.

  Regarding the usage status of the file in (3), it is necessary to evaluate a format conversion file having a high usage record from the viewpoint that it can be determined that the quality is reliable. This evaluation has been conventionally performed by referring to a usage record recorded in a spreadsheet software or the like.

  If the format conversion file suitable for reuse exists as a result of the evaluation, the file is used as it is or after being modified. If there is no format suitable for reuse, it is necessary to create a new format conversion file.

Patent Document 1 describes a technique that enables searching for a data source that does not necessarily support a format required by a client using XML and XSLT techniques.
JP 2002-539547 A

  However, the following problems are associated with the creation or reuse of format conversion files.

  The first problem is that similar format conversion files are flooded.

  That is, when the information of the integrated DB is handled by a plurality of systems, the data items to be handled have the same contents as long as the data format of the integrated DB as the cooperation partner is the same even if the systems differ. Therefore, the data formats of the systems tend to be similar to each other, and as a result, the format conversion is likely to be similar. By creating a plurality of files in which similar format conversion is defined, similar format conversion files are flooded.

  For example, FIG. 3 is a diagram illustrating an example of similar format conversion. In FIG. 3, conversion source formats (A) and (B) differ only in the item name of each data item, and the hierarchical structure of data and the meaning of each data item are the same. Accordingly, the format conversion files A and B are also similar. Such a case often occurs when the table item name of the conversion source DB is directly applied to the item name of the conversion source format.

  Also, there is a high possibility that the two format conversion files “before correction” and “after correction” when the format conversion file is corrected by debugging or version upgrade are similar. If there is another system that uses the file before correction, it is necessary to retain this file, and as a result, a plurality of similar format conversion files exist.

  The second problem is that it is difficult to create a new format conversion file.

  That is, when there is no existing format file suitable for reuse, it is necessary to create a completely new format conversion file. Although a general-purpose tool for creating a format conversion file such as XSLT is already on the market, even if such a tool is used, complicated manual work is required.

  FIG. 4 is a diagram for explaining an example of a conventional new creation operation of an input format conversion file. In FIG. 4, the definition of the data format of the system to be linked (531), the association between the data item of each system and the data item of the integrated DB (532), and the setting of the function used for the data conversion of the item as necessary In (533), when there is no data item corresponding to the integrated DB, operations such as setting a constant (534) as necessary are shown. It is very inefficient that such work is performed every time a format conversion file is created.

  A third problem is that it is difficult to evaluate an existing format conversion file for reuse.

  That is, when selecting an existing format conversion file suitable for reuse, it is necessary to perform the evaluations (1) to (3) described above. That is, it is necessary to visually analyze the format conversion file, create test data, and execute a test. These tasks are difficult to perform unless they are skilled technicians. In addition, when there are a large number of format conversion files, it is very difficult to perform these evaluations on all the format conversion files.

  The present invention has been made in view of the above points, and it is an object of the present invention to provide a conversion rule creation program and a conversion rule evaluation program that can reduce the work load related to the creation of definition information of data format conversion rules. And

  In order to solve the above problems, the present invention provides a conversion rule creation program for causing a computer to create definition information of conversion rules between data formats each composed of a plurality of elements each having a value. A duplication procedure for creating at least a copy of the definition information of the data format as the definition information of the second data format, each element constituting the second data format, and the copy source of the each element Association procedure for associating each element constituting the first data format with one of the associated elements as the conversion source and the other as the conversion destination, and the value of the conversion source element as the value of the conversion destination element And a first conversion rule creation procedure for creating the conversion rule definition information as the conversion rule definition information.

  Such a conversion rule creation program can automatically create definition information of conversion rules between data formats. Therefore, it is possible to reduce the work load related to the creation of the definition information of the data format conversion rule.

  In order to solve the above problems, the present invention is a conversion rule evaluation program for causing a computer to perform reusability evaluation on conversion rule definition information between data formats each composed of a plurality of elements each having a value. A conversion rule storage procedure for storing the conversion rule definition information, a conversion target selection procedure for selecting an element to be converted from the elements constituting the data format to be converted or converted, and For each of the definition information stored in the conversion rule storage procedure, an excess / deficiency determination procedure for determining an excess / deficiency between an element to be converted in the definition information and an element selected in the conversion target selection procedure A display procedure for causing the display device to display evaluation information based on the excess / deficiency determined in the excess / deficiency determination procedure; Characterized in that it has.

  With such a conversion rule evaluation program, it is possible to appropriately evaluate the reusability of the definition information of the data format conversion rule. Therefore, the existing resources can be effectively reused, and the work load related to the creation of the definition information of the data format conversion rule can be reduced.

  ADVANTAGE OF THE INVENTION According to this invention, the conversion rule preparation program and conversion rule evaluation program which can reduce the work burden concerning preparation of the definition information of the conversion rule of a data format can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 5 is a diagram illustrating a hardware configuration example of the format conversion file creation device according to the embodiment of the present invention. Here, the format conversion file refers to a file in which conversion rules between the data format of each system linked to the integrated DB (hereinafter referred to as “cooperation system”) and the data format of the integrated DB are defined. The integrated DB is an intermediary or common database for performing data linkage between a plurality of systems. Further, the data format refers to information including the structure of information managed in the system (for example, a tree structure) and attribute information (item name, data type, etc.) of each data item constituting the structure. Also called schema information.

  The format conversion file is classified into two types according to the conversion direction. That is, a format conversion file that performs conversion from the cooperation system to the integrated DB is referred to as an input format conversion file, and a format conversion file that performs the reverse conversion is referred to as an output format conversion file.

  The format conversion file creation device 10 of FIG. 5 includes a drive device 100, an auxiliary storage device 102, a memory device 103, an arithmetic processing device 104, a display device 105, and an input device that are mutually connected by a bus B. 106.

  A program for realizing processing in the format conversion file creation apparatus 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The arithmetic processing unit 104 executes functions related to the format conversion file creation device 10 in accordance with a program stored in the memory device 103. The display device 105 displays a GUI (Graphical User Interface) or the like by a program. The input device 106 includes a keyboard and a mouse, and is used to receive various operation instructions.

  FIG. 6 is a diagram illustrating a functional configuration example of the format conversion file creation device according to the embodiment of the present invention. In FIG. 6, the format conversion file creation apparatus 10 includes a basic format conversion file editing unit 11, a basic format conversion file evaluation unit 12, an abstract item setting unit 13, a format conversion file management unit 14, a basic format conversion file DB 21, and a format definition. It comprises a DB 22, a function definition DB 23, an abstract item setting DB 24, a format conversion file DB 25, and the like. These functions are realized by processing of a program installed in the format conversion file creation device 10.

  The basic format conversion file editing unit 11 generates a basic format conversion file through a dialog with a user via a screen (hereinafter referred to as a “basic format conversion file editing screen”) for creating or modifying a basic format conversion file. And editing. Here, the basic format conversion file is a template that is abstracted (perforated state), that is, expressed as a variable without specifically specifying the data item name on the cooperation system side in the definition of the conversion rule. A format conversion file as a type.

  FIG. 7 is a diagram for explaining the basic format conversion file. In FIG. 7, the definition of a specific format conversion file for each cooperative system is shown in a table format on the left side. That is, the format conversion file A501 and the format conversion file B502 correspond to different cooperative systems. However, the difference between the two is only the item name before conversion. The basic format conversion file 503 on the right side of the figure is an abstraction (variable) of the differences in the item names.

  By creating one basic format conversion file in which conversion rules are abstracted, it becomes easy to create a specific format conversion file of “type” similar to the basic format conversion file. In the example of FIG. 7, by creating the basic format conversion file 503, the format conversion file A 501 and the format conversion file B 502 are created only by filling the abstracted portion, that is, by assigning specific values to the variables. Just apply. The items abstracted in the basic format conversion file are hereinafter referred to as “abstract items”.

  FIG. 8 is a diagram showing a display example of the basic format conversion file editing screen. The display example of the basic format conversion file editing screen 110 in FIG. 8 shows a state in which the basic format conversion file is defined to some extent.

  That is, the conversion source format display area 1106 displays the data format of the conversion source (cooperation system), and the conversion destination (integrated DB) format display area 1107 displays the data format of the conversion destination. “Employee” and “age” in the conversion source format display area 1106 are enclosed in parentheses (), which indicates that they are defined as abstract items.

  Definition that links 11 and 12 connecting data items of the conversion source and the conversion destination are directly registered in the conversion destination (employee name or age) as the value of the conversion source ((employee name) or (age)) Indicates. Moreover, the value of the conversion source “Seibetsu” becomes the function f1 by the link 13 from the conversion source “Seibetsu” to the function f1 and the link 14 from the function f1 to the conversion destination “employee gender”. In other words, it is defined that registration is made in “employee gender” of the conversion destination. Here, for example, the function is expressed by “0” or “1” in the linkage system for the gender, and the conversion source value is expressed by “m” or “f” in the integrated DB. Information that defines the correspondence between the two when they cannot be handled as they are.

  The link 15 from the constant c1 to the “sort order” of the conversion destination indicates that it is defined that the value (1) of the constant c1 is assigned to the “sort order” of the conversion destination.

  As described above, in the basic format conversion file editing screen 110, it is possible to create conversion rules between the conversion source data format and the conversion destination data format, that is, definition information of the basic format conversion file. Definition information relating to the created basic format conversion file is stored in the basic format conversion file DB 21.

  Returning to FIG. The basic format conversion file evaluation unit 12 is used when a new basic format conversion file is created by reusing an existing basic format conversion file, and the existing format conversion file managed by the basic format conversion file DB 21 is used. Evaluate whether or not reuse is appropriate, and present the evaluation result to the user.

  The abstract item setting unit 13 allows the user to set a specific value for the abstract item via the GUI. A value set in the abstract item (hereinafter referred to as “abstract item setting value”) is stored in the abstract item setting DB 24.

  The format conversion file management unit 14 creates a specific format conversion file for a specific linkage system based on the abstract item setting value and the basic format conversion file. Information on the created format conversion file is stored in the format conversion file DB 25.

  The format definition DB 22 is a database that manages data format definition information (format definition) for each system including the integrated DB, and includes a format definition table and a format definition item table.

  FIG. 9 is a diagram illustrating a configuration example of a format definition table constituting the format definition DB. The format definition table 221 is a table for managing format definitions. One record in the format definition table 221 represents one format definition, and includes items such as a format definition ID, a format definition name, and a format type.

  The format definition ID is an ID for identifying each format definition, and is automatically assigned when the format definition is registered. The format definition name is a name given to the format definition. The format type is information indicating whether the format definition is “conversion source system format”, “integrated DB format”, or “conversion destination system format”. The “conversion source system format” indicates a format definition of a system that is a conversion source for the integrated DB (side that outputs data to the integrated DB). “Integrated DB format” indicates the format definition of the integrated DB. The “conversion destination system format” indicates the format definition of the system that is the conversion destination from the integrated DB (the side that fetches data from the integrated DB).

  FIG. 10 is a diagram showing a configuration example of a format definition item table constituting the format definition DB. The format definition item table 222 is a table for managing definition information of elements each having a value, that is, each data item (hereinafter referred to as “format definition item”), which constitutes a data format defined by the format definition. . One record in the format definition item table 222 represents one format definition item, and format definition ID, item ID, parent item ID, item type, item name, item name abstraction flag, data type, data length, and sort order It consists of items such as.

  The format definition ID is the format definition ID of the format definition to which the format definition item belongs. Multiple format definition items can belong to one format definition. The item ID is an ID for identifying each format definition item, and is automatically numbered. The parent item ID is an ID for identifying the parent item of the format definition item when the data format forms a hierarchical structure such as a tree structure. If the item is the root, a NULL value is set.

  The item type is information indicating whether the format definition item is “hierarchy” or “end”. “Hierarchy” refers to a format definition item related to a node having child nodes in a tree structure. On the other hand, “terminal” refers to a format definition item relating to a node having no child node. For example, in the conversion destination data format of FIG. 8, “employee list” and “employee information” are classified into “hierarchies”, and “employee name”, “employee code”, “employee gender”, and “employee gender” “Sort order” is classified as “terminal”.

  The item name is the name of the format definition item. The item name abstraction flag is a flag indicating whether or not the item name of the format definition item is an abstract item. The data type and data length indicate the data type and data length of the format definition item. The sort order indicates the display order in the hierarchy to which the format definition item belongs.

  The basic format conversion file DB 21 in FIG. 6 will be described. The basic format conversion file DB 21 is a database that manages information related to the basic format conversion file, and includes a basic format conversion definition table, a setting link information table, a setting function item table, a setting constant item table, an abstract item management table, and the like. Is done.

  FIG. 11 is a diagram showing a configuration example of a basic format conversion definition table constituting the basic format conversion file DB. The basic format conversion definition table 211 is a table for managing conversion rule definition information (hereinafter referred to as “basic format conversion definition information”) in the basic format conversion file. One record in the basic format conversion definition table 211 represents one basic format conversion definition information (one-way conversion rule definition information between one format definition and another format definition), and a basic format conversion definition ID. , Conversion source format definition ID, conversion destination format definition ID, input / output type, basic format conversion file name, and basic format conversion file.

  The basic format conversion definition ID is an ID for identifying each basic format conversion definition information and is automatically numbered. The conversion source format definition ID is a format definition ID of a format definition that is a conversion source in the basic format conversion definition information. The conversion destination format definition ID is the format definition ID of the format definition that is the conversion destination in the basic format conversion definition information.

  The input / output type is information indicating whether the basic format conversion definition information is for input or output. The basic format conversion file name is the file name of the basic format conversion file in which the basic format conversion definition information is described. The basic format conversion file is actual data of the basic format conversion file in which the basic format conversion definition information is described.

  FIG. 12 is a diagram illustrating a configuration example of a setting link information table constituting the basic format conversion file DB. The setting link information table 212 is a table for managing information related to the association (link) of each data item or the like between the conversion source and the conversion destination. One record in the setting link information table 212 represents one link (for example, each of l1, l2, l3, l4, and l5 in FIG. 8), and includes a basic format conversion definition ID, a link ID, a link source object type, It consists of items such as a link source object ID, a link destination object type, and a link destination object ID.

  The basic format conversion definition ID is the basic format conversion definition ID of the basic format conversion definition information in which the link is defined. A plurality of links can be defined in one basic format conversion definition information. The link ID is an ID for identifying each link and is automatically numbered.

  The link source object type is information indicating the type of the conversion source object (link source) among the objects to be linked. The object type includes a format definition item, a function, or a constant. The link source object ID is an ID for identifying the link source object, and an item ID, a function ID, or a constant ID is registered according to the type of the object. The item ID is the item ID of the format definition item. The function ID and constant ID are IDs assigned to identify each function or constant in a setting function item table or setting constant item table described later.

  The link destination object type is information indicating the type of a conversion destination object (link destination) among objects to be linked. The link destination object ID is an ID for identifying the link destination object.

  FIG. 13 is a diagram showing a configuration example of a setting function item table constituting the basic format conversion file DB. The setting function item table 213 is a table for managing information (function information) related to a function interposed between the conversion source and the conversion destination. One record in the setting function item table 213 represents one function, and includes items such as a basic format conversion definition ID, a function ID, an abstraction flag, a function definition ID, and a function name.

  The basic format conversion definition ID is the basic format conversion definition ID of the basic format conversion definition information in which the function is defined. A plurality of functions can be defined in one basic format conversion definition information. The function ID is an ID for identifying each function and is automatically assigned. The abstract flag is a flag indicating whether or not the function is an abstract item. The function definition ID is an ID assigned to identify each definition content in the function definition DB 23 in which the function definition content is managed. That is, here, the function is merely associated with the definition content, and the actual definition content is not managed. The function definition ID is treated as invalid when the abstraction flag is ON. This is because the specific definition contents in the case of abstraction are defined by individual format conversion files derived from the basic format conversion file. The function name is the function name of the function. However, when the abstraction flag is OFF, this value is treated as invalid.

  FIG. 14 is a diagram showing a configuration example of a setting constant item table constituting the basic format conversion file DB. The set constant item table 214 is a table for managing information (constant information) related to constants set in the conversion destination. One record in the set constant item table 214 represents one constant, and includes items such as a basic format conversion definition ID, a constant ID, an abstraction flag, a constant value, and a constant name.

  The basic format conversion definition ID is the basic format conversion definition ID of the basic format conversion definition information in which the constant is defined. A plurality of constants can be defined in one basic format conversion definition information. The constant ID is an ID for identifying each constant and is automatically assigned. The abstract flag is a flag indicating whether or not the constant is an abstract item. The constant value is the value of the constant. However, the constant value is treated as invalid when the abstraction flag is ON. This is because when the abstraction flag is ON, specific values are defined in individual format conversion files. The constant name is the constant name of the constant. However, when the abstraction flag is OFF, this value is treated as invalid.

  FIG. 15 is a diagram showing a configuration example of an abstract item management table that constitutes the basic format conversion file DB. The abstract item management table 215 is a table for managing information related to abstract items set in the basic format conversion definition information. One record in the abstract item management table 215 represents one abstract item, and includes items such as a basic format conversion definition ID, abstract item ID, target ID, abstract item type, and abstract item name. The

  The basic format conversion definition ID is the basic format conversion definition ID of the basic format conversion definition information in which the abstract item is set. A plurality of abstract items can be set in one basic format conversion definition information. The abstract item ID is an ID for identifying each abstract item. The target ID is an ID for specifying an object that is an abstract item, and an item ID (FIG. 10), a function ID (FIG. 13), or a constant ID (FIG. 14) is registered. The abstract item type is information indicating the type of the abstract item (item name, function, or constant). The abstract item name is the name of the abstract item.

  The function definition DB 23 (FIG. 6) will be described. FIG. 16 is a diagram illustrating a configuration example of a function definition table constituting the function definition DB. The function definition table 231 is a table for managing function definition contents. One record in the function definition table 231 corresponds to one function and includes items such as a function definition ID, a function name, and function definition contents.

  The function definition ID is an ID for identifying each definition content and is automatically assigned. The function name is the function name of the function related to the definition content. The function definition content is the function definition content itself. The description language is not limited to a predetermined language.

  The abstract item setting DB 24 (FIG. 6) will be described. FIG. 17 is a diagram illustrating a configuration example of an abstract item setting information table constituting the abstract item setting DB. The abstract item setting information table is a table for managing values set for the abstract items in the basic format conversion definition information. One record in the abstract item setting information table 241 corresponds to setting information for one abstract item, and includes a basic format conversion definition ID, an abstract item setting ID, an abstract item ID, an abstract item setting value, and an output flag. It consists of items such as.

  The basic format conversion definition ID is the basic format conversion definition ID of the basic format conversion definition information in which the corresponding abstract item is set. The abstract item setting ID is an ID for identifying setting information of each abstract item, and is automatically assigned. The abstract item ID is an abstract item ID in the abstract item management table 215 (FIG. 15), and is used to specify the corresponding abstract item. The abstract item setting value is a value set for the abstract item. The output flag is a flag indicating whether or not the abstract item is to be converted in a specific format conversion file.

  The format conversion file DB 25 (FIG. 6) will be described. FIG. 18 is a diagram illustrating a configuration example of a format conversion file management table constituting the format conversion file DB. The format conversion file management table 251 is a table for managing information related to a specific format conversion file for each cooperative system. One record in the format conversion file management table 251 represents one format conversion file and includes items such as a basic format conversion definition ID, an abstract item setting ID, a format conversion file, and a use system name.

  The basic format conversion definition ID is a basic format conversion definition ID for identifying basic format conversion definition information used as a template of the format conversion file. The abstract item setting ID is an abstract item setting ID for specifying the abstract item setting information (FIG. 17) referred to when the format conversion file is created. The format conversion file is actual data of the format conversion file. The use system name is the system name of the linkage system that uses the format conversion file.

  Hereinafter, the processing procedure of the format conversion file creation device 10 of FIG. 6 will be described. FIG. 19 is a flowchart for explaining an example of processing outline when a format conversion file is created or reused in the format conversion file creation device.

  For example, when the user wants to newly link another system to the integrated DB, the cooperation is realized by the following processing.

  First, the basic format conversion file evaluation unit 12 performs an evaluation (reusability evaluation) on the appropriateness of reuse for an existing basic format conversion file registered in the basic format conversion file DB 21 (FIGS. 11 to 15). The evaluation result is presented to the user (S11). If there is no basic format conversion file suitable for reuse (No in S13), the basic format conversion file editing unit 11 creates a new basic format conversion file or corrects an existing basic format conversion file (S15). ). The basic format conversion file editing unit 11 registers definition information or the like of the created or modified basic format conversion file in the basic format conversion file DB 21 and the function definition DB 23 (FIG. 16).

  When there is a reusable basic format conversion file (Yes in S13) or following step S15, the abstract item setting unit 13 sets a value (abstract) corresponding to the cooperation system in the abstract item in the basic format conversion file. Set the generalization item setting value). The abstract item setting unit 13 registers setting information for the abstract item in the abstract item setting DB 24 (FIG. 17). In addition, the format conversion file management unit 14 applies the setting value to the abstract item in the basic format conversion file based on the abstract item setting DB 24 and the basic format conversion file DB 21, so that the format corresponding to the cooperation system is used. A conversion file is generated (S17). The format conversion file management unit 14 registers the generated format conversion file in the format conversion file DB 25 (FIG. 18).

  Thereafter, information indicating the usage status of the format conversion file is registered by the format conversion file management unit 14 (S19).

  In FIG. 19, the basic format conversion file is initially evaluated (S11). However, the basic format conversion file may be newly created (S15) at the user's discretion.

  Next, details of each step in FIG. 19 will be described. First, the new creation or correction process of the basic format conversion file in step S15 will be described.

  The operation method of the basic format conversion file editing screen 110 will be described with reference to FIG. In FIG. 8, the basic format conversion file editing screen 110 has a basic format conversion file selection box 1101, an edit button 1102, a delete button 1103, a new creation button 1104, etc. arranged above it, and the conversion source format is displayed in the edit frame 1105. A display area 1106, a conversion destination format display area 1107, an item addition button 1108, a function addition button 1109, a constant addition button 1110, a function definition button 1111, an edit button 1112, a delete button 1113, an abstract button 1114, a save button 1115, and the like. Has been placed.

  The basic format conversion file selection box 1101 is a combo box having a pull-down list for displaying a list of file names of basic format conversion files already registered in the basic format conversion file DB 21, and the basic format conversion file to be corrected is selected. This is for selection. The basic format conversion file selected here is hereinafter referred to as a “current basic format conversion file”.

  When the edit button 1102 is clicked, the basic format conversion file editing unit 11 acquires the definition information of the current basic format conversion file from the basic format conversion file DB 21 and displays it on the edit frame 1105.

  When the delete button 1103 is clicked, the basic format conversion file editing unit 11 deletes the definition information of the current basic format conversion file from the basic format conversion file DB 21.

  When the new creation button 1104 is clicked, the basic format conversion file editing unit 11 displays a new creation / editing dialog.

  FIG. 20 is a diagram illustrating a display example of a new creation / editing dialog. 20, the new creation / editing dialog 31 includes a file name input area 311, an input / output type selection box 312, an integrated DB side format definition selection box 313, and the like. Via these components, the file name of the basic format is input (311), whether or not the file is a basic format conversion file for input or output (312), and the integrated DB side to be linked is selected. A format definition is selected (313). Further, when the registration button 314 is clicked, the basic format conversion file editing unit 11 reflects the setting contents in the new creation / editing dialog 31 on the basic format conversion file editing screen 110.

  FIG. 21 is a diagram showing a display example of the basic format conversion file editing screen in which the setting contents of the new creation / editing dialog are reflected.

  As shown in FIG. 21, the input file name is added to the pull-down list of the basic format conversion file selection box 1101 to be selected. Further, the format definition of the integrated DB is acquired from the format definition DB 22, and the conversion format format display area 1107 or the conversion source format definition conversion source format display area is selected depending on whether the newly created basic format conversion file is input or output. 1106 is displayed. That is, when the newly created basic format conversion file is for input, the integrated DB is the conversion destination, and when the newly created basic format conversion file is for output, the integrated DB is the conversion source.

  In this state, the user drags and drops one of the format definition items of the conversion destination data format displayed in the tree in the conversion destination format display area 1107 to the conversion source format display area 1106 to thereby convert the conversion destination and the conversion source. Basic format conversion definition information can be created easily.

  FIG. 22 is a diagram for explaining an editing operation by drag and drop of a conversion destination data format. When the format definition item “employee information” of the conversion destination data format is dragged and dropped into the conversion source data format display area 1106, the basic format conversion file editing screen 110 is displayed as shown in FIG. Is as shown in FIG.

  That is, the data format below the dropped format definition item “employee information” is copied to the conversion source data format display area 1106 as it is. As a result, the format definition of the conversion source (that is, the cooperation system) is automatically made (S15a).

  Further, links are set between corresponding format definition items at the copy destination and the copy source. This automatically associates the format definition item between the conversion source and the conversion destination (S15b).

  Also, a link with a function or constant is automatically set (S15c, S15d).

  In the conversion source data format display area 1106, all format definition item names are displayed enclosed in parentheses. This indicates that the item name of each format definition item is an abstract item by default. This is because the basic format conversion file is created.

  The method of realizing the function described in FIG. 22, that is, the process executed by the basic format conversion file editing unit 11 in response to the drag and drop of the format definition item will be described.

  FIG. 23 is a flowchart for explaining processing when a format definition item is dragged and dropped. Here, the case where the conversion destination is the integrated DB (in the case of input) will be described with reference to FIG. 22, but the case where the conversion source is the integrated DB can be performed by substantially the same processing.

  When the format definition item is dragged and dropped between the conversion source data format display area 1106 and the conversion destination data format display area 1107, the basic format conversion file editing unit 11 reads the format definition item (hereinafter “ A copy of definition information (referred to as “current copy source item”) in FIG. 10 is created in the memory, and this definition information copy is defined as definition information of the format definition item of the copy destination (hereinafter referred to as “current copy destination item”). (S150).

  However, for the format definition ID, item ID, parent item ID, and item name abstraction flag in the definition information, the value of the copy source is not used as it is. That is, the format definition ID is replaced with the format definition ID on the cooperation system side. The item ID is newly assigned a value on the cooperation system side. Also, the parent item ID is replaced with the ID of the parent item on the cooperation system side or is set to a NULL value. The item name abstraction flag is initialized to ON (abstraction).

  Subsequently, the basic format conversion file editing unit 11 converts all the existing basic format conversion definition information (that is, the reference of the basic format conversion file to be created from now on) whose conversion target is the data format of the integrated DB to be linked. The basic format conversion definition ID of the basic format conversion definition information that is likely to become) is extracted from the basic format conversion definition table (FIG. 11), and a list thereof is created (S151). That is, the list of basic format conversion definition IDs (FIG. 11) of the basic format conversion definition information whose conversion destination format definition ID (FIG. 11) matches the format definition ID (FIG. 9) of the integrated DB that is currently the copy source. Is created.

  If the list created in step S151 is not empty (No in S152), that is, if there is basic format conversion definition information that already converts the same data format, the basic format conversion file editing unit 11 Based on the list of basic format conversion definition IDs, a list of path information (link links) of conversion performed in the existing basic format conversion definition information is created for the current copy source item (S153). More specifically, the setting link information table 212 (FIG. 12) is referred to for each basic format conversion definition ID included in the list, and the link information whose link destination object ID indicates the current copy source item is searched. Further, the link destination is specified by the link source object ID in the searched link information.

  For example, when the current copy source item is “employee information” (FIG. 22), the link l11 specifies that the link source is (employee information). When the current copy source item is “employee sex”, the function f1 is specified as the link source by the link l15. Further, the link 114 that uses the function f1 as the link destination object specifies that (employee sex) is the most upstream link source in the path starting from the current copy source item “employee sex”.

  Therefore, such a link connection is created for each basic format conversion definition information as route information.

  Subsequently, the basic format conversion file editing unit 12 determines whether or not the order of the types (items, functions, and constants) of the objects that pass through all match in the path information created for each basic format conversion definition information. (S154). That is, in the existing basic format conversion definition information, it is determined whether the conversion contents for the current copy source item are all the same.

  When the types of objects passed through in the route information are the same, the route information obtained from the existing basic format conversion definition information is copied onto the memory as route information connecting the current copy source item and the current copy destination item (S155). . That is, when link information (FIG. 12) and a function or constant are included in the path, function item information (FIG. 13), constant item information (FIG. 14), etc. are copied.

  That is, the function information and constant information set in the past are used as they are for the basic format definition of this time, so that the functions and constants are automatically set. However, when copying a route, if the setting value of the object to be copied is not the same in all routes, or if the abstraction flag is not OFF in all routes, the route information is copied. Functions and constants are abstract items (the abstract flag is turned ON). Since functions and constants cannot be uniquely determined, they are set as abstract items, and the contents are left to the user's judgment when creating a specific format conversion file.

  On the other hand, if the types of objects in the route information do not match completely, for example, if the route contains functions and constants and those that do not contain them, it is common Since no correct route is determined, the route information is not copied.

  If the types of objects present in all paths are not the same in step S155 or step S154, the process proceeds to step S156, where it is determined whether the format definition of the current copy destination item copied in step S150 needs to be updated. Specifically, if the object that is the starting point of the route is a constant instead of an item, or if the data type and data length of the format definition of the copy destination item are the same for all routes, there is no need to update the format definition. to decide. In other cases, the process proceeds to S157, and the data format definition is updated. Specifically, if the data types of the copy destination items in the route information are all the same and the data lengths of the copy destination items in the route are different, the data type is set to the copy destination item in the route information. Set to the data type, and the data length is set to the maximum value of the data length of the copy destination item in the path information. In other cases, data in the memory of the data type and data length of the current copy destination item is set to an unset state and updated.

  If it is not necessary to update the format definition in step S157 or S156, the process proceeds to step S158, and the basic format conversion file editing unit 12 determines whether the current copy source item is a hierarchy or a terminal. If it is a hierarchy, the format definition items below it are also recursively processed (S15A). If it is at the end, the processing ends.

  On the other hand, if the list of basic format conversion definition IDs is empty at step S152, that is, if there is no reference, the conversion unit 12 links the current copy source item and the current copy destination item. Information (FIG. 12) is generated on the memory (S159). Thereafter, the processing after step S158 is executed.

  Based on the various types of information created on the memory by the above processing, the display described in FIG. 22 is made.

  Other functions of the basic format conversion file editing screen 110 will be described (FIG. 8).

  When any format definition item (node) is selected in the conversion source format display area 1106 or the conversion destination format display area 1107 and the item addition button 1108 is clicked, the basic format conversion file editing unit 11 displays the item edit dialog. Is displayed.

  FIG. 24 is a diagram illustrating a display example of the item edit dialog. The user adds the item name (321), item type (322), data type (323), data length (324), sort order (325), abstract flag ( 326) can be set. When the registration button 327 is clicked, the basic format conversion file editing unit 11 holds the definition information (FIG. 10) of the format definition item set in the item edit dialog 32 on the memory, and corresponds to the format definition item. The node is added to the conversion source format display area 1106 or the conversion destination format display area 1107. At this time, if the selected node is a terminal, a new node is added to the same hierarchy as the selected node, and if the selected node is a hierarchy, a new node is added below that hierarchy.

  When the function addition button 1109 is clicked on the basic format conversion file editing screen 110, the basic format conversion file editing unit 11 displays a function editing dialog.

  FIG. 25 is a diagram illustrating a display example of the function editing dialog. The user can set an abstraction flag (331), a function (332), and a function name (333) in the function editing dialog 33. In the function, the function name acquired from the function definition table 231 is set as a combo box option. However, the function can be selected only when the abstraction flag is set to OFF. The function name can be input only when the abstraction flag is set to ON. When the registration button 334 is clicked, the basic format conversion file editing unit 12 stores the function information (FIG. 13) set in the function editing dialog 33 on the memory, and displays a rectangle indicating the function (hereinafter, “function box”). Is displayed on the basic format conversion file editing screen 110 (for example, a rectangle indicating the function f1).

  When a constant addition button 1109 is clicked on the basic format conversion file editing screen 110, the basic format conversion file editing unit 11 displays a constant editing dialog.

  FIG. 26 is a diagram illustrating a display example of the constant editing dialog. The user can set an abstraction flag (341), a constant value (342), and a constant name (343) in the constant editing dialog 34. However, the constant value can be input only when the abstraction flag is set to OFF. The constant name can be input only when the abstraction flag is set to ON. When the registration button 344 is clicked, the basic format conversion file editing unit 12 stores the constant item information (FIG. 14) set in the constant editing dialog 34 in the memory, and displays a rectangle indicating the constant (hereinafter, “constant box”). It is displayed on the basic format conversion file editing screen 110 (for example, a rectangle indicating the constant c1).

  When the function definition button 1111 is clicked on the basic format conversion file editing screen 110, the basic format conversion file editing unit 11 displays a function definition editing dialog.

  FIG. 27 is a diagram illustrating a display example of the function definition editing dialog. In the function definition editing dialog 35, the user can input a function name (351, 352) and define a function (353). Regarding the input of a function name, a combo box 351 can be selected from existing function names. When the new registration button 352 is clicked, the combo box changes to a text box, and a new function name can be entered in the text box. In the former case, the function definition corresponding to the existing function name is acquired from the function definition table 231 and displayed in the function definition area 353. When the registration button 354 is clicked, the basic format conversion file editing unit 11 stores the function definition information (FIG. 16) set in the function definition editing dialog 35 on the memory, and the function definition ID is selected. Is substituted for the function definition ID of the function information (FIG. 13) on the memory related to the function box.

  When the edit button 1112 is clicked with the format definition item (node), function box, or constant box selected on the basic format conversion file editing screen 110, the basic format conversion file editing unit 11 edits the selected object. A dialog (FIG. 24, FIG. 25, or FIG. 26) is displayed. Therefore, the user can correct the information once set. The modified content is reflected on the screen and the format definition item information (FIG. 10), function item information (FIG. 13) or constant item information (FIG. 14) on the screen and by the basic format conversion file editing unit 11. The

  When the delete button 1113 is clicked on the basic format conversion file editing screen 110, the basic format conversion file editing unit 11 displays the format definition item information on the memory corresponding to the selected format definition item, function, constant, or link. (FIG. 10), function item information (FIG. 13), constant item information (FIG. 14), or link information (FIG. 12) is deleted from the memory, and nodes, function boxes, and constant boxes displayed on the screen. Or delete the link from the screen.

  When the abstract button 1114 is clicked on the basic format conversion file editing screen 110, the basic format conversion file editing unit 11 displays format definition item information on the memory corresponding to the selected format definition item, function or constant (see FIG. 10) The abstraction flag of the function item information (FIG. 13) and constant item information (FIG. 14) is switched ON / OFF, and the display is updated.

  When drag and drop is performed between the format definition item node, function box or constant box on the basic format conversion file editing screen 110, the basic format conversion file editing unit 12 links the dropped object to the dragged object. Create That is, link information (FIG. 12) corresponding to the link is generated on the memory, and an arrow indicating the link is displayed between the objects.

  When the save button 1115 is clicked on the basic format conversion file editing screen 110, the basic format conversion file editing unit 11 executes a basic format conversion file creation process based on various types of information stored in the memory.

  FIG. 28 is a flowchart for explaining a basic format conversion file creation process by the basic format conversion file editing unit.

  First, format definition information and basic format conversion definition information on the cooperative system side in the memory are registered in the format definition DB 22 or the basic format conversion file DB 21 (S161).

  Subsequently, a basic format conversion file is generated based on the basic format conversion definition information on the memory (S162). That is, based on each link information, the basic format conversion file is generated so that the link source (conversion source) value is registered as the link destination (conversion destination) value. At this time, when the link source is a constant value, the constant value is defined to be registered in the conversion destination. In addition, when a function is present in the link, it is defined that the result of processing the conversion source value by the function is registered in the conversion destination. As such, the generated basic format conversion file is shown in FIG. 29, for example.

  FIG. 29 is a diagram illustrating a definition example of a basic format conversion file. 29, the basic format conversion file 5031 corresponds to the definition content in the basic format conversion file editing screen 110 of FIG.

  The basic format conversion file 5031 conforms to the following description format unique to the present embodiment.

  (1) Basically, it is described by repeating “conversion destination path = value;”.

(2) The following functions can be used as built-in functions: • value (“path”): The value of data existing in that path is output.
-Func ("Function processing", argument): The result of processing the value given to the argument by "Function processing" is output.
• cons (“value”): The value indicated by “value” is output.

  (3) The abstract item is described as follows.

Item name: Abstract_Name (% item ID)
Function: Abstract_Func (% function ID)
Constant: Abstract_Cons (% constant ID)
From the above, it can be seen that the following is defined in the basic format conversion file 5031.

  The value of “/ Juyokyoin / (item with abstract item name abstracted = 1)” in the linkage system is “/ employee list / employee information / employee name” in the integrated DB. It is registered (5031a).

  The value of “/ Juyokyoin / (item with abstract item name abstracted = 2)” in the linkage system is “/ employee list / employee information / employee code” in the integrated DB. It is registered (5031b).

  The value output from the abstract function with function ID = 1, using the value of “/ Jugyoin / Seibetsu” in the linkage system as an argument is “/ employee list / employee information / employee gender” in the integrated database. (5031c).

  The constant value of the constant ID = 1 is registered in “/ employee list / employee information / sort order” of the integrated DB (5031d).

  FIG. 30 is a diagram illustrating a definition example of a basic format conversion file by XSLT. FIG. 30A shows a basic format conversion file 5032 in which the same definition as FIG. 29 is made by XSLT. In the basic format conversion file 5032 of FIG. 30, the same reference numerals are given to the portions corresponding to FIG. 29, and description thereof is omitted.

  FIG. 30B shows XML data 5033 in the conversion source data format, and XML data 5034 in the conversion destination data format as a result of conversion of the XML data 5033 by the basic format conversion file 5032. .

  In the basic format conversion file 5032, the abstract items are described as follows.

Item name: Abstract_Name (% item ID)
Function: Abstract_Func (% function ID)
Constant: Abstract_Cons (% constant ID)
Further, regarding the abstracted function, the specific processing contents are not described in the basic format conversion file.

  As shown in the example of FIG. 29, the description format of the basic format conversion file is not limited to XSLT. However, XML and XSLT are generally used as already established technologies, and libraries for handling documents described in XML or XSLT are enriched. XML also has a high affinity with the Internet. From this viewpoint, there is an advantage of adopting XML and XSLT.

  Subsequently, the generated basic format conversion file is registered in the basic format conversion definition table 211 (FIG. 11) (S163). Subsequently, the abstract item setting information on the memory is registered in the abstract item management table 215 (FIG. 15) (S164), and the process ends.

  Next, reusable basic format conversion file evaluation processing in step S11 (FIG. 19) will be described.

  The basic format conversion file evaluation unit 12 provides a screen (hereinafter referred to as a “basic format conversion file evaluation screen”) for providing an evaluation function regarding whether or not to reuse an existing basic format conversion file registered in the basic format conversion file DB 21. .) Is displayed on the display device 105.

  FIG. 31 is a diagram showing a display example of the basic format conversion file evaluation screen. In FIG. 31, a basic format conversion file evaluation screen 120 includes an overall DB format selection box 121, an integrated DB format display area 122, an evaluation start button 123, an input format conversion file evaluation result display area 124, and an output format conversion file evaluation. It consists of a result display area 125 and the like. FIG. 31 shows a state in which information is displayed in each area. In the initial state immediately after display of the basic format conversion file evaluation screen 120, each area is blank.

  The integrated DB format selection box 121 is a combo box for selecting an integrated DB format definition to be linked. When an integrated DB format definition is selected in the integrated DB format selection box 121, the basic format conversion file evaluation unit 12 formats the definition information of the selected format definition (hereinafter referred to as “integrated DB format definition”) as a format definition. Acquired from the DB 22 and displays the acquired definition information in the integrated DB format display area 122 in a tree structure.

  The user can select a format definition item to be linked with the linkage system in the integrated DB format display area 122. That is, a check button is arranged for each format definition item, and by checking the check button, the format definition item can be set as a cooperation target. In the figure, “name”, “age”, “contact”, “telephone number”, “extension number”, and “FAX” are to be linked. The format definition item selected here is hereinafter referred to as “cooperation target item”.

  When the evaluation start button 123 is clicked, the basic format conversion file evaluation unit 12 evaluates whether or not the cooperation of the cooperation target items is appropriate for all the basic format conversion files registered in the basic format conversion file DB 21 for input. The evaluation result for the format conversion file is displayed in the input format conversion file evaluation result display area 124, and the evaluation result for the output format conversion file is displayed in the output format conversion file evaluation result display area 125. As shown in the figure, the number of uses, surplus items, deficient items, processing time, evaluation values, evaluation comments, and the like are displayed for each basic format conversion file as evaluation results.

  The number of uses indicates the total number of systems using the basic format conversion file. As the number of uses increases, it can be estimated that the use record is high and the reliability is high.

  The surplus item indicates the number of format definition items that the basic format conversion file can cooperate with in addition to the cooperation target item. The larger the number of surplus items, the higher the expandability, that is, the higher the adaptability when a new data item needs to be converted.

  The missing item indicates the number of items that cannot be linked to the basic format conversion file among the items to be linked. Existence of missing items means the necessity of correcting the basic format conversion file so that the missing items can be linked.

  The processing time indicates the processing time when conversion is performed using the basic format conversion file. The shorter the processing time, the higher the performance can be inferred.

  The evaluation value is a numerical value representing the result of combining the above evaluation items. The higher the evaluation value, the more suitable for reuse.

  The comment expresses the result of integrating the above evaluation items as a message easy for the user to understand.

  A lamp 1241 is displayed in front of the file name of each basic format conversion file. The lamp 1241 is displayed by being color-coded according to the evaluation value, and indicates the recommended degree of the basic format conversion file to the user. For example, the lamp 1241 is displayed in blue when it is optimal, yellow when it is suitable, and red when it is not suitable.

  The user can appropriately and easily determine a basic format conversion file suitable for reuse based on the above evaluation results.

  Hereinafter, a process executed when the evaluation start button 123 is clicked will be described. FIG. 32 is a flowchart for explaining basic format conversion file evaluation processing by the basic format conversion file evaluation unit.

  First, a list of basic format conversion definition information for input and output linked with the format definition selected in the integrated DB format selection box 121 is acquired from the basic format conversion definition table 211 (FIG. 11) ( S111).

  Subsequently, one basic format conversion definition information is sequentially processed from the acquired list (S112). Here, the basic format conversion definition information to be processed is hereinafter referred to as “current conversion definition information”.

  Subsequently, records belonging to the current conversion definition information (records related to the basic format conversion definition ID of the current conversion definition information) are extracted from the format conversion file management table 251 (FIG. 18), and the number of the extracted records is the usage system. It is set as a number (S113).

  Subsequently, among the format definition items in the format definition of the integrated DB, a list of format definition items to be converted by the current conversion definition information is generated (S114). That is, when the current conversion definition information is for input, the links from the format definition items of the integrated DB-side format definition are reversed (from the link destination to the link source) based on the link information (FIG. 12) belonging to the current conversion definition information. As a result, a list of items finally reaching the format definition items on the cooperation system side is generated.

  If the current definition information is for output, the links from the format definition items of the integrated DB-side format definition are forwarded (from the link source to the link destination) based on the link information (FIG. 12) belonging to the current conversion definition information. Finally, a list of items that finally reach the format definition items on the cooperation system side is generated.

  Subsequently, the excess items and the deficient items are calculated by determining whether the list of format definition items to be converted by the current conversion definition information and the items to be linked are excessive or deficient (S115).

  Subsequently, the format definition on the input side for the current conversion definition information is acquired from the format definition table 221 (FIG. 9) and the format definition item table 222 (FIG. 10) (S116). Here, when the current conversion definition information is for input, the input side is the cooperative system side. When the current conversion definition information is for output, the input side is the integrated DB side.

  Subsequently, test data based on the format definition on the input side is generated for the current conversion definition information (S117). Note that, for the item name that is an abstract item in the format definition, a character string as the item ID of the item is used as a dummy item name.

  Subsequently, actual data of the basic format conversion file related to the current conversion definition information is acquired from the basic format conversion definition table 211 (FIG. 11), and based on the actual data, the format conversion for testing in which the abstract item is dummyized A file is created (S118). That is, the item name that is an abstract item is replaced with the character string of the item ID. Further, the function name of the function that is an abstract item is replaced with a character string of the function ID, and the function definition content is replaced with an output value as it is. In addition, the constant value that is an abstract item is replaced with the character string of the constant ID.

  Subsequently, the test data generated in step S117 is converted using the test format conversion file generated in step S118 (S119). At this time, the processing speed is measured.

  Subsequently, an evaluation value is calculated based on the surplus items, the deficient items, and the processing speed calculated in the above, and an evaluation comment is selected (S120).

  The evaluation value is calculated based on the following equation, for example.

Evaluation value = standard constant + surplus item rate × α− (shortage item rate × β + processing time × γ)
here,
Surplus item rate = number of surplus items / number of items to be linked Insufficient item rate = number of missing items / number of items to be linked.

  The above formula indicates that the evaluation value increases as the number of surplus items increases. This indicates that high scalability is determined as a positive element. Moreover, it shows that an evaluation value becomes low, so that there are many lacking items. This indicates that an increase in the correction amount is determined as a negative factor. Moreover, it shows that an evaluation value becomes low, so that processing time is long. This indicates that low performance is determined as a negative factor.

  The reference constant is a constant that serves as a reference for the evaluation value, and may be set arbitrarily. Further, α (surplus item coefficient), β (insufficient item coefficient), and γ (processing time coefficient) may be arbitrarily set.

  The evaluation comment is selected from the following tables stored in advance in the auxiliary storage device 102. FIG. 33 is a diagram illustrating a configuration example of an evaluation comment management table. In FIG. 33, an evaluation comment management table 1201 manages evaluation comments for each combination of a missing item rate (high, low, no), a surplus item rate (high, low, no), and a processing time (short, medium, long). Has been. Therefore, an evaluation comment is selected based on the missing item rate, the surplus item rate, and the processing time. In the table, “/” means OR, and “−” means that any value is applicable.

  Subsequently, the surplus item, the deficient item, the processing degree, the evaluation value, and the evaluation comment are displayed in the input format conversion file evaluation result display area 124 or the output format conversion file evaluation result display area 125 (S121).

  Subsequently, it is determined whether or not the processing has been completed for all the basic format conversion definition information lists generated in step S111 (S122). If processing has not been completed for all, the remaining basic format conversion definition information is evaluated. If the process is completed for all, the process ends.

  When the setting button 1242 is clicked on the basic format conversion file evaluation screen 120, the basic format conversion file evaluation unit 12 displays the integrated DB that is the conversion target in the basic format conversion file for which the setting button 1242 is clicked. The format definition item is checked in the integrated DB format display area 122. In this state, when the evaluation start button 123 is clicked, the processing described in FIG. 32 is executed. Therefore, for example, when the setting button 1242 is clicked for the output basic format file, the user can obtain an evaluation for each input format conversion file regarding the suitability of the output basic format file. Specifically, when the “XX sales” setting button 1242 for output is clicked, the format definition items on the integrated DB output by the output basic format conversion file related to “XX sales” are checked. . When the evaluation start button 123 is clicked in this state, an evaluation regarding the suitability of cooperation with the format definition item output by “XX sales” is displayed.

  Next, abstract item setting and format conversion file creation processing in step S17 (FIG. 19) will be described.

  The abstract item setting unit 13 sets a specific value for the abstract item and a screen for creating a specific format conversion file corresponding to an individual linkage system (hereinafter referred to as “abstract item setting screen”). ) Is displayed on the display device 105.

  FIG. 34 is a diagram illustrating a display example of the abstract item setting screen. 34, an abstract item setting screen 170 includes a basic format conversion file selection box 171, a use system name selection box 172, an edit button 173, a new creation button 174, a delete button 175, an abstract item setting area 176, and a save button. 177 and the like.

  The basic format conversion file selection box 171 is a combo box for selecting basic format conversion definition information (basic format conversion file) to be set as an abstract item. The basic format conversion definition information selected here is hereinafter referred to as “current conversion definition information”.

  The used system name selection box 172 is a combo box for selecting a system name that uses a format conversion file in which a specific value is set in an abstract item from existing system names. When the use system name is selected from existing system names, the existing format conversion file is modified.

  When the new creation button 174 is clicked, the use system name selection box 172 changes to a text box, and a new system name can be input. When the delete button 175 is clicked, the format conversion file management unit 14 deletes from the format conversion file management table 251 the format conversion file whose name is entered in the usage system selection box 172. When the edit button 173 is clicked, the abstract item setting unit 13 and the format conversion file management unit 14 execute the following processing.

  FIG. 35 is a flowchart for explaining abstract item setting processing by the abstract item setting unit and format conversion file creation processing by the format conversion file management unit.

  In step S171, the abstract item setting unit 13 creates a list of abstract item information belonging to the current conversion definition information from the abstract item management table 215 (FIG. 15) based on the basic format conversion definition ID of the current conversion definition information. get.

  Subsequently, the abstract item setting unit 13 displays a list of abstract item setting information belonging to the current conversion definition information based on the basic format conversion definition ID of the current conversion definition information, as an abstract item setting information table 241 (FIG. 17). (S172). However, in the case of new creation, since abstract item setting information does not exist, an empty list is acquired here.

  Subsequently, based on the acquired list of abstract item information and the list of abstract item setting information, the abstract item setting unit 13 outputs an abstract item output flag, an abstract item name, The item type, setting value, and the like are displayed in the “valid”, “abstracted item”, “item type”, and “setting value” fields of the abstract item setting area 176 (S173). However, in the case of new creation, the output flag and set value are not displayed.

  Subsequently, the user inputs an output flag and a set value (FIG. 34). If the item name is abstracted, a specific item name is set (1762). If the constant value is abstracted, a specific constant value is input (1763). If the function is abstracted, a specific function is selected from the function definition table 231 (FIG. 16) (1764). Also, the user can select whether or not the abstract item is to be output to the format conversion file by checking the “valid” column (1761). That is, by converting only the format definition items required in the format conversion file in the target use system, not all the format definition items that are converted in the basic format conversion file. , Conversion speed can be improved.

  When necessary items are input and the save button 177 is clicked by the user, the abstract item setting unit 13 registers the setting information in the abstract item setting information table 241 (FIG. 17) (S176).

  Subsequently, the format conversion file management unit 14 acquires the basic format conversion file of the current conversion definition information from the basic format conversion definition table 211 (FIG. 11) based on the basic format conversion definition ID of the current conversion definition information (S177). ).

  Subsequently, the format conversion file management unit 14 creates an individual format conversion file in the use system based on the acquired basic format conversion file. In other words, a file obtained by applying a set value to an abstract item is output as a format conversion file. However, the portion related to the conversion process for the format conversion definition item whose output flag is OFF is not output to the format conversion file.

  FIG. 36 is a diagram for explaining a format conversion file creation process based on a basic format conversion file.

  FIG. 36 shows how a format conversion file 2501 is created based on a basic format conversion file 5031. That is, Abstract_Name (% 1) and Abstract_Name (% 2), which are abstract items of the item name in the basic format conversion file 5031, are replaced with specific item names “name” and “bango” in the format conversion file 2501. (S178a, S178b).

  Also, Abstract_Function (% 1), which is a function abstraction item in the basic format conversion file 5031, is replaced with a specific function definition in the format conversion file 2501 (S178c).

  The constant substitution process for the sort order in the basic format conversion file 5031 is not output to the format conversion file 2501 because the output flag is OFF (S178d).

  FIG. 37 is a diagram for explaining a format conversion file creation process based on a basic format conversion file by XSLT. FIG. 37 shows how a format conversion file 2502 based on XSLT is created based on a basic format conversion file 5032 based on XSLT.

  Each step number in FIG. 37 corresponds to FIG. That is, Abstract_Name (% 1) and Abstract_Name (% 2), which are abstract items of the item name in the basic format conversion file 5031, are replaced with specific item names “name” and “bango” in the format conversion file 2501. (S178a, S178b).

  Also, Abstract_Function (% 1), which is a function abstraction item in the basic format conversion file 5031, is replaced with a specific function definition in the format conversion file 2501 (S178c).

  The constant substitution process for the sort order in the basic format conversion file 5031 is not output to the format conversion file 2501 because the output flag is OFF (S178d).

  Subsequently, the format conversion file management unit 14 registers the created format conversion file in the format conversion file management table 251 (FIG. 18) and ends the process.

  As described above, according to the format conversion file creation device 10 in the embodiment of the present invention, the work required for creating a new format conversion file is automated by a simple operation of drag and drop. Man-hours for format conversion files can be greatly reduced.

  In addition, since the basic format conversion file is automatically evaluated, the work required for the evaluation can be reduced, and non-skilled developers can easily select a basic format conversion file suitable for reuse. Can do.

  In addition, since a specific format conversion file template such as a basic format conversion file is created, a plurality of similar format conversion files can be easily generated from one basic format conversion file.

  That is, conventionally, in order to create a similar format conversion file, it is necessary to analyze and correct an existing format conversion file. However, if the basic format conversion file is used, a similar format conversion file can be easily created simply by setting a value in the abstract item.

  In addition, since the management and reuse of existing resources is performed based on the basic format conversion file, the amount of resources to be selected and managed can be reduced compared to the case of individual format conversion files. Can be reduced.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to the specific embodiment which concerns, In the range of the summary of this invention described in the claim, various deformation | transformation * It can be changed.

Regarding the above description, the following items are further disclosed.
(Supplementary note 1) A conversion rule creation program for causing a computer to create definition information of conversion rules between data formats each composed of a plurality of elements each having a value,
A duplication procedure for creating at least a copy of the definition information of the first data format as the definition information of the second data format;
An association procedure for associating each element constituting the second data format with each element constituting the first data format corresponding to the copy source of each element;
A first conversion rule creation procedure for creating, as the conversion rule definition information, that any one of the associated elements is the conversion source and the other is the conversion destination, and the conversion source element value is the conversion destination element value. A conversion rule creation program characterized by comprising:
(Additional remark 2) It has the conversion rule storage procedure which accumulate | stores the definition information of a conversion rule with said 1st data format,
In the first conversion rule creation procedure, when a function or a constant is used for conversion with each element constituting the first data format in the already-stored conversion rule definition information, the function Alternatively, the conversion rule creating program according to appendix 1, wherein the conversion rule definition information includes creating a value based on a constant as a value of the element of the conversion destination.
(Additional remark 3) Said 1st conversion rule preparation procedure produces the definition information using a variable about the conversion rule of the said element of the conversion origin, and the said element of the conversion destination, The Additional remark 1 or 2 characterized by the above-mentioned. Conversion rule creation program.
(Supplementary Note 4) The conversion rule creation program according to Supplementary Note 3, wherein in the first conversion rule creation procedure, the name of the conversion source or the conversion destination element is used as a variable.
(Supplementary note 5) The supplementary note 3 or 4, wherein the first conversion rule creation procedure uses a function between the conversion source and the conversion destination or a constant assigned to the conversion destination as a variable. Conversion rule creation program.
(Additional remark 6) The input procedure which inputs the value with respect to the said variable,
The conversion created in the first conversion rule creation procedure by applying the value input in the input procedure to the variable in the conversion rule definition information created in the first conversion rule creation procedure. 6. The conversion rule creation program according to any one of appendices 3 to 5, further comprising a second conversion rule creation procedure for creating conversion rule definition information using the rule definition information as a model.
(Supplementary note 7) A conversion rule evaluation program for causing a computer to perform reusability evaluation on definition information of conversion rules between data formats each composed of a plurality of elements each having a value,
A conversion rule storage procedure for storing the conversion rule definition information;
A conversion target selection procedure for selecting an element to be converted from the elements constituting the data format to be converted or converted; and
For each of the definition information stored in the conversion rule storage procedure, an excess / deficiency determination procedure for determining an excess / deficiency between an element to be converted in the definition information and an element selected in the conversion target selection procedure When,
A conversion rule evaluation program comprising: a display procedure for causing a display device to display evaluation information based on excess / deficiency determined in the excess / deficiency determination procedure.
(Supplementary note 8) The conversion according to supplementary note 7, wherein the definition information accumulated in the accumulation procedure is defined using a variable for a conversion rule between a conversion source element and a conversion destination element. Rule evaluation program.
(Supplementary Note 9) An input procedure for inputting a value for the variable;
A conversion rule creation procedure for creating conversion rule definition information using the conversion rule definition information stored in the conversion rule storage procedure as a template by applying the value input in the input procedure to the variable. The conversion rule evaluation program according to appendix 8, characterized by comprising:
(Supplementary Note 10) For each of the definition information stored in the conversion rule storage procedure, a usage number determination procedure for determining the number of conversion rule definition information created using the definition information as a template in the conversion rule creation procedure Have
The conversion rule evaluation program according to appendix 9, wherein the display procedure includes displaying the number determined in the usage number determination procedure in the evaluation information.
(Additional remark 11) It has the processing time measurement procedure which measures the processing time of the said conversion process by performing the conversion process about each said definition information accumulate | stored in the said conversion rule accumulation | storage procedure,
The conversion rule evaluation program according to any one of appendices 7 to 10, wherein the display procedure includes displaying the processing time measured in the processing time measurement procedure in the evaluation information.
(Additional remark 12) The computer-readable recording medium which recorded the conversion rule preparation program or conversion rule evaluation program as described in any one of Additional remark 1 thru | or 11.
(Supplementary note 13) A conversion rule creation device for creating definition information of a conversion rule between data formats each composed of a plurality of elements each having a value, wherein at least a part of the definition information of the first data format is copied Replication means to create as definition information of the second data format;
Association means for associating each element constituting the second data format with each element constituting the first data format corresponding to a copy source of each element;
First conversion rule creating means for creating, as the conversion rule definition information, that one of the associated elements is the conversion source, the other is the conversion destination, and the value of the conversion source element is the value of the conversion destination element. And a conversion rule creating device.
(Supplementary Note 14) A conversion rule evaluation apparatus that evaluates reusability of conversion rule definition information between data formats each composed of a plurality of elements each having a value,
Conversion rule storage means for storing definition information of the conversion rule;
A conversion target selecting means for selecting an element to be converted from the elements constituting the data format to be converted or converted; and
For each of the definition information stored in the conversion rule storage means, an excess / deficiency determination means for determining an excess or deficiency between an element that is a conversion target in the definition information and an element that is selected by the conversion target selection means When,
A conversion rule evaluation device comprising: a display device for displaying evaluation information based on the excess / deficiency determined by the excess / deficiency determination device on a display device.
(Supplementary note 15) A conversion rule creation method for creating conversion rule definition information between data formats each composed of a plurality of elements each having a value using a computer, wherein at least part of the definition information of the first data format A duplication procedure for creating a duplication of data as definition information of the second data format;
An association procedure for associating each element constituting the second data format with each element constituting the first data format corresponding to the copy source of each element;
A first conversion rule creation procedure for creating, as the conversion rule definition information, that any one of the associated elements is the conversion source and the other is the conversion destination, and the conversion source element value is the conversion destination element value. A conversion rule creating method characterized by comprising:
(Supplementary Note 16) A conversion rule evaluation method for evaluating reusability of conversion rule definition information between data formats composed of a plurality of elements each having a value using a computer,
A conversion rule storage procedure for storing the conversion rule definition information;
A conversion target selection procedure for selecting an element to be converted from the elements constituting the data format to be converted or converted; and
For each of the definition information stored in the conversion rule storage procedure, an excess / deficiency determination procedure for determining an excess / deficiency between an element to be converted in the definition information and an element selected in the conversion target selection procedure When,
A conversion rule evaluation method comprising: a display procedure for displaying evaluation information based on excess / deficiency determined in the excess / deficiency determination procedure on a display device.

It is a conceptual diagram for demonstrating the data cooperation between systems via integrated DB. It is a conceptual diagram for demonstrating the format conversion by XSLT. It is a figure which shows the example of similar format conversion. It is a figure for demonstrating the example of the conventional new preparation work of a format conversion file. It is a figure which shows the hardware structural example of the format conversion file creation apparatus in embodiment of this invention. It is a figure which shows the function structural example of the format conversion file creation apparatus in embodiment of this invention. It is a figure for demonstrating a basic format conversion file. It is a figure which shows the example of a display of a basic format conversion file edit screen. It is a figure which shows the structural example of the format definition table which comprises format definition DB. It is a figure which shows the structural example of the format definition item table which comprises format definition DB. It is a figure which shows the structural example of the basic format conversion definition table which comprises basic format conversion file DB. It is a figure which shows the structural example of the setting link information table which comprises basic format conversion file DB. It is a figure which shows the structural example of the setting function item table which comprises basic format conversion file DB. It is a figure which shows the structural example of the setting constant item table which comprises basic format conversion file DB. It is a figure which shows the structural example of the abstract item management table which comprises basic format conversion file DB. It is a figure which shows the structural example of the function definition table which comprises function definition DB. It is a figure which shows the structural example of the abstract item setting information table which comprises abstract item setting DB. It is a figure which shows the structural example of the format conversion file management table which comprises format conversion file DB. It is a flowchart for demonstrating an example of the process outline | summary at the time of preparation of a format conversion file in a format conversion file preparation apparatus, or reuse. It is a figure which shows the example of a display of a new creation edit dialog. It is a figure which shows the example of a display of the basic format conversion file edit screen in which the setting content of the new creation edit dialog was reflected. It is a figure for demonstrating edit operation by drag and drop of the data format of a conversion destination. It is a flowchart for demonstrating the process at the time of the drag and drop of a format definition item. It is a figure which shows the example of a display of an item edit dialog. It is a figure which shows the example of a display of a function edit dialog. It is a figure which shows the example of a display of a constant edit dialog. It is a figure which shows the example of a display of a function definition edit dialog. It is a flowchart for demonstrating the creation process of the basic format conversion file by a basic format conversion file edit part. It is a figure which shows the example of a definition of a basic format conversion file. It is a figure which shows the example of a definition of the basic format conversion file by XSLT. It is a figure which shows the example of a display of a basic format conversion file evaluation screen. It is a flowchart for demonstrating the evaluation process of the basic format conversion file by a basic format conversion file evaluation part. It is a figure which shows the structural example of an evaluation comment management table. It is a figure which shows the example of a display of an abstract item setting screen. It is a flowchart for demonstrating the abstract item setting process by an abstract item setting part, and the format conversion file creation process by a format conversion file management part. It is a figure for demonstrating the creation process of the format conversion file based on a basic format conversion file. It is a figure for demonstrating the creation process of the format conversion file based on the basic format conversion file by XSLT.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Format conversion file creation apparatus 11 Basic format conversion file edit part 12 Basic format conversion file evaluation part 13 Abstraction item setting part 14 Format conversion file management part 21 Basic format conversion file DB
22 Format definition DB
23 Function definition DB
24 Abstract item setting DB
25 Format conversion file DB
DESCRIPTION OF SYMBOLS 100 Drive apparatus 101 Recording medium 102 Auxiliary storage apparatus 103 Memory apparatus 104 Arithmetic processing apparatus 105 Display apparatus 106 Input apparatus B Bus

Claims (5)

A conversion rule creation program for causing a computer to create conversion rule definition information between data formats each composed of a plurality of elements each having a value,
A duplication procedure for creating at least a copy of the definition information of the first data format as the definition information of the second data format;
An association procedure for associating each element constituting the second data format with each element constituting the first data format corresponding to the copy source of each element;
A first conversion rule creation procedure for creating, as the conversion rule definition information, that any one of the associated elements is the conversion source and the other is the conversion destination, and the conversion source element value is the conversion destination element value. A conversion rule creation program characterized by comprising: A conversion rule storage procedure for storing conversion rule definition information with the first data format;
In the first conversion rule creation procedure, when a function or a constant is used for conversion with each element constituting the first data format in the already-stored conversion rule definition information, the function The conversion rule creating program according to claim 1, wherein the conversion rule creating information includes creating a value based on a constant as a value of the element of the conversion destination as definition information of the conversion rule. The conversion rule creation according to claim 1 or 2, wherein the first conversion rule creation procedure creates definition information using a variable for the conversion rule between the conversion source element and the conversion destination element. program. An input procedure for inputting a value for the variable;
The conversion created in the first conversion rule creation procedure by applying the value input in the input procedure to the variable in the conversion rule definition information created in the first conversion rule creation procedure. 4. The conversion rule creation program according to claim 3, further comprising a second conversion rule creation procedure for creating conversion rule definition information using the rule definition information as a model. A conversion rule evaluation program for causing a computer to perform reusability evaluation on conversion rule definition information between data formats each composed of a plurality of elements each having a value,
A conversion rule storage procedure for storing the conversion rule definition information;
A conversion target selection procedure for selecting an element to be converted from the elements constituting the data format to be converted or converted; and
For each of the definition information stored in the conversion rule storage procedure, an excess / deficiency determination procedure for determining an excess / deficiency between an element to be converted in the definition information and an element selected in the conversion target selection procedure When,
A conversion rule evaluation program comprising: a display procedure for causing a display device to display evaluation information based on excess / deficiency determined in the excess / deficiency determination procedure.

Images