JP7733322B2 - Application Development System - Google Patents

Description

Regarding application development systems.

In recent years, application development support systems (no-code development systems, low-code development systems) have been gaining attention as they reduce the burden on application developers and enable development by those without specialized IT knowledge. For example, the information processing device described in Patent Document 1 (JP 2022-059478 A) creates product applications based on application software developed as a template.

Generally, when changing specifications during application development, the designer manually changes the specifications, and the implementer then changes the implementation accordingly. Furthermore, if changes are made to the implementation in advance, the specifications are manually changed accordingly. Ensuring consistency between the specifications and implementation in this way improves the efficiency of operation and maintenance.

However, applications developed using application development support systems are often developed by people without specialized application development expertise, making it difficult to ensure consistency between specifications and implementation.

The first-perspective application development system develops applications in two layers: a design section and an implementation section. The design section creates design information, which is the information necessary for the application to run. The implementation section implements the application.

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

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, which is information about tables used in the application. The second processing unit creates second information, which is information about the application screen. The third processing unit creates third information, which is information for creating the screen layout.

The third aspect of the application development system is the second aspect of the application development system, and the first information includes table names, field names, data types, and relationship information.

The fourth aspect of the application development system is the second or third aspect of the application development system, and the second information includes information related to screen names and screen transitions.

The application development system of the fifth aspect is an application development system of any one of the second aspect to the fourth aspect, wherein the third information includes screen size, frame configuration, component type, placement, and attribute information.

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

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

The seventh aspect of the application development system is the sixth aspect of the application development system, in which the implementation unit further includes a reflection unit. After the implementation information is updated, the reflection unit reflects the contents of the update in the design information.

In this application development system, the reflection unit reflects the contents of updated implementation information into the design information. This makes it easy to ensure consistency between specifications and implementation.

1 is a schematic diagram illustrating an overall configuration of an application development system. FIG. 10 is a diagram illustrating the relationship between design information and implementation information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating design information. FIG. 10 is a diagram illustrating an example of a screen for creating mounting information. FIG. 10 is a diagram illustrating an example of a screen for creating mounting information. FIG. 10 is a diagram illustrating an example of a screen for creating mounting information. FIG. 10 is a diagram illustrating an example of a screen for creating mounting information. FIG. 10 is a diagram illustrating an example of a screen for reflecting mounting information in design information. 10 is a flowchart showing the flow of a process for creating design information. 10 is a flowchart showing the flow of a process for creating packaging information. 10 is a flowchart showing the flow of a process for reflecting packaging information in design information.

The application development system 100 according to an embodiment of the present disclosure will be described with reference to the drawings.

(1) Overall Configuration The application development system 100 is an application development support system that supports users in developing applications. The application development system 100 is configured with one or more computers. When the application development system 100 is configured with 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 this has the same meaning.

The application development system 100 comprises a control and arithmetic unit and a storage device. The control and arithmetic unit can be a processor such as a CPU or GPU. The control and arithmetic unit reads a program stored in the storage device and performs predetermined image processing and arithmetic processing in accordance with this program. Furthermore, the control and arithmetic unit can write the results of calculations to the storage device and read information stored in the storage device in accordance with the program.

As shown in FIG. 1, the application development system 100 mainly comprises a design unit 110, an implementation unit 120, a display unit 130, an input unit 140, and a memory unit 150. The design unit 110, specification management unit 111, basic processing unit 112, first processing unit 113, second processing unit 114, third processing unit 115, implementation unit 120, creation unit 121, fourth processing unit 122, fifth processing unit 123, and 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.

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

The input unit 140 is, for example, a mouse and keyboard. The input unit 140 may also be a touch panel or the like. The input unit 140 accepts user operations and manual input of various information.

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

(2) Detailed Configuration (2-1) Storage Unit 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 the arbitrary network.

Specification information 161 is information about specifications, including a specification identifier, specification number, specification name, classification, icon information, specification description, version information, and version comments. The specification identifier is an identifier that uniquely identifies the data in specification information 161; even if the specification number is the same, different versions are assigned different specification identifiers. Basic information 162 is basic information about the application, including the application name, release date, and summary. First information 163 is information about the table configuration, including table names, item names, data types, and relationship information. Second information 164 is information about screens, including screen names and information about screen transitions. Third information 165 is information about the screen layout, including the screen size, frame configuration, component types, placement, and attribute information.

App information 171 is information about an application, including classification, schema name, app name, app identifier, icon information, app description, and compatible specification identifier. The app identifier is an identifier that uniquely identifies the data in app information 171. Fourth information 172 is information that includes the same items as first information 163, with the addition of detailed information such as table descriptions and notes for each item. Fifth information 173 is information that includes the same items as second information 164 and third information 165, with the addition of detailed information such as link information and display content information.

As shown in FIG. 2, the specification identifiers of basic information 162, first information 163, second information 164, and third information 165 are linked to the specification identifier of specification information 161. Furthermore, the corresponding specification identifier of app information 171 is linked to the specification identifier of specification information 161. Furthermore, the app identifiers of fourth information 172 and fifth information 173 are linked to the app identifier of app information 171.

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 entered or when a required value is not entered.

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

Figure 2 shows an example of a screen 1101 that displays a list of specification names. Screen 1101 is mainly composed of a menu section 1101a, a selection section 1101b, a button section 1101c, and a list section 1101d. Menu section 1101a displays "Home" and "Design" as selectable options. Selection section 1101b displays "Specification Management," "Classification Management," and "Version Information" as selectable options. Button section 1101c is configured to allow selection of functions required for screen 1101.

Figure 3 shows the state when "Home" is selected in the menu section 1101a and "Specification Management" is selected in the selection section 1101b.

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 memory unit 150. If 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 highest version value in the list section 1101d. If no specification information 161 is stored in the memory unit 150, the specification management unit 111 does not display anything in the list section 1101d.

In response to a user operation, the specification management unit 111 displays a screen 1102 for creating or updating specification information 161 on the display unit 130, as shown in FIG. 4. The user inputs values via the input unit 140. If the user performs a new creation operation, only "Save as New" may be displayed as the save method 1102a, and "1" may be displayed as the version 1102b. If the user performs an edit operation, the specification management unit 111 may display a dialog for selecting the version to edit. The specification management unit 111 may display screen 1102 after the user selects a version. In this case, "Overwrite" and "Version Upgrade" may be displayed as the save method 1102a. If the user selects "Overwrite," the value of the version selected by the user may be displayed as version 1102b. If the user selects "Version Upgrade," the value obtained by adding 1 to the value of the highest version of the specification information 161 having the specification number selected by the user may be displayed as version 1102b. The specification management unit 111 creates or updates specification information 161 based on the input values and stores it in the storage unit 150 together with the specification identifier.

For example, if the selected saving method 1102a in FIG. 4 is "New Saving," the specification management unit 111 stores new specification information 161 in the storage unit 150 based on the input values. Also, for example, if the selected saving method 1102a is "Overwrite," the specification management unit 111 overwrites the selected version of specification information 161 with the input values and stores the overwritten version in the storage unit 150. Also, for example, if 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 values.

(2-2-2) Basic Processing Unit The basic processing unit 112 creates or updates basic information 162 of an 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 .

Figure 5 shows an example of a screen 1103 for creating basic information 162. 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 content of menu section 1103a is the same as that of menu section 1101a. Function section 1103b is configured to allow selection of functions required for screen 1103. Selection section 1103c displays "basic information," "first information," "second information," and "third information" in a selectable manner.

Figure 5 shows the state when "Design" is selected in the menu section 1103a and "Basic Information" is selected in the selection section 1103c.

The basic processing unit 112 displays values in the content section 1103d based on the basic information 162 stored in the memory unit 150. If the basic information 162 is not stored in the memory 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 multiple example sentences. The basic processing unit 112 creates or updates the basic information 162 based on the input values and stores it in the memory unit 150.

(2-2-3) First Processing Unit 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 (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.

Figure 6 shows an example of a screen 1104 for creating or updating the first information 163, which includes table names, field names, and data types. 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 menu section 1104a and first selection section 1104c are the same as those of menu section 1101a and selection section 1103c, respectively. The function section 1104b is configured to allow selection of functions required for screen 1104. The second selection section 1104d displays "Table Definition" and "Relationship" as selectable options. The third selection section 1104f displays "Description," "Design," and "Data" as selectable options.

Figure 6 shows the state in which "Design" is selected in the menu section 1104a, "First Information" in the first selection section 1104c, "Table Definition" in the second selection section 1104d, and "Design" in the third selection section 1104f.

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 memory unit 150. Figure 6 shows the 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 memory unit 150. If the first information 163 is not stored in the memory 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 values via the input unit 140. The first processing unit 113 creates or updates the first information 163 based on the input values and stores it in the memory unit 150.

Figure 7 shows an example of a screen 1105 for creating or updating relationship information, which is the first information 163. 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 menu section 1105a, first selection section 1105c, and second selection section 1105d are the same as the display contents of menu section 1101a, first selection section 1104c, and second selection section 1104d, respectively. Function section 1105b is configured to allow the functions required for screen 1105 to be selected.

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

The first processing unit 113 displays the table name and item name in the content section 1105e based on the first information 163 stored in the memory unit 150. Furthermore, the first processing unit 113 displays a diagram showing relationship information in the content section 1105e based on the first information 163 stored in the memory unit 150. If the first information 163 is not stored in the memory 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 memory unit 150, the first processing unit 113 displays only the table name and item name in the content section 1105e. The content section 1105e in Figure 7 shows a state in which relationship information is set between the department ID of the employee table and the department ID of the department table. Furthermore, the qualification table shows a state in which relationship information is not set. The user inputs 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.

The user can set relationship information by, for example, selecting the field name of the table for which a relationship is to be set by clicking with the mouse, and then dragging and dropping it onto the field name of the table to which the relationship is to be established. Tables used to create relationship information may include tables linked from external systems.

(2-2-4) Second Processing Unit 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 (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.

Figure 8 is an example of a screen 1106 for creating or updating a screen name, which is second information 164. 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 menu section 1106a and first selection section 1106c are the same as the display contents of menu section 1101a and selection section 1103c, respectively. Function section 1106b is configured to allow the selection of functions required for screen 1106. Second selection section 1106d displays "Screen list" and "Screen transition" as selectable options.

Figure 8 shows the state in which "Design" is selected in the menu section 1106a, "Second Information" is selected in the first selection section 1106c, and "Screen List" is selected in the second selection section 1106d.

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 memory unit 150. If the screen names of the second information 164 are not stored in the memory unit 150, the second processing unit 114 does not display anything in the list section 1106e. The user inputs values via the input unit 140. The second processing unit 114 creates or updates the second information 164 based on the input values and stores it in the memory unit 150.

Figure 9 is an example of a screen 1107 for creating or updating information about screen transitions, which is second information 164. Here, the information about screen transitions includes information about the source screen, destination screen, and default screen. 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 menu section 1107a, first selection section 1107c, and second selection section 1107d are the same as the display contents of menu section 1101a, selection section 1103c, and second selection section 1106d, respectively. The function section 1107b is configured to allow the selection of functions required for screen 1107.

Figure 9 shows the state in which "Design" is selected in the menu section 1107a, "Second Information" is selected in the first selection section 1107c, and "Screen Transition" is selected in the second selection section 1107d.

The second processing unit 114 displays a screen transition diagram in the content section 1107e based on information about screen transitions in the second information 164 stored in the memory unit 150. If information about screen transitions in the second information 164 is not stored in the memory unit 150, the second processing unit 114 displays nothing in the content section 1107e. The second processing unit 114 displays the names of screens that have not yet been placed in the list section 1107f in a selectable list format, for example. The content section 1107e in Figure 9 shows a state in which transitions from the menu screen to screens A1 and B1 are possible, and transitions from screen A1 to screen A11 are possible. The user creates or updates information about screen transitions via the input unit 140. The second processing unit 114 creates or updates the second information 164 based on the created or updated information about screen transitions, and stores it in the memory unit 150.

The user can select a screen name in the list section 1107f by clicking it with the mouse, and then drag and drop it into the content section 1107e, thereby displaying the screen name in the content section 1107e. Also, a screen transition diagram can be created by dragging and dropping the source screen and the destination screen, for example.

(2-2-5) Third Processing Unit The third processing unit 115 creates or updates third information 165, which is information for creating the layout of an application screen, and stores the third information 165 in the storage unit 150. The third processing unit 115 also displays screens for creating the third information 165, including screens 1108 and 1109, on the display unit 130. Here, the information for creating the screen layout includes, for example, screen size, frame configuration, component types, placement, attribute information, and background images. The component types indicate the types of elements that make up the screen, such as labels, text fields, text areas, numeric fields, date fields, check boxes, radio buttons, and command buttons. The attribute information of the component includes settings such as the font of characters displayed in the component and the image size. The information for creating the screen layout is written, 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, it grays out buttons and input fields, etc. for creating or editing the third information 165, so as not to accept input of the third information 165.

Figure 10 is an example of a screen 1108 for creating or updating a frame configuration, which is the third information 165. 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 menu section 1108a and first selection section 1108c are the same as the display contents of menu section 1101a and selection section 1103c, respectively. The function section 1108b is configured to allow selection of functions required for screen 1108. The second selection section 1108d displays screen names stored in storage section 150 so that each screen name can be selected. The list section 1108f displays frame configurations so that they can be selected in a list format, etc.

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

The third processing unit 115 displays the screen layout in the content section 1108e based on the third information 165 of screen A1 stored in the memory unit 150. If the third information 165 of screen A1 is not stored in the memory 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 memory unit 150.

Figure 11 is an example of a screen 1109 for creating or updating the type and arrangement of components, which is third information 165. 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 menu section 1109a, first selection section 1109c, and second selection section 1109d are the same as the display contents of menu section 1101a, selection section 1103c, and second selection section 1108d, respectively. Function section 1109b is configured to allow the selection of functions required for screen 1109. List section 1109f displays components in a selectable format, such as a list.

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

The third processing unit 115 displays the screen layout in the content section 1109e based on the third information 165 of screen A1 stored in the memory unit 150. If the third information 165 of screen A1 is not stored in the memory 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 memory unit 150.

The user can select a component in the list section 1109f by clicking it with the mouse, and then drag and drop it onto the screen layout in the content section 1109e to arrange the component. The third processing unit 115 displays the screen layout in which the components have been arranged in the content section 1109e in response to the user's operation. The user can select a component in the content section 1109e by clicking it with the mouse, and then drag and drop it to change the placement position, size, etc. Furthermore, the user can select a component in the content section 1109e by clicking it with the mouse, and then select from a list or pull-down menu to change attribute information such as the font and color of the text.

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 or when a required value is not input.

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

Figure 12 is an example of a screen 1110 that displays a list of app names. 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 selectable options such as "Home," "Table Design," and "Screen Design." The selection section 1110b displays selectable options such as "App Management," "Table Management," and "Job Flow Management." The button section 1110c is configured to allow selection of functions required for screen 1110.

Figure 12 shows the state when "Home" is selected in the menu section 1110a and "App Management" is selected in the selection section 1110b.

The creation unit 121 displays a list of app names in the list section 1110d based on the app information 171 stored in the storage unit 150. If no app information 171 is stored in the storage unit 150, the creation unit 121 does not display anything in the list section 1110d.

In response to a user operation, the creation unit 121 displays a screen 1111 for creating app 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 allow the user to select specification information 161 stored in the storage unit 150. The setting unit 1111b is configured to allow the user to input part of the app information 171. The user selects the specification information 161 to be linked and inputs part of the app information 171 via the input unit 140.

In response to a user 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 first information 163, second information 164, and third information 165 associated with the selected specification identifier. If 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, if the required 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 app identifier and stores it in the storage unit 150 as app 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 in the design information 160 indicating whether or not the implementation information 170 has been created. The creation unit 121 stores the acquired first information 163 as fourth information 172 in the storage unit 150, and stores the acquired second information 164 and third information 165 as fifth information 173 in the storage unit 150. Regarding the information on screen transitions that is the second information 164, the creation unit 121 may store only information on a default screen as fifth information 173 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 app 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 the 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 the table in the schema. Furthermore, the creation unit 121 creates or updates the relationship of the 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.

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

Figure 14 is an example of a screen 1112 for creating or updating the fourth information 172, which includes the table name, item name, data type, and notes. 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 content of menu section 1112a is the same as the display content of menu section 1110a. Function section 1112b is configured to allow the selection of functions required for screen 1112.

Figure 14 shows the state when "Table Design" is selected in the menu section 1112a.

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 memory unit 150. If the table name of the fourth information 172 is not stored in the memory unit 150, the fourth processing unit 122 does not display anything in the list section 1112c. The fourth processing unit 122 displays the definition contents of the table linked to the table name specified in the list section 1112c in the content section 1112d based on the item names, data types, etc. of the fourth information 172 stored in the memory unit 150. If the item names, data types, etc. of the fourth information 172 are not stored in the memory unit 150, the fourth processing unit 122 displays each item in the content section 1112d as blank. The user inputs values via the input unit 140. The fourth processing unit 122 creates or updates the fourth information 172 based on the input values and stores it in the memory unit 150. In addition, the fourth processing unit 122 creates or updates the table configuration within the schema based on the created or updated fourth information 172.

The fourth processing unit 122 displays a screen (not shown) on the display unit 130 for creating or updating relationship information, which is the fourth information 172. The fourth processing unit 122 displays the relationship status based on the fourth information 172 stored in the memory unit 150. The user inputs 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 memory unit 150. The fourth processing unit 122 also creates or updates relationships between tables in the schema based on the created or updated fourth information 172.

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

(2-3-3) Fifth Processing Unit The fifth processing unit 123 creates or updates fifth information 173, which is information for creating application screen information and screen layouts, and stores the information 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).

Figure 15 is an example of a screen 1113 for implementing an application screen. 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 content of menu section 1113a is the same as the display content of menu section 1110a. The function section 1113b is configured to allow the functions required for screen 1113 to be selected.

Figure 15 shows the state when "Screen Design" is selected in the menu section 1113a.

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 memory 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 memory unit 150. If the fifth information 173 is not stored in the memory 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 for setting the screen layout for screen 1113 may be the same as the method for setting the screen layout for 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 for command buttons arranged in the screen layout. Furthermore, for example, the user can set the content to be displayed in a component, such as a text field arranged in the screen layout, by specifying a table name and an item name. 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.

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

In response to a user operation, the reflection unit 124 displays a screen 1114 for updating the design information 160, as shown in FIG. 16. The screen 1114 is mainly composed of an application selection unit 1114a and a specification selection unit 1114b. The reflection unit 124 displays the application information 171 selected by the user in the application selection unit 1114a. The reflection unit 124 also displays the specification information 161 linked to the corresponding specification identifier of the selected application information 171 in the specification selection unit 1114b.

In response to a user operation, the reflection unit 124 acquires an app identifier (hereinafter referred to as the selected app identifier) associated with the selected app information 171, and acquires fourth information 172 and fifth information 173 associated with the selected app identifier. The reflection unit 124 also acquires a corresponding specification identifier associated with the selected app information 171. The reflection unit 124 acquires specification information 161 associated with the corresponding specification identifier. Based on the acquired specification information 161, the reflection unit 124 creates new specification information 161 with a different version value from the acquired specification information 161, and stores the new specification information 161 in the storage unit 150. Specification information 161 with a different version value is, in other words, new specification information 161 with a different specification identifier. The reflection unit 124 also 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.

(3) Description of Application Development Using Application Development System The flow of application development using the application development system 100 will be described using 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 consistent range. 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 consistent range.

(3-1) Creation of Design Information The flow of creating new design information 160 using the application development system 100 will be described with reference to FIG.

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

When the user selects a specification name in the list section 1101d by clicking it with the mouse, etc., 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 that specification name (hereinafter referred to as the selected specification). The basic processing section 112 displays each item in the content section 1103d as blank.

When the user enters values into each input field in the content section 1103d and instructs saving, the basic processing unit 112 stores the entered values as basic information 162 in the memory unit 150. This creates basic information 162 for the application (step S12).

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

When the user inputs a table name and table definition on screen 1104 and instructs saving, the first processing unit 113 stores the input information as first information 163 in the storage unit 150. This creates the table name and table definition, which are the first information 163 of the application (step S13).

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

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

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

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

When the user presses "Screen Transition" in the second selection section 1106d, the second processing unit 114 displays a screen 1107 related to the selected specifications. The second processing unit 114 displays the screen name stored as the second information 164 in the list section 1107f, and displays nothing in the content section 1107e.

When the user inputs information about screen transitions on screen 1107 and instructs saving, the second processing unit 114 stores the input information as second information 164 in the storage unit 150. This creates information about screen transitions, which is the second information 164 of the application (step S16).

When the user presses "Third Information" in the first selection section 1107c, the third processing section 115 displays a screen 1108 for creating third information 165 related to the selected specifications. The third processing section 115 displays a blank screen layout in the content section 1108e.

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

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

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

(3-2) Creation of Implementation Information The flow of creating new implementation information 170 using the application development system 100 will be described with reference to FIG.

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

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

The creation unit 121 creates app information 171, fourth information 172, and fifth information 173 based on the specification information 161 selected by the user and the input values in the setting unit 1111b, and stores them in the storage unit 150. The creation unit 121 also checks the existence of tables in the schema based on the schema name of the app information 171 and the fourth information 172, and then creates or updates the tables in the schema. This creates implementation information 170 (step S22). The creation unit 121 displays the created app information 171 in the list unit 1110d.

When the user selects an app name in the list section 1110d by clicking it with the mouse, for example, and then presses "Table Design" in the menu section 1110a, the fourth processing unit 122 displays a screen 1112 for creating or updating fourth information 172 related to that app name (hereinafter referred to as the selected app). On the screen 1112, the fourth processing unit 122 displays the fourth information 172 stored in the memory unit 150.

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

When the user instructs the function unit 1112b to display relationship information, the fourth processing unit 122 displays a screen (not shown) for creating or updating relationship information related to the selected app.

When the user inputs relationship information and instructs it to be saved, the fourth processing unit 122 stores the input information in the storage unit 150 as fourth information 172. This creates table relationship information, which is the fourth information 172 of the application. The fourth processing unit 122 also creates or updates table relationships within the schema based on the input fourth information 172 (step S24).

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 app. The fifth processing section 123 displays the fifth information 173 stored in the memory section 150 in the list section 1113c and the content section 1113d.

When the user creates a screen name and screen layout on screen 1113 and instructs it to be saved, the fifth processing unit 123 stores the input content in the storage unit 150 as fifth information 173. This creates the screen name and screen layout, which are the fifth information 173 of the application (steps S25 and S26).

(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.

When a user instructs the application development system 100 to launch screen 1110 for displaying a list of app names, the reflection unit 124 displays screen 1110.

When the user selects an app name in the list section 1110d by clicking it with the mouse, for example, and then presses the "Link" button in the button section 1110c, the reflection unit 124 displays a screen 1114 for updating the design information 160 of the selected app (step S31).

When the user issues a reflection instruction, the reflection unit 124 creates new specification information 161, first information 163, second information 164, and third information 165 based on the app information 171 of the app selection unit 1114a and the specification information 161 of the specification selection unit 1114b, and stores them in the memory unit 150 (step S32).

(4) Features When changing specifications in general application development, the designer manually changes the specifications, and the implementer then changes the implementation accordingly. Also, if the implementation is changed first, the specification is manually changed accordingly.

However, application development using application development support systems, which have been gaining attention in recent years, is often carried out by people without specialized application development expertise, making it difficult to ensure consistency between specifications and implementation.

(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 specifications and the implementation.

(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 about tables used in the application. The second processing unit 114 creates second information 164, which is information about the application screen. The third processing unit 115 creates third information 165, which is information for creating the screen layout.

(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 tables used in the application.

(4-4)
In the application development system 100 of this embodiment, the second information 164 includes information about screen names and screen transitions. With this configuration, the design unit 110 can create information about screens used in the application.

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

(4-6)
In the application development system 100 of this embodiment, the implementation unit 120 includes a creation unit 121. The creation unit 121 creates part of the implementation information 170, which is information necessary for implementation, based on the design information 160. Because the design information 160 includes information about tables and screens necessary for implementation, the creation unit 121 can create 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.

(4-7)
In the application development system 100 of this embodiment, the implementation unit 120 includes a reflection unit 124. After the implementation information 170 is updated, the reflection unit 124 reflects the updated content in the design information 160. Because 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 specifications and the implementation.

(4-8)
In the application development system 100 of this embodiment, when the reflection unit 124 reflects the implementation information 170 into the design information 160, new specification information 161, first information 163, second information 164, and third information 165, each having a different specification identifier, are created and stored in the storage unit 150. This configuration makes it possible to store the change history of the design information 160.

(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.

(4-10)
In the application development system 100 of this embodiment, when the reflecting unit 124 displays the design information 160 on which the implementation information 170 is reflected, 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. This configuration makes it possible to restrict updates to the design information 160 on which the implementation information 170 is reflected. As a result, it is easy to ensure consistency between the specifications and the implementation.

(5) Modifications (5-1) Modification A
In this embodiment, the basic information 162 is created, but the creation of the basic information 162 may be omitted.

(5-2) Modification B
In this embodiment, the table name and the table definition content are created as the first information 163, but the table to be created may have only an ID (identification information) column. In this case, the creation unit 121 may also create or update a table within the schema.

(5-3) Modification C
In this embodiment, information relating to screen transitions is created as the second information 164, but creation of the information relating to screen transitions may be omitted.

(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 as defined in the claims.

100 Application development system 110 Design unit 113 First processing unit 114 Second processing unit 115 Third processing unit 120 Implementation unit 121 Creation unit 124 Reflection unit 160 Design information 163 First information 164 Second information 165 Third information 170 Implementation information

Japanese Patent Application Laid-Open No. 2022-059478

Claims (5)

An application development system (100) for supporting application development,
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;
The design unit has a first processing unit (113) for creating first information (163) which is information on a table used in the application,
the first information includes a table name, an item name, a data type, and relationship information;
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,
the creation unit creates table relationships based on the implementation information.
Application development system. The design unit
a second processing unit (114) for creating second information (164) which is information on the 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 . The second information includes a screen name and information related to a screen transition.
The application development system according to claim 2 . the third information includes a screen size, a frame configuration, a type of component, an arrangement, and attribute information;
4. The application development system according to claim 2 or 3. The implementation unit further includes a reflection unit (124) that reflects the updated content of the implementation information in the design information after the implementation information is updated.
The application development system of claim 1 .