JPH05108319A - Automatic program generating system using data-based software parts - Google Patents

Abstract

PURPOSE:To improve the productivity and the reliability of software by generating automatically a program and its specifications with the use of the data item-based software parts. CONSTITUTION:A function 207 selects automatically the software parts defined in a dictionary 201 and a relative check definition form 202 and produces the program specifications. A function 209 produces a source program by synthesizing the program skelton parts stored in a standard pattern library 205 with the software parts based on the specifications produced by the function 207. A function 212 edits the program specifications. Then a function 208 changes the software parts based on the program specifications. In such constitution, the reutilization ratio and the productivity of the software are improved. Furthermore the matching properties are automatically secured among the software parts, the specifications produced from the software parts, and the source program for improvement of the reliability of these items.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to improvement of software productivity, and in particular, existing software is made into parts, program specifications are automatically generated from these parts, and programs are automatically made from the program specifications. The present invention relates to a software development support method suitable for making new software development efficient by generating it.

[0002]

2. Description of the Related Art One of the effective methods for improving software productivity is to reuse existing software and develop new software. When this new software is reused to develop new software, it is reused at the stage of business system creation or program creation, and the programmer analyzes the document or source program describing the specifications of the existing software. Then
It is common to make corrections.

However, even for software of the same type of business, the required specifications vary depending on the user, and it is difficult to specify the corrected portion only from the document or the source program by the above-mentioned reuse method.
There are drawbacks such as deterioration of software maintainability, because corrections are added to one software due to differences in specifications required by multiple users.

[0004] Due to such drawbacks, even in software development of the same type of business, reuse of existing software is often abandoned and new software is often developed, which hinders improvement in productivity.

As one method for solving this problem,
There is a method of automatically generating a new program by dividing the software into parts by subdividing the functions and defining the correspondence between these parts and the program. By this method, software can be divided into small parts groups, and when developing new software, existing software can be reused at the parts level. Differences in software application tasks and required specifications It is now possible to deal with the difference by selecting, changing, or adding parts.

Note that, as a technique related to this kind of technology, for example, Hitachi Review VOL. 66 (issued in March 1984), pages 19 to 24, "system development support software" EAGLE "" and the like.

[0007]

The conventional method has the following problems.

The first problem in the prior art lies in the means of software componentization and the method of inheriting software component design information to the program specification document.

In the prior art in which the above-described software is made into parts and a program is automatically generated by synthesizing the parts, how to make parts when the parts are made because the parts of the software are made by subdividing the functions. It was difficult to set clear criteria such as how to subdivide the function from what point of view, and to what level it should be one component, and the designers of the components had different ways of dividing the software. Therefore, it has been difficult to thoroughly standardize software parts.

Further, in order to generate a source program, the designer or programmer must define the correspondence between the target business program and the parts for each program, which improves productivity and reliability. I couldn't get enough.

On the other hand, although some means for creating software parts and means for generating a source program from them have been developed, most of the work for creating a program specification document is independent of the work for creating these software parts. It was done manually by humans. There is a method of managing a program specification document as an electronic document created by using a computer dedicated to document creation such as a so-called word processor, but even now it is possible to support document clearing and storage, but the program design work itself It is still done manually by the program designer, including electronic document creation. With such a method of creating a program specification document, it is impossible to automatically inherit design information from a software component design process to a program design process. For this reason, it is difficult to improve the productivity of the program specification document creation work, and it is also up to the programmer to manually confirm that the software component and the source program generated from it match the program specification document. It has also been an obstacle to improving reliability.

A second problem in the prior art is that there is no means for generating a source program according to the program specification document when the program specification document describes the specifications different from the prepared software parts.

As described in the first problem, in the prior art, most of the work of creating the program specification document is performed manually, and therefore, for some reason, such as the program to be generated includes exception handling,
Even if the program specification document describes specifications different from the prepared software parts, it is impossible to reflect them in the source program generation. Therefore, in such a case, the programmer needs to correct the generated source program in accordance with the program specification document, and thus productivity and reliability cannot be sufficiently improved.

The third problem in the prior art is that even if the specification of the target business program is changed, even if the program specification document is modified, the software component is automatically operated according to the specification described in the program specification document. It cannot be corrected. Further, as another case, the same is true when the software component itself has an incorrect specification due to a poor definition or the like and the specification described in the program specification document is the originally correct specification. Therefore, in such a case, it is necessary for the programmer to modify the generated source program in accordance with the program specification document, and also to modify the software component, which hinders the improvement of the reliability of the software component and eventually the software component. It also hindered the reuse of parts.

The fourth problem in the prior art lies in the operating method and operability of software that supports the development of such software by making it into parts.

The operation for using the software that supports the software development as described above (such software is hereinafter referred to as a software development support tool, or simply a tool) is carried out by incorporating the tool. It can only be done with the device, and the person using the tool must always follow the operating method specified by the tool. For this reason, the manager must make a capital investment in proportion to the number of software developers, while the work of the software developers is limited to the installation location of the device in which the tool is installed and the operating hours. In addition, it is necessary to learn the unique operation method defined by the tool, which has hindered the improvement of software productivity.

The first object of the present invention is to provide a method for managing a component in a format that conforms to this standard by setting a certain standard that does not depend on the individuality of the designer or the characteristics of the application in the software componentization. By establishing it, it is to standardize software components and facilitate reuse of existing software.

Further, without designing the correspondence between the business program and the software parts by the designer or the programmer, the software parts required for the program are selected based on the names of the data items and the program specifications are prepared. By automatically generating and allowing the source program to be automatically generated from this program specification, the software component design information is automatically inherited to the program specification and the source program, and software productivity and reliability To improve.

A second object of the present invention is to enable the software program which allows modification such as change, addition, deletion, etc. of the generated program specification to prepare the specification described in the modified program specification in advance. It is to improve the productivity and reliability of software by enabling the source program to be automatically generated according to the program specifications even when the specifications are different from those of the parts.

A third object of the present invention is to make it possible to modify the program specifications as described above, and, if necessary, automatically adjust the software parts according to the specifications described in the modified program specifications. By making it possible to correct the software specification automatically, the consistency between the program specification and the software component is automatically maintained, the reliability of the software component is improved, and the reuse of the software component is facilitated. It is also to improve productivity.

A fourth object of the present invention is to modify the program specifications described in the second object, such as changes, additions and deletions, by using a so-called device other than a specific device in which the software development support tool is incorporated. By making it possible to use general-purpose spreadsheet software and document creation software on personal computers and workstations, reduce capital investment for using the software development support tool. In addition to providing a work environment where software developers are not limited to the operating conditions of specific equipment, and can develop software using general-purpose software that they are already familiar with, even if they do not have to learn the operation method specific to the tool. It is possible to
As a result, it is to improve the productivity of software.

[0022]

In order to achieve the first object, in the present invention, the software is defined as a software component by dividing the individual processing for each data item into several types in units of data items. , A method called a dictionary, and a related check process that determines the validity of data based on the interrelationship between multiple data items are defined as software parts and stored in a file called a related check definition document. It is characterized by having means and means for managing the software parts stored in these dictionaries and related check definition documents based on the data item names.

Hereinafter, the software parts stored in the dictionary and the related check definition will be collectively referred to as data item-centered software parts, and the processes defined in these parts will be referred to as data item-centered processes. ..

Further, in addition to the means for defining the software parts centered on the above-mentioned data items, means for defining information such as file and form attributes and layouts, and storing them in a file called a data definition, and for each program A means for defining information of input / output media and storing it in a file called a program definition document, and processing programs such as screens, forms, and files are divided into several types by focusing on the characteristics of the control structure.
A means for storing business individual processing as a program skeleton standard pattern that does not have it, and storing it in a file called a standard pattern library, and a standard function explanation part along with the program skeleton standard pattern parts in a file called a standard function explanation library. It is characterized by having means for storing.

Further, a software component is selected from the dictionary, the related check definition document, the data definition document, the program definition document, and the standard function explanation library based on the data item in the input / output medium of the target business program. Then, a means for automatically generating a program specification consisting of several types of specifications, and a program skeleton standard pattern part based on the program specification,
It is characterized by having means for automatically generating a source program by selecting and synthesizing a software component in the dictionary and a software component in the related check definition document.

As means for achieving the first object under a more strict standardization standard, the present invention provides means for dividing a single process for a data item in a dictionary into three types: checking, input editing, and output editing. It is characterized by having.

In order to achieve the second object, according to the present invention,
It is characterized by having means for making modifications such as changes, additions and deletions to the generated program specifications, and means for automatically generating a source program based on the program specifications corrected here. ..

In order to achieve the third object, in the present invention,
It is characterized by having means for automatically correcting the definition contents of the software parts stored in the dictionary, the related check definition document, the data definition document, and the program definition document from the corrected program specification document.

In order to achieve the fourth object, according to the present invention,
It is characterized by having a means that makes it possible to modify the generated program specifications using a general-purpose software on a device different from the device that generated the program specifications. And

[0030]

In order to achieve the first object, in the present invention, the software is defined as a software component by dividing the individual processing for each data item into several types and defining a plurality of data items. It was decided to define the related check process that determines the validity of data based on the mutual relationship between them as software parts, and manage these data-centric software parts based on the data item name. On the other hand, for software components that are not included in these data-centric software components, software components that define the attributes and layout of files and forms,
A program skeleton that does not have individual business processing by itself, dividing processing programs such as software parts, screens, forms, and files that define input / output medium information for each program into several types, focusing on the characteristics of the control structure. It is decided to define separately the software parts called standard patterns and the software parts called standard function explanation parts along the program skeleton standard pattern parts.

As described above, in dividing software into parts, which was different in the prior art depending on the individuality of the designer and the characteristics of the application, the method of dividing the software into parts was divided with the data items at the center. It is possible to set certain clear criteria that Furthermore, by storing each of these software parts in a file with a specific structure, it is possible to establish a method of managing in a format that meets this standard, so standardize the software parts and re-create the existing software. It is possible to facilitate the use of the software, which in turn can improve the productivity of software, and solve the problems of the conventional technology.

Further, a software component is selected from the dictionary, the related check definition document, the data definition document, the program definition document, and the standard function explanation library based on the data item in the input / output medium of the target business program. Then, a program specification consisting of several types of specifications is automatically generated, and based on the program specification, the program skeleton standard pattern parts, software parts in the dictionary, and software in the related check definition The source program is automatically generated by selecting and synthesizing the wear parts.

Therefore, according to the conventional technique, the source program can be automatically generated without associating the program with the software component, which the designer or programmer had to define for each business program. In addition, it is possible to automate the program specification creation work, which in the past was mostly dependent on the designer's manual work, and realize the automatic inheritance of design information from the software component design process to the program design process. It will be possible. As a result, the productivity and reliability of software can be improved, and the problems of the prior art can be solved.

As a means for achieving the first object under a stricter standardization standard, in the present invention, a single process for a data item in a dictionary is divided into three types: check, input edit, and output edit. did.
This allows the structure of the software components stored in the dictionary to be further restricted, improving the productivity and reliability of the software components and thus facilitating their reuse.

In order to achieve the second object, in the present invention,
Modifications such as changes, additions and deletions to the generated program specifications can be made, and a source program can be automatically generated based on the modified program specifications.

As a result, even if the program to be generated has a specification different from the software component prepared in advance in the program specification due to some reason such as exception processing, this should be reflected in the generation of the source program. Therefore, it is not necessary to modify the source program generated according to the software parts according to the program specification document as in the prior art, and it is possible to improve the productivity and the reliability of the software. The problems of the prior art can be solved.

In order to achieve the third object, in the present invention,
It became possible to automatically correct the definition contents of the software parts stored in the dictionary, the related check definition document, the data definition document, and the program definition document from the modified program specification document. As in the case described in the third problem in the prior art, even if the program specification is modified due to a change in the specifications of the target business program, it is still necessary to match the specifications described in the program specification. Software components can be automatically corrected. Therefore, in such a case, it is possible to automate the correction work of the software component, which was manually performed in the conventional technique, and improve the reliability of the software component and the productivity of the software to solve the problems of the conventional technique. ..

In order to achieve the fourth object, in the present invention,
For the generated program specifications, it is possible to modify the program specifications by using general-purpose software on a device different from the device that generated the program specifications. This makes changes to the program specifications,
For correction operations such as addition and deletion, use general-purpose so-called spreadsheet software and document-creation software on so-called personal computers and workstations other than the specific device in which the software development support tool is installed. It becomes possible to do it. Therefore, in addition to reducing the capital investment for using the software development support tool, the software developer is not limited to the operating conditions of a specific device and has to learn the operation method specific to the tool. It is possible to provide a work environment in which software development can be performed using general-purpose software that has already been used, and it is possible to improve the productivity of software and solve the problems of the conventional technology.

[0039]

Embodiments of the present invention will be described in detail below with reference to the drawings.

First, a hardware configuration for realizing this embodiment and means for realizing some functions of this embodiment will be described with reference to FIGS. 1 and 2.

FIG. 1 shows the hardware configuration of a system for implementing the present invention. Device group A (108)
Is the generation of the program specification or the source program, the correction of the generated program specification, and the update of the software component which is the generation source information of the program specification from the corrected program specification (in this embodiment, the reverse generation and It is a device group for performing. In addition, device group B (11
8) is used when the program specification is modified on a device group different from the device group A. As the device group B, a so-called personal computer or workstation is preferably used, but the optimum one is selected from the environment in which the user is placed. Also, for device group A, device group B
It is also possible to use multiple sets, or conversely, the device group B
It is also possible to perform all the functions and operations according to the present invention by using the device group A without the need.

First, the device group A (108) will be described with reference to FIG. The device group A includes a CPU (103) as its central device. An input device (10) for making an input for instructing execution of generation and for making data input when editing a generated program specification.
5), a display device (104) for displaying the data of the generated program specifications, and a printer (102) for outputting the generated program specifications are C
When connected to the PU as its input / output device and when the device group B is further used, the generated program specifications are transmitted to the device group B or the program specifications edited by the device group B are received. A communication device (107) for playing the game is connected to the CPU.

When the program specification is generated, the CPU also has an external storage device (106) for storing the software component which is the generation source and the generated program specification and the source program, and the generation of the program specification. A memory (101) for storing programs and data during execution of editing is connected. External storage device (106)
2 includes the dictionary (201), the related check definition document (202), the data definition document (203), the program definition document (204), the standard pattern library (205), and the standard function explanation library shown in FIG. (206), program specification library (210),
The files of the source program library (211) are included. The same applies to each device in the device group B (118). However, the data stored in the external storage device (116) is the program specification library (21
0) only.

In this embodiment, the program specification generation function (207), the program generation function (209) shown in FIG.
It is realized by four functions of a program specification editing function (212) and a software component reverse generation function (208).

The program specification generation function (207)
Dictionary (20) on the external storage device (106)
1), the related check definition (202), the data definition (203), the program definition (204) and the standard function explanation library (206) are input to generate a program specification, and the external storage device (106) is also generated. ) Store in the program specification library (210) above,
Alternatively, the generated program specification (213) is output to the printer (102).

The program generation function (209) inputs the program specification library (210), the data definition document (203) and the standard pattern library (205) on the external storage device (106) and generates a source program. And stores it in the source program library (211) on the external storage device (106).

The program specification editing function (212) is
An editor for inputting a program specification library (210) on an external storage device (106) and using the input device (105) and display device (104) to make corrections such as additions, changes and deletions of the program specifications. Is.

The program specification editing function (212) can also be used on the device group B (118). In this case, the program specification library (210) of the device group A (108) is transferred from the external storage device (106) of the device group A to the external storage device (116) of the device group B, and the display device of the device group B ( 114) and the input device (115), the program specification library (210) in the external storage device (116) of the device group B is edited, and the corrected program specification document is printed by the printer on the device group B. Output to (112).

Further, the program specification library (210) edited by the device group B is transferred again to the external storage device (106) of the device group A, and the program generation function (209) and the software described below are executed by the device group A. The parts reverse generation function (208) can be used.

In the above, the program specification editing function (2
In order to implement 12), it is also possible to use existing general-purpose software, for example, so-called spreadsheet software or document creation software, in addition to using a dedicated editor, by the conventional technique. Is also within the scope of the present invention.

Software component reverse generation function (208)
Inputs the program specification library (210) on the external storage device (106) and, if necessary, the dictionary (20) also on the external storage device (106).
1) Update the software components stored in the related check definition document (202), the data definition document (203) and the program definition document (204).

In this embodiment, the program specification (2
13) is a program processing outline diagram (FIG. 18), program function explanatory diagram (FIG. 19), check condition table (FIG. 20),
Related check condition table (Fig. 21), edit condition table (Fig. 22)
It consists of 5 types of specifications.

In the present embodiment, the above five types will be described as examples, but in addition to these, file specifications, record specifications, form specifications, screen specifications, database specifications, subroutine connection specifications, and other devices. Documents related to the program, such as the specifications for accessing the above resources and processes, can be output by the conventional technique, and in this case, it is within the scope of the present invention.

Prior to the description of the concrete procedure for generating the program specification according to the present invention, the dictionary (20
1), related check definition document (202), data definition document (203), program definition document (204), standard pattern library (205), standard function explanation library (2)
06) and the definition parts stored in each library will be described in detail.

FIG. 6 is a schematic diagram of an example of a business program to which the present invention is applied. The program 602 has an input file “KYFIL” having a data structure (605).
(601) is read, the validity of the data is checked, and invalid data is output form “KYERR” (604) having the layout 607 format, and normal data is output form “KYLST” having the layout 606 format. (603) is edited and output. Hereinafter, the present embodiment will be described with reference to this program example.

The dictionary (201) will be described with reference to FIGS. 7 to 11. A dictionary is a data item that defines and stores individual processing software components for each data item. Here, the data item refers to the smallest unit of data that has a business meaning, such as name and date of birth. The independent process is an operation that is performed only on the data item, and is a process that is not involved in any data item other than itself.

The dictionary software parts include
Data item definition part (701), check process definition part (7
06), an input edit definition part (707) and an output edit definition part (708). Here, the check process, the input edit process, and the output edit process are defined as follows. That is,
Checking process is to check the data format and validity of the data from the input form or input screen, and the input data editing process is to convert the input data to the format to be stored in the database or file. And
The output editing process is a process of converting data in a database or a file into a format that is output to an output form or an output screen.

In this example, "SIMEI-NO" (FIG. 7), "SIMEI" (FIG. 8), "NYUSYA-YM".
D "(Fig. 9)," SOKUI-CD "(Fig. 10),
An example of the definition for the data item "SIKYU-GK" (Fig. 11) is shown.

In the data item definition section (701), a comment that defines the attribute of the data item name, the Japanese name, the format and the number of digits, and the use and meaning of the data item is defined. In the example of FIG. 7, the data item name of (702) is "SI.
MEI-NO ”, (703) the Japanese name is“ name number ”, (704) defines that the attribute of the data is 9 digits, and (705) defines the meaning of the data item. It is defined.

The check processing definition section (706) defines the conditions for judging that the data is invalid, and the error code and error message used to notify the user that the data is invalid. Similarly, in the example of FIG.
(709) is a keyword indicating that a check is performed by calling a subroutine "SUB01" for the input related to this data item, (710) is an error code "ER10" when an error occurs, and (7)
11) defines that the error message is "Incorrect name number".

The input edit definition section (707) is shown in FIG.
Will be explained. In this example, (707) indicates "SUB.
By describing (SUB02), SIMEI-NO ”, it is defined that the input editing for this data item is performed by calling the subroutine“ SUB02 ”. Similarly, regarding the output edit definition section, in the example of FIG. 9, by describing “DATE” in (708), the output format is set to “Y” when performing output edit for this data item.
Y. MM. DD ”(YY: year, MM: month, DD: day) is converted and output. As mentioned above,
Keywords such as “SUB” and “DATE” are used to define the check conditions and the editing methods for input editing and output editing. Keywords are subroutine calls for check conditions, numeric checks, alphanumeric checks, range checks, etc., and for editing methods, some general software such as subroutine calls, formulas, and character string concatenation editing. It is a character string that represents a wear part and its grammar rules.

Next, the related check definition parts stored in the related check definition document (202) will be described with reference to FIG. The related check definition parts are defined in the form of a decision table of software parts for the related check processing between a plurality of data items.

In this example, the data item "SIKYU-GK" is used.
It is an example of a related check definition component for "SYOKUI-CD". (801) defines that the target data item name is "SIKYU-GK", and (80)
In 2), the related data item name is "SYOKUI-CD".
Is defined. It should be noted that there may be two or more related data item names. (803) is a relation check condition definition part, and (807) is a relation check error processing definition part.

The condition definition part (803) has a data item name (804), a condition (805) and a relation matrix (8).
06) is defined. In the error processing definition part (807),
Error code (808), error message (809)
And an association matrix (810).

The condition (805) is described by using a keyword as in the case of the dictionary software component. In this example, "When SIKYU-GK is not larger than 80000 and SYOKUUI-CD is larger than'A03 ', the error code is ER50 and the error message is'Payment amount is less than standard'." And, "SIK
YU-GK is greater than 80,000, SYOKUUI-
If the CD is not larger than'A03 ', the error code is ER60, and the error message is'the amount of payment exceeds the standard'. "

Next, the data definition document (203) will be described. The data definition document stores a form definition component defining file and form information, a file definition component, and a record definition component. Hereinafter, these definition parts will be described.

The form defining component will be described with reference to FIG. In this example, the “salary list” in FIG.
The information on the form (606) is defined. The form definition part includes a form attribute definition part (901),
There is a form layout definition section (907). (902) defines that the form definition part name is "KYLST", and (903) defines that the form name is "salary list", and (905)
Is the record length, and (906) is the number of lines of printing of the detailed work per page. Form layout definition section (90
7), the start line (908), the start column (909), and the number of repetitions of the detail line (9) when the data item is stamped on the form.
10), data item name (911), and attribute (912) are defined.

Similarly, FIG. 13B shows a form definition component related to the “error list” (607) in FIG.
Since the contents are the same as those in FIG. 13A, description thereof will be omitted.

The file definition component and the record definition component will be described with reference to FIG.

This example is based on the program example of FIG.
The file of (601) and its record format (605) are defined. (1002) has the file definition component name "KYFIL", and (1003)
Has a file name of "salary file" (1004)
Is the file symbol name used in the program is "KYUY
O-FILE ”, and (1005) defines that the name of the record definition component that defines the record format for this file is“ KYREC ”. Also, the record length (1006) and block length (1
007), a record format (1008), etc. are defined.

The record definition parts (1009) and the record layout definition part (101) are included in the record definition parts.
2) exists, and the record definition component name is (K) in (1010).
YREC ”, and (1011) defines that the record name is“ salary record ”. A level number (1013), a data item name (1014), and an attribute (1015) are defined in the record layout definition section.

In this embodiment, a batch processing program is used as an example, and the above three types are used as the data definition document. However, in a system that uses a screen or database in addition to files and forms, the screen definition is defined. Parts, database definition parts, and in the case of the client / server model compatible system, access definition parts for resources and processes on other devices can be defined in the same manner, and this is also included in the present invention.

The standard pattern library (205) will be described with reference to FIG.

A program skeleton standard pattern component (hereinafter referred to as a pattern skeleton component) which is a component of a process program such as a screen, a form, and a file, which is divided into several types by paying attention to the control structure, and which does not include the individual process for business. It is called a standard pattern). This example is a standard pattern of a type in which a file is read, checked, and output separately for normal data and error data. (1201) is a standard pattern name, and (1202) is a program skeleton part which is the standard pattern body. The check processing unit (1203), the related check processing unit (1204), and the edit processing unit (1205) are business-specific processes, and these are not included in the standard pattern, and the program generation function (209) is a software component centering on data items. Is the part that expands.

The standard function explanation library (206) will be explained with reference to FIG. The standard function explanation library stores standard function explanation parts according to a standard pattern. In this example, the standard pattern "C described above is used.
It is a standard function explanation part corresponding to "HK01". (13
01) is a standard function explanation part name, and (1302) is a description of the processing part of the function explanation. Note that there is a one-to-one correspondence between standard function explanation parts and standard patterns, so the standard function explanation part name (1301) is the same as the corresponding standard pattern name.

Referring to FIG. 15, the program definition document (20
The program definition parts stored in 4) will be described. This example defines the program specifications of (602) in the program example of FIG. (1101) is a program attribute definition part, and (1106) is an input / output medium definition part. In (1102), the program symbol name is "PR
OG01 ”, (1103) the program Japanese name is“ salary list creation ”, and (1104) defines that the standard pattern name used in the program is“ CHK01 ”. In (1105), a comment that specifies the outline of program processing is defined.

In the input / output medium definition section (1106), the file definition part name and the form definition part name corresponding to the input / output medium are set to (1107), and the respective input / output categories (hereinafter, I
/ O classification) (1108), usage classification (110)
9), a logical device name (1110), and a prefix (1111) added to a data item when used in a program are defined.

Here, the use classification (1109) is a classification indicating that each standard pattern is a file used for a certain special purpose. In this example, the use category of the input / output medium “KYERR” is defined as “ERR”, but this is the output destination of the error code or error message edited in the check process in the standard pattern “CHK01”. It shows a thing.

The procedure for generating the program specifications will be described in detail below with reference to the flowchart of FIG. First, a program definition part (shown in FIG. 15) of a business program to be generated (hereinafter abbreviated as the program) is input (step 301), a standard pattern name (1104) used in the business program, an input / output medium. Definition part name (110
8), use classification (1109) is acquired.

Next, the program processing outline diagram is developed and output (302).

A method of expanding the program processing outline diagram will be described with reference to FIG. The program name (1401), symbol name (1402), standard pattern name (1403), and process outline (1412) are program definition parts (FIG. 15), respectively.
(1103) (1102) (1104) (1105)
Output more acquired.

Definition component name of the input / output medium (1404) (1
406), I / O division (1407), use division (140
8), logical device name (1409), prefix (1410)
Are (1107) (1108) (1109) (1110) of the input / output medium definition part of the program definition part, respectively.
The information obtained from (1111) is output. The Japanese name (1405) of the input / output medium (1404) refers to the file definition component and the form definition component based on the definition component name (1107) of the input / output medium, and the file name (1003) and the form name (903). ) Is acquired and output.

In this example, since the definition component name (1107) is defined as "KYFIL" in the program definition component,
File definition parts (Fig. 14)
Referring to (a)), the “salary file” is acquired as the file name (1003) and output to the Japanese name (1405). (Hereinafter, the process of referring to the definition component based on the definition component name and acquiring the Japanese name of the file or form is called Japanese name acquisition. Similarly, for data items, the data item name is also Also, the Japanese name of the data item can be acquired by referring to the dictionary (201), which is also called Japanese name acquisition.) Furthermore, based on the above information, the input / output relation of the program is drawn ( 1411), the data is converted into a diagram and output.

Next, returning to FIG. 3, standard function explanation parts are input based on the standard pattern name (1104) already acquired from the program definition parts (303), and the program function explanation diagram is expanded and output (304).

The expansion method of the program function explanatory diagram will be described with reference to FIG. Program name (1501), program symbol name (1502), standard pattern name (150
3) outputs the ones acquired from the program definition parts (1103), (1102) and (1104) in the same manner as described above. The input medium name (1504) and the output medium names (1506) (1507) are also input / output medium definition part (110) of the program definition part in the same manner as described above.
From 6), the Japanese name is acquired by referring to the definition component name (1107), and the definition component name and the Japanese name are output. Whether the input medium is the input medium or the output medium can be referred to the corresponding I / O section (1108). Hereinafter, the I / O section of the input / output medium is “I”. An object is called an input medium, and an "O" is called an output medium.

Regarding the description of the process (1505) of the functional explanatory diagram, the description part (1302) of the process of the standard functional explanatory parts
Then, the Japanese name of the input / output medium acquired is combined and output.

Next, returning to FIG. 3, a check condition table is created based on the standard pattern name already acquired from the program definition part,
It is determined whether the related check condition table is generated (305). For example, the standard pattern “CHK01” used in this example.
Is a pattern that reads an input file, checks its contents, and writes it to an output file. For such a standard pattern including the check processing of the input data, it is determined that the check condition table and the related check condition table need to be generated and output.

When it is determined that the check condition table and the related check condition table need to be generated, the check condition table and the related check condition table are developed and output as follows.

First, the method of expanding the check condition table will be described with reference to FIG.

For each input medium defined in the program definition part, a file definition part and a record definition part are input based on the input medium definition part name, and further data for all data items used in the input medium are input. The check condition table is expanded for each item while referring to the dictionary (306).

The method of outputting the program name (1603) and the program symbol name (1604) is the same as that in the program processing outline diagram. Input media definition parts name (1
For 602) and its Japanese name (1601), the input medium definition part name acquired from the program definition part and the Japanese name acquired based on it are output. Output medium definition part name (1606) and its Japanese name (16
In 05), the information regarding the output medium to which the error code and the error message edited by the check process are output is output. Therefore, of the output media defined in the program definition part, the usage category (1109) is "ERR".
Is determined as the output destination of the error message, and the output medium definition component name and the Japanese name acquired based on it are output.

In the input item column, the data item name and its Japanese name (1607) are stored in the dictionary (201).
Attribute (1608) from the software component (701) of
Is acquired from the definition part of the input medium and is output.

In the check processing column, a keyword (1609), a check condition (1610), an error code (1611), and an error code (1611) are stored based on the contents defined in the check processing definition section (706) of the dictionary (201). The error message (1612) is output in the column. Regarding the check condition column, since the editing method is described by the keyword in the software component of the dictionary, the meaning indicated by the keyword is converted into Japanese and output.

In this example, first, the input medium definition part name (1107) of the program definition part is "KYFIL".
Therefore, the corresponding file definition parts (see FIG.
(A)), the corresponding record definition component name (1
010) which is “KYREC”. Further, the corresponding record definition component (FIG. 14B) is input, and the input item column and the check processing column are expanded and output in the order of the defined data items.

In the record layout definition (1012) of "KYREC", the first defined data item name (1014) is "SIMEI-NO". Therefore, first, the software component of the corresponding dictionary (201). Referring to (FIG. 7), the Japanese name (703) of the data item, “name number”, is acquired. Next, the keyword (709), the error code (710), and the error message (711) are acquired and output from the dictionary check processing definition unit (706). Keywords (16
09) "SUB (SUB01)" is a keyword indicating a software component for calling a subroutine, and S
UB01 represents the program symbol name of the called subroutine. Therefore, check condition column (1610)
"Check by calling a subroutine (SUB01)", expands the meaning indicated by the keyword into Japanese and outputs it (hereinafter, processing for converting such meaning indicated by the keyword into Japanese Called word conversion).

Record layout definition (1012)
The check condition table is generated by repeating the same procedure for the data item name (1014). Next, returning to FIG. 3, a related check condition table is generated (307). For all input media defined in the program definition part, enter file definition parts and record definition parts based on the input medium definition part name, and for all data items used in the input medium, for each data item Then, it is determined whether to generate the related check condition table.

The judgment condition is that there is a related check definition part for the data item, and all the related data items (802) described in the related check definition part corresponding to the data item are in the program. Only when included in the input medium to be used, the related check condition table for the related check definition part is generated. When there are a plurality of input media, the related data item may be included in any of the input media.

In this example, of the data item names (1014) on the input medium, there is a related check definition part for "SIKYU-GK" (FIG. 12), and the related data item name of the related definition part. Since "SYOKUI-CD" described in (802) is included in the record definition component (FIG. 14B) for the input medium of the program, it is determined that the input check condition table needs to be generated. At this time, the input medium definition component name that is the input source of the related data item is acquired.

There is no related check definition part "SI
For data items other than “KYU-GK”, it is determined that the related check condition table is not generated.

When it is judged that the related check condition table needs to be generated, the related check condition table is developed while referring to the related check definition parts and the software parts of the dictionary (201).

A method of developing the related check condition table will be described with reference to FIG. The method of outputting the program name (1701) and the program symbol name (1702) is the same as in the program processing outline diagram. The symbol name (1706) and its Japanese name (1705) on the input medium are the data item name acquired from the data item name (804) of the related check definition part and the Japanese name acquired based on it. Is output. The condition (1707) and matrix (1708) are acquired from the condition (805) and matrix (806) of the related check definition parts,
Output. Regarding the error code (1711), error message (1712), and matrix (1713), the error code (80
8), the error message (809) and the matrix (810) to obtain and output.

Regarding the definition part name of the input medium (1704) and its Japanese name (1703), the definition part name of the input medium including the data item, which has already been acquired at the time of determination of the related check, It also outputs that the Japanese name was acquired.

The definition component name (1710) of the output medium and its Japanese name (1709) are output in exactly the same manner as the error code and error message output destination in the check condition table.

Next, a method of expanding the editing condition table will be described with reference to FIG.

For all combinations of output media and input media defined in the program definition parts, for each combination, a file definition part based on the output medium definition part name,
Record definition parts and form definition parts are input, and for all data items used on the output medium, the editing condition table is expanded for each data item while referring to the dictionary software parts (Fig. Three
308).

The method of outputting the program name (1803) and the program symbol name (1804) is the same as in the program processing outline diagram. Output medium definition part name (1
802) and its Japanese name (1801), the definition part name of the input medium (1806) and its Japanese name (180
In 5), the output medium definition component name acquired from the program definition component, the input medium definition component name, and the Japanese name acquired based on the output medium definition component name are output.

For the output item column, output item name (1
807) outputs the data item name and the Japanese name acquired based on it, and the attribute (1808) is the attribute (912) defined on the output medium for the data item name.
And output. Input item name in the input item column (181
Regarding 2) and attribute (1813), the data item name on the input medium that becomes the information source when editing the output item, and the Japanese name (703) from the software item of the dictionary based on the data item name And attributes (704)
To get and output.

In the edit field, the keyword field (180) is used based on the contents defined in the input edit definition section (707) and the output edit definition section (708) of the dictionary.
9), edit method column (1810), and edit category column (1
811). In the edit method column (1810), since the edit method of the software component of the dictionary is described by the keyword, the keyword Japanese is converted and output. In the edit section column (1811),
If the editing method is the one developed from the input editing of the software component of the dictionary, "input editing" is output, and if the editing method is the one developed from the output editing, "output editing" is output.

Here, a description will be given of the judgment conditions for expanding the editing method defined in the software component of the dictionary for the data item into the keyword column (1809) and the editing method column (1810).

First, the expansion determination conditions for input editing will be shown. The input medium for the program is an input screen or
It is a medium entered by the user, such as an input form,
Alternatively, during execution of the program, the data item is newly created based on the data in the input medium, that is,
There are two points that the data item is not included in the input medium of the program but included in the output medium.
If you meet the requirements, expand the input editing.

The expansion determination conditions for output editing are shown below. When the output medium of the program is an output screen or a medium such as a form, and both the input medium and the output medium include the data item, the output editing is expanded.

Hereinafter, an example of generating the editing condition table in this example will be described in detail. The set of the output medium and the input medium defined in the program definition part is the output form “KYLST” (603), the input file “KYFIL” (601), and the output form “K”.
"YERR" (604) and input file "KYFIL"
Since it is (601), first, the first set of "KYLST"
And pay attention to "KYFIL". A form definition component (FIG. 13A) is input based on “KYLST” and attention is paid to the data items defined therein.

Since the first defined data item of the data item name (911) is "SIMEI-NO", the Japanese name of the data item "name number" (from the dictionary software component (Fig. 7)). 703), the attribute “X (4)” (912) is acquired from the form definition part and output. Since "SIMEI-NO" is included in the input medium,
Input editing is not expanded. Next, refer to the output edit definition section of the dictionary, but nothing is defined. This indicates that at the time of output editing, the data item is output without any processing. So leave the keyword blank,
"Transfer as is" is output to the edit method column (1810).

Since the second defined data item of the data item name (911) is "SIMEI", the Japanese name "name" of the data item from the dictionary software component (Fig. 8) is also changed. The attribute “N (7)” (912) is acquired from the form definition component name and output. Next, referring to the input editing definition section (707) of the dictionary, the editing method keyword "SUB (SUB02, SIMEI-
No) ”is acquired. This is a keyword indicating a software component for calling a subroutine. "SUB02" indicates a subroutine name, and "SIMEI-NO" indicates an input parameter to be passed to the subroutine. Therefore, the input item name (1
It can be seen that 812) is "SIMEI-NO".

Since "SIMEI" is not included in "KYFIL" which is the input medium of the program, it satisfies the expansion determination condition in the case of input editing. Therefore, the keyword "SUB" and the keyword-Japanese converted processing are entered in the edit column (1809, 1810), and the input item "SIMEI-NO" and its attribute are entered in the input item column (18).
12, 1813) respectively.

In this example, since nothing is defined in the output edit definition section of the dictionary, only the input edit is expanded in this way. However, when it is also defined in the output edit definition section, , Input edit and output edit are both expanded and output in this order.

Since the third data item defined in the data item name (911) is "NYUSYA-YMD", the "companion date" is changed from the dictionary software part (FIG. 9) to the form definition part. From name to attribute "X
(8) ”(912) and output item column (18
07, 1808). Next, referring to the output edit definition section (708) of the dictionary, the keyword “DA
TE ”is acquired. Since the output medium is a form, it satisfies the expansion determination condition for output editing. Therefore, the keyword column (1809) and the editing method column (1810)
Is output as a keyword and the keyword "Japanese is converted into YY.MM.DD format" is output, and the input item column (1812, 1813) has the same name as "N.
YUSYA-YMD "and its attributes are acquired from the dictionary software component and are output.

Regarding the fourth defined data item "SYOKUI-CD" of the data item name (911),
It develops like the case of "SIMEI-NO."

Regarding the fifth defined data item "SIKYU-GK" of the data item name (911),
Similar to "SIMEI-NO", there is no definition information in the input edit definition part and the output edit definition part of the dictionary, but the attributes acquired from the form definition parts are "Z, ZZZ, ZZ.
9 "(912), which is for zero suppression and comma editing, and in this case," edit in Z, ZZZ, ZZ9 format "is output to the editing method column (1810).

The procedure of program generation will be described below.

Prior to the description of the program generation procedure, the program specification library (2
10) The storage format of the program specifications described above will be described.

FIG. 23 shows the program specification library (2
10) It is a storage format of the above program processing outline diagram. This format is the program name (190
1), symbol name (1902), standard pattern name used in business program (1903), Japanese name of input / output medium (1904), definition part name (1905), I / O classification (1906), usage classification ( 1907), logical device name (1
908), a prefix (1909), and a program processing outline (1910). This is composed of exactly the same data as the output example of the program processing outline diagram in FIG.

FIG. 24 shows the program specification library (2
10) Storage format of the above check condition table. This format is defined as input media definition component name (2001), output medium definition component name (2002), and input item Japanese name (200).
3), symbol name (2004), attribute (2005), check processing keyword (2006), check condition (20)
07), error code (2008), and error message (2009). This is composed of exactly the same data as the output example of the check condition table in FIG.

FIG. 25 shows the program specification library (2
10) A storage format of the related check condition table above. This format is defined parts name (2101) of input / output medium, Japanese name of input item (2102), symbol name (2103), keyword of check condition (2104), error code (21
05), error message (2106) and matrix (2107). This is composed of exactly the same data as the output example of the related check condition table in FIG.

FIG. 26 shows the program specification library (2
10) It is a storage format of the above editing condition table. This format is defined by input media definition component name (2201), output medium definition component name (2202), output item Japanese name (2203), symbol name (2204), attribute (2205), and editing method keyword (2206). ), Editing method (2207), editing category (2208), input item Japanese name (2209), symbol name (2210), and attribute (2211). This is composed of exactly the same data as the output example of the editing condition table in FIG.

Next, the procedure of program generation will be described based on the flowchart.

FIG. 4 is a flowchart showing the procedure of program generation, and FIGS. 27 to 29 show the program specifications (FIGS. 23 to 26) and the definition parts (FIGS. 13 to 14) in the data definition. It is an example of developing a source program by the original program generation function. Hereinafter, the specific procedure of the program generation function will be described using this example.

The generation function first acquires the standard pattern name “CHK01” (1903) to be used from the program processing outline diagram (1900) of the business program to be generated, and stores the corresponding standard pattern (1202) in the standard pattern library (205). )) (Step 401).

In the input / output component expansion (402), the definition component of the input / output medium is input from the data definition document (203) based on the input / output medium name defined in the program processing outline diagram of the program, and the program is input. The source code of the output declaration part is generated, and this is combined with the standard pattern input in step 401.

The expansion method of the input / output declaration portion will be specifically described with reference to FIG. The program generation function uses “KYFIL” and “KYLST” from the input / output medium definition part name (1905) described in the program processing outline diagram (1900).
And the like, and the corresponding file definition component (1001) and form definition component (901,
907), and the input / output environment definition (2302, 2303), file description (2304, 2306) and data description (2305,
2307) and generates a standard pattern (1202).
To synthesize.

The form printing process expansion (404) is performed when the program uses a standard pattern for outputting a form, and based on the output medium definition component name described in the program process outline diagram of the program. Data definition document (2
03), the corresponding form definition component is input, a form editing work area and a form output procedure are generated from this, and combined with the standard pattern input in step 401.

The form printing process expansion process (4
04) will be specifically described. The program generation function is based on the form definition part name (1905) described in the program processing outline diagram (1900), and the form definition part (90
1, 907), and based on these definition contents, a work area (2309) for editing a form and a work area (230) such as a counter used when executing a program.
8) is generated, and this is combined with the standard pattern (1202).

In the check, related check, and edit processing expansion (405), the data item centering is performed based on the keywords described in the check condition table, the related check condition table, and the edit condition table in the program specifications. The process is generated, and the check process unit (12
03), the related check processing unit (1204), and the editing processing unit (1205).

With reference to FIG. 29, the source program expansion method will be specifically described by taking the expansion from the editing condition table as an example. First, the edit condition table (2200) of the program is read, a process for the data item is generated based on the edit condition defined by the keyword (2206) in the edit condition table, and this is used as a standard pattern edit process. Department (1
205). At that time, the work area necessary for editing the data item is also generated at the same time. For example, the keyword "DA" in the third line of the editing condition table (2200)
In the case of "TE" (2206), as shown in the area (2310), a work area for dividing the date into years, months, and days and a work area for editing are generated.

When further expanding the processing for the data item, as shown in this example, the program processing outline diagram (190
The prefix (1909) defined in 0) is added to the item name on each file. For example, the statement (23
As shown in 14), for the data item "SIKYU-GK", the input item is "IN-" and the output item is "OU."
"-" Is added, the symbol item name on the input file is "IN-SIKYU-GK" (2315), and the symbol item name on the output file is "OU-SIKYU-GK" (23
16) and it was decided at the time of program generation. As a result, the software component centering on the data item is made independent from the definition component of the input / output medium such as a file that handles the data item.

FIG. 28 shows the standard pattern (1202).
The undefined file symbol name therein is replaced with the file symbol name (1004) of the file definition part.

In the source program output (406), the target business program generated by the above processing is output to the source program library (211).

In the present embodiment, an example of a batch processing program has been described, but the same applies to an interactive processing program involving access to a database and a program for accessing resources and processes on other devices. Can be generated.

Further, in the present embodiment, the source program is generated from the program specification, but the dictionary (201), the related check definition (202), the data definition (203), Program definition (204), standard function explanation library (20
It is also possible to directly input 6) to directly generate the source program, and the case of using this method is also included in the scope of the present invention. In this case, in the same way as when creating the program specifications, the software parts centering on the data items are selected based on the data items existing in the input / output medium of the target business program, and are combined into the standard pattern. ..

Finally, the program specification editing function (212) and software component reverse generation function (208) in this embodiment will be described together with examples of using these functions. The usage example introduced below is
For the program example shown in FIG. 6, the program specification editing function (212) is used to modify the program specifications, and the software parts reverse generation function (208) is used from the corrected program specifications to create the software parts. Is an example of correcting.

First, examples of modification of various program specifications will be introduced. 24A is an example of the check condition table immediately after generation, and FIG. 24B is an example of the check condition table after correction. 25A is an example of the related check condition table immediately after generation, and FIG. 25B is an example of the corrected related check condition table. FIG. 26A is an example of the edit condition table immediately after generation, and FIG. 26B is an example of the edited edit condition table.

Here, the editing condition table (FIG. 26) will be taken up and the correction contents will be introduced in detail. Third in FIG. 26 (b)
In the line (2222), the keyword is changed from "DATE" to blank, and accordingly, the editing method is changed from "to YY.MM.DD format ..." to "Transfer as is" (this operation is referred to as correction 1). This is the data item "NYUSYA
"-YMD" means that the data is not processed at the time of output editing. Further, in FIG. 26B, the fourth row (2212) in FIG. 26A has been deleted (the same correction 2). This is the data item "SYOKUI-
CD ”from the output medium. FIG. 26
In the fourth line (2223) of (b), the output item "SIKY
U-GK ”attributes from“ Z, ZZZ, ZZ9 ”to“ Z,
ZZ9 ". In addition, change the keyword from blank to "C
OMP (SIKYU-GK / 1000) ", and accordingly, the editing method is" edit in the format of Z, ZZ9 in units of 1,000 yen "(correction 3). This is "SIKYU
This is to newly define an output editing process of outputting a value divided by 1000 when outputting "-GK".

The program specification library (21
Regarding the modification of the program specification in 0), since the program specification is stored as an image of a simple table as shown in FIGS. 23 to 26, without using a dedicated editor,
It is also possible to use general-purpose spreadsheet software or document creation software, and this is also included in the scope of the present invention. Furthermore, the device group A that generated the program specifications
It is also possible to transfer to a device group B (118) which is a device different from (108) and edit it on the device group B using general-purpose spreadsheet software or document creation software. Yes, this is also within the scope of the present invention.

Next, the procedure of software component reverse generation will be described with reference to FIG. Inverse generation in this embodiment means
It means to rewrite the software component which is the source of the information based on the modified program specification to reflect the modification content of the program specification.

In the software component reverse generation function (208) of this embodiment, a program processing outline diagram is input (501), and the program definition document (204) is reversely generated (502). Next, the check condition table is input (503), and the dictionary (201) and the data definition document (203) are subject to reverse generation (504). Next, the related check condition table is input (505), and the dictionary (201), the related check definition (202), and the data definition (203) are inversely generated (50).
6). Next, the editing condition table is input (507), and the dictionary (201) and the data definition document (203) are subject to reverse generation (508).

Next, the result of reverse generation will be described. Figure 3
In FIGS. 0 to 36, only the definition contents changed before and after the reverse generation when the reverse generation is performed based on the corrected program specifications described above are shown. 30 to 34
Is an example of a dictionary software component after reverse generation, and examples of definitions before reverse generation are shown in FIGS. Fig. 35
Is an example of a related check definition component after reverse generation, and FIG. 12 shows a definition example before reverse generation. FIG. 36 shows an example of a form definition component for “KYLST” in the data definition document after reverse generation, and a definition example before this reverse generation is FIG. 13 (a).

The above-mentioned modified editing condition table (see FIG. 26)
A specific procedure for reverse generation will be described based on the example of (b).

In Modification 1, the keyword (2214) is changed to blank. In this case, the reverse generation function first refers to the edit category (2215), and since this is “output edit”, it refers to the symbol name (2210) and the input item “NYUSYA-
YMD "(2216). The corresponding software component of the dictionary (201) is the target of reverse generation. As shown in the input edit definition part (2401) of the software component (FIG. 32) of the dictionary after reverse generation, the keyword is changed to blank.

In FIG. 26B, the data item "SYOKUI-CD" (2212) is deleted from the output items by the correction 2. In this case, the reverse generation function uses the form definition component “KYLST” (FIG. 1) of the form that is the output medium of the program.
Delete "SYOKUI-CD" from 3 (a)). In the form definition component (FIG. 36) after the reverse generation, as shown in the form layout definition part (2601), the data item “SYOKUI-CD” is deleted.

In Modification 3, the keywords are changed as in Modification 1. In this case as well, the editing category is "output editing" (22
20), the symbolic name "SIKYU-GK" (222
1) is acquired, and the output edit definition part of the dictionary software component (FIG. 34) corresponding thereto is the target of reverse generation. The corrected keyword (2206) is "COMP
(SIKYU-GK / 1000) "(2219), so the keyword of output editing of dictionary software component for" SIKYU-GK "(2402)
To update.

In Modification 3, the symbol name "SIKY
The attribute (2218) of "U-GK" (2217) is changed. In this case, the attribute of the data item in the form definition component “KYLST” (FIG. 13A) of the form that is the output medium is changed. Form definition component after reverse generation (Fig. 36)
The change contents are reflected as shown in (2602) of the form layout definition part of.

As described above, the software component reverse generation function (208) reverses the procedure of the program specification generation function (209) to the program specification library (21).
From 0), the modified software component is specified, and the software component is updated based on the contents of the program specification library (210). In the case of using the program processing outline diagram, the check condition table, and the related check condition table as well, the reverse generation of the software component can be performed as in the editing condition table.

[0153]

Since the present invention has the processing procedure described above, it has the following effects.

The software is defined as a software component by dividing the single processing for each data item into several types in data item units, and the validity of the data is judged based on the mutual relationship between the plurality of data items. The related check process is defined as a software component, and these data-centric software components are managed based on the data item name. On the other hand, for software components not included in these data-centric software components, files, software components that define the attributes and layout of forms, software components that define input / output medium information for each program, screens, and forms. , A software component called a program skeleton standard pattern, which divides processing programs such as files into several types, paying attention to the characteristics of the control structure, and which does not have individual business processing by itself,
It was decided to define it separately for the software parts called standard function explanation parts along the program skeleton standard pattern parts.

As described above, in dividing software into parts, a certain definite standard for dividing the software around the data items can be set for the method of dividing the software when dividing into parts. By storing each part in a file with a specific structure, it is possible to establish a method to manage it in a format that meets this standard, so standardize software parts and facilitate reuse of existing software. Therefore, it is possible to improve the productivity of software.

Further, a software component is selected from the dictionary, the related check definition document, the data definition document, the program definition document, and the standard function explanation library based on the data item in the input / output medium of the target business program. Then, a program specification consisting of several types of specifications is automatically generated, and based on the program specification, the program skeleton standard pattern parts, software parts in the dictionary, and software in the related check definition The source program is automatically generated by selecting and synthesizing the wear parts.

Therefore, the source program can be automatically generated without the designer or programmer associating the business program with the software component.
Further, it becomes possible to automate the work of creating the program specifications and realize the automatic inheritance of the design information from the software component design process to the program design process. This can improve the productivity and reliability of software.

In addition to this, in order to achieve the above-mentioned software componentization under a more strict standardization standard, the present invention checks the independent processing for the data item in the dictionary, input edit, and output edit. I decided to divide it into three types. This allows the structure of the software components stored in the dictionary to be further restricted, improving the productivity and reliability of the software components and thus facilitating their reuse.

Further, according to the present invention, it is possible to modify, add, or delete the generated program specification,
Furthermore, we decided to automatically generate the source program based on the program specifications revised here.

As a result, the software component prepared in advance in the program specification is, for some reason, such as that the program to be generated includes exception handling.
Even when different specifications are described, this can be reflected in the generation of the source program, and the productivity and reliability of the software can be improved.

Further, in the present invention, it is possible to automatically correct the definition contents of the dictionary, the related check definition document, the data definition document, and the software parts stored in the program definition document from the modified program specification document. did. Therefore, it is possible to automate the modification work of the software parts due to the specification change and the like, and it is possible to improve the reliability of the software parts and the productivity of the software.

Further, according to the present invention, it is possible to modify the generated program specification by using general-purpose software on a device different from the device which generated the program specification. did. As a result, the facility investment for using the software development support tool of the present invention is reduced, and the software developer does not have to be restricted by the operating conditions of a specific device, and has a tool-specific operation method. It becomes possible to provide a work environment in which software development can be performed using general-purpose software that is already familiar, without mastering
As a result, the productivity of software can be improved.

[Brief description of drawings]

FIG. 1 is a hardware configuration diagram of a system for implementing an embodiment of the present invention.

FIG. 2 is a functional configuration diagram of a system that implements the present invention.

FIG. 3 is a flowchart showing a procedure for generating a program specification.

FIG. 4 is a flowchart showing a procedure of program generation.

FIG. 5 is a flowchart showing a procedure for software component reverse generation.

FIG. 6 is a diagram showing an example of a business program used for explaining the present embodiment.

FIG. 7 is a diagram showing a definition example of a dictionary.

FIG. 8 is a diagram showing a definition example of a dictionary.

FIG. 9 is a diagram showing a definition example of a dictionary.

FIG. 10 is a diagram showing a definition example of a dictionary.

FIG. 11 is a diagram showing a definition example of a dictionary.

FIG. 12 is a diagram showing a definition example of a related check processing definition component.

FIG. 13 is a diagram showing a definition example of a form definition part.

FIG. 14 is a diagram showing definition examples of a file definition component and a record definition component.

FIG. 15 is a diagram showing a definition example of a program definition part.

FIG. 16 is a diagram showing an example of standard pattern components.

FIG. 17 is a diagram showing an example of standard function explanation parts.

FIG. 18 is a diagram showing an output example of a program processing outline diagram.

FIG. 19 is a diagram showing an output example of a program function explanatory diagram.

FIG. 20 is a diagram showing an output example of a check condition table.

FIG. 21 is a diagram showing an output example of a related check condition table.

FIG. 22 is a diagram showing an output example of an editing condition table.

FIG. 23 is a diagram showing an example of a storage format of a program processing schematic diagram.

FIG. 24 is a diagram showing an example of a storage format of a check condition table.

FIG. 25 is a diagram showing an example of a storage format of a related check condition table.

FIG. 26 is a diagram showing an example of a storage format of an editing condition table.

FIG. 27 is a diagram showing an example of source program expansion by a program generation function.

FIG. 28 is a diagram showing an example of source program expansion by a program generation function.

FIG. 29 is a diagram showing an example of developing a source program by a program generation function.

FIG. 30 is a diagram showing a definition example of a dictionary after reverse generation.

[Fig. 31] Fig. 31 is a diagram illustrating a definition example of a dictionary after inverse generation.

[Fig. 32] Fig. 32 is a diagram illustrating a definition example of a dictionary after reverse generation.

[Fig. 33] Fig. 33 is a diagram illustrating a definition example of a dictionary after reverse generation.

[Fig. 34] Fig. 34 is a diagram illustrating a definition example of a dictionary after inverse generation.

FIG. 35 is a diagram showing a definition example of a related check definition component after reverse generation.

FIG. 36 is a diagram showing a definition example of a form definition component after reverse generation.

[Explanation of symbols]

201 ... Dictionary, 202 ... Related check definition document, 203 ... Data definition document, 204 ... Program definition document, 205 ... Standard pattern library, 206 ... Standard function explanation library, 207 ... Program specification generation function, 208 ... Software component reverse Generating function, 209 ... Program generating function, 210 ... Program specification library, 211 ... Source program library, 212 ... Program specification editing function, 213 ... Program specification,
701 ... Data item definition part, 702 ... Data item name, 7
03 ... Japanese name, 704 ... Attribute, 705 ... Comment, 7
06 ... Check processing definition part, 707 ... Input edit definition part,
708 ... Output edit definition part, 709 ... Check condition, 71
0 ... error code, 711 ... error message, 802
... Related data item name, 803 ... Condition definition part, 807 ... Error processing definition part, 901 ... Form attribute definition part, 902 ... Form definition part name, 903 ... Form name, 904 ... Form symbol name,
907 ... Form layout definition part, 1001 ... File attribute definition part, 1002 ... File definition part name, 1003 ...
File name, 1004 ... File symbol name, 1005 ... Record definition component name, 1009 ... Record attribute definition part, 1
010 ... Record definition component name, 1011 ... Record name,
1012 ... Record layout definition part, 1101 ... Program attribute definition part, 1102 ... Symbol name, 1103 ... Program name, 1104 ... Standard pattern name, 1105 ... Process outline, 1106 ... Input / output medium definition part, 1107 ... Definition part name, 1108 Input / output (I / O) classification, 1109 ... Usage classification, 1110 ... Logical device name, 1111 ... Prefix, 1
201 ... Standard pattern name, 1202 ... Standard pattern, 1
203 ... Check processing unit, 1204 ... Related check processing unit, 1205 ... Editing processing unit, 1301 ... Standard function explanation component name, 1302 ... Standard function explanation component

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Naoki Hashimoto 12 stock companies at 890 Kashimada, Sachi-ku, Kawasaki-shi, Kanagawa Hitachi, Ltd. Information Systems Development Division (72) Inventor, Ho Nakagawa 890 Kashimada, Sachi-ku, Kawasaki-shi, Kanagawa Number 12 stock company Hitachi Information Systems Development Division

Claims (5)

[Claims] 1. A means for storing software in a file called a dictionary, which is defined as a software component by dividing the software into independent processing for each data item in units of data items, and between a plurality of data items. A means for defining related check processing that determines the validity of data based on mutual relationships as a software component and storing it in a file called a related check definition document, and a software component stored in these dictionaries and related check definition documents. Defines information such as file and form attributes and layout, and a method of managing
The characteristics of the control structure that means to store in a file called a data definition, the means to define the input / output medium information for each program and to store in a file called a program definition, and the processing programs such as screens, forms, and files. Paying attention to the above, it is divided into several types, and the individual work processes are made into parts as a program skeleton standard pattern that does not have itself,
Means to store in a file called standard pattern library, means to store standard function explanation parts along with program skeleton standard pattern parts in a file called standard function explanation library, dictionary, related check definition document, data definition document, program From the definition document and standard function explanation library, select a software component based on the data item name in the input / output medium of the target business program and create a program specification consisting of several types of specifications. The source program is automatically created by selecting and synthesizing the program skeleton standard pattern parts, the software parts in the dictionary and the software parts in the related check definition, based on the automatic generation means and the program specifications. And means for generating Over data-centric software program automatic generation method by the component. 2. The automatic program generation method by the data-centric software component according to claim 1, further comprising means for dividing a single process for a data item in the dictionary into three types of checking, input editing, and output editing. Automatic program generation method using data-centric software parts. 3. The automatic program generation method using the data-centric software component according to claim 1 or 2, and means for making modifications such as changes, additions and deletions to the generated program specifications, and further modifying here. An automatic program generation method using data-centric software parts, characterized by having means for automatically generating a source program based on the specified program specifications. 4. An automatic program generation method using data-centric software components according to claim 1, 2, or 3,
Data-centric software characterized by having a means for automatically correcting the definition contents of the software parts stored in the dictionary, the related check definition document, the data definition document, and the program definition document from the modified program specification document. Automatic program generation method by wear parts. 5. The automatic program generation method using the data-centric software components according to claim 1, 2, 3 and 4, wherein the generated program specification is on a device different from the device which generated the program specification. An automatic program generation method using data-centric software parts, characterized in that it has means for making it possible to modify the program specifications using general-purpose software.