WO2017170045A1

WO2017170045A1 - Program source conversion method, program source conversion apparatus, information processing apparatus, information processing method, and program

Info

Publication number: WO2017170045A1
Application number: PCT/JP2017/011471
Authority: WO
Inventors: 佳範城代
Original assignee: 株式会社日立公共システム
Priority date: 2016-03-30
Filing date: 2017-03-22
Publication date: 2017-10-05
Also published as: CN113986253A; JP6653205B2; CN109074254A; CN109074254B; JP2017182491A

Abstract

A reversing apparatus (R) at a conversion-development side is provided with: a parser unit (r1) that performs syntax analysis of a current program source (P1) before maintenance and generates lists (P1a, P2a) of tokens and syntaxes being used in the current program source (P1); a setting unit (r2) that sets, on the basis of a design standard (10) of a new program source, permission information (11) indicating tokens, syntaxes, and strings that are permitted to be used in the new program source, and prohibition information (12) indicating tokens, syntaxes, and strings that are prohibited from being used in the new program source; and a tool generating unit (r4) that generates a code check tool (20) for determining whether or not the permission information (11) and the prohibition information (12) are being used in the current program source after maintenance.

Description

Program source conversion method, program source conversion device, information processing device, information processing method, and program

The present invention relates to a software development technique that involves system migration from a current system to a new system.

In the system migration from the current system to the new system, for example, there is work of program conversion development. In conversion development, the program language of the current program source used in the current system (eg COBOL (COmmon Business Oriented Language)) is replaced with another program language (eg JAVA (registered trademark)), and the new used in the new system Create a program source.

∙ Maintenance development of the current system may be carried out in the middle of conversion development. Since conversion development of a large-scale system is a long-term operation, maintenance development in the middle of conversion development may be performed several times. When maintenance development is carried out, catch-up work is performed on the new system under development. The catch-up work refers to a work for reflecting the program correction change generated by the maintenance development in the new program source of the new system which has been created once and completed the system test. Although the catch-up work is indispensable, it increases the amount of conversion development work and delays the system migration, so there is a demand to reduce the work man-hours and end it early. However, since the design contents of conversion development are not basically considered in maintenance development, it is difficult to estimate the work man-hours for catch-up work, and it is never easy to reduce the work man-hours.

Patent Document 1 discloses a program verification apparatus that verifies whether or not a verification target program satisfies a specified internal specification using an abstract syntax tree.

JP 2011-215998 A

However, Patent Document 1 neither describes nor suggests the above-mentioned problem relating to catch-up work and its solution. As a result, it is not possible to realize early system transition where program conversion development is performed.

Therefore, the present invention has been made in view of such circumstances, and an object thereof is to realize an early system transition from a current system in which maintenance and development are performed to a new system.

In order to achieve the above object, an information processing apparatus of the present invention provides:
A program source conversion device for converting a first program source into a second program source,
Creating a code check tool that analyzes the first program source and checks for allowed rules;
Converting the first program source into the second program source;
When the first program source is maintenance-developed, the maintenance-developed first program source is checked using the code check tool, and the maintenance-developed first program source is converted to the conversion. Extracting a usage outside the allowed rules to determine a policy to be reflected in the already-finished second program source;
Performing the step of converting the first program source developed and maintained based on the policy into a second program source and merging with the converted second program source;
It is characterized by that.
Other means will be described later.

According to the present invention, it is possible to realize an early system transition from a current system where maintenance development is performed to a new system.

It is a sequence which shows system transfer when not applying this invention. It is a sequence which shows system transfer at the time of applying this invention. It is a flowchart which shows the detailed procedure of the conversion development in a transfer development environment, and the detailed procedure of the maintenance development in the current system maintenance development environment. It is a functional block diagram of a reverse apparatus. It is a functional block diagram of a code check tool. It is a flowchart which shows the present program source determination process (in the case of a syntax) after a maintenance.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

≪Overview≫
[Conventional system migration]
As shown in FIG. 1, the system migration in which conversion development of a program as a comparative example is performed includes, for example, a current system server 1, a current system maintenance PC (Personal Computer) 2, a test server 2t, and a repository server 3 This is realized by exchanging information among the new system maintenance PC 4, test server 4 t, conversion development server 5, test server 5 t, and new system server 6.

The current system server 1 is a server that reads the current program source P1 (current program source before maintenance) and performs processing for the actual operation of the current system. The current system server 1 is in the current system production environment, and is installed at, for example, a customer of a conversion developer.
The current program source P1 is a source code of a program for the current system. The current program source P1 is described in, for example, COBOL, but may be described in another language.
In this specification, the current program source may be referred to as a “first program source” and the current system may be referred to as a “first system” regardless of whether or not maintenance development has been performed.

The current system maintenance PC 2 is a server that modifies the current program source P1 and creates a maintained current program source P2. The maintained current program source P2 is equal to the current program source P1 for which maintenance development has been completed. The maintained current program source P2 is described in the same language as the current program source P1.
The test server 2t is a server that performs an operation check test on the maintained current program source P2.
The current system maintenance PC 2 and the test server 2t are in the current system maintenance development environment, and are installed at, for example, a customer of a conversion developer.
Maintenance development includes unscheduled work such as correcting a bug that causes a failure in the current system, and scheduled work such as changing the specification of a program in accordance with a revision of the law.

The repository server 3 is a resource management server. The repository server 3 stores and manages the current program source P1, the maintained current program source P2, the new program source P3, and the maintained new program source P4.
The new program source P3 is a source code of a program for the new system.
The maintained new program source P4 is equal to the new program source P3 for which the maintenance development has been completed.
The repository server 3 is in a resource management environment and is installed at, for example, a customer. The resource management environment may be the current system maintenance development environment or a new system maintenance development environment described later. In other words, the current system maintenance PC 2 or the new system maintenance PC 4 can be designed to function as the repository server 3.

The new system maintenance PC 4 is a server that modifies the new program source P3 and creates a maintained new program source P4.
The test server 4t is a server that performs an operation check test (system test) of the maintained new program source P4.
The new system maintenance PC 4 and the test server 4t are in a new system maintenance development environment and are installed at, for example, a customer.

The conversion development server 5 is a server that creates a new program source P3 by replacing the program language of the current program source P1 with another program language. The new program source P3 is described in JAVA, for example, but may be described in another language.
The test server 5t is a server that performs a test for confirming the operation of the new program source P3.
The conversion development server 5 and the test server 5t are in a migration development environment, and are installed at, for example, a conversion developer.

The new system server 6 is a server that reads the maintained new program source P4 and performs processing for the actual operation of the new system. The new system server 6 is in a new system production environment and is installed at, for example, a customer.
In this specification, the new program source may be referred to as a “second program source” and the new system may be referred to as a “second system” regardless of whether or not maintenance development has been performed.

The system migration procedure in FIG. 1 is as follows.
First, in step A1, the current system server 1 reads the current program source P1 acquired from the repository server 3 and performs the actual operation.

Next, in step A2, the conversion development server 5 performs conversion development of the current system for the current program source P1 acquired from the repository server 3, and creates a new program source P3. In addition, the test server 5t performs a test for confirming the operation of the new program source P3. The new program source P3 that has been tested by the test server 5t is stored in the new system maintenance PC 4.

Next, in step A3, the current system maintenance PC 2 modifies the current program source P1 acquired from the repository server 3, performs maintenance development, and creates a maintained current program source P2. In addition, the test server 2t performs a test for confirming the operation of the maintained current program source P2. Step A3 is performed one or more times in parallel with step A2 before completion of step A2 (parallel maintenance). The maintained current program source P2 that has been tested by the test server 2t is stored in the repository server 3.

Next, in step A4, the test server 4t performs a system test of the new program source P3. Specifically, the test server 4t confirms the conversion result output as the new program source P3 as a system test. The new program source P3 that has completed the system test in the test server 4t is stored in the repository server 3.

Next, in step A5, the current system server 1 reads the maintained current program source P2 acquired from the repository server 3, and starts the production operation with the maintained content.

Next, in step A6, the conversion development server 5 reads the maintained current program source P2 acquired from the repository server 3 and performs a catch-up operation. Specifically, the conversion development server 5 specifies the difference between the current program source P1 and the maintained current program source P2 as a program change correction amount by the maintenance development in step A3. Moreover, the conversion development server 5 performs conversion development of the current system that has been maintained for the specified program change correction. Also, the conversion development server 5 creates a maintained new program source P4 by reflecting the result of conversion development of the current system that has been maintained in the new program source P3. “Reflecting the result of conversion development of the current system that has been maintained in the new program source P3” means that the first conversion development design in step A2 is made to correspond to parallel maintenance. . In addition, the test server 5t performs a test for confirming the operation of the maintained new program source P4. The maintained new program source P4 that has been tested by the test server 5t is stored in the new system maintenance PC 4.

Next, in step A7, the test server 4t performs a system test of the maintained new program source P4. Specifically, the test server 4t confirms the conversion result output as the maintained new program source P4 as a system test. The maintained new program source P4 that has completed the system test in the test server 4t is stored in the repository server 3.

Next, in step A8, system transition is performed (reference M1). Specifically, in step A5, the production operation with the maintained contents performed by the current system server 1 is terminated, and the new system server 6 acquires the maintained new program acquired from the repository server 3. The source P4 is read, and the production operation is started with the maintained content.
Next, in step A9, the current system server 1 uses the maintained current program source P2 to start the backup operation with the maintained content.

The amount of the catch-up work in step A6 depends on the result of the program change correction of the current program source P1 in the maintenance development in step A3. Conventionally, the design of conversion development is not basically considered in maintenance development (because maintenance developers prioritize the convenience of maintenance development and do not care about conversion development), the current program in maintenance development There are various ways of realizing program change and correction of the source P1. For example, the program may be corrected using a new (COBOL) instruction word that is not targeted for migration design in maintenance development (the “correction” is a correction using a new “instruction word”, and Including the meaning of both, using the new "How to use command words". In this case, the conversion design for conversion development needs to be corrected. The majority of conversions (program language conversions) can be done mechanically using a given conversion tool, but if the conversion development transition design is modified, the conversion tool should be adapted to accommodate this transition design modification. It needs to be corrected. In addition, when performing conversion using the modified conversion tool, it is necessary to test the operation of the modified conversion tool itself in advance. Since these work may be accompanied by catch-up work, it is not easy for the conversion development side to predict the amount of work for the catch-up work, estimate the work man-hour for the catch-up work, and reduce it.
For very complicated conversion procedures, conversion may be performed manually without using a conversion tool from the viewpoint of development cost. It is assumed that maintenance development is corrected in the conversion manual work portion of the current program source P1. In this case, even if there is no correction of the conversion design for conversion development, in the catch-up operation, conversion according to the correction result of maintenance development is performed manually, and a test is performed to determine whether the conversion has been performed correctly.

[System migration of this embodiment]
In view of the above circumstances, in the present embodiment, the procedure shown in FIG. 2 is taken. As shown in FIG. 2, the system migration in which the conversion development of the program is performed in this embodiment is the same as the comparative example shown in FIG. 1, for example, the current system server 1, the current system maintenance PC 2, and the test server 2t. This is realized by exchanging information among the repository server 3, the new system maintenance PC 4, the test server 4t, the conversion development server 5, the test server 5t, and the new system server 6. Hereinafter, the system migration in the present embodiment will be described with a focus on differences from FIG.

At the beginning of step A2, step B1 is performed. In step B1, the conversion development server 5 determines the program syntax (hereinafter, simply referred to as “syntax”) as a premise for conversion development, and then the design standard 10 and code check tool reflecting the syntax. 20 is created.
The design standard 10 is a design standard for the new program source P3, and collectively describes necessary conditions for system migration design (described later).
The code check tool 20 is a tool used for maintenance development coding (described later) on the current system maintenance PC 2. Details of the code check tool 20 will be described later.

Thereafter, step B2 is performed instead of step A3 (FIG. 1). In step B2, the current system maintenance PC 2 performs maintenance and development, and uses the design standard 10 and the code check tool 20 acquired from the conversion development server 5 when creating the maintained current program source P2. Use syntax that assumes development (consideration). The current system maintenance PC 2 operates the code check tool 20 on the created maintained current program source P2 to determine whether or not a syntax deviating from the design standard 10 is used. If there is a syntax deviating from the design standard 10, the current system maintenance PC 2 may create the maintained current program source P <b> 2 so that no syntax deviating from the design standard 10 exists. If a syntax that deviates from the design standard 10 is inevitably required for maintenance development, the current system maintenance PC 2 creates a non-standard list 30 that describes the syntax and the like collectively. The non-standard list 30 can determine a policy for reflecting the maintained current program source P2 in the new program source P3. Details of the non-standard list 30 will be described later.

Thereafter, Step B3 is performed at the end of Step A2. In step B3, if the non-standard list 30 exists, the conversion development server 5 creates the new program source P3 by reflecting the non-standard list 30 acquired from the current system maintenance PC 2.

The catch-up work in step B4 is equivalent to the catch-up work in step A6 (FIG. 1). The conversion development server 5 converts the maintained current program source P2 based on the policy of the non-standard list 30 and merges it with the new program source P3.

Conversion development (step A2) is performed in accordance with the design standard 10. For this reason, the non-standard list 30 is not created if the maintenance-completed current program source P2 is created in a manner consistent with the design standard 10 in maintenance development. As a result, in the catch-up operation (step B4), the part related to the migration design for system migration can be omitted.
Further, even if the maintenance current program source P2 is created in a manner deviating from the design standard 10 and the non-standard list 30 is created in the maintenance development, the system migration corresponding to the syntax of the non-standard list 30 is performed. The transition design can be performed at the stage of step B3, that is, prior to the catch-up work (step B4) (pre-empting the catch-up work). Conventionally (FIG. 1), after the catch-up operation (step A6), after the maintenance current program source P2 as a maintenance development product is acquired and parsed, the syntax of the non-standard list 30 is used. The corresponding syntax could not be specified, and the system migration migration design corresponding to the specified syntax could not be performed.

As described above, a part of the catch-up work (step B4) can be omitted, or the system development transition design can be performed prior to the conversion development stage. As a result, compared with the catch-up work in step A6 (FIG. 1), it is possible to shorten the work period of the catch-up work (step B4) and reduce the number of man-hours. The system can be moved up from the system transition (reference numeral M1) in FIG. 1 (early system transition).
It should be noted that the period required to create the design standard 10 and the code check tool 20 in step B1 and the period required to reflect the non-standard list 30 in step B3 are so short that they can be ignored compared to the shortening period of the catch-up work.
The conversion development server 5 that executes the above steps B1, B3, and B4 and the current system maintenance PC 2 that executes step B2 constitute the program source conversion device of the present invention, and the program source conversion method of the present invention. Execute.

[Conversion development details, maintenance development details]
With reference to FIG. 3, a detailed procedure of conversion development in the migration development environment and a detailed procedure of maintenance development in the current system maintenance development environment will be described.
As shown on the left side of FIG. 3, in the migration development environment in which the conversion development server 5 and the test server 5t are arranged, migration analysis (step B11), migration design (step B12), reverse (step B13), program Conversion (step B31), conversion test (step B32), program conversion (step B41), and test (step B42) are executed in this order.

In the migration analysis (step B11), syntax analysis of the current program source P1 is performed.
In the migration design (step B12), setting of coding rules (example: variable naming, method and class setting) is performed. The design standard 10 is created by the transition design (step B12).
In reverse (step B13), the code check tool 20 is created by reflecting (reversing) the result of the migration design (step B12) in a parser of known technology.
The above migration analysis (step B11), migration design (step B12), and reverse (step B13) are executed in step B1 (FIG. 2).

In the program conversion (step B31), the program language used in the current program source P1 is converted into another program language to create a new program source P3.
In the conversion test (step B32), a test of the new program source P3 is performed by the test server 5t.
The program conversion (step B31) and the conversion test (step B32) are executed in step B3 (FIG. 2).

In the program conversion (step B41), the program language used in the maintained current program source P2 is converted into another program language to create a maintained new program source P4.
In the test (step B42), a test of the maintained new program source P4 by the test server 5t is performed.
The program conversion (step B41) and the conversion test (step B42) are executed in step B4 (FIG. 2).

As shown on the right side of FIG. 3, in the current system maintenance development environment in which the current system maintenance PC 2 and the test server 2t are arranged, basic design (step B21), detailed design (step B22), coding (step B23), And a test (step B24) is performed in this order.

In the basic design (step B21), the modification change portion of the current program source P1 and the modification items of the portion are determined. In the basic design (step B21), the design standard 10 is appropriately referred to.
In the detailed design (step B22), the setting of the coding rule and the like are performed in a manner that is as close as possible to the design standard 10. When the detailed design (step B22) is completed, the maintained current program source P2 is created.
In coding (step B23), a coding review including the output result of the code check tool 20 is performed on the created maintained current program source P2. The coding review is repeatedly performed, and bugs and the like included in the maintained current program source P2 are removed.
In the test (step B42), a test of the current program source P2 that has been maintained by the test server 2t is performed. When the test (step B42) is completed, a maintained current program source P2 in which operation confirmation is guaranteed is created.
The basic design (step B21), detailed design (step B22), coding (step B23), and test (step B24) are executed in step B2 (FIG. 2).

≪Configuration≫
[Reverse device]
The reverse apparatus R (information processing apparatus) of this embodiment will be described with reference to FIG. The reverse device R is a device that performs reverse (step B13 in FIG. 3), and is a device that is a part of the conversion development server 5. The reverse device R is a computer including hardware such as an input unit, an output unit, a control unit, and a storage unit. For example, when the control unit is configured by a CPU (Central Processing Unit), information processing by a computer including the control unit is realized by program execution processing by the CPU. The storage unit included in the computer stores various programs for realizing the functions of the computer in accordance with instructions from the CPU. This realizes cooperation between software and hardware. The program can be provided by being recorded on a recording medium or via a network.

The reverse device R includes a parser unit r1 (parser unit), a setting unit r2 (setting unit), an editing unit r3, and a tool creation unit r4 (tool creation unit). The parser unit r1, the setting unit r2, the editing unit r3, and the tool creation unit r4 are specific functional units of the control unit of the reverse device R. The reverse device R includes a code check program 14. The code check program 14 constitutes a part of the code check tool 20 and is a program source in which processing contents of the code check tool 20 are described. The code check program 14 is created in reverse (step B13 in FIG. 3) and stored in the storage unit of the reverse device R.

(Parser part r1)
The parser unit r1 performs syntax analysis of the current program source P1. When the parsing of the current program source P1 is completed, the parser unit r1 can specify the token and syntax used for the current program source P1. The parser unit r1 outputs the specified token as a pre-maintenance token list P1a, and outputs the specified syntax as a pre-maintenance syntax list P1b. The parser unit r1 can be prepared for each programming language.

(Setting part r2)
The setting unit r2 sets information permitted to be used for the new program source P3 as the permission information 11 based on the design standard 10 of the new program source P3. The permission indicated by the permission information 11 is a permission from the conversion development side that creates the new program source P3 to the maintenance development side that creates the maintained current program source P2, and a viewpoint of shortening the catch-up work (step B4 in FIG. 2). Therefore, the information shown in the permission information 11 may be used for the maintained current program source P2.

The permission information 11 includes additional token permission information 11a, additional syntax permission information 11b, and additional character string permission information 11c.
The additional token permission information 11a is information indicating tokens that are permitted to be used for the new program source P3.
The additional syntax permission information 11b is information indicating a syntax permitted to be used for the new program source P3.
The additional character string permission information 11c is information indicating a character string permitted to be used for the new program source P3. The “character string” is, for example, a comment sentence, and does not contribute to the operation of the program among codes used for the program source. In the present specification, the term “character string” is used in the meaning described on the left.

For example, since the token, syntax, and character string used in the current program source P1 are information to be developed for conversion development, it is preferable to use permission information 11 (tokens and maintenance in the pre-maintenance token list P1a). The syntax in the previous syntax list P1b is classified as permission information 11). However, this does not prevent the permission information 11 from including part of the token, syntax, and character string used in the current program source P1. On the conversion development side, a token, syntax, and character string other than the token, syntax, and character string used in the current program source P 1 may be appropriately prepared and added to the permission information 11.

Further, the setting unit r2 sets information prohibited from being used for the new program source P3 as the prohibition information 12 based on the design standard 10 of the new program source P3. The prohibition indicated by the prohibition information 12 is a prohibition from the conversion development side that creates the new program source P3 to the maintenance development side that creates the maintained current program source P2, and is a viewpoint of shortening the catch-up work (step B4 in FIG. 2). This means that the information shown in the prohibition information 12 is not desired (or may not be used) for the maintained current program source P2.

The prohibition information 12 includes additional token prohibition information 12a, additional syntax prohibition information 12b, and additional character string prohibition information 12c.
The additional token prohibition information 12a is information indicating tokens that are prohibited from being used for the new program source P3.
The additional syntax prohibition information 12b is information indicating a syntax that is prohibited from being used for the new program source P3.
The additional character string prohibition information 12c is information indicating a character string prohibited from being used for the new program source P3.

For example, since the token, syntax, and character string used in the current program source P1 are information to be developed for conversion development, it is preferable not to use the prohibition information 12. However, it does not prevent the token, syntax, and part of the character string used in the current program source P1 from being included in the prohibition information 12. Moreover, the conversion development side may prepare a predetermined token, syntax, and character string as appropriate and add them to the prohibition information 12.
The permission information 11 and the prohibition information 12 described above constitute an allowance rule for maintenance development, and are presented from the conversion development side to the maintenance development side.

(Editor r3)
The editing unit r3 edits the pre-maintenance token list P1a and the pre-maintenance syntax list P1b output from the parser unit r1 and the permission information 11 and prohibition information 12 output from the setting unit r2 so as to be combined into a desired format. To do. The editing unit r3 outputs the collected information as check information 13.

(Tool creation unit r4)
The tool creation unit r4 creates the code check tool 20 (tool) by packaging the check information 13 and the code check program 14.
The code check tool 20 created by the tool creation unit r4 and the design standard 10 created by the migration design (step B12 in FIG. 3) are installed in the test server 2t in the current system maintenance development environment (see FIG. 2). . The code check tool 20 and the design standard 10 may be installed in the current system maintenance PC 2 in the current system maintenance development environment.

[Details of Code Check Tool 20]
As shown in FIG. 5, the code check tool 20 includes a parser unit 21 and a determination unit 22 in addition to the check information 13 already described. The parser unit 21 and the determination unit 22 constitute a code check program 14.

(Parser part 21)
The parser unit 21 performs syntax analysis of the current program source P5 after maintenance. The post-maintenance current program source P5 is one in which the current program source P1 is tentatively or definitely modified and changed by maintenance development. Specifically, the post-maintenance current program source P5 is the maintained current program source P2 when coding (step B23 in FIG. 3) is in progress or completed (before the test), or the test (FIG. 3). Or the maintained current program source P2 when step B42) is completed.

When the parsing of the current program source P5 after maintenance is completed, the parser unit 21 can specify the token and syntax used in the current program source P5 after maintenance. The parser unit 21 outputs the specified token as a post-maintenance token list P5a, and outputs the specified syntax as a post-maintenance syntax list P5b. The parser unit 21 can be prepared for each programming language.

(Determination unit 22)
The determination unit 22 determines whether the permission information 11 and the prohibition information 12 are used in the current program source P5 after maintenance. Specifically, the post-maintenance token list P5a, the post-maintenance syntax list P5b, and the check information 13 (FIG. 4) of the code check tool 20 are input to the determination unit 22. Further, the difference between the post-maintenance token list P5a and the pre-maintenance token list P1a included in the check information 13 is specified, and the difference between the post-maintenance syntax list P5b and the pre-maintenance syntax list P1b included in the check information 13 is specified. Further, it is determined whether or not these specified differences are classified into the permission information 11 and whether or not the difference is classified into the prohibition information 12. Details of the determination process of the determination unit 22 will be described later.

The determination unit 22 causes the test server 2t to output the determination result 23 of the above determination. When information not shown in the permission information 11 is used in the current program source P5 after maintenance or information shown in the prohibition information 12 is used in the current program source P5 after maintenance, the determination unit 22 A list of such information used is included in the determination result 23 as a non-standard list 30 (see FIG. 2).
The determination by the determination unit 22 can be performed after the syntax analysis by the parser unit 21 or can be performed while performing the syntax analysis.

Further, the determination unit 22 can perform the same determination as described above not only on tokens and syntax but also on character strings. Specifically, first, the code check tool 20 extracts a character string from the post-maintenance current program source P5 using a known technique, and creates a post-maintenance character string list P5c. Further, the post-maintenance character string list P5c and the check information 13 (FIG. 4) are input to the determination unit 22. Further, it is determined whether or not each of the character strings included in the post-maintenance character string list P5c is classified into the permission information 11 and the prohibition information 12. The determination unit 22 causes the test server 2t to output a determination result 23 regarding the character string. When information not shown in the permission information 11 is used in the post-maintenance character string list P5c, or when information shown in the prohibition information 12 is used in the post-maintenance character string list P5c, the determination unit 22 A list of such information used is included in the determination result 23 as a non-standard list 30 (see FIG. 2).

(Determination process of the determination unit 22)
As shown in FIG. 6, the post-maintenance current program source determination process performed by the determination unit 22 for the post-maintenance current program source P5 is as follows. FIG. 6 describes the syntax included in the post-maintenance syntax list P5b of the post-maintenance program source P5.

First, in step S1, the determination unit 22 determines whether or not the additional syntax permission information 11b of the permission information 11 includes the post-maintenance syntax list P5b. If included (Yes in step S1), it means that all of the syntaxes in the post-maintenance syntax list P5b are permitted to be used for the new program source P3, and the process proceeds to step S2. On the other hand, if it is not included (No in step S1), it means that at least one of the syntaxes in the post-maintenance syntax list P5b is not permitted to be used for the new program source P3. move on.

Next, in step S2, the determination unit 22 determines whether the additional syntax prohibition information 12b of the prohibition information 12 and the post-maintenance syntax list P5b are sparse. If they are sparse (Yes in step S2), it means that none of the syntaxes in the post-maintenance syntax list P5b corresponds to a syntax that is prohibited from being used in the new program source P3. Proceed to On the other hand, if they are not sparse (No in step S2), it means that at least one of the syntaxes in the post-maintenance syntax list P5b is prohibited from being used for the new program source P3, and the process proceeds to step S4. .

Next, in step S3, the determination unit 22 determines that the syntax in the post-maintenance syntax list P5b includes only the additional syntax permission information 11b of the permission information 11 (according to the design standard 10). Is output.
In step S4, the determination unit 22 includes a syntax not included in the additional syntax permission information 11b of the permission information 11 in the syntax in the post-maintenance syntax list P5b, or an additional syntax of the prohibition information 12 An NG determination indicating that the syntax corresponding to the prohibition information 12b is included (departs from the design standard) is output.
After step S4, in step S5, the determination unit 22 extracts the syntax that has caused the NG determination from the syntax in the post-maintenance syntax list P5b, and adds it to the non-standard list 30 (usage outside acceptable rules). To do.
Next, in step S6, the determination unit 22 causes the test server 2t to output a determination result 23 obtained by combining the OK determination and the NG determination.

The determination result 23 is transmitted to the conversion development server 5 and the test server 5t in the migration development environment. The conversion development side can create a new program source P3 based on the determination result 23.

Note that the above description of the processing of the determination unit 22 is related to the syntax, but a token and a character string can be processed with the same logic. That is, it is determined whether or not the token in the post-maintenance syntax list P5b is composed only of the additional token permission information 11a of the permission information 11. Further, it is determined whether or not the character string in the post-maintenance syntax list P5b is composed only of the additional character string permission information 11c of the permission information 11.

(Summary)
According to the present embodiment, conversion development for converting the program language of the current program source P1 to create a new program source P3 and maintenance development for the current program source P1 are used in parallel for the new program source P3. Permission information 11 and prohibition information 12 that are permitted and prohibited to be set, and whether or not the permission information 11 and the prohibition information 12 are used in the current program source P5 after maintenance developed by the code check tool 20 Determine. Thereby, based on the determination result, it is possible to perform a system test of the new program source P3 after accurately grasping the program correction change due to the maintenance development, and to catch up with the maintained current program source P2 (FIG. 2). In step B4), it is easy to estimate the work man-hours, and it is possible to reduce the work period of the catch-up work and reduce (reduce) the man-hours.
Therefore, it is possible to realize early system transition from the current system where maintenance development is performed to the new system.

In addition, the code check tool 20 may indicate that the non-standard list 30 does not exist in the current program source P5 after maintenance, or if the non-standard list 30 exists, the non-standard list 30 may be acquired on the conversion development side. it can. As a result, if the non-standard list 30 does not exist, in the catch-up work for the current program source P2 that has been maintained, the part related to the system migration design can be omitted. Further, even if the non-standard list 30 exists, the system migration design can be performed prior to the catch-up work. As a result, it is possible to achieve further shortening of the work period and man-hour reduction of the catch-up work.

(Modification)
The present invention is not limited to the above-described embodiment, and can be modified without departing from the spirit of the present invention. For example, there are the following (a) and (b).
(A): Not limited to conversion development, which is the conversion of the program language of the current program source, but can be applied to system development that provides the same type of service but needs to change the contents of the program source more or less by region. it can. In other words, when creating a new program source that is planned to be operated in the B region using the current program source of the system operated in the A region, the program correction change due to the maintenance development of the current program source in the A region After grasping, it is possible to start catching up with a new program source for the region B. As a result, the amount of the catch-up work can be reduced, and the work period of the catch-up work can be shortened and the number of steps can be reduced.

(B): In the present embodiment, step B3 (FIG. 2) is assumed to be a part of step A2, and has been described as being performed prior to the catch-up operation (step B4). However, step B3 may not be a part of step A2, but may be handled as a work subsequent to step A2 and handled as a work preceding the catch-up work (step B4). In this case, the new program source P3 becomes a result of the work in step A2, and does not become a result of the work in step B3. In this case, step B3 is an operation in which the conversion development server 5 reflects the non-standard list 30 acquired from the current system maintenance PC 2 in the new program source P3 created in step A2. Step B3 can be handled to be performed in parallel with step A2. Further, the work combining Step B3 and Step B4 can be handled as a catch-up work.

In addition, it is possible to realize a technique in which various techniques described in this embodiment are appropriately combined.
The software described in this embodiment can be realized as hardware, and the hardware can also be realized as software.
In addition, hardware, software, flowcharts, and the like can be changed as appropriate without departing from the spirit of the present invention.

2 PC for current system maintenance
2t test server (test equipment)
5 Conversion development server 5t Test server P1 Current program source (current program source before maintenance)
P2 Maintained current program source P3 New program source P4 Maintained new program source P5 Current program source after maintenance 10 Design standard 11 Permit information 12 Prohibition information 13 Check information 20 Code check tool 21 Parser part 22 Judgment part 23 Judgment result 30 Non-standard List R Reverse device (information processing device)
r1 parser section (parser means)
r2 setting part (setting means)
r3 editing part r4 tool creation part (tool creation means)

Claims

A program source conversion device for converting a first program source into a second program source,
Creating a code check tool that analyzes the first program source and checks for allowed rules;
Converting the first program source into the second program source;
When the first program source is maintenance-developed, the maintenance-developed first program source is checked using the code check tool, and the maintenance-developed first program source is converted to the conversion. Extracting a usage outside the allowed rules to determine a policy to be reflected in the already-finished second program source;
Performing the step of converting the first program source developed and maintained based on the policy into a second program source and merging with the converted second program source;
The program source conversion method characterized by the above-mentioned.
In a program source conversion device for converting a first program source into a second program source,
Means for analyzing the first program source and creating a code checking tool for checking permissible rules;
Means for converting the first program source into the second program source;
When the first program source is maintenance-developed, the maintenance-developed first program source is checked using the code check tool, and the maintenance-developed first program source is converted to the conversion. Means for extracting a usage outside the permissible rule for determining a policy to be reflected in the completed second program source;
Means for converting the first program source developed and maintained based on the policy into a second program source and merging with the converted second program source;
A program source conversion apparatus.
A parser unit that parses the current program source before maintenance and creates a list of tokens and syntax used in the current program source before maintenance;
Based on the design criteria of the new program source, permission information indicating tokens, syntax, and character strings permitted to be used for the new program source, and use for the new program source are prohibited. A setting section for setting prohibition information indicating a token, syntax, and character string;
A tool creation unit that creates a tool for determining whether the permission information and the prohibition information are used in the current program source after maintenance,
An information processing apparatus characterized by that.
The tool created by the tool creation unit is
When operating in a test apparatus that tests the current program source after maintenance, information not shown in the permission information is used for the current program source after maintenance, or information shown in the prohibition information is When used in the current program source after the maintenance, the list of these used information is output to the test device.
The information processing apparatus according to claim 3.
Information processing device
Parsing the current program source before maintenance and creating a list of tokens and syntax used in the current program source before maintenance;
Based on the design criteria of the new program source, permission information indicating tokens, syntax, and character strings permitted to be used for the new program source, and use for the new program source are prohibited. Setting forbidden information indicating tokens, syntax, and strings;
Creating a tool for determining whether the permission information and the prohibition information are used in the current program source after maintenance; and
An information processing method characterized by the above.
Computer
Parser means for parsing the current program source before maintenance and creating a list of tokens and syntax used in the current program source before maintenance based on the parsing;
Based on the design criteria of the new program source, permission information indicating tokens, syntax, and character strings permitted to be used for the new program source, and use for the new program source are prohibited. Setting means for setting prohibited information indicating token, syntax, and character string,
Tool creation means for creating a tool for determining whether the permission information and the prohibition information are used in the current program source after maintenance;
Program to function as.