Information processing system, control method thereof, and program

Abstract

To provide a system of easily setting a definition file when generating a program to be used in a Web application.SOLUTION: An information processing unit generates a program to be used as a Web application and includes: definition management means configured to manage a definition file; item dictionary management means configured to manage a correspondence between one or more items and predetermined definition information corresponding to the item; and display control means configured to display, in a display part, a first display region for displaying a display item showing a definition file managed in the definition management means and a second display region different from the first display region. The item dictionary management means is configured to set a definition file corresponding to the display item as a management object in response to a drag-and-drop operation of a display item displayed in the first display region to the second display region.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to a program generation device, a control method, and a computer program. [Background technology]

[0002] In recent years, web applications have been developed automatically using program generation devices, without the need for programming. Instead of programming, the automatic generation tool running on the program generation device uses definitions based on predetermined rules to build web applications. Here, each definition used to build a web application is set for each schema information and screen information for the database used within the application.

[0003] Patent Document 1 discloses a system design support program that generates a program using definition information in an upstream design tool. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-41707 Summary of the Invention [Problem to be solved by the invention]

[0005] As the scale of a Web application increases, more and more definition files are used. In this case, the automatic generation tool sets the same keywords for multiple definition files, which can make user operations cumbersome. Therefore, it is desirable to centrally manage definition files. However, the technology described in Patent Document 1 does not take into consideration user operability when managing existing definition files.

[0006] Therefore, the present invention ,a Application of Generate Used for definition of The purpose is to provide a mechanism that is easy to set up. [Means for solving the problem]

[0007] Defines the items used to build the application , having a key and at least one value a management means for managing definition information; Manage using the management means fixed a registration means for registering definition information in an item dictionary; a construction means for constructing an application by using, when a value of definition information relating to an item registered in the item dictionary is changed, the changed value as a value of definition information referencing the same key; The present invention is characterized by having the following. [Effects of the Invention]

[0008] application of Generate Used for definition of It is possible to provide a mechanism for easy setting. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of an information processing system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration applicable to each component of the information processing system according to the present embodiment. [Figure 3] FIG. 2 is a diagram illustrating a functional configuration of the program development device according to the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating a functional configuration of the program development device according to the present embodiment. [Figure 5] 10 is a flowchart showing a process for creating a new item dictionary. [Figure 6] FIG. 10 is a diagram showing an example of an operation screen for creating a new item dictionary. [Figure 7] FIG. 10 is a diagram showing an example of a screen displaying an item dictionary file. [Figure 8] 10 is a flowchart showing a process for adding an item to an item dictionary. [Figure 9]FIG. 10 is a diagram showing an example of a display screen when an entry is added to an item dictionary file. [Figure 10] FIG. 10 is a diagram showing an example of a display screen when adding one definition item to an entry. [Figure 11] FIG. 10 is a diagram showing an example of a display screen when adding multiple definition items to an entry. [Figure 12] 10 is a flowchart showing a process for reflecting an item dictionary in a repository definition. [Figure 13] FIG. 10 is a diagram showing an example of a display screen when an item dictionary is reflected in a repository definition. [Figure 14] FIG. 10 is a diagram showing an example of a display screen when an item dictionary is reflected in a repository definition. [Figure 15] 10 is a flowchart showing a process for updating the contents of a dictionary entry and a dictionary item. [Figure 16] 10 is a flowchart showing a process for generating a Web application. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0011] FIG. 1 is a system (information processing system) configuration diagram showing an example of the configuration of a program development device (an information processing device used by a developer to generate a Web application) according to this embodiment, a program development server, a database server, an application client (client device), and an application server.

[0012] The program development device 101 defines the screen layout, database search instructions, etc. in accordance with the developer's operations. The program development device 101 alone may accept input from the developer and have the program development server 102, which will be described later, perform the actual program generation process and application generation process, or the program development device 101 alone may perform the program generation and application generation process.

[0013] In this embodiment, the application generated by the program development device 101 is a web application, but this is not limited to this, and it may be an application that does not use 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.

[0014] Program development servers 102a and 102b (information processing devices) develop programs according to instructions from a developer input via program development device 101. Program development server 102a may be located within network 106 such as a LAN, and program development server 102b may be located on the Internet or in the cloud.

[0015] Database servers 103a-103b (information processing devices) are databases used by developed applications, and may also be used during development for purposes such as checking operation. For example, database server 103 for use by developers may be configured as the same device as program development device 101, or may be located within network 106 such as a LAN (database server 103a). It may also be located on the Internet or in the cloud (database server 103b). Furthermore, when program development device 101 cooperates with program development server 102, program development server 102 and database server 103 may be configured in the same device.

[0016] The application servers 105a and 105b (information processing devices) execute applications developed by the program development device 101. They may be located within a network 106 such as a LAN (application server 105a), or may be located on the Internet or the cloud (application server 105b). They can also operate by connecting to a database server 103 on the network 106, the Internet, or the cloud.

[0017] The application clients 104a to 104b (information processing devices) are user input terminals that operate application programs developed by the program development device 101 in cooperation with the application server 105. They may be located within a network 106 such as a LAN (application client 104a), or may be located on the Internet or in the cloud (application client 104b). The information processing devices may also be mobile terminals or tablet terminals.

[0018] FIG. 2 is a block diagram showing an example of the hardware configuration applicable to the program development device 101, the program development server 102, the database server 103, the application client 104, and the application server 105 according to this embodiment.

[0019] In FIG. 2, a CPU 201 controls all devices connected to a system bus 204 .

[0020] The ROM 203 or external memory 211 also stores an operating system (OS) that is a control program for the CPU 201, and programs for realizing various functions of the information processing device, such as each server, client, and device, which will be described later.

[0021] The RAM 202 functions as the main memory, work area, temporary save area, etc. for the CPU 201.

[0022] The input controller 205 controls input from the input unit 209. In the case of an information processing device, the input unit 209 may include a keyboard, a mouse, or other pointing device.

[0023] The output controller 206 controls the display of the output unit 210. Examples of this output unit 210 include a CRT and a liquid crystal display. In other words, the output unit 210 has a function as a display unit that displays a screen. In this case, the CPU 201 can control the display of the display unit via the output controller 206. In other words, the CPU 201 is one aspect of display control means.

[0024] The external memory controller 207 controls access to an external memory 211 that stores a boot program, various applications, font data, user files, edit files, printer drivers, etc. In addition, various tables and parameters for realizing various functions of each server, client, device, etc. Examples of this external memory 211 include a hard disk (HD), a flexible disk (FD), a CompactFlash (registered trademark) card connected to a PCMCIA card slot via an adapter, and a SmartMedia card.

[0025] A communication I / F controller 208 executes communication control processing with external devices via a network.

[0026] The functional configuration of the program development device 101 will be described with reference to Figures 3 and 4. Each function in the program development device 101 is executed by a CPU 201 of the program device 101. A program 212 executed by the CPU 201 is recorded in an external memory 211 and is loaded into a RAM 202 as needed. In other words, each function is realized by cooperation between the CPU 201 and the memory (RAM 202).

[0027] The program development device 101 includes a repository definition unit 300 , an item dictionary management unit 320 , a repository definition editing unit 310 , an item dictionary reference command unit 330 , and a Web application generation unit 340 .

[0028] The repository definition section 300 includes a database definition 406 , an application definition 401 , a data model definition 403 , an input / output definition 402 , and a business process definition 404 .

[0029] A plurality of item definitions are set in the data model definition 403 and the input / output definition 402. Each item definition is stored in association with item dictionary reference information 405. This allows the data model definition 403 and the input / output definition 402 to refer to information managed by the item dictionary management unit 320 (described later) and use it as a definition.

[0030] The repository definition unit 300 manages, as input / output definitions 402, input definition information that defines items to be input as arguments to a program, and output definition information that defines items to be output from the program as processing results. Here, the input definition information is information that defines the input items that a user of the generated Web application enters via the screen of the Web application. Also, the output definition information is information that defines the output items to be output as the screen of the generated Web application.

[0031] A user (for example, a Web application developer) can intuitively add, change, or delete input / output items on a Web application screen based on the various definitions managed by the repository definition unit 300. This allows the user to easily create a program to be used as a Web application. The above-mentioned "addition, change, and deletion" is performed using a GUI such as a layout editor.

[0032] The data model definition 403 is information for managing schema information of a database (that is, the attributes, names, and number of digits of items).

[0033] The business process definition 404 is information for managing the business flow.

[0034] The item dictionary reference information 405 manages reference information indicating whether or not to refer to predetermined definition information in the item dictionary managed by the item dictionary management unit 320 for the data model definition 403 and the input / output definition 402 .

[0035] The item dictionary management unit 320 has the functions of registering, editing, and deleting items to be defined in the item dictionary, and managing the information in the item dictionary. Each item that has been registered, modified, or deleted is managed by the item dictionary storage unit 421.

[0036] A new item dictionary can be created by operating the screen displayed in the item dictionary file creation display section 424. The process of creating a new item dictionary will be described later with reference to FIG.

[0037] Items can be registered, edited, or deleted from the item dictionary by operating the screen displayed in the item dictionary editing and display unit 423. Items registered in the item dictionary are managed as a single unit, consisting of a combination of definition type and definition target. Hereinafter, this single unit of data set will be referred to as an "entry." Registered items are managed as value data, data for data model items, and data for input / output items. Each piece of data for registered items can be edited by the repository definition editing unit 310. Specifically, it is available from the item dictionary selection and display unit 422, which the repository definition editing unit 310 controls via the item dictionary reference command unit 330. Information indicating a reference to the dictionary is stored as item dictionary reference information 405.

[0038] The Web application generation unit 340 has a function for generating a Web application. The repository definition analysis unit 441 analyzes repository information registered in the item dictionary based on the item dictionary reference information 405. That is, the repository definition analysis unit 421 reads and analyzes the database definition 406, data model definition 403, input / output definition 402, and business process definition 404 from the repository definition unit 400 based on the item dictionary reference information 405. The Web application generation unit 442 can generate a program as a Web application via the source code compilation unit 445.

[0039] 5 is an example of a flowchart for creating a new item dictionary. Each step in the flowchart is executed by each function of the program development device 101.

[0040] In S500, the item dictionary management unit 320 receives a new dictionary creation event when a display item indicating the creation of a new dictionary file is selected on an operation screen (not shown) displayed on the display unit.

[0041] In S510, in response to receiving the above-mentioned event, the item dictionary file creation display unit 424 of the item dictionary management unit 320 displays a new dictionary file creation screen 600. FIG. 6 shows details of the new dictionary file creation screen 600. FIG. 6 is a diagram showing an example of an operation screen for creating a new item dictionary. The new item dictionary creation screen 600 includes an input acceptance unit 601. The user can input a code and a name from the input acceptance unit 601. In other words, the code and name of the newly created item dictionary are determined based on the code and name entered on the new dictionary file creation screen 600. In this embodiment, an example is shown in which "customer" is entered as the code and "customer dictionary" as the name on the new dictionary file creation screen 600.

[0042] In S520, in response to the pressing of the Finish button 620, the item dictionary management unit 320 creates a new item dictionary file.

[0043] Next, the item dictionary file created according to the flow of FIG. 5 will be described with reference to FIG.

[0044] FIG. 7 shows an example of a screen displaying an item dictionary file. FIG. 7(a) is an editing screen on which an item dictionary file can be edited. Editing screen 700 is a screen displayed by the item dictionary editing display unit 423. FIG. 7(b) is an XML display screen displayed in XML format. An item dictionary file is created from text data 700 written in the XML language (hereinafter referred to as XML data). The code and name entered in step 520 are set as part of the text data in XML 700, as indicated by code 701 and name 702. Note that when the "File Information" and "XML" tabs are selected on the editing screen 700 in FIG. 7(a), the item dictionary editing display unit 423 changes the display to the corresponding information.

[0045] Next, a control flow for adding an item to the generated item dictionary will be described with reference to Fig. 8. This control is executed by the functions of the program development device 101.

[0046] In S800, the item dictionary management unit 320 acquires an event to open the item dictionary editing screen. For example, the item dictionary management unit 320 acquires the event in response to a user operation from a display showing the file name of the created item dictionary.

[0047] In S801, the item dictionary edit display unit 423 displays the edit screen 700.

[0048] In S802, the item dictionary management unit 320 receives an entry addition event in response to the selection of the Add button 901 on the context menu screen 900 displayed by the item dictionary edit display unit 423. The context menu screen 900 is displayed, for example, by accepting a click operation on the file name of the item dictionary on the edit screen 700.

[0049] In S803, the item dictionary management unit 320 sets a dictionary key, a name, and a reading for the added entry. In this embodiment, as shown in Fig. 9, the following are set for the entry: the dictionary key is set to "ORDER," the name is set to "Kyuuyuu" (order), and the reading is set to "Chuumon" (reading). With these settings, the XML data 710 is updated to XML data 920. The updated entry is displayed as shown on the editing screen 910 in Fig. 9. In other words, the updated entry is displayed in the entry list display portion 911 on the added (or updated) editing screen 910 in a manner that allows it to be distinguished from other entries.

[0050] In S804, the item dictionary management unit 320 determines whether the item to be registered in the item dictionary is a single item. Here, if the item dictionary management unit 320 receives an add event in response to selecting the add button 901 from the context menu screen 900 displayed by the item dictionary edit display unit 423, it determines that a single item has been added.

[0051] In S805 and S806, at least one of value data, data model item data, and input / output item data is input to and saved in the definition information for the entry selected on the editing screen 940 by a user operation. By performing this saving process, XML 920 is updated to XML 950. The updated dictionary is displayed as a list in a definition information display section 941 on the editing screen 940 shown in FIG. 10 . Here, the definition information display section 941 has a function of displaying the definition information of the entry selected in an entry list display section 942 on the editing screen 940.

[0052] The flow when it is determined in the determination process of S804 that the item to be registered in the item dictionary is not a single item will be described. As an example, in S804, if the registration process is performed by dragging and dropping from the data model item definition and input item definition in the definition tree 970 displayed by the definition structure display unit 412 in Fig. 11, it is determined that the item is not a single item. Also, if an add event is received based on the selection of 961 or 962 on the context menu screen 960 displayed by the item dictionary edit display unit 423, it is determined that the item is not a single item.

[0053] In this way, one or more definitions that have already been set can be registered in the item dictionary in a single operation, allowing the user to set them with a simple operation.

[0054] In S807, the item dictionary management unit 320 determines whether to register all of the keys to be registered in the dictionary. If the item dictionary management unit 320 receives an event based on the selection of the partial registration menu 962, it determines that not all of the keys are to be registered and proceeds to S809.

[0055] In S808, the item dictionary management unit 320 sets all keys defined in the triggered repository definition as registration targets. In S809, the item dictionary management unit 320 sets the items set in the registration setting file 990 as registration targets.

[0056] In S810, the item dictionary management unit 320 determines whether the triggered repository definition is a data model item definition. If the item dictionary management unit 320 determines that it is a data model item definition, the process proceeds to S811. In S811, the item dictionary management unit 320 registers the value defined in the data model item as a dictionary. If the determination process in S810 determines that the triggered repository definition is an input / output item definition, the process proceeds to S812. In S812, the item dictionary management unit 320 registers the value defined in the input / output item definition as an item dictionary.

[0057] In S813, when an item is registered in the item dictionary, the item dictionary management unit 320 determines whether to refer to the item dictionary for the registered item. The item dictionary management unit 320 makes this determination depending on whether an input has been made to the input receiving unit 991 on the environment setting screen 990 shown in FIG.

[0058] In S814, the item dictionary management unit 320 sets the triggered repository definition to a dictionary reference state. More specifically, the item dictionary management unit 320 displays a display item 1421 indicating that the item dictionary is in a reference state on the definition editing screen 1420.

[0059] FIG. 9 shows an example of a display screen when adding an entry to an item dictionary file.

[0060] The context menu screen 900 is a screen for adding entries to the dictionary. 901 is an add button. An entry is added in response to selecting the add button 901 from the context menu screen 900 displayed by the added item dictionary edit display unit 423. After the entry is added, the XML of the item dictionary becomes the state shown in 920. The edit screen 910 is an operation screen for displaying entries and their corresponding definitions and for editing them. In the entry list display unit 911, each entry is displayed in an identifiable manner.

[0061] Fig. 10 is an example of a screen when adding a single item to a dictionary entry. Adding a single item to a dictionary entry is performed by operating the editing screen 940 displayed by the item dictionary editing display unit 423. XML data 950 is the XML data after the addition. Note that the XML data 920 in Fig. 9 is the XML data before the addition. Dictionary items are managed in the item dictionary storage unit 421 as value data, data model item data, and input / output item data, and are managed so that they are unique for each definition type and definition target.

[0062] 11 shows an example of a screen used when adding multiple items to a dictionary entry all at once. This addition operation is preferably performed when a definition file already exists in the repository and the definitions of that definition file are to be registered all at once in the item dictionary. The item dictionary management unit 320 displays an edit screen 980 in response to the selection of 961 or 962 on a context menu screen 960. It is also possible to set the items to a reference state at the same time as registration using the environment setting screen 990. The definition structure display unit 412 displays a definition tree 970.

[0063] Here, the area where the definition tree 970 displayed by the definition structure display unit 412 is displayed is referred to as a first display area, and the area where the editing screen 980 is displayed is referred to as a second display area.

[0064] The editing screen 980 includes a plurality of reception areas (981, 982, 983) as a second display area. The reception area 981 is a display area that displays a list of entries corresponding to the category selected in the reception area 982 (entry list reception section). The reception area 982 is a display area that displays a list of categories (category list reception section). The reception area 983 is a display area that displays definition information for the selected entry (definition information section).

[0065] Here, an operation for registering definitions of definition files in a batch in the item dictionary will be described with reference to FIG. 11 . The user can drag and drop display items representing data model item definitions or input item definitions displayed in the definition tree 970 onto the entry list display section 981 of the editing screen 980. This drag-and-drop operation allows definition information files to be registered in a batch in the item dictionary. In other words, the item dictionary management unit 320 manages definition files corresponding to display items in response to the drag-and-drop operation. The item dictionary management unit 320 manages definition files in different ways depending on which of the multiple reception areas the drag-and-drop operation was performed on. Specifically, when a definition file is dragged and dropped from the definition tree 970 to reception area 982, an entry is added to the category of the drop destination. When a definition file is dragged and dropped from the definition tree 970 to reception area 983, definition information is added to the entry of the drop destination.

[0066] In this way, the contents of the definition file can be easily set in the item dictionary in response to a drag-and-drop operation. Also, the usability can be improved by switching the setting contents depending on the drop destination of the drag-and-drop operation.

[0067] FIG. 12 shows the flow when a registered item dictionary is reflected in a repository definition.

[0068] In S1200, the item dictionary reference command unit 330 receives a dictionary reference event in response to selection of a dictionary reference item 1301, which is one of the items on a context menu screen 1300 displayed by the item dictionary edit display unit 423. Alternatively, the item dictionary reference command unit 330 receives a dictionary reference event in response to selection of a dictionary reference item 1321 from the item dictionary list screen 1320.

[0069] In S1210, the transmitting unit 431 of the item dictionary reference command unit 330 calls the edit screen 1401, and the item dictionary selection display unit 422 displays the edit screen 1401.

[0070] In S1220, the item dictionary management unit 320 sets a selected entry from among the entries displayed in the entry list display portion 1401 of the editing screen 1400 as the entry to be reflected when the button 1402 is pressed. The user can select the entry to be reflected from the entry list display portion 1401.

[0071] In S1221, the item dictionary reference command unit 330 determines whether or not the event is reflected to a single entity. In S1230, if the event is a dictionary reference event caused by the dictionary reference item 1321, the item dictionary reference command unit 330 determines that the event is reflected to a single entity, and sets the triggered item to a dictionary reference state. In this case, the dictionary reference item 1321 is changed to the display mode indicated by the dictionary reference item 1421. In this embodiment, the color of the dictionary reference item is changed, but this is not limited to this, and other identifiable display modes such as size, shape, pattern, etc. may also be included.

[0072] The XML data for the repository definition information is changed from 1310 to 1410. Also, the repository definition information is managed by the state of the dictionary item key, not by the value of the dictionary item. This means that when the dictionary value is changed, the change is propagated to all items that reference the same dictionary item key.

[0073] The following describes the flow of the item dictionary reference command unit 330 when it is determined in S1221 that the change is not to be reflected to a single item. Specifically, when a dictionary reference event is received from the context menu 1301, the process proceeds to S1240, where a batch reference process is performed on multiple dictionary item keys registered in the entry.

[0074] 13 shows a screen used when a registered item dictionary is reflected in a repository definition. This is a context menu screen 1300 displayed by the item dictionary edit display unit 423. The context menu screen 1300 includes a dictionary reference item 1301.

[0075] The XML data 1310 is the XML data before the repository definition is reflected.

[0076] The item dictionary list screen 1320 is a screen that lists item dictionaries. The item dictionary list screen 1320 includes a dictionary reference item 1321 that indicates whether the contents of the item dictionary are reflected in the repository definition. The dictionary reference item 1321 is a display item that indicates that the contents are not reflected in the repository definition.

[0077] 14 shows a screen used when reflecting a registered item dictionary in a repository definition. An editing screen 1400 includes an entry list display section 1401 and a button 1402. An entry displayed in the entry list display section 1401 can be selected. When the button 1402 is pressed, the selected entry becomes the target for reflection. The user can select the entry to be reflected from the entry list display section 1401.

[0078] XML data 1410 is the XML data after the repository definition has been reflected.

[0079] The item dictionary list screen 1420 is a screen that lists item dictionaries. The item dictionary list screen 1420 includes a dictionary reference item 1421 that indicates whether the contents of the item dictionary are reflected in the repository definition. The dictionary reference item 1421 is a display item that indicates that the contents are reflected in the repository definition.

[0080] FIG. 15 shows the control flow for updating the contents of dictionary entries and dictionary items.

[0081] In S1500, the item dictionary management unit 320 receives an event to open an edit screen in response to a user operation.

[0082] In S1510, the item dictionary edit display unit 423 displays the edit screen 940. In S1520, the item dictionary edit display unit 423 receives an entry selection event for an entry displayed in the entry list display unit 911.

[0083] In S1530, if the selected entry has been edited, the item dictionary management unit 320 receives an edit event.

[0084] In S1540, the item dictionary management unit 320 receives a dictionary item key selection event when the value of the dictionary item key is to be edited.

[0085] In S1550, if a value is to be edited, the item dictionary management unit 320 receives an edit event. In S1560, the item dictionary management unit 320 stores the edited item dictionary in the item dictionary storage unit 421 and finalizes the changes.

[0086] Figure 16 shows the flow of generating a web application.

[0087] In S1600, the repository definition analysis unit 441 acquires the application definition 401.

[0088] In S1610, the repository definition analysis unit 441 acquires the data model definition 403 included in the application acquired in S1600.

[0089] In S1620, the repository definition analysis unit 441 acquires the items of the data model definition 403.

[0090] In S1630, the repository definition analysis unit 441 determines whether or not the acquired item definition includes a dictionary reference. If the repository definition analysis unit 441 determines that the acquired item definition includes a dictionary reference, it executes the process of S1640.

[0091] In S1640, the repository definition analysis unit 441 acquires dictionary values ​​based on the item dictionary reference information 405. The repository definition analysis unit 441 repeats this process for the number of items in the data model definition 403, and then proceeds to S1650.

[0092] In S1650, the repository definition analysis unit 441 acquires the input / output definition 402 belonging to the application acquired in S1600.

[0093] In S1660, the repository definition analysis unit 441 acquires the items of the input / output definition 402.

[0094] In S1670, it is determined whether or not the item definition acquired in S1660 includes a dictionary reference. If the repository definition analysis unit 441 determines that the acquired item definition includes a dictionary reference, it executes the process of S1680.

[0095] In S1680, the repository definition analysis unit 441 acquires dictionary values ​​based on the item dictionary reference information 405. After repeating this process for the number of items in the input / output definition 403, the process proceeds to S1690. Next, in S1690, the repository definition analysis unit 441 acquires the business process definition 404 and database definition 406 belonging to the application acquired in S1600.

[0096] In S1700, the Web application code generation unit 442 receives the results of the repository definition analysis unit 441 and generates program code.

[0097] In S1710, the source code compiling unit 445 performs compilation to generate an application.

[0098] In the above-described embodiment, the programming development device (information processing device) uses repository definition unit 300 to manage input / output definition information that defines items to be input to a Web application screen and items to be output to the Web application screen (input / output definition management means).The programming development device then uses item dictionary management unit 320 to manage the correspondence between one or more items (entries) and the predetermined definition information corresponding to those items (item dictionary management means).Furthermore, the programming development device uses Web application generation unit 340 to generate a program using the input / output definition information managed by the input / output definition management means and the correspondence managed by the item dictionary management means (program generation means).

[0099] This makes it possible to generate a program used in a Web application by applying items that are common among multiple definition files.

[0100] Furthermore, by managing entries and predetermined definition information in the item dictionary management means, it is possible to prevent different definitions for the same keyword or the setting of different keywords with the same meaning, which is more effective when a group of multiple users develops a common application.

[0101] Furthermore, the contents managed by the item dictionary management means are displayed in a list, and can be easily edited, checked, deleted, etc. Therefore, if a change occurs to a definition, the change can be easily made, which contributes to reducing the number of steps required for program development.

[0102] Although the present invention has been described above using the above-mentioned embodiment, the present invention is not limited to the above-mentioned embodiment. In particular, the functions of the program development device 101 are not limited to the present embodiment, and may be processed in cooperation with multiple program development devices. Furthermore, the program development device may be a server used in an on-premise environment, or may be a virtual server in a cloud service.

[0103] The present invention can be embodied, for example, as a system, device, method, program, or storage medium, and specifically, may be applied to a system consisting of multiple devices, or may be applied to an apparatus consisting of a single device.

[0104] The present embodiment can also be realized by a computer or a control computer executing a program (computer program). Also, means for supplying a program to a computer, such as a computer-readable recording medium such as a CD-ROM on which such a program is recorded, or a transmission medium such as the Internet for transmitting such a program, can also be applied as an embodiment. The above-mentioned program can also be applied as an embodiment. The above-mentioned program, recording medium, transmission medium, and program product are included in the scope of the present invention.

[0105] Although the present invention has been described in detail above based on the embodiments, it is not limited to the specific embodiments, and various forms within the scope of the invention are also included in the scope of the present invention as long as they do not deviate from the gist of the invention. Furthermore, the above-described embodiment is merely an example, and inventions that can be easily imagined from the above-described embodiment are also included in the scope of the present invention. [Explanation of symbols]

[0106] 101 Program Development Device 300 Repository definition section 310 Repository Definition Editorial Department 320 Item Dictionary Management Unit 340 Web Application Generation Unit

Claims

1. a management means for managing definition information having a key and at least one value, which defines items used in constructing an application; a registration means for registering definition information managed by the management means in an item dictionary; a construction means for constructing an application by using, when a value of definition information relating to an item registered in the item dictionary is changed, the changed value as a value of definition information referencing the same key; An information processing system comprising:

2. The registering means registers definition information relating to an item corresponding to an object in an item dictionary in response to a user's operation on the object indicating an item of definition information managed by the managing means.

2. The information processing system according to claim 1, wherein:

3. The registration means registers definition information relating to an item corresponding to the object in an item dictionary by performing an addition operation from a first display area in which the object is displayed to a second display area different from the first display area.

3. The information processing system according to claim 2, wherein:

4. The registration means registers definition information relating to items corresponding to the plurality of objects in an item dictionary in a lump by an addition operation of the plurality of objects.

4. The information processing system according to claim 3, wherein:

5. The adding operation includes a drag-and-drop operation.

5. The information processing system according to claim 3 or 4, wherein:

6. The definition information relating to the items managed by the management means includes at least one of definition information of input / output items and definition information of data model items.

6. The information processing system according to claim 1, wherein:

7. The value includes at least one of the attribute, data type, name, and number of digits of the definition information related to the item to be registered.

7. The information processing system according to claim 1, wherein:

8. a reflecting means for reflecting definition information relating to the items registered in the item dictionary in preset definition information; The system further comprises a display control means for identifiably displaying the definition information reflected by the reflection means.

8. The information processing system according to claim 1, wherein:

9. The application is a web application.

9. The information processing system according to claim 1, wherein:

10. a management step of managing definition information having a key and at least one value that defines items used in constructing an application; a registration step of registering the definition information managed in the management step in an item dictionary; a construction step of constructing an application by using, when a value of definition information relating to an item registered in the item dictionary is changed, the changed value as a value of definition information referencing the same key; 1. A method for controlling an information processing system, comprising:

11. 10. A program for causing at least one computer to function as each of the means of the information processing system according to any one of claims 1 to 9.

Images