JPH11296357A - Flow chart input device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily generate a correct flow chart without an error in PRO GRAM by arranging function parts selected by an input device to designated positions and editing flow chart data which indicates a flow chart structure. SOLUTION: A user generates a flow chart while viewing a display device 5 through the use of the input device 1. The device 1 is constituted of the parts such as a keyboard 1A and a mouse 1B, for displaying the intention of the user in the device. In this case, the device 1 selects the optional function parts stored in a function parts library 6 and designates that they are displayed at the prescribed positions on a display device 5. Then, an input part 2 analyzes the operation of the user, judges the propriety of the operation and gives a proper indication to a flow chart editing part 3. The part 3 executes a processing for editing flow chart data 7 in accordance with the intention of the user.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a CAS capable of automatically converting a document into a program for supporting software development, especially development of a mechatronics product.
The present invention relates to a flowchart input device that can be an E (computer aided software engineering) tool.

[0002]

2. Description of the Related Art A mechatronics product is composed of three elements: a logic circuit, a mechanism, and software. Therefore, a mechanism designer, a software designer, and a circuit designer must work together to develop a product. Usually, a designer who designs the mechanism has an image of how to control and operate the mechanism. However, mechanism designers generally do not have the technology to realize the image as software. On the other hand, even if software designers have the technology to realize software,
The control method and operation of the newly designed mechanism must be heard from the mechanism designer. Therefore, the mechanism designer needs to create a document for transmitting the control and operation image of the mechanism to the software designer.

[0003] A software designer develops software based on a document received from a mechanism designer. This requires that the document be free of inconsistencies and ambiguities, and be programmatically correct.
However, since the mechanism designer has no software design technology, it is not easy to create such a document. Therefore, there is a need for a tool that can easily draw a correct document even for a person who does not have software design technology.

In addition, software for mechatronics products is required to have high processing speed performance. Therefore, the program is an event-driven program that makes extensive use of interrupts. Therefore, it is desirable that the document created by the mechanism creator is also described in an event-driven manner according to the actual program.

[0005] That is, the following requirements are desired for a document creation tool applied to the development of mechatronics products. 1. To be able to create correct documents without knowledge of software. 2. Event-driven description is possible.

[0006] On the other hand, there are the following methods for creating documents conventionally. 1. Draw a flowchart by hand. 2. Use a drawing tool to draw a flowchart. 3. A CASE tool dedicated to software development called an HCP chart, a PAD, a HIPO, and an NS chart is used. 4. Use a CASE tool with a flowchart.

[0007]

However, the above-mentioned prior art has the following problems to be solved.
Drawing a flowchart manually requires a lot of man-hours. In addition, the degree of freedom of description is too large, and humans must rely on checking the validity of the flowchart. Furthermore,
Without software knowledge, it is difficult to create a correct flowchart without system support. If a drawing-based tool having a template for a flowchart is used, figure drawing becomes easy, and input man-hours are reduced. However, other problems are the same as manual work.

On the other hand, HCP chart, PAD, HIP
Since the CASE tools such as the O and NS charts do not use a flowchart, the above problem is solved. In addition, this method itself has an appropriately limited degree of freedom as compared with a flowchart, and it is easy to write a relatively correct document. Also,
It has been developed taking into account automatic conversion to programs.
However, there is a problem that these methods are not yet general and have not been standardized, so that they are not particularly familiar to non-software designers.

There are not many CASE tools that use flowcharts. In particular, those that can be automatically converted to programs are rare. Also, due to the problem of the flow chart itself, there is no program that can be converted into a goto-less structured program. That is, the conventional C
Many ASE tools are intended for software designers, and it is difficult to create correct documents without programming knowledge. Also, few of these tools are specialized for embedded devices, that is, for mechatronics products. Therefore, there are few things that can create event-driven documents.

[0010]

The present invention employs the following structure to solve the above problems. <Structure 1> When a group of graphic parts used in a flowchart to represent a procedure for completing a certain process is called a functional part, a functional part library storing a plurality of images of the functional part, and the functional part library described above. An input device for selecting an arbitrary functional part stored in the display device and displaying it at a predetermined position on the display device, and arranging the functional part selected by the input device at a specified position. And a flowchart editing unit for editing flowchart data indicating the structure of the flowchart.

<Structure 2> In the flowchart input device according to Structure 1, each functional part includes an empty part indicating a position where another functional part can be inserted and arranged in advance. Flow chart input device.

<Structure 3> In the flowchart input device described in Structure 2, if the insertion position of the functional part specified by the input device is not on an empty part of the functional part already displayed on the display device, the insertion is refused. A flow chart input device, comprising:

<Structure 4> In the flowchart input device according to Structure 3, an insertion judgment matrix for preliminarily limiting the functional parts that can be inserted into the empty part of each functional part is provided. A flowchart input device for determining whether to reject insertion of a functional part selected by an input device with reference to a matrix.

<Structure 5> In the flowchart input device described in Structure 1, when a new functional part is inserted into the flowchart already displayed on the display device, the flowchart editing unit may execute another function part. 2. A flowchart input device, wherein empty parts for displaying positions where a character can be inserted and arranged are arranged between functional parts in the flowchart.

<Structure 6> In the flowchart input device described in Structure 1, each functional part is characterized in that a connection point mark indicating a position to which an arrow indicating a program flow can be connected is included in advance. Flowchart input device.

<Structure 7> In the flowchart input device described in Structure 6, when the connection position of an arrow included in an arbitrary functional part displayed on the display device is designated by the input device, the connection position is already displayed on the display device. A flow chart input device comprising: a connection judging unit for rejecting the connection when the connection is not on the connection point mark of the set functional part.

<Structure 8> In the flowchart input device described in Structure 7, the connection determination unit does not satisfy a predetermined criterion based on a relationship between the designated arrow connection position and the functional part already displayed on the display device. A flowchart input device for rejecting a connection of an arrow specified by the input device.

<Structure 9> In the flowchart input device according to Structure 1, the flowchart editing unit expresses the flowchart data in a hierarchical structure, and includes data related to steps indicating a state and information related to arrows indicating a state transition. A flowchart input device, wherein a data hierarchy including attribute information of a step indicating the state is provided below the hierarchy.

<Structure 10> In the flowchart input device according to Structure 9, a data hierarchy including information on a step indicating a state and information on an arrow indicating a state transition in the flowchart data is selected, and the state transition is performed. A flow chart input device, comprising: a state transition diagram generation unit that extracts an event that causes an event from a lower data hierarchy to generate a state transition diagram.

<Structure 11> In the flowchart input device described in Structure 1, the program source code prepared for each functional part and the flowchart data are edited to automatically execute the source program for executing the flowchart. A flowchart input device comprising a program generation unit for generating.

<Structure 12> When a group of graphic parts used to represent a procedure for completing a certain process used in the flowchart is called a functional part, a functional part library in which a plurality of functional part images are stored in advance is used. Prepare and use the input device to select an arbitrary functional part stored in the functional parts library and specify it to be displayed at a predetermined position on the display device, and specify the selected functional part So that it is located at
A recording medium storing a computer program for inputting a flowchart, which operates to edit flowchart data indicating the structure of the flowchart.

<Structure 13> When a group of graphic parts used in the flowchart to represent a procedure for completing a certain process is called a functional part, a functional part library in which a plurality of functional part images are stored in advance is used. Prepare and use the input device to select an arbitrary functional part stored in the functional parts library and specify it to be displayed at a predetermined position on the display device, and specify the selected functional part So that it is located at
Edits the flowchart data indicating the structure of the flowchart, edits the program source code prepared for each functional part and the flowchart data, and automatically generates a source program for executing the flowchart. Recording medium storing a computer program for inputting a flowchart.

[0023]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below using specific examples. <Embodiment 1> FIG. 1 is a block diagram showing a flowchart input device of the present invention. This device, as shown in the figure,
It comprises an input device 1, an input unit 2, a flowchart editing unit 3, a flowchart display unit 4, a display device 5, a functional parts library 6, flowchart data 7, and the like.

The user uses the input device 1 to display the display device 5.
Create a flowchart while watching The input device 1
It is composed of components such as a keyboard 1A and a mouse 1B for indicating a user's intention to the apparatus. The input unit 2 is a unit that interprets a user operation, determines whether or not the operation is possible, and performs a process of issuing an appropriate instruction to the flowchart editing unit 3. The flowchart editing unit 3 is a part that performs a process of editing the flowchart data 7 according to the user's will.

The flowchart display unit 4 is a part for monitoring the update state of the flowchart data 7 and controlling to display the edited and updated flowchart data on the display device 5 each time. Further, the flowchart display unit 4 also performs a process of notifying the user of the availability of the operation.
The display device 5 includes a CRT display, a liquid crystal display panel, and the like, and is a device for notifying a user of an editing result. As will be described in detail later, the functional parts library 6 is a part for storing images and information that are parts of the flowchart when the user constructs the flowchart. The flowchart data 7 is composed of data edited by the flowchart editing unit 3 and having a structure as described later.

The above-described apparatus is realized by, for example, installing a computer program for realizing the above functional blocks in a workstation or a personal computer. The input unit 2, the flowchart editing unit 3, the flowchart display unit 4, and the like are configured by program modules for realizing the respective functions. The functional parts library 6 and the flowchart data 7 are realized by data of a predetermined configuration stored in a storage device provided in the computer.

FIG. 2 is a schematic diagram of a window displayed on the display device 5 shown in FIG. This screen is displayed when a flowchart input operation is performed, and includes a main window 11 and a parts palette 12. The main window 11 includes a flowchart display area 13 for creating and displaying a flowchart, and a main menu 14 for a user to instruct various operations.
And a tool button group 15 for directly instructing a specific operation by clicking with a mouse. On the parts palette 12, buttons for selecting various functional parts 6A of the functional parts library 6 shown in FIG. 1 are arranged. The details of the button for selecting the tool button group 15 and the functional part 6A are not shown here.

Conventionally, a template of a graphic part such as a rhombus, a square, and an arrow is prepared using a parts palette,
It was used as a part for constructing such a flowchart. However, the graphic parts themselves have no meaning as a program, and the degree of freedom in creating a flowchart is too large. Therefore, the present invention assists in creating a flowchart in units of the following functional parts. That is, the parts pallet 12 of FIG. 2 uses functional parts as one unit.

FIG. 3 is an explanatory diagram of a specific example of the functional parts. FIGS. 3A to 3F show various examples of functional parts used for creating a flowchart in the present invention. Each of the functional parts is composed of a group of graphic parts for expressing a procedure used in the program to complete a certain process. The graphic parts are diamonds, squares, arrows, and the like, as described above.

For example, FIG. 3A shows functional parts called "steps". This has a function of transiting to another state when an event occurs in a standby loop, and a determination diamond 17 is arranged in the standby loop 16. This corresponds to one state in the state transition diagram. Also,
It corresponds to the column of the state transition matrix table. This part differs from a normal loop in that a normal loop is a repetition of processing, whereas a functional part of a step shifts to a task wait state.

The event occurrence check is left to the operating system. When detecting the occurrence of an event, the operating system executes a process corresponding to the event. An event-driven program is a program described by a combination of these steps. Since a plurality of types of event waiting may be performed in the same state, an arbitrary number of diamonds 17 can be inserted into the waiting loop 16 later.

The function part called a branch shown in FIG. 3B has a function of making a certain condition judgment at the diamond 17 and branching to two types of routes. Arbitrary processing is inserted into the route after each branch as necessary. This also has a function of executing a certain complete process from the entrance to the exit. (C) is a functional part of the case sentence. Diamond 1
The condition is determined in the part 7 and the route branches to three or more routes according to the case. In each route, a process corresponding to each case is executed. A rectangle 18 indicates the processing.

FIG. 3D shows functional parts of the terminal.
This part 19 is used at the start and end of the program. (E) is a pre-judgment loop, and (f) is a post-judgment loop. In the pre-judgment loop, a certain judgment is made with a diamond 17. For example, when the condition is not satisfied, the processing loop including the rectangle 18 is repeated, and when the condition is satisfied, the process exits from the functional part. In the case of the post-judgment loop, the processing of the rectangle 18 is executed in advance, and the condition judgment is performed with the diamond 17. If the condition is not satisfied, the processing loop including the rectangle 18 is repeated. If the condition is satisfied, the process exits from this functional part.

As described above, each functional part has a correct meaning in terms of a program, completes a certain process, and becomes a unit for constructing a flowchart. Since the user assembles a flowchart by arranging such functional parts, a correct flowchart can be described programmatically. Further, the contents of processing by these functional parts can correspond to program source codes.

For example, (a) can be described by a group of messages that directly convey an event to the operating system. (B) is described by a so-called if-Then, Else sentence. (C) is described by a case statement. The terminal of (d) is an end statement. (E) and (f) are described by an if sentence or a for sentence.

FIG. 4 is a diagram illustrating a design example when a specific software designer designs a flowchart.
For example, it is assumed that a flowchart is created for a mechanism as shown in FIG. The mechanism shown in FIG. 1A drives a conveyor 22 using a transport motor 21,
It operates to transport the workpiece 23 from the right side to the left side in the figure. Here, the position of the workpiece 23 is detected by the first sensor 24 and the second sensor 25 while being transported on the conveyor 22. When the first sensor 24 detects the passage of the workpiece 23, a certain process is executed. Further, when the second sensor 25 detects the workpiece 23, another process is executed. In such a case, a flowchart as shown in FIG.

That is, in step S1 of FIG. 4B, when the motor starts, in step S2, the first sensor 24 enters an event waiting state in which the workpiece 23 passes. When the first sensor detects the workpiece 23, the process proceeds to the process 1 of S3. Then, the process proceeds to step S4, in which the second sensor shifts to an event waiting state of waiting for the workpiece 23 to pass. When the second sensor detects the passage of the workpiece 23, S5
And the process 2 is executed.

In an actual mechatronics product, various complicated controls are performed. For example, when the control as shown in FIG. 4B is performed, the monitoring of the first sensor and the monitoring of the second sensor are performed as shown in FIG. The functional parts of the steps described with reference to FIG. After that, although not illustrated in FIG. 3, functional parts indicating processing of only a rectangle are combined. The apparatus of the present invention is utilized when creating a flowchart in this way.

FIG. 5 is a diagram for explaining an example of creating a flowchart and converting the program. With reference to this figure, a specific flowchart input operation of the apparatus shown in FIG. 1 will be described. First, the user causes the display device 5 shown in FIG. 1 to display a screen as shown in FIG. Then, various functional parts are dragged from the parts palette 12 and dropped on the flowchart display area 13. By repeating this operation, for example, a flowchart as shown in FIG. 5A is drawn. In this flowchart, the functional parts of the step shown in FIG. 3A are connected next to the functional parts of the initial processing, and the functional parts of the event 2 are added to the event 1 included in the functional parts of the steps in advance. . After that, the functional parts of the event processing 1 and the functional parts of the event processing 2 are connected.

When such a functional part is dragged by operating the mouse 1B shown in FIG. 1, the input unit 2 detects the start of the drag of the functional part. The user specifies a predetermined position on the flowchart display area 13 and drops a functional part. The input unit 2 detects a drop of a functional part. Then, it is determined which position in the flowchart is the drop position. When the functional part is inserted at an appropriate position in the flowchart, this is notified to the flowchart editing unit 3.

The flowchart editing unit 3 extracts the data of the corresponding functional part from the functional part library 6 and writes the data corresponding to the corresponding part of the flowchart data 7. When detecting that the flowchart data 7 has been updated, the flowchart display unit 4 extracts and displays an image of the corresponding functional part on the display device 5. As described above, the input editing of the flowchart proceeds.

FIG. 5B is a diagram for a flowchart when a conventional drawing tool is used. The diamond 17 shown in this figure alone has no programmatic significance. As shown in (c) of the figure, a procedure for completing a certain process is expressed only when an arrow or the like indicating a branch route as a result of the condition determination is included. By supporting the creation of the flowchart in units of such functional parts, the creation of the flowchart becomes easy and accurate. Further, as shown in FIG. 5C, this functional part can be directly replaced with an if sentence, and a source program can be automatically created.

<Effects of Specific Example 1> As described above, a functional part library in which a program is created for each functional part and an image of the functional part is stored, an input device for specifying a position in the flowchart, and a flowchart data There is an effect that a correct flowchart free from programmatic errors can be easily created by a flowchart editing unit or the like that edits.

<Specific Example 2> When the flowchart is created as described above, the operation of connecting the functional parts to each other or inserting another functional part into each part of the functional part is performed. Here, an example will be described in which it is determined whether the insertion position of the functional part by the user is correct and the creation of the flowchart is supported.

FIG. 6 shows an apparatus block diagram for realizing this. In this figure, the same components are denoted by the same reference numerals based on the configuration of the device shown in FIG. In the device of this specific example 2, an insertion determination unit 31 is added to the device shown in FIG.

FIG. 7 is an explanatory diagram (1) of a display example for insertion determination. (A) of the figure combines the functional parts of the entrance terminal and the functional parts of the exit terminal. Actually, various functional parts are inserted during this period to complete the flowchart. A circle is displayed between the entrance terminal and the exit terminal shown in the figure. The 印 marks indicate positions where other functional parts can be inserted and arranged in advance, and are referred to as empty parts in the present invention.

Each functional part includes such an empty part in advance, and guides a point where the functional part dragged from the parts palette can be dropped. In addition, the cross mark superimposed and displayed with the empty part indicated by the circle mark represents a connection point mark to which the tip of an arrow in a flowchart described later can be connected.

FIG. 5B shows a new flowchart in which some functional parts are inserted in the flowchart of FIG. In the drawing, for example, a broken circle o is an empty part into which another event can be inserted during the step including the event 2. Empty parts are also placed at the entrance and exit of each functional part. The empty parts marked with ○ are arranged between the functional parts. These, ○
Blank parts such as marks, ◎ marks, and broken circles ○ are displayed in different colors or in different shapes to distinguish the types of functional parts that can be inserted as necessary.

While the user is dragging the part, the mouse cursor changes its shape between a position where it can be dropped and a position where it cannot be dropped. Thus, the user can be made aware of the drop position of the functional part. Also, if the user attempts to drop a functional part at a position where it cannot be dropped, the system ignores the operation. Such an operation itself has already been widely implemented by existing software and can be easily realized.

Next, the operation of the device of the present invention will be described. First, the user uses the input device 1 to drag a functional part in the parts palette 12 as shown in FIG. The input unit 2 detects the start of dragging of a functional part. The input unit 2 sequentially detects the positions of the parts being dragged, and passes the position information to the insertion determination unit 31. Insertion determination unit 31
Determines whether the part position being dragged is on an empty part. Then, the result is notified to the flowchart display unit 4. The flowchart display unit 4 changes the shape of the mouse cursor being dragged in accordance with the instruction from the input unit 2, and notifies the user whether the position is a droppable position.

When a functional part is dropped, the input unit 2 detects the drop and determines the position where the functional part was dropped.
Notify 1. The insertion determination unit 31 determines whether the dropped position is on an empty part, and ignores the operation if inappropriate. If the dropped position is on an empty part, the insertion determination unit 31 notifies the flowchart editing unit 3 that a part has been inserted at the corresponding position on the flowchart.

The flowchart editing unit 3 extracts the data of the functional part from the functional part library 6 and inserts the part data into a corresponding part of the flowchart data 7. The flowchart editing unit 3 inserts a newly required empty part into the flowchart data 7 when a new functional part is inserted. When detecting that the flowchart data 7 has been updated, the flowchart display unit 4 outputs the result to the display device 5 and updates and displays the flowchart.

Conventionally, for example, when a flowchart is created using a drawing-based tool, graphic parts can be freely arranged, and it is up to the user to give the correct context to those parts. Was. Therefore, there are many cases where inappropriate parts are placed depending on the level of the user.

In this specific example, an insertable portion is designated so that a part is always inserted only at an appropriate position, and this is determined by the insertion determination section 31. Therefore, it is possible to prevent an error, for example, that the inserted functional part floats without being attached to any part, and to always input a correct flowchart programmatically. Further, it is possible to recognize at which point in the program the inserted functional part was inserted, based on the point where the functional part was inserted. This operation will be specifically described.

FIG. 8 is a diagram (part 2) for explaining an example of display for insertion determination. As shown in FIG. 3A, this flowchart is configured by connecting a functional part of step 1 and a functional part of step 2. At this time, in general, the processing inserted in the part (1) in the figure is the event processing of Step 1 or Step 2
It is not possible to determine whether the process is the initial process before the execution of.

However, as already described, empty parts indicated by ◎ are arranged at the entrance and exit of each functional part, for example. Then, as shown in (b), when two sets of functional parts of Step 1 and Step 2 are connected, a new empty part marked with a circle is added to the connection point. ◎ in (2)
The blank part of the mark is a process belonging to Step 1. (3)
The blank part marked with ◎ in the part is a process belonging to step 2. The blank part marked with a circle is a part into which a new functional part can be inserted. By utilizing this, it is possible to distinguish whether the functional part newly inserted in this portion is a process belonging to Step 1 or Step 2 or an independent process.

Therefore, when each function part is replaced with the source code in the manner already described, when generating a source program, it is determined which function part source code includes the source code of the newly inserted function part. It becomes possible to do. Of course, if the surrounding empty parts are continuously displayed on the display device 5, the flow chart creator can
The distinction can be made.

<Effect of Specific Example 2> As described above, the place where the functional part can be inserted in the flowchart is limited, and the insertion determination unit 31 controls to determine this. Mistakes such as insertion of functional parts can be prevented. Also, the flow of the program is clarified, and automatic conversion to a source program in units of functional parts becomes easy.

<Example 3> As described with reference to Example 2, if a position where another functional part can be inserted into each functional part is set in advance as an empty part, the flow chart can be easily created. By limiting the functional parts that can be inserted, it is possible to input a flowchart without errors. Therefore, data for determining a functional part that can be inserted is set.

FIG. 9 shows a device block diagram of the third embodiment. This device is obtained by adding an insertion determination matrix to the device of the second embodiment. Other parts have the same configuration as that of the device of the second embodiment, and are represented by the same reference numerals.

FIG. 10A is a diagram for explaining the contents of the insertion judgment matrix. (B) shows an operation explanatory diagram of the insertion determination unit that operates with reference to the insertion determination matrix. As shown in FIG. 10A, the empty parts shown on the left side are distinguished from each other as ○, ◎, broken line 及 び, and thick line ○. If these empty parts are present in the flowchart, the various functional parts shown at the top of the figure, such as step, branch, event processing, terminal, pre-judgment, post-judgment, case, connector, etc. Of those, only those with a circle can be inserted there.

In the example shown in (a) of FIG.
The mark prohibits insertion other than the event. ○ of this broken line
The mark was displayed in the functional part of the step as shown in FIG. The step indicates a state of waiting for an event, and is different from general loop processing. Therefore,
No other events can be inserted during the step. The user can identify the position where the functional part being dragged can be inserted, based on the shape and type of the empty part. Specifically, the device operates as follows.

First, when a functional part is dropped,
The input unit 2 shown in FIG. 9 detects this, and inserts the type of the dropped part and the dropped position information into the insertion determination unit 31.
Notify. The insertion determination unit 31 determines whether the type of the mark indicating the dropped part and the empty part is a combination that can be inserted. This is performed with reference to the insertion determination matrix 32 as shown in FIG.

If the insertion determination matrix 32 does not indicate that the combination is valid, the drop operation is ignored. If the insertion determination unit 31 determines that the combination is a valid combination, the insertion determination unit 31 notifies the flowchart editing unit 3 that the functional part has been inserted at the corresponding position on the flowchart. The flowchart editing unit 3 extracts the data of the corresponding functional part from the functional part library 6 and inserts the data into the corresponding position of the flowchart data 7. Then, the flowchart editing unit 3 inserts, into the flowchart data 7, an empty part that is newly required due to the insertion of the part. Thereafter, the flowchart display unit 4 detects the update of the flowchart data 7 and displays a new flowchart on the display device 5.

For example, in FIG. 10B, it is assumed that the functional parts of the steps enclosed by the broken line have already been drawn, and that the parts of event 1 and event 2 have been inserted.
If a new processing part is inserted into this, it becomes useless as an event waiting step. This is because the insertion of the processing in the loop makes it impossible to shift the task to the wait state, which is the same as ordinary repetition processing.

Furthermore, since such a part exists at a place where a step should be, conversion into a state transition diagram becomes impossible. In addition, such improper insertion of parts degrades the validity of event-driven orientation. Therefore, by making it impossible to create a flowchart as shown in FIG.
The object of the present invention is achieved.

<Effect of Specific Example 3> As described above, by providing the insertion determination matrix, it is possible to limit the types of functional parts that can be inserted into empty parts. In this manner, the creation of an erroneous flowchart due to the insertion of an inappropriate part can be prevented.

<Example 4> In Example 3, the position where the functional part should be inserted was determined. In the program flowchart input work, in addition to inserting functional parts,
There is an arrow connection to the state transition destination after event processing. If there is an error in the connection of the arrows, a logical contradiction occurs, and the validity of the program as event-driven is impaired.

FIG. 11 is a block diagram of the apparatus of the fourth embodiment. This device is provided with a connection determination unit 33 for determining the validity of the arrow connection. Other functional blocks are the same as those described with reference to the third embodiment, and are denoted by the same reference numerals.

FIG. 12 is an example of a flowchart drawn according to the present invention. The connection determination operation will be described with reference to FIG. Then processing shown on the right side of this figure;
The arrow following (4) or (5) is provided in a portion following the Else processing. You can move the arrow to any location by clicking and dragging the black square at the neck of the arrow with your cursor. Then, when the drop is made at the designated place, the tip of the arrow is connected in the flowchart. Here, a connection point mark of X is shown at a place where the tip of the arrow can be connected.

That is, the tips of these arrows cannot be connected to places other than (1), (2) and (3) in the figure. That is, in order to maintain the event-driven character of the program, the arrow can be connected only to an appropriate place as a state transition destination. The arrow shown in (6) of the figure is included in the functional parts of the steps. Moving the tip of this arrow prevents the functional part itself from operating properly.
Therefore, a black square is not prepared and its movement is not recognized. Similarly, the connection cannot be changed in the arrows of the pre-judgment loop shown in FIGS. 3E and 3F and the post-judgment loop shown in FIG.

For example, if the ends of the arrows are connected for purposes other than state transition, event-driven processing becomes impossible. For this reason, the above-mentioned restrictions are imposed. If an attempt is made to make a connection that is not permitted during the input of the flowchart, the movement of the arrow is not recognized and the original position is returned.

In the example shown in FIG. 12, the functional parts of the steps starting from (1) undergo state transition according to two types of events. When the state transition is performed by the event 1 arranged on the upper side, the process proceeds to the processing by the functional part of the conditional branch shown on the right side of the drawing. If the condition is satisfied, a Then process is performed, and if the condition is not satisfied, an Else process is performed.

On the other hand, when a state transition is made in the event 2 below the step starting with (1), the event processing immediately above (2) is executed, and the process proceeds to the step starting from (2). Thus, the state transits to a state of waiting for the next event 3. For this reason, the arrows shown in (4) and (5) cannot move to places other than (1), (2) or (3), which are boundaries of state transition. The connection determination unit 33 operates according to such criteria.

FIG. 13 is an explanatory diagram (part 2) of the connection judging operation after the arrow shown in (5) of FIG. 12 is moved to the position of (3). The operation of the device shown in FIG. 11 will be described with reference to FIG. First, the user clicks the tip of the arrow (5) displayed on the flowchart display area 13 using the input device 1. Then, drag as it is. When the input unit 2 detects that the dragging of the arrow has been started on the input device 1, the input unit 2 connects the fact to the connection determination unit 33. The connection determination unit 33 determines whether the dragged arrow is draggable, and ignores the operation if the dragged arrow is prohibited as in (6).

The input unit 2 sequentially detects the position of the tip of the arrow being dragged from the input device 1 and notifies the connection determination unit 33 of the position information. The connection determination unit 33 determines whether or not the position information of the received arrow is on a connectable X mark. Then, the result is notified to the flowchart display unit 4. The flowchart display unit 4 changes the shape of the mouse cursor being dragged according to the instruction of the input unit 2,
The user is notified of whether or not connection to the location is possible.

When the tip of the arrow is dropped, the input unit 2
Detects this, and determines the dropped position in the connection determination unit 33.
Notify. The connection determination unit 33 determines whether the dropped position is on the appropriate X mark, and if inappropriate, instructs the flowchart editing unit 3 to reconnect the arrow to the default position, that is, the position before the start of dragging. Notice. When determining that the dropped position is on the appropriate X mark, the connection determination unit 33 instructs the flowchart editing unit 3 to connect the arrow to the designated position.

The flowchart editing section 3 changes the connection destination of the arrow in the flowchart data 7 so as to be the designated position. Thereafter, the flowchart display unit 4 detects that the flowchart data 7 has been updated, and instructs the display device 5 to redisplay the flowchart.

FIG. 14 shows an example of an incorrect flowchart. In the flowchart shown in this figure, the arrow indicating the branch destination as a result of the conditional branch jumps into the pre-determination loop. In such a flowchart, a goto statement must be used. It is generally said that it is desirable to avoid using a goto statement because it impairs the readability and maintainability of the program.

That is, such a flow is inappropriate because it contradicts the idea of event-driven structured programming centering on state transition. With traditional tools, you are free to draw such flowcharts,
It was up to the user to prohibit this. According to the present invention, the connection location of the arrow is limited in advance, and the connection determination unit 33 determines the location. Therefore, such inappropriate connection of the arrow can be prohibited.

<Effect of Specific Example 4> As described above, in the present invention, connection of an inappropriate arrow in a flowchart can be prohibited. For example, regardless of the level of the user's programming ability, a structured goto is always available. The user can be assisted to create a flow chart of the reply. In addition, logically erroneous connections can be prevented, and a bug-free program can be automatically generated thereafter.

Therefore, even if it does not contradict the restriction by the structured programming as described above, the connection of the arrow is prohibited in all cases where an inappropriate operation occurs when the connection of the arrow is performed. Can be widely used for processing.

<Embodiment 5> In the apparatus of the present invention as described above, the flowchart data can be expressed by a combination of functional parts. Therefore, for example, if the names of the functional parts and the mutual connection relationship are clarified, the flowchart data can be generated. In addition, if there is such a flowchart, it is possible to automatically generate a source program by replacing each functional part with the corresponding source code and converting the functional part into an arrow indicating the destination of state transition.

However, when displaying the functional parts on the display device, it is necessary to appropriately link the images of the graphic parts constituting the functional parts to cope with the deformation. In such a case, efficient and accurate management of each graphic part is required. Therefore, in this specific example, flowchart data having a hierarchical structure as described below is used.

FIG. 15 shows a device block diagram of the embodiment 5. The block diagram shown here corresponds to the device of the fourth embodiment.
The difference is that the hierarchical structure flowchart data 34 is adopted. Other parts are denoted by the same reference numerals as in Example 4.

The structure of the hierarchical structure flowchart data will be described with reference to FIG. 16, FIG. 17, and FIG. FIG.
Shows a flowchart of a program having the states of step 1, step 2, and step S3. This flowchart shows an operation for directly performing a state transition from step 1 to step 3 and a program for performing a state transition from step 1 to step 3 via step 2. Here, it is assumed that a new functional part is inserted into the part (1) immediately before the event processing executed in the process of transitioning from step 1 to step 2.

FIG. 17 shows that a functional part for performing branch condition processing is added to the part (1) in FIG.
In the flowchart shown in FIG. 16, when the event 1-1 occurs from the state of step 1, the corresponding event processing is performed, and the process proceeds to step 2. Event 1-2
Occurs, the corresponding event processing is executed, and the routine proceeds to step 3. In the state of step 2, event processing corresponding to the case where the event 2-1 has occurred is executed, and the process proceeds to step 3. Step 3 is event 3-1
When this occurs, a process for ending this program is performed. In FIG. 17, when the event 1-1 occurs, the branch condition is determined by a new functional part before executing the corresponding event processing. When such a functional part is added or subsequently deleted during a flowchart input operation, it is desirable that flowchart data having a structure suitable for display control exist.

FIG. 18 shows an example in which the flowchart of FIG. 16 is represented by flowchart data having a hierarchical structure.
First, this flowchart has a basic structure in which a child part is sandwiched between a start terminal and a stop terminal. This is No. 1 is displayed in the data hierarchy. N
o. As shown in FIG. 16, the child part shown in the first data hierarchy is composed of the function steps shown in step 1, the function steps shown in step 2, and the function steps shown in step 3. These steps are illustrated in dashed boxes.

An arrow indicates a state transition destination for each step. In the figure, what is displayed as a red circle is
Empty parts placed at the entrance and exit of each step. In an event-driven program, basically all processes can be represented by this alone. The relationship between the upper hierarchy and the lower hierarchy is that the latter indicates the former attribute data. Arrows indicate pointer data. For example, the attribute data of the start terminal and the stop terminal is “No. It is displayed in the second layer. In other words, each of them has a content that is constituted by an ellipse and a line that is a part of the flowchart.

Next, No. The third layer will be described. Here, only an example of the attribute data in step 1 is shown, and the other components are the same, so that illustration is omitted. As shown in FIG. 16, the functional steps of Step 1 include a straight line connected to the start terminal, an empty part indicated by a dashed circle at the beginning, an event 1-1, an empty part, an event 1-2, There are graphic parts such as sky parts. Further, there is a loop line expressing the event waiting state.

Therefore, No. 1 shown in FIG. In the layer 3, there are attributes such as a head line, child parts corresponding to empty parts at the entrance, a line going to event 1-1, child parts including event 1 and event 2, and a loop line. Data is displayed. ◎ Child parts showing empty parts are
No. At the fourth level, the attribute is displayed as a green circle. In addition, No. The three blue circles in the hierarchy of No. 4 and the event 1-1 and the event 1-2 sandwiched therebetween are No. 4. The attribute data indicates the child part of No.3.

Further, the event 1-1 and the event 1-2
Are composed of diamond-shaped figures, branch lines, and child parts connected to the ends of the branch lines. This is N
o. 5 is shown. The event processing of (1) shown in FIG. 16 has a configuration in which functional parts for processing are sandwiched between empty parts indicated by green circles. This is N
o. 6 are shown. Also, since the functional part of the processing is composed of a square figure, this is designated as No. 7 is shown.

As described above, this flowchart data expresses information of steps indicating states and information of arrows indicating state transitions between these steps in a basic data hierarchy, and for each step indicating each state. , And the attribute data of the step are sequentially expressed in a hierarchical structure. In such a configuration, when the functional part of (2) as shown in FIG. 17 is inserted into the portion of (1) shown in FIG.
As shown in (2), the flowchart data is rewritten.

That is, in FIG. 19, the No. shown in FIG.
No. 6 is newly added to the hierarchy of No. 6. "Branches" and "empty parts represented by green circles" belonging to the child parts shown in the fifth layer are added. Then, in order to represent the attribute of “branch”, No.
The seventh layer indicates that the shape is a rhombus and is composed of a line, two child parts, and a branch line. The two child parts are expressed as empty parts indicated by green circles in which another new functional part can be inserted.

As described above, when a new functional part is added, the data of the functional part having the hierarchical structure may be inserted at a time into a corresponding part of the flowchart having the hierarchical structure. Conversely, when removing such a functional part, the functional part elements having a hierarchical structure indicated by the broken line in FIG. 19 may be collectively deleted. In other words, all the parts required for the functional part "branch" have a hierarchical structure, and the flowchart also has a hierarchical structure, so when adding or deleting functional parts, some graphic parts are left behind. No inconsistency occurs.

<Effect of Specific Example 5> As described above,
If flowchart data is expressed in a hierarchical structure, when creating and processing flowcharts in units of functional parts,
When performing trial and error by adding or deleting functional parts, it is easy to handle flowchart data,
The occurrence of errors can be prevented. Therefore, there is no problem of causing contradiction in the flowchart or leaving meaningless parts. Moreover, when a part is deleted, it is easy to automatically connect the front and rear of the corresponding part in the flowchart.

<Embodiment 6> No. of the flowchart data shown in FIG. Focus on the second layer. In this hierarchy,
As shown in the figure, only information of steps indicating states and information of arrows indicating state transitions between these steps appear. Using such data, a basic structural analysis of a program can be performed.

FIG. 20 shows functional blocks for this structural analysis. By adding such a functional block to the apparatus shown in FIG. 1, for example, a state transition diagram as shown in FIG. 21 can be generated and displayed from the flowchart data. That is, the apparatus shown in FIG. 20 includes the hierarchical structure flowchart data 34, the conversion unit 36, the state transition diagram data 37, the data display unit 38, and the display device 5. Further, in this figure, referring to the hierarchical structure flowchart data 34 and the functional parts library 6,
A program generator for generating a source program corresponding to the flowchart is illustrated.

The program generation unit 40 first generates the contents of the event and the attribute data for each state with reference to the flowchart data of the hierarchical structure or the flowchart data of another structure. Next, referring to the functional part library 6, the source code as described above of the functional parts used in the flowchart is acquired. Then, the source code is copied to a program code description portion attached to the event or state attribute data. Thus, the program can be automatically generated.
Other specific program generation procedures are the conventional CA
This is the same as the processing executed by the SE tool.

The hierarchical structure flowchart data 34 is data having contents as shown in FIG. The conversion unit 36
For example, the No. Referring to the second data hierarchy, this data is converted and the state transition diagram data 37 is generated. The data display unit 38 displays the state transition diagram data 3
7 is a portion for displaying 7 on the display device 5. When a software engineer analyzes the operation of the entire program, a state transition diagram is generally created. If this can be automatically created and displayed on the display device, it is helpful for the user to check the result after creating the flowchart or for other software engineers to understand the contents.

FIG. 21 is an explanatory diagram of an example of a state transition diagram.
The operation of the device shown in FIG. 20 will be described with reference to FIG. First, the conversion unit 36 analyzes the flowchart data 34, and converts the No. shown in FIG. A step indicating a state is extracted from the second data hierarchy. The conversion unit 3
6 analyzes the flowchart data shown in FIG. 18 and determines the position, symbol figure, and the like when displaying the state of each step on the display device. 21. The circles in FIG. 21 in which "step 1", "step 2", and "step 3" are written are the symbol figures.

Next, the converter 36 converts the No. shown in FIG.
Data corresponding to an arrow is extracted from the second data hierarchy, and each state is displayed. For example, circles shown in FIG. 21 are connected by an image of an arrow. Further, in the case of No.
Events of three or less data hierarchies are extracted, and information indicating their meaning is added to arrows indicating state transitions. At the same time, No. 1 shown in FIG. With reference to the first layer, information corresponding to the start and stop terminals is added. In this way, an image as shown in FIG. 21 is generated, and the graphic image is displayed on the display device 5 under the control of the data display unit 38.

<Effect of Specific Example 6> As described above,
Automatically generate a state transition diagram by extracting the necessary state from the data hierarchy representing the state transition, extracting the contents of the state transition from the corresponding event, by configuring the flowchart data as described above. Can be. This makes it possible to immediately verify whether the flowchart is an event-driven program belonging to a program implemented in the mechatronics product, and is effectively used for creating a flowchart and analyzing the flowchart.

Each of the inventions shown in the specific examples 1 to 6 can be executed by a program installed in a personal computer, a workstation, or the like, as described above. These programs are stored on floppy disks and CDs.
-It can be stored in a ROM or other program recording medium. Further, it is possible to directly install and execute the program on a computer using a communication line or the like.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a flowchart input device of the present invention.

FIG. 2 is a schematic diagram of a window displayed on a display device.

FIG. 3 is a diagram illustrating a specific example of a functional part.

FIG. 4 is an explanatory diagram of a software design example.

FIG. 5 is an explanatory diagram of an example of flow chart creation and conversion to a program.

FIG. 6 is a device block diagram of a specific example 2.

FIG. 7 is an explanatory diagram (part 1) of a display example for insertion determination.

FIG. 8 is an explanatory diagram (part 2) of a display example for insertion determination.

FIG. 9 is a device block diagram of a specific example 3.

FIG. 10 is an explanatory diagram of an insertion determination matrix.

FIG. 11 is a device block diagram of a specific example 4.

FIG. 12 is an explanatory diagram (part 1) of a connection determination operation.

FIG. 13 is an explanatory diagram (part 2) of the connection determination operation.

FIG. 14 is an explanatory diagram of an example of an incorrect flowchart.

FIG. 15 is a device block diagram of a specific example 5.

FIG. 16 is an explanatory diagram of a flowchart example before a change.

FIG. 17 is an explanatory diagram of a flowchart example after a change.

FIG. 18 is an explanatory diagram of a flowchart data example (before change).

FIG. 19 is an explanatory diagram of a flowchart data example (after change).

FIG. 20 is a block diagram of an apparatus of a specific example 6.

FIG. 21 is an explanatory diagram of an example of a state transition diagram.

[Explanation of symbols]

 Reference Signs List 1 input device 2 input unit 3 flowchart editing unit 4 flowchart display unit 5 display device 6 functional parts library 6A functional parts 7 flowchart data

Claims (13)

[Claims] When a group of graphic parts used in a flowchart to represent a procedure for completing a certain process is called a functional part, a functional part library storing a plurality of images of the functional part; An input device for selecting an arbitrary functional part stored in the library and displaying it at a predetermined position on the display device, and arranging the functional part selected by the input device at the specified position A flowchart input device comprising: a flowchart editing unit configured to edit flowchart data indicating a structure of a flowchart. 2. The flowchart input device according to claim 1, wherein each functional part includes an empty part indicating a position where another functional part can be inserted and arranged in advance. Flow chart input device. 3. The flowchart input device according to claim 2, wherein the insertion of the functional part specified by the input device is not on an empty part of the functional part already displayed on the display device, and the insertion is rejected. A flowchart input device comprising an insertion determining unit. 4. The flowchart input device according to claim 3, further comprising an insertion determination matrix for preliminarily defining a functional part that can be inserted into a vacant part of each functional part, wherein the insertion determining unit includes the insertion determination matrix. A flowchart input device for determining whether to reject insertion of a functional part selected by the input device with reference to FIG. 5. The flowchart input device according to claim 1, wherein the flowchart editing unit, when a new functional part is inserted into the flowchart already displayed on the display device, next executes another functional part. A flowchart input device, wherein empty parts for displaying positions where insertion and placement are possible are arranged between functional parts in the flowchart. 6. The flowchart input device according to claim 1, wherein each functional part includes a connection point mark indicating a position to which an arrow indicating a program flow can be connected in advance. Flow chart input device. 7. The flowchart input device according to claim 6, wherein a connection position of an arrow included in an arbitrary functional part displayed on the display device is already displayed on the display device when specified by the input device. A flow chart input device, comprising: a connection judging unit for rejecting the connection when the connection is not on the connection point mark of the functional part. 8. The flowchart input device according to claim 7, wherein the connection determination unit determines that the connection position of the designated arrow does not satisfy a predetermined criterion based on a relationship with the functional part already displayed on the display device. Is a flowchart for rejecting the connection of the arrow specified by the input device. 9. The flowchart input device according to claim 1, wherein the flowchart editing unit expresses the flowchart data in a hierarchical structure, and includes data relating to a step indicating a state and information relating to an arrow indicating a state transition. A data hierarchy including attribute information of the step indicating the state is provided below the flowchart. 10. The flowchart input device according to claim 9, wherein a data hierarchy including information on a step indicating a state and information on an arrow indicating a state transition in the flowchart data is selected, and the state of the state transition is selected. A flow chart input device, comprising: a state transition diagram generation unit that generates a state transition diagram by extracting a causal event from a lower data hierarchy. 11. The flowchart input device according to claim 1, wherein the program source code prepared for each functional part and the flowchart data are edited to automatically generate a source program for executing the flowchart. A flowchart input device, comprising: 12. When a group of graphic parts used in a flowchart to represent a procedure for completing a certain process is called a functional part, a functional part library storing a plurality of images of the functional part is prepared in advance. When the input device selects an arbitrary functional part stored in the functional part library and designates it to be displayed at a predetermined position on the display device, the selected functional part is designated. A recording medium storing a computer program for inputting a flowchart, which operates so as to be arranged at a position and edits flowchart data indicating the structure of the flowchart. 13. When a group of graphic parts used in a flowchart to represent a procedure for completing a certain process is called a functional part, a functional part library storing a plurality of images of the functional part is prepared in advance. When the input device selects an arbitrary functional part stored in the functional part library and designates it to be displayed at a predetermined position on the display device, the selected functional part is designated. The source for executing the flowchart by editing the flowchart data showing the structure of the flowchart and arranging the program source code prepared corresponding to each functional part and the flowchart data so as to be arranged at the position. A computer program for inputting flowcharts that operates to automatically generate programs Recording medium recording the ram.