Information processing device, information processing method, and program

Abstract

To enable the determination of whether an application created by the user to register records meets predetermined conditions. [Solution] The information processing device includes an acquisition unit that acquires application information including information set in a user-configurable item, relating to an application that includes one or more fields for receiving input of values ​​to be registered as records, and which includes user-configurable items; a determination unit that determines whether the configured information included in the acquired application information satisfies predetermined conditions relating to the information set in the configurable item; and an output unit that outputs the result of the determination.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] Conventionally, techniques for diagnosing the presence or absence of defects in applications from a security perspective have been studied (for example, Patent Document 1).

[0003] On the other hand, in recent years, tools for assisting in creating applications with no-code or low-code have become widespread. In such tools, a user can easily create an application capable of recording records including values input into fields by arranging fields prepared in advance on the application screen.

Summary of the Invention

Problems to be Solved by the Invention

[0004] Due to the spread of such tools as described above, even those with little programming experience can easily create applications. This means that there is a possibility that applications not conforming to conditions (for example, conditions regarding the use of applications such as specifications) predetermined within an organization or the like for applications may be created by those with immature IT literacy. However, in the prior art, it is not possible to determine the conformity of such applications to predetermined conditions.

[0005] The present invention has been made in view of the above points, and an object thereof is to enable determination of the conformity of an application for registering records, created according to user settings, to predetermined conditions.

Means for Solving the Problems

[0006] To solve the above problems, the information processing device includes an acquisition unit that acquires application information including information set in a user-configurable item, relating to an application that includes one or more fields for receiving input values ​​to be registered as records, and which includes user-configurable items; a determination unit that determines whether the configured information included in the acquired application information satisfies predetermined conditions relating to the information set in the configurable item; and an output unit that outputs the result of the determination. [Effects of the Invention]

[0007] It is possible to determine whether an application created by the user to register records meets predetermined conditions. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the system configuration in the first embodiment. [Figure 2] This figure shows an example of the hardware configuration of the application diagnostic device 10 in the first embodiment. [Figure 3] This figure shows an example of the functional configuration of the application creation device 20 and the application diagnostic device 10 in the first embodiment. [Figure 4] This diagram shows an example of the home screen display for an app creation service. [Figure 5] This figure shows an example of the display of the business application creation screen. [Figure 6] This figure shows an example of the business application creation screen after the business application creation process is complete. [Figure 7] This is a sequence diagram illustrating an example of the processing procedure for creating a business application in the first embodiment. [Figure 8] This diagram shows an example of updating the home screen after creating a business application. [Figure 9] This figure shows an example of how the initial screen of an app looks. [Figure 10]It is a diagram showing an example of the display of an app screen. [Figure 11] It is a diagram showing an example of the configuration of a daily report DB. [Figure 12] It is a diagram showing an example of the display of the initial app screen after record registration. [Figure 13] It is a sequence diagram for explaining an example of the processing procedure of the diagnostic processing of a business app in the first embodiment. [Figure 14] It is a diagram showing an example of the display of an app selection screen in the first embodiment. [Figure 15] It is a flowchart for explaining an example of the processing procedure of the diagnostic processing of a business app in the first embodiment. [Figure 16] It is a diagram showing an example of diagnostic items in the first embodiment. [Figure 17] It is a diagram showing an example of diagnostic results in the first embodiment. [Figure 18] It is a diagram showing an example of the display of a diagnostic item selection screen. [Figure 19] It is a diagram showing an example of the display of a threshold setting screen. [Figure 20] It is a diagram showing an example of the functional configuration of an app creation device 20 and an app diagnostic device 10 in the fourth embodiment. [Figure 21] It is a sequence diagram for explaining an example of the processing procedure of the diagnostic processing of a business app in the fourth embodiment. [Figure 22] It is a flowchart for explaining an example of the processing procedure of the diagnostic processing of a business app in the fourth embodiment. [Figure 23] It is a diagram showing an example of diagnostic items in the fourth embodiment. [Figure 24] It is a diagram showing an example of diagnostic results in the fourth embodiment.

Modes for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present invention will be described based on the drawings. FIG. 1 is a diagram showing an example of a system configuration in the first embodiment. In FIG. 1, one or more user terminals 30 are connected to an application creation device 20 and an application diagnosis device 10 via a network such as a LAN (Local Area Network) or the Internet. The application diagnosis device 10 is connected to the application creation device 20 via a network such as a LAN or the Internet.

[0010] The application creation device 20 is one or more computers that provide a service (hereinafter referred to as the "application creation service") for assisting in the creation of applications without code or with low code. The application is created by determining the arrangement positions on the screen for one or more fields for receiving input of values to be registered as records. The service may be provided as a cloud service. In the present embodiment, an example of creating an application used in business (hereinafter referred to as a "business application") will be described, but the present embodiment is also applicable to applications for other uses than business.

[0011] Users of the application creation service can create a business application by setting configurable items. More specifically, the user arranges any one or more fields from a plurality of types of fields (setting items) prepared in advance on the screen (form) of the business application through a GUI (Graphical User Interface), and sets a name (hereinafter referred to as the "field name") etc. for each field, so that a business application that can record a record including the value input for each field associated with the field name of the field in a database or the like can be created. The types of fields are distinguished by the type of value input to the field. Examples of the type include a character string, a numerical value, an attached file, etc.

[0012] The user terminal 30 is a terminal used by users who create business applications using the application creation device 20. The user terminal 30 also requests the application diagnostic device 10 to diagnose the business application selected by the user. Diagnosing a business application means determining whether or not the business application meets predetermined conditions (e.g., specifications) set in advance.

[0013] The application diagnostic device 10 is one or more computers that perform diagnostics on business applications requested by user terminals 30, and is an example of an information processing device.

[0014] Figure 2 shows an example of the hardware configuration of the application diagnostic device 10 in the first embodiment. As shown in Figure 2, the application diagnostic device 10 is built by a computer and includes a CPU 101, ROM 102, RAM 103, HD 104, HDD (Hard Disk Drive) controller 105, display 106, external device connection I / F (Interface) 108, network I / F 109, data bus 110, keyboard 111, pointing device 112, DVD-RW (Digital Versatile Disk Rewritable) drive 114, and media I / F 116.

[0015] Of these, the CPU 101 controls the operation of the entire application diagnostic device 10. The ROM 102 stores programs used to drive the CPU 101, such as the IPL. The RAM 103 is used as the work area for the CPU 101. The HD 104 stores various data such as programs. The HDD controller 105 controls the reading or writing of various data to the HD 104 according to the control of the CPU 101. The display 106 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 108 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I / F 109 is an interface for data communication using the communication network 100. The data bus 110 is an address bus and data bus, etc., for electrically connecting each component such as the CPU 101 shown in Figure 2.

[0016] The keyboard 111 is a type of input means equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 112 is a type of input means for selecting and executing various instructions, selecting processing targets, and moving the cursor. The DVD-RW drive 114 controls the reading or writing of various data to the DVD-RW 113, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may also be DVD-R, etc. The media I / F 116 controls the reading or writing (storage) of data to the recording medium 115, such as flash memory.

[0017] The application creation device 20 and the user terminal 30 may also have the same hardware configuration as shown in Figure 2. The application creation device 20 and the application diagnostic device 10 may be implemented using the same computer. Figure 3 shows an example of the functional configuration of the application creation device 20 and the application diagnostic device 10 in the first embodiment. In Figure 3, the application creation device 20 has a UI unit 21 and an application creation unit 22. Each of these units is realized by processing that one or more programs installed in the application creation device 20 cause the CPU of the application creation device 20 to execute. The application creation device 20 also utilizes an application information storage unit 23. The application information storage unit 23 can be realized, for example, using the HD of the application creation device 20, or a storage device that can be connected to the application creation device 20 via a network.

[0018] The UI unit 21 provides a GUI (e.g., a web page) for creating business applications to the user terminal 30 and accepts input from the user of information necessary for creating business applications (hereinafter referred to as "input information"). Specifically, the UI unit 21 accepts input of the placement location of one or more fields from a plurality of pre-prepared field types for the business application form (screen), as well as the field name for those fields. The UI unit 21 also accepts input of the name of the business application to be created, an icon representing the business application, etc. Therefore, the input information includes the application name, icon (icon name), field names and location information of each placed field, etc. Note that the input information is an example of information set in the items that can be set for the business application. In other words, the business application is created when the user sets these items. The application name may be a value that is set in advance as an initial value, and the icon may be an image that is set in advance as an initial image.

[0019] The application creation unit 22 creates a business application based on the input information. Specifically, the application creation unit 22 displays a screen containing each field placed in the business application, accepts input values ​​for each field through the screen, and creates the business application to register the input values ​​for each field in a database or the like, associating them with the field names of each field. It also generates information about the created business application (hereinafter referred to as "application information").

[0020] The application creation unit 22 stores the application information generated by the application creation unit 22 in the application information storage unit 23. The application information includes the application name, application ID, icon, and field information for each field. Field information includes the field name, field type, and position information on the form.

[0021] On the other hand, the application diagnostic device 10 has an input unit 11, an acquisition unit 12, a determination unit 13, and an output unit 14. Each of these units is realized by processing that one or more programs installed on the application diagnostic device 10 cause the CPU 101 to execute. The application diagnostic device 10 also utilizes a determination criteria storage unit 15. The determination criteria storage unit 15 can be realized, for example, using an HD 104 or a storage device that can be connected to the application diagnostic device 10 via a network.

[0022] The input unit 11 accepts information from the user that is necessary for diagnosing the business application. For example, the input unit 11 accepts the selection of the business application to be diagnosed.

[0023] The acquisition unit 12 acquires application information of the business application from the application information storage unit 23.

[0024] The determination unit 13 determines whether the business application satisfies predetermined conditions. More specifically, the determination unit 13 determines whether the application information acquired by the acquisition unit 12 satisfies the conditions that are set in advance and relate to the information set in the user-configurable items. The determination unit 13 identifies the conditions to be used for the determination based on the information stored in the determination criteria storage unit 15.

[0025] The output unit 14 outputs the result of the determination made by the determination unit 13.

[0026] The following describes the processing procedures performed by the application creation device 20 or the application diagnostic device 10. First, the processing procedures performed by the application creation device 20 when creating a business application will be described.

[0027] When the user terminal 30 accesses the application creation device 20, the UI unit 21 of the application creation device 20 displays the home screen of the application creation service on the user terminal 30.

[0028] Figure 4 shows an example of the home screen display of the app creation service. In Figure 4, the home screen 510 includes an app list 511 and an app creation button 512. The app list 511 is an area that displays a list of app names of business applications that have already been created. The app names of business applications that have already been created can be identified by referring to the app information storage unit 23. The app creation button 512 is a button for receiving instructions to create a new business application.

[0029] When the user presses the app creation button 512, the UI unit 21 displays the business application creation screen on the user terminal 30.

[0030] Figure 5 shows an example of the display of the business application creation screen. In Figure 5, the business application creation screen 520 includes an icon area 521, an application name area 522, a field area 523, a form area 524, a cancellation button 525, and an application creation button 526, and is a screen that provides a predetermined format for creating a business application. In other words, the business application is created based on the format of the business application creation screen 520.

[0031] The icon area 521 is an area for selecting an icon for the business application to be created (hereinafter referred to as the "target application"), and is also the area where the selected icon is displayed. Specifically, in the initial state, the icon area 521 displays an initial image. The initial image is the default icon as the initial value. When the user performs a predetermined operation such as selection on the icon area 521, a list of candidate icons is displayed. When the user selects one icon from this list, that icon is displayed in the icon area 521. In other words, the user can customize the icon area 521 to set an icon suitable for the target application.

[0032] The application name area 522 is an area for accepting input of a string indicating the application name of the target application. Initially, the application name area 522 displays a default application name, such as "New Business Application". Users can customize it to enter an appropriate application name for the target application in the application name area 522.

[0033] Field area 523 is an area that displays a list of field types that can be selected as placement targets for the target application (hereinafter referred to as "field types").

[0034] Form area 524 is the area corresponding to the form (screen) of the target application. In its initial state, nothing is placed in form area 524.

[0035] The Cancel Creation button 525 is a button that accepts a command to cancel the creation of the target application. The Create Application button 526 is a button that accepts a command to proceed with the creation of the target application.

[0036] For example, the user first operates the icon area 521 to select the icon of the target app. Next, the user enters the app name of the target app into the app name area 522.

[0037] Next, the user drags and drops one of the field types included in the field area 523 to any location in the form area 524, thereby placing a field of that field type at the drop location. The user then sets a field name for the placed field. If multiple fields are to be placed on the form of the target application, the user repeats the process of placing the field types and setting the field names. Figure 5 shows an example where a field of type string is placed in the form area 524.

[0038] Once the above steps are completed, the business application creation screen 520 will look like Figure 6, for example.

[0039] Figure 6 shows an example of the business application creation screen after the business application creation process is complete. In Figure 6, the same parts as in Figure 5 are denoted by the same symbols. In Figure 6, an icon is selected and "Daily Report App" is entered as the application name. It also shows an example where four fields, whose field names are "Date," "Work Details," "Impressions," and "Goal Achievement," are placed in form area 524. The field type for "Date" is "Date," the fields for "Work Details" and "Impressions" are "Text," and the field type for "Goal Achievement" is "Radio Button." As the name of the application ("Daily Report App") suggests, the target application with these fields is a business application that supports the creation of daily reports. Users of the target application can electronically record their daily reports by entering values ​​into the fields of the target application.

[0040] When the application creation button 526 is pressed on the business application creation screen 520 in Figure 6, the processing procedure in Figure 7 is executed.

[0041] Figure 7 is a sequence diagram illustrating an example of the processing steps for creating a business application in the first embodiment.

[0042] In step S110, the user terminal 30 sends input information for the business application creation screen 520 to the UI unit 21 of the application creation device 20 in response to the press of the application creation button 526. This input information includes the icon name of the icon displayed in the icon area 521, the application name displayed in the application name area 522, and the field information of each field located in the form area 524.

[0043] When the UI unit 21 receives the input information, it sends the input information to the application creation unit 22 (S120).

[0044] Next, the app creation unit 22 creates the target app based on the input information (S130). The creation of the target app generates app information based on the input information. Basically, the app information includes the app ID in addition to the information contained in the input information. Therefore, the app information includes the app ID, icon, app name, field information for each field, etc.

[0045] Next, the application creation unit 22 transmits the generated application information to the application information storage unit 23 (S140), and the application information storage unit 23 stores the application information (S150).

[0046] Next, the app creation unit 22 sends a display instruction to the UI unit 21 for the creation results of the target app (S160). This display instruction includes a list of app names for each app stored in the app information storage unit 23.

[0047] The UI unit 21 regenerates the home screen 510 based on the list of app names and displays the home screen 510 on the user terminal 30 (S170).

[0048] Figure 8 shows an example of updating the home screen after creating a business application. In Figure 8, the same parts as in Figure 4 are denoted by the same reference numerals. In the home screen 510 of Figure 8, the name of the target application ("Daily Report Application") has been newly added to the application list 511. The home screen 510 is a screen that is displayed to all users not only when creating a business application but also when using an existing business application, and users can select the business application to use from the application list 511. Therefore, when the home screen 510 as shown in Figure 8 is displayed, not only the user who created the target application but also other users can use the target application.

[0049] For example, when the home screen 510 shown in Figure 8 is displayed on the user terminal 30 of the user who created the target app or another user (hereinafter referred to as "app user"), if the app user selects "Daily Report App" in the app list 511, the UI unit 21 displays the target app's initial screen (hereinafter referred to as "app initial screen") on the user terminal 30 based on the target app's app information.

[0050] Figure 9 shows an example of the initial screen display of the application. In Figure 9, the initial screen 530 of the application includes a record list area 531 and an add record button 532.

[0051] The record list area 531 is an area that displays a list of records registered in the database corresponding to the target application (hereinafter referred to as the "daily report DB") based on values ​​previously entered by users of the target application (daily report application). In Figure 9, corresponding to the situation when the target application is used for the first time, no records have been registered in the daily report DB, so no records are displayed in the record list area 531. Note that an empty (without records registered) daily report DB may have been created in the auxiliary storage device of the application creation device 20 at the timing of step S130 in Figure 7.

[0052] The record addition button 532 is a button that accepts instructions to add (register) a new record (daily report) using the target application.

[0053] Therefore, if an app user wants to enter a daily report using the target app, they should press the Add Record button 532.

[0054] When the record addition button 532 is pressed, the UI unit 21 displays the main screen of the target application (hereinafter referred to as the "application screen") on the application user's terminal 30, based on the application information of the target application.

[0055] Figure 10 shows an example of the application screen display. In Figure 10, the application screen 540 includes an icon area 541, an application name area 542, a form 543, a cancel button 544, and a save button 545. The icon area 541 is the area where the icon of the target application is displayed. The application name area 542 is the area where the application name of the target application is displayed. The form 543 is the area that includes the fields set for the target application and accepts value input through each field. Note that since Figure 10 corresponds to Figure 6, the form 543 in Figure 10 contains the fields that were placed in the form area 524 of Figure 6. The cancel button 544 is a button that accepts the instruction to cancel input. The save button 545 is a button that accepts the instruction to save the values ​​entered in each field.

[0056] Note that while Figure 10 shows the state where values ​​have already been entered into each field, immediately after the display of the app screen 540, no values ​​have been entered into each field.

[0057] For example, when values ​​are entered into each field as shown in Figure 10 and the save button 545 is pressed, the application records (registers) a record containing the entered values ​​in the daily report database.

[0058] Figure 11 shows an example of the daily report database configuration. As shown in Figure 11, the daily report database is a database that has items corresponding to the field names of each field in the target application (daily report application), and stores the set of these items as a single record. The item name of each item matches the field name of each field in the target application. Therefore, the values ​​entered for each field on the application screen 540 are registered in the daily report database, corresponding to the field names of each field. Note that the contents of one record shown in Figure 11 correspond to Figure 10.

[0059] When the daily report database is in the state shown in Figure 11, and the display of the target application's initial screen 530 is instructed, the application's initial screen 530 will be displayed, for example, as shown in Figure 12.

[0060] Figure 12 shows an example of the initial screen display of the application after a record has been registered. In Figure 12, the same parts as in Figure 9 are denoted by the same reference numerals. In the initial application screen 530 of Figure 12, the record shown in Figure 11 has been added to the record list area 531.

[0061] Next, we will explain the diagnosis of the business application. The diagnosis of the business application is performed by the application diagnostic device 10. For convenience, the above also describes the phase in which the target application is used, but for example, the diagnosis of the target application may be performed before the target application is used. The execution of the diagnosis of the target application may be instructed by the user who created the target application, or by the administrator of the business application, etc.

[0062] Figure 13 is a sequence diagram illustrating an example of the processing procedure for the business application diagnostic process in the first embodiment. In the explanation of Figure 13, "user" may be the creator of the business application to be diagnosed, or the administrator of the business application. Furthermore, the timing of the execution of Figure 13 may be immediately after the creation of the business application to be diagnosed, or at any time after the start of use of the business application.

[0063] At the start of the processing procedure shown in Figure 13, the input unit 11 displays a screen (hereinafter referred to as the "application selection screen") on the user terminal 30 that allows the user to select the business application to be diagnosed from among the business applications whose application information is stored in the application information storage unit 23 (i.e., the business applications that have already been created).

[0064] Figure 14 shows an example of the display of the app selection screen in the first embodiment. In Figure 14, the app selection screen 550 includes a dropdown list 551, a diagnostic button 552, a plus button 553, and a "diagnose all apps" button 554, etc.

[0065] The dropdown list 551 is a display component that accepts the selection of a business application to be diagnosed from a list of application names of business applications whose application information is stored in the application information storage unit 23.

[0066] The diagnostic button 552 is a button that accepts a command to run a diagnostic for one business application selected in the dropdown list 551 adjacent to it on the left.

[0067] The plus button 553 is a button that accepts instructions to add a pair of dropdown list 551 and diagnostic button 552. By adding the pair of dropdown list 551 and diagnostic button 552, it becomes possible to select multiple business applications as targets for diagnosis.

[0068] The All Apps Diagnostic button 554 is a button that accepts a command to run a diagnostic for all multiple business applications when multiple business applications are selected by multiple dropdown lists 551, by adding a pair of dropdown lists 551 and a diagnostic button 552.

[0069] When one or more business applications are selected as targets for diagnosis by the user, and the diagnosis button 552 or the all-application diagnosis button 554 is pressed, the user terminal 30 sends a request to execute the diagnosis to the application diagnostic device 10 (S210). This execution request includes the application IDs of the one or more selected business applications.

[0070] When the input unit 11 receives the execution request, it forwards the execution request to the determination unit 13 (S220).

[0071] In response to the execution request, the determination unit 13 requests the acquisition unit 12 to acquire application information by specifying one or more application IDs included in the execution request (S230).

[0072] Next, the acquisition unit 12 acquires application information containing the specified application ID from the application information storage unit 23 for each application ID (S231, S232). The acquisition unit 12 then transmits one or more acquired application information to the determination unit 13 (S240).

[0073] Next, the determination unit 13 performs a diagnosis for each acquired application information (S250). At this time, the determination unit 13 identifies items corresponding to the conditions used for diagnosis (hereinafter referred to as "diagnosis items") by referring to the determination criteria storage unit 15.

[0074] Next, the determination unit 13 transmits the diagnosis result to the output unit 14 (S260).

[0075] The output unit 14 displays the diagnostic result on the user terminal 30 (S270).

[0076] Next, we will explain the details of step S250. Figure 15 is a flowchart illustrating an example of the processing procedure for the business application diagnostic process in the first embodiment. Below, we will explain the process performed for one of the business applications selected as the target of diagnosis (hereinafter referred to as the "target application"). If there are multiple business applications to be diagnosed, the same process should be performed for all of them.

[0077] Note that the processing procedure in Figure 15 assumes that the information stored in the judgment criteria storage unit 15 is as shown in Figure 16. The information shown in Figure 16 indicates that it should be determined whether or not the pre-set conditions are met for four diagnostic items: application name, icon, field name, and number of records.

[0078] In step S301, the determination unit 13 reads the application information of the target application (hereinafter referred to as "target application information").

[0079] Next, the judgment unit 13 performs a diagnosis regarding the diagnostic item "App Name" in Figure 16 in steps S302 to S305.

[0080] In step S302, the determination unit 13 determines whether the app name in the target app information is the same as the initial value. In other words, it determines whether the condition "the app name is different from the initial value" is satisfied. Since the initial value of the app name is common to all newly created business apps, if a business app is created with the app name remaining at the initial value, there is a high possibility that multiple business apps with the same app name will exist. In this case, it becomes more difficult to distinguish between each app.

[0081] If the app name in the target app information is the same as the default value (Yes in S302), the judgment unit 13 sets the judgment result for the diagnostic item "app name" to "needs improvement" and adds supplementary information indicating the improvement content (hereinafter referred to as "improvement information") to the judgment result (S303). In this case, the improvement information may be a message such as, "The app name is still the default setting. It is important to change the app name to something easily recognizable so that it is immediately clear who is using it and for what purpose."

[0082] Next, the determination unit 13 determines whether the application name of the target application information overlaps with the application name of other business applications (S304). In other words, it determines whether the condition "the application names do not overlap" is satisfied. The purpose of this condition is the same as the purpose of the condition "the application name is different from the initial value," but this condition is an example of a condition related to the comparison between two or more business applications. The application names of other business applications can be obtained from the application information stored in the application information storage unit 23 for those other business applications.

[0083] If the app name in the target app information is duplicated with the app name of another business app (Yes in S304), the judgment unit 13 sets the judgment result for the diagnostic item "App Name" to "Needs Improvement" and adds improvement information as supplementary information to the judgment result (S305). In this case, the improvement information may be a message such as, "The app name is duplicated. It is important to make the app name easily recognizable so that it is immediately clear who will use it and for what purpose."

[0084] Next, the judgment unit 13 performs a diagnosis regarding the diagnostic item "icon" in Figure 16 in steps S306 to S307.

[0085] In step S306, the determination unit 13 determines whether the icon of the target application is the same as the initial image. In other words, it determines whether the condition "the icon is different from the initial image" is satisfied. This is because the initial image of the icon is common to all newly created business applications, so if a business application is created with the same icon as the initial image, there will be multiple business applications with the same icon, making it highly likely that it will become impossible to visually distinguish between the business applications.

[0086] If the icon for the target app information is the same as the initial image (Yes in S306), the judgment unit 13 sets the judgment result for the diagnostic item "Icon" to "Needs Improvement" and adds improvement information as supplementary information to the judgment result (S303). In this case, the improvement information may be a message such as, "The app icon is still the default. It is important to make it an easily recognizable icon so that it is immediately clear who is using it and for what purpose."

[0087] The conditions related to steps S302 and S306 relate to the degree of customization from the initial values ​​or initial image.

[0088] Next, the determination unit 13 performs a diagnosis regarding the diagnostic item "field name" in Figure 16 in steps S308 to S309.

[0089] In step S308, the determination unit 13 determines whether or not there are duplicate field names within the application information of the target application. That is, it determines whether or not there are two or more fields with the same field name set for the target application. In other words, it determines whether or not the condition "field names are not duplicated" is satisfied. This is because if field names are duplicated, it may become difficult to distinguish between each field.

[0090] If field names are duplicated (Yes in S308), the determination unit 13 sets the determination result for the diagnostic item "field name" to "needs improvement" and adds improvement information to the determination result as supplementary information (S309). In this case, the improvement information may be a message such as, "There are duplicate field names. It is important to use clear and understandable field names."

[0091] Next, the determination unit 13 performs a diagnosis regarding the diagnostic item "number of records" in Figure 16 in steps S310 to S311.

[0092] In step S310, the determination unit 13 determines whether the number of records in the target application (the number of records in the daily report DB in the case of a daily report application) is equal to or greater than a threshold. In other words, it determines whether the condition "the number of records is less than a threshold" is met. This is because an increase in the number of records can degrade the performance of the target application due to increased load on the record reading process and increased memory consumption.

[0093] If the number of records is greater than or equal to the threshold (Yes in S310), the determination unit 13 sets the determination result for the diagnostic item "field name" to "needs improvement" and adds improvement information as supplementary information to the determination result (S311). In this case, the improvement information is, for example, a message such as "The number of records is greater than or equal to the threshold."

[0094] Note that the number of records in the target application increases after the application is put into use, so the diagnosis regarding the "number of records" is only valid after the application has been put into use. If the number of records in the target application exceeds a threshold, measures such as splitting the field set of the target application into two business applications may be considered to distribute the load on the target application.

[0095] Next, the judgment unit 13 integrates the judgment results for each diagnostic item to generate a diagnostic result (S350).

[0096] Figure 17 shows an example of the diagnostic results in the first embodiment. As shown in Figure 17, the diagnostic results are an integrated representation of the judgment results for each diagnostic item. For diagnostic items that meet the conditions (diagnostic items whose judgment result is not "needs improvement"), the "judgment result" is set to "no problem".

[0097] In step S260 of Figure 13, such diagnostic results are transmitted to the output unit 14, and in step S270, such diagnostic results are output (displayed).

[0098] Furthermore, the conditions for each diagnostic item may be stored in the judgment criteria storage unit 15. The judgment conditions in steps S302, S304, S306, S308, and S310 are examples of conditions related to the use of the application. The judgment conditions in steps S302, S304, S306, and S308 are also examples of conditions related to items that can be set by the user. The judgment conditions in steps S302 and S306 are also examples of conditions related to the degree of application customization. In addition, the judgment condition in step S308 is also an example of a condition related to a field.

[0099] As described above, according to the first embodiment, it is possible to determine whether an application for registering records, created by the user's settings, conforms to predetermined conditions (conditions based on specifications, etc.). As a result, the user can, for example, identify areas for improvement in the application.

[0100] Next, a second embodiment will be described. The differences between the second embodiment and the first embodiment will be described. Therefore, points not specifically mentioned may be the same as in the first embodiment.

[0101] In the second embodiment, when a business application to be diagnosed is selected on the application selection screen 550 (Figure 14) displayed at the start of the processing procedure in Figure 13, and the diagnosis button 552 or the all-application diagnosis button 554 is pressed, step S210 is not executed, but a diagnosis item selection screen is displayed on the user terminal 30.

[0102] Figure 18 shows an example of the display of the diagnostic item selection screen. In Figure 18, the diagnostic item selection screen 560 includes a selection area 561 and a diagnostic button 562, etc. The selection area 561 is an area that allows the user to select the diagnostic items to be diagnosed, with check buttons for each diagnostic item stored in the judgment criteria storage unit 15. In Figure 18, the state in which "App Name" and "Field Name" are selected is shown.

[0103] The diagnostic button 562 is a button that accepts the instruction to perform a diagnostic.

[0104] When one or more diagnostic items are selected in the selection area 561 by user operation and the diagnostic button 562 is pressed, in step S210 of Figure 13, the user terminal 30 sends a diagnostic execution request to the application diagnostic device 10. This execution request includes the application IDs of one or more business applications selected on the application selection screen 550 and the item names of one or more diagnostic items selected on the diagnostic item selection screen 560.

[0105] Steps S220 to S270 are the same as in the first embodiment, except for step S250. In Figure 15, which corresponds to step S250, only the steps related to the diagnostic items corresponding to the item names included in the diagnostic execution request are executed. For example, if "app name" and "field name" are the targets of the diagnosis, steps S306, S307, S310 and S311 are not executed. As a result, in the second embodiment, whether or not the target app is satisfied is determined only for the conditions corresponding to the diagnostic items selected by the user.

[0106] Furthermore, whether or not to display the diagnostic item selection screen 560 (i.e., whether to implement the first embodiment or the second embodiment) may be switchable by a setting.

[0107] Next, a third embodiment will be described. The differences between the third embodiment and the first embodiment will be described. Therefore, points not specifically mentioned may be the same as in the first embodiment.

[0108] In the third embodiment, when a business application to be diagnosed is selected on the application selection screen 550 (Figure 14) displayed at the start of the processing procedure in Figure 13, and the diagnosis button 552 or the all-application diagnosis button 554 is pressed, step S210 is not executed, but a threshold setting screen is displayed on the user terminal 30.

[0109] Figure 19 shows an example of the threshold setting screen. In Figure 19, the threshold setting screen 570 includes a threshold input area 571 and a diagnostic button 572, etc. The threshold input area 571 is an area for receiving input of a threshold value for the number of records, and in the initial state, an initial value is entered. In Figure 19, the state in which "20000" has been entered is shown.

[0110] When a threshold is entered into the threshold input area 571 through user operation and the diagnostic button 572 is pressed, in step S210 of Figure 13, the user terminal 30 sends a diagnostic execution request to the application diagnostic device 10. This execution request includes the application ID of one or more business applications selected on the application selection screen 550 and the threshold entered on the threshold setting screen 570.

[0111] Steps S220 to S270 are the same as in the first embodiment, except for step S250. In step S310 in Figure 15, which corresponds to step S250, the threshold included in the diagnostic execution request is used. As a result, in the third embodiment, a diagnosis can be performed on the diagnostic item "number of records" based on a threshold set by the user. This improves the flexibility of the diagnosis.

[0112] Furthermore, whether or not to display the threshold setting screen 570 (i.e., whether to implement the first embodiment or the third embodiment) may be switchable by a setting.

[0113] Furthermore, the second embodiment may be combined with the third embodiment. For example, when the diagnostic button 562 is pressed on the diagnostic item selection screen 560 (Figure 18) and the diagnostic item "number of records" is selected as the diagnostic target, the threshold setting screen 570 may be displayed.

[0114] Next, a fourth embodiment will be described. The differences between the fourth embodiment and the first embodiment will be described. Therefore, points not specifically mentioned may be the same as in the first embodiment.

[0115] The fourth embodiment describes an example that enables complex diagnoses, such as qualitative diagnosis and the discovery of similar apps.

[0116] Figure 20 shows an example of the functional configuration of the application creation device 20 and the application diagnostic device 10 in the fourth embodiment. In Figure 20, the same parts as in Figure 3 are denoted by the same reference numerals, and their descriptions are omitted.

[0117] In Figure 20, the application diagnostic device 10 further includes an AI control unit 16 and an interactive AI 17. The AI ​​control unit 16 and the interactive AI 17 are realized by processing that one or more programs installed on the application diagnostic device 10 cause the CPU 101 to execute. The interactive AI 17 may be located in a device connected to the application diagnostic device 10 via a network (for example, a device providing cloud services).

[0118] The conversational AI17 includes a pre-trained machine learning model (for example, a Large Language Model (LLM)) as its language model, takes text called a prompt as input, and outputs text corresponding to the prompt (for example, a sequence of words with the highest probability of appearing in the prompt) based on the pre-trained language model. Here, machine learning is a technique that enables computers to acquire human-like learning abilities, and it refers to a technique in which a computer autonomously generates algorithms necessary for judgments such as data identification from pre-acquired training data, and applies these to new data to make predictions. The learning method for machine learning can be supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or deep learning, or a combination of these learning methods, and the learning method for machine learning is not restricted.

[0119] The AI ​​control unit 16 inputs the prompt sentence generated by the determination unit 13 to the interactive AI 17 and outputs the output from the interactive AI 17 to the determination unit 13.

[0120] In the fourth embodiment, the determination unit 13 performs a diagnosis related to the diagnostic items and generates prompt sentences for input to the interactive AI 17.

[0121] Figure 21 is a sequence diagram illustrating an example of the processing procedure for the business application diagnostic process in the fourth embodiment. In Figure 21, steps identical to those in Figure 13 are given the same step numbers, and their explanations are omitted. In Figure 21, steps S251 to S253 are added between steps S250 and S260. Steps S250 to S253 are executed for each business application to be diagnosed. Here, we will focus on one business application (hereinafter referred to as the "target application") in our explanation.

[0122] In step S251, the determination unit 13 generates a prompt statement based on the application information of the target application and sends the prompt statement to the AI ​​control unit 16. The AI ​​control unit 16 inputs the prompt statement to the interactive AI 17 and obtains the text output from the interactive AI 17 (S252). The AI ​​control unit 16 sends the output text from the interactive AI 17 to the determination unit 13 (S253).

[0123] Next, we will explain the details of steps S250 to S253. Figure 22 is a flowchart illustrating an example of the processing procedure for the business application diagnostic process in the fourth embodiment. In Figure 22, steps identical to those in Figure 15 are given the same step numbers, and their explanations are omitted. In Figure 22, it is assumed that the information stored in the judgment criteria storage unit 15 is as shown in Figure 23. The information shown in Figure 23 indicates that it should be determined whether the two diagnostic items, field name and similar application, meet the pre-set conditions. Note that the application name, icon, and number of records are not included in Figure 23 for convenience, and these diagnostic items may also be included as targets for diagnosis in the fourth embodiment.

[0124] The determination unit 13 performs a diagnosis regarding the diagnostic item "field name" in Figure 23 in steps S308 to S309 and steps S321 to S323. That is, in the fourth embodiment, the processing in steps S321 to S323 is added with respect to "field name". This processing is for determining whether the condition "the field name conforms to the type" is satisfied. This condition is intended to reduce the possibility of defining fields where it is unclear what value should be entered. The condition "the field name conforms to the type" requires a qualitative judgment and is difficult to determine using rule-based methods. Therefore, the determination unit 13 uses the interactive AI 17 to determine whether this condition is satisfied.

[0125] Specifically, in step S321, the determination unit 13 generates a prompt statement to check the suitability of the field name to the type, and sends the prompt statement to the AI ​​control unit 16. Step S321 corresponds to step S251 in Figure 21.

[0126] For example, the prompt statement may be as follows:

[0127] <Prompt message starts here> You need to determine if the label name assigned to the field is correct.

[0128] Here, a field refers to each individual item that makes up a record. For example, in an employee roster app, each item such as name, address, and email address would be considered a "field." Each field has a type, and there is a list of {type enumerations and definitions}.

[0129] Now, you need to determine if it is appropriate for a field named "△△" to have a field type of "××".

[0130] The items to be evaluated are shown below in the format "Field Name:Field Type". For each item, return "true" if it is appropriate, and "false" if another type should be used.

[0131] *** Date: Numeric Job description: string ... *** <End of prompt message> Note that in the above prompt, {enumeration and definition of types} is actually replaced by an enumeration of types and a description of the definition of each type. Also, the list of "field name:field type" is generated based on the field information for each field included in the application information of the target application.

[0132] The AI ​​control unit 16 inputs the prompt statement to the interactive AI 17 and obtains the text output from the interactive AI 17. When the above prompt statement is input, text containing either "true" or "false" is output for each field. For example, if the field type is numeric but the field name is set to "Fault Details", it is expected that the interactive AI 17 will output false for "Fault Details". The AI ​​control unit 16 sends the text output from the interactive AI 17 to the determination unit 13.

[0133] Next, the determination unit 13 determines, based on the text, whether or not there are any fields that do not conform to the type (S322). Specifically, a field that does not conform to the type is a field for which false is output. If there are fields that do not conform to the type (Yes in S322), the determination unit 13 sets the determination result for the diagnostic item "field name" to "needs improvement" and adds improvement information to the determination result as supplement (S309). In this case, the improvement information is, for example, the field name of the field that does not conform to the type and a message indicating that the field does not conform to the type.

[0134] Next, the determination unit 13 performs a diagnosis regarding the diagnostic item "Similar Applications" in Figure 23 in steps S324 to S326. This process determines whether the condition "There are no multiple business applications with similar purposes" is met. This condition is intended to prevent the dispersion of information (records) related to the same business when multiple business applications with similar purposes are used for the same business. This condition can also be considered an example of a condition related to the comparison of two or more business applications. The condition "There are no multiple business applications with similar purposes" requires a qualitative judgment and is difficult to determine using rule-based methods. Therefore, the determination unit 13 uses the interactive AI 17 to determine whether this condition is met.

[0135] Specifically, in step S324, the determination unit 13 generates a prompt message to check other business applications similar to the target application, and sends the prompt message to the AI ​​control unit 16. Step S324 corresponds to step S251 in Figure 21.

[0136] For example, the prompt message could be as follows. Note that, in this case, the target application is assumed to be the "Daily Report App".

[0137] <Prompt message starts here> You need to find similar business applications. Below, we will show the names and fields of several business applications in the form of an object array. Here, a field is each individual item that makes up a record. For example, in an employee roster application, each item such as name, address, and email address would be a "field," with the key being the field name and the value being the field type. The object array is shown below. *** [ Daily report app: Date: Date, Objective achieved: Radio button, Job description: string, Impressions / Lessons Learned: Strings, }, Customer complaint handling app: Customer name: string, Person in charge: string, Claim details: string, }, Business trip reporting app: Business trip date: Date, Business travelers: string, Business trip destination: string, Purpose: string, }, ... ] *** If there are any business applications with a similar purpose to the "Daily Report App" included in this list, extract them. If no such business application exists, output "No matching applications found". The extracted output should be returned in JSON format as shown below. The following is an example.

[0138] *** { Daily report app: {○○-type app: [Business app A, Business app D]} } *** <End of prompt message> The AI ​​control unit 16 inputs the prompt statement to the interactive AI 17 and obtains the text output from the interactive AI 17. When the above prompt statement is input, the interactive AI 17 is expected to evaluate the similarity between business applications based on the similarity of fields between the daily report application and other business applications. The AI ​​control unit 16 sends the text output from the interactive AI 17 to the determination unit 13.

[0139] Next, the determination unit 13 determines, based on the text, whether or not there are other business applications similar to the target application (S325). If there are other business applications similar to the target application (Yes in S325), the determination unit 13 sets the determination result for the diagnostic item "Similar applications" to "Needs improvement" and adds improvement information to the determination result as supplement (S309). In this case, the improvement information is, for example, a message that includes the name of the similar application and a suggestion to combine the target application and the similar application.

[0140] Next, the judgment unit 13 integrates the judgment results for each diagnostic item to generate a diagnostic result (S350).

[0141] Figure 24 shows an example of the diagnostic results in the fourth embodiment. Figure 24 shows that the field name "Date and Time" is duplicated and that the business report application is similar to the daily report application.

[0142] As described above, according to the fourth embodiment, it is possible to diagnose business applications based on qualitative conditions as well.

[0143] The application diagnostic device 10 is not limited to a general-purpose computer, as long as it is a device equipped with communication capabilities. The application diagnostic device 10 may be, for example, an output device such as a PJ (Projector), IWB (Interactive White Board: an electronic whiteboard with the ability to communicate with each other), or digital signage, a HUD (Head Up Display) device, industrial machinery, imaging devices, sound collection devices, medical equipment, networked home appliances, a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet device, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC.

[0144] Furthermore, each function of each of the above embodiments can be realized by one or more processing circuits. Hereinafter, "processing circuit" as used herein includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules designed to execute each of the functions described above.

[0145] Furthermore, the apparatuses of each of the above embodiments represent only one of several computing environments for carrying out the embodiments disclosed herein.

[0146] In one embodiment, the application diagnostic device 10 includes multiple computing devices, such as a server cluster. These computing devices are configured to communicate with each other via any type of communication link, including a network or shared memory, and perform the processing disclosed herein. Similarly, the application creation device 20 may include multiple computing devices configured to communicate with each other.

[0147] Although embodiments of the present invention have been described in detail above, the present invention is not limited to these specific embodiments, and various modifications and changes are possible within the scope of the gist of the present invention as described in the claims.

[0148] Examples of the present invention are as follows:

[0149] <1> An application that includes one or more fields for accepting input values ​​to be registered as records, and which includes user-configurable items, and an acquisition unit that acquires application information including information set in the configurable items, A determination unit that determines whether the set information included in the acquired application information satisfies the predetermined conditions relating to the information set in the settable items, An output unit that outputs the result of the above determination, An information processing device characterized by having the following features.

[0150] <2> The aforementioned application is created based on a predetermined format. Characterized by <1> The information processing device described.

[0151] <3> The aforementioned application information includes the number of records related to the application, The determination unit further makes a determination based on the conditions relating to the number of records. Characterized by <1> or <2> The information processing device described.

[0152] <4> The determination unit determines whether the application information stored in the storage unit satisfies the conditions. Characterized by <1> ~ <3> Any of the information processing devices described above.

[0153] <5> The aforementioned conditions include conditions relating to the degree of customization of the created application, Characterized by <1> ~ <4> Any of the information processing devices described above.

[0154] <6> The aforementioned conditions include conditions relating to the comparison between two or more of the aforementioned applications. Characterized by <1> ~ <5> Any of the information processing devices described above.

[0155] <7> The acquisition unit acquires the application information of the application selected by the user from among the multiple applications. Characterized by <1> ~ <6> Any of the information processing devices described above.

[0156] <8> The determination unit includes in the determination result information indicating the improvement content for the conditions among the plurality of conditions that the application information does not satisfy. Characterized by <1> ~ <7> Any of the information processing devices described above.

[0157] <9> The determination unit generates the determination result using a pre-trained language model. Characterized by <1> ~ <8> Any of the information processing devices described above.

[0158] <10> An application that includes one or more fields for accepting input values ​​to be registered as records, and which includes user-configurable items, and a procedure for obtaining application information that includes information set in the said configurable items, A determination procedure for determining whether the information set in the acquired application information satisfies the predetermined conditions that relate to the information set in the configurable items, Output procedure for outputting the result of the above determination, An information processing method characterized by a computer executing the following.

[0159] <11> An application that includes one or more fields for accepting input values ​​to be registered as records, and which includes user-configurable items, and a procedure for obtaining application information that includes information set in the said configurable items, A determination procedure for determining whether the information set in the acquired application information satisfies the predetermined conditions that relate to the information set in the configurable items, Output procedure for outputting the result of the above determination, A program that causes a computer to execute something. [Explanation of Symbols]

[0160] 10. Application diagnostic device 11 Input section 12 Acquisition Department 13 Judgment section 14 Output section 15 Judgment criteria storage section 16 AI control section 17 Conversational AI 20 App creation devices 21 UI section 22 App Testing Department 23. Application Information Storage Unit 30 User terminals [Prior art documents] [Patent Documents]

[0161] [Patent Document 1] Japanese Patent Publication No. 2010-277288

Claims

1. An application that includes one or more fields for accepting input of values ​​to be registered as records, and which includes user-configurable items, and an acquisition unit that acquires application information including information set in the configurable items, A determination unit that determines whether the set information included in the acquired application information satisfies the predetermined conditions relating to the information set in the settable items, An output unit that outputs the result of the above determination, An information processing device characterized by having the following features.

2. The aforementioned application is created based on a predetermined format. The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

3. The aforementioned application information includes the number of records related to the application, The determination unit further makes a determination based on the conditions relating to the number of records. The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

4. The determination unit determines whether the application information stored in the storage unit satisfies the conditions. The information processing apparatus according to claim 1 or 2, characterized in that it is a product of the same type.

5. The aforementioned conditions include conditions relating to the degree of customization of the created application, The information processing apparatus according to claim 1, characterized in that it is a product of the present invention.

6. The aforementioned conditions include conditions relating to the comparison between two or more of the aforementioned applications. The information processing apparatus according to claim 1 or 2, characterized in that it is a product of the same type.

7. The acquisition unit acquires the application information of the application selected by the user from among the multiple applications. The information processing apparatus according to claim 1 or 2, characterized in that it is a product of the same type.

8. The determination unit includes in the determination result information indicating the improvement content for the conditions among the plurality of conditions that the application information does not satisfy. The information processing apparatus according to claim 1 or 2, characterized in that it is a product of the same type.

9. The determination unit generates the determination result using a pre-trained language model. The information processing apparatus according to claim 1 or 2, characterized in that it is a product of the same type.

10. An application that includes one or more fields for accepting input values ​​to be registered as records, and which includes user-configurable items, and a procedure for obtaining application information that includes information set in the said configurable items, A determination procedure for determining whether the information set in the acquired application information satisfies the predetermined conditions that relate to the information set in the configurable items, Output procedure for outputting the result of the above determination, An information processing method characterized by a computer executing the following.

11. An application that includes one or more fields for accepting input values ​​to be registered as records, and which includes user-configurable items, and a procedure for obtaining application information that includes information set in the said configurable items, A determination procedure for determining whether the information set in the acquired application information satisfies the predetermined conditions that relate to the information set in the configurable items, Output procedure for outputting the result of the above determination, A program that causes a computer to execute something.

Images