JP7530343B2 - System development support device, system development support method and system development support program - Google Patents

Description

The present invention relates to a system development support device, a system development support method, and a system development support program.

Patent Document 1 discloses a user interface development support device that combines and links the screen display function that a user interface should have, the data input function from the screen, and the function of calling up an application program and its data from the screen with screen elements prepared in advance, thereby eliminating the need to create individual screen elements and programs when developing/changing a user interface and simplifying data setting, thereby facilitating the development/changing of a user interface and reducing development costs and development time (see paragraph 0028 of Patent Document 1).

JP 2009-9472 A

In the field of system development, when developing systems through programming, there is a problem in that the high degree of freedom allows users to write inappropriate response processes (actions) in response to user operations. The same problem exists in low-code development.

Below is a brief explanation of a specific example of an inappropriate action setting. For example, it is inappropriate to set "Launch a message box" as an action that constitutes a value change process for a text box. This is because a user would not normally intend to launch another message box while changing the value of a text box. In this case, an example of an appropriate action setting would be "Show tool tip".

The present invention has been made in consideration of the above problems, and aims to provide a system development support device, a system development support method, and a system development support program that can prevent inappropriate setting of actions in system development, in which a developer sets actions to be executed on a screen used by a user.

In order to solve the above-mentioned problems and achieve the object, the system development support device according to the present invention is a system development support device that includes a control unit that can prevent inappropriate setting of an action in system development in which a developer sets an action to be executed on a screen used by a user, and the control unit is characterized in that it includes an acquisition means that acquires, during system development, a control selected by the developer, an event set by the developer for the selected control, and configurability identification information and error identification information associated with the action set by the developer for the selected event, by referring to an action table for managing information on configurable actions, the action table including a control that is an element displayed on the screen, an event executed for the control, the action that is a specific process performed during or after the event, configurability identification information for identifying whether the setting of the action is appropriate or inappropriate, and error identification information, and a display means that displays an error message corresponding to the error identification information acquired by the acquisition means when the configurability identification information acquired by the acquisition means indicates that the setting of the action is inappropriate.

The system development support device according to the present invention is also characterized in that the error message includes information about the appropriate action to be set.

The system development support device according to the present invention is also characterized in that the system development is performed without writing any source code or with very little source code.

In addition, the system development support method according to the present invention is a system development support method executed by an information processing device having a control unit, which can prevent inappropriate setting of an action in system development in which a developer sets an action to be executed on a screen used by a user, and is characterized in that it includes an acquisition step of acquiring configurable/non-configurable identification information and error identification information associated with a control selected by the developer, an event set by the developer for the selected control, and an action set by the developer for the selected event during system development, by referring to an action table for managing information on configurable actions, the action table including a control that is an element displayed on the screen executed by the control unit, an event executed for the control, the action that is a specific process performed during or after the execution of the event, configurable/non-configurable identification information for identifying whether the setting of the action is appropriate or inappropriate, and error identification information, and a display step of displaying an error message corresponding to the error identification information acquired in the acquisition step if the configurable/non-configurable identification information acquired in the acquisition step indicates that the setting of the action is inappropriate.

In addition, the system development support program according to the present invention is a system development support program for causing an information processing device having a control unit to execute, which can prevent inappropriate setting of an action in system development in which a developer sets an action to be executed on a screen used by a user, and which is executed by the control unit. The system development support program includes an acquisition step of acquiring, during system development, a control selected by the developer, an event set by the developer for the selected control, and setting possibility identification information and error identification information associated with the action set by the developer for the selected event, by referring to an action table for managing information on the settable actions, which includes a control that is an element displayed on the screen to be executed by the control unit, an event to be executed for the control, the action that is a specific process performed during or after the execution of the event, setting possibility identification information for identifying whether the setting of the action is appropriate or inappropriate, and error identification information, and a display step of displaying an error message corresponding to the error identification information acquired in the acquisition step, if the setting possibility identification information acquired in the acquisition step is information indicating that the setting of the action is inappropriate.

The present invention has the effect of preventing inappropriate setting of actions during system development in which a developer sets the actions to be executed on a screen used by a user.

FIG. 1 is a block diagram showing an example of the configuration of a system development support device. FIG. 2 is a diagram illustrating an example of an action table. FIG. 3 is a diagram showing an example of a correspondence table between error codes and messages. FIG. 4 is a diagram illustrating an example of the control information. FIG. 5 is a diagram showing an example of logic flow information and action information. FIG. 6 is a diagram illustrating an example of event information. FIG. 7 is a diagram showing an example of an overall image of a check. FIG. 8 is a diagram showing an example of a flowchart for checking screen information. FIG. 9 is a diagram showing an example of a flowchart for checking event information. FIG. 10 is a diagram showing an example of a flowchart for checking logic flow information. FIG. 11 is a screenshot showing the selection of a control and adding an event. FIG. 12 is an example screen showing the creation of a logic flow called "Value Change Process 1." FIG. 13 is an example of a screen showing the arrangement of an action called "Execute API." FIG. 14 is an example of a screen showing the placement of an action called "branch." FIG. 15 is an example of a screen showing the arrangement of an action called "Launch Message Box." FIG. 16 is an example of a screen showing the arrangement of an action called "display tool tip." FIG. 17 is a diagram showing an example of a tool tip display.

Below, an embodiment of a system development support device, a system development support method, and a system development support program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[1. Overview, etc.]
(1) Terms Used in the Present Invention The terms used in the present invention have the following meanings.
・Control: Synonymous with general controls such as text and buttons.
・Event: A process executed by a user's interactive operation, such as clicking a button. Synonymous with a general event.
Action: A unit of processing to achieve a single purpose, such as "executing an API" or "launching a screen."
・Logic flow: A group of 0 to N processes (actions) that can be set for an event. It holds information such as action information (multiple) and the execution order of the actions.
Screen event: An event that is executed for the operation of the entire screen, such as an event that is executed when the screen is started. As information, the event type and the logic flow identifier are stored.
・Control event: An event executed for a control, such as an event when a text value is changed or when a button is clicked. The information held includes the control identifier, the event type, and the logic flow identifier.

(2) Background and Overview of the Invention The present invention relates to a function for suppressing degradation of usability during system development in a low-code development tool.

As the business environment changes rapidly, it is assumed that information systems must keep up with the speed of management, and rapid system changes are necessary. In this environment, low-code development tools are attracting attention, and their user base is expanding beyond vendors to include system managers at the companies that use the systems. For this reason, there is a demand for a system that allows anyone to easily create highly usable screens.

Here, in system development that did not use low-code development, the programmer could freely write the process for each control event if they wanted to implement a process. As a result, there was a problem that the verification process could result in screen actions that the user could not predict, such as "page transitions" and "message boxes" being launched when checking checkboxes. There were also problems with the consistency of behavior.

Furthermore, similar problems have traditionally occurred in system development using low-code development, making it difficult to restrict the actions that can be set for each control event.

In this embodiment, for example, a check mechanism is provided for actions that can be set for screen control events, thereby preventing the development of screens that have inconsistent behavior and screens that are not appropriate in response to user operations. In other words, in this embodiment, for example, by defining each screen operation function (executing business processing, screen transitions, screen startup, etc.) for control events, it becomes possible to detect invalid settings at the time a setting operation is performed. The specific configuration and operation are described below.

2. Configuration
An example of the configuration of a system development support device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the system development support device 100.

The system development support device 100 is a commercially available desktop personal computer. Note that the system development support device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The system development support device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the system development support device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the system development support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the system development support device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described below may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

The memory unit 106 includes, for example, an action table 106a, a correspondence table 106b, control information 106c, logic flow information/action information 106d, and event information 106e.

The development support device 100 according to this embodiment can prevent inappropriate setting of actions in system development in which a developer sets actions to be executed on a screen used by a user. The system development is preferably, for example, system development performed without writing any source code (so-called no-code development) or system development performed with very little source code (so-called low-code development).

As shown in FIG. 2, the action table 106a includes, for example, a control (control type) which is an element displayed on the screen, an event (event type) which is executed for the control, the action (action type) which is a specific process performed during or after the event, setting availability identification information (availability) for identifying whether the setting of the action is appropriate or inappropriate, and error identification information (error code). In short, the action table 106a is a table for managing information on the configurable actions. The setting availability identification information (availability) is information indicating that the setting of the action is appropriate ("◯" in FIG. 2) or information indicating that the setting of the action is inappropriate ("X" in FIG. 2).

For example, as shown in Figure 2, it is inappropriate to set the action type "Launch Message Box" for the control type "Text Box" and event type "Value Change", so availability is set to "X" and error code "Error6". In contrast, as shown in Figure 2, it is appropriate to set the action type "Show Tooltip" for the control type "Text Box" and event type "Value Change", so availability is set to "〇".

As shown in FIG. 3, the correspondence table 106b includes, for example, the error identification information (error code), an error message, and the like. It is preferable that the error message includes information on the appropriate action to be set. For example, in the error message "Message box launch cannot be set for a text value change event. Please display errors and warnings in a tooltip," the part "Please display errors and warnings in a tooltip" corresponds to the information on the appropriate action to be set.

The control information 106c holds the object information (control model) of the control in an array. As shown in FIG. 4, the control information 106c includes, for example, an identification key, a type, a child element key, and an identification name. The identification key is a unique key assigned within the system. The type is the type of the control. The child element key is an array of identification keys that can become child elements of itself. The identification name is a unique key set by the user.

Next, logic flow information/action information 106d holds logic flow object information (logic flow model) in an array. Within the logic flow model, the action object information (action model) and the object that controls the execution order (flow model) are held in an array.

Logic flow information/action information 106d, for example, has multiple logic flows, and further has a flow and the action for each logic flow.

In the example of logic flow information/action information 106d shown in FIG. 5, a "button click process" identified by the identification key "logic flow key 1" and a "value change process" identified by the identification key "logic flow key 2" are set as multiple logic flows. In the example of logic flow information/action information 106d shown in FIG. 5, a flow and an action are set for the "button click process."

As shown in Figure 5, a flow includes a source action key, a next action key, a callback key, and so on. The source action key is an identification key of an action that is the basis for the execution order of processes. The next action key is an identification key of an action to be executed after the action indicated by the source action key is executed. The callback key is a key for determining the action selected by the user at execution (for example, if the user selects Yes in a message box, the Yes flow is identified and the action according to the end key is executed).

An action includes an identification key, a type, etc., as shown in Figure 5.

Next, event information 106e is information that links the events and logic flows that can be set for each control, and holds object information (event models) of the events in an array. As shown in FIG. 6, event information 106e includes, for example, a type, a control identification key, an event type, and a logic flow identification key. The type is a value that indicates whether it is a screen event or a control event. The control identification key is an identification key for the control model. The event type is the type of event to be executed. The logic flow identification key is an identification key for the logic flow model.

Regarding the settings of the bottom row in the example of event information 106e shown in Figure 6, with the word "Event Model" written to the right, in this column, "Value Change" is set as the event type, "Control Key 3 (corresponding to the text box as shown in Figure 4)" is set as the control identification key, and "Logic Flow Key 2 (corresponding to the value change process as shown in Figure 5)" is set as the logic flow identification key. Therefore, in this column, an event called "Value Change" and a logic flow called "Value Change Process" are set for the text box.

The control unit 102 is a CPU or the like that provides overall control of the system development support device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various types of information processing based on these stored programs.

The control unit 102 is functionally conceptually equipped with, for example, a screen information check unit 102a, an event information check unit 102b, and a logic flow information check unit 102c. The logic flow information check unit 102c further includes, for example, an acquisition unit 102c1 as an acquisition means for acquiring the control selected by the developer, the event set by the developer for the selected control, and the action set by the developer for the selected event during system development by referring to an action table for managing information on the configurable actions, including a control that is an element displayed on the screen, an event executed for the control, the action that is a specific process performed during or after the execution of the event, configurability identification information for identifying whether the setting of the action is appropriate or inappropriate, and error identification information, and a display unit 102c2 as a display means for displaying an error message corresponding to the error identification information acquired by the acquisition means when the configurability identification information acquired by the acquisition means is information indicating that the setting of the action is inappropriate.

The screen information checking unit 102a checks the screen information.

The event information checking unit 102b checks the event information.

The logic flow information checking unit 102c checks the logic flow information.

The acquisition unit 102c1 refers to an action table 106a (see FIG. 2) including the control type, the event type, the action type, the availability, and the error code, and acquires the availability and error code associated with the control selected by the developer during system development, the event set by the developer for the selected control, and the action set by the developer for the selected event.

When the availability information acquired by the acquisition unit 102c1 indicates that the action is inappropriately set (in FIG. 2, "x"), the display unit 102c2 displays an error message corresponding to the error code acquired by the acquisition unit 102c1.

[3. Processing Overview and Flow]
In this section, an overview of the processing according to this embodiment will be described in [3-1], and the flow of the processing according to this embodiment will be described in [3-2].

[3-1. Processing Overview]
This section describes an overview of the process according to this embodiment. The overall image of the check in this embodiment is as shown in Figure 7. The "check process" is executed based on the screen information, and the check result is returned to the developer.

In this embodiment, the check process is executed asynchronously whenever the settings are changed. The reason it is executed asynchronously is so that the developer can continue to change the settings even while the check is in progress.

The target of the check process in this embodiment is screen information (control information, logic flow information, action information, and event information).

In this embodiment, the result information of the check process is an error code and an error message that are returned to the developer. Note that multiple error codes and error messages may be returned.

[3-2. Processing flow]
In this section, the flow of processing according to this embodiment will be explained with reference to Figures 8 to 10. In this embodiment, checks are performed in the order of control information, event information, logic flow information, and action information. Errors detected during the execution of the check process are stacked as error codes in the "error code stack."

(1) Checking Screen Information First, checking screen information will be described with reference to FIG.

The screen information checking unit 102a checks the control information (step S1 in FIG. 8). Specifically, it checks whether there are any inconsistencies in the parent-child relationships and whether any invalid properties have been set.

If there is an inconsistency in the parent-child relationship or if an invalid property is set (NG in step S1 of FIG. 8), the screen information check unit 102a adds the detected error to the error code stack (step S2 of FIG. 8).

On the other hand, if the check result is OK (OK in step S1 of FIG. 8), the process proceeds to FIG. 9, where all events defined in the screen information are checked in order.

(2) Checking Event Information Next, checking event information will be described with reference to FIG.

The event information checking unit 102b checks whether the identifier of the set control exists in the control information 106c (step S3 in FIG. 9).

If it does not exist (NG in step S3 in FIG. 9), the event information check unit 102b adds the detected error to the error code stack (step S4 in FIG. 9), and the process ends (END).

On the other hand, if the control type exists (OK in step S3 in FIG. 9), the event information checking unit 102b retains the control type. Then, the event information checking unit 102b next checks whether the identifier of the set logic flow exists in the logic flow information/action information 106d (step S5 in FIG. 9).

If it does not exist (NG in step S5 in FIG. 9), the event information check unit 102b adds the detected error to the error code stack (step S6 in FIG. 9), and the process ends (END).

On the other hand, if it does exist (OK in step S5 in FIG. 9), the process proceeds to FIG. 10, where the target logic flow information is checked. At this time, the control type and event type are passed to the logic flow check.

(3) Checking Logic Flow Information Finally, checking logic flow information will be explained with reference to FIG.

The logic flow information checking unit 102c checks whether there are any breaks in the logic flow and whether any unnecessary flows have been drawn (step S7 in FIG. 10).

If there is a break in the logic flow or if an unnecessary flow has been drawn (NG in step S7 of FIG. 10), the logic flow information check unit 102c adds the detected error to the error code stack (step S8 of FIG. 10).

If there are no breaks in the logic flow and no unnecessary flows have been drawn (OK in step S7 of FIG. 10), the logic flow information checking unit 102c checks all the actions defined in the logic flow in order (step S9 of FIG. 10).

Specifically, the logic flow information checking unit 102c acquires the action type of the action to be processed (step S10 in FIG. 10). Next, the logic flow information checking unit 102c checks whether availability information and an error code can be acquired from the action table 106a in FIG. 2 based on the control type and event type passed at the end of (2) and the acquired action type (step S11 in FIG. 10). Note that step S11 is a characteristic process of the present invention, and will be described in detail in [4. Specific examples of processing] below.

If the error cannot be obtained (NG in step S11 of FIG. 10), the logic flow information checking unit 102c adds the detected error to the error code stack (step S12 of FIG. 10).

If the action information is acquired (OK in step S11 in FIG. 10), the logic flow information check unit 102c checks the action information (step S13 in FIG. 10). Note that step S13 is a characteristic process of the present invention, and will be described in detail in [4. Specific examples of processing] below.

If the check result is NG (NG in step S13 of FIG. 10), the logic flow information check unit 102c adds the detected error to the error code stack (step S14 of FIG. 10).

On the other hand, if the check result is OK (OK in step S13 of FIG. 10), the logic flow information checking unit 102c checks whether there are any unchecked actions (step S15 of FIG. 10).

If there are any unchecked actions (NG in step S15 of FIG. 10), the logic flow information checking unit 102c returns to step S9 of FIG. 10 and continues processing until there are no more unchecked actions.

On the other hand, if there are no unchecked actions (OK in step S15 of FIG. 10), the process ends (End of FIG. 10).

4. Specific examples of processing
In this section, a specific example of the processing according to this embodiment will be described mainly with reference to FIGS. 2 to 3 and FIGS. 11 to 17.

The present invention relates to a setting check mechanism for setting up processing for controls in a low-code development tool. This section provides a specific explanation of how errors are displayed if an inappropriate setting is made when a developer performs low-code development from a screen on which controls are placed.

[4-1. Control Selection and Event Settings]
First, as indicated by the arrow (left side) in FIG. 11, the developer selects a "text box" as a control for which an event is to be set.

Next, as shown by the arrow (right side) in Figure 11, the developer sets "Value Change" as an event, and then presses the "OK" button in the bottom right of the screen.

[4-2. Creating logic flow]
Next, a logic flow called "Value Change Process 1" is created, as shown in Fig. 12. At this time, a control event that links the control and the logic flow is generated behind the scenes.

[4-3. Setting logic flow]
Next, in this section, we will explain the detailed settings for the logic flow created in [4-2].

First, the developer places an "Execute API" action, as shown in Figure 13.

Next, the "branch" is placed by the developer, as shown in Figure 14.

Below, we will explain separately when the action placed after "branch" is "launch a message box" or "display a tooltip".

(1) When "Launch Message Box" is Placed First, as shown in FIG. 15, the process when an action called "Launch Message Box" is placed by a developer (when an error is displayed due to an inappropriate setting) will be described.

In this example, as explained in [4-1], the event "Value Change" is set for the control "Text Box", and as the action to be performed during "Value Change", "Launch Message Box" is set, as explained in the previous paragraph.

The acquisition unit 102c1 acquires the availability indicator "x" and the error code "Error6" from the action table 106a in FIG. 2 as information associated with the control type "text box", the event type "value change", and the action type "message box launch". In other words, the placement of the action "message box launch" is inappropriate.

When the acquisition unit 102c1 acquires the availability status "X", it further acquires from the correspondence table 106b in FIG. 3 the error message "Message box launch cannot be set for a text value change event. Please display errors and warnings in a tooltip" as an error message associated with the acquired "Error6".

Then, the display unit 102c2 displays the error message acquired by the acquisition unit 102c1 on the screen as shown in FIG. 15. The reason why an error message is displayed when "Launch Message Box" is placed in this way is, for example, as follows. That is, when the value of the text box is changed, the screen state is being changed, so an interrupt process such as a message box is stressful for the user.

As described above in section (1), the system development support device 100 according to this embodiment can prevent the setting of inappropriate actions and can suggest appropriate action placements to the developer.

(2) When "Show Tooltip" is Placed Next, as shown in FIG. 16, the processing when the action "Show Tooltip" is placed by the developer (when no error is displayed due to appropriate settings) will be described.

In this example, as explained in [4-1], the event "Value Change" is set for the control "Text Box", and as the action to be performed during "Value Change", "Show Tooltip" is set, as explained in the previous paragraph.

The acquisition unit 102c1 acquires the availability "o" as information associated with the control type "text box", the event type "value change", and the action type "tooltip display" from the action table 106a in FIG. 2 (no error code is acquired). In other words, the placement of the action "tooltip display" is appropriate. Note that a "tooltip" is a type of display element on a computer's operation screen, and is an annotation that is displayed around an object when the cursor or mouse pointer is placed over the object. In the example in FIG. 17, the tooltip is a rectangle with the words "Item not filled in." written on it.

If the availability is confirmed as "Yes", naturally no error message will be displayed and the developer will be able to continue with low-code development.

[5. Summary of the present embodiment]
In this way, according to the system development support device 100 of this embodiment, in system development in which a developer sets actions to be executed on a screen used by a user, it is possible to prevent the setting of inappropriate actions.

However, the act of developing a system through programming means that there is a high degree of freedom, so there is a risk that inappropriate response processing will be written for user operations. Furthermore, traditional low-code development tools do not have the functionality to prevent or suggest degradation of usability during setup, so there is a risk that usability will decrease depending on how the system is developed. In other words, traditional low-code development may be able to meet the necessary functionality, but it often does not take into account the quality of the system when it is in use.

In this embodiment, for example, by providing a mechanism for controlling the processes that can be set for control events and proposing appropriate processes, it is possible to prevent the development of screens that are inappropriate in response to user operations and screens that lack consistency in their behavior. In other words, in this embodiment, for example, it is possible to set control events that can be set for each screen operation function, and further, it is possible to immediately detect an illegal arrangement by determining whether or not the arrangement is illegal at the time the control is operated.

As a result, in this embodiment, for example, in low-code development, it is possible to consider the quality of the system when it is in use while still satisfying the necessary functionality. In a system developed based on the mechanism of this embodiment, it is expected that usability will be improved and system utilization will become more efficient.

[6. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

7. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

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

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

Furthermore, with regard to the system development support device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the system development support device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the system development support device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the system development support device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The system development support device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The system development support device 100 may also be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful in all industries and business sectors.

100 System development support device 102 Control unit
102a Screen information check unit
102b Event information check unit
102c Logic flow information check unit
102c1 Acquisition unit
102c2 Display unit 104 Communication interface unit 106 Storage unit
106a Action Table
106b Correspondence table
106c Control Information
106d Logic flow information/action information
106e Event information 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (5)

A system development support device including a control unit that can prevent an inappropriate setting of an action in a system development in which a developer sets an action to be executed on a screen used by a user, the system development support device comprising:
The control unit is
an acquisition means for acquiring, during system development, a control selected by the developer, an event set by the developer for the selected control, and setting possibility identification information and error identification information associated with the action set by the developer for the selected event, by referring to an action table for managing information on settable actions, the table including a control which is an element displayed on the screen, an event executed for the control, the action which is a specific process performed during or after the event is executed, setting possibility identification information for identifying whether the setting of the action is appropriate or inappropriate, and error identification information;
a display means for displaying an error message corresponding to the error identification information acquired by the acquisition means when the setting possibility identification information acquired by the acquisition means indicates that the setting of the action is inappropriate;
To have
A system development support device characterized by: the error message includes information about the appropriate action to be taken;
2. The system development support device according to claim 1, The system development is
System development that is done without writing any source code or with very little source code.
3. The system development support device according to claim 1 or 2, A system development support method executed by an information processing device having a control unit, which can prevent inappropriate setting of an action in system development in which a developer sets an action to be executed on a screen used by a user, comprising:
Executed by the control unit,
an acquisition step of acquiring setting possibility identification information and error identification information associated with a control selected by the developer during system development, an event set by the developer for the selected control, and an action set by the developer for the selected event, by referring to an action table for managing information on settable actions, the table including a control which is an element displayed on the screen, an event executed for the control, the action which is a specific process performed during or after the event, setting possibility identification information for identifying whether the setting of the action is appropriate or inappropriate, and error identification information;
a display step of displaying an error message corresponding to the error identification information acquired in the acquisition step when the setting possibility identification information acquired in the acquisition step indicates that the setting of the action is inappropriate;
containing,
A system development support method comprising the steps of: A system development support program for causing an information processing device having a control unit to execute the program, the system development support program being capable of preventing an inappropriate setting of an action in a system development in which a developer sets an action to be executed on a screen used by a user, the system development support program being executed by the information processing device having a control unit,
To cause the control unit to execute
an acquisition step of acquiring setting possibility identification information and error identification information associated with a control selected by the developer during system development, an event set by the developer for the selected control, and an action set by the developer for the selected event, by referring to an action table for managing information on settable actions, the table including a control which is an element displayed on the screen, an event executed for the control, the action which is a specific process performed during or after the event, setting possibility identification information for identifying whether the setting of the action is appropriate or inappropriate, and error identification information;
a display step of displaying an error message corresponding to the error identification information acquired in the acquisition step when the setting possibility identification information acquired in the acquisition step indicates that the setting of the action is inappropriate;
containing,
A system development support program characterized by:

Images