JP6287093B2 - Software development support apparatus, software development support method and program - Google Patents

Description

  The present invention relates to a software development support apparatus, a software development support method, and a program, and in particular, a technique for performing version management of a program and assets used by the program and finding version inconsistency caused by changing any of these. About.

  An automatic program generation system (Patent Document 1 and Patent Document 2) and an integrated program development tool called Integrated Development Environment (IDE) are widely used. These systems and tools are provided mainly for the purpose of efficiently developing the source code of a program. On the other hand, when a common asset referenced by the program, for example, a file containing various items of data, is changed, has the corresponding change been made on the program side that would be affected by the change in the file? There is no provision of a function for checking the consistency between files and programs.

  In this regard, Patent Documents 3 to 6 disclose a system that centrally manages design information and coding information, which are program meta information, in a repository. However, none of these systems has been used to check the consistency of whether files and programs have been changed appropriately using design information and coding information.

  Patent Documents 7 to 11 disclose a system in which when a program code, design information, or the like is changed, an influence range due to the change can be confirmed. However, none of these systems uses design information or coding information to check the consistency of whether both files and programs have been modified appropriately.

  Furthermore, none of the techniques described in the above documents confirms whether or not the program reflecting the file change has been properly placed in the operating environment.

Japanese Patent Laid-Open No. 01-147621 Japanese Patent No. 3871832 JP 2006-079212 A JP 2006-106893 A JP 2007-087127 A JP 2009-294940 A JP 2010-015458 A JP 2009-122754 A JP 2007-172223 A JP 2007-018334 A Japanese Patent Laid-Open No. 05-061655

  Therefore, at present, when a file is changed, all the work to confirm whether the program affected by the change has been changed and whether the changed program has been placed in the operating environment is performed visually. . If the system is small enough to be visually confirmed, this method will not cause any problems. However, the larger the system, the greater the number of programs and the more complicated the dependency between each program and file. This increases the man-hours and difficulty involved in confirming the changes described above, such as omission of confirmation. The risk is also increased. In addition, as the number of files and programs and the number of locations in the program that refer to files increase, it becomes more difficult to confirm the change and the risk of oversight increases. In many cases, file and program changes are implemented after the system enters the operation phase, but if there is a lack of confirmation in such a case, there are few cases where the impact is significant even if it is a small mistake. Absent. In particular, omissions during production operations often led to serious problems. Therefore, checking the changes of files and programs after the system enters the operation phase puts a severe burden on the developer.

  In order to solve these problems, when a file or program specification is changed, it is important to have a mechanism for confirming that all other related assets, that is, the program and file are also changed appropriately.

  The present invention has been made to solve such problems, and performs version management of programs and assets used by the programs, and version inconsistencies caused by changing any of these. It is an object to provide a software development support apparatus, a software development support method, and a program that can be found.

  Other problems and novel features will become apparent from the description of the specification and the accompanying drawings.

  The software development support device according to the present invention is a file that is a target of data input / output by a program, and defines the item and the version of the item for the file including one or more items. File definition means for outputting together with the version of the file specification, the processing content of the program, the item used by the program, and the version of the item to define the program specification, and the program specification Program definition means for outputting together with the version of the file, and according to the file specification, generating a source code or an executable format file of the file input / output component for inputting / outputting the item from the file, the version of the file input / output component, The item used by the file input / output component According to the program specification, a file input / output component generation means for holding and outputting, and generating a source code or an executable format file of the program according to the program specifications, the version of the program, and the item used by the program Program generation means for holding and outputting the version, the file specification, the program specification, the file input / output component, the program, the versions thereof, and the version of the item of the item that each includes or uses And inspection means for inspecting consistency by comparing any two or more of them.

  The software development support method according to the present invention is a file that is a target of data input / output by a program, and defines the item and the version of the item for the file including one or more items. Define the file definition step to be output together with the version of the file specification, the processing content of the program, the item used by the program, and the version of the item to define the program specification, and the program specification A program definition step that is output together with the version of the file, and in accordance with the file specification, generates a source code or an executable file of a file input / output component for inputting / outputting the item from the file, and a version of the file input / output component, Used by the file input / output component According to the version of the item, a file input / output component generation step for holding and outputting, and the program specification, generating a source code or an executable file of the program, the version of the program, and the program used by the program A program generation step for holding and outputting the version of the item, the file specification, the program specification, the file input / output component, the program, the version thereof, and the item of the item that each includes or uses An inspection step for checking consistency by comparing any two or more of the versions.

  The program according to the present invention is a program for causing a computer to execute the above method.

  According to the present invention, a software development support apparatus, a software development support method, and a program capable of performing version management of a program and assets used by the program and finding a version inconsistency caused by changing any of them are provided. be able to.

It is a figure which shows the structure of embodiment of this invention. It is a figure which shows the program production | generation process of embodiment of this invention. It is a figure which shows the example of the file definition screen of embodiment of this invention. It is a figure which shows the example of the file specification of embodiment of this invention. It is a figure which shows the example of the relationship table (file relationship information) of embodiment of this invention. It is a figure which shows the example of the program definition screen of embodiment of this invention. It is a figure which shows the example of the file specification reference screen of embodiment of this invention. It is a figure which shows the example of the program specification of embodiment of this invention. It is a figure which shows the example of the relationship table (program related information) of embodiment of this invention. It is a figure which shows the example of the file version information of embodiment of this invention. It is a figure which shows the example of the file version information of embodiment of this invention. It is a figure which shows the example of the relationship table (file input / output component relationship information) of embodiment of this invention. It is a figure which shows the example of the program version information of embodiment of this invention. It is a figure which shows the example of the relationship table (program related information) of embodiment of this invention. It is a figure which shows the example of the dummy structure of embodiment of this invention. It is a figure which shows the example of the consistency test | inspection process of embodiment of this invention. It is a figure which shows the example of the consistency test | inspection process of embodiment of this invention. It is a figure which shows the example of the consistency test | inspection process of embodiment of this invention.

  Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings.

  First, the configuration of the software development support apparatus 100 according to the embodiment of the present invention will be described with reference to FIG.

  The software development support apparatus 100 includes a file definition unit 101, a program definition unit 106, a file input / output component generation unit 112, a program generation unit 116, a repository 120, a version matching inspection unit 130, a version acquisition unit 131, and an operating environment 140.

  Hereinafter, the configuration and operation of each means will be described with reference to FIGS.

<File definition>
The file definition unit 101 defines file specifications in accordance with user input. Further, the file definition unit 101 generates and manages version information of the file itself, and further generates and manages version information for each item constituting the file. In order to realize these functions, the file definition unit 101 includes a version information creation unit 103, a file specification output unit 104, and a relation table output unit 105.

  The version information creation unit 103 receives user input for defining a file specification, and automatically generates version information of files and items. The version information creation unit 103 provides, for example, an input screen shown in FIG. 3 to the user as a graphical user interface for defining file specifications. This input screen is displayed on the monitor. This input screen is referred to as a file definition screen 102.

  The file definition screen 102 is divided into a plurality of cells. Among these, each cell in which the character string “file name” “file version” “item name” “attribute” “item version” is displayed is a cell in which the version information creation unit 103 displays a fixed character string. is there.

  A cell that displays a file version, that is, a cell in the right column of “File version” (“3” is displayed), and a cell that displays an item version, that is, a cell that is continuous across multiple rows under “Item version” ( “1”, “2”, “2”,...) Are cells for displaying version information automatically generated by the version information creating unit 103.

  All other cells are cells in which a user should input a value according to a predetermined input rule. That is, a cell in the right column of “file name” (“FILE_A” is displayed) is a cell for inputting a file name. In addition, cells that are continuous over multiple lines under “item name” (“item A”, “item B”, “item C”... Are input), and cells that are continuous over multiple lines under “attribute” (“char” [5], “long”, “char [20]”,...) Is a cell for inputting an item name and an attribute (data type) for each of one or more items constituting the file.

  When the user inputs a new file name, the version information creation unit 103 sets the file version to “1”. Then, when the user changes the file name, newly inputs, changes or deletes an item and outputs a file specification (described later), the version information creation unit 103 increments (+1) the version of the file. In FIG. 3, the file version is “3”.

  The same applies to each item constituting the file. That is, when the user newly inputs an item (item name and attribute), the version information creation unit 103 assigns version “1” to the item. When the user changes the item name or attribute of a certain item and outputs the file specification, the version information creating unit 103 increments (+1) the version of the item.

  As a matter of course, even if the definition contents of an item are changed many times before outputting the file specification, the version is limited to a maximum of +1. If a new file definition is created, it remains at 1. is there. If an item is deleted, the version of the item is deleted.

  When the user finishes inputting necessary information on the file definition screen 102, the user issues an instruction to register the file definition, in other words, to output the file specification. For example, the user presses (clicks) a registration button.

  In response to this, the file specification output unit 104 and the relationship table output unit 105 register the updated information in the file specification 121 and the relationship table 123 in the repository 120.

  FIG. 4 shows an example of file specification information registered in the file specification 121 by the file specification output means 104. The file specification information includes a file name, a file version (a version of the entire file definition), an item name, an item attribute, and an item version.

  FIG. 5 shows an example of file relation information registered in the relation table 123 by the relation table output means 105. The file relation information includes a file name, an item name, a file version (version of the entire file definition), and an item version.

  If a line having the same file name already exists in the relation table 123, the relation table output means 105 outputs the above-mentioned file relation information after once deleting the existing line.

<Program definition>
The program definition means 106 defines the specification of the program according to the user input. The program definition means 106 generates and manages a program version. Further, the program definition unit 106 manages the version of the program in association with the version of each of one or more items in the file that the program uses as the data input / output destination. In order to realize these functions, the program definition unit 106 includes a version information creation unit 109, a program specification output unit 110, and a relation table output unit 111.

  The version information creation unit 109 accepts user input for defining a program specification, and automatically generates program version information. The version information creation unit 109 provides, for example, an input screen shown in FIG. 6 to the user as a graphical user interface for defining a program specification. This input screen is displayed on the monitor. This input screen is referred to as a program definition screen 107.

  The program definition screen 107 includes a program flow diagram screen, an input process definition screen, an output process definition screen, and a free description screen.

  First, the user defines the program structure on the program flow diagram screen. The user defines the structure of the entire program by combining nodes representing processing units constituting the program in a tree shape. The program definition screen 107 provides a graphical user interface for arranging nodes at arbitrary positions on the screen space and defining dependencies between the arranged nodes. The details of such an interface are out of the scope of the problem to be solved by the present invention, so that the description thereof is omitted, but it goes without saying that various existing technologies can be used.

  In the program structure defined in this tree type, one node corresponds to one processing unit. Three types of these nodes are prepared in advance. That is, an input processing node, an output processing node, and a free description node. The user selects an appropriate type of node according to the content of the process to be described (input process, output process, or other process) and arranges it in the tree. Here, for example, when the B processing node is arranged subordinate to the A processing node, it means that the A processing is constituted by a series of processing including the B processing.

  When the input to the program flow diagram screen is completed, the user defines the specific processing contents of each node using the input processing definition screen, output processing definition screen, or free description screen shown in FIG. For example, when the user selects (clicks) a certain node in the program flow diagram, the version information creating unit 109 can display a definition screen corresponding to the type of the node on the monitor. That is, if an input processing node is selected, an input processing definition screen is displayed. If an output processing node is selected, an output processing definition screen is displayed. If a free description node is selected, a free description screen is displayed.

  A file specification reference button is provided on the definition screen for input processing and output processing. When the user presses the file specification reference button, the file specification reference means 108 displays the file specification reference screen shown in FIG. 7 on the monitor. The file specification reference screen allows the user to specify a file to be input / output by the program and its items in the input process or output process.

  The file specification reference means 108 refers to the file specification 121 of the repository 120 and acquires file specification information. Then, the file specification reference unit 108 displays the file name, file version, item name, attribute, and item version defined in the file specification information on the file specification reference screen.

  The user selects an item used by the program in the selected processing unit from the list of file items. When an item is selected, the version information creation unit 109 creates file version information that is a combination of the file name that includes the selected item, the selected item name, and the item version.

  The version information creation unit 109 displays the item name and item version related to the file version information at the position of the used item name (version) on the input processing screen or the output processing screen.

  When the file item selection is canceled on the file specification reference screen, the version information creation unit 109 deletes the file version information and displays the item name (version) displayed on the input processing screen or the output processing screen. To delete the item name and item version of the item.

  Note that if an item not selected on the file specification reference screen is used by the user on the input processing, output processing, or free description screen, an error will occur at the time of program generation, and it will be restricted that such a program cannot be generated (described later). ).

  The version information creation unit 109 creates a program definition newly created, that is, a definition of a program structure including one or more nodes in the program flow diagram, and an input process definition screen, an output process definition screen, or a free description screen. A series of processes including the definition of the process contents of the node are newly performed. When these processes are completed, “1” is assigned to the program version (version of the entire program definition). Also, the version information creation means 109 increments (+1) the program version when the program structure or the definition of the processing content of each node is changed.

  As a matter of course, even if the program structure or node contents are changed many times before outputting the program specification, the program version is only +1 at the maximum. It remains.

  When the user finishes inputting necessary information on the program definition screen 107, the user issues an instruction to register the program definition. For example, a registration button is pressed.

  In response to this, the program specification output unit 110 and the relationship table output unit 111 register the updated information in the program specification 122 and the relationship table 123 in the repository 120.

  FIG. 8 shows an example of program specification information registered in the program specification 122 by the program specification output means 110. The program specification information includes a program name, a program version (version of the entire program definition), a node name, a node type, processing information (extraction conditions), and used file item version information. The used file item version information includes a file name, an item name, and an item version.

  FIG. 9 shows an example of program relation information registered in the relation table 123 by the relation table output means 115. The program related information includes a set of a program name and a program version (a version of the entire program definition). Furthermore, the program related information includes a set of a program name and file version information (a set of used file name, used item name and used item version).

<File input / output component generation>
The file input / output component generator 112 automatically generates a file input / output component for the program to input / output data to / from the file based on the file specification. The file input / output component generation unit 112 includes a generation unit 113, a version incorporation unit 114, and a relation table output unit 115.

  The generation unit 113 reads the file specification from the file specification 121 of the repository 120 and generates a source of the file input / output component using the file specification. Here, the file input / output component is a software component for implementing data input / output processing for a file in a program. The file input / output component has an interface capable of inputting / outputting data in item units by designating item names from the program side. It should be noted that the specific method for generating the file input / output component source is out of the scope of the problem to be solved by the present invention and will not be described in detail, but can be realized by using various known methods. Yes.

  The generation unit 113 stores the generated file input / output component source in the input / output component source 124 of the repository 120. Further, the generation unit 113 compiles and links the generated file input / output component source and saves it in the input / output component (library) 125.

  When the source of the file input / output component is generated by the generation unit 113, the version embedding unit 114 sets the file version of the file to be input / output by the file input / output component and the input / output target. Include item version information for each item. That is, the version embedding unit 114 refers to the file specification 121 and incorporates file version information as shown in FIG. 10 into the source of the file input / output component. The file version information can be incorporated in a format that can be referred to by a known what command or the like as a static variable.

  That is, the file version information can be stored in the static variable SccsID of the character string. Specifically, the file version information includes a file name, a file version, an item name, and the version of the item after “@ (#)”. Thereafter, the item is defined with the item name and the version of the item. Repeated as much as possible.

  Further, the version embedding unit 114 automatically incorporates into the file input / output component a process that outputs the file version information when the file output process is performed. FIG. 11 shows an example of file version information to be output. The file version information includes a file name, a file version, an item name, and the version of the item. Thereafter, the item name and the version of the item are repeated as many times as the item is defined. This file version information is output in a file having a file name with “_Version” added to the file name of the output file. The version embedding unit 114 automatically generates a process in the file input / output component so that the output process is automatically executed after the file output process of the file input / output component is opened.

  The relation table output unit 115 includes the source file name of the file input / output component generated by the generation unit 113, the file version of the file to be input / output by the file input / output component, and the item for each item to be input / output Information relating the version information is output to the relation table 123. Also, the execution file name of the file input / output component generated by the generation unit 113, the file version of the file that the file input / output component is to be input / output, and the item version information for each item to be input / output The associated information is output to the relation table 123. These pieces of information are referred to as file input / output component related information.

  FIG. 12 shows an example of file input / output component relationship information output by the relationship table output means 115. As shown in FIG. 12A, the file input / output component relationship information includes the source file name of the generated input / output component, the file version of the file to be used, and the item to be used in the file. Contains a set of name, version of the item. Further, as shown in FIG. 12B, the file part relation information includes a set of a generated execution file name, a file version of a file to be used, an item name to be used in the file, and a version of the item.

  If there are already lines with the same source file name or execution file name in the relation table 123, the relation table output means 115 once deletes those lines that already exist, and then the file input / output component relation information described above. Is output.

<Program generation>
The program generation unit 116 automatically generates a program source code and an execution file based on the program specification. The source code of the program generated here reflects the definition contents input by the user on the file definition screen 102 and the program definition screen 107 (FIG. 2). The program generation unit 116 includes a generation unit 117, a version incorporation unit 118, and a relation table output unit 119.

  The generation unit 117 reads the program specification 122 of the repository 120. Then, the generation unit 117 generates a program source. Note that a specific method for generating a program source is out of the scope of the problem to be solved by the present invention, and thus detailed description thereof is omitted. For example, for input processing and output processing, file input / output component generation is performed. Code for calling the file input / output component generated by the means 112 can be included. In addition, regarding the free description process, a code entered by the user on the free description screen can be included.

  In addition, when a file item that is not selected on the file specification reference screen is used in the process of each node, the generation unit 117 may end the program generation with an error. Thereby, it is possible to prevent the use of a file item in which version information is not incorporated.

  For example, as illustrated in FIG. 15, the generation unit 117 is implemented by using an item name of an unused item (for example, the item B in this case) as a member name of the dummy structure. By doing so, it can be configured such that a compile error occurs when the user uses item B.

  Here, the version embedding unit 118 incorporates program version information into the program source when the generating unit 117 generates the program source. That is, the version incorporating means 118 refers to the program specification 122 and incorporates program version information as shown in FIG. 13 into the program source. The file version information can be incorporated in a format that can be referred to by a known what command or the like as a static variable.

  That is, the program version information can be stored in the static variable SccsID of the character string. Specifically, the program version information includes a program name, a program version (version of the entire program definition), a used file name, a used item name, and the version of the item after “@ (#)”. The set of file name, used item name, and version of the item is repeated for the item to be used.

  The generation unit 117 stores the generated program source in the program source 126 of the repository 120. Further, the program generation unit compiles and links the source of the program, generates an execution format program, and stores it in the program (execution format) 127.

  The relation table output unit 119 combines the source file name of the program generated by the generation unit 117 and the version of the program (version of the entire program definition), and also the source file name, used file name, and used item name of the program. The version of the item is paired and output to the relation table 123. Further, the relation table output means 119 combines the executable file name of the program generated by the generating means 117 and the version of the entire program definition, and also the executable file name of the program, the used file name, the used item name, and its item. Are output as a set to the relationship table 123. These pieces of information are referred to as program related information.

  FIG. 14 shows an example of the program relation information output by the relation table output means 119. As shown in FIG. 14A, the program-related information includes a set of the source file name of the generated program and the version of the entire program definition. Furthermore, the program related information in FIG. 14A includes a set of a source file name, a used file name, a used item name, and a version of the item of the generated program. Further, as shown in FIG. 14B, the program related information includes a set of the generated executable file name and the version of the entire program definition. Furthermore, the program related information in FIG. 14B includes a set of a generated executable file name, a used file name, a used item name, and a version of the item.

  If there are already lines with the same source file name or execution file name in the relation table 123, the relation table output means 115 once deletes those lines that already exist, Output.

  Through the steps so far, the repository 120 stores the file specification 121, the program specification 122, the input / output component source 124, the input / output component (library) 125, the program source 126, and the program (execution format) 127.

  The generated program execution format file, input / output component library, and file are placed in the operation environment 140 (see 141 to 143 in FIG. 1), and are used for actual operation.

<Consistency check>
The checking unit 132 performs a consistency check for checking whether the version of the file or file item that the program actually intends to use is the one intended when the program is created.

  For example, if only a file or file item is updated after the program is generated, there may be a discrepancy between the file or file item assumed by the program and the actual file or file item. Thus, when a file or file item is updated, the program should also update it. Conventionally, it was not immediately known which program should be updated, but in this embodiment, as described above, version information is assigned to each file or file item and program, The correspondence relationship that should be recorded is recorded in the relationship table 123. Therefore, by using these pieces of information, it is possible to easily check the consistency between the file or file item and the program.

  The inspection unit 132 includes a version acquisition unit 131 and a version matching inspection unit 130.

(Get version information)
First, the version acquisition unit 131 collects versions of programs, input / output components, and files to be inspected for consistency.

  S101: The version acquisition unit 131 selects one program to be subjected to the consistency check. In the present embodiment, it is assumed that PRG_A is selected as the inspection target program and the consistency inspection is performed on PRG_A.

  S102: The version acquisition unit 131 acquires the version of the program from the relation table 123 using the name of the program (“PRG_A” in the example of the present embodiment) as a key.

  The relationship table 123 includes a table output by the relationship table output unit 105 (FIG. 5), a table output by the relationship table output unit 111 (FIG. 9), a table output by the relationship table output unit 115 (FIG. 12), It is also assumed that the table (FIG. 14) output by the relation table output means 119 is stored. The version acquisition unit 131 obtains the program version from the table of FIG. 9 using the program name as a key.

  S103: The version acquisition unit 131 uses the source file name of the program (typically obtained by adding “.c” to the program name) as a key from the table of the relation table 123 shown in FIG. Get the source version of the program.

  S104: The version acquisition unit 131 uses the execution file name of the program (typically obtained by adding “.EXE” to the program name) as a key from the table of the relation table 123 shown in FIG. Get the version of the program executable.

  S105: The version acquisition unit 131 applies a what command to an execution format file 141 (typically obtained by adding “.EXE” to the program name) of a program that is actually used in the operation environment 140. Execute. Here, the what command is a command for acquiring the value of the static variable SccsID embedded in the program. In this embodiment, the SccsID of the program includes program version information as shown in FIG. 13 (consisting of “@ (#)”, program name, program version, used file name, used item name, and version of the item). Is stored.

  S106: The version acquisition unit 131 acquires the file name to be used from the table of the relation table 123 shown in FIG. 9 using the program name acquired in step S102 as a key. Further, the version of the item is acquired from the table of the relation table 123 shown in FIG. 5 using the used file name (corresponding to the file name in the table of FIG. 5) as a key.

  S107: The version acquisition unit 131 uses the source file name of the file input / output component (typically obtained by adding “.c” to the used file name acquired in step S106) as a key. The version of the item is acquired from the table of the relation table 123 shown in FIG.

  S108: The version acquisition unit 131 uses the execution file name of the file input / output component (typically obtained by adding “.DLL” to the used file name acquired in step S106) as a key. The version of the item is acquired from the table of the relation table 123 shown in FIG.

  S109: The version acquisition unit 131 obtains the file input / output part library 142 (typically, “.DLL” added to the used file name acquired in step S106) in actual operation in the operation environment 140. Execute a what command. Here, the what command is a command for acquiring the value of the static variable SccsID embedded in the program. In this embodiment, file version information (consisting of “@ (#)”, file name, file version, item name, and item version) as shown in FIG. 10 is stored in the SccsID of the program.

  S110: The version acquisition means 131 is a file in which file version information relating to the file 143 used for actual operation in the operation environment 140 is described (file name file with “_Version” added to the file name of the file 143). Is read, and the file version information that is the content is read.

  A list of information acquired from the relation table 123 by the version acquisition unit 131 as a result of the processing so far is shown in FIGS.

(Consistency check)
Next, the version consistency checking unit 130 checks whether the versions of programs, input / output components, and files acquired by the version acquisition unit 131 in steps S101 to S110 are consistent with each other.

  S201: Here, after updating the program specifications, whether the program source and program (execution format) are generated by the program generation means, or the same program as the generated program (execution format) is copied to the operating environment It is confirmed by comparing the value of each version. If all of the version values match, it can be determined that there is no update omission and is consistent.

  The version consistency checking unit 130 uses the program version acquired in S102 (version of the entire program definition) as a reference, the version of the program source acquired in S103, the version of the executable program acquired in S104, and the operation acquired in S105. Compare versions of executable programs placed in the environment. Specifically, the version values shown as a in FIG. 16 are compared.

  Here, if all of these versions match, there is a match. That is, there is no update omission.

  On the other hand, if these versions do not match, the source file name, executable file name, or executable file name of the operating environment that has a version that did not match the program version (the version of the entire program definition), and those versions And the program name used as a reference for comparison are stored in a memory (not shown).

  S202: Here, the program uses whether the item used by the program is updated after the program specification is updated, after the program is generated, or after the program is copied to the operating environment. Confirm by comparing the item version value, the item version value when the file specification is created, the item version value of the input / output component, and the item version value when the file is created. If all of the version values match, it can be determined that there is no update omission and is consistent.

  The version consistency checking unit 130 uses the version of the item used by the program definition acquired in S106 as a reference, the version of the item used by the source of the input / output component acquired in S107, and the input / output component in the execution format acquired in S108. The version of the item to be used, the version of the item used by the input / output component of the operating environment acquired in S109, and the version of the item acquired from the file bearing “_Version” of the operating environment are respectively compared. Specifically, the values of the versions indicated as b1 or b2 in FIGS. 16 and 17 are compared.

  Here, if all of these versions match, there is a match. That is, there is no update omission.

  On the other hand, if these versions do not match, the source file name, execution file name, operating environment execution file name, or “_Version” that uses the item that does not match the version of the item used by the program definition is The named file name, the file name of the program definition used as a reference for comparison, the item names, and their versions are stored in a memory (not shown).

  S203: Here, after the file specification is updated, the file input / output component generation means generates the input / output component source, the input / output component (library), or the same component as the generated input / output component (library) Is confirmed by comparing the values of each version. If all of the version values match, it can be determined that there is no update omission and is consistent.

  The version consistency checking unit 130 uses the version of the file definition shown in FIG. 5 as a reference, the source version of the file input / output component shown in FIG. 12 (A), and the file input / output component in the execution format shown in FIG. 12 (B). The version, the version of the execution format file 142 of the input / output component of the operational environment 140, and the version of the file with “_Version” in the operational environment 149 are compared. Specifically, the version values shown as c in FIG. 17 are compared.

  Here, if all of these versions match, there is a match. That is, there is no update omission.

  On the other hand, if these versions do not match, the source file name, execution file name, operation environment execution file name, or file name bearing “_Version” whose version does not match the file definition version These versions and the file name of the file definition used as a reference for comparison are stored in a memory (not shown).

  When there are a plurality of file definitions, the version consistency checking unit 130 performs the same process for all the file definitions.

  S301: The version consistency inspecting unit 130 performs a series of processes relating to S101 to S110 and S201 to S203 for all the programs recorded in the relation table 123.

  S302: Finally, the version consistency checking unit 130 presents to the user information related to a file stored in the memory and whose version does not match. Here, it is preferable to eliminate duplication when there is duplication of information. Note that it is possible to eliminate waste of information duplication in advance by using existing technology.

  As a result, the user can know which file has a version mismatch.

  FIG. 18 shows an example of a method for presenting information to the user. In this example, in the program definition, the version of the item C is “1” (see the item with a circle in FIG. 16). On the other hand, the version of item C is “2” in each of the file definition, the file input / output component source file, the execution file, and the file with “_Version” in the operating environment.

  Thereby, the user can know that the update omission exists in the part using the item C of the file FILE_A of the program definition PRG_A because the version of the item C in the program definition is the smallest. .

  Note that the execution order of the steps S101 to S110 is merely an example, and can be executed in any order. Similarly, the execution order of the steps S201 to S203 is merely an example, and can be executed in any order.

  According to the present embodiment, the checking means 132 checks the version consistency of the item of the file used from the program, and the user can check the result. As a result, it is possible to perform a consistency check that has conventionally required a larger number of man-hours as the development assets of programs and files increase, in a relatively short time. The larger the system, the greater the effectiveness.

  In addition, according to the present embodiment, not only the development assets (assets accumulated in the repository 120) but also the assets arranged in the operation environment 140, the latest, that is, the consistent program, It is easy to confirm that a part (library) is placed and a file is created. For this reason, it is possible to suppress the occurrence of operational errors such as arrangement omission.

  Furthermore, according to the present embodiment, the file referred to by the program can be grasped at the item level. Further, by using a file input / output component having an interface for each item, even if a change occurs in an item that is not used in the program, the program is not affected and the number of programs to be corrected can be minimized.

  Further, according to the present embodiment, if consistency verification is performed after changing a certain file specification, a program that uses the file, that is, a program that needs to be changed is displayed. As a result, the program that must be changed can be grasped without omission.

  Note that the present invention is not limited to the above-described embodiment, and can be changed as appropriate without departing from the spirit of the present invention. For example, in the above-described embodiments, the present invention has been mainly described as a hardware configuration. However, the present invention is not limited to this, and a CPU (Central Processing Unit) executes a computer program for arbitrary processing. Can also be realized. In this case, the computer program can be stored and provided to the computer using various types of non-transitory computer readable media. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (for example, flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (for example, magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / W, semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). The program may also be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

For example, the present invention can be expressed as follows.
(Appendix 1)
A file which is a target of data input / output by a program, and defines the item and the version of the item as a file specification for the file including one or more items, and outputs together with the version of the file specification File definition means to
Program definition means for defining the processing content of the program, the item used by the program, and the version of the item to define a program specification, and outputting the program specification with the version,
According to the file specification, a source code or an executable format file of a file input / output component for inputting / outputting the item from the file is generated, and the version of the file input / output component and the item used by the file input / output component are used. A version of the file I / O component generation means for holding and outputting,
Program generation means for generating a source code or an executable format file of the program according to the program specification, and holding and outputting the version of the program and the version of the item used by the program;
The file specification, the program specification, the file input / output component, and the program are checked for consistency by comparing any two or more of these versions and the versions of the items that each includes or uses. And a software development support device comprising:
(Appendix 2)
The inspection means includes the version of the program specification, the version of the source code of the program, the version of the executable file of the program, and the executable file of the program arranged in an actual operating environment. The software development support apparatus according to attachment 1, wherein any two or more of the versions are compared.
(Appendix 3)
The inspection means includes the version of the item used by the program specification, the version of the item used by the source code of the file input / output component, and the item used by the execution format file of the file input / output component. By comparing any two or more of the versions of the file and the version of the executable file of the file input / output component arranged in the actual operating environment,
The software development support apparatus according to appendix 1 or 2.
(Appendix 4)
The inspection means is arranged in the version of the file specification, the version of the source code of the file input / output component, the version of the executable file of the file input / output component, and the actual operating environment. By comparing any two or more of the version of the executable file of the file input / output component and the version of the file arranged in the operating environment,
The software development support apparatus according to any one of appendices 1 to 3.
(Appendix 5)
The inspection means includes the version of the item of the file specification, the version of the item of the source code of the file input / output component, the version of the item of the executable file of the file input / output component, and the actual Compare two or more of the version of the item of the executable file of the file input / output component arranged in the operating environment and the version of the item of the file arranged in the operating environment. By
The software development support device according to any one of appendices 1 to 4.
(Appendix 6)
It further has a repository that holds the relationship table,
The file definition means holds the version of the file specification and the version of the item in the relation table,
The program definition means holds the version of the program specification and the version of the item in the relation table,
The file input / output component generation means holds the version of at least one of the source code or the executable file of the file input / output component and the version of the item in the relation table,
The program generation unit causes the relationship table to hold the version of at least one of the source code or the executable file of the program and the version of the item. Software development support equipment.
(Appendix 7)
The file input / output component generation means includes at least one of the source code or the executable format file of the file input / output component, the version of the source code or the executable format file, the version of the item, Is stored as a value that can be referenced externally,
The program generation means can refer to the version of the source code or the executable format file and the version of the item from the outside in at least one of the source code or the executable format file of the program. The software development support device according to any one of supplementary notes 1 to 6, wherein the software development support device is held as a value.
(Appendix 8)
A file which is a target of data input / output by a program, and defines the item and the version of the item as a file specification for the file including one or more items, and outputs together with the version of the file specification File definition step to
A program definition step of defining the processing contents of the program, the item used by the program, and the version of the item to define a program specification, and outputting the program specification together with the version of the program specification;
According to the file specification, a source code or an executable format file of a file input / output component for inputting / outputting the item from the file is generated, and the version of the file input / output component and the item used by the file input / output component are used. And the file input / output component generation step for holding and outputting,
In accordance with the program specifications, a program generation step of generating a source code or an executable format file of the program and holding and outputting the version of the program and the version of the item used by the program;
The file specification, the program specification, the file input / output component, and the program are checked for consistency by comparing any two or more of these versions and the versions of the items that each includes or uses. And a software development support method including an inspection step.
(Appendix 9)
The checking step includes the version of the program specification, the version of the source code of the program, the version of the executable file of the program, and the executable file of the program arranged in an actual operating environment. The software development support method according to appendix 8, wherein any two or more of the versions are compared.
(Appendix 10)
The inspection step includes the version of the item used by the program specification, the version of the item used by the source code of the file input / output component, and the item used by the execution format file of the file input / output component. By comparing any two or more of the versions of the file and the version of the executable file of the file input / output component arranged in the actual operating environment,
The software development support method according to appendix 8 or 9.
(Appendix 11)
The inspection step includes the version of the file specification, the version of the source code of the file input / output component, the version of the executable file of the file input / output component, and the actual operation environment. By comparing any two or more of the version of the executable file of the file input / output component and the version of the file arranged in the operating environment,
The software development support method according to any one of appendices 8 to 10.
(Appendix 12)
The checking step includes: the version of the item of the file specification; the version of the item of the source code of the file input / output component; the version of the item of the executable file of the file input / output component; Compare two or more of the version of the item of the executable file of the file input / output component arranged in the operating environment and the version of the item of the file arranged in the operating environment. By
The software development support method according to any one of appendices 8 to 11.
(Appendix 13)
The file definition step stores the version of the file specification and the version of the item in a relational table in a repository,
The program definition step stores the version of the program specification and the version of the item in the relation table,
In the file input / output component generation step, the version of at least one of the source code or the executable file of the file input / output component and the version of the item are held in the relationship table,
The program generation step causes the relationship table to hold the version of at least one of the source code or the executable file of the program and the version of the item. Software development support method.
(Appendix 14)
In the file input / output component generation step, at least one of the source code or the executable format file of the file input / output component, the version of the source code or the executable format file, the version of the item, Is stored as a value that can be referenced externally,
In the program generation step, at least one of the source code or the executable format file of the program can refer to the version of the source code or the executable format file and the version of the item from the outside. The software development support method according to any one of appendices 8 to 13, which is held as a value.
(Appendix 15)
A program for causing a computer to execute the method according to any one of appendices 8 to 14.

DESCRIPTION OF SYMBOLS 100 Software development support apparatus 101 File definition means 102 File definition screen 103 Version information creation means 104 File specification output means 105 Relation table output means 106 Program definition means 107 Program definition screen 108 File specification reference means 109 Version information creation means 110 Program specification output Means 111 Relation table output means 112 File input / output component generation means 113 Generation means 114 Version incorporation means 115 Relation table output means 116 Program generation means 117 Generation means 118 Version incorporation means 119 Relation table output means 120 Repository 121 File specifications 122 Program specifications 123 Relation table 124 Input / output component source 125 Input / output component (library)
126 program source 127 program (execution format)
130 Version Consistency Check Means 131 Version Acquisition Means 132 Check Means 140 Operating Environment 141 Program (Execution Format)
142 I / O parts (library)
143 files

Claims (10)

A file which is a target of data input / output by a program, and defines the item and the version of the item as a file specification for the file including one or more items, and outputs together with the version of the file specification File definition means to
Program definition means for defining the processing content of the program, the item used by the program, and the version of the item to define a program specification, and outputting the program specification with the version,
According to the file specification, a source code or an executable format file of a file input / output component for inputting / outputting the item from the file is generated, and the version of the file input / output component and the item used by the file input / output component are used. A version of the file I / O component generation means for holding and outputting,
Program generation means for generating a source code or an executable format file of the program according to the program specification, and holding and outputting the version of the program and the version of the item used by the program;
The file specification, the program specification, the file input / output component, and the program are checked for consistency by comparing any two or more of these versions and the versions of the items that each includes or uses. And a software development support device comprising: The inspection means includes the version of the program specification, the version of the source code of the program, the version of the executable file of the program, and the executable file of the program arranged in an actual operating environment. The software development support apparatus according to claim 1, wherein any two or more of the versions are compared. The inspection unit, the version of the item of which program is used, the version of the item of which source code is used by the file input and output parts, the item of which executable file uses the file input and output components By comparing any two or more of the versions of the file and the version of the executable file of the file input / output component arranged in the actual operating environment,
The software development support apparatus according to claim 1 or 2. The inspection unit, the version of the file specification, wherein the version of the source code before Symbol file input and output components, wherein the version of the executable file of the file input and output part are arranged in a production environment the By comparing any two or more of the version of the executable file of the file input / output component and the version of the file arranged in the operating environment,
The software development support apparatus according to any one of claims 1 to 3. The inspection unit, the version of the item of the file specification, the version of the item of the source code before Symbol file input and output components, the version of the item of the executable file of the file input and output parts, the actual Compare two or more of the version of the item of the executable file of the file input / output component arranged in the operating environment and the version of the item of the file arranged in the operating environment. By
The software development support apparatus according to any one of claims 1 to 4. It further has a repository that holds the relationship table,
The file definition means holds the version of the file specification and the version of the item in the relation table,
The program definition means holds the version of the program specification and the version of the item in the relation table,
The file input / output component generation means holds the version of at least one of the source code or the executable file of the file input / output component and the version of the item in the relation table,
The said program generation means makes the said relationship table hold | maintain the said version of at least any one of the said source code of the said program, or the said execution format file, and the said version of the said item in any one of Claim 1 thru | or 5. The software development support apparatus described. The file input / output component generation means includes at least one of the source code or the executable format file of the file input / output component, the version of the source code or the executable format file, the version of the item, Is stored as a value that can be referenced externally,
The program generation means can refer to the version of the source code or the executable format file and the version of the item from the outside in at least one of the source code or the executable format file of the program. The software development support device according to claim 1, wherein the software development support device is held as a value. A file which is a target of data input / output by a program, and defines the item and the version of the item as a file specification for the file including one or more items, and outputs together with the version of the file specification File definition step to
A program definition step of defining the processing contents of the program, the item used by the program, and the version of the item to define a program specification, and outputting the program specification together with the version of the program specification;
According to the file specification, a source code or an executable format file of a file input / output component for inputting / outputting the item from the file is generated, and the version of the file input / output component and the item used by the file input / output component are used. And the file input / output component generation step for holding and outputting,
In accordance with the program specifications, a program generation step of generating a source code or an executable format file of the program and holding and outputting the version of the program and the version of the item used by the program;
The file specification, the program specification, the file input / output component, and the program are checked for consistency by comparing any two or more of these versions and the versions of the items that each includes or uses. And a software development support method including an inspection step. The checking step includes the version of the program specification, the version of the source code of the program, the version of the executable file of the program, and the executable file of the program arranged in an actual operating environment. The software development support method according to claim 8, wherein any two or more of the versions are compared.   A program for causing a computer to execute the method according to claim 8 or 9.

Images