JPH10307715A - Developing tool - Google Patents

Abstract

PROBLEM TO BE SOLVED: To decrease a development man-hour and to facilitate correction by the ruling of operation procedures and the integration of development information by defining function information, screen items by functions, and processes by the function, generating a source according to the definitions, and automatically generating the source according to corrections of the respective definitions. SOLUTION: A subsystem is registered (C1). The function information constituting the registered subsystem is defined (c2). A grand menu is generated (c3). Information on the screen items by the functions is inputted (c4). The screen items by the functions are defined (c5). Then FORMs by the function are defined (c6). Core processes by the functions are generated (c7). The core processes by the functions are generated (c8). Thus, the definition of the function information, the generation of the grand menu, the definition of the screen items by the functions, the generation of the forms by the functions, and the definition of the core process by the functions are performed and the source is automatically generated according to the definitions. Consequently, the source can automatically be generated according to corrections of the respective definitions.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a development tool for developing a program for a business processing system.

[0002]

2. Description of the Related Art Conventionally, when developing a system for inputting data from a screen and performing search and registration, etc., a screen is designed and a screen definition body is manually created. It was designed such that a program for performing a business process by using the above was manually coded and both were integrated to develop a desired system.

[0003]

For this reason, when modifying a part of a screen or a part of a business process, it is necessary to modify a screen definition body, modify a coding of a program, or use a very troublesome and specialized knowledge. There was a problem that it was required and required many man-hours.

[0004]

In order to solve these problems, the present invention defines function information, function-specific screen items, and function-specific processing and automatically generates a source according to these definitions. The purpose is to enable automatic re-generation of the source according to the definition modification, to reduce the number of development man-hours and to facilitate the modification by making the work procedure into a tool and integrating development information.

[0005]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A means for solving the problem will be described with reference to FIG. In FIG. 1, C1 registers a subsystem. In this method, a subsystem name having functions such as data inquiry and registration is registered in the DB from the screen.

[0006] C2 defines the function information that constitutes the subsystem registered in C1. This registers definition information (function name, screen definition body, file name, etc.) of each function in the DB.

The C3 creates a grand menu.
This creates a screen (ground menu) for selecting the function defined in C2. C4 captures screen item information for each function. This is the data type of information defined on the screen designed by the designer by referring to the screen definition (form) for each function registered in C2,
Register item names in the DB.

C5 defines a screen item for each function. This is for each item in the screen definition registered in C4
Change or add definition information such as data type and item name,
Register in DB.

C6 creates a function-specific FORM. This reflects the information specified in the definition of the function-specific screen items,
Create a form. C7 defines a core process for each function. This is a processing program (core process) for the function specified by the button window on the screen, etc.
Is defined.

C8 creates a core process for each function. This creates a source based on the information defined from C1 to C7. Also, in the case where one function is selected from a plurality of selection functions generally used in a business system and one function is realized by designating an input item and a selection item for the selected function, it is common. Regardless of the combination of the processing, there are differences in the target data and attributes, so the programs had to be coded separately. For example, when one function is selected from a plurality of function selection items, in the object-oriented programming, a data attribute and a processing procedure when selected are set for each selection button in which each function name is arranged. However, the processing procedure at the time of function selection is different only in the function name and the transition destination, and in many cases the programs can be made common. Therefore,
It is desired that the program source is automatically generated by setting only different parts.

Therefore, it is necessary to define function information, create a grand menu, define function-specific screen items, create function-specific forms, and define function-specific core processes for actual processing, and automatically generate sources according to these definitions. As a result, the source can be automatically regenerated according to the modification of each definition, the work procedure can be made into a tool and the development information can be integrated to reduce the development man-hour and facilitate the modification.

Next, the detailed description of FIG. 1 will be given with reference to FIGS. 2 to 11. FIG. 2 is a detailed explanatory diagram (1) of the present invention. This is a detailed explanatory diagram of registration of the subsystem of C1 in FIG.

In FIG. 2A, the subsystem ID and name are determined in C1-1, and set in the subsystem definition table in C1-2. The subsystem definition table is a table as shown in FIG. 10A, and is a "subsystem ID" that is a unique identifier for each subsystem.
Is composed of a “subsystem name” output as a subsystem name on each definition information setting screen.

In this example, as described with reference to FIG. 1, a source program that realizes a subsystem by simply defining a function name for each subsystem, a screen definition body name for each function, data to be processed, a check type, and the like. Is automatically generated.

For example, by displaying the screen as shown in FIG. 11A, "subsystem", "processing",
Select "Function" and display the screen to enter the corresponding definition information. The subsystem name described with reference to FIG. 2 is registered in the subsystem definition table, and is displayed as a “subsystem” selection candidate on the screen shown in FIG.

Next, "processing" designates which definition information is defined. In this example, in order to set the definition information as shown in FIG. 1, each procedure and name of C1-C8 are set. If registered in advance, it will be displayed as a selection candidate for “processing”.

Next, "function" designates a function name when setting information for each function when a plurality of functions such as data inquiry and update are included in one subsystem. is there. A function name is registered in a function information definition table to be described later, and is displayed as a selection candidate of “function selection” on the screen shown in FIG.

FIG. 3 is a detailed explanatory view of the present invention (part 2).
Is shown. This is a detailed explanatory diagram of the definition of the function information of C2 in FIG. In FIG. 3, an initial screen for selecting the processing content as shown in FIG.
When the function definition is designated, the in-subsystem function definition screen is displayed in C2-2, and the function information in the subsystem is input in C2-3 and set in the function information definition table. The function information definition table is a table as shown in FIG. 10B, and specifies each function in the specified subsystem. In this example, a subsystem that collects functions related to “customer” is taken as an example, and an example in which “guest history inquiry” is set as the function name to be configured will be described. As a definition information of each function, a “display FORM name” for storing a screen definition body for inputting a “V / L” inquiry item in addition to the function name is set in this table. FIG. 4 shows a detailed explanatory diagram (part 3) of the present invention. This is a detailed explanatory diagram of the creation of the grand menu of C3 in FIG.

In FIG. 4, the process selection initial screen of FIG. 11A is displayed at C3-1, and when the creation of the grand menu is designated, the grand menu creation screen is displayed at C3-2. The grand menu is a list screen of functions constituting the subsystem. Since this processing is for displaying a list of different function names for each subsystem, a template screen definition body having a plurality of selection item fields as shown in FIG. 11B is set in advance. , The designated function name is set as the name of the selection item field.

Since the information is registered in the function information definition table in the function information definition process of C2, the registered function name is referred to from the function information definition table in C3-3. In this example, in the function information definition process, "guest history inquiry" is set as the function of the "customer" subsystem, so a screen definition body of the grand menu as shown in FIG. 11B is created. In addition, the processing program that displays the grand menu and the processing program that executes the corresponding function when the function item in the grand menu is selected are common processing for all subsystems.
A template program is set in advance. Also, since the screen definition body name for the selected function is registered as the display FORM name in the function information definition table, when a function is specified in the template program, it is embedded in the screen transition body name to which the next transition is made. Just need. In C3-4, by referring to the function information definition table as described above and embedding the necessary items as a template in the screen definition body and processing program, the grand menu (function list) for the specified subsystem is displayed. Screen).

FIG. 5 is a detailed explanatory view (4) of the present invention. This is a detailed explanatory diagram of taking in the function-specific screen item information of C4 in FIG. In FIG. 5, C4-1 is
FORM for each function (for example, here for the guest history inquiry)
Design and create (only screen design). Here, a screen definition body for displaying a screen for each function is designed, and information of each item constituting the screen is registered. Therefore, it is possible to set the data names of the items used in the source of the control program for processing the items input from the screen only by the screen design for designating the processing.

According to a certain rule, the screen definition body is "LA (label)" such as an input item name, "TX (text)" such as a text input item, and "LB (list box)" such as a selection item group. ) "And other data for setting the data contents together with the tag data.

Next, in C4-2, the name of the subsystem to be processed and the name of the screen definition body are referred to the subsystem definition table and the function information definition table, and the corresponding screen definition body is analyzed. Since data is set in the screen definition body in accordance with the rules described above, the tag data is read and the item type and the item name constituting the screen are C4-3 and the function shown in (c) of FIG. Register in another screen item definition table.

FIG. 6 is a detailed explanatory view (5) of the present invention. This is a detailed explanatory diagram of the definition of the screen item for each function of C5 in FIG. In FIG. 6, the initial screen for selecting the processing content is displayed in C5-1, and when the function-specific screen item definition is selected, the function-specific screen information definition screen is displayed in C5-2. This captures the contents of the function-specific screen item definition table of FIG. 10C and displays it as shown below on the function-specific screen information definition screen of FIG. 12C.

-FORM name: CMSHIST0-Item type: TX-Item name: NAMEK-Check type: -Input enable / disable: In C5-3, if necessary, additionally input information for each item. For example, if it is an input item, the check type of the input data is added. In addition to the check type, control specification of a function key valid on a specification screen (not shown) is added.

At C5-4, function-specific screen information is registered. In this case, data added as described below in the function-specific screen item definition table 13 of FIG. 10F is also registered.

• FORM name: CMSHIST0 • Item type: TX • Item name: NAMEK • Check type: Customer name Kana • Input availability: Allowable FIG. This is a detailed explanatory diagram of the creation of the function-specific FORM of C6 in FIG.

In FIG. 7A, an initial screen for selecting a process is displayed in C6-1, and when a function-specific FORM creation is instructed, in C6-2, each item set in C5 is added. Check the function information definition table for definition information such as check type and effective function key control, etc., and display FO corresponding to the function of the specified subsystem.
It is reflected on the RM according to the function-specific screen definition table.

By the above, a functional FORM as shown in FIG. 12D is created. FIG. 8 is a detailed explanatory view (No. 7) of the present invention. This is C in FIG.
7 is a detailed explanatory diagram of definition of a core process for each function, which is a processing procedure for each screen of FIG.

In FIG. 8A, an initial screen for selecting a process is displayed at C7-1, and when the definition of the core process for each function is specified, the process is shown at C7-2 in FIG. 12D. Display such a core process definition screen. By referring to the subsystem definition table and function information, the processing procedure (process) registration screen for the corresponding screen definition is displayed.

C7-3 inputs actual processing for each function. In this case, an actual process for each function is input based on the OP information table 15 of FIG. 10D and the SUBOP information table 16 of FIG. 10E. The OP information and SUBOP information tables define candidates for processing procedures that can be registered.

FIG. 10D shows an example of the OP information table. Here, as shown, two processing procedures are registered as selection candidates. -OP name: ENTER processing Individual check processing FIG. 10E shows an example of the SUBOP information table.
The SUBOP information table defines selection candidates for subordinate processing procedures used in the processing procedures registered in the OP information.

OP name: Judgment True False Judgment end In C7-3, when an input is instructed on the core process definition screen as shown in FIG.
The P information table and the (e) SUBOP information table of FIG. 10 are referred to, and a selection candidate of a process that can be input is displayed. Therefore, a corresponding process is selected.

The procedure of the processing selected in C7-4 is shown in FIG.
0 is output to the core process definition table as shown in (f). Although not shown, the processes registered as OP information and SUBOP information are managed in correspondence with the source code. The corresponding source code is only a template, and data such as the item name to be processed is embedded according to the settings of the already-defined function-specific screen item definition table. For example, in this example, since the item name “NAME” is set as the item type “TX (text)”, the check type “customer name kana”, and the input permission / prohibition “OK”, individual check processing is performed as processing in the core process definition table. When selected, the source code to check "Yes" as the input availability check process in the source code preset as individual check process, "Text" as the item type check process, and "Customer name kana" as the detailed check type The data is embedded in the determination part inside.

As described above, the core process definition table 17 shown in FIG. FIG.
Shows a detailed explanatory view (No. 8) of the present invention. This is a detailed explanatory diagram of creation of a function-specific core process of C8 in FIG.

In FIG. 9A, an initial screen for selecting a process is displayed in C8-1, and when the function-specific core process creation is selected, a core process is created based on the definition information in C8-2. (A process to be actually performed by the function-specific FORM is created). This creates a source program based on the core process definition table 17 of FIG.

[0037]

As described above, according to the present invention,
Since the function information is defined, the screen items for each function are defined, and the processing for each function is defined and the source is automatically generated according to this definition, the source can be automatically regenerated according to each definition modification. Tooling of the procedure and integration of development information can be achieved to reduce development man-hours and facilitate modification.

[Brief description of the drawings]

FIG. 1 is a flowchart for explaining the operation of the present invention.

FIG. 2 is a detailed explanatory diagram (part 1) of the present invention.

FIG. 3 is a detailed explanatory diagram (part 2) of the present invention.

FIG. 4 is a detailed explanatory diagram (part 3) of the present invention.

FIG. 5 is a detailed explanatory diagram (4) of the present invention.

FIG. 6 is a detailed explanatory diagram (5) of the present invention.

FIG. 7 is a detailed explanatory diagram (part 6) of the present invention.

FIG. 8 is a detailed explanatory view (No. 7) of the present invention.

FIG. 9 is a detailed explanatory view (No. 8) of the present invention.

FIG. 10 is an explanatory diagram of a definition table of the present invention.

FIG. 11 is a screen example (continued) of the present invention.

FIG. 12 is a screen example (continuation) of the present invention.

[Explanation of symbols]

 11: Subsystem definition table 12: Function information definition table 13: Function-specific screen item definition table 14: Check ID definition table 15: OP information table 16: SUBOP information table 17: Core process definition table

Claims (2)

[Claims] 1. A development tool for developing a program for executing a business processing system, comprising: means for registering a function of the business processing system; means for creating a screen definition body and a processing program for selecting the registered function; A development tool comprising: means for defining an item on another screen and processing contents for the item; and means for creating a screen definition body and a processing program for this function-specific screen. 2. A means for registering a function of a business processing system, a means for creating a screen definition body and a processing program for selecting the registered function, and an item on a function-specific screen and processing contents for the item. Means and a medium for recording a program for functioning as a means for creating a screen definition body of this function-specific screen and a processing program.