JPH06103051A - Programming device - Google Patents

Abstract

PURPOSE:To provide the programming device which can shorten program developing time and can improve quality. CONSTITUTION:This device is provided with a first translator 1 for translating a parts definition description A into event parts 11 and action parts 12 in a target language, second translator 2 for preparing a state transition data table 13 and a parallel table 213c from an operation specification description B expressed in a state transition diagram introducing the conception of parallelization, an a third translator 3 for preparing an event table 14 and an action table 15 from an event/action definition description C, and a target program 100 is prepared by synthesizing these event parts 11, action parts 12, state transition data table 13, parallel table 213c, event table 14 and action table 15 with a general-purpose state transition engine 16, a signal input part 17, an event extraction part 18 and a signal output part 19.

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 used for creating programs such as control system microcomputer programs.

[0002]

2. Description of the Related Art In recent years, general household electric appliances such as microwave ovens and refrigerators are increasingly equipped with microcomputers, and their functions are rapidly becoming complicated and sophisticated in response to diversifying user needs.

Under these circumstances, a method of creating a program by component synthesis is being widely adopted in various software development fields. This is a method of preparing a typical processing pattern and program parts with high versatility in advance, and embedding the necessary program parts in the processing pattern selected from them to create one program. The aim is to improve production efficiency by structuring and reusing parts. However, under the present circumstances, there are many problems with this method, such as a decrease in production efficiency and quality as the required function becomes complicated, and a loss of practicality due to a large size.

In the initial stage of software development, it is a basic work routine to first define functional specifications and create a design document such as a flow chart based on the functional specifications. However, the problem here is that the notation of design documents is not stylized. For this reason, it is often the case that it is difficult to closely study the functions at the design document level with others. In addition, it is the current situation that ensuring the consistency between the design document and the source code is left only to the designer, and that it takes a considerable amount of time and effort to make corrections.

[0005]

As described above, in the conventional method for creating a program by synthesizing parts, as the required functions become more complicated and sophisticated, the production efficiency and quality deteriorate, and the function examination at the design document level occurs. Also, ensuring the consistency between the design document and the source code was likely to be insufficient.

The present invention is intended to solve such a problem, and an object of the present invention is to provide a program creating apparatus capable of shortening the program development period and improving the quality.

[0007]

In order to achieve the above object, the program creating apparatus of the present invention includes a first conversion means for converting a part definition description into an event part and an action part of a target language, and an event and an action. And the behavior specification description expressed by the state transition diagram that introduces the concept of parallelization is converted into a format that can be interpreted by the target language to create a state transition data table, and exists between the state transition diagrams. The second conversion means for creating a parallel table in which parallel relationship information is registered, and the event / action definition description defining the event component and action component corresponding to the event and action on the behavior specification description are targeted. Third conversion means for creating an event / action table by converting into a format that can interpret the language The event component and the action component obtained by the conversion means, the state transition data table, the parallel table, the event / action table, the state transition data table, the parallel table, and the event / action table. The target program is generated by synthesizing with the state transition engine unit that drives the event component and the action component while grasping the parallel relationship existing between the state transition diagrams with reference to FIG.

[0008]

In the present invention, the event parts, the action parts,
Of the programs configured to incorporate the state transition data table, parallel table, event / action table, and state transition engine part, the event parts, action parts, state transition data table, parallel table, and event / action table are standardized. The conversion program is automatically created from the created component definition description, operation specification description, and event / action definition description, and a target program is created by combining these with a general-purpose state transition engine unit. Therefore, by standardizing the component definition description, the operation specification description, and the event / action definition description corresponding to the design document, it is possible to easily and closely study the specifications with others, and to efficiently and efficiently We can create quality products. Also, by introducing the concept of parallelization to the state transition diagram, it is possible to improve the comprehension of the state transition diagram and reduce the size thereof.

[0009]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the structure of a program creating apparatus according to an embodiment of the present invention and the program created by this apparatus.

In the figure, reference numeral 1 designates a part definition description A as an event part 11 and an action part 12 in the target language.
It is a first translator as a first converting means for converting to. Reference numeral 2 is a second translator as a second conversion means for converting the operation specification description B represented by the state transition diagram into a format that can be interpreted by the target language and creating the state transition data table 13. 3 is an event / action definition description C that defines event parts and action parts corresponding to the events and actions on the behavior specification description B is converted into a format that can be interpreted in the target language to create an event table 14 and an action table 15. It is a third translator as a third converting means.

The event component 11, the action component 12, the state transition data table 13, the event table 14, and the action table 15 created by the first to third translators 1, 2, and 3 are general-purpose state transition engine units. The state transition engine 16, the signal input unit 17, the event extraction unit 18, and the signal output unit 1 that configure the
9 and a linker (not shown) are used to synthesize the target program 100.

Here, the state transition engine 16 manages the current state on the state transition data table 13 and the current state management section 16a which drives the event parts and action parts based on the state transition data table 13. Part 1
6b and. Further, the signal input unit 17 inputs the signal from the controlled object G, and the event extraction unit 18 compares the signal input from the signal input unit 17 with the event components sequentially driven by the state transition engine 16 to find the corresponding event. The component for extracting a component, and the signal output unit 19 is a component for outputting a signal to the control target G based on the action component driven by the state transition engine 16.

FIG. 2 shows an example of the part definition description A.
As shown in the figure, the part definition description A is a specification part A1 in which external specifications of event parts and action parts are described.
And a main body A2 which is a fragment of a program code written in the target language. That is,
The first translator 1 cuts out only the main body portion A1 from the component definition description A and generates the event component 11 and the action component 12 in the target program 100.

FIG. 3 shows an example of the operation specification description B.
As shown in the figure, this behavior specification description B describes the design behavior specification of the target program 100 in a state transition diagram including events and actions. Here, an event is an event that triggers the controlled object G to start an operation, and an action is an operation of the controlled object G caused by the occurrence of an event. The events and actions used in the behavior specification description B are limited to those defined in the event / action definition description C.

FIG. 4 shows an example of the state transition data table 13 created by the second translator 2 from this operation specification description B. Here, ST0 and ST1 are states, E0, E1 and E2 are events, and further A0, A1 and
A2 indicates an action. In addition, each state (ST)
The number is automatically added when converting.

FIG. 5 is a diagram showing an example of the event / action definition description C. The event / action definition description C describes which event component and what action argument should be given in order to realize the event and action on the behavior specification description B.

FIG. 6 is a diagram showing an example of the event table 16 and the action table 17 created by the third translator 3 from the event / action definition description C. The event table 16 and the action table 17 indicate which event component and what action argument should be given to realize the event and action on the state transition data table 13, respectively.

Next, the operation of the state transition engine 16 in the created program 100 will be described with reference to the flowchart of FIG.

The state transition engine 16 always holds the present state in the present state management section 16a. Now, in ST1 in which the current state is "LED lighting", it is assumed that the signal indicating that the "button has been pressed" has been input from the control target G to the signal input unit 17.

The state transition engine 16 first refers to the state transition data table 13 and extracts one event from the state ST1 held by the current state management unit 16a (step 701). Next, the state transition engine 16
By referring to the event table 14, the event component and its argument corresponding to the retrieved event are checked (step 7
02), the event component is activated (step 70).
3). Here, it is assumed that the event component of E0 is activated. This part is a part for determining whether or not the switch is turned off. Here, the event extraction unit 18
The signal input from the signal input unit 17 is compared with the activated event component, and the state transition engine 16 is notified whether or not the event is actually occurring (step 704). In this case, the failure of the event is notified to the state transition engine 16. Then, the state transition engine 16
The state transition data table 13 is again referred to, the next event E2 from the state ST1 held in the current state management unit 16a is extracted (step 701), and the event table 14 is referred to by the event corresponding to this event E2. The component and its argument are checked (step 702), and the event component is activated (step 703). This event component is a component that determines whether or not a button has been pressed. Therefore, in this case, the state transition engine 16 receives notification from the event extraction unit 18 that the event has occurred. The state transition engine 16 that has learned the occurrence of the event refers to the state transition data table 13 again and takes out the action corresponding to the event (step 705). Then, referring to the action table, the action component 1 corresponding to the extracted action
5 and its arguments (step 706), this action component is activated (step 707), and the signal output unit 19
A signal is output to the controlled object G through. Then, after this, the current state is updated (step 708).

Thus, according to the program creating apparatus of this embodiment, the part definition description A, the operation specification description B, and the event / action definition description C corresponding to the design document are formalized and the specifications are examined with others. It can be performed easily and densely, and the parts definition description A, the operation specification description B, and the event / action definition description C can be mechanically converted into programs by the translators 1, 2, and 3. Quality and quality can be improved.

Since the state transition engine 16, the signal input unit 17, the event extraction unit 18, and the signal output unit 19 are allowed to be generalized, when defining a new program, the part definition description A and the operation specification description are provided. It is sufficient to describe only B and the event / action definition description C.

Next, another embodiment of the present invention will be described.

FIG. 8 is a block diagram showing the structure of a program creating apparatus according to another embodiment of the present invention and the program created by this apparatus. In addition, in FIG.
The same parts as those in FIG.

In this embodiment, the concept of layering is introduced into the state transition diagram in order to improve the comprehension of the state transition diagram and further reduce the size. The behavior specification description B described in this hierarchical state transition diagram is the second translator 102.
The state transition data table 11
3a and a hierarchy table 113b in which information on hierarchy relationships existing between the state transition diagrams is registered.

As the state transition engine 116,
In addition to the current state management unit 116a and the state transition interpreting unit 116b, a layer interpreting unit 116c that interprets the hierarchical relationship existing between the state transition diagrams by referring to the layer table 113b is prepared.

FIG. 9 shows an example of a hierarchical state transition diagram. In the figure, 91 is a main (topmost) state transition diagram, and 92 is a lower state transition diagram in which the state S2 in this main state transition diagram 91 is expanded. Here, the lower state transition diagram 92 always has one initial state S20, and has the final states E5 and E6 by the number of events (abstract events) from the upper state S2. The state S2 is set as an abstract state.

Next, the flow of state transition on this hierarchical state transition diagram will be described. When the event e1 occurs on the main state transition diagram 91, the state transitions to the state S2, and then to the initial state S20 on the lower state transition diagram 92. Furthermore, when an event e2 occurs here, the state transits to state S22,
Then, the event e3 occurs, so that the final state E5
Transition to. Further, when the event e4 occurs in the state S22, the state transits to the final state E6. Then, by transiting to either of these final states E5 and E6, the event E5 or the event E6 in the main state transition diagram 91 occurs and the state S1 on the main state transition diagram 91
Alternatively, the state transits to state S3. Here, the event E5 and the event E6 which are emitted from the state S2 having the lower development are all abstract events, and the lower final states E5 and E6 are
Determined by That is, the actual event can be accepted only in the states in the state transition diagram 92 of the lower order. Here, the actual event is an event whose occurrence is understood by a signal actually input from the controlled object G.

In this hierarchical state transition diagram, however, by expanding the state transition diagram common to a plurality of states, the number of states and the number of transitions can be greatly reduced.

FIG. 10 shows an example thereof. This is a part of the specifications of the microwave oven and represents the function of controlling the hot air heater in two stages depending on the temperature and time. Here, since the same state name cannot be used on one state transition diagram, in order to call a common state transition diagram from multiple states, each state has a different state name ( Oven 1 and oven 2), the name of the state transition diagram (oven) that expands this state, and the argument (200 degrees, 20 minutes, etc.) to be given to the state transition diagram are described.

The second translator 102 extracts the state name of a state having a hierarchical relationship and the state transition diagram name of the expanded state transition diagram from the hierarchical state transition diagram described above. Then, these are registered in the hierarchy table 113b as information indicating the hierarchy relationship existing between the state transition diagrams.

Next, the state transition engine 1 in this embodiment
The operation of 16 is shown in FIG. Basic operation (Step 1
Nos. 101 to 1108) are the same as those in the previous embodiment, only the characteristic portions will be described here.

In the case where all the events that come out of the current state on a state transition diagram have not occurred (steps 1104 and 110)
9) Further, if this current state is the state on the highest state transition diagram (step 1110), the layer interpreting unit 116c refers to the layer table 113b to display the lowest state transition diagram that expands the current state. A check is made and a transition is made to the initial state (step 1111). If all the events are not fired in the current state on the state transition diagram other than the highest level, the state transitions to the parent state on the state transition diagram one level higher (step 1).
112).

FIG. 12 shows the state transitions in an easy-to-understand manner. The state e is generated from the state st0 on the highest-level state transition diagram 1201
When all the events that have transited to state 1 and exited from this state st1 have not occurred, the state transits to the initial state st111 in the lowest state transition diagram 1202. Furthermore, this initial state s
If all the events have not occurred at t111, the state transitions to the parent state st11 in the state transition diagram 1203 one level higher. Furthermore, if all the events have not occurred in this state st11, the highest state transition diagram 12
Return to the parent state st1 in 01.

As described above, according to this embodiment, the number of states and the number of transitions are determined by introducing the concept of hierarchization into the state transition diagram and expanding the common state transition diagram under the plurality of states. It is possible to improve the comprehensibility of the state transition diagram and reduce the size thereof.

Further, there are the following methods for further reducing the description amount of the state transition diagram.

FIG. 13 (a) specifies that in the hierarchical state transition diagram of FIG. 13 (b), "actual events ([reset key, ON] in this example) that come out of states other than the lowest order are inherited to the lower order". This is an example of description in which is added. That is, in this example, in all the states in each of the lower state transition diagrams of the "during cooking" state, when the reset key is pressed, the state transitions to the reset state.

Further, FIG. 14A is a description expressing an interrupt "A real event is received in a state other than the lowest state and returns to the original state after the action is completed".
Here, a description (broken line) different from the normal transition description (solid line) shown in (b) is used for the description of the transition. This is because, as shown in (c), the transition that has entered the "oven" state enters the initial state of the state transition diagram expanded below it, and cannot return to the original state. . There may be a state in the middle of this interrupt description. Thereby, the number of states and the number of transitions can be reduced.

Next, still another embodiment of the present invention will be described.

FIG. 15 is a block diagram showing the structure of the program creating apparatus of this embodiment and the program created by this apparatus.

In this embodiment, in order to further improve the comprehension of the state transition diagram and further reduce the size, the concept of parallelization is introduced to the state transition diagram in addition to the concept of layering. Then, the behavior specification description B described in the hierarchical and parallel state transition diagrams is interpreted by the second translator 202, whereby the state transition data table 213a, the hierarchy table 213b, and further between the state transition diagrams. A parallel table 213c is created by registering information on existing parallel relationships.

As the state transition engine 216,
In addition to the current state management unit 216a, the state transition interpretation unit 216b, the hierarchy interpretation unit 216c, a parallel interpretation unit 216d that interprets the parallel relationship existing between the state transition diagrams by referring to the parallel table 213c is prepared. .

FIG. 16 shows heater 1, heater 2 and fan 3
The state of ON / OFF control of one control target is shown.
Note that description of events and actions is omitted for simplification. Here, the two heaters are alternately turned on / off at a constant time cycle, and the heater 2 is turned off at x + a degrees.
Turns on at x-a degrees. Also, if the fan reaches y + b degrees, it will be O
N, and OFF when y-b degrees. If you describe this in a single state transition diagram, there are 2 ³ states in total for each of the 3 controlled objects. Of these, 2 heaters cannot be turned on at the same time, so subtract this. There are 6 ways. FIG. 17 describes the state transition diagram of FIG. 16 by introducing the concept of parallelization. As shown in the figure, in this control, the two heaters and the fan are operating independently of each other, so the state transition diagram shows the state transition process P1 for the operation of the two heaters and the operation of the fan. It can be described separately from the state transition process P2.

Then, the second translator 202
Sets a plurality of state transition process names having a parallel relationship from the parallel type state transition diagram described above, and registers the pair of state transition process names in the parallel table 213c.

FIG. 18 is a diagram showing a state transition diagram described by introducing both the concept of hierarchization and parallelization. here,
The state transition process A and the state transition process B are in a parallel relationship, and the state transition process A has a hierarchy.

The operation of the state transition engine 216 represented in this case will be described below. FIG. 19 is a flowchart showing the flow of the operation of the state transition engine 216.

As shown in the figure, in this case, every time the state transition engine 216 evaluates one event on a certain state transition process, the state evaluation engine 216 targets the other state transition regardless of the evaluation result. Switch to process (step 1920).

For example, in the state transition process A of FIG. 18, the st0 state is the current state, and in the state transition process B, stb0.
It is assumed that the state is the current state. First, the event e1 is evaluated on the state transition process A, and it is determined that the event has not occurred. Next, the event ev1 is evaluated on the state transition process B, the occurrence is determined, and the current state on the state transition process B is updated to stb1. Next, state transition process A again
If the event e1 is evaluated above and the occurrence thereof is determined, the current state on the state transition process A is the lower state st1.
Transition to 0. After that, the event ev2 is evaluated on the state transition process B.

Thus, according to this embodiment, the number of states and the number of transitions can be reduced by decomposing and describing the state transition diagrams of the control objects that operate independently, as separate state transition processes. It is possible to improve the comprehension of the state transition diagram and reduce its size.

[0051]

As described above, according to the program creating apparatus of the present invention, it is possible to easily and closely study the specifications with another person, and at the same time, the component definition description,
A program in the target language can be generated directly from the behavior specification description and event / action definition description.
It is possible to improve productivity and quality. Also, by introducing the concept of parallelization to the state transition diagram, it is possible to improve the comprehension of the state transition diagram and reduce the size thereof.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a program creating device according to an embodiment of the present invention and a program created by the device.

FIG. 2 is a diagram showing an example of a component definition description.

FIG. 3 is a diagram showing an example of an operation specification description.

FIG. 4 is a diagram showing the contents of a state transition data table created by a second translator from the operation specification description of FIG.

FIG. 5 is a diagram showing an example of an event / action definition description.

6 is a third diagram from the event / action definition description of FIG.
It is a figure which shows the content of the event table and action table created by the translator of FIG.

7 is a flow chart for explaining the operation of the state transition engine in FIG.

FIG. 8 is a block diagram showing a configuration of a program creating device of another embodiment according to the present invention and a program created by this device.

FIG. 9 is a diagram showing an example of a hierarchical state transition diagram.

FIG. 10 is a diagram showing an example of description in which a common state transition diagram is expanded under a plurality of states.

11 is a flow chart for explaining the operation of the state transition engine in FIG.

FIG. 12 is a diagram for explaining state transitions in a hierarchical state transition diagram.

FIG. 13 is a diagram for explaining subordinate inheritance of an actual event on the hierarchical state transition diagram.

FIG. 14 is a diagram for explaining an interrupt on a hierarchical state transition diagram.

FIG. 15 is a block diagram showing the configuration of a program creating device and a program created by this device according to still another embodiment of the present invention.

FIG. 16 is a diagram showing an example of a state transition diagram that is the target of parallelization introduction.

FIG. 17 is a diagram showing a state transition diagram expressing the state transition diagram of FIG. 16 in parallel.

FIG. 18 is a diagram showing a state transition diagram described by introducing concepts of both hierarchization and parallelization.

19 is a flowchart for explaining the operation of the state transition engine in FIG.

[Explanation of symbols]

 201 ... First translator 202 ... Second translator 203 ... Third translator 211 ... Event component 212 ... Action component 213a ... State transition data table 213b ... Hierarchical table 213c ... Parallel table 214 ... Event table 215 ... Action Table 216 ... State transition engine 217 ... Signal input section 218 ... Event extraction section 219 ... Signal output section A ... Parts definition description B ... Behavior specification description C ... Event / action definition description

─────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] August 11, 1993

[Procedure Amendment 1]

[Document name to be corrected] Drawing

[Correction target item name] All drawings

[Correction method] Change

[Correction content]

[Figure 1]

[Fig. 2]

[Figure 3]

[Figure 4]

[Figure 5]

[Figure 6]

[Figure 9]

[Figure 7]

FIG. 17

[Figure 8]

[Figure 10]

[Fig. 12]

FIG. 11

FIG. 18

[Fig. 13]

FIG. 14

FIG. 15

FIG. 16

FIG. 19

Claims (1)

[Claims] 1. A first conversion means for converting a part definition description into an event part and an action part of a target language, and an operation specification description expressed by a state transition diagram including an event and an action and introducing a concept of parallelization. Second conversion means for converting the target language into a format that can be interpreted to create a state transition data table, and for creating a parallel table in which information on parallel relationships existing between the state transition diagrams is registered. Third, an event / action table is created by converting an event / action definition description that defines the event component and action component corresponding to the event and action on the behavior specification description into a format that can be interpreted by a target language. And the event parts and the action parts obtained by the respective conversion means, By referring to the state transition data table, the parallel table, and the event / action table, and referring to the state transition data table, the parallel table, and the event / action table, the parallel relationship existing between the state transition diagrams is grasped. However, the program creating apparatus is characterized in that the target program is generated by combining with the state transition engine unit for driving the event parts and the action parts.