JPS6289133A - Program development supporting system - Google Patents

Abstract

PURPOSE:To improve the productivity at the time of preparing the data base access program by generating the data base access processing by the individual applied program in a lump and replacing the data access processing from the applied program to the centralizingly controlled common access module. CONSTITUTION:After the data base design is completed, a data base schema definition 3 is prepared by using the data base definition function. Thereafter, as the preparing work, the logical record to satisfy the processing request from an applied program 4 is designed, and by using a logical record definition means 10, the logical record definition is registered to a logical record definition library 11. Next, by using an access module generating means 20, the access module forming the logical record is generated. In accordance with the necessity, by using a customized means 30, the access module is changed. After the preparing work is completed, the logical record defined by the logical record definition means 10 is prepared, and by using the data base operating instruction which is an object, the applied program 4 is prepared.

Description

DETAILED DESCRIPTION OF THE INVENTION (Field of Industrial Application) The present invention relates to improving productivity in the development and maintenance of application programs that handle network-type databases.

(Prior Art) In network databases, the information structure of the real world is statically expressed as a data structure, as typified by the C0DASYL proposal. In the data structure definition, auxiliary structures were added in consideration of access efficiency from application programs, and redundant information was expressed. Therefore, application programs that operate network databases require knowledge of how real-world information is embedded in data structures and what auxiliary structures are defined.

Database management systems that support network databases use operation instructions that can describe where and how to enter a data structure, which structure to follow, and what to do with which records in order to operate such databases. provided and released to application programs.

Furthermore, since this operation command requires processing to trace the data structure, it is an important task for the application program to be aware of where in the data structure it is currently processing. Therefore, as database data processing demands become more sophisticated, it becomes difficult to access various records while being aware of their relationships with other records, and the logic for using the above operating instructions in application programs and programs becomes complex. .

(Problems to be Solved by the Invention) In the above-mentioned conventional technology, in the database operation commands that are released to application programs, the database structure such as the access route, record name, set name, etc. to obtain the target data from the database is Element names are written directly in the application program. For this reason, logic for extracting necessary data from the database must be created for each application program, which has the disadvantage of increasing the burden on each program creator.

In addition, since the same type of processing with only some differences is written redundantly in different programs, the scope of program modification due to database design changes is spread out, and the contents of modification become diversified, resulting in slow program development. This has the disadvantage of reducing maintenance productivity.

It is an object of the present invention to solve the above-mentioned drawbacks by collectively generating database access processes that have been developed separately in individual application programs and replacing the data pace system from the application programs with a centrally managed common access module. The purpose of the present invention is to provide a program development support system that is structured so as to eliminate the burden on program creators during program creation, and to avoid reducing the productivity of program development and maintenance.

(Means for Solving the Problems) The program development support system according to the present invention is a database that is provided with access means for each record in order to operate data stored and managed in a network type database from an application program. used in the system, comprising: a logical record definition means;
an access module generation means, a customization means,
The program is composed of a program synthesis means.

The logical record definition means is for defining a database portion consisting of a plurality of records necessary for processing an application program as one logical record.

The access module generation means refers to a normal database schema definition and the definition created by the logical record definition means, and searches and updates the logical record given by each of the above definitions. It is used to generate a data dictionary that maintains associations between database elements and access modules.

The customizing means is for partially modifying the access module and data dictionary generated by the access module generating means and performing additional registration or re-registration.

The program synthesis means interprets a search/update request statement for a defined logical record written in the application program, and adds the access module created by the access module generation means or the customization means to this search/update request statement. It is intended to be replaced and incorporated into an application program.

(Example) Next, the present invention will be explained in detail with reference to the drawings.

FIG. 1 is a functional block diagram showing an embodiment of a program development support system according to the present invention.

In FIG. 1, one embodiment of the present invention includes a logical record definition means 10, a database schema definition 3 found in a typical database management system, and a logical record storing a logical record definition created by the logical record definition means 10. A definition library 11, a data dictionary 22, an access module generation means 20, an access module library 21 that stores access modules generated by the access module generation means 20, a customization means 30, and a database used in this embodiment. An application program 4 created using the operation command, a program synthesis means 40, a post-synthesis application program 41 in which the access module has been incorporated by the program synthesis means 40, and a CRT display 1.
and input means 2.

Once the user who develops an application program that accesses a database using the program development support system of the present invention has completed the database design, the user can define the database schema using the database definition function provided by a normal database management system. Create 3. Thereafter, as a preparatory work before starting the application program development work, a logical record that satisfies the processing request from the application program 4 is designed, and the logical record definition is converted into the logical record definition library 1 using the logical record definition means 10.
Register to 1. After that, access module generation means 2
0 is used to generate an access module for forming a logical record.

Further, the access module is changed using the customizing means 30 as necessary. After such preparatory work is completed, a logical record defined by the logical record definition means 10 is created, and an application program 4 is created using the target database operation command.

This application program is synthesized by the program synthesis means 40 into a form that can be input to a normal compiler, and then converted into an application program.

Hereinafter, the program development support system according to the present invention will be sequentially explained in accordance with the development procedure of a database access application program, divided into the steps of logical record definition, access module generation, access module customization, and program synthesis.

First, the definition of a logical record will be explained.

FIG. 2 is a flowchart showing the operation of logical record definition processing by the logical record definition means 10.

The logical record definition means 10 receives a logical record definition request from the input means 2 in step 201. Step 202
Now, the access path information described in the logical record definition request input in step 201 is analyzed. At this time, database schema definition 3 is also referred to, and the validity of the access bus information is confirmed, and if correct. for,
A logical record definition object is generated. In step 203, the logical record definition object generated in step 202 is registered in the logical record definition library 11. At the end of logical record definition, the data dictionary is updated to record the association of logical records with database elements.

FIG. 8 is an explanatory diagram showing a specific example of logical record definition using the logical record definition means 10, in which a logical record definition instruction is inputted from the input means 2.

301, a logical record R1303 and a logical record R2504 are defined on the database schema definition 3 having the data structure shown by the database schema definition diagram 302. Logical record R130 in logical record definition instruction 301! Referring to the description for , a logical record name is given in step 3011, and in step 3012 it is defined that the entry point in the database when configuring logical record R1303 is an A record, and that the A1 field is to be drawn from that record. are doing. Step 3G1! , 3014.15
015, respectively, B1.015 in the logical record R1505. B2. φ---Fl, F2, F! The access path for field 'hrincludebft' is defined.

As another example of logical record definition, FIG. 4 shows several examples in which logical records are defined from data expressed in a tree structure often seen in ordinary databases. When defining a logical record from a tree structure, there are cases where child record B 402 and child record C 403 are handled separately, such as logical record L1 406, and cases where logical record L
In some cases, the data may be handled in synchronization as in 2406. ball,
It may also be handled like logical record L5 407.

As another example, multiple mutually independent data structures,
FIG. 5 shows an example in which the common middle items contained therein are used to connect them and define them as one logical record. In this example, a shipping record 504 is defined as a logical record from two independent data structures, order data 501 and shipping data 502. Referring to the logical record definition directive 503 for defining this logical record, it is defined as follows in steps 5031, 5055, and 5039. That is, step 5031 defines that order record 5011 is used as an entry point.

In step 5035, in order to combine the ordered item record 5012 and the item record 5021, the item record 5012 and the item record 5021 are combined.
021 is defined to use the item code of the ordered item record as a search key.

In step 6059, the shipping record 5022 is defined.

In the logical record definition means of this embodiment, the procedure for forming a logical record is specified in detail in the logical record definition instruction. Therefore, it becomes possible to express various logical records as seen in the variations of logical record expression in the tree structure shown in FIG.

Second, generation of an access module will be explained.

FIG. 6 is a flowchart showing the operation of access module generation processing by the access module generation means 20. The access module generation means 20 receives an access module generation instruction from the input means 2 in step 601. The received instruction is analyzed in step 602 to identify the logical record to be generated, the type of access module to be generated, and the access module name to be used when registering in the access module library 21.

In step 603, the logical record name is received from the generation request analyzed in step 602, and the logical record definition library 11 is accessed to obtain the definition object of the corresponding logical record. In step 604, an access module is assembled based on the logical record definition object while referring to the database schema definition 3. When the assembly of the access module in step 604 is completed, the generated access module is output to the access module library 21 in step 606, and finally, in step 606, the data dictionary 22 is stored in order to record the relationship between the database element and the access module. Perform the update.

FIG. 7 shows the general format of an access module generation instruction statement that is input to the access module generation means 20.

FIG. 8 shows, as a specific example of the access module generation process, the logical record R130! shown as a specific example of the record definition in FIG. 8 shows a processing flow 802 of an access module that receives an access module generation instruction statement 801 from the input means 2 and outputs it to the access module library 21 as a generation result.

Eighth, customization of the access module will be explained.

FIG. 9 is a flowchart showing the operation of the access module customization process by the customization means 30. The customizing means 30 obtains the name of the access module to be customized from the input means 2 in step 901, accesses the access module library 21 in step 902, and displays the framework of the access module on the CRT display 1. In step 903, the user
The access module is modified while communicating with the customizing means 30 using the display 1 and the input means 2. Once you have been notified of the order to complete the necessary series of corrections,
The customizing means 30 replaces the access module on the access module library 21 with a new access module in step 904, and finally updates the data dictionary to record the update history of the access module and customization information.

The database access module generated by the access module generation means 20, as shown at 802 in FIG. 8, consists of a series of basic commands for database records to form the logical record. The customizing means 30 inputs the access module generated by the access module generating means 20, and as a specific example,
In the past, a user-specific process inputted from the input means 2 into a predetermined part of the access module, as shown by a blue sky is added to change the access module and output to the access module library IJ21.

Fourth, synthesis of application programs will be explained.

FIG. 10 is a flowchart showing the operation of program synthesis processing by the program synthesis means 40. The program synthesis means 40 determines from the application program source read in step 1001 whether or not the instruction is a database operation instruction for performing logical record processing in step 1002. If it is a database operation instruction, the instruction is The content of the request is analyzed, and the access module corresponding to the database operation for the specified logical record is read from the access module library 21 and output as part of the application program source. Then step 1
004, the data dictionary 22 is used to record the mutual reference relationship between the access module and the application program.
Perform 0 update. After the processes from steps 1001 to 1004 described above are performed until the end of the application program source, the program synthesis process is completed.

In this embodiment, the concept of a logical record is introduced to database access from an application program, and new database operation instructions as shown in FIG. 11 are provided to the application program so that the database access processing can be assembled for this logical record. are doing. The program synthesis means 40 provides a function of interpreting the new database operation command embedded in the application program, extracting the corresponding access module from the access module library 21, and developing it as an application program north.

FIG. 12 shows a specific example of an application program written using database operation instructions targeting logical records.
A specific example of an application program after synthesis generated by the program synthesis means 40 is shown.

(Effects of the Invention) As explained above, the present invention collectively generates database access processing that has been developed separately in each application program, and creates a common access module that centrally manages database access processing from application programs. By replacing it with , it is possible to minimize the impact on programs caused by database changes and the complexity when creating programs, which were previously considered drawbacks, without compromising the functionality and performance features of network-based databases. ,
This has the effect of improving productivity when creating a database access program and also improving maintainability of the program.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing an embodiment of a program development support system according to the present invention. FIG. 2 is a flowchart showing the configuration of the logic and code definition means of FIG. FIG. 8 is an explanatory diagram showing a specific example of logical record definition. FIG. 4 and FIG. 5 are explanatory diagrams each showing another specific example of logical record definition. FIG. 6 is a flowchart showing the configuration of the access module generating means of FIG. 1. FIG. 7 is an explanatory diagram showing the general format of an access module generation instruction statement that is input to the access module generation means. FIG. 8 is a diagram showing a specific example of access module generation. FIG. 9 is a flowchart showing the configuration of the stomizing means of FIG. 1. FIG. 10 is a flowchart showing the configuration of the program synthesis means of FIG. 1. FIG. 11 is an explanatory diagram showing a list of logical record manipulation commands released to application programs by the program development support system according to the present invention. FIG. 12 is an explanatory diagram showing a specific example of program synthesis processing by the program synthesis means. 1... - CRT display 2... Input means 3... Life data base schema definition 4... Application program 10... Logical record definition means 11... Logical record definition library 20... e-access module generation means 21...Access module library 22Φ...Data dictionary 30...Customizing means 40...ΦProgram synthesis means 41...Application programs after synthesis 201-204, 601-606, 901-905゜1
001-10 units 5...and processing steps 301-304
．． 401~407.501~506°801.802.
8020-8025 @Φ・・・Part of Noato wear

Claims (1)

[Claims] A program development support system for a database system that provides a record-by-record access means for manipulating data stored and managed in a network database from an application program. With reference to a logical record definition means for defining a database part consisting of a single logical record as one logical record, a normal database schema definition, and a definition created by the logical record definition means, a database access module for searching and updating logical records, and access module generation means for generating a data dictionary that maintains associations between database elements and access modules; and access generated by the access module generation means. customizing means for partially modifying the module and the data dictionary for additional registration or re-registration; and access module generating means for interpreting a search/update request statement for a defined logical record written in an application program. or program synthesis means for replacing the access module created by the customizing means with the search/update request statement and incorporating it into an application program.