Business support apparatus, business support method, and business support program

Abstract

To help developers to create control item descriptions for application program screens, thereby reducing the burden on the developers.SOLUTION: An acquisition unit refers to control list information including identification names and types of controls for inputting components configuring a screen, and acquires at least identification names and types corresponding to the controls included in a designed screen from control list information. An item description data generating unit generates item description data, which is description data for each control included in the designed screen, including the acquired identification name, type, and input fields for the description of each control. This allows the creation of the item description data to be substantially automated, supporting the task of creating item descriptions and reducing the burden on developers.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a business support device, a business support method, and a business support program. [Background technology]

[0002] Patent Document 1 (Japanese Patent No. 2988911) discloses an automatic program generation device that efficiently generates a screen program and automatically generates logic and documents other than the screen display that constitutes the screen application.

[0003] In this automatic program generation device, a layout group generation unit generates layout groups from multiple specified data items and defines attribute information for each layout group. An intra-group layout definition unit defines the layout of each data item within the layout group. The layout generation unit also determines the screen layout by arranging the layout groups on the screen. The program generation unit generates a screen program by referencing information about the determined screen layout, attribute information for the arranged layout groups and the data items that make them up, etc. Furthermore, if communication processing is involved, the program generation unit automatically generates communication logic after allowing functions and function arguments registered in the logic file to be set from the screen. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 2988911 Summary of the Invention [Problem to be solved by the invention]

[0005] When developing an application program, in addition to creating the application program, manuals (item manuals) for the controls that are input components that make up the screen are often created.

[0006] However, there was a problem in that the task of creating this item description manual was a burden on the developer.

[0007] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that can support the creation of item descriptions for controls on the screen of an application program, thereby reducing the burden on developers. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the objectives, the business support device of the present invention has an acquisition unit that references control list information including the identification names and types of controls that are input components that make up the screen, and acquires at least the identification names and types corresponding to the controls included in the designed screen from the control list information, and an item description data generation unit that generates item description data that is description data for each control included in the designed screen, including the acquired identification names, types, and input fields for the explanatory documents of each control.

[0009] In addition, in order to solve the above-mentioned problems and achieve the objectives, the business support method of the present invention includes an acquisition step in which an acquisition unit refers to control list information including the identification names and types of controls that are input components that make up the screen, and acquires at least the identification names and types corresponding to the controls included in the designed screen from the control list information, and an item description data generation step in which an item description data generation unit generates item description data that is description data for each control included in the designed screen, including the acquired identification names, types, and input fields for the explanatory documents of each control.

[0010] In addition, in order to solve the above-mentioned problems and achieve the objective, the business support program of the present invention causes a computer to function as an acquisition unit that references control list information including the identification names and types of controls that are input components that make up the screen, and acquires from the control list information at least the identification names and types corresponding to the controls included in the designed screen, and an item description data generation unit that generates item description data that is description data for each control included in the designed screen, including the acquired identification names, types, and input fields for the explanatory documents of each control. [Effects of the Invention]

[0011] The present invention can reduce the burden on developers by supporting the creation of item descriptions for controls on the screen of an application program. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing the system configuration of a Web application system provided with a development terminal device according to an embodiment, and the hardware configuration of the development terminal device according to an embodiment. [Figure 2] FIG. 2 is a diagram showing an example of the layout editing screen. [Figure 3] FIG. 3 is a diagram showing control list information for control IDs ID0 to ID22. [Figure 4] FIG. 4 is a diagram showing control list information for control IDs ID23 to ID47. [Figure 5] FIG. 5 is a diagram showing an example of a property setting screen for a control. [Figure 6] FIG. 6 is a diagram showing an example of property information set for each control. [Figure 7] FIG. 7 is a diagram showing an example of a logic flow setting screen. [Figure 8] FIG. 8 is a diagram showing an example of various definitions set via the logic flow setting screen. [Figure 9]FIG. 9 is a diagram illustrating an example of a conditional branch setting for a logic flow. [Figure 10] FIG. 10 is a diagram showing an example of the action setting screen. [Figure 11] FIG. 11 is a diagram showing an example of a return value set in a control via the action setting screen. [Figure 12] FIG. 12 is a diagram showing an example of the condition setting screen. [Figure 13] FIG. 13 is a diagram showing an example of the condition setting data. [Figure 14] FIG. 14 is a diagram showing an example of items and operators that can be specified on the right and left sides of an expression that is a condition of a business rule. [Figure 15] FIG. 15 is a diagram showing an example of a business rule setting screen. [Figure 16] FIG. 16 is a diagram illustrating an example of business rule setting data. [Figure 17] FIG. 17 is a diagram showing the "caption label" and "column cell" controls extracted as "heading controls" from the control list information. [Figure 18] FIG. 18 is a diagram showing a list of "header controls" extracted from the control list information. [Figure 19] FIG. 19 is a diagram showing how the control of the "text box" closest to the "caption label" extracted as the "heading control" is detected. [Figure 20] FIG. 20 is a diagram showing how the "text box" closest to the "caption label" of "caption label construction No." is detected. [Figure 21] FIG. 21 is a diagram showing an example of control list information of controls arranged in the detail area. [Figure 22] FIG. 22 is a diagram showing how the control of a "cell" in the same row and column is detected based on the row and column in which the "column cell" is located. [Figure 23]FIG. 23 shows the state in which the properties of a control are displayed as an item description. [Figure 24] FIG. 24 is a diagram summarizing how properties are detected. [Figure 25] FIG. 25 is a diagram for explaining the contents to be input for the items "Specify" and "Display only." [Figure 26] FIG. 26 is a diagram showing an example of item description data automatically created by the development terminal device according to the embodiment. [Figure 27] FIG. 27 is a diagram showing an example of an editing screen for item description data. [Figure 28] FIG. 28 is a diagram for explaining additional editing of item description data. [Figure 29] FIG. 29 is a diagram for explaining the exclusion editing of the item description data. [Figure 30] FIG. 30 is a diagram showing an example of the editing screen after addition editing and subtraction editing have been performed. [Figure 31] FIG. 31 shows an example of an item description page in which addition editing and subtraction editing have been reflected. DETAILED DESCRIPTION OF THE INVENTION

[0013] A development terminal device according to an embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the following embodiment.

[0014] (System Configuration) First, Fig. 1 shows a Web (World Wide Web) application system to which a development terminal device 1 according to an embodiment is applied. As shown in Fig. 1, the Web application system is configured by connecting the development terminal device 1 according to an embodiment, a server device 51, and a user terminal device 52 via a network 53.

[0015] The network 53 may be, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0016] The development terminal device 1 creates a Web application program (hereinafter simply referred to as an application program) to be provided to the user terminal device 52 and an item description of the controls that make up the screen of the application program, and transmits these to the server device 51 via the network 53.

[0017] The server device 51 stores the application programs and control item descriptions developed on the development terminal device 1 in the database 50. The server device 51 also executes the application programs stored in the database 50 and provides the application program screens and functions as well as the control item descriptions to the user terminal device 52 via the network 53.

[0018] The user terminal device 52 uses the screen and functions of the application program provided by the server device 51. If the user is unclear about how to input items on the provided screen or what to input, the user receives an item explanation manual from the server device 51 to help the user understand how to input items and what to input.

[0019] (Hardware configuration of the development terminal device) As shown in FIG. 1, the development terminal device 1 comprises a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function. The communication interface unit 4 is connected to a network, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0020] The storage unit 2 may be, for example, a read-only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD). The storage unit 2 stores a development support program (an example of a support program) that supports the creation of item descriptions for controls that constitute the screen of an application program, thereby reducing the burden on developers. This development support program supports the development of application programs that mainly use GUI (Graphical User Interface) operations without using source code, such as low-code or no-code.

[0021] The storage unit 2 also includes a control list information storage unit 11, an item description data storage unit 12, and a screen layout data storage unit 13, each of which is a storage area.

[0022] The control list information storage unit 11 stores control list information including the control identification name, the control type, the specified caption name, and the like, stored for each control.

[0023] The item description data storage unit 12 stores item description data for controls that constitute the screen of an application program, which is automatically created based on the control list information.

[0024] The screen layout data storage unit 13 stores screen layout data that indicates the screen configuration of the application program screen and the controls that configure this screen.

[0025] (Functional configuration of the developed terminal device) Next, the control unit 3 executes the development work support program stored in the memory unit 2, and thereby functions as a display control unit 21, an acquisition unit 22, a screen layout construction unit 23, an item description data generation unit 24, an editing control unit 25, and a communication control unit 26, as shown in FIG. 1.

[0026] The display control unit 21 displays, via the output device 7, the screen of the application program under development, the screen of the developed application program, and item manuals of the controls that make up the screen.

[0027] The acquisition unit 22 refers to control list information including the identification names and types of controls, which are input components that make up the screen, and acquires from the control list information at least the identification names and types corresponding to the controls included in the designed screen.

[0028] The screen layout construction unit 23 stores in the screen layout data storage unit 13 the screen layout data of the screen of the application program constructed by the developer with the desired controls arranged thereon.

[0029] The item description data generating unit 24 generates item description data, which is description data for each control included in the designed screen, including the identification name, type, and input fields for the explanatory text of each control acquired by the acquiring unit 22. Then, the item description data generating unit 24 stores the generated item description data in the item description data storage unit 12.

[0030] The control list information also includes the identification names and types of the auxiliary controls attached to the main control (see FIGS. 3 and 4). The acquisition unit 22 acquires the identification names and types of the auxiliary controls attached to the main control, as well as the identification names and types of the main control, from the control list information (see FIG. 19).

[0031] The item description data generating unit 24 generates item description data including input fields for the identification names, types, and explanatory text of the main control and auxiliary controls.

[0032] In addition, the control list information includes, for each control and each attached control, mandatory information indicating whether the control is a mandatory control, initial value set information indicating whether the control is a control that is treated with an initial value set, specification information indicating whether at least one item or multiple items can be specified for the control, and display-only information indicating that the control is a display-only control (see Figure 24).

[0033] The acquisition unit 22 acquires the identification names and types of the controls and auxiliary controls, as well as the required information, initial value set information, designation information, and display-only information from the control list information.

[0034] The item description data generating unit 24 generates item description data including required information, initial value set information, designated information, and display-only information, along with input fields for the identification name, type, and description of the control and auxiliary control (see FIG. 26).

[0035] When editing of the item description data displayed on the display unit (output device 7) is designated, the edit control unit 25 puts the input field for the description of each control into a state in which the description can be input.

[0036] The item description data generating unit 24 generates item description data including the explanatory text, the identification name, and the type input in the input fields, and stores the data in the item description data storage unit 12 .

[0037] Furthermore, the above-mentioned control list information includes, for each control, at least, an item attribute indicating characters, symbols, or numbers that can be used when inputting data to the control, and the number of digits that can be input.

[0038] The acquiring unit 22 acquires, from the control list information, the item attribute indicating a character, symbol, or numeric value and the number of digits that can be entered, along with the identification name and type.

[0039] The item description data generation unit 24 generates item description data including the identification name, type, and input fields for each control's description, as well as item attributes indicating characters, symbols, and numbers and the number of digits that can be entered, and stores this in the item description data storage unit 12.

[0040] In addition, when the addition of a control is specified, the acquisition unit 22 acquires the identification name, type, input field for explanatory text, item attributes indicating characters, symbols or numbers, and the number of digits that can be entered corresponding to the added control from the control list information.

[0041] The editing control unit 25 adds and inserts the identification name, type, input field for the explanatory document, item attributes indicating characters, symbols or numbers, and the number of digits that can be entered corresponding to the added control into the item description data displayed on the display unit (output device 7).

[0042] The item description data generation unit 24 generates item description data that includes the identification name, type, input field for explanatory text, item attributes indicating characters, symbols or numbers, and the number of digits that can be entered corresponding to the additionally inserted control, as well as information indicating that it is an additionally inserted control (see Figure 30), and stores the data in the item description data storage unit 12.

[0043] In addition, the editing control unit 25 adds information indicating that the control has been excluded (see Figure 30) to the item description data of the control that has been specified as excluded from the controls displayed on the display unit (output device 7).

[0044] In this case, the item description data generating unit 24 generates item description data from which the excluded control has been deleted.

[0045] The item description data edited in this manner is stored in the item description data storage unit 12, and is transmitted by the communication control unit 26 to the server device 51 via the network 53, where it is stored in the database 50. The item description data stored in the database 50 is then provided to the user terminal device 52 by the server device 51. Based on the provided item description data, the user recognizes how to input items on the screen of the application program and the input contents, and performs operations or inputs desired information.

[0046] [Creating item instructions] Next, we will explain the operation of creating item descriptions for controls that make up the screen of an application program in the development terminal device 1 of this embodiment. The development terminal device 1 of this embodiment creates an item description by performing the following steps in order: "screen editing process" → "automatic creation process of item description based on edited screen layout" → "item description editing process."

[0047] The control unit 3 creates the item description by functioning as the display control unit 21 to the communication control unit 26 based on the development work support program. In this example, the display control unit 21 to the communication control unit 26 are described as being realized by software using the development work support program, but some or all of the display control unit 21 to the communication control unit 26 may also be realized by hardware. In either case, the same effects as those described below can be obtained.

[0048] [Screen editing behavior] (Layout editing operation) First, the screen editing process of an application program to be developed will be described. In this case, the developer performs a designation operation to display a layout editing screen. When this designation operation is performed, the display control unit 21 displays the layout editing screen shown in FIG. 2 via the output device 7. As shown in FIG. 2, the layout editing screen includes a display area for a list of controls and an area for arranging the controls. The developer selects a desired control from the display area for the list of controls, drags it, and drops it into the control arrangement area, thereby arranging the desired control at a desired position on the screen.

[0049] The example in Figure 2 shows a layout where controls called "cards," on which one or more controls can be placed, are arranged one above the other. The bottom "card" has a control called a "spread," which has multiple "column cell" controls. The top "card" has controls such as a "caption," "label," "text box," and "button."

[0050] Figures 3 and 4 show control list information indicating the type and relationship of each control arranged in this way. As shown in Figures 3 and 4, the control list information includes the control identification number (control ID), identification name, type (classification), caption name, and child element ID list of each control. Figure 3 shows control list information for control IDs ID0 to ID22. Figure 4 shows control list information for control IDs ID23 to ID47.

[0051] As shown in Figure 3, the page control with control ID ID0 has the following controls associated as child elements: command bar with ID1, output condition area with ID2, and card details with ID38. The output condition area with ID2 has the following controls associated as child elements: caption label construction no. with ID03 to radio group payment destination with ID8, range panel payment destination with ID11, search button payment destination with ID16 to check group output target with ID19, caption label issue category with ID23, radio group issue category with ID24, and check box official issue with ID27 to label sender with ID37.

[0052] (Control property setting behavior) Next, the developer selects the placed control and sets its properties, as exemplified in FIG. 5. Specifically, when a control is selected, the display control unit 21 displays a property setting screen via the output device 7, as exemplified in FIG. 5. The example in FIG. 5 is a property setting screen for the "Text Construction No." control. The developer sets properties such as "Required or not," "Can alphabets be input?", "Can numbers be input?", "Can symbols be input?", "Can half-width katakana be input?", "Can full-width characters be input?", and "Desired number of input characters" via this property setting screen.

[0053] When the properties are set in this way, the screen layout construction unit 23 generates property information set for each control as shown in FIG. 6, includes it in the screen layout data described later, and stores it in the screen layout data storage unit 13.

[0054] The example in Figure 6 shows that the text box control for the text Construction No. with ID4 is a required control, and that the properties that allow input of 12 digits of alphabetic characters and numbers have been set (required: true, alphabetic characters allowed: true, numeric characters allowed: true, number of digits: 12). Also, the example in Figure 6 shows that the text box control for the text Sending Origin with ID33 has the properties that allow input of 1 digit of alphabetic characters, numbers, kana characters, or symbols (alphabetic characters allowed: true, numeric characters allowed: true, kana characters allowed: true, symbol characters allowed: true, number of digits: 1).

[0055] (Logic flow setting operation) Next, the developer performs a designation operation to display the logic flow setting screen. When this designation operation is performed, the display control unit 21 displays the logic flow setting screen shown in FIG. 7 via the output device 7. A list of actions to be set is displayed on this logic flow setting screen. The developer selects and sets a desired action for an event from this list of actions. The example in FIG. 7 is an example in which an action (API call) that calls an application program interface is set for a screen activation event.

[0056] When the desired action for the event is set in this manner, the screen layout construction unit 23 generates an event allocation definition as illustrated in FIG. 8(a), a logic flow definition as illustrated in FIG. 8(b), an action definition as illustrated in FIG. 8(c), and a flow definition as illustrated in FIG. 8(d), and stores them in the screen layout data storage unit 13 together with the screen layout data described later.

[0057] In addition to the screen activation event shown in Figure 8(b), other events include a "click" event when a button is pressed and a "verification process" event when an item is exited. However, if a value is set in an item by a screen activation event, it is treated as the initial value set.

[0058] Another action is the "Screen Update" action, which sets a value to an item. In this case, a fixed value or a system variable (such as the current date) is set. Also, when a value is set in the "Screen Update" action, it is treated as an initial value set, just as described above.

[0059] Also, within the logic flow, conditional branching can be set as shown in Figure 9, but regardless of whether or not there is a conditional branching, if an item value is set on the logic flow, it will be treated as an initial value set.

[0060] (Action setting operation) Next, the developer performs a designation operation to display the action setting screen. When this designation operation is performed, the display control unit 21 displays the action setting screen shown in Fig. 10 via the output device 7. The developer selects a desired API via this action setting screen and sets a return value for the control as shown in Fig. 11.

[0061] The examples in Figures 10 and 11 are examples in which the return values ​​of "Construction No.," "Construction NOSEQ (Construction Number Sequence)," "Payee," and "Sender Designation" are set for each control of the API in the initial value set. As will be described in more detail later, the item description automatically generated by the development terminal device 1 of the embodiment has an "Initial" field that indicates whether or not a return value is set for the API in the initial value set. For controls for which a return value is set, the information "○" is added to this "Initial" field. Therefore, as will be described later, the information "○" is added to the "Initial" field for each of the controls in the item description: "Construction No.," "Construction NOSEQ (Construction Number Sequence)," "Payee," and "Sender Designation."

[0062] (Condition setting operation) Next, the developer specifies the display of the condition setting screen. When this specification is performed, the display control unit 21 displays the condition setting screen shown in FIG. 12 via the output device 7. The developer sets an expression that will be the condition of the business rule via this condition setting screen. The business rule is the desired control processing when the condition shown in the following expression is met.

[0063] 12 and 13 show that the sender address is set to a fixed value (4), indicating that the address is "other than the sender address." When such a condition is set, the screen layout construction unit 23 generates condition setting data that associates the condition ID, name, and expression, as shown in the example of Fig. 13, and stores the data in the screen layout data storage unit 13 together with the screen layout data described later.

[0064] Also, Fig. 14(a) shows the condition "whether there is an error in the control." Fig. 14(b) shows the items that can be set on the right and left sides of such a conditional expression. Also, Fig. 14(c) shows the operators that can be set for the conditional expression.

[0065] (Business rule setting behavior) Next, the developer specifies the display of the business rule setting screen. When this specification is performed, the display control unit 21 displays the business rule setting screen shown in Fig. 15 via the output device 7. The developer selects a desired control via this business rule setting screen and selects the processing of the selected control when the conditions of the above-mentioned formula are met.

[0066] The desired control processing can be selected from among "lock item," "make item required," and "hide item." Note that this business rule can be set for controls such as normal text boxes and column cells, but cannot be set for cells of detail controls.

[0067] When such business rules are set, when an application program is executed, it is evaluated whether the conditions set in the condition settings are met depending on screen operations, etc., and the control selected in the business rule settings executes the selected processing.

[0068] As will be described in more detail later, the item description automatically generated by the development terminal device 1 of this embodiment has a "Required" item that indicates whether the control is a required control. However, the state of a control for which such a business rule is set changes depending on the conditions described above. For this reason, a "black triangle icon" is added to the "Required" item in the item description for a control for which a business rule is set, indicating that the state changes depending on the conditions described above.

[0069] As mentioned above, the business rule settings also allow you to set business rules for "locking items" and "hiding items." Therefore, it is also possible to add "read-only (locked)" and "hidden items" to the item description. In this case, if a business rule for "locking items" or "hidden items" is set for a control, the information for "read-only (locked)" or "hidden items" will be displayed as a black triangle icon. Furthermore, if a "fixed value" is set in the "control property settings" described above and "locked" or "hidden" is selected in this state, the information for "read-only (locked)" or "hidden items" will be displayed as a circle.

[0070] When the business rule is set in this manner, the screen layout construction unit 23 generates business rule setting data that associates the business rule ID, processing content, control ID of the control for which the business rule is set, and condition ID, as illustrated in Figure 16, and stores the data in the screen layout data storage unit 13 together with the screen layout data described later.

[0071] [Automatic creation of item instructions based on edited screen layout] Next, when the screen of the application program is designed and the screen layout data including the controls, layout, properties, conditions, business rules, etc. that make up the screen is stored in the screen layout data storage unit 13, it becomes possible to automatically create item descriptions for the controls that make up the screen.

[0072] (Extraction of headings) That is, when a developer specifies the display of a desired screen, the display control unit 21 reads out the screen layout data of the specified screen stored in the screen layout data storage unit 13. Then, the display control unit 21 displays the specified screen via the output device 7 based on the read-out screen layout data.

[0073] Next, the developer specifies the creation of an item description for the displayed screen. When this specification is performed, the item description data generation unit 24 automatically creates an item description based on the screen layout data of the currently displayed screen and the control list information stored in the control list information storage unit 11 (see FIGS. 3 and 4).

[0074] Specifically, the item description data generation unit 24 first extracts "header controls," which are controls such as cards, spreads, caption labels, and column cells, from the control list information, as shown in bold in Fig. 17. For an explanation of controls such as cards, spreads, caption labels, and column cells, see Fig. 2.

[0075] Next, the item description data generation unit 24 generates a list of the extracted "headline control" items, as shown in Fig. 18. At this time, the item description data generation unit 24 treats card and spread items as "group control" items in the item description, and generates a list of "headline control" items so that the item names appear as white letters on a black background, as shown in Fig. 18, in other words, as black bars. This list of "headline control" items becomes the list of items in the item description.

[0076] (Selection of corresponding items) Next, the item description data generation unit 24 detects, from among the extracted header controls, controls whose control types (categories) are "caption labels" and "column cells." Then, the item description data generation unit 24 refers to the control list information, groups the controls by "caption label," and, as shown by the arrow in Fig. 19, detects the nearest "text box" control from among the "text box" controls listed next to that "caption label" in the order of control types listed in the control list information.

[0077] That is, in the example of Fig. 19, the item description data generating unit 24 detects the control of "Text Construction No." as the control of the "Text Box" closest to the control of the "Caption Label" of "Caption Label Construction No." Fig. 20 shows how the "Text Box" closest to the "Caption Label" of "Caption Label Construction No." is detected.

[0078] The item description data generation unit 24 also detects the "Text Payee Code Start" control as the "Text Box" control closest to the "Caption Label" control of "Caption Label Payee." Furthermore, the item description data generation unit 24 detects the "Text Order Form No." control as the "Text Box" control closest to the "Caption Label" control of "Caption Label Order Form No."

[0079] In addition, as shown in FIG. 19, if there is no "text box" control between a "caption label" and the next "caption label", the item description data generating unit 24 recognizes this as "no text box control."

[0080] Furthermore, for a control in a "column cell," the item description data generation unit 24 detects controls in cells in the "same row" and "same column." That is, FIG. 21 shows partial control list information for the details area in which spread controls are arranged on the screen shown in FIG. 2. As shown in FIG. 21, the control list information includes the identification name and type (classification) of each control, as well as information on the row and column in which the control is arranged. The number "1" in the row item shown in FIG. 21 indicates the "first row," and the number "1" in the column item indicates the "first column."

[0081] For example, in the case of a "column cell" control for "column publication date and time", since the control is located in the "first column" of the "first row", the item description data generation unit 24 detects the control for the "label cell publication date and time (text cell (date))" which is the control for the "cell" in the "first column" of the same "first row". Figure 22 shows how the text cell (date) for "label cell publication date and time", which is the "cell" in the "first column" of the same "first row", is detected for the "column cell" of this "column publication date and time".

[0082] Similarly, in the case of a control for a "column cell" of, for example, "column payment recipient code," since this control is located in the "second column" of the "first row," the item description data generation unit 24 detects the control for "label payment recipient code (text cell)," which is the control for the "cell" in the "second column" of the same "first row."

[0083] Similarly, in the case of a control for the "column cell" of, for example, "column payee name," since this control is located in the "third column" of the "first row," the item description data generation unit 24 detects the control for the "label payee name (label cell)," which is the control for the "cell" in the "third column" of the same "first row."

[0084] (Property detection) Next, based on the screen layout data stored in the screen layout data storage unit 13, the item description data generation unit 24 detects properties of each control constituting the screen, such as "whether it is required or not," "item attributes such as whether alphabetic characters and numbers can be input," "number of digits," "whether it is searchable," "whether it is set as a return value for the initial value set (initial)," and "specify" and "display only," which will be described later, as shown in FIG. 23.

[0085] Fig. 24 is a diagram summarizing the methods of detecting properties in a list. In Fig. 23 and Fig. 24, the item description data generating unit 24 assigns a number to each group control and adds the number to the item description data so that the number becomes a "consecutive number."

[0086] For "required" items, if there is an input field (text box) corresponding to the heading item, the item description data generation unit 24 adds attribute information of "●" (●) to the required item of that control. If there is no input field, the item description data generation unit 24 reflects the setting of the caption label. Also, if the required status changes depending on the business rule setting (if it changes depending on the conditions), the item description data generation unit 24 adds attribute information of a "black triangle icon" to the required item of that control.

[0087] As the "screen item name," the item description data generation unit 24 adds an arbitrary caption name entered by the developer to the item description data of the control. If no caption name is entered, the item description data generation unit 24 adds a default caption name to the item description data of the control.

[0088] For the "item attribute" item, the item description data generating unit 24 adds attribute information such as characters that can be entered into the input item (text box) corresponding to the heading item to the item description data of the control.

[0089] That is, as one example, the "item attributes" items include an "English" item indicating whether English characters can be input, a "Number" item indicating whether numerical values ​​can be input, a "Kana" item indicating whether kana characters can be input, a "Record" item indicating whether symbols can be input, a "Full" item indicating whether full-width characters can be input, and an "Other" item indicating whether numerical values, dates or times can be input.

[0090] The item description data generation unit 24 refers to the screen layout data and detects the properties set for the control, as explained with reference to Fig. 5. Then, the item description data generation unit 24 adds additional information, etc. to the item description data for the control based on the detected properties.

[0091] The "Number of digits" field indicates the number of digits that can be entered, and in the case of a numeric value, it is expressed as an integer or decimal. The item description data generation unit 24 references the screen layout data and detects the number of digits set for the control, as described with reference to FIG. 5. Then, the item description data generation unit 24 adds the number of digits to the item description data for the control based on the detected number of digits.

[0092] The "Search" item indicates whether or not a search button is present. The item description data generation unit 24 refers to the screen layout data and detects controls that have a search button among the group of controls (multiple controls grouped together in parentheses in Figure 19) that are grouped by heading item. Then, the item description data generation unit 24 adds search button information of "○" to the item description data of the control that has a search button.

[0093] The "Initial" item indicates whether or not an initial value has been set for the input item (text box) corresponding to the heading item (whether or not an initial value has been set for the item attribute or the activation event). The item description data generation unit 24 refers to the screen layout data, detects whether or not an initial value has been set for the item attribute or the activation event (see FIG. 10), and adds the initial information "〇" to the item description data for that control based on the detection result.

[0094] The "Specify" item indicates the type of input in the group of controls grouped by heading (see Figure 19). The "Display only" item is added to the control that cannot be used to input labels, etc., and is only for display in the group of controls grouped by heading (see Figure 19).

[0095] Specifically, for a "Specify" item, if a range panel exists as shown in Figure 25(a) and the same group contains multiple select boxes (select boxes in which multiple options can be selected simultaneously) as shown in Figure 25(b), the item description data generation unit 24 adds "Range / Optional" designation information to the item description data for that control. On the other hand, if a range panel exists as shown in Figure 25(a) and the same group does not contain multiple select boxes as shown in Figure 25(c), the item description data generation unit 24 adds "Range Designation" designation information to the item description data for that control.

[0096] Furthermore, as shown in FIG. 25(d), when there are multiple select boxes or check groups, the item description data generating unit 24 adds designation information of "multiple selection" to the item description data of the control.

[0097] Furthermore, as shown in FIG. 25(e), if a radio group exists, the item description data generating unit 24 adds designation information of "single selection" to the item description data of the control.

[0098] Furthermore, as shown in FIG. 25(f), if a text box exists, the item description data generating unit 24 adds designation information of "single designation" to the item description data of the control.

[0099] In addition, in cases other than those shown in Figures 25(a) to 25(f), the item description data generation unit 24 adds designation information of "blank" to the item description data of that control, and adds display information of "◯" to the "display only" item.

[0100] Next, the item description data generation unit 24 generates item description data to which is added a list of "headline control" items shown in Fig. 18, attribute information of each control explained using Figs. 19 to 25, and an input field for explanations or notes of each control. This makes it possible to automatically create an item description corresponding to the screen configuration of an application program, as exemplified in Fig. 26. This item description data is stored in the item description data storage unit 12 shown in Fig. 1, and is displayed by the display control unit 21 via the output device 7.

[0101] When the developer completes an application program, he or she transmits the application program and the item description data stored in item description data storage unit 12 to server device 51 shown in Fig. 1 at the desired timing. When this transmission operation is performed, communication control unit 26 reads out the item description data stored in item description data storage unit 12, and controls communication of communication interface unit 4 to transmit the application program and item description data to server device 51 via network 53.

[0102] The server device 51 stores (registers) the transmitted application program and item description data in the database 50. The application program stored in the database 50 is provided to each user of the user terminal device 52 as, for example, a Web application program (which may be an application program that the user downloads and uses). When a user is unsure of what to input or wants to know the function of a control, the item description data corresponding to the screen shown in FIG. 26 is read from the database 50 in response to a request from the user and provided to the user terminal device 52 of that user. This allows the user to recognize the input content or the function of a control.

[0103] (Editing of item description) Next, the developer can make desired edits to the item description data created in this way. That is, when the developer edits the item description data, the developer specifies the desired screen and specifies the edit. When this edit specification is made, the display control unit 21 displays an edit screen for the item description corresponding to the specified screen via the output device 7, based on the item description data stored in the item description data storage unit 12. An example of the edit screen is shown in FIG. 27.

[0104] The editing control unit 25 makes it possible to input desired characters, etc., into the input fields for "arbitrary screen item name (arbitrary caption name)" and "description" on the editing screen. The developer performs edits on the editing screen, such as inputting, changing, or deleting the "arbitrary screen item name (arbitrary caption name)". The developer also performs edits on the "description", such as inputting, changing, or deleting. After this editing, the developer operates the save button 61. The item description data generation unit 24 generates item description data including the edited "arbitrary caption name)" and "description", etc., and stores it in the item description data storage unit 12. This makes it possible to edit the "arbitrary caption name" and "description", etc., of the item description data.

[0105] 27, the display control unit 21 displays an add button 60, a save button 61, and a close button 62 on the edit screen together with a list of controls corresponding to the specified screen. The add button 60 is a button for specifying the addition of a desired item. The save button 61 is a button for storing (saving) the edited item description data in the item description data storage unit 12. The close button 62 is a button for specifying the non-display of the edit screen.

[0106] As an example, if there is one input item that is automatically identified for a heading control and a desired input item is to be added to this (to be displayed in addition to the item description), the developer operates the add button 60 to add the desired item.

[0107] That is, when the add button 60 is operated, the display control unit 21 displays a layout editing screen (see FIG. 2) having a configuration corresponding to the item description data of the currently displayed editing screen via the output device 7. The developer adds a desired control to a desired heading, as described with reference to FIG. 2.

[0108] Specifically, in the example of Figure 28(a), for the heading "Construction No.", one text box on the right side is output as an input item attribute, so the developer added and placed the control for "Construction No. SEQ" to the right of the text box. Also, the example of Figure 28(b) is an example where an independent control such as "Official Issue" has been added.

[0109] After adding the desired controls in this way, the developer operates the Confirm button (not shown) displayed on the layout editing screen. When this Confirm button is operated, the display control unit 21 returns the display screen to the editing screen shown in Fig. 27. At this time, the editing control unit 25 adds a new line corresponding to the added control and displays the item description, as shown in Fig. 30. The line to which the "added item" information (icon) shown in Fig. 30 has been added is the line corresponding to the control added by the developer.

[0110] Since the "arbitrary caption name" and "description" for the added item have not been entered, the input fields for "arbitrary caption name" and "description" are displayed as "blank" when the edited item instruction manual is displayed by the display control unit 21. The developer can also enter an "arbitrary caption name" or "description" for the added control.

[0111] Next, when the save button 61 on the editing screen is operated, the item description data generating unit 24 generates item description data to which the item description data of the added control has been added, and stores the data in the item description data storage unit 12.

[0112] If an input item added to the location of an existing heading control is not subject to selection of a corresponding item, the item description data generation unit 24 does not reflect it in the item description. If it is to be reflected in the item description, it is set as an added item on the layout editing screen described above. This causes it to be reflected in the item description.

[0113] It is also possible to exclude desired controls. For example, group controls, which divide the screen area, are displayed in the item description as white text on a line of black bars, as shown in Figure 29. Figure 29 shows an example in which the line "Card details of screen group" and the line "Row input spread of screen group" are displayed in the item description, but suppose the developer specifies to exclude the unnecessary "Row input spread of screen group."

[0114] When this exclusion is specified, the edit control unit 25 adds information indicating that the row has been excluded to the row of the "row input spread of the screen group" for which the exclusion has been specified, as shown in Fig. 30. The information (icon) of the "excluded item" shown in Fig. 30 is the information indicating that the row has been excluded.

[0115] Next, when the save button 61 on the editing screen is operated, the item description data generation unit 24 generates item description data that excludes (deletes) the item description data of the controls that have been specified for exclusion, and stores the data in the item description data storage unit 12.

[0116] Next, we will explain the meanings of the symbols "-", "x", and "←" entered in the right column of the editing screen in Figure 30. These symbols are used to set the state of each control in the item manual. By clicking these symbols with a mouse, for example, the developer can set the state of each control to the desired state.

[0117] Specifically, the symbol "-" indicates that an item description including the item description of that control will be created.

[0118] The "x" symbol indicates the cancellation of an added item. In other words, when the symbol is changed to "x", the item description data generation unit 24 generates item description data in a state where the added control has been cancelled. This allows you to adjust whether or not to display the added control in the item description.

[0119] The "←" symbol is a symbol that is selected when making the control item an excluded item. When the "-" symbol is clicked, the editing control unit 25 changes the "-" symbol to a "←" symbol. The item description data generation unit 24 generates item description data that excludes the control that has been changed to a "←" symbol. This makes it possible to display an item description that excludes the control that has been changed to a "←" symbol.

[0120] The item description data generating unit 24 generates item description data that reflects the addition and removal of desired control items in this way. As a result, the display control unit 21 displays the item description shown in Fig. 31 via the output device 7. The item description data is also provided to the user of the user terminal device 52 from the server device 51 via the network 53.

[0121] (Effects of the embodiment) As is clear from the above explanation, the development terminal device 1 of the embodiment can assist in the creation of item descriptions for controls that make up the screen of an application program, thereby reducing the burden on the developer.

[0122] Furthermore, an item description showing a list of header items and input item attributes corresponding to the created application program can be automatically created and output, thereby preventing the inconvenience of incompleteness or errors caused by manual work.

[0123] Furthermore, the item description that reflects desired editing content such as adding or removing items can be easily output again, making it possible to always provide the latest item description.

[0124] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of goals "8" and "9" of the SDGs.

[0125] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs goals 12, 13, and 15.

[0126] Furthermore, the present invention can contribute to strengthening control and governance, thereby contributing to the achievement of Goal 16 of the SDGs.

[0127] [Other embodiments] The present invention can be implemented in various different forms other than the above-described embodiments within the scope of the technical concept described in the claims.

[0128] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically using a known method or the like.

[0129] Furthermore, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in the specification or drawings may be changed as desired unless otherwise specified.

[0130] Furthermore, the components shown in the figure are conceptual functional elements of the development terminal device 1, and do not necessarily have to have the physical configuration shown. For example, all or any part of the processing functions of the development terminal device 1, particularly the processing functions performed by the control unit 3, may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0131] The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in the embodiments, and is mechanically read by the development terminal device 1 as needed. That is, a storage unit 2 such as a ROM or HDD stores a computer program for working with an OS (Operating System) to give instructions to a control unit 3 (CPU) and perform various processes. This computer program is loaded into RAM, expanded, and executed appropriately by the control unit 3.

[0132] In addition, the development work support program of this development terminal device 1 may be stored in another server device connected to the development terminal device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0133] Furthermore, the business support program for executing the processes described in the embodiments may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0134] Here, the "recording medium" can be any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0135] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code.

[0136] It should be noted that a "program" is not necessarily limited to a single structure, but includes a structure that is distributed as multiple modules or libraries, and a structure that achieves its function by working together with other programs, such as an OS.

[0137] Furthermore, the specific configuration for reading the recording medium in the development terminal device 1 of the embodiment, the reading procedure, and the installation procedure after reading can be any known configuration or procedure.

[0138] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, web page files, etc. used for various processes or providing websites.

[0139] The development terminal device 1 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may also be implemented with software (including programs or data) that realizes the processes described in the embodiments.

[0140] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be selectively implemented by combining them in any way. [Industrial Applicability]

[0141] The present invention is suitable for application to program development work. [Explanation of symbols]

[0142] 1 Development terminal device 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / output interface section 6 Input Devices 7 Output Devices 11 Control list information storage section 12 Item Description Data Storage Unit 13 Screen layout data storage unit 21 Display control unit 22 Acquisition Department 23 Screen Layout Construction Department 24 Item Description Data Generation Section 25 Editing control section 26 Communication control section 50 databases 51 Server equipment 52 User terminal device 53 Network

Claims

1. an acquisition unit that refers to control list information including identification names and types of controls that are input components that configure a screen, and acquires at least identification names and types corresponding to the controls included in the designed screen from the control list information; an item description data generating unit that generates item description data, which is description data for each control included in the designed screen, including the acquired identification name, the type, and an input field for an explanation document for each control; A business support device having the above.

2. The control list information includes an identification name and a type of an attached control attached to the main control, the acquiring unit acquires, from the control list information, the identification name and the type of the main control, as well as the identification name and the type of the attached control attached to the main control; the item description data generation unit generates the item description data including the input fields for identification names, types, and explanatory text of the main control and the auxiliary control; 2. The business support device according to claim 1, wherein:

3. The control list information includes, for each of the controls and each of the attached controls, essential information indicating whether the control is an essential control or not, initial value set information indicating whether the control is a control that is handled with an initial value set or not, designation information indicating whether at least one item or multiple items can be designated for the control, and display-only information indicating that the control is a display-only control, the acquiring unit acquires the required information, the initial value set information, the designation information, and the display-only information together with the identification names and the types of the control and the attached control from the control list information; the item description data generation unit generates the item description data including the required information, the initial value set information, the designation information, and the display-only information together with the input fields for the identification names, types, and explanatory documents of the control and the attached control; 3. The business support device according to claim 2, wherein:

4. an edit control unit that, when editing of the item description data displayed on the display unit is designated, makes the input field ready for input of an explanatory document; the item description data generation unit generates the item description data including the explanatory text input in the input field, the identification name, and the type; 4. The business support device according to claim 3, wherein:

5. The control list information includes, for each control, at least, an item attribute indicating characters, symbols, or numbers that can be used when inputting data to the control, and the number of digits that can be input. the acquiring unit acquires, from the control list information, the item attribute indicating a character, symbol, or numeric value and the number of digits that can be entered, along with the identification name and the type; the item description data generating unit generates the item description data including the item attributes indicating characters, symbols, and numerical values ​​and the number of digits that can be input, together with the input fields for the identification name, type, and explanatory text of each control; 5. The business support device according to claim 4, wherein:

6. when the addition of the control is specified, the acquisition unit acquires, from the control list information, an identification name, a type, the input field of the explanatory document, the item attribute indicating a character, a symbol, or a numerical value, and the number of digits that can be entered, corresponding to the added control; the editing control unit additionally inserts, into the item description data displayed on the display unit, an identification name, a type, the input field of the explanatory document, the item attribute indicating a character, a symbol or a numerical value, and the number of digits that can be input, corresponding to the added control; the item description data generation unit generates the item description data including an identification name, type, the input field of the explanatory document, the item attribute indicating a character, symbol or numeric value, and the number of digits that can be input corresponding to the additionally inserted control, and to which information indicating that the control is an additionally inserted control is added; 6. The business support device according to claim 5,

7. the editing control unit adds information indicating that the control has been excluded to the item instruction manual data of the control that has been designated as excluded from the controls displayed on the display unit; the item description data generating unit generates the item description data from which the control designated for exclusion has been deleted; 7. The business support device according to claim 6, wherein:

8. an acquisition step in which an acquisition unit refers to control list information including identification names and types of controls that are input components that configure a screen, and acquires at least identification names and types corresponding to the controls included in the designed screen from the control list information; an item description data generating step in which an item description data generating unit generates item description data, which is description data for each control included in the designed screen, including the acquired identification name, the type, and an input field for an explanatory document for each of the controls; A business support method having the above.

9. Computer, an acquisition unit that refers to control list information including identification names and types of controls that are input components that configure a screen, and acquires at least identification names and types corresponding to the controls included in the designed screen from the control list information; functioning as an item description data generating unit that generates item description data, which is description data for each control included in the designed screen, including the acquired identification name, the type, and an input field for an explanation document for each control; A business support program that features:

Images