JP2024094938A - Information processing device, information processing method, and program - Google Patents

Abstract

The present invention aims to easily identify and display whether a developer should modify source code in response to the deletion of a screen item or whether the developer can deal with the deletion without modifying the source code.
SOLUTION
An information processing device that modifies a program of an application having a screen item, comprising: a receiving means for receiving the deletion of a screen item of the application; a determination means for determining a variable defined within an action of the application that is linked to the screen item to be deleted that is received by the receiving means; and a control means for deleting the relevant part of the variable determined by the determination means and, in the case of an action that satisfies a specified condition, controlling the deletion of the relevant part of the variable.
[Selected figure] Figure 5

Description

The present invention relates to an information processing device, an information processing method, and a program for performing refactoring of application software under development.

When defining an action for an input field placed on a screen in a web application, it is necessary to link the input field with the variable used in the action. Also, in order to output the result of the action to an output field, it is necessary to link the output field with the output result of the action.

However, the names of variables used in screen input/output item IDs and actions (for example, JavaScript (registered trademark)) must be defined separately.

Patent document 1 discloses a technology that extracts related variable names from the variables being analyzed in a source program, and outputs information on the number of occurrences and occurrence probability, making it easy to check related variable names.

JP 2002-132544 A

However, in Patent Document 1, the system only outputs and allows the user to confirm the names of related variables; when a screen item is deleted, it is not possible to immediately determine whether source code such as JavaScript (registered trademark) in which the corresponding variable is used should be modified.

The present invention aims to easily identify and display whether a developer should modify source code in response to the deletion of a screen item or whether the developer can deal with the problem without modifying the source code.

The present invention provides an information processing device for modifying a program of an application having screen items, comprising:
A receiving means for receiving deletion of a screen item of the application;
a specifying means for specifying a variable defined in an action of the application associated with the screen item to be deleted received by the receiving means;
a control means for controlling the deletion of the relevant part of the variable identified by the identifying means in the case of an action that satisfies a predetermined condition by deleting the relevant part of the variable;
The present invention is characterized by having the following.

According to the present invention, when a screen item is deleted, it is possible to easily identify and display whether the developer should modify the source code or whether the developer can deal with the problem without modifying it.

FIG. 1 is a system configuration diagram according to an embodiment of the present invention. FIG. 2 is a block diagram showing an example of a hardware configuration applicable to a program development device, an execution server, a database server, and a client terminal according to the present embodiment. 13 is an example of a flowchart of an application generation process. 13 is an example of a flowchart of a screen definition deletion process. 13 is an example of a flowchart of a process for identifying and displaying or deleting a variable associated with a screen item ID. 13 is an example of a screen display when an application is generated. 13 is an example of a screen display when modifying an application before and after deleting a screen item. 13 is an example of a screen display when an application is modified before a screen item is deleted. 13 is an example of a screen display when an application is modified after a screen item is deleted.

The following describes in detail the embodiments of the present invention with reference to the drawings.

Figure 1 is a system (information processing system) configuration diagram showing an example of the configuration of an information processing device 101 (a program development device operated by a developer to generate a Web application), an execution server 102, a database server 103, and a client terminal 104 according to the present invention.

The information processing device 101 defines screen layouts and database search instructions, etc., according to operations by a developer. The information processing device 101 generates application software such as programs (hereinafter simply referred to as applications). Specifically, the information processing device 101 sets the application definition, input/output definition, data model definition, business process definition, and database definition as repository definitions by a developer who develops a Web application, and generates a Web application using these definitions. These application definition, input/output definition, data model definition, business process definition, and database definition definitions may be input or configured in advance by the developer via a Web application development tool.

In this embodiment, the application generated by the information processing device 101 is a Web application, but this is not limited to this, and the application may not be an application that uses communication via Web technology, such as an application that runs on an information processing device such as a mobile phone, smartphone, or tablet, or embedded software.

The execution server 102 executes applications developed in the information processing device 101. It is also capable of operating in connection with the database server 103.

The database server 103 is a database used by the developed application, and may be used during development for purposes such as checking operation. For example, the database server 103 for use by a developer may be configured as the same device as the information processing device 101 or execution server 102, or may be located within a network 105 such as a LAN.

The client terminal 104 is an input terminal of an end user that operates an application program developed in the information processing device 101 in cooperation with the execution server 102. The client terminal 104 may be an information processing device such as a mobile terminal.

In addition, any of the information processing device 101, the execution server 102, the database server 103, and the client terminal 104 may be placed on the Internet, such as on the cloud.

Figure 2 is a block diagram showing an example of the hardware configuration applicable to the information processing device 101, execution server 102, database server 103, and client terminal 104 according to the present invention.

In FIG. 2, the CPU 201 comprehensively controls each device connected to the system bus 204.

The ROM 203 or external memory 211 also stores an operating system (OS), which is the control program for the CPU 201, and programs for implementing various functions of information processing devices, such as servers, clients, and devices, which will be described later.

RAM 202 functions as the CPU 201's main memory, work area, temporary storage area, etc.

The input controller 205 controls input from the input unit 209. In an information processing device, the input unit 209 may be a keyboard, a pointing device such as a mouse, or a touch panel.

When the input unit 209 is a touch panel, the user can give various instructions by pressing (touching with a finger, etc.) icons, cursors, or buttons displayed on the touch panel.

The touch panel may also be a touch panel capable of detecting positions touched by multiple fingers, such as a multi-touch screen.

The output controller 206 controls the display of the output unit 210. Examples of the output unit 210 include a CRT or a liquid crystal display. Note that this also includes the display of a notebook computer that is integrated into the main body. It may also be a projector.

The external memory controller 207 controls access to the external memory 211, which stores the boot program, various applications, font data, user files, edit files, printer drivers, etc. The external memory 211 stores various tables and parameters for implementing the various functions of each server, client, device, etc. Examples of this external memory 211 include a hard disk (HD), a flexible disk (FD), a compact flash (registered trademark) connected to a PCMCIA card slot via an adapter, a smart media, etc.

The CPU 201 enables display on the output unit 210 by, for example, executing an outline font expansion (rasterization) process on a display information area in the RAM 202. The CPU 201 also enables user instructions with a mouse cursor (not shown) on the output unit 210.

The communication I/F controller 208 executes communication control processing with external devices via a network. For example, communication using TCP/IP is possible.

The program 212 for implementing the present invention is recorded in the external memory 211, and is executed by the CPU 201 by being loaded into the RAM 202 as required.

Figure 3 is a diagram showing an example of a flowchart for generating a web application. Note that each step of the flowchart in Figure 3 is executed by the CPU 201 of the information processing device 101.

In S301, the information processing device 101 receives input of a screen definition for the application from the developer. An example of the screen definition will be described with reference to FIG. 6.

Figure 6 (a) shows an example of a screen definition entered by a developer. A screen definition such as the input/output screen on the right is accepted by dragging and dropping with the mouse from palettes such as "Input/Output" and "Selection List" on the left to the editor area 604 on the right.

Figure 6 (b) shows the properties of the text input area 601 in Figure 6 (a).

In FIG. 6(b), "G_ITEM_TEXT" is automatically set as the code (the name written as the variable name when the source code is generated) for the text input area 601. Let's return to the explanation of the flowchart in FIG. 3.

In S302, the information processing device 101 divides the process depending on whether or not there is a request from the developer to input an action definition for the screen definition. If there is a request to input an action definition, the process transitions to S303, and if there is no input request, the process transitions to S304.

In S303, the information processing device 101 accepts input of an action definition from the developer. Examples of actions will be described with reference to Figures 7 and 8.

Figure 7 (a) is an action definition corresponding to the update action button 602 in Figure 6 (a), and is a definition in which the process in the middle flowchart is performed after the update action button 602 is pressed.

Figure 8 (a) is an action definition corresponding to the insert action button 603 in Figure 6 (a), and is a definition in which the process in the middle flowchart is performed after the insert action button 603 is pressed.

When defining each, the data entered in the text input area 601 is stored in the variable name "ptext" at 701 in FIG. 7(a) and 801 in FIG. 8(a), and is used to update or insert data. Let's return to the explanation of the flowchart in FIG. 3.

In S304, the information processing device 101 divides the process depending on whether or not there is a request from the developer to save the screen definition. If there is a save request, the process proceeds to S505, and if there is no save request, the process proceeds to S306.

When the process transitions to S305, the information processing device 101 saves the screen definition (including the action definition) in the external memory 211.

In S306, the information processing device 101 divides the process depending on whether or not there is a request from the developer to generate an application. If there is a request to generate an application, the process transitions to S307. If there is no request to generate an application, the process returns to S301, and the process returns to inputting the screen definition.

In S307, the information processing device 101 generates an application from the screen definition defined in S301 and the action definition defined in S303. As a result of the processing of the flowchart in FIG. 3, a web application having an input screen like the screen of the editor area 604 in FIG. 6(a) is generated.

Next, the process flow for deleting a screen definition from the Web application generated in FIG. 3 will be described with reference to FIG. 4. Note that each step of the flowchart in FIG. 4 is executed by the CPU 201 of the information processing device 101.

In S401, the information processing device 101 displays the screen editor that was generated or is being generated in FIG. 3 on the output unit 210. FIG. 6(a) is an example of the display of the screen editor.

In S402, the information processing device 101 receives an instruction to delete a screen item (e.g., the text input area 601) in the screen editor displayed in S401. When the deletion instruction is received, a screen is displayed on the screen editor with the text input area 621 removed, as shown in FIG. 6(c).

In S403, the information processing device 101 divides the process depending on whether there is an action event in the screen definition in which a variable corresponding to the deleted screen item is used. If there is an action event, the process transitions to S404. If there is no action event, the process ends with the flowchart in FIG. 4 and only the process of deleting the screen item from the screen definition.

In S404, the information processing device 101 executes a process to select whether to identify and display the variables linked to the ID (code) of the screen item to be deleted, or to delete the process linked to the ID (code) of the screen item. Details will be described with reference to FIG. 5.

FIG. 5 is a flowchart illustrating the flow of processing executed by selecting whether to identify and display variables linked to the ID (code) of a screen item to be deleted in this embodiment, or to delete a process linked to the ID (code) of the screen item.
@
In step S501, the information processing apparatus 101 acquires the name of a variable associated with the ID (code) of the screen item to be deleted. For example, when deleting a text input area 601 as shown in 621 in Fig. 6C, a variable name "ptext" as shown in 701 or 801 in Fig. 7A or 8A is acquired.

In S502, the information processing device 101 divides the process depending on whether or not there is an action using the variable name obtained in S501. If there is an action using the variable name obtained in S501, the process transitions to S503, and if there is no action using the variable name obtained in S501, the process of the flowchart in FIG. 5 ends.

When the process transitions to S503, the information processing device 101 divides the process depending on whether the action using the variable name acquired in S501 is only a data model bind process. If the action using the variable name acquired in S501 is only a data model bind process, the process transitions to S508, and if the action using the variable name acquired in S501 is used for something other than a data model bind process, the process transitions to S504.

Data model binding is a process that associates data input and output by the user with a database. A situation in which a variable name is only used in the data model binding process means that the variable name was not used by the developer in the action definition in S303 when the application was generated in S307. The data model binding process is a process that can automatically generate an application in S307, and if a variable name is used by the developer in the action definition in S303, the developer has made some changes to it as a processing formula or conditional expression. Therefore, simply deleting the variable name in the part that the developer has made changes to runs the risk of a syntax error in the processing formula or conditional expression.

In S504, the information processing device 101 identifiably displays (priority display) the variable names obtained in S501 within the action.

In S505, the information processing device 101 identifiably displays the data model bind step of the variable name acquired in S501. The screen images of the processing results of S504 and S505 will be described with reference to FIG. 9.

Figure 9(a) shows an example of a case where the screen item "G_ITEM_TEXT" has been deleted as in 621 in Figure 6(c) from the data model bind 801 registration of "G_ITEM_TEXT" in Figure 8(a), which is the data model bind setting. The screen item code "G_ITEM_TEXT" has been deleted as in 901, but the variable name "ptext" has not been deleted. Therefore, as in 901, "ptext" is displayed with a thick underline or similar to make it identifiable from other variable names. Also, as in the flow chart in the middle of Figure 9(b), an exclamation mark "!" is added to the processing step in which the variable name "ptext" is used as in 912, to make it identifiable from other processing steps.

The reason why the "ptext" line in 901 itself is not deleted is to prevent the occurrence of a syntax error caused by arbitrarily deleting the variable name "ptext" 901 that has been modified (quoted) by the developer. For example, if the "ptext" 911 quoted in the conditional expression 913 in FIG. 9B is simply deleted, the conditional expression 913 will change from "pkey !='' && ptext !=''" to "pkey !='' && !=''", resulting in a syntax error in which there is no term to the left of the inequality sign in the second term. When a developer sees the deleted conditional expression, they will not know what was written there, which will take time to debug. For this reason, the variable name obtained in S501 is intentionally left displayed, and is displayed in a thick underline like 911 so that it can be easily identified, encouraging the developer to make appropriate corrections. Return to the explanation of the flowchart in FIG. 5.

In S506 of FIG. 5, the information processing device 101 accepts changes to the action's source code from the developer.

In S507, the information processing device 101 checks the source code for errors after the developer changes the source code in S506, and if the errors are resolved, the process proceeds to S508. If the errors are not resolved, the process returns to S506, and the developer is prompted to resolve the errors.

In S508, the information processing device 101 deletes the data model bind process definition corresponding to the variable name obtained in S501 from the action. Specifically, line 902 in FIG. 9A is deleted. Also, if the only action using the variable name obtained in S501 is the data model bind process (if transition is made directly from S503 to S508), this can also be handled by deleting line 701 from FIG. 7A to FIG. 7B.

As described above, if the only action using the variable name obtained in S501 is data model binding, the data model bind process definition itself is deleted, but if the action using the variable name obtained in S501 is used for something other than data model binding, the data model bind process definition is not immediately deleted. By identifiably displaying action definitions that use the variable names obtained in S501 that are relevant to the developer and allowing them to correct them, it is possible to minimize debugging work due to syntax errors, etc. Return to the explanation of the flowchart in Figure 4.

In S405 of FIG. 4, if there are other actions (for example, an UPDATE action in addition to the INSERT action), the process returns to S404 to select whether to identify and display the variables linked to the ID (code) of the screen item to be deleted for the other actions, or to delete the process linked to the ID (code) of the screen item.

The above process makes it easy to identify whether the developer should modify the source code in response to the deletion of a screen item or whether the developer can handle the situation without modifying it.

As described above, it goes without saying that the object of the present invention can be achieved by supplying a recording medium on which a program that realizes the functions of the above-mentioned embodiments is recorded to a system or device, and having the computer (or CPU or MPU) of that system or device read and execute the program stored on the recording medium.

In this case, the program read from the recording medium itself realizes the novel functions of the present invention, and the recording medium on which the program is recorded constitutes the present invention.

Recording media for supplying the program may include, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a DVD-ROM, a magnetic tape, a non-volatile memory card, a ROM, an EEPROM, a silicon disk, etc.

Furthermore, it goes without saying that not only are the functions of the above-mentioned embodiments realized by the computer executing a program it has read, but also that the functions of the above-mentioned embodiments can be realized by an operating system (OS) or the like running on the computer carrying out some or all of the actual processing based on the instructions of the program.

Furthermore, it goes without saying that this also includes cases where a program read from a recording medium is written into a memory provided on a function expansion board inserted into a computer or a function expansion unit connected to a computer, and then a CPU or the like provided on the function expansion board or function expansion unit performs some or all of the actual processing based on the instructions of the program code, thereby realizing the functions of the above-mentioned embodiments.

The present invention may be applied to a system made up of multiple devices, or to a device made up of a single device. Needless to say, the present invention can also be applied to cases where the effects of the present invention are achieved by supplying a program to a system or device. In this case, the effects of the present invention can be enjoyed by reading a recording medium that stores a program for achieving the present invention into the system or device.

The program may be in the form of object code, program code executed by an interpreter, script data supplied to an OS (operating system), etc.

Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or device can enjoy the effects of the present invention. Note that the present invention also includes configurations that combine the above-mentioned embodiments and their modified examples.

101 Program development device (information processing device)
102 execution server 103 database server 104 client terminal 105 network

Claims (11)

An information processing device for modifying a program of an application having a screen item, comprising:
A receiving means for receiving deletion of a screen item of the application;
a specifying means for specifying a variable defined in an action of the application associated with the screen item to be deleted received by the receiving means;
a control means for controlling the deletion of the relevant part of the variable identified by the identifying means in the case of an action that satisfies a predetermined condition by deleting the relevant part of the variable;
13. An information processing device comprising: The information processing device according to claim 1, wherein the control means controls the part related to the variable to be identifiable and displayed without deleting the part related to the variable when the action does not satisfy the predetermined condition. The information processing device according to claim 1 or 2, characterized in that the action is a process executed by pressing a UI button on the application screen. The information processing device according to claim 1 or 2, characterized in that, when there is an action that does not satisfy the predetermined condition due to the deletion of a screen item accepted by the accepting means, the control means displays the part of the action related to the variable with priority. The information processing device according to claim 4, characterized in that the control means preferentially displays the part of the variable related to the action that does not satisfy the predetermined condition, and then deletes the part of the variable related to the action that satisfies the predetermined condition. The information processing device according to claim 1 or 2, characterized in that the action that does not satisfy the predetermined condition is an action that would cause an inconsistency in the application if the relevant part of the variable identified by the identification means is deleted. The information processing device according to claim 1 or 2, characterized in that the action that does not satisfy the predetermined condition is an action that causes an error when the application is executed if the relevant part of the variable identified by the identification means is deleted. The information processing device according to claim 1 or 2, characterized in that the action that does not satisfy the predetermined condition is an action that the application cannot execute if the relevant part of the variable identified by the identification means is deleted. The information processing device according to claim 1 or 2, characterized in that the action that does not satisfy the predetermined condition is an action other than an action that accesses a database. A control method for an information processing device for modifying a program of an application having a screen item, comprising:
a receiving step of receiving deletion of a screen item of the application;
a step of identifying a variable defined in an action of the application associated with the screen item to be deleted received in the receiving step;
a control step of deleting the relevant part of the variable identified in the identifying step in the case of an action that satisfies a predetermined condition by deleting the relevant part of the variable;
13. A method for controlling an information processing apparatus comprising the steps of: A program for causing a computer to function as each of the means of the information processing device described in claim 1 or 2.