JPH0744358A - Production support system for software - Google Patents

Abstract

PURPOSE:To improve the efficiency of production at the time of program genera tion by automatically extracting a program generated by an input/output rela tion generation part and the input/output relation of an input/output medium related to this program. CONSTITUTION:Manual work can be eliminated and the efficiency of production at the time of program generation can be improved by automatically extracting the relation with the input/output medium (such as a picture, slip, file or magnetic tape, etc.,) related to the program while using an input/output relation generation part 103 and a program relation generation part 109. On the other hand, the definition of item transition can be preformed mechanically and a software process can be automated by providing an item transition registration part 106 at a software generation tool. Further, software developments overlapped each other can be decreased since procedures related to items can be systematically managed by providing an item dictionary registration part 107. Moreover, a parts production rate can be improved since detailed parts development can be defined by providing a parts registration part 102 and a parts development part 108.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to software production support technology, and is particularly suitable for efficiently designing and programming software by interactive operation on a display using a workstation or the like. The present invention relates to a software production support system.

[0002]

2. Description of the Related Art Conventionally, for the purpose of improving software productivity, for example, pages 41 to 41 of "Nikkei Computer Separate Volume Software" (1988, Nikkei BP).
Page 87 and "Nikkei Computer 1990.1
1.5 (no. 239) ”(1990, published by Nikkei BP), pages 78 to 101, and so on.
E (Computer Aided Software)
Software production support systems such as engineering and computer-aided software engineering tools have been developed.

In these software production support systems, (A) a function for defining the flow of data between programs by pictures (B) a function for defining screen transitions by pictures (C) layout and items of screens, forms, and files (D) A function for registering a program part (E) A function for expanding a program part and generating a program. With these features,
The operator is a data flow diagram that describes the business process specifications of the business system to be designed, or a system that breaks down from this data flow diagram and describes the computer process flow of each business in this data flow diagram. Flow design diagram, screen transition diagram that describes the flow and operation of each screen of each business in the data flow diagram, and the form specifications of the screen in this screen transition diagram that is broken down from this screen transition diagram It is possible to describe the screen form diagram and the like on the display as a figure. The software production support system uses reusable program parts registered in advance corresponding to each figure based on the description of these data flow diagrams, system flow design diagrams, screen transition diagrams, screen form diagrams, etc. To automatically generate a program related to the target business system.

However, the above-mentioned functions alone have the following problems. (A) Issues related to production efficiency during program generation: In the conventional software production support system, program generation has a function to define screen transitions with a picture and a function to define screen / form / file layout and item attributes. , The function of registering a program component is used to develop the program component to generate a program. Therefore, at the time of generating the program, it is necessary to define the screen / form / file name related to the program and the input / output type (input / reference / update / output), which causes a lot of manual work by the user. However, the productivity of program generation cannot be increased. (B) Issues related to software process automation: When developing a program related to a screen, it is essential to define the state in which the items in the screen transit according to the screen input by the user of the developed screen program. The support system does not have the function of defining item transitions on the screen, and cannot automate the entire software development process. (C) Issues related to reducing duplicate software development:
The conventional software production support system is
With respect to items such as files, since there is no function to define the procedure to be expanded in the office processing program, there are frequent developments of procedures for items that are duplicated among multiple programs that use the same item. Therefore, the development cost is high and the maintenance range is wide. (D) Issues related to component generation rate: In the component registration function of the conventional software production support system, the component development function is
The character string of a part is replaced with a program generation parameter, and the expansion procedure of the part can be defined in the part, and the generation rate of the program cannot be increased.

[0005]

The problem to be solved by the prior art is that, in the prior art, the screen / form / file name and input / output type (related to the program at the time of generating the program in the software development process) Input / reference / update / output) definition, definition of transition status of items in the screen corresponding to screen input operation during screen program development, and expansion to office processing programs for items such as screens, forms, and files It is not possible to define the procedure to be performed and the procedure for deploying the component in the component. An object of the present invention is to solve the problems of the conventional techniques, reduce the software development cost by automating the entire software development process, reduce the development of duplicate software, and improve the quality of software by increasing the program generation rate. It is to provide a software production support system capable of improving the productivity and improving the productivity of the software.

[0006]

In order to achieve the above object, the software production support system of the present invention comprises:
(1) Focusing on the flow of data, at least a data flow diagram that describes the business process specifications of the business system to be designed, and a breakdown from each data flow diagram of each business in this data flow diagram. A system flow design diagram that describes the flow of computer processing, a screen transition diagram that describes the flow and operation of each screen of each business, and a breakdown from this screen transition diagram, and the form specifications of the screen in this screen transition diagram The screen form diagram to be described is described in figures on the display, the pre-registered reusable program parts are developed corresponding to each figure, and the production of the program related to the business system is produced. In the support system, the computer process defined on the system flow blueprint and the folder accessed by this computer process. Based on the flow of data between input / output media such as files, input / output of computer processing to the input / output medium and access relations such as reference are generated, and input related to the related computer processing and the input / output medium are registered. An output relationship generation unit is provided, and the program parts corresponding to the computer processing are expanded using the access relationship of the computer processing for the input / output medium generated by the input / output relationship generation unit. Also,
(2) An item transition definition section is provided for displaying the item transition condition table when the screen form diagram is generated, and for registering the transition conditions between the items input via this item transition condition table. The feature is that the program condition relating to the transition between the items is expanded by using the transition condition between the registered items. In addition, (3) the item procedure definition table is displayed when the screen form diagram is generated, and at least the item input check procedure and the item data that are input through the item procedure definition table are used alone or in other plurals. There is an item dictionary definition part for registering the procedure generated from the item and the procedure for the item including the output check procedure of the item, and the procedure for the item registered in this item dictionary definition part is used to It is characterized by performing expansion. In addition, (4) a parts registration definition screen is displayed on the display, and a parts registration unit for registering the expansion procedure of this program part in a reusable program part input via this parts expansion definition screen. Provided,
It is characterized in that the parameter part of the program part is expanded using the part expansion procedure of the program part registered by the part registration unit. Also, (5) above (1)
The input / output relation generating unit, the item transition definition unit of (2), the item dictionary definition unit of (3), and the component registration unit of (4) are provided in any combination, and information from each is provided. Are associated with each other and the program parts are expanded.

[0007]

According to the present invention, the input / output relationship of the program and the input / output medium (screen, form, file, magnetic tape, etc.) related to the program generated by the input / output relationship generating section can be automatically extracted. Therefore, at the time of generating the program, the operator does not need to manually define the names of the screens, forms, files, etc. related to the program and the input / output types (input / reference / update / output). It is possible to improve the production efficiency at the time of program generation, which is the problem of the above (a). Further, by providing the item transition registration unit, the operator can define the transition state of the item in the screen according to the screen input of the system user at the time of displaying the screen form diagram. It is possible to automate the entire software development process, which was the issue of. In addition, by providing the item dictionary registration unit, the operator can check the items such as the item input check procedure, the procedure of generating item data from a single item or a plurality of other items, and the item output check procedure. , It is possible to define the procedure to be developed in the program, and to manage the procedure related to the item uniformly. As a result, it is possible to avoid the development of duplicate procedures between a plurality of programs that use the same item, reduce the duplicate software development that was the problem of (c) above, reduce the development cost, and maintain the maintenance range. Can be reduced. Furthermore, by providing a parts registration unit,
Detailed component development can be defined, detailed component development can be performed without replacing the character string of the program component with the program generation parameter by the component development function, and the generation rate of the component which was the problem of (d) above. It is possible to raise.

[0008]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a block diagram showing a first embodiment of a configuration relating to the present invention of a software production support system of the present invention. In this example, a computer processing program for issuing an order receipt is generated. In the figure, 101 is a display device for inputting and displaying data, and 110 is a memory for storing data. It is a device. Reference numeral 102 denotes a component registration unit that registers a program input on the screen of the display device 101 in the storage device 110 as a reusable component, and 103 denotes a program and an input / output medium such as a form, file, magnetic tape, or OCR. Is an input / output relationship generation unit that generates an input / output relationship with
Input / output relational data is generated from the flow chart of the data between the programs input on the screen 01 and transferred to the program relation generation unit 109 described later.

Reference numeral 104 denotes a layout registration unit for registering layout data of the input / output medium, which is used for the display device 1.
The layout data input on the screen 01 is transferred to the program-related generation unit 109 described later. Reference numeral 105 denotes a screen transition registration unit that registers a transition state of a screen that is an input / output target for a plurality of screens used in the program,
The screen transition data input on the screen of the display device 101 is transferred to the program-related generation unit 109 described later. 1
Reference numeral 06 denotes an item transition registration unit that registers a transition state of an item to be input / output with respect to an item on the screen used in the program. The item transition data input on the screen of the display device 101 is associated with a program related program to be described later. Transfer to the generation unit 109. Reference numeral 107 denotes an item dictionary registration unit that registers a procedure related to an item used in the program, and transfers procedure data related to the item input on the screen of the display device 101 to a program-related generation unit 109 described below.

Reference numeral 109 designates the input / output relationship generation unit 10
3, regarding the data transferred from the layout registration unit 104 and the screen transition registration unit 105, a relation is created by the name of the program and the name of the input / output medium, and the layout registration unit 104, the item transition registration unit 106, and the item dictionary registration unit. 10
It is a program relation generation unit that generates a relation by the name of an item with respect to the data transferred from 7, and registers the generated program relation data in the storage device 110. Reference numeral 108 also extracts input / output items from the information registered in the association storage device 110 by the program association generation unit 109 from the input / output medium, screen transition, and item transition information associated with the program generated by the input / output relation generation unit 103. At the same time, a screen control procedure is generated from the screen transition, item transition, and item dictionary information, and a procedure related to the item is generated from the input / output item and the item dictionary, and the component expansion procedure in the component is executed. A component expansion unit that expands a parameter portion of a component, inputs an instruction on the screen of the display device 101 when an error occurs, extracts program-related data and a component from the storage device 110, and stores the generated program in the storage device 110.
To store.

FIG. 2 is a block diagram showing a second embodiment of the configuration relating to the present invention of the software production support system of the present invention. In this example, the input / output relationship generator 1
03, layout registration unit 104, screen transition registration unit 10
5, the respective outputs of the item transition registration unit 106 and the item dictionary registration unit 107 are stored in the storage device 110 as they are without passing through the program-related generation unit 109. The program relation generation unit 109 creates a relation between the input / output relational data, the layout data, and the screen transition data stored in the storage device 110 by the name of the program and the name of the input / output medium, and also generates the layout data and the item transition data. With respect to the item dictionary data, a relation is generated by the name of the item, and the generated program-related data is stored in the storage device 110. Then, the component expanding unit 108 inputs / outputs from the information stored in the association storage device 110 by the program association generating unit 109, the input / output medium related to the program generated by the input / output relation generating unit 103, the screen transition, and the item transition information. While extracting items, create screen control procedures from screen transitions, item transitions, and item dictionary information,
By executing the procedure related to the item from the input / output item and the item dictionary, the component expansion procedure in the component is executed.
The parameter part of the component is expanded, and when an error occurs, the program-related data and the component are extracted from the storage device 110 based on the instruction input from the screen of the display device 101, and the generated program is stored in the storage device 110.

The operation of the software production support system of this example will be described below. FIG. 3 is an explanatory diagram showing an example of the operation of the software production support system in FIG. 2 according to the present invention. The component registration unit 102 inputs the component (program) name and the component designated on the component definition screen 301, and inputs these input data into the component data file 3
Register at 13. The input / output relationship generation unit 103 inputs the input / output relationship between the program designated on the input / output relationship definition screen 302 and the input / output medium and the data flow between the programs, and inputs the input / output medium for each program. Output relation data is generated and registered in the input / output relation data file 314. The layout registration unit 104 displays the layout definition screen 3
The layout data file 315 is entered by inputting the name of the input / output medium and the layout data of the items specified on 03.
Register with. The screen transition registration unit 105 inputs the transition states of the screens to be input / output for the plurality of screens used in the program, which are designated on the screen transition definition screen 304, and the names given to the screen transitions. Register in the data file 316.

The item transition registration section 106 inputs the transition state of the item designated on the item transition definition screen 305 as an input / output target for the item in the screen and registers it in the item transition data file 317. The item dictionary registration unit 107
The procedure related to the item designated on the item dictionary definition screen 306 is input and registered in the item dictionary data file 318. Then, the program relation generation unit 109 generates relation data between files with respect to the input / output relation data file 314, the layout data file 315, and the screen transition data file 316, using the input / output medium name as a key, and the layout data file. 315, item transition data file 317, and item dictionary data file 31
With respect to No. 8, related data between records in the file is generated using the item name as a key and output to the program related data file 320. The component expanding unit 108 generates a program using the input / output medium associated with the component specified in the input / output relational data file 314 and the associated item data, and outputs the program to the file 322.

As described above, in the software production support system of this example, it is necessary for the program to be automatically generated by the input / output relationship generation unit 103 which generates the input / output relationship between the program and the input / output medium from the flow chart of the program. Data can be automatically extracted, and
Component registration unit 1 that specifies the parameterized procedure for deploying components
02, an item transition registration unit 106 that registers a transition state of an item to be input / output with respect to an item of a screen used in the program, an item dictionary registration unit 107 that registers a procedure related to an item used in the program, and an input / output relationship. A program relation generation unit 109 that generates a relation regarding data, layout data, screen transition data, item transition data, and item dictionary data, and a component development registration unit 108 that develops a component.
By providing, it becomes possible to reduce the addition and correction work for the generated program.

FIG. 4 is an explanatory diagram showing a data flow between the programs relating to the program for issuing the order receiving slip defined on the input / output relationship definition screen in FIG. In this example,
It is a flow chart of the data created on the screen. In this figure, the figure 404 is a program for issuing an order receipt slip, using "slip issuance 10" as a component for generating the program, and the program name is "order receipt slip". Issuance ". Further, a line 414 shows the coupling relationship between the program and the input / output medium used in this program. In the data flow chart, when there is a coupling relationship with the input / output medium located above the program, Indicates "input relationship". A line 415 and a line 418 have a single arrow indicating the coupling relationship between the program and the input / output medium used in this program, and here, "reference relationship".
Indicates. The line 416 has a two-way arrow indicating the coupling relationship between the program and the input / output medium used in this program, and indicates the “update relationship” here. Line 417,
Reference numeral 419 shows a coupling relationship between the program and the input / output medium used in this program. When there is a coupling relationship with the input / output medium located below the program in the data flow chart, “output relationship” is given. Indicates.

A graphic 401 indicates that there are a plurality of input screens for the program, a screen transition definition exists, the name of the screen transition data is "order input screen transition", and the screen name that is the target of the screen transition is Indicates "order header,""orderbody," and "order error." Figure 402
Is the program's reference file name is "person in charge master"
Is shown. A figure 403 indicates that the reference file name of the program is “customer master”. A graphic 405 indicates that the update file name of the program is “product master”. A graphic 406 indicates that the output file name of the program is "order F". Figure 4
07 indicates that the output form name of the program is “delivery slip”. A graphic 408 indicates “sort utility”, and a “order F” of graphic 406 is an input file of the “sort utility” of graphic 408. A graphic 409 indicates that the output file name of the “sort utility” of the graphic 408 is “sorted order F”.

A graphic 412 is a program for outputting a form, and indicates that "table 1" is used as a component for generating the program and the program name is "order date total output". A graphic 409 is an input file of the program of the graphic 412. A figure 410 indicates that the reference file name of the program of the figure 412 is “customer master”. The graphic 411 indicates that the reference file name of the program of the graphic 412 is “product master”.
A graphic 413 indicates that the output form name of the program of the graphic 412 is “order date total table”.

FIG. 5 is an explanatory diagram showing an example of the data structure relating to each input / output medium and the position information of the program in the data flow chart shown in FIG. In the figure, 501 is a type column indicating the type of the program and the input / output medium (type of file, screen, program, etc.), and 502 is an ID indicating the ID for identifying the program and the input / output medium having different display positions. A column, 503 is a coordinate column showing a position for displaying the program and the input / output medium, and 504 is a content column showing a character string displayed on the program and the input / output medium.
Reference numeral 505 denotes a data structure relating to position information of the graphic 401 (“order input screen transition”) in FIG. 4, which includes a type column “1”, an ID column “0”, a coordinate column “(10, 20)”,
Contents column "Order input screen transition, order header, order body,
"Order received error". Similarly, 506 is shown in FIG.
4 is a data structure relating to position information of the graphic 402 (“person in charge”) in FIG.
(“Customer Master”) location information data structure,
508 is a data structure relating to position information of the graphic 404 (program) in FIG. 4, 509 is graphic 4 in FIG.
05 (“product master”) position information data structure 510 represents the position information of the graphic 406 (“order F”) in FIG. 4 and 511 represents the graphic 407 (“delivery slip”) in FIG. A data structure relating to the position information, and 512 is a data structure relating to the position information of the graphic 408 (“sort utility”) in FIG.

FIG. 6 is a "data flow chart" shown in FIG.
It is explanatory drawing which shows the example of the data structure regarding the connection information of the input / output medium and program. In the figure, 601 is a type column indicating the type of line (straight line, line with one arrow, line with bidirectional arrow, etc.), and 602 is a line starting from the ID shown in the ID column 502 in FIG. A start symbol column indicating to draw, 603 an end symbol column to indicate that a line is drawn with the ID shown in the ID column 502 in FIG. 5 as an end point, and 604 is a coordinate column to indicate the vertex coordinates of the line. Reference numeral 605 denotes a data structure relating to the connection information of the line 414 in FIG. 4, which includes a type column “1”, a start symbol column “0”, an end symbol column column “3”, and a coordinate column “(60,
60), (60, 90) ". And so on
606 is a data structure relating to the connection information of the line 418 (“reference relationship”) in FIG. 4, 607 is the line 41 in FIG.
Data structure related to connection information of 5 (“reference relationship”), 6
Reference numeral 08 denotes a data structure relating to connection information of the line 416 (“update relationship”) in FIG. 4, and 609 denotes a line 417 in FIG.
A data structure relating to the connection information ("output relation") and a data structure 610 relating to the connection information of the line 419 ("output relation") in FIG.

FIG. 7 is a flow chart showing an example of the processing procedure of the input / output relation generating section in FIG. In the processing of this example, the input / output relationship generation unit 103 in FIG. 2 inputs the data shown in FIGS. 5 and 6 and generates the data shown in FIG. 8 described later. With respect to the data shown in FIG. 5, the processing of steps 702 to 706 is repeated until the symbols (input / output medium, program, etc.) are completed (steps 701 and 707). That is, first, the contents of the type column 501 of FIG. 5 are determined, and the line whose type is program is extracted (step 702). Next, regarding the data shown in FIG. 6, until the connection record ends (steps 703 and 705),
Rows that have a connection relation between the program extracted in step 702 and the input, reference, update, and output are extracted (step 70).
4).

FIG. 8 is an explanatory diagram showing an example of the structure of the input / output relation data generated by the input / output relation generation unit in FIG. In the figure, reference numeral 801 is a program column showing the name of the program and component name, and 802 is an input / output medium column showing the input / output type and name of the input / output medium and the type of the medium which are connected to the program. Reference numeral 817 is data indicating a program. Reference numeral 803 is the graphic 401 in FIG.
This is data indicating (“order input screen transition”), and the input / output type (“input”), name (“order input screen transition”), and medium type (“1”) are registered. Similarly, 80
4 to 806 are data showing the screen of the "order input screen transition" of the graphic 401 in FIG. 4, 807 is data showing the graphic 402 ("person in charge master") in FIG. 4, 808 is the graphic 403 in FIG. 4), data 809 indicates the figure 405 in FIG. 4 (“product master”), and 810 indicates the figure 406 in FIG.
("Order F"), 811 is data indicating the graphic 407 ("delivery slip") in FIG. 4, and 816 is FIG.
Showing data 412 ("Program / Order date total output") in FIG.
(“Sort order F”), 813 is data indicating the graphic 410 (“customer master”) in FIG. 4,
814 is data indicating the graphic 411 (“product master”) in FIG. 4, and 815 is the graphic 413 in FIG.
(“Order date total table”).

FIG. 9 is an explanatory diagram showing a first specific example of the defining operation on the layout defining screen by the layout registering section in FIG. In this example, the graphic 401 in FIG.
The screen layout of the "order header" of ("order input screen transition") is shown, and 902 is an item of the slip number.
Is a customer code item, 903 is a customer name item, 90
Reference numeral 4 is a person in charge code item, and 905 is a person in charge name item.

FIG. 10 is an explanatory diagram showing a second specific example of the defining operation on the layout defining screen by the layout registering section in FIG. In this example, the graphic 401 in FIG.
Shows the screen layout of the "order body" of ("order input screen transition"), and 1001 is an item of the product code.
002 is a product name item, 1003 is an order quantity item, 1
004 is an item of the order amount.

FIG. 11 is an explanatory diagram showing a first specific example of the defining operation on the screen transition definition screen by the screen transition registration unit in FIG. This example is the content of the layout data defined for the item 902 of the slip number on the “order entry” screen in FIG. 9, and 1101 has the item name “slip number”.
1102 indicates the display position occupied by the item on the screen (7 rows, 60 columns in this example), 1103 indicates the item length (6), 1104 indicates the input / output type of the item, Reference numeral 1105 denotes a distinction between character types such as numbers, characters, and kanji, 1106 denotes a display color (green) when a character is output to an item, and 1107 denotes whether or not the item is a key item.

FIG. 12 is an explanatory diagram showing an example of the definition operation on the item dictionary definition screen by the item dictionary registration unit in FIG. This example is the item dictionary data defined for the item 902 of the slip number on the "order entry" screen in FIG.
1201 indicates that the item name registered in the item dictionary is "slip number", 1202 indicates that the key name of the procedure registered in the item dictionary is "input check", 12
05 is the contents of the "input check" procedure (number and (V
al> 0)), and 1203 indicates that the key name of the procedure registered in the item dictionary is “create” 1206.
Indicates the content of the “generation” procedure (Val = Val + 1), 1204 indicates that the key name of the procedure registered in the item dictionary is “output check”, and 1207 indicates the content of the “output check” procedure (ifInput (Val ) T
hen production (Val)).

FIG. 13 is an explanatory diagram showing a second specific example of the defining operation on the screen transition definition screen by the screen transition registration section in FIG. This example shows the screen transition data defined for the “order input screen transition” of the graphic 401 in FIG. 4, and the screen 1309 initially displays the “order header”.
1301 to 1308 indicate screens and transition conditions to be transited from the currently displayed screen. For example, the transition condition from the “order header” screen to the “order body” screen is to press the key “PF11”. Has become.

FIG. 14 is an explanatory diagram showing an example of the definition operation on the item transition definition screen by the item transition registration unit in FIG. This example shows the item transition data defined for the customer code item 901 and the customer name item 903 of the “order entry” screen in FIG. 9, and 1403 indicates that the initial input item is “customer code”. Shown, 1401-140
Reference numeral 2 indicates an item and a transition condition for transitioning the input target item from the current input target item. For example, the transition condition from the "customer code" to the "customer name" is the key "->" or "Ta".
Pressing "b" and inputting "OK".

FIG. 15 is a flow chart showing an example of the operation procedure of the program relation generation unit in FIG. First,
The cases for which the association is to be generated are classified (step 1)
501). When the data is the input / output relation data, the relation is generated by the program name and the input / output medium name (step 1502), and when the data is the layout data, the relation is generated by the input / output medium name and the item name ( Step 15
03), if the data is screen transition data, an association is generated with the input / output medium name (step 1504), and if the data is item transition data, an association is generated with the input / output medium name and the item name ( (Step 1505) In addition, if the data is an item dictionary, a relation is generated by the item name (step 1506).

FIG. 16 is an explanatory diagram showing an example of the data structure of the program-related data file in FIG.
Layout data 1601 and item dictionary data 1605
Has a one-to-one relationship 1609 between the item name in the layout data 1601 and the item name in the item dictionary data 1605. The layout data 1601 and the input / output relationship data 1602 have a many-to-one relationship 1606 with respect to the input / output medium name targeted by the layout data 1601 and the input / output medium name in the input / output relationship data 1602. Input / output relation data 1602 and screen transition data 160
3 has a one-to-one relationship 1607 with respect to the input / output medium name in the input / output relation data 1602 and the input / output medium name in the screen transition data 1603. Screen transition data 16
03 and item transition data 1604 are screen transition data 16
There is a one-to-many relationship between the input / output medium name in 03 and the input / output medium name in the item transition data 1604. Then, item dictionary data 1605 and item transition data 1604
Has a one-to-one relationship between the item name in the item dictionary data 1605 and the item name in the item transition data 1604.

17 to 20 are explanatory views showing first to fourth specific examples of the component data defined on the component definition screen by the component registration unit in FIG. The part consists of a procedure for extracting related information and a procedure for expanding the part. In FIG. 17, from component character string 1701 to component character string 17
18 is the beginning of the part. Parts character string 1701
Indicates that this part is for the main program,
In the component character string 1702, the parameters used in component expansion are "IO_REL", "IO_OBJ", and "SCREEN".
_TR ”,“ ITEM_TR ”, and“ DICT ”. This "IO_REL" is used when searching for the input / output medium name, "IO_OBJ" is used when searching for the item attribute of the input / output medium, and "SCREEN_TR" is
When searching for screen transition information, "ITEM_TR"
“DICT” is used when searching the screen item transition information, and is used when searching the item dictionary information. Information can be easily acquired by using the expansion parameter in combination with the function for searching the related information shown in FIG. The "printf" function is used as the procedure for expanding the component.

The component character string 1703 expands the program name, and the component character string 1704 specifies that only the screen targeted by this component is searched (KeyGet function). A component character string 1705 takes out one-screen information targeted by this component (Get function). Parts character string 1706
Extracts the screen name from one screen information and expands it, and the component character string 1707 changes the currently targeted screen information to the next information. The component character string 1708 specifies that only the input file targeted by this component is searched (KeyG).
(et function) and the component character string 1709 take out one input file information targeted by this component (Get function). The part character string 1710 extracts the input file name, the part character string 1711 expands the input file name, and the part character string 1712 specifies that the item attribute is searched for the currently targeted input file (KeyGet).
function). The component character string 1713 specifies that the primary key is to be searched from the item attribute (KeyGet function), the component character string 1714 extracts one piece of primary key information, and the component character strings 1715 to 1716 are the primary key information. Expand the name. The part character string 1717 changes the currently targeted main key information to the next information, and the part character string 1718 changes the currently targeted input file information to the next information.

In FIG. 18, component character strings 1801 to 1818 are parts relating to screen transitions. The component character string 1801 expands a definition statement indicating the beginning of screen transition expansion, the component character string 1802 extracts one screen information from the screen transition information, and the component character string 1803 extracts a transition source screen from the one screen information. . The component character string 1804 extracts the name from the transition source screen, the component character string 1805 extracts the registration ID from the transition source screen, and the component character string 1806.
Extracts a plurality of transition destination screens from the transition source screen. The component character string 1807 takes out one transition destination screen from a plurality of transition destination screens, the component character string 1808 takes out a name from one transition destination screen, and the component character string 1831 shows one transition destination screen. The registration ID of the transition condition is taken out from, and the component character string 1809 develops one transition destination screen. In the component character string 1810, the current transition destination screen is changed to the next transition destination screen, and the component character strings 1811 to 1817 are displayed.
Expands the remaining transition destination screen and displays the part character string 1818
Changes the currently targeted screen information to the next screen information.

Component character string 1819 to component character string 183
0 is a part related to the screen transition condition. Parts character string 1
Reference numeral 820 expands a definition statement indicating the beginning of the screen transition condition, and the component character string 1821 extracts one screen information from the screen transition information. The component character string 1822 extracts the transition source screen from one screen information, the component character string 1823 retrieves the name from the transition source screen, the component character string 1824 retrieves a plurality of transition destination screens from the transition source screen, and the component character Row 1
825 retrieves one transition destination screen from the plurality of transition destination screens, the component character string 1826 retrieves the registration ID of the transition condition from the transition destination screen, and the component character string 1827 retrieves the transition condition from the transition destination screen. . Parts character string 1828
Expands the transition condition, the component character string 1829 changes the current target transition destination screen to the next transition destination screen, and the component character string 1830 changes the current target screen information to the next screen information. Change.

In FIG. 19, a part character string 1901 to a part character string 1929 are parts relating to item transition.
The component character string 1901 extracts one screen information from the screen information, the component character string 1902 extracts a screen name from the one screen information, and the component character string 1903 expands a definition statement indicating the beginning of the processing procedure related to the one screen information. To do. The component character string 1904 extracts item information related to one screen information, the component character string 1905 extracts a plurality of item attribute information from the item information, and the component character string 1906 expands a definition statement indicating the start of item transition. . Parts character string 1907
Extracts a plurality of item transition information related to the current screen, and the component character string 1908 is 1 from the plurality of item transition information.
Item transition information is extracted, and the component character string 1909 is
Information of the item transition source is extracted from one item transition information.
The component character string 1910 retrieves the name from the item transition source information, the component character string 1911 retrieves the information of a plurality of item transition destinations transitioning from the item 1909, and the component character string 1912 retrieves a plurality of item transition destinations. The information of one item transition destination is extracted from the information, and the component character string 1913 extracts the name from the information of one item transition destination. Parts character string 19
14 expands one item transition, and a part character string 1915
Changes the currently targeted item transition destination information to the next item transition destination information.

From component character string 1916 to component character string 192
0 is a development part regarding the next item transition destination information. The part character string 1921 expands a line feed code. The component character string 1922 changes the currently targeted item transition information to the next item transition information. The component character string 1923 positions the currently targeted item transition information at the top item transition information. The part character string 1925 is 1 from a plurality of item transition information.
Item transition information is extracted, and the component character string 1926 is
Information on a plurality of item transition destinations is extracted from one item transition information, and a component character string 1927 is extracted from one item transition destination information from a plurality of item transition destination information.
8 develops one item transition condition. Parts character string 19
29 changes one item transition destination information which is the current target to the next item transition destination information.

In FIG. 20, the part character string 2001 is
Expand the definition statement that indicates the beginning of the item input check procedure. The component character string 2002 extracts one input item information from a plurality of item information, the component character string 2003 extracts a name from one input item information, and the component character string 200
4 and the part character string 2005 extract the input check procedure related to one input item from the item dictionary and develop the input check procedure. The component character string 2006 changes the item to be expanded to the next item. Parts character string 20
07 positions the access positions of a plurality of item information to the head item information. The component character string 2008 expands a definition statement indicating the beginning of the item generation procedure. Parts character string 20
09 extracts one output item information from a plurality of item information, and the component character string 2010 extracts a name from one output item information, and outputs a component character string 2011 and a component character string 20.
Reference numeral 12 extracts a generation procedure related to one output item from the item dictionary and expands the generation procedure. Parts character string 2
006 changes the item to be expanded to the next item. The component character string 2014 positions the access position of a plurality of item information in the head item information. Parts character string 201
5 develops a definition statement indicating the beginning of the item check procedure. The component character string 2016 extracts one output item information from a plurality of item information, and the component character string 2017 is 1
The name is extracted from the individual output item information, and the part character string 20
18 and the component character string 2019 extract the generation procedure related to one output item from the item dictionary and expand the generation procedure. The component character string 2020 changes the item to be expanded to the next item.

FIG. 21 is a flow chart showing an example of the processing operation of the component developing section in FIG. The processes of steps 2102 to 2105 are repeated until the record of the input / output relational data file 314 in FIG. 3 is completed (steps 2101 and 2106). That is, the information regarding one program is extracted from the input / output relation data, and the component corresponding to the program is read from the component data file 313 of FIG. 3 (step 2102). The program-related data file 320 of FIG. 3 is compared with the program currently targeted for component development, and the program-related data file 320 of FIG. 3 related to the component development parameter shown in the component character string 1702 of FIG. 17 is accessed. The target is determined and the component expansion parameter of the component character string 1702 of FIG. 17 is generated (step 2103). And
The component generation interpreter is called and the component is developed using the generation parameter (step 2104). The generated program is the generated program data file 32 of FIG.
It is output as 2 (step 2106).

22 and 23 are explanatory views showing first and second specific examples of the program data generated by the component expanding section in FIG. This example is an example in which the components shown in FIGS. 17 to 20 are expanded with respect to the “program” of the graphic 404 in FIG. The expanded character string 2201 is shown in FIG.
Is a developed part character string 1703, and expanded character strings 2202 to 2204 are part character strings 1704 to
1707 is expanded. Expanded character string 2206 ~
2210 describes the same expansion procedure as the component character strings 1708 to 1718 of FIG. 17 in the reference file (expanded character string 2205
~ 2208), update file (expanded character strings 2209-2
210), the output file (expanded character string 2211), and the form (expanded character string 2212).
The expansion character string 2213 is for automatically processing the PF key, and the expansion character string 2214 is for the component character strings 1801 to 1 of FIG.
818, the expanded character string 2215 is the component character string 1820.
˜1803, the expanded character string 2301 is the component character string 1903 of FIG. 19, and the expanded character string 2302 is the component character string 1
906 to 1922, the expansion character string 2303 expands the component character strings 1924 to 1929, and the expansion character string 2
304 is a part character string 2001-2006 of FIG.
The expansion character string 2305 is the component character strings 2008 to 2013.
The expanded character string 2306 is the component character strings 2015 to 20.
It is a development of 20.

As described above with reference to FIGS. 1 to 23, in the software production support system of this embodiment,
Since the input / output relation generating unit and the program relation generating unit can automatically extract the relation with the input / output medium related to the program, manual work can be eliminated and the production efficiency at the time of generating the program can be improved. Further, by providing the item transition registration unit in the software production tool, the definition of the item transition can be mechanized and the software process can be automated. Further, by providing the item dictionary registration unit, the procedure regarding the items can be managed in a unified manner, so that duplicate software development can be reduced. Further, by providing the component registration unit and the component development unit, detailed component development can be defined, so that the component generation rate can be increased. The present invention is
The embodiment is not limited to the embodiment described with reference to FIGS. 1 to 23, and various modifications can be made without departing from the spirit of the invention.

[0040]

According to the present invention, in the software development process, the definition of the screen / form / file name and input / output type (input / reference / update / output) related to the program at the time of generating the program, During the development of the screen program, the definition of the transition state of the items in the screen corresponding to the screen input operation, the definition of the procedure to be expanded to the office processing program for the items such as screens, forms, files, etc. It is possible to define the deployment procedure of parts, reduce the software development cost by automating the entire software development process, reduce the development of duplicate software, and improve the quality of software by increasing the program generation rate. It is possible to improve software productivity.

[Brief description of drawings]

FIG. 1 is a block diagram showing a first embodiment of a configuration relating to the present invention of a software production support system of the present invention.

FIG. 2 is a block diagram showing a second embodiment of the configuration related to the present invention of the software production support system of the present invention.

FIG. 3 is an explanatory diagram showing an example of an operation of the software production support system in FIG. 2 according to the present invention.

FIG. 4 is an explanatory diagram showing a data flow between programs related to a program for issuing an order reception slip defined on the input / output relationship definition screen in FIG.

5 is an explanatory diagram showing an example of a data structure relating to position information of each input / output medium and program of the data flow chart shown in FIG. 4;

6 is an explanatory diagram showing an example of a data structure relating to connection information of an input / output medium and a program in the "data flow chart" shown in FIG.

7 is a flowchart showing an example of a processing procedure of an input / output relationship generation unit in FIG.

FIG. 8 is an explanatory diagram showing a structural example of input / output relation data generated by an input / output relation generation unit in FIG.

FIG. 9 is an explanatory diagram showing a first specific example of the defining operation on the layout defining screen by the layout registering unit in FIG.

10 is an explanatory diagram showing a second specific example of the defining operation on the layout defining screen by the layout registering unit in FIG.

FIG. 11 is an explanatory diagram showing a first specific example of the defining operation on the screen transition definition screen by the screen transition registration unit in FIG.

12 is an explanatory diagram showing an example of a defining operation on an item dictionary definition screen by the item dictionary registration unit in FIG.

FIG. 13 is an explanatory diagram showing a second specific example of the definition operation on the screen transition definition screen by the screen transition registration unit in FIG.

14 is an explanatory diagram showing an example of a defining operation on an item transition definition screen by an item transition registration unit in FIG.

15 is a flowchart showing an example of an operation procedure of a program relation generation unit in FIG.

16 is an explanatory diagram showing an example of a data structure of a program-related data file in FIG.

17 is an explanatory diagram showing a first specific example of component data defined on the component definition screen by the component registration unit in FIG. 2. FIG.

18 is an explanatory diagram showing a second specific example of the component data defined on the component definition screen by the component registration unit in FIG. 2. FIG.

19 is an explanatory diagram showing a third specific example of the component data defined on the component definition screen by the component registration unit in FIG. 2. FIG.

20 is an explanatory diagram showing a fourth specific example of the component data defined on the component definition screen by the component registration unit in FIG. 2. FIG.

21 is a flowchart showing an example of a processing operation of a component developing unit in FIG.

22 is an explanatory diagram showing a first specific example of program data generated by the component expanding unit in FIG. 2. FIG.

FIG. 23 is an explanatory diagram showing a second specific example of program data generated by the component expansion unit in FIG.

[Explanation of symbols]

101 display device 102 component registration unit 103 input / output relationship generation unit 104 layout registration unit 105 screen transition registration unit 106 item transition registration unit 107 item dictionary registration unit 108 component expansion unit 109 program relation generation unit 110 storage device 301 component definition screen 302 input Output relationship definition screen 303 Layout definition screen 304 Screen transition definition screen 305 Item transition definition screen 306 Item dictionary definition screen 313 Parts data file 314 Input / output relation data file 315 Layout data file 316 Screen transition data file 317 Item transition data file 318 Item dictionary Data file 320 Program-related data file 322 Generated program file 401-413 Graphic 414-419 Line 501 Type column 502 ID column 503 Coordinate column 5 04 content column 505-512 data structure 601 type column 602 start symbol column 603 end symbol column 604 coordinate column 605-610 data structure 801 program column 802 input / output medium column 803-817 data 901 customer code item 902 slip number item 903 Customer name item 904 Person code item 905 Person name item 1001 Product code item 1002 Product name item 1003 Order quantity item 1004 Order amount item 1101 to 1107 Layout data 1201 to 1207 Item dictionary data 1301 ˜1309 Screen transition data 1401-1403 Item transition data 1601 Layout data 1602 Input / output relation data 1603 Screen transition data 1604 Item transition data 1605 Item dictionary data 1606 610 related 1701～1718,1801～1830,1901～
1929, 2001-2020 Parts character string 2201-2215, 2301-2306 Expanded character string

Claims (5)

[Claims] 1. At least focusing on the flow of data,
A data flow diagram that describes business process specifications of a business system to be designed, a system flow design diagram that breaks down from the data flow diagram, and describes a computer process flow of each business in the data flow diagram and the above A screen transition diagram that describes the flow and operation of each screen of each business, and a screen form diagram that is broken down from the screen transition diagram and that describes the form specifications of the screen in the screen transition diagram are displayed on the display. In the software production support system that develops reusable program parts registered in advance corresponding to each figure and generates a program related to the business system, on the system flow design diagram described above. Data flow between the computer process defined and input / output media such as files accessed by the computer process Based on the input / output of the computer process to the input / output medium, an access relation such as reference is generated based on the input / output medium, and an input / output relation generating means for registering in association with the related computer process and the input / output medium is provided. A production support system for software, characterized in that the program parts corresponding to the computer processing are expanded using the access relationship of the computer processing to the input / output medium generated by the output relationship generating means. 2. Focusing on the flow of data, at least
A data flow diagram that describes business process specifications of a business system to be designed, a system flow design diagram that breaks down from the data flow diagram, and describes a computer process flow of each business in the data flow diagram and the above A screen transition diagram that describes the flow and operation of each screen of each business, and a screen form diagram that is broken down from the screen transition diagram and that describes the form specifications of the screen in the screen transition diagram are displayed on the display. In the software production support system that develops reusable program parts registered in advance corresponding to each figure and generates a program related to the business system at the time of generating the screen form diagram described above. An item transition definition means for displaying the item transition condition table and registering the transition condition between items input via the item transition condition table is provided. , Using a transition condition between items registered in said item transition definition means, software production support system which comprises carrying out the deployment of the program components of transitions between said item. 3. Focusing on the flow of data, at least
A data flow diagram that describes business process specifications of a business system to be designed, a system flow design diagram that breaks down from the data flow diagram, and describes a computer process flow of each business in the data flow diagram and the above A screen transition diagram that describes the flow and operation of each screen of each business, and a screen form diagram that is broken down from the screen transition diagram and that describes the form specifications of the screen in the screen transition diagram are displayed on the display. In the software production support system that develops reusable program parts registered in advance corresponding to each figure and generates a program related to the business system at the time of generating the screen form diagram described above. Displaying the item procedure definition table and inputting at least the item input definition procedure through the item procedure definition table, An item dictionary defining means for registering a procedure for generating eye data from a single item or a plurality of other items and a procedure for an item including an item output check procedure is provided, and the procedure for the item registered by the item dictionary defining means is used. And a software production support system for developing the program parts using the items. 4. At least focusing on the flow of data,
A data flow diagram that describes business process specifications of a business system to be designed, a system flow design diagram that breaks down from the data flow diagram, and describes a computer process flow of each business in the data flow diagram and the above A screen transition diagram that describes the flow and operation of each screen of each business, and a screen form diagram that is broken down from the screen transition diagram and that describes the form specifications of the screen in the screen transition diagram are displayed on the display. In the software production support system that develops reusable program parts registered in advance corresponding to each figure and generates a program related to the business system, the part expansion definition on the display. The screen is displayed, and the program is stored in the reusable program part input through the part expansion definition screen. A software production support characterized by providing a parts registration means for registering a parts development procedure, and expanding the parameter part of the program parts by using the parts development procedure of the program parts registered by the parts registration means. system. 5. At least focusing on the flow of data,
A data flow diagram that describes business process specifications of a business system to be designed, a system flow design diagram that breaks down from the data flow diagram, and describes a computer process flow of each business in the data flow diagram and the above A screen transition diagram that describes the flow and operation of each screen of each business, and a screen form diagram that is broken down from the screen transition diagram and that describes the form specifications of the screen in the screen transition diagram are displayed on the display. The input / output relation of claim 1 in a software production support system which describes the reusable program parts registered in advance corresponding to each figure and generates a program related to the business system. Generating means, item transition defining means of claim 2,
A production support system for software, characterized in that the item dictionary defining means according to claim 3 and the parts registering means according to claim 4 are provided in an arbitrary combination, and information from each is associated to develop the program parts. .