Application development system

Abstract

To solve the problem in which in many cases, applications developed using application development support systems are developed by persons in charge who do not have specialized knowledge of application development, and it is not easy to ensure consistency between specifications and implementation.SOLUTION: An application development system 100 develops an application in two layers of a design unit 110 and an implementation unit 120. The design unit 110 creates design information 160 which is information necessary for the application to operate. The implementation unit 120 implements the application.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] Regarding application development systems. [Background technology]

[0002] In recent years, application development support systems (no-code development systems, low-code development systems) that reduce the burden on application developers and enable development by people who do not have specialized IT knowledge have been attracting attention. For example, the information processing device of Patent Document 1 (JP Patent Publication No. 2022-059478) creates a product application based on application software developed as a template.

[0003] Generally, when changing specifications in application development, the designer manually changes the specifications, and the implementer changes the implementation accordingly. Also, if the implementation is changed in advance, the specifications are manually changed accordingly. By ensuring consistency between the specifications and the implementation in this way, the efficiency of operation and maintenance is improved. Summary of the Invention [Problem to be solved by the invention]

[0004] However, applications developed using application development support systems are often developed by people who do not have specialized knowledge of application development, and it is not easy to ensure consistency between the specifications and the implementation. [Means for solving the problem]

[0005] The application development system of the first aspect develops applications in two layers: a design section and an implementation section. The design section creates design information, which is information necessary for the application to operate. The implementation section implements the application.

[0006] This application development system makes it easy to ensure consistency between specifications and implementation.

[0007] The application development system of a second aspect is the application development system of the first aspect, in which the design unit has a first processing unit, a second processing unit, and a third processing unit. The first processing unit creates first information that is information on tables used in the application. The second processing unit creates second information that is information on screens of the application. The third processing unit creates third information that is information for creating a layout of the screen.

[0008] The application development system according to a third aspect is the application development system according to the second aspect, in which the first information includes a table name, an item name, a data type, and relationship information.

[0009] The application development system according to a fourth aspect is the application development system according to the second or third aspect, wherein the second information includes information relating to a screen name and a screen transition.

[0010] An application development system according to a fifth aspect is the application development system according to any one of the second aspect to the fourth aspect, wherein the third information includes a screen size, a frame configuration, a type of component, an arrangement, and attribute information.

[0011] An application development system according to a sixth aspect is the application development system according to any one of the first aspect to the fifth aspect, in which the implementation unit has a creation unit. The creation unit creates a part of the implementation information based on the design information. The implementation information is information necessary for implementation.

[0012] In this application development system, the creation department creates part of the implementation information based on the design information, which makes it easy to ensure consistency between the specifications and the implementation.

[0013] The application development system according to a seventh aspect is the application development system according to the sixth aspect, in which the implementation unit further includes a reflecting unit, after the implementation information is updated, the reflecting unit reflects the contents of the update in the design information.

[0014] In this application development system, the reflecting unit reflects the contents of the updated implementation information in the design information, which makes it easy to ensure consistency between the specifications and the implementation. [Brief description of the drawings]

[0015] [Figure 1] 1 is a schematic diagram showing an overall configuration of an application development system. [Diagram 2] FIG. 13 is a diagram illustrating the relationship between design information and implementation information. [Diagram 3] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 4] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Diagram 5] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 6] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 7] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 8] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 9] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 10] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 11] FIG. 13 is a diagram illustrating an example of a screen for creating design information. [Figure 12] FIG. 13 is a diagram illustrating an example of a screen for creating mounting information. [Figure 13] FIG. 13 is a diagram illustrating an example of a screen for creating mounting information. [Figure 14] FIG. 13 is a diagram illustrating an example of a screen for creating mounting information. [Figure 15]FIG. 13 is a diagram illustrating an example of a screen for creating mounting information. [Figure 16] FIG. 13 is a diagram showing an example of a screen for reflecting mounting information in design information; [Figure 17] 13 is a flowchart showing a process for creating design information. [Figure 18] 13 is a flowchart showing a process for creating mounting information. [Figure 19] 13 is a flowchart showing the flow of a process for reflecting mounting information in design information. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] An application development system 100 according to an embodiment of the present disclosure will be described with reference to the drawings.

[0017] (1) Overall structure The application development system 100 is an application development support system that supports the development of applications by users. The application development system 100 is composed of one or more computers. When the application development system 100 is composed of multiple computers, the multiple computers may be connected to each other via a network. Note that in this specification, an application may be referred to as an app, but the meaning is the same.

[0018] The application development system 100 includes a control arithmetic device and a storage device. A processor such as a CPU or a GPU can be used for the control arithmetic device. The control arithmetic device reads a program stored in the storage device and performs predetermined image processing and arithmetic processing according to the program. Furthermore, the control arithmetic device can write the results of the calculation to the storage device and read information stored in the storage device according to the program.

[0019] As shown in Fig. 1, the application development system 100 mainly includes a design unit 110, an implementation unit 120, a display unit 130, an input unit 140, and a storage unit 150. The design unit 110, the specification management unit 111, the basic processing unit 112, the first processing unit 113, the second processing unit 114, the third processing unit 115, the implementation unit 120, the creation unit 121, the fourth processing unit 122, the fifth processing unit 123, and the reflection unit 124 shown in Fig. 1 are various functional blocks realized by the control arithmetic device. These functional blocks appear when the control arithmetic device executes a program.

[0020] The display unit 130 is, for example, a liquid crystal display. The display unit 130 displays display data output from the control arithmetic device. The display data may be a moving image or a still image.

[0021] The input unit 140 is, for example, a mouse and a keyboard. The input unit 140 may be a touch panel, etc. The input unit 140 accepts operations by a user and manual input of various information.

[0022] The storage unit 150 is a storage device that is mainly composed of a ROM, a RAM, a hard disk, and a solid-state drive (SSD). The storage unit 150 stores programs that can be read and executed by the control arithmetic device.

[0023] (2) Detailed configuration (2-1) Storage section The storage unit 150 stores design information 160 and implementation information 170. The design information 160 is information necessary for an application to operate. The implementation information 170 is information necessary for implementing an application. The design information 160 includes specification information 161, basic information 162, first information 163, second information 164, and third information 165. The implementation information 170 includes application information 171, fourth information 172, and fifth information 173. The design information 160 and the implementation information 170 may be stored in a server connected via an arbitrary network. In this case, the various functional blocks described above may acquire or update the design information 160 and the implementation information 170 via an arbitrary network.

[0024] The specification information 161 is information about the specification, including a specification identifier, a specification number, a specification name, a classification, icon information, a description of the specification, version information, and a comment on the version. The specification identifier is an identifier that uniquely indicates the data of the specification information 161, and when the version is different even if the specification number is the same, a different specification identifier is assigned. The basic information 162 is basic information about the application, including the application name, the release date, and an overview. The first information 163 is information about the table configuration, including the table name, the item name, the data type, and relationship information. The second information 164 is information about the screen, including the screen name and information about the screen transition. The third information 165 is information about the screen layout, including the screen size, the frame configuration, the type of the component, the arrangement, and attribute information.

[0025] The application information 171 is information about an application, including a classification, a schema name, an application name, an application identifier, icon information, a description of the application, and a corresponding specification identifier. The application identifier is an identifier that uniquely indicates the data of the application information 171. The fourth information 172 is information that includes the same items as the first information 163, and further includes detailed items such as an explanation of a table and remarks for each item. The fifth information 173 is information that includes the same items as the second information 164 and the third information 165, and further includes detailed items such as link information and display content information.

[0026] 2, the specification identifiers of the basic information 162, the first information 163, the second information 164, and the third information 165 are linked to the specification identifier of the specification information 161. Moreover, the corresponding specification identifier of the application information 171 is linked to the specification identifier of the specification information 161. Moreover, the application identifiers of the fourth information 172 and the fifth information 173 are linked to the application identifier of the application information 171.

[0027] (2-2) Design department 1, the design unit 110 includes a specification management unit 111, a basic processing unit 112, a first processing unit 113, a second processing unit 114, and a third processing unit 115. The design unit 110 creates design information 160, which is information necessary for an application to operate. The design unit 110 may display a warning when an invalid value is input, when a necessary value is not input, or the like.

[0028] (2-2-1) Specification Management Department The specification management unit 111 creates or updates specification information 161 of the application, and stores it in the storage unit 150. In addition, the specification management unit 111 displays a screen 1101 for displaying a list of specification names and a screen 1102 for creating or updating the specification information 161 on the display unit 130.

[0029] 2 is an example of a screen 1101 that displays a list of specification names. The screen 1101 is mainly composed of a menu section 1101a, a selection section 1101b, a button section 1101c, and a list section 1101d. The menu section 1101a displays "Home" and "Design" in a selectable manner. The selection section 1101b displays "Specification management", "Classification management", and "Version information" in a selectable manner. The button section 1101c is configured to allow the selection of functions required for the screen 1101.

[0030] FIG. 3 shows a state in which "Home" is selected in menu section 1101a and "Specification Management" is selected in selection section 1101b.

[0031] The specification management unit 111 displays a list of specification names in the list section 1101d based on the specification information 161 stored in the storage unit 150. When multiple versions of specification information 161 with the same specification number are stored, the specification management unit 111 may display only the specification information 161 with the largest version value in the list section 1101d. When no specification information 161 is stored in the storage unit 150, the specification management unit 111 does not display anything in the list section 1101d.

[0032] In response to a user's operation, the specification management unit 111 displays a screen 1102 for creating or updating the specification information 161 on the display unit 130 as shown in FIG. 4. The user inputs a value via the input unit 140. When the user performs an operation for creating a new file, only "save new" may be displayed as the save method 1102a, and "1" may be displayed as the version 1102b. When the user performs an operation for editing, the specification management unit 111 may display a dialog for selecting a version to be edited. The specification management unit 111 may display the screen 1102 after the user selects a version. In this case, "overwrite" and "upgrade" may be displayed as the save method 1102a. When the user selects "overwrite", the value of the version selected by the user may be displayed as the version 1102b. When the user selects "upgrade", the value obtained by adding 1 to the value of the largest version among the specification information 161 having the specification number selected by the user may be displayed as the version 1102b. The specification management unit 111 creates or updates the specification information 161 based on the inputted values, and stores it in the storage unit 150 together with the specification identifier.

[0033] 4, when the selected saving method 1102a is "new saving", the specification management unit 111 stores new specification information 161 in the storage unit 150 based on the input value. Also, when the selected saving method 1102a is "overwrite", the specification management unit 111 overwrites the specification information 161 of the selected version with the input value and stores it in the storage unit 150. Also, when the selected saving method 1102a is "version upgrade", the specification management unit 111 stores new specification information 161 in the storage unit 150 based on the input value.

[0034] (2-2-2) Basic processing section The basic processing unit 112 creates or updates basic information 162 of the application, and stores it in the storage unit 150. The basic processing unit 112 also displays a screen 1103 for creating the basic information 162 on the display unit .

[0035] 5 is an example of a screen 1103 for creating basic information 162. The screen 1103 is mainly composed of a menu section 1103a, a function section 1103b, a selection section 1103c, and a content section 1103d. The display contents of the menu section 1103a are the same as those of the menu section 1101a. The function section 1103b is configured to allow selection of functions required for the screen 1103. The selection section 1103c displays "basic information", "first information", "second information", and "third information" in a selectable manner.

[0036] FIG. 5 shows a state in which "Design" is selected in menu section 1103a and "Basic Information" is selected in selection section 1103c.

[0037] The basic processing unit 112 displays values ​​in the content section 1103d based on the basic information 162 stored in the storage unit 150. If the basic information 162 is not stored in the storage unit 150, the basic processing unit 112 displays each item in the content section 1103d as blank. The user inputs values ​​via the input unit 140. For example, the input field for the summary 1103e may be configured to allow selection from a plurality of example sentences. The basic processing unit 112 creates or updates the basic information 162 based on the input values, and stores it in the storage unit 150.

[0038] (2-2-3) First Processing Section The first processing unit 113 creates or updates first information 163, which is information on a table used in an application, and stores it in the storage unit 150. Furthermore, the first processing unit 113 displays screens for creating the first information 163, including screens 1104 and 1105, on the display unit 130. When the first processing unit 113 displays the design information 160 in which the implementation information 170 has been reflected by the reflection unit 124, which will be described later, the first processing unit 113 grays out buttons, input fields, and the like for creating or editing the first information 163, so as not to accept input of the first information 163.

[0039] FIG. 6 is an example of a screen 1104 for creating or updating the table name, item name, and data type, which are the first information 163. The screen 1104 is mainly composed of a menu section 1104a, a function section 1104b, a first selection section 1104c, a second selection section 1104d, a list section 1104e, a third selection section 1104f, and a content section 1104g. The display contents of the menu section 1104a and the first selection section 1104c are the same as the display contents of the menu section 1101a and the selection section 1103c, respectively. The function section 1104b is configured to allow the selection of a function required for the screen 1104. The second selection section 1104d displays "Table definition" and "Relationship" selectably. The third selection section 1104f displays "Description", "Design", and "Data" selectably.

[0040] FIG. 6 shows a state in which "Design" is selected in menu section 1104a, "First information" is selected in first selection section 1104c, "Table definition" is selected in second selection section 1104d, and "Design" is selected in third selection section 1104f.

[0041] The first processing unit 113 displays a list of table names in the list section 1104e based on the table names of the first information 163 stored in the storage unit 150. FIG. 6 shows a state in which the employee table is selected in the list section 1104e. The first processing unit 113 displays the definition contents of the table linked to the table name specified in the list section 1104e in the content section 1104g based on the item names and data types of the first information 163 stored in the storage unit 150. If the first information 163 is not stored in the storage unit 150, the first processing unit 113 displays each item in the list section 1104e and the content section 1104g as blank. The user inputs a value via the input unit 140. The first processing unit 113 creates or updates the first information 163 based on the input value and stores it in the storage unit 150.

[0042] 7 is an example of a screen 1105 for creating or updating relationship information, which is the first information 163. The screen 1105 is mainly composed of a menu section 1105a, a function section 1105b, a first selection section 1105c, a second selection section 1105d, and a content section 1105e. The display contents of the menu section 1105a, the first selection section 1105c, and the second selection section 1105d are the same as the display contents of the menu section 1101a, the first selection section 1104c, and the second selection section 1104d, respectively. The function section 1105b is configured to allow a function required for the screen 1105 to be selected.

[0043] FIG. 7 shows a state in which "Design" is selected in menu section 1105a, "First Information" is selected in first selection section 1105c, and "Relationship" is selected in second selection section 1105d.

[0044] The first processing unit 113 displays the table name and the item name in the content section 1105e based on the first information 163 stored in the storage unit 150. Furthermore, the first processing unit 113 displays a diagram showing the relationship information in the content section 1105e based on the first information 163 stored in the storage unit 150. If the first information 163 is not stored in the storage unit 150, the first processing unit 113 does not display anything in the content section 1105e. If the relationship information of the first information 163 is not stored in the storage unit 150, the first processing unit 113 displays only the table name and the item name in the content section 1105e. The content section 1105e in FIG. 7 shows a state in which the relationship information is set between the department ID of the employee table and the department ID of the department table. Moreover, the qualification table shows a state in which the relationship information is not set. The user inputs the relationship information via the input unit 140. The first processing unit 113 creates or updates the first information 163 based on the input relationship information, and stores it in the storage unit 150.

[0045] The user can set relationship information by, for example, selecting the item name of the table for which a relationship is to be set by clicking with the mouse, and dragging and dropping it onto the item name of the table to which the relationship is to be set. The tables used to create relationship information may include tables linked from an external system.

[0046] (2-2-4) Second Processing Section The second processing unit 114 creates or updates second information 164, which is information on the screen of the application, and stores it in the storage unit 150. Furthermore, the second processing unit 114 displays screens for creating the second information 164, including screens 1106 and 1107, on the display unit 130. When the second processing unit 114 displays the design information 160 in which the implementation information 170 has been reflected by the reflection unit 124, which will be described later, the second processing unit 114 grays out buttons, input fields, and the like for creating or editing the second information 164, so as not to accept input of the second information 164.

[0047] 8 is an example of a screen 1106 for creating or updating a screen name, which is the second information 164. The screen 1106 is mainly composed of a menu section 1106a, a function section 1106b, a first selection section 1106c, a second selection section 1106d, and a list section 1106e. The display contents of the menu section 1106a and the first selection section 1106c are the same as the display contents of the menu section 1101a and the selection section 1103c, respectively. The function section 1106b is configured to allow the selection of functions required for the screen 1106. The second selection section 1106d displays a "screen list" and a "screen transition" selectably.

[0048] FIG. 8 shows a state in which "Design" is selected in menu section 1106a, "Second information" is selected in first selection section 1106c, and "Screen list" is selected in second selection section 1106d.

[0049] The second processing unit 114 displays a list of screen names in the list section 1106e based on the screen names of the second information 164 stored in the storage unit 150. If the screen name of the second information 164 is not stored in the storage unit 150, the second processing unit 114 does not display anything in the list section 1106e. The user inputs a value via the input unit 140. The second processing unit 114 creates or updates the second information 164 based on the input value and stores it in the storage unit 150.

[0050] 9 is an example of a screen 1107 for creating or updating information on screen transition, which is the second information 164. Here, the information on screen transition includes information on a screen from which the transition originates, a screen to which the transition is to be made, and a default screen. The screen 1107 is mainly composed of a menu section 1107a, a function section 1107b, a first selection section 1107c, a second selection section 1107d, a content section 1107e, and a list section 1107f. The display contents of the menu section 1107a, the first selection section 1107c, and the second selection section 1107d are the same as the display contents of the menu section 1101a, the selection section 1103c, and the second selection section 1106d, respectively. The function section 1107b is configured to allow a function required for the screen 1107 to be selected.

[0051] FIG. 9 shows a state in which "Design" is selected in menu section 1107a, "Second information" is selected in first selection section 1107c, and "Screen transition" is selected in second selection section 1107d.

[0052] The second processing unit 114 displays a screen transition diagram in the content section 1107e based on the information on the screen transition of the second information 164 stored in the storage unit 150. If the information on the screen transition of the second information 164 is not stored in the storage unit 150, the second processing unit 114 does not display anything in the content section 1107e. The second processing unit 114 displays the screen names that have not yet been arranged in the list section 1107f in a selectable manner such as in a list format. The content section 1107e in FIG. 9 shows a state in which the menu screen can be transitioned to screen A1 and screen B1, and the screen A1 can be transitioned to screen A11. The user creates or updates information on the screen transition via the input unit 140. The second processing unit 114 creates or updates the second information 164 based on the created or updated information on the screen transition, and stores it in the storage unit 150.

[0053] The user can display the screen name in the content section 1107e by, for example, selecting the screen name in the list section 1107f by clicking it with the mouse and dragging and dropping it into the content section 1107e. Also, for example, a screen transition diagram can be created by dragging and dropping a source screen and a destination screen.

[0054] (2-2-5) Third Processing Section The third processing unit 115 creates or updates third information 165, which is information for creating a layout of a screen of an application, and stores it in the storage unit 150. The third processing unit 115 also displays screens for creating the third information 165, including a screen 1108 and a screen 1109, on the display unit 130. Here, the information for creating the screen layout includes, for example, a screen size, a frame configuration, a type of a component, an arrangement, attribute information, and a background image. The type of a component indicates the type of an element that configures a screen, such as a label, a text field, a text area, a numeric field, a date field, a check box, a radio button, and a command button. The attribute information of a component includes settings such as a font of characters to be displayed in the component, an image size, and the like. The information for creating the screen layout is described, for example, in XAML (Extensible Application Markup Language). When the third processing unit 115 displays the design information 160 in which the implementation information 170 has been reflected by the reflection unit 124 described later, the third processing unit 115 grays out buttons, input fields, etc. for creating or editing the third information 165 so as not to accept input of the third information 165.

[0055] 10 is an example of a screen 1108 for creating or updating a frame configuration, which is the third information 165. The screen 1108 is mainly composed of a menu section 1108a, a function section 1108b, a first selection section 1108c, a second selection section 1108d, a content section 1108e, and a list section 1108f. The display contents of the menu section 1108a and the first selection section 1108c are the same as the display contents of the menu section 1101a and the selection section 1103c, respectively. The function section 1108b is configured to allow selection of functions required for the screen 1108. The second selection section 1108d displays screen names stored in the storage section 150 in a selectable manner for each screen name. The list section 1108f displays frame configurations in a selectable manner in a list format or the like.

[0056] FIG. 10 shows a state in which "Design" is selected in menu section 1108a, "Third Information" is selected in first selection section 1108c, and "Screen A1" is selected in second selection section 1108d.

[0057] The third processing unit 115 displays a screen layout in the content section 1108e based on the third information 165 of the screen A1 stored in the storage unit 150. When the third information 165 of the screen A1 is not stored in the storage unit 150, the third processing unit 115 displays a blank screen layout in the content section 1108e. The user creates or updates a frame configuration via the input unit 140. For example, when the user selects a frame configuration in the list section 1108f via the input unit 140, the third processing unit 115 displays the frame configuration in the content section 1108e. The third processing unit 115 creates or updates the third information 165 based on the created or updated frame configuration, and stores it in the storage unit 150.

[0058] 11 is an example of a screen 1109 for creating or updating the type and arrangement of components, which is the third information 165. The screen 1109 is mainly composed of a menu section 1109a, a function section 1109b, a first selection section 1109c, a second selection section 1109d, a content section 1109e, and a list section 1109f. The display contents of the menu section 1109a, the first selection section 1109c, and the second selection section 1109d are the same as the display contents of the menu section 1101a, the selection section 1103c, and the second selection section 1108d, respectively. The function section 1109b is configured so that a function required for the screen 1109 can be selected. The list section 1109f displays components in a selectable manner, such as in a list format.

[0059] FIG. 11 shows a state in which "Design" is selected in menu section 1109a, "Third Information" is selected in first selection section 1109c, and "Screen A1" is selected in second selection section 1109d.

[0060] The third processing unit 115 displays a screen layout in the content section 1109e based on the third information 165 of the screen A1 stored in the storage unit 150. If the third information 165 of the screen A1 is not stored in the storage unit 150, the third processing unit 115 displays a blank screen layout in the content section 1109e. The user creates or updates the screen layout via the input unit 140. The third processing unit 115 creates or updates the third information 165 based on the created or updated screen layout, and stores it in the storage unit 150.

[0061] The user can select a component in list section 1109f by clicking it with the mouse, for example, and arrange the components by dragging and dropping it onto the screen layout in content section 1109e. Third processing section 115 displays the screen layout in which the components are arranged in content section 1109e in response to the user's operation. The user can select a component in content section 1109e by clicking it with the mouse, for example, and change the arrangement position, size, etc. by dragging and dropping it. In addition, the user can change attribute information such as the font and color of characters by selecting a component in content section 1109e by clicking it with the mouse, for example, and selecting from a list or pull-down menu.

[0062] (2-3) Mounting section 1, the implementation unit 120 includes a creation unit 121, a fourth processing unit 122, a fifth processing unit 123, and a reflection unit 124. The implementation unit 120 implements an application. The implementation unit 120 may display a warning when an invalid value is input, when a required value is not input, or the like.

[0063] (2-3-1) Creation Department The creation unit 121 creates or updates implementation information 170 of the application, and stores it in the storage unit 150. Furthermore, the creation unit 121 creates or updates a table based on the fourth information 172. Furthermore, the creation unit 121 displays a screen 1110 for displaying a list of application names on the display unit 130.

[0064] 12 is an example of a screen 1110 displaying a list of application names. The screen 1110 is mainly composed of a menu section 1110a, a selection section 1110b, a button section 1110c, and a list section 1110d. The menu section 1110a displays "Home", "Table Design", "Screen Design", etc. in a selectable manner. The selection section 1110b displays "Application Management", "Table Management", "Job Flow Management", etc. in a selectable manner. The button section 1110c is configured to allow selection of a function required for the screen 1110.

[0065] FIG. 12 shows a state in which "Home" is selected in menu section 1110a and "Application Management" is selected in selection section 1110b.

[0066] Creation unit 121 displays a list of application names in list section 1110d based on application information 171 stored in storage unit 150. If application information 171 is not stored in storage unit 150, creation unit 121 does not display anything in list section 1110d.

[0067] In response to a user's operation, the creation unit 121 displays a screen 1111 for creating application information 171 on the display unit 130 as shown in Fig. 13. The screen 1111 is mainly composed of a selection unit 1111a and a setting unit 1111b. The selection unit 1111a is configured to be able to select the specification information 161 stored in the storage unit 150. The setting unit 1111b is configured to be able to input a part of the application information 171. The user selects the specification information 161 to be linked and inputs a part of the application information 171 via the input unit 140.

[0068] In response to a user's operation, the creation unit 121 acquires a specification identifier (hereinafter, referred to as a selected specification identifier) ​​associated with the selected specification information 161, and acquires the first information 163, the second information 164, and the third information 165 associated with the selected specification identifier. Here, when the implementation information 170 exists for the specification information 161 associated with the selected specification identifier, the creation unit 121 displays a warning and does not create the implementation information 170. Furthermore, when the necessary design information 160 is not stored in the storage unit 150, the creation unit 121 may display a warning screen. The creation unit 121 creates an application identifier and stores it in the storage unit 150 as application information 171 together with the selected specification identifier and the input value of the setting unit 1111b. The creation unit 121 may store a flag indicating whether the implementation information 170 has been created in the design information 160. The creation unit 121 stores the acquired first information 163 as the fourth information 172 in the storage unit 150, and stores the acquired second information 164 and third information 165 as the fifth information 173 in the storage unit 150. The creation unit 121 may store only information on a default screen as the fifth information 173 in the storage unit 150, as information on screen transitions that is the second information 164. Furthermore, the creation unit 121 checks the existence of a table in the schema based on the schema name of the application information 171 and the fourth information 172. If a table with the same name that is not permitted to be updated exists in the schema, the creation unit 121 does not create a table. If a table with the same name does not exist in the schema, or if a table with the same name that is permitted to be updated exists in the schema, the creation unit 121 creates or updates a table in the schema. Furthermore, the creation unit 121 creates or updates a relationship of a table in the schema based on the fourth information 172. In other words, the creation unit 121 creates the implementation information 170 based on the design information 160.

[0069] (2-3-2) Fourth Processing Section The fourth processing unit 122 creates or updates fourth information 172, which is information on a table used in an application, and stores it in the storage unit 150. In addition, the fourth processing unit 122 displays a screen for creating the fourth information 172, including a screen 1112, on the display unit 130.

[0070] 14 is an example of a screen 1112 for creating or updating the table name, item name, data type, and remarks, which are the fourth information 172. The screen 1112 is mainly composed of a menu section 1112a, a function section 1112b, a list section 1112c, and a content section 1112d. The display contents of the menu section 1112a are the same as the display contents of the menu section 1110a. The function section 1112b is configured so that functions required for the screen 1112 can be selected.

[0071] FIG. 14 shows a state in which "Table Design" is selected in the menu section 1112a.

[0072] The fourth processing unit 122 displays a list of table names in the list section 1112c based on the table names of the fourth information 172 stored in the storage unit 150. If the table name of the fourth information 172 is not stored in the storage unit 150, the fourth processing unit 122 does not display anything in the list section 1112c. The fourth processing unit 122 displays the definition content of the table linked to the table name specified in the list section 1112c in the content section 1112d based on the item names and data types of the fourth information 172 stored in the storage unit 150. If the item names and data types of the fourth information 172 are not stored in the storage unit 150, the fourth processing unit 122 displays each item in the content section 1112d as blank. The user inputs a value via the input unit 140. The fourth processing unit 122 creates or updates the fourth information 172 based on the input value and stores it in the storage unit 150. Moreover, the fourth processing unit 122 creates or updates a table configuration in the schema based on the created or updated fourth information 172.

[0073] The fourth processing unit 122 displays a screen (not shown) for creating or updating relationship information, which is fourth information 172, on the display unit 130. The fourth processing unit 122 displays the state of the relationship based on the fourth information 172 stored in the storage unit 150. The user inputs the relationship information via the input unit 140. The fourth processing unit 122 creates or updates the fourth information 172 based on the input relationship information, and stores it in the storage unit 150. The fourth processing unit 122 also creates or updates the relationship of the tables in the schema based on the created or updated fourth information 172.

[0074] The method of setting relationship information on a screen (not shown) for creating or updating relationship information may be the same as the method of setting relationship information on screen 1105.

[0075] (2-3-3) Fifth Processing Section The fifth processing unit 123 creates or updates fifth information 173, which is information on the screen of the application and information for creating a screen layout, and stores it in the storage unit 150. The fifth processing unit 123 also displays a screen for creating the fifth information 173, including the screen 1113, on the display unit 130. The information for creating the screen layout is written in, for example, XAML (Extensible Application Markup Language).

[0076] 15 is an example of a screen 1113 for implementing an application screen. The screen 1113 is mainly composed of a menu section 1113a, a function section 1113b, a list section 1113c, and a content section 1113d. The display contents of the menu section 1113a are the same as the display contents of the menu section 1110a. The function section 1113b is configured so that functions required for the screen 1113 can be selected.

[0077] FIG. 15 shows a state in which "Screen Design" is selected in menu section 1113a.

[0078] The fifth processing unit 123 displays a list of screen names in the list section 1113c based on the fifth information 173 stored in the storage unit 150. The fifth processing unit 123 displays a screen layout associated with the screen name specified in the list section 1113c in the content section 1113d based on the fifth information 173 stored in the storage unit 150. If the fifth information 173 is not stored in the storage unit 150, the fifth processing unit 123 displays a blank screen layout in the content section 1113d. The user creates or updates the screen layout via the input unit 140. The method of setting the screen layout in the screen 1113 may be the same as the method of setting the screen layout in the screens 1108 and 1109. The attribute information of the component further includes operation settings such as events related to the component. Specifically, for example, the user can set link information of a command button arranged in the screen layout. Also, for example, the user can set the contents to be displayed in the component by specifying a table name and an item name for a component such as a text field arranged in the screen layout. The fifth processing unit 123 creates or updates fifth information 173 based on the created or updated screen layout, and stores it in the storage unit 150.

[0079] (2-3-4) Reflection section The reflection unit 124 reflects the implementation information 170 of the application in the design information 160 .

[0080] 16, the reflection unit 124 displays a screen 1114 for updating the design information 160. The screen 1114 is mainly composed of an application selection unit 1114a and a specification selection unit 1114b. The reflection unit 124 displays application information 171 selected by the user in the application selection unit 1114a. In addition, the reflection unit 124 displays specification information 161 associated with the corresponding specification identifier of the selected application information 171 in the specification selection unit 1114b.

[0081] In response to a user's operation, the reflecting unit 124 acquires an application identifier (hereinafter, referred to as a selected application identifier) ​​associated with the selected application information 171, and acquires fourth information 172 and fifth information 173 associated with the selected application identifier. Furthermore, the reflecting unit 124 acquires a corresponding specification identifier associated with the selected application information 171. The reflecting unit 124 acquires specification information 161 associated with the corresponding specification identifier. Based on the acquired specification information 161, the reflecting unit 124 creates new specification information 161 having a different version value from the acquired specification information 161, and stores the new specification information 161 in the storage unit 150. The specification information 161 having a different version value is, in other words, new specification information 161 having a different specification identifier. Furthermore, the reflecting unit 124 creates new first information 163 based on the acquired fourth information 172, creates new second information 164 based on the acquired fifth information 173, and creates new third information 165 based on the acquired fifth information 173. In other words, the reflection unit 124 creates new design information 160 based on the implementation information 170.

[0082] (3) Explain application development using an application development system The flow of application development using the application development system 100 will be described with reference to Figures 17 to 19. Note that the flowcharts shown in Figures 17 to 19 are merely examples and may be modified as appropriate within a range that does not contradict. For example, other steps not shown may be included before or after each step, and the order of each step may be modified as appropriate within a range that does not contradict each other.

[0083] (3-1) Creating design information The flow of creating new design information 160 using the application development system 100 will be described with reference to FIG.

[0084] When the user instructs the application development system 100 to launch a screen 1101 for displaying a list of specification names, the specification management unit 111 displays the screen 1101. Thereafter, when the user presses "Create new" in the button section 1101c, the specification management unit 111 displays a screen 1102 for creating or updating specification information 161. When the user inputs values ​​in each input field and instructs new saving, the specification management unit 111 stores the input values ​​as specification information 161 in the storage unit 150. This creates the application specification information 161 (step S11). The specification management unit 111 displays the created specification information 161 in the list section 1101d.

[0085] When the user selects a specification name in the list section 1101d by clicking the mouse or the like and then presses "Design" in the button section 1101c, the basic processing section 112 displays a screen 1103 for creating basic information 162 related to the specification name (hereinafter, referred to as selected specification). The basic processing section 112 displays each item in the content section 1103d as blank.

[0086] When the user inputs values ​​into each input field in the content section 1103d and instructs saving, the basic processing section 112 stores the input values ​​as the basic information 162 in the storage section 150. In this way, the basic information 162 of the application is created (step S12).

[0087] When the user presses "first information" in the selection section 1103c, the first processing section 113 displays a screen 1104 for creating first information 163 regarding the selected specifications. The first processing section 113 displays each item in the list section 1104e and the content section 1104g of the screen 1104 as blank.

[0088] When the user inputs a table name and table definition content on screen 1104 and instructs to save it, first processing unit 113 stores the input content as first information 163 in storage unit 150. As a result, the table name and table definition content, which are first information 163 of the application, are created (step S13).

[0089] When the user presses "relationship" in the second selection portion 1104d, the first processing portion 113 displays a screen 1105 for creating relationship information related to the selected specifications. The first processing portion 113 displays the table name and the item name in the content portion 1105e.

[0090] When the user inputs relationship information in content section 1105e and instructs saving, first processing section 113 stores the input content as first information 163 in storage section 150. Thereby, relationship information of the table, which is first information 163 of the application, is created (step S14).

[0091] When the user presses "second information" in the first selection portion 1105c, the second processing portion 114 displays a screen 1106 for creating second information 164 regarding the selected specifications. The second processing portion 114 does not display anything in the list portion 1106e.

[0092] When the user inputs a screen name or the like on screen 1106 and instructs saving, second processing unit 114 stores the input value as second information 164 in storage unit 150. This creates the screen name, which is second information 164 of the application (step S15). Second processing unit 114 displays the created second information 164 in list unit 1106e.

[0093] When the user presses “screen transition” in the second selection portion 1106d, the second processing portion 114 displays a screen 1107 relating to the selected specifications. The second processing portion 114 displays the screen name stored as the second information 164 in the list portion 1107f, and displays nothing in the content portion 1107e.

[0094] When the user inputs information about screen transition on screen 1107 and instructs to save it, second processing unit 114 stores the input content in storage unit 150 as second information 164. As a result, information about screen transition, which is second information 164 of the application, is created (step S16).

[0095] When the user presses "Third information" in the first selection portion 1107c, the third processing portion 115 displays a screen 1108 for creating third information 165 regarding the selected specifications. The third processing portion 115 displays a blank screen layout in the content portion 1108e.

[0096] When the user presses "Screen Size" from the functional unit 1108b, the third processing unit 115 displays a screen (not shown) for selecting a screen size. When the user inputs the screen size and frame configuration and instructs saving, the third processing unit 115 stores the input contents as the third information 165 in the storage unit 150. As a result, the frame configuration and screen size, which are the third information 165 of the application, are created.

[0097] When the user presses "Component" from function section 1108b, third processing section 115 displays screen 1109 regarding the selected specifications. Third processing section 115 displays the frame configuration stored as third information 165 in content section 1109e, and displays selectable components in list section 1109f.

[0098] When the user creates a screen layout by selecting and arranging components on screen 1109 and instructs to save it, third processing unit 115 stores the input contents in storage unit 150 as third information 165. This creates information for creating a screen layout, which is third information 165 of the application (step S17).

[0099] (3-2) Creating implementation information The flow of creating new implementation information 170 using the application development system 100 will be described with reference to FIG.

[0100] When the user instructs application development system 100 to launch screen 1110 for displaying a list of application names, creation unit 121 displays screen 1110.

[0101] When the user presses "Link" in button section 1110c, creation section 121 displays screen 1111 for creating application information 171. The user selects specification information 161 to link in selection section 1111a, inputs part of application information 171 in setting section 1111b, and then issues an instruction for import (step S21). If implementation information 170 exists for specification information 161 selected by the user, creation section 121 displays a warning and does not create implementation information 170.

[0102] The creation unit 121 creates application information 171, fourth information 172, and fifth information 173 based on the specification information 161 selected by the user and the input value of the setting unit 1111b, and stores them in the storage unit 150. Furthermore, the creation unit 121 checks the existence of a table in the schema based on the schema name of the application information 171 and the fourth information 172, and then creates or updates a table in the schema. As a result, the implementation information 170 is created (step S22). The creation unit 121 displays the created application information 171 in the list unit 1110d.

[0103] When the user selects an application name in the list section 1110d by clicking the mouse or the like and then presses “Table Design” in the menu section 1110a, the fourth processing section 122 displays a screen 1112 for creating or updating fourth information 172 related to the application name (hereinafter, referred to as the selected application). On the screen 1112, the fourth processing section 122 displays the fourth information 172 stored in the storage section 150.

[0104] When the user inputs a table name and table definition content in the list section 1112c and the content section 1112d and instructs saving, the fourth processing section 122 stores the input values ​​as the fourth information 172 in the storage section 150. This creates the table name and table definition content, which are the fourth information 172 of the application. Furthermore, the fourth processing section 122 creates or updates the table configuration in the schema based on the input fourth information 172 (step S23).

[0105] When the user issues an instruction to display the relationship information from the functional unit 1112b, the fourth processing unit 122 displays a screen (not shown) for creating or updating relationship information regarding the selected application.

[0106] When the user inputs relationship information and instructs saving, the fourth processing unit 122 stores the input content in the storage unit 150 as the fourth information 172. This creates table relationship information, which is the fourth information 172 of the application. Furthermore, the fourth processing unit 122 creates or updates the relationship of the tables in the schema based on the input fourth information 172 (step S24).

[0107] When the user presses “screen design” in the menu section 1112a, the fifth processing section 123 displays a screen 1113 for creating fifth information 173 related to the selected application. The fifth processing section 123 displays the fifth information 173 stored in the storage section 150 in a list section 1113c and a content section 1113d.

[0108] When the user creates a screen name and a screen layout on the screen 1113 and instructs to save them, the fifth processing unit 123 stores the input contents in the storage unit 150 as the fifth information 173. As a result, the screen name and the screen layout, which are the fifth information 173 of the application, are created (steps S25 and S26).

[0109] (3-3) Reflection of implementation information The flow of reflecting the implementation information 170 in the design information 160 using the application development system 100 will be described with reference to FIG.

[0110] When the user instructs the application development system 100 to open a screen 1110 for displaying a list of application names, the reflection unit 124 displays the screen 1110.

[0111] When the user selects an application name in the list section 1110d by clicking the mouse or the like and then presses the “Link” button in the button section 1110c, the reflection section 124 displays a screen 1114 for updating the design information 160 of the selected application (step S31).

[0112] When the user gives an instruction to reflect, the reflection unit 124 creates new specification information 161, first information 163, second information 164, and third information 165 based on the application information 171 of the application selection unit 1114a and the specification information 161 of the specification selection unit 1114b, and stores them in the memory unit 150 (step S32).

[0113] (4) Features In general application development, when specifications are changed, the designer manually changes the specifications, and the implementer changes the implementation accordingly. Also, if the implementation is changed in advance, the specification is manually changed accordingly.

[0114] However, application development using application development support systems, which have been attracting attention in recent years, is often carried out by people who do not have specialized knowledge of application development, making it difficult to ensure consistency between the specifications and the implementation.

[0115] (4-1) The application development system 100 of this embodiment develops applications in two layers: a design unit 110 and an implementation unit 120. The design unit 110 creates design information 160, which is information necessary for the application to run. The implementation unit 120 implements the application. This configuration makes it easy to ensure consistency between the specification and the implementation.

[0116] (4-2) In the application development system 100 of this embodiment, the design unit 110 has a first processing unit 113, a second processing unit 114, and a third processing unit 115. The first processing unit 113 creates first information 163, which is information on tables used in the application. The second processing unit 114 creates second information 164, which is information on the screen of the application. The third processing unit 115 creates third information 165, which is information for creating the layout of the screen.

[0117] (4-3) In the application development system 100 of this embodiment, the first information 163 includes a table name, an item name, a data type, and relationship information. With this configuration, the design unit 110 can create information for creating a table used in the application.

[0118] (4-4) In the application development system 100 of this embodiment, the second information 164 includes information on the screen name and the screen transition. With this configuration, the design unit 110 can create information on the screens used in the application.

[0119] (4-5) In the application development system 100 of this embodiment, the third information 165 includes screen size, frame configuration, type of component, arrangement, and attribute information. With this configuration, the design unit 110 can create information for creating a layout of a screen used in an application.

[0120] (4-6) In the application development system 100 of this embodiment, the implementation unit 120 has a creation unit 121. The creation unit 121 creates a part of the implementation information 170, which is information necessary for implementation, based on the design information 160. Since the design information 160 includes information on tables and information on screens necessary for implementation, the creation unit 121 can create a part of the implementation information 170 based on the design information 160. This configuration makes it easy to ensure consistency between the specifications and the implementation.

[0121] (4-7) In the application development system 100 of this embodiment, the implementation unit 120 has a reflection unit 124. After the implementation information 170 is updated, the reflection unit 124 reflects the contents of the update in the design information 160. Since the implementation information 170 is created based on the design information 160, the reflection unit 124 can reflect the implementation information 170 in the design information 160. This configuration makes it easy to ensure consistency between the specification and the implementation.

[0122] (4-8) In the application development system 100 of this embodiment, when the reflection unit 124 reflects the implementation information 170 in the design information 160, new specification information 161, first information 163, second information 164, and third information 165 having different specification identifiers are created and stored in the storage unit 150. According to this configuration, the change history of the design information 160 can be stored.

[0123] (4-9) In the application development system 100 of this embodiment, if implementation information 170 exists for the selected specification information 161, the creation unit 121 displays a warning and does not create the implementation information 170. This configuration makes it possible to prevent multiple pieces of implementation information 170 from being created based on one piece of design information 160. As a result, it becomes easier to ensure consistency between the specification and the implementation.

[0124] (4-10) In the application development system 100 of this embodiment, when the design information 160 in which the implementation information 170 is reflected by the reflecting unit 124 is displayed, the first processing unit 113 grays out buttons, input fields, etc. for creating or editing the first information 163, and does not accept input of the first information 163. The second processing unit 114 grays out buttons, input fields, etc. for creating or editing the second information 164, and does not accept input of the second information 164. The third processing unit 115 grays out buttons, input fields, etc. for creating or editing the third information 165, and does not accept input of the third information 165. With this configuration, it is possible to restrict updates to the design information 160 in which the implementation information 170 is reflected. As a result, it becomes easy to ensure consistency between the specification and the implementation.

[0125] (5) Variations (5-1) Variation A In this embodiment, the basic information 162 is created, but the creation of the basic information 162 may be omitted.

[0126] (5-2) Variation B In this embodiment, a table name and table definition contents are created as the first information 163, but the table to be created may have only an ID (identification information) column. Even in this case, the creation unit 121 may create or update a table in the schema.

[0127] (5-3) Variation C In this embodiment, information regarding screen transitions is created as the second information 164, but creation of the information regarding screen transitions may be omitted.

[0128] (5-4) Although the embodiments of the present disclosure have been described above, it will be understood that various changes in form and details can be made without departing from the spirit and scope of the present disclosure described in the claims. [Explanation of symbols]

[0129] 100 Application Development Systems 110 Design Department 113 First Processing Section 114 Second Processing Section 115 Third Processing Section 120 Mounting section 121 Creation Department 124 Reflection section 160 Design information 163 1st information 164 Second information 165 Third information 170 Implementation Information [Prior art documents] [Patent documents]

[0130] [Patent Document 1] JP 2022-059478 A

Claims

1. An application development system (100) for supporting application development, comprising: The application is developed in two layers: a design section (110) that creates design information (160) that is information necessary for the application to operate, and an implementation section (120) that implements the application. Application development system.

2. The design unit includes: a first processing unit (113) for generating first information (163) which is information on a table used in the application; A second processing unit (114) for generating second information (164) which is information on a screen of the application; a third processing unit (115) for creating third information (165) which is information for creating a layout of the screen; having The application development system of claim 1 .

3. The first information includes a table name, an item name, a data type, and relationship information. The application development system according to claim 2 .

4. The second information includes a screen name and information regarding a screen transition.

4. The application development system according to claim 2 or 3.

5. The third information includes a screen size, a frame configuration, a type of a component, an arrangement, and attribute information.

4. The application development system according to claim 2 or 3.

6. The mounting unit has a creation unit (121) that creates a part of mounting information (170), which is information necessary for mounting, based on the design information.

3. The application development system according to claim 1 or 2.

7. The implementation unit further includes a reflection unit (124) that reflects the update content in the design information after the implementation information is updated. The application development system according to claim 6.

Images