Graphics-based flow-graph generating apparatus and application development system using same

Abstract

The present invention relates to a graphics-based flow-graph generating apparatus that enables an application, which is implemented through programming or coding work, to be developed easily and conveniently through a graphics-based interface, and to an application development system using same. The present invention provides a flow-graph generating apparatus that allows a developer to easily generate a flow-graph, and a flow-graph execution engine for interpreting and executing the flow-graph generated by the flow-graph generating apparatus. The flow-graph generating apparatus provides a graphics-based IDE (1) to the developer. The developer can call a node (30) from a node library through the IDE (1) and generate a desired flow-graph through a simple operation of connecting the node (30) using an edge (40). In particular, the flow-graph generating apparatus provides means for setting both a process flow and a data flow together in a single flow-graph. This provides a basis for establishing an interaction between a user and loops and decision tree processes which are not possible in a data-flow-only diagram.

Description

A graphic-based flowchart generator and an application development system using it.

[0001] The present invention relates to a graphic-based flowchart generation device that enables easy and convenient development of an application implemented through programming or coding work on a graphic basis, and to an application development system using the same.

[0002] Any program used by a user to perform a task using a computer is called application software, or simply an application. Applications are used in a wide range of fields, including gaming, graphics, computer-aided design (CAD), communications, word processing, office computing, databases, and numerical analysis for scientific and technological applications. In particular, with the recent surge in interest in artificial intelligence (AI), a wide variety of AI applications have been developed and deployed.

[0003] When developing or creating applications, including AI, data flow graphs and flowcharts are created by considering the flow of data and processes. Then, programming or coding is performed using an appropriate programming language. A variety of programming languages ​​have been developed and are currently being used to create applications. Examples include Python, R, C / C++, Java, JavaScript, Julia, Scala, Ruby, MATLAB, Octave, and SA, all of which are text-based. Creating applications using these programming languages ​​requires specialized knowledge of the language. AI algorithms, in particular, involve highly complex and difficult mathematical operations, and their programming requires significant manpower and time.

[0004] Recently, generative applications such as Amazon CodeWhisperer have been proposed that utilize the Large Language Mode (LLM) and the Foundation Model (FM) in an Integrated Development Environment (IDE) to help developers build applications quickly and safely.

[0005] Korean Patent No. 10-0633241 (Title: Embedded Linux Education Integrated Development Environment System), Korean Patent No. 10-0553707 (Title: SCORM-based Content Creation System), Korean Patent No. 10-0860963 (Title: Device and Method for Component-based Software Development), Publication Patent No. 10-2018-0048213 (Title: Method and Device for Configuring User-Defined Member Editing Window in Integrated Development Environment), Korean Patent No. 10-2622652 (Title: Method and Device for Automatic Software Development for a Group of Controller-based Devices), Publication Patent No. 10-2022-0050362 (Title: GUI-based Integrated Development Environment Providing System for Algorithm Configuration), and Publication Patent No. 10-2023-0089495 (Title: Spiking Neural Network Input Data Processing System of GUI-based Integrated Development Environment) include graphic-based integrated development environments (IDEs). These inventions disclose systems that provide a variety of algorithms and complex architectures. However, these inventions have the problem that they cannot adequately address the development of applications with diverse algorithms and complex architectures.

[0006] The technical purpose of the present invention is to provide a flowchart generation device that can provide an integrated development environment in which developers can develop flowcharts and applications based on graphics.

[0007] In addition, the present invention has another technical purpose of providing a flowchart generation device capable of providing a flowchart that can set up a data flow and a process flow together through a single flowchart.

[0008] In addition, the present invention has another technical purpose of providing an application development system that allows developers to easily develop applications based on graphics.

[0009] The present invention provides a flowchart generation device that enables developers to easily create flowcharts, and a flowchart execution engine for interpreting and executing flowcharts generated by the flowchart generation device. The flowchart generation device provides an IDE that enables developers to graphically create flowcharts using nodes and edges. In addition, the flowchart generation means comprises a first storage means having a node library and a second storage means for storing flowcharts. The node library has node information corresponding to a node list, and the node information includes program source or code information. The IDE provides a means for developers to call nodes from the node library and connect the called nodes with edges to establish process flows and data flows. The node information called by the developer and the edge information connecting the nodes are stored in the second storage means by the IDE. The flowchart execution engine interprets and executes the flowchart information stored in the second storage means.

[0010] According to the present invention, which comprises the above-described configuration, developers can create a desired flowchart through the simple task of calling nodes from a node library via an IDE and connecting the nodes via edges. The flowchart includes program source or code information required for application execution, as well as execution information. In particular, the flowchart generation device provides a means for setting up both process flow and data flow in a single flowchart. This provides a foundation for setting up loops and decision tree processes, as well as user interaction, that are not possible with a data flow-only flowchart.

[0011] Figure 1 is a block diagram showing a flowchart generation device according to one embodiment of the present invention.

[0012] FIG. 2a is a drawing showing an example of a user interface (20) provided by the IDE (1) in FIG. 1.

[0013] Fig. 2b is a drawing showing an example of a flowchart registration window (201) provided by the IDE (1) when the flowchart registration menu (222) is selected in Fig. 2a.

[0014] Figure 2c is a drawing showing an example of an interface screen provided by the IDE (1) when the developer selects the flowchart extension menu (224) in Figure 2a.

[0015] FIG. 2d is a drawing showing an example of a list of categories (225a) selectable through the node selection menu (225) in FIG. 2a;

[0016] FIG. 2e is a diagram showing an example of a list of nodes (225b) that can be selected through selection of a category list (225a) in FIG. 2d.

[0017] Figure 2f is a drawing showing an example of a method of loading a desired node from a node list (225b) into a workspace (21).

[0018] Figure 2g is a drawing showing an example of another way of calling a node (30) as a workspace (21).

[0019] FIG. 2h is a drawing showing an example of a selection window (213) related to a node (30) provided by a user interface (20).

[0020] Figure 3 is a drawing showing an example of a work process for creating a flowchart in a workspace (21) using a user interface (20).

[0021] Figure 4 is a drawing showing the types of nodes for setting up data flow and an example of their configuration.

[0022] Figure 5 is a drawing showing the types of nodes for setting up a process flow and an example of their configuration.

[0023] FIG. 6a is a drawing showing an example of a setting window (214) provided corresponding to a path selection node (301) in FIG. 5.

[0024] FIG. 6b is a drawing showing an example of a setting window (215) provided corresponding to the loop control node (302) in FIG. 5.

[0025] FIG. 6c is a drawing showing an example of a setting window (216) provided corresponding to the match-branch node (303) in FIG. 5.

[0026] Figure 7 is a block diagram showing the configuration of an application development system according to one embodiment of the present invention.

[0027] Fig. 8 is a drawing showing another configuration example of a selection window (213) related to a node (30) provided by a user interface (20).

[0028] A graphic-based flowchart generation device according to a first aspect of the present invention is a device for generating a flowchart used in the development of an application or model implemented in software, comprising: an IDE providing means for providing an IDE capable of generating a flowchart graphically; a first storage means having a node library; and a second storage means for storing a flowchart, wherein the IDE providing means includes a flowchart generator and a user interface, wherein the user interface includes a workspace and a selection menu, and the selection menu includes a node list for selecting a node required for generating a flowchart; the user interface provides a node calling means for a developer to call a node to a workspace; the node library is provided with node information corresponding to the node list, the node information includes program source or code information, the node has a process port that can be connected to another node through an edge, and the second storage means stores node connection information together with the node information.

[0029] In addition, the selection menu further includes a flowchart list for selecting a flowchart, and the second storage means is characterized in that it has a flowchart library corresponding to the flowchart list.

[0030] In addition, the node is characterized in that it has a data port that can be connected to another node through an edge, and the data port includes an input port for data input or an output port for data output.

[0031] Additionally, the node is characterized by including a node for establishing a data flow.

[0032] Additionally, the node is characterized in that it includes a node for setting a process flow.

[0033] In addition, the process flow setting node is characterized by including at least one of a path selection node, a loop control node, and a match-branch node.

[0034] In addition, the IDE providing means is characterized by providing a branch setting window for a developer to set the number of branches of a process flow setting node.

[0035] In addition, the IDE providing means is characterized by providing an editing means for a developer to modify or edit the node information.

[0036] According to a second aspect of the present invention, an application development system is provided for use in developing an application or model implemented in software, comprising: an IDE providing means for providing an IDE that allows a developer to create a flowchart graphically; a node library in which node information is stored; a flowchart library in which a flowchart is stored; and a flowchart execution engine that executes the flowchart, wherein the flowchart includes nodes and edges connecting between nodes, the nodes have process ports that can be connected to other nodes through the edges, the edges include edges for setting a process flow, the node information includes program source or code information, and the flowchart library stores node information and connection information between nodes in correspondence with the flowchart.

[0037] In addition, the IDE providing means includes a user interface, the user interface includes a workspace and a selection menu, the selection menu includes a node list for selecting nodes required for creating a flowchart, and the user interface is characterized in that it provides a node calling means for a developer to call a node to the workspace and an edge connecting means for connecting between nodes through edges.

[0038] In addition, the node is characterized in that it has a data port that can be connected to another node through an edge, and the data port includes an input port for data input or an output port for data output.

[0039] Additionally, the node is characterized by including a node for establishing a data flow.

[0040] Additionally, the node is characterized in that it includes a node for setting a process flow.

[0041] In addition, the process flow setting node is characterized by including at least one of a path selection node, a loop control node, and a match-branch node.

[0042] In addition, the above flowchart execution engine is characterized by being a simulator.

[0043] Additionally, the flowchart execution engine is characterized by being a compiler.

[0044] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiments described below are merely exemplary of one preferred implementation of the present invention, and these examples are not intended to limit the scope of the present invention. The present invention can be implemented with various modifications without departing from the technical spirit thereof.

[0045] Figure 1 is a block diagram showing a flowchart generation device according to an embodiment of the present invention. The flowchart generation device provides an integrated development environment (IDE: Integrated Development Environment) (1) for application development. The IDE (1) has a flowchart generator (10) as an IDE providing means. The flowchart generator (10) provides a means for a developer to generate a flowchart including a data flow and a process flow. The IDE (1) provides a user interface (20) for a developer or a user. The user interface (20) preferably includes a GUI (Graphical User Interface). The developer can generate a flowchart graphically through the user interface (20).

[0046] Fig. 2a is a drawing showing an example of a user interface (20) provided by an IDE (1). The user interface (20) basically includes a workspace (21) and a number of selection menus (22). The workspace (21) is for creating a flowchart. As described later, a developer calls nodes to the workspace (21) and creates a flowchart graphically by appropriately connecting the nodes. A display window (23) is provided at the top of the workspace (21) to display the project name and flowchart name related to the application currently being developed.

[0047] The selection menu (22) can be selected by the developer by clicking on the corresponding area, for example, with a mouse (not shown). Of course, in another preferred implementation example, the selection menu (22) can be implemented so that the developer can select it using a keyboard shortcut. The selection menu (22) includes a project name selection menu (221) for registering and selecting a project name, a flowchart registration menu (222) for registering a new flowchart, and a flowchart selection menu (223) for selecting and loading an existing registered flowchart. Fig. 2b is a drawing showing an example of a flowchart registration window (201) provided by the user interface (20) when the flowchart registration menu (222) is selected. In the drawing, the flowchart registration window (201) includes a name field (201a) for entering a flowchart name, a category field (201b) for selecting or registering a category, and a registration button (201c). The flowchart registered through the flowchart registration window (201) can be viewed and selected through the flowchart selection menu (223) of Fig. 2a.

[0048] In addition, an extension menu (224) related to the flowchart is provided on one side of the flowchart registration menu (222). Fig. 2c is a drawing showing an example of an interface screen provided by the IDE (1) when a developer selects the flowchart extension menu (224). In the drawing, the flowchart extension menu (224) has a number of selection items (224a to 224f) that the developer can select in relation to the flowchart currently being worked on. These selection items include a workspace clear item (224a) for initializing the workspace (21), an edit item (224b) for returning to the flowchart registration window (201) of Fig. 2b to modify or edit flowchart-related information, a copy item (224c) for copying the work content, a download item (224d) for saving the flowchart to a local memory, etc., a flowchart delete item (224e) for deleting the corresponding flowchart list, and an upload item (224f) for uploading the downloaded flowchart.

[0049] Meanwhile, in Fig. 2a, the user interface (20) has a node selection menu (225), a flowchart operation button (226) for editing a flowchart, and a run button (227) for executing the generated flowchart. The node selection menu (225) preferably has a category list and a node list. These can be viewed and selected by the developer by selecting the node selection menu (225). Figs. 2d and 2e are drawings showing examples of a category list (225a) and a node list (225b) that can be selected through the node selection menu (225). In the drawings, the node list (225a) is provided by the IDE (1) when the developer selects a desired category list (225a). The method of providing the node list (225b) is not specified and may be modified in various ways.

[0050] Each node in the node list (225b) corresponds to a task to be performed programmatically, including operations. One node can correspond to one program module. Developers can create their own desired flowchart by selecting an appropriate flowchart or node from the flowchart selection menu (223) and node selection menu (225).

[0051] FIG. 2f is a diagram showing an example of a method for calling a desired node from a node list (225b) to a workspace (21). When a developer wishes to call a desired node to a workspace (21), the developer clicks on the desired node item in the node list (225b) with the mouse and then calls the node (30) to a desired location in the workspace (21) by dragging and dropping. The node (30) called to the workspace (21) can then be moved to a desired location by dragging and dropping again. The method for calling the node (30) to the workspace (21) is not specified.

[0052] Fig. 2g is a diagram illustrating another example of a method of calling a node (30) in a workspace (21). When a developer right-clicks on an empty area of ​​the workspace (21) with the mouse, a selection window (211) equipped with an 'Add Node' item is provided in the corresponding clicked area of ​​the workspace (21). The developer can call a desired node (30) in the workspace (21) by selecting a desired node item from a category list (225a) and a node list (225b) that are displayed step-by-step from this selection window (211).

[0053] Returning to FIG. 2f, the node (30) has a number of elements (31 to 33) that are schematically arranged. The node (30) basically has an element (31) for defining the work content. In addition, the node (30) has elements (32, 33) for inputting and outputting data as needed. The type and number of elements provided in the node (30) may vary depending on the type of the node (30), i.e., the work that the node (30) must perform.

[0054] FIG. 2h is a diagram illustrating an example of a selection window (213) related to a node (30) provided by a user interface (20). When a developer right-clicks on a node (30) area, the user interface (20) provides a selection window (213) related to the node (30). At this time, the selection window (213) includes a selection item for setting the node as the start node of the flowchart, and selection items for cutting, copying, duplicating, and deleting the node.

[0055] Returning to FIG. 2f, the node (30) has ports (31a, 32a, 33a) that can be connected to other nodes (30). These ports basically include a process port (31a) for establishing a process flow, and optionally include data ports (32a, 33a) for establishing a data flow. In addition, the data ports (32a, 33a) may include an input port (32a) for data input, and an output port (33a) for data output. In a preferred embodiment, the ports (31a, 32a, 33a) are configured with different shapes and colors according to their functions so that developers can easily distinguish them. The developer creates a flowchart by appropriately connecting the ports (31a, 32a, 33a) of the nodes (30) using edges.

[0056] FIG. 3 is a diagram illustrating an example of a process for creating a flowchart in a workspace (21) using a user interface (20). When creating a flowchart in a workspace (21), first, a desired node (30) is called from a node list (225b) and the node (30) is placed in the workspace (21). Then, the process port (31a) and the data port (32a, 33a) of the node (30) are connected with an edge (40) to set the process flow and the data flow in the flowchart. The creation or connection of an edge (40) is executed by clicking on one port (31a, 32a, 33a) with the mouse and dragging the mouse to another desired port (31a, 32a, 33a). In addition, in a preferred implementation example, the IDE (1) sets the colors of the edges that set the process flow and the edges that set the data flow differently, so that the developer can easily recognize the process flow and the data flow.

[0057] Returning to FIG. 2d, in a preferred embodiment of the present invention, the category list (225a) of the node selection menu (225) includes a category (data flow) that includes a list of nodes for setting up a data flow. FIG. 4 is a diagram illustrating the types of nodes included in the data flow category, i.e., nodes for setting up a data flow, and examples of their configurations.

[0058] In a more preferred embodiment of the present invention, the category list (225a) of the node selection menu (225) includes a category (flow control) that includes a list of nodes for setting up a process flow. Fig. 5 is a diagram illustrating the types of nodes included in the flow control category, i.e., nodes for setting up a process flow, and examples of their configurations. Nodes for setting up a process flow include a path selection node (301), a loop control node (302), and a match-branch node (303).

[0059] The path selection node (301) provides a function that allows the user to select a desired path through a flow graph. The IDE (1) provides a setting window that allows the developer to set the number of branches of the path selection node (301). Fig. 6a is a drawing showing an example of a setting window (214) provided in response to the path selection node (301). The setting window (214) is created when the developer clicks the left mouse button on the path selection node (301) area. The setting window (214) has an add branch button (214a) for the developer to add a branch port, and a remove branch button (214b) for the developer to remove a branch port. In addition, the setting window (214) has a lock button (214c) for locking or unlocking a value set by the developer, i.e., the number of branch ports. In the drawing, node (301a) represents a state in which the developer has increased the number of branch ports of the path selection node (301) using the setting window (231).

[0060] The loop control node (302) provides developers with the ability to control the repetitive execution of a process flow. The IDE (1) provides a settings window that allows developers to set the number of repetitions of the process flow. Figure 6b is a diagram illustrating an example of a settings window (215) provided in response to the loop control node (302).

[0061] The match-branch node (303) provides a function to branch input by pattern. The IDE (1) provides a setting window in which the developer can set the match pattern and branch. Fig. 6c is a drawing showing an example of a setting window (216) provided in response to the match-branch node (303). The setting window (216) has a field (216a) for the developer to define a pattern, buttons (216b, 216c) for adding and removing the field and branch, and a lock button (216d) for locking or unlocking the setting value through the setting window (216). In the drawing, the node (303a) shows a state in which the developer has added a branch port of the match-branch node (303) using the setting window (216).

[0062] Figures 4 and 5 are exemplary examples of nodes for establishing process flow and data flow, and the configuration and types of these nodes are not specified. The configuration and types of nodes may be appropriately changed depending on the application or programming language. The nodes for establishing process flow and data flow provide the effect of simplifying the overall structure of the flowchart and enabling developers to easily create flowcharts. The flowchart according to the present invention includes process flow as well as data flow in a single flowchart. This provides a basis for establishing loops and decision tree processes and user interaction that are not possible in a flowchart with only data flow.

[0063] Returning to Fig. 1, the flowchart generator has a storage unit (2). The storage unit (2) has a node library and a flowchart library. The node library stores node information for each node corresponding to the nodes provided to the developer by the IDE (1), i.e., the node list (225b) provided through the node selection menu (225) in Fig. 2e. Here, the node information includes program source or code information corresponding to the node. The flowchart library stores flowchart information corresponding to the flowchart list provided through the flowchart selection menu (223). The flowchart information stores program source or code information corresponding to the nodes included in the flowchart, and connection information between the nodes, i.e., edge (40, Fig. 3) information. That is, the flowchart library stores node information constituting the flowchart, its process flow information, and data flow information.

[0064] In FIGS. 1 and 2b, when a developer registers a flowchart through an input window (201), the IDE (1), i.e., the flowchart generator (10), creates a flowchart file along with directory information in the storage unit (2). When the developer calls a node (30) as a workspace (21) in FIG. 3, the flowchart generator (10) retrieves node information from the node library and stores it in a flowchart file. When the developer connects nodes using an edge (40), the flowchart generator (10) creates the connection information and stores it in a flowchart file. Accordingly, the flowchart file stores node information and their connection information corresponding to the flowchart created by the developer.

[0065] Figure 7 is a block diagram illustrating the configuration of an application development system according to an embodiment of the present invention. In the figure, the development system comprises a client side and a server side. The server side provides an IDE (110) that enables developers to create flowcharts. The IDE (110) is substantially the same as the IDE (1) described in Figure 1. The IDE (110) provides a flowchart generator (10) as an IDE providing means and a user interface (20) for developers or users, thereby providing means for creating flowcharts including data flows and process flows.

[0066] The server side is equipped with a storage device (120). This storage device (120), like the storage unit (2) of Fig. 1, includes a node library and a flowchart library for creating flowcharts. In addition, the server side is equipped with a flowchart execution engine (140) for developers to execute flowcharts. These server assets are connected to the IDE (110) via an API (Application Programming Interface) (130). As mentioned in Fig. 2, the user interface (20) is equipped with a task button (226) for executing the creation and editing of flowcharts, and a run button (227) for executing the flowchart. When the developer selects the run button (227) after creating the flowchart, the flowchart execution engine (140) is driven. The flowchart execution engine (140) may be, for example, a simulator for simulation or a compiler for compiling the flowchart into another appropriate programming language.

[0067] The embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments, and various modifications may be made without departing from the technical spirit thereof.

[0068] For example, in a preferred embodiment of the present invention, the IDE (1, 110) may provide a function that allows a developer to modify node information on a flowchart, i.e., the program source or code of a node, as needed. FIG. 8 is a diagram showing another configuration example of a selection window (213) related to a node (30) provided by a user interface (20), which corresponds to FIG. 2h. In the present embodiment, the selection window (213) is provided with a selection item (213a) that allows the developer to modify or edit the program source of the corresponding node (30). When the developer selects this, the IDE (1, 110) retrieves the corresponding program source from the storage unit (2, 120) and provides an editing window in which the developer can edit it. At this time, the modified code information will be stored in the flowchart file.

[0069] The present invention provides a means for easily developing software-based applications used in a wide range of fields, including games, graphics, computer-aided design (CAD), communications, document processing, office computing, databases, and numerical analysis for scientific and technological applications. Typically, applications are implemented through expert programming or coding. The present invention provides a graphical flowchart generation device that facilitates the easy and convenient development of such applications, and an application development system utilizing the same.

Claims

1. In a device that generates a flowchart used in the development of an application or model implemented in software, An IDE provider that provides an IDE that can create flowcharts based on graphics, and A first storage means having a node library, and It comprises a second storage means in which the flow chart is stored, The above IDE providing means includes a flowchart generator and a user interface, The above user interface includes a workspace and a selection menu, The above selection menu contains a list of nodes for selecting the nodes required to create the flowchart. The above user interface provides a node calling means for developers to call nodes into the workspace, The above node library is provided with node information corresponding to the node list, The above node information includes program source or code information, The above node has a process port that can be connected to other nodes through edges, A graphic-based flowchart generation device characterized in that node connection information is stored together with node information in the second storage means.

2. In paragraph 1, The above selection menu additionally includes a list of flowcharts for selecting a flowchart, A graphic-based flowchart generation device characterized in that the second storage means has a flowchart library corresponding to the flowchart list.

3. In paragraph 1, A graphic-based flowchart generation device, characterized in that the above node has a data port that can be connected to another node through an edge, and the data port includes an input port for data input or an output port for data output.

4. In paragraph 3, A graphical flowchart generator, characterized in that the above node includes a node for setting up a data flow.

5. In paragraph 1, A graphic-based flowchart generator, characterized in that the above node includes a node for setting a process flow.

6. In paragraph 5, A graphic-based flowchart generation device, characterized in that the above process flow setting node includes at least one of a path selection node, a loop control node, and a match-branch node.

7. In paragraph 6, The above IDE providing means is a graphic-based flowchart generation device characterized in that it provides a branch setting window for a developer to set the number of branches of a process flow setting node.

8. In paragraph 1, A graphic-based flowchart generation device characterized in that the above IDE providing means provides an editing means for a developer to modify or edit the above node information.

9. In an application development system used to develop applications or models implemented in software, An IDE provider that provides an IDE that allows developers to create flowcharts graphically, and A node library where node information is stored, A flowchart library where flowcharts are stored, and Consists of a flowchart execution engine that executes the flowchart, The above flowchart includes nodes and edges connecting the nodes. The above node has a process port that can be connected to other nodes through edges, The above edge includes an edge for setting the process flow, The above node information includes program source or code information, An application development system characterized in that the above flowchart library stores node information and connection information between nodes corresponding to the flowchart.

10. In paragraph 9, The above IDE providing means includes a user interface, The above user interface includes a workspace and a selection menu, The above selection menu contains a list of nodes for selecting the nodes required to create a flowchart, An application development system characterized in that the above user interface provides a node calling means for a developer to call a node as a workspace and an edge connection means for connecting between nodes through edges.

11. In paragraph 9, An application development system characterized in that the above node has a data port that can be connected to another node through an edge, and the data port includes an input port for data input or an output port for data output.

12. In paragraph 11, An application development system, characterized in that the above node includes a node for establishing a data flow.

13. In paragraph 9, An application development system, characterized in that the above node includes a node for setting a process flow.

14. In paragraph 13, An application development system characterized in that the above process flow setting node includes at least one of a path selection node, a loop control node, and a match-branch node.

15. In paragraph 9, An application development system characterized in that the above flowchart execution engine is a simulator.

16. In paragraph 9, An application development system characterized in that the above flowchart execution engine is a compiler.

Images