JPH1124904A - Program creation device and storage medium storing program creation program - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To provide a program creation device that realizes a highly versatile event procedure independent of the type of a module that is a connection candidate and improves the efficiency of man-machine program creation. A program creation device according to the present invention includes a display information file for storing display information, and a component common definition storage for storing function information in which a behavioral operation is defined independently of a correspondence relationship with the display information. Function information selecting means for selecting predetermined function information from the means 11, specific information determining means for determining specific information for the function information selected by the function information selecting means, and associating the selected display information with the function information Is provided from the display information, the function information, and the unique information, and the program execution means is configured to execute the program based on the display information, the function information, the unique information, and the connection information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program creating device and a storage medium storing the program creating program.

[0002]

2. Description of the Related Art A man-machine program is created in the following procedure. (1) Display information (screen) is created by arranging display modules (parts) such as buttons, labels, and texts in an area for screen editing and setting display attributes of each display module. (2) The behavior of the display information created in the above procedure is defined as an event procedure of each display module using a script language.

As a method for supporting the creation of a conventional event procedure, a “program creation method” (Japanese Patent Laid-Open No. 8-137)
678). In this method, a template of a procedure to be executed when an event occurs is prepared in advance as a connector module. FIG. 25 is a diagram showing a functional configuration of a conventional program creating system described in Japanese Patent Application Laid-Open No. 8-137678. In the figure, reference numeral 101 denotes a request input for inputting a request from a user via an input device or a computer connected to a network;
4. Analysis control in which a necessary function among the navigator 105, the connector generation 106, and the interpretation / execution 107 is called and the result is passed to the response output 103.

Reference numeral 104 denotes program information 1 to be edited
09 and module information 10 which is a component of the program
8, program editing to read, write, edit,
Navigator 106 that reads navigation information 110 that guides a method of combining modules at the time of editing in program editing 104 and a user level 111 that restricts the use of navigation information 110 according to the level of the user, and performs the guidance, 106 A module for combining the modules is generated from the guidance result, the generated module (hereinafter, referred to as a connector) is written to the connector 112, and the relationship between the generated combined module and the generated module is represented by program information. Create connector to write to 109, 107
Is an interpretation / execution for reading, interpreting and executing the program information 109, the module information 108 and the connector 112.

Next, a method of creating a program will be described. First, in the program editing 104, the module stored in the storage device (module information 108) is displayed on the display device according to the instruction from the request input 101. Then, a module for performing a combination between modules is input from the request input 101 from among the displayed modules,
In response to a command from the request input 101, the navigator 10
In step 5, a search is performed for a navigation program that guides a combination between modules (including behavior between program modules) stored in the storage device based on the type of the selected module, and the searched navigation program group is displayed. Display on the device.

Then, the user selects an arbitrary navigation program from the displayed navigation program group, and the selected navigation program is operated. here,
The navigating program, when a module is selected,
In order for the navigation program corresponding to the module to be called, the navigation information 110 is stored in association with the module and the navigation program.

[0007] Next, in order to make a combination between modules, according to the navigating program, a guide parameter output by the navigating program is specified, and a connector module for making a combination between modules based on the input guiding parameter. Is generated and stored in the storage device (connector 112). Finally, in analysis / execution 107, the program is executed based on the program information 109, module information 108, and information stored in the connector 112.

[0008]

Since the conventional method of creating a program is performed as described above, there are the following problems. During the event procedure, a navigation program corresponding to the selected module is executed, and a connector is generated according to the guidance of the navigation program, so that the navigation program is dependent on the selected module. The connector that defines the behavior of the module created according to the guidance also depends on the module. Therefore, the definition of the procedure inside the connector depends on the module that is a connection candidate, and the versatility of the connector is low.

When the behavior to be defined is composed of a plurality of behaviors, the behaviors are not defined individually, but are defined as one behavior in which the behaviors are put together. Connection cannot be defined. Furthermore, since the connection target to the connector is limited to the componentized module, it can be connected only to the connection target component,
Connection with other parts or parts with different platforms cannot be made.

The present invention has been made to solve such a problem, and realizes a highly versatile event procedure that does not depend on the type of a module as a connection candidate, thereby improving the efficiency of man-machine program creation. An object of the present invention is to provide a device and a storage medium storing a program creation program. In addition, a program creation device and a program creation program that improve the efficiency of man-machine program creation by enabling the behavior of a program to be defined not only by function information and display information but also by a combination between function information are stored. It is to provide a storage medium.

[0011]

According to the present invention, there is provided a program creating apparatus for storing display information storing means for storing display information, and function information in which a behavioral operation is defined independently of a correspondence relationship with the display information. Function information common definition storing means, function information selecting means for selecting predetermined function information from function information stored in the function information common definition storing means, and a function information specific to the function information selected by the function information selecting means. Unique information determining means for determining the information of the display information, the connection information defining the association between the display information and the function information selected by the function information selection means display information, function information, connection information creation means to create from the unique information, Program execution means for executing a program based on display information, function information, unique information, and connection information.

Further, the connection information creating means displays a display component corresponding to the display information and a functional component corresponding to the selected function information, and uses the displayed display component and the functional component to generate the connection information. create.

[0013] The connection information creating means may store the connection information defining the association between the first function information and the second function information selected by the function information selecting means, with the first and second function information, and 1. It is created from the first and second unique information for the second function information. Further, the connection information creating means includes:
A first function component corresponding to the selected first function information and a second function component corresponding to the selected second function information are displayed, and the displayed first function component and the second function component are displayed. Create connection information using the functional components. Furthermore, there are a plurality of pieces of information defined to be associated with the function information or the display information.

The function information includes input terminal information for receiving information from display information, an update function simulating the behavior of the function information, a state variable relating to the update function, and an output for outputting a result obtained by the update function. It includes terminal information and an evaluation condition for selecting one or both of input terminal information to be input and output terminal information to be output.

Further, the input terminal information is one or both of an event terminal for receiving an event input and a data input terminal for receiving data required for executing an update function. Furthermore, at least one of the update function, the input terminal information, and the output terminal information is plural. The functional component has a component name corresponding to the function information, an input terminal corresponding to the input terminal information, and an output terminal corresponding to the output terminal information.

Further, the display information includes type data information defining a data type, the function information includes type data information defining a data type, and the connection information creating means includes the type data of the function information and the function information. When the type data of the information to be associated with is the same, it is associated with this function information.

Further, the display information includes type data information defining a data type, the function information includes type data information defining a data type, and includes type conversion storage means defining a type conversion rule. The information creating means associates the function information with the function information when the type data of the function information and the type data of the information relating the function information are the same as the type conversion rules defined in the type conversion storage means. .

Further, there is provided a connection mode storage unit which defines the correspondence between the connection source and the connection destination, and the connection method generation unit generates connection information based on the correspondence stored in the connection mode storage unit.

The storage medium storing the program creation program according to the present invention is a display component for selecting predetermined display information from display information storage means storing display information and displaying a display component corresponding to the display information. The display process and the display information are selected independently from the function information common definition storage unit that stores the function information in which the behavioral operation is defined independently of the correspondence between the display information and the function component corresponding to the function information. A function component display process to be displayed, a unique information determination process for determining unique information for the functional component displayed in the function component display process, and connection information defining an association between the selected display information and the function information are displayed. Connections created by visually defining the correspondence between displayed display components and functional components A distribution creation programs, display information, function information, and stores the unique information, the program generation program including a program execution program for executing the program based on the connection information.

Further, the functional component display process displays a plurality of functional components, and the connection information creating process determines a correspondence relationship between the plurality of functional components for which connection information for defining association of the selected function information is displayed. Create by defining visually.

Further, as the function information, input terminal information for receiving information from the display information, an update function simulating the behavior of the function information, a state variable relating to the update function, and a result obtained by the update function are output. Output terminal information,
An evaluation condition for selecting one or both of input information to be input and output terminal information to be output is provided. The functional component includes a component name corresponding to the function information, an input terminal corresponding to the input terminal information, and an output terminal. And an output terminal corresponding to the information.

Further, the display information includes type data information that defines a data type, the function information includes type data information that defines a data type, and the connection information creating process includes the step of creating the type data of the function information and the function data. When the type data of the information to be associated with the information is the same, the information is associated with the function information.

[0023]

BEST MODE FOR CARRYING OUT THE INVENTION

Embodiment 1 FIG. FIG. 1 is a diagram showing a configuration of a man-machine program creating device according to Embodiment 1 of the present invention. In the figure, 1 is an input device for inputting by a keyboard, a pointing device, a computer or the like via a network, 2 is an output device for outputting output information, 3 is a screen editing management 4, a function editing management 5, and a program execution management 9. This is program creation management for managing which of the processes is to be performed.

Reference numeral 4 denotes a screen edit management for displaying and editing necessary modules (hereinafter, referred to as display parts) on the screen. Reference numeral 5 denotes function information for defining the behavior of the display parts displayed in the screen edit management 4 and this function. Function edit management for creating connection information defining the relationship between information and display components, 6 is a component generation unit for creating components (described below), 7 is for designating display components and components, or a combination between components Combination designating means, 8
Is a connection inspection means for determining whether the combination specified by the combination specifying means 7 is appropriate, and 9 is a program execution management for managing the execution of the program.

Reference numeral 10 denotes a display information file for storing information of display components. Reference numeral 11 denotes function information for defining the function of the display information independently of the correspondence relationship with the display information, and information of components visualizing the function information. A stored component common definition file, 12 is a component unique information file for storing unique information for determining characteristics of each component, 13 is a component attribute list file storing component attributes, 14 is display information and function information, Or
6 is a connection information file that stores connection information indicating a connection relationship between function information.

Next, the operation of the man-machine program creating apparatus shown in FIG. 1 will be described with reference to the flowchart shown in FIG. When the man-machine program creating device is started, first, an initial screen is displayed (S101).

FIG. 3 is a diagram showing a configuration of an initial screen according to the present embodiment. As shown in FIG. 3, the initial screen includes a parts list display area 21 in which a list of parts for creating display information is displayed, and a parts screen for creating display information from the parts displayed in the parts list display area 21 An editing area 22, a component list display area 23 for displaying a list of components (described in detail below) defining behaviors related to components, and components selected and displayed from the components displayed in the component list display area 22. Function editing area 24 for creating connection information between parts or components, screen editing button 25a, function editing button 25b, execution button 25c, end button 2
It is composed of a button group 25 such as 5d.

After the initial screen is displayed, an input on this initial screen is accepted. When the screen edit button 25a shown in FIG. 3 is selected, S103 is executed, when the function edit button 25b is selected, S104 is executed, and when the execute button 25c is selected, S105 is executed.
When the end button 25d is selected, the program creation management process ends. (S102)

[Processing Flow of Screen Editing Management] Next, S1
03 will be described. S103 is processing for accepting an input of the screen editing area 22 shown in FIG. 3 in the screen editing management 4 shown in FIG. In S102, FIG.
When the screen edit button 25a shown in FIG. 1 is selected, the screen edit management 4 shown in FIG. 1 searches the component attribute list file 13 to obtain a list of component names, and displays the list in the component list display area 21 shown in FIG. indicate. When a component displayed in the component list display area 21 is selected through the input device, a component ID is assigned to the selected component, and the component name and the component ID are set in the screen editing area 22 shown in FIG. Displays the selected and included parts.

FIG. 4 is a view showing an example of the parts displayed in the screen editing area 22 shown in FIG. In FIG. 4, n text parts, n label parts, and two button parts are displayed. Each of the n text parts has a part name of Text and a part ID of 1 to n, and n parts. Label parts are labeled Label and 1 to n, respectively.
Are the Button IDs of the two button components, respectively.
The part name “on” and the part IDs 1 and 2 are both displayed.

In step S103, initial values such as a display position, a display color, and a display size for the selected component are determined, and display information indicating information of the generated component is generated. FIG. 5 is a diagram showing the structure of the display information file. The display information file includes a screen ID of a screen on which the component is displayed, a component name indicating the type of the component, a component ID,
It consists of display attribute names such as display position, display color and display size, and initial values for the display attributes.

[Processing Flow of Function Editing Management] Next, FIG.
The processing of S104 (function editing) shown in FIG. In step S104, in the function edit management 5 shown in FIG.
This is a process of creating the behavior and connection information of the components created in the screen editing management 4. FIG. 6 shows S104 shown in FIG.
FIG. 7 is a processing flowchart illustrating the processing of FIG. S shown in FIG.
In 102, when the function edit button 25b shown in FIG. 3 is selected, the function edit management 5 shown in FIG. 1 displays a function edit screen (S201). FIG. 7 is a diagram showing a display example of a function editing screen. As shown in FIG. 7, the function editing screen includes a component generation button 24a, a component connection button 24b, an inter-component connection button 24c, an end button 24d, and a connection flow diagram display area 24e.

After the function edit screen 24 is displayed, an input on the function edit screen 24 is accepted. When the component generation button 24a shown in FIG. 7 is selected, S203 is executed. When the component connection button 24b is selected, S204 is executed. When the component connection button 24c is selected, S210 is executed. . And
When the end button 24d is selected, the function editing management process ends. (S202)

[Processing Flow of Component Generation Means]
Next, the processing of S203 (component generation) shown in FIG. 6 will be described in detail. In step S203, the component generation unit 6 illustrated in FIG. 1 creates a component (described in detail below) that defines a behavior related to the component created in the screen editing management 4.

Here, the components will be described before describing the processing of S203. FIG. 8 is a diagram showing a configuration of a component. FIG. 8A is a diagram for explaining the function of the component, and FIG. 8B shows an example of the component actually displayed. As shown in FIG. 8A, components are used to define behavior and connection information for components. Each component is connected to a state variable and an input terminal for storing data unique to each component. Using the acquired value and the value of the state variable, an update function that updates the output value and the value of the state variable, an event terminal for controlling the execution start / stop of the update function, and the input / output processing of the update function An input terminal and an output terminal are used as connection terminals. The description of the update function differs from the definition in the script language in the past, and does not include the description depending on the display component of the screen.

When an evaluation condition is provided and a component has a plurality of event terminals, it is possible to set which input / output terminal is to be evaluated or not for each event (type of event terminal) to be generated. It is possible. Thus, it is possible to perform fine control such as setting data to an output destination only when a certain event occurs.

Here, the state variables, update functions, and input / output data types are defined in common for all screens. Conversely, event reception targets and input / output parameters (actual data) are It is unique for each screen.

When defining the behavior corresponding to the display information using the components shown in FIG. 8A, a component name and a component ID for recognizing the component, and an event for indicating the connection relationship are defined. , Input and output terminals are displayed as shown in FIG. 8 (b), and the connection relationship between the terminals is visually defined to define the correspondence. Note that, here, for simplicity of description, components each having one event, input, and output terminals are shown, but this is not particularly limited to one, and the event terminal, the input terminal, and the input terminal are not limited to one. , There can be a plurality of output terminals. In addition, since the connection between the terminals can define the connection between a component and a component and the connection between a component and another component, a plurality of behaviors can be defined by connecting a plurality of components. Note that the connection between the terminals includes connecting a plurality of components or a plurality of display components to one component, connecting a plurality of display components to one component,
Furthermore, these can be combined.

FIG. 9 is a processing flowchart for explaining the processing of S203 shown in FIG. First, the component common definition file 11 shown in FIG. 1 is read, and a list of component names registered in this file is displayed in the component list display area 23 shown in FIG. (S3
01)

FIG. 10 is a diagram showing a record structure of the component common definition file 11. The common definition file 11 is output using a component name indicating a type of the component, a state variable list including a list of state variables for storing data unique to each component, input values, and values of the state variables. An update function list consisting of a list of update functions for updating values and values of state variables,
An event terminal list including a list of event terminals for controlling execution start / stop of the update function, an input terminal list including a list of input terminals used for input processing of the update function, and an output terminal used for output processing of the update function The output terminal list is composed of the following list.

More specifically, as shown in FIG. 10B, the record structure of the state variable list includes a variable name of the state variable and a data type indicating the data type of the variable name. As shown in FIG. 10C, the record structure of the update function list has a function name of the update function, a program address where an execution program of the update function is stored, and
It consists of evaluation conditions corresponding to the input terminal evaluation conditions. As shown in FIG. 10D, the record structure of the event terminal list includes a terminal number of the event terminal and a data type to which the event terminal belongs.

The record structure of the input terminal list is, as shown in FIG. 10E, the terminal number of the input terminal, the data type to which the input terminal belongs, and the evaluation for determining the input terminal for inputting the input value. Consists of conditions. The record structure of the output terminal list is the same as the record structure of the input terminal list shown in FIG. The evaluation condition stores an event number (a plurality of events can be specified) serving as a condition for executing the update function. The evaluation conditions include the input terminal (or
An event number (a plurality can be specified) serving as a condition for applying an evaluation described later to the (output terminal) is stored.

When a component displayed in the component list display area 23 shown in FIG. 3 is selected through the input device, a value (component name) of the selected component is obtained. (S302) Then, a record having a component name that matches the selected component is searched from the common definition file 11 shown in FIG. 1, and the variable name and data type are obtained using the values of the state variable list of the matching record. To display the unique information setting screen. (S303)

FIG. 11 shows the configuration of a screen for setting component-specific information. The component specific information setting screen includes a component name 31, a component ID 32,
It comprises a group of buttons 35 such as a variable display area 33, a message display area 34, a registration button 35a, an end button 35b, and the like. In the component name 31, the selection value of S302 is displayed. A continuous number (1, 2,..., N) for each component type is sequentially assigned to the component ID 32 every time a component is generated. The variable display area 33 includes a variable name 33a and its initial value setting area 33.
The variable obtained by the search in S303 is displayed in the variable name 33a.

When the screen for setting the unique information is displayed, the input of the setting screen is accepted through the input device.
Initial value setting area 33b of variable display area 33 on the setting screen
When the variable is displayed and the variable display area 33 is selected, S305 is executed, and when the registration button 35a is selected, S307 is executed. When the end button 35b is selected, the process of component generation management ends.
(S304) In S304, a value is input to the initial value setting area 33b of the variable display area 33 of the setting screen, and the variable display area 33 is set.
Is selected, the initial value setting area 33 of the selected variable
Obtain the value input to b. (S305)

Then, the data type of the initial value obtained in S305 and the data type of the variable obtained in S303 are compared. As a result of the comparison, if the data types are the same, the message "set value O" is displayed in the message area 34 shown in FIG.
K ”is output, and the process returns to S304. If the data types are different, "data type mismatch" is output to the message area 34, the data is deleted, and the process returns to S304.

Next, when the registration button 35a shown in FIG. 11 is selected in S304, the initial values set for the respective variables are stored in the component unique information file 12 shown in FIG. (S307) FIG. 12 is a diagram showing the structure of the component specific information file. The unique information file 12 includes a screen ID, a component name, a component ID, a state variable name, and an initial value. For the component name, the component name acquired in S302, and for the component ID, S30
In step S306, the number assigned in step 3 and the state variable name and the initial value respectively store the initial value for which the data type check has been completed.

When the setting of the unique information is completed as described above, the component for which the setting of the unique information is completed is shown in FIG.
Connection flow diagram display area 24e of the function editing screen shown in FIG.
To be displayed additionally. (S308) FIG. 13 is a diagram in which components are additionally displayed in the connection flow diagram display area 24e shown in FIG. The display of a component consists of the component name, the I
In addition to D, an event terminal, an input terminal, and an output terminal list corresponding to the component name are searched from the component common definition file 11 shown in FIG. 1, and the terminal numbers included in these lists are also displayed. For example, FIG.
In the case of the component below the connection flow diagram display area 24e, the component name (Component_
C), a component when a new component with ID (0) is generated is additionally displayed.

[Process Flow of Connection Between Components and Components] Next, S204 to S209 shown in FIG. 6 will be described. In S202, when the component connection button 24b shown in FIG. 13 is selected, the selection of the connection source terminal is accepted. (S204) When the terminal of the component displayed in the connection flow diagram display area 24e shown in FIG. 13 is selected according to the input from the input device, the component name, ID, and the selected component (connection source) are selected. To get the terminal number. (S204) Then, a connection destination component selection screen for selecting a connection destination component name is displayed. (S205)

FIG. 14 is a diagram showing the configuration of a connection part selection screen. The connection destination component selection screen includes a connection source component name 41, a connection source component ID 42, a connection source terminal number 43, a connection destination component name display area 44, a connection destination component ID display area 45, and a connection destination attribute name display area 46. . 41 to 43 display the selection values (component name, ID, terminal number) acquired in S204.

In the connection destination part name display area 44, the display information file 10 shown in FIG. 1 is searched using the screen ID of the screen currently being edited, and matches the screen ID of the currently edited screen. A list of component names having a screen ID is obtained and displayed. Connection part ID display area 45
FIG. 1 shows a list of component IDs of the component name when a component name in the connection destination component name display area 44 is selected, and a list of display attributes of the component in the connection destination attribute name display area 46. The results retrieved from the displayed information file 10 are displayed.

Then, the component name, component ID, and display attribute name of the connection destination set on the connection destination component selection screen in S205 are acquired. (S206) Next, the data type of the connection source terminal is compared with the data type of the display attribute of the connection destination component. The data type of the connection source terminal is S2
The component common definition file 11 shown in FIG. 1 is searched for and obtained using the component name and the terminal number acquired in step 04. The data type of the display attribute is determined by searching the component attribute list file 13 shown in FIG. 1 using the component name and the display attribute name acquired in S206.

FIG. 15 is a diagram showing the structure of the component attribute list file 13. The component attribute list file 13 includes a component name, a display attribute name, and a data type. If the data type does not match as a result of the comparison between the data type of the connection source terminal and the data type of the connection destination (display attribute), the process returns to S202. If the data types match as a result of the comparison, the connection information is stored in the connection information file 14 shown in FIG. The connection information file will be described later. (S20
8)

When the above connection information is registered, the connection flow diagram display area 24 shown in FIG.
The connection state of the terminal is additionally displayed in e. (S209) A data flow indicating the connection relationship between the connection ID and the label added to indicate the component ID and the display attribute is displayed.
In the case of the connection relationship at the upper left of the connection flow diagram display area 24e in FIG.
The case where the state attribute of the button component Button1 is connected is displayed.

[Process Flow of Connection Between Components] Next, S210 to S214 shown in FIG. 6 will be described. S2
In 02, when the inter-component connection button 24c shown in FIG. 13 is selected, the selection of the connection source terminal is accepted. When the terminal of the component displayed in the connection flow diagram display area 24e shown in FIG. 13 is selected as the connection source terminal according to the input from the input device, the component name, ID, and terminal number of the connection source terminal are obtained. I do. (S210)

After the connection source terminal is selected, the selection of the connection destination terminal is accepted. When the terminal of the component displayed in the connection flow diagram display area 24e shown in FIG. 13 is selected as the connection destination terminal according to the input from the input device, the component name, ID, and terminal number of the connection destination are acquired. (S211)

Next, when the connection source terminal and the connection destination terminal are selected in this way, the data type of the connection source terminal selected in S210 is compared with the data type of the connection destination terminal selected in S211. I do. The data type of each terminal is obtained by searching the component common definition file 11 shown in FIG. 1 using the component name and the terminal number. If the data types do not match as a result of the comparison, the process returns to S202. (S2
12) If the data types match as a result of the comparison, the connection information is stored in the connection information file 14 shown in FIG. (S21
3)

FIG. 16 is a diagram showing the structure of the connection information file 14. As shown in FIG. 16A, the connection information file 14 includes a screen ID, a connection source component name, a component ID of the connection source component, a connection source terminal number, and a connection target. The record structure to be connected is
It consists of a connection component information storage record or a connection component information storage record. It should be noted that a plurality of connection component information storage records and connection component information storage records are prepared when there are a plurality of connection targets. The connection part information storage record is shown in FIG.
As shown in the figure, the information includes a component name, a component ID, and an attribute name. The values acquired in S206 are set for the component name, component ID, and attribute name.

As shown in FIG. 16C, the connection component information storage record includes a connection destination component name, a component ID of the connection destination component, and a terminal number of the connection destination. The values acquired in S211 are set for the component name, component ID, and terminal number, respectively. The selection value of S204 or S213 is stored in the component name, the component ID, and the terminal number.

When the connection information is registered, the connection state of the terminal is additionally displayed in the connection flow diagram display area 24e of FIG. 13 according to the connection information. (S214) A data flow indicating the connection relationship between the connection source terminal and the connection destination terminal is displayed. In the case of the connection relation of the components at the upper right of the connection flow diagram display area 24e in FIG. 13, the case where the output terminal OUT1 of the component A and the event terminal EV1 of the component B are connected is displayed.

[Process Flow of Program Execution Management] Next, the process of S105 shown in FIG. 2 will be described. FIG. 17 is a diagram showing a detailed flow of S105. S401 is an input receiving process of the program execution management. An event generated by operating a component displayed on the connection flow diagram display area 24e shown in FIG. 13 is received, and a component name and a component ID in which the event has occurred are acquired. FIG.
When the connection flow from the output terminal to the event terminal is defined between the components displayed on the connection flow diagram display area 24e shown in (2), this occurs when the output terminal of the component is evaluated in a procedure described later. The event is received, and its component name, ID, and output terminal are obtained.

In step S402, the component name, component ID, and display attribute (or component name, ID,
Output terminal), the connection information file 1 shown in FIG.
4 is searched for the connection destination component name and event terminal number. In step S403, the update function, the event terminal, the input terminal, and the output terminal list are respectively searched from the component common definition file 11 illustrated in FIG. 1 using the component name acquired in step S402.

In step S404, the input terminal list acquired in step S403 is sequentially evaluated. If the evaluation condition of the input terminal matches the event terminal number obtained in S402, the connection source component (or connection destination component) of the terminal is searched from the connection information file 14 shown in FIG. Executes input processing according to the type of component name (or component name). In step S405, an update function having an evaluation condition that matches the event terminal number acquired in step S402 is searched from the function list of the component acquired in step S403.

In step S406, the procedure specified by the program address of the update function acquired in step S403 is executed. S
407 evaluates the output terminal list acquired in S403 in order. If the evaluation condition of the output terminal matches the event terminal number acquired in S402, the connection destination component (or connection destination component) of the terminal is searched from the connection information file 14 shown in FIG. Executes output processing according to the type of component name (or component name).

In this embodiment, a description has been given of the parts, the components, and the connection method between the components.
It goes without saying that these components may be connected first, and then connected between components and components.

In this embodiment, since the function information for defining the behavior does not depend on the components, highly versatile function information independent of the type of the connection candidate component can be used. Creation efficiency can be improved. Furthermore, the connection is determined not by the type of the component but by the data type of the connection terminal, so the connection depends not on the component but on the data type. Parts created on different platforms can also be connected.

Further, a combination definition can be defined not only between components and components but also between components. That is, since the function information defining the behavior for the components can be connected, the behavior composed of a plurality of functions can be defined for each component. It can be defined for each behavior.

Further, since the program execution management automatically inputs and outputs data necessary for the execution of the component based on the types of connection terminals and connection information of the component,
Inside the component, there is no need to define a process according to the connection target.

Embodiment 2 This embodiment is obtained by adding processing for performing a type conversion procedure according to a type conversion rule file when the data type of the connection destination and the connection source do not match in the processing flow of the function editing management shown in FIG. FIG. 18 is a diagram showing a configuration of a man-machine program creating device according to the second embodiment of the present invention. In the figure, 15
Is a type conversion rule file that indicates the type conversion rules that allow connection between the connection source and connection destination data. The other parts are the same as those shown in FIG.

This embodiment is the same as Embodiment 1 except for the method of generating the connection information, and the other description is omitted. FIG. 19 is a flowchart of the second embodiment of the present invention. S501 to S514 correspond to the S described in FIG.
The description is omitted because it is the same as 201 to S214.

First, in the data type check in S507,
If the data types match, S508 is executed. If they do not match, S515 is executed. S515 is S50
It is checked by searching the type conversion rule file 15 shown in FIG. 18 whether the type conversion from the data type of the connection source terminal obtained in step 4 to the data type of the display attribute obtained in step S506 is possible. FIG. 20 is a diagram showing the structure of the type conversion rule file 15 shown in FIG. Type conversion file 15
Consists of a connection source data type, a connection destination data type, and a conversion procedure name indicating the name of this conversion procedure.

Then, as a result of searching the type conversion rule file 15, if there is no conversion procedure in which the data types of the connection source and the connection destination match, the process returns to S502. If there is a conversion procedure in which the data types of the connection source and the connection destination match, S509 is executed. S509 is composed of S504 and S
The connection information acquired in 506 is stored in the connection information file 14 shown in FIG. If the conversion procedure has been acquired in S508, the conversion procedure name is also stored.

In the embodiment of the present invention, the connection is determined by the type conversion rule file and if the type conversion is possible, the type conversion procedure is added to the connection information. In this case, the connection can be defined.

Embodiment 3 In this embodiment, in the processing of the function editing management shown in FIG. 6, a combination of connections is changed to a processing of designating by selecting from a connection pattern file. FIG. 21 is a diagram showing a configuration of a man-machine program creating device according to the third embodiment of the present invention. In the figure, reference numeral 16 denotes a connection pattern file indicating connection patterns. The other parts are the same as those shown in FIG.

This embodiment is the same as Embodiment 1 except for the method of generating the connection information, and the other description is omitted. FIG. 22 is a flowchart in which the combination of connections is changed to the process of designating by selecting from the connection pattern file 16 shown in FIG. 21 in the processing flow of the function editing management shown in FIG. Steps S601 to S603 are the same as steps S201 to S203 shown in FIG. Hereinafter, the processing described in FIG. 6 will be omitted.

Step S604 is a process for displaying a list of connection pattern names registered in the connection pattern file 16 shown in FIG. FIG. 23 shows the connection pattern file 14.
FIG. 3 is a diagram showing the structure of FIG. As shown in FIG. 23A, the connection pattern file 14 includes a connection pattern name, a connection source component name, a terminal number, and a connection target. The connection target record structure includes a connection component information storage record or a connection component information storage record, as shown in FIG. As shown in FIG. 23B, the connection part information storage record includes a connection destination part name and a display attribute name. The connection component information storage record includes a connection destination component name and a terminal number, as shown in FIG. In step S605, a value selected from the connection pattern name displayed in step S604 is acquired based on an input from the input device.

FIG. 24 is a diagram showing the configuration of the connection setting screen. The connection setting screen includes a button group 5 including a connection pattern name 51, a connection parameter setting area 52, a connection pattern flow chart 53, a registration button 54a, and an end button 54b.
4. Connection parameter setting area 52
Consists of a component name display area 52a, a component name display area 52b, and an ID input area 52c. S606 is S6
The connection pattern file 16 shown in FIG. 21 is searched using the connection pattern name acquired in step 05, the connection source component name, the connection destination component name, and the connection destination component name that match the connection pattern name are obtained. 5
2 is displayed.

Step S607 is an input receiving process in the connection parameter setting area. When the ID input area 52c is selected, S608 is executed, and when the registration button 54a is selected, S610 is executed. Then, when the end button 54b is selected, the process returns to S602. S608
Acquires the value set in the ID input area in S607.
In step S609, the value acquired in step S608 is stored in the connection information file 14 illustrated in FIG. In the connection information file 14, the ID acquired in S608 is added to each of the connection source component name, the connection destination component name, and the connection destination component name acquired in S606, and stored in a format suitable for the file structure.

In this embodiment, by making settings using the connection pattern in the connection pattern file,
The connection information can be generated only by specifying the ID of the component to which the connection pattern is applied and the ID of the component. Therefore, it is possible to simplify the combination specification on a screen in which the same connection format is repeatedly used.

Note that the program creation methods described in the first to third embodiments are realized by, for example, a program creation program, which is a compact disk (CD-ROM), a magneto-optical disk (MO), a flexible disk ( FD) or the like and provided.

[0081]

According to the program creating apparatus of the present invention, since the function information in which the behavioral operation is defined in advance is defined independently of the correspondence with the display information, the function information does not depend on the display information. This makes it possible to use highly versatile function information that does not depend on the type of a component that is a connection candidate, thereby improving the efficiency of man-machine program creation.

The connection information creating means displays a display component corresponding to the display information and a functional component corresponding to the selected function information, and uses the displayed display component and the functional component to convert the connection information. To create
The connection information can be easily created visually.

The connection information creating means stores the connection information defining the association between the first function information and the second function information selected by the function information selecting means, as the first and second function information, and the first and second function information. Since it is created from the first and second unique information for the second function information, when the behavior to be defined is composed of a plurality of behaviors, a plurality of functions can be individually defined. Versatile function information that defines the behavior of the program can be used, and the efficiency of man-machine program creation can be improved.

The connection information creating means displays a first function component corresponding to the selected first function information and a second function component corresponding to the selected second function information, and the display is performed. Since the connection information is created using the first functional component and the second functional component, the connection information can be easily created visually.

Since there are a plurality of pieces of information for which the association is defined with the function information or the display information, the association between one or a plurality of pieces of information and other pieces of information can be defined.

The function information includes input terminal information for receiving information from the display information, an update function simulating the behavior of the function information, state variables related to the update function, and output terminal information for outputting a result obtained by the update function. And evaluation conditions for selecting one or both of the input terminal information to be input and the output terminal information to be output, the function information can be made independent of the display information.

Since the input terminal information is one or both of an event terminal for receiving an event input and a data input terminal for receiving data necessary for executing an update function, it is possible to distinguish between an event input and a data input. Connection between terminals can be facilitated.

Since at least one of the update function, the input terminal information, and the output terminal information is plural, it is possible to add a new required behavior or define an association with plural pieces of information. it can.

Since the functional component has a component name corresponding to the function information, an input terminal corresponding to the input terminal information, and an output terminal corresponding to the output terminal information, connection between the terminals is facilitated. Can be.

The connection information creating means associates the function information with the function information when the type data of the function information and the type data of the information associated with the function information are the same, so that the connection does not depend on the parts. It is possible to connect to other platforms.

The connection information creating means is provided with type conversion storage means for defining type conversion rules. The type information of function information and the type data of information for associating the function information are defined by the type conversion storage means. Since it is associated with this function information when the type conversion rule is the same, connection can be made even if the type data is different.

A connection mode storage unit that defines the correspondence between the connection source and the connection destination is provided. The connection information generation unit generates connection information based on the correspondence stored in the connection mode storage unit. The connection information can be created more easily simply by selecting the correspondence defined in the mode storage means.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a program creation device according to a first embodiment of the present invention.

FIG. 2 is a flowchart illustrating a process according to the first embodiment of the present invention.

FIG. 3 is a diagram showing a configuration of an initial display screen according to the first embodiment of the present invention.

FIG. 4 is a diagram showing a configuration of a screen editing screen according to the first embodiment of the present invention.

FIG. 5 is a diagram showing a structure of a display information file shown in FIG.

FIG. 6 is a flowchart showing a function editing process of FIG. 2;

FIG. 7 is a diagram showing a configuration of a function editing screen according to the first embodiment of the present invention.

FIG. 8 is a diagram illustrating components according to the first embodiment of the present invention.

FIG. 9 is a flowchart illustrating a generation process of the component of FIG. 6;

FIG. 10 is a diagram showing the structure of a component common definition file.

FIG. 11 is a diagram showing a configuration of a component specific information setting screen.

FIG. 12 is a diagram showing the structure of a component specific information file.

FIG. 13 is a diagram showing a configuration of a function editing screen according to the first embodiment of the present invention.

FIG. 14 is a diagram showing a connection destination component selection screen according to the first embodiment of the present invention.

15 is a diagram showing the structure of a component attribute list file shown in FIG.

FIG. 16 is a diagram showing the structure of a connection information file shown in FIG.

FIG. 17 is a flowchart showing a process of executing the program of FIG. 2;

FIG. 18 is a configuration diagram of a program creation device according to a second embodiment of the present invention.

FIG. 19 is a flowchart illustrating a process according to the second embodiment of the present invention.

20 is a diagram showing the structure of the type conversion rule file shown in FIG.

FIG. 21 is a configuration diagram of a program creation device according to a third embodiment of the present invention.

FIG. 22 is a flowchart illustrating a process according to the third embodiment of the present invention.

FIG. 23 is a diagram showing a structure of a connection pattern file shown in FIG. 21.

FIG. 24 is a diagram showing a configuration of a connection setting screen according to the third embodiment of the present invention.

FIG. 25 is a configuration diagram of a conventional program creation device.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 Input device 2 Output device 3 Program creation management 4 Screen editing management 5 Function editing management 6 Component generation means 7 Combination designation means 8 Connection inspection means 9 Program execution management 10 Display information file 11 Component common definition file 12 Component specific information file 13 Parts Attribute list file 14 Connection information file 15 Type conversion rule file 16 Connection pattern file 21 Parts list display area 22 Parts screen editing area 23 Component list display area 24 Function editing area 24a Component generation button 24b Component connection button 24c Component connection button 24d end button 24e connection flow diagram display area 25 button group 25a screen edit button 25b function edit button 25c execute button 25d end button 31 Component name 32 Component ID 33 Variable display area 33a Variable name 33b Initial value setting area 34 Message display area 35 Button group 35a Registration button 35b End button 41 Connection source component name 42 Connection source component ID 43 Connection source terminal number 44 Connection destination part name Display area 45 Connection destination part ID display area 46 Connection destination attribute name display area 51 Connection pattern name 52 Connection parameter setting area 52a Component name display area 52b Component name display area 52c ID input area 53 Connection pattern flow diagram 54 Button group 54a Registration button 54b End button 101 Request input 102 Analysis control 103 Response output 104 Program editing 105 Navigator 106 Connector generation 107 Interpretation / execution 108 Module information 109 Program Information 110 Navigating information 111 User level 112 Connector

Claims (17)

[Claims] 1. A display information storage means for storing display information; a function information common definition storage means for storing function information in which a behavioral operation is defined independently of a correspondence relationship with the display information; Function information selecting means for selecting predetermined function information from function information stored in the common definition storage means, and unique information determining means for determining information unique to the function information selected by the function information selecting means; The connection information defining the association between the display information and the function information selected by the function information selection means, the display information, the function information, the connection information creating means for creating the unique information, the display information, A program execution unit for executing a program based on the function information, the unique information, and the connection information. Place. 2. A connection information creation means for displaying a display component corresponding to the display information and a functional component corresponding to the selected function information, and using the displayed display component and the functional component to generate the connection information. 2. The program creating apparatus according to claim 1, wherein the program is created. 3. The connection information creating means includes: connection information defining an association between the first function information and the second function information selected by the function information selection means; First and second functions corresponding to the first and second function information
The program creation device according to claim 1, wherein the program creation device is created from the unique information. 4. The connection information creating means displays a first function component corresponding to the selected first function information and a second function component corresponding to the selected second function information, and displays the first function component corresponding to the selected second function information. 4. The program creating apparatus according to claim 3, wherein the connection information is created using the displayed first functional component and the displayed second functional component. 5. The apparatus according to claim 1, wherein a plurality of pieces of information are defined in association with the function information or the display information.
5. The program creation device according to any one of items 4 to 5. 6. The function information includes input terminal information for receiving information from display information, an update function simulating the behavior of the function information, a state variable related to the update function, and a result obtained by the update function. The program creation according to any one of claims 1, 3, and 5, further comprising output terminal information to be performed and an evaluation condition for selecting one or both of an input terminal and an output terminal. apparatus. 7. The function information includes input terminal information for receiving information from display information, an update function simulating the behavior of the function information, a state variable related to the update function, and a result obtained by the update function. 5. The program creating apparatus according to claim 2, further comprising: output terminal information to be input and evaluation conditions for selecting one or both of input terminal information to be input and output terminal information to be output. . 8. The input terminal information according to claim 6, wherein the input terminal information is one or both of event terminal information for receiving an input of an event and data input terminal information for receiving data necessary for executing an update function. Item 7. The program creation device according to Item 7. 9. The program creating apparatus according to claim 6, wherein at least one of the update function, input terminal information, and output terminal information is plural. 10. The function component according to claim 7, wherein the function component includes a component name corresponding to the function information, an input terminal corresponding to the input terminal information, and an output terminal corresponding to the output terminal information. Program creation device. 11. The display information includes type data information that defines a data type, the function information includes type data information that defines a data type, and the connection information creating unit includes: the type information of the function information; 11. The program creating apparatus according to claim 1, wherein when the type data of the information to be associated with the information is the same, the information is associated with the function information. 12. The display information includes type data information defining a data type, the function information includes type data information defining a data type, and includes type conversion storage means defining a type conversion rule. The information creating means, when the type data of the function information and the type data of the information associated with the function information are the same as the type conversion rules defined by the type conversion storage means, The program creating apparatus according to claim 1, wherein the program is associated with the program. 13. A connection mode storage unit defining a correspondence between a connection source and a connection destination, wherein the connection information creation unit creates connection information based on the correspondence stored in the connection mode storage unit. The program creation device according to claim 1, wherein 14. A display component display process for selecting predetermined display information from display information storage means storing display information and displaying a display component corresponding to the display information, and a correspondence relationship between the display information and the display information. A function component display process of selecting predetermined function information from function information common definition storage means for storing function information in which behavioral behavior is independently defined, and displaying a function component corresponding to the function information;
A unique information determination process for determining unique information for the functional component displayed in the functional component display process, and the display component displaying connection information defining an association between the selected display information and the function information; A connection information creation process created by visually defining a correspondence relationship with a functional component; and a program execution process of executing a program based on the display information, the function information, the unique information, and the connection information. A storage medium storing a program creation program. 15. The functional component display process displays a plurality of functional components, and the connection information creating process includes:
15. The program creating program according to claim 14, wherein the connection information defining the association of the selected function information is created by visually defining the correspondence between the plurality of displayed functional components. Storage medium. 16. The function information includes input terminal information for receiving information from display information, an update function simulating the behavior of the function information, a state variable relating to the update function, and a result obtained by the update function. Output terminal information
An evaluation condition for selecting one or both of input information to be input and output terminal information to be output, and a functional component, a component name corresponding to the function information, and an input terminal corresponding to the input terminal information, 16. A storage medium storing a program creation program according to claim 14, further comprising an output terminal corresponding to the output terminal information. 17. The display information includes type data information that defines a data type, the function information includes type data information that defines a data type, and the connection information creation process includes: 17. The storage medium storing the program creating program according to claim 14, wherein the information is associated with the function information when the type data of the information to be associated with the information is the same. .