JPH11338684A - State transition movement system, its generating method and computer readable medium for recording the same system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a state transition movement system which efficiently develops a new state transition movement system by reusing an existing state transition movement system. SOLUTION: A sequence control system is provided with at least two sequence parts 1 to realize partial movement specifications that are made by dividing a representable movement specification as a state transition diagram, and a connecting part 2 that connects the sequence parts 1. The part 2 switches activation of the parts 1 based on an external event. Further, the part 2 allocates the externally given event to either of each sequence part 1 when the event does not accompany activation switching between the parts 1 and switches activation of the parts 1 and also changes the internal state of the parts 1 when the event accompanies activation switching between the parts 1.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a state transition operation system such as a sequence control system for realizing an operation specification that can be expressed as a state transition diagram, and more particularly to a new state transition by reusing an existing state transition operation system. The present invention relates to a state transition operation system that enables efficient development of an operation system, a generation method thereof, and a computer-readable recording medium recording the state transition operation system.

[0002]

2. Description of the Related Art Conventionally, a sequence control system has been known as a system for controlling a series of operations caused by an external input or a change in an internal state, such as a TV control system. The operation specification of such a sequence control system can usually be described by a state transition diagram.
The state transition diagram schematically represents transitions between states, inputs (events) that cause the transition, conditions that cause the transition, and actions (actions) that accompany the transition. Note that a sequence control system that implements the operation specifications described by the state transition diagram can be implemented by a computer program.

[0003] When a sequence control system is implemented by a computer program, there is often a need to add a new function to the operation specifications of the sequence control system developed in the past to extend the operation specifications. Conventionally, in such a case, a new sequence control program is created by directly changing the inside of the sequence control program that realizes transition between states and the like.

FIGS. 23 to 26 are views for explaining a method of developing a conventional sequence control system (TV control system). FIG. 23 is a state transition diagram describing operation specifications of the TV control system. In FIG. 23, two boxes with rounded corners represent two states that the TV control system can take, namely, “power off” and “tuning processing”. The arrows connecting the boxes represent transitions between the states, and the description attached to the arrows represents an event that causes the transition and an action executed in accordance with the transition. Here, there are three transitions.
The transition from the “power OFF” state to the “tuning process” state occurs when a “power button input” event is received, and at the same time, an operation of “power relay on” is performed as an action. Also, from the “tuning process” state to the “tuning process”
The transition to the state occurs when the "tuning button input" event is received, and at the same time, the operation of "channel switching processing" is performed as an action. Furthermore, "tuning process"
The transition from the state to the "power OFF" state occurs when the "power button input" event is received, and at the same time, the operation of "power relay off" is performed as an action.

That is, in the state transition diagram shown in FIG.
This document describes the operation specifications of a simple TV having a power button and a music selection button. The power is turned on / off by inputting the power button, and it is shown that the channel can be switched by the music selection button when the power is turned on. I have. Note that a sequence control system that realizes such operation specifications is implemented, for example, as a sequence control program as shown in FIG. 24 in a programming language (C ++ language).

Here, consider a case where a request has been made to add a new function to such a sequence control system to extend its operation specifications. FIG. 25 is a state transition diagram describing an example of the extended operation specification. FIG. 25 shows a case where a function of a "sleep timer" for turning off the power after a certain period of time after pressing the sleep timer button is added. In this case, the state transition diagram shown in FIG. One transition and two states have been added. Here, the transition from the “tuning process” state to the “sleep timer wait” state occurs only when the “sleep timer button input” event is received in the “tuning process” state, and at the same time, the “ The operation of "starting of the rest timer" is performed. Further, the bidirectional transition between the "wait for rest timer" state and the "time display" state occurs when the "display button input" event is received in the "wait for rest timer" state. When the "display button input" event is received in the "wait for rest timer" state, the action is "power off."
The time until the power is turned off is displayed on the screen for a certain period of time until the counting of the display timer is completed. The transition from the "waiting" state to the "power OFF" state occurs when the count of the rest timer ends, and the action of "power relay off" is performed as an action.

Conventionally, as a method for developing a sequence control program for realizing such an extended operation specification, the sequence control program shown in FIG. 25, a new sequence control program for realizing the operation specifications as shown in FIG. FIG. 26 is a diagram showing an example of a sequence control program created by such a method. In the sequence control program shown in FIG. 26, lines 3 to 4, 11 to 12, and 34
Lines 71 to 71 have been changed.

[0008]

As described above, in the prior art, when a new function is added to an operation specification of a sequence control system developed in the past to extend the operation specification, an existing sequence control program is used. A new sequence control program was created by directly changing the inside of the program.

However, in such a conventional method of generating a sequence control system, the existing sequence control program is directly modified and modified, so that the sequence control program to be modified is understood in detail. There is a need. For this reason, when the inside of the sequence control program to be corrected is complicated, many man-hours are required, and there is a problem that the possibility of errors being mixed during the work increases.

In the case where the sequence control program is realized on hardware using a mask ROM or the like, even when the sequence control program is reused, the existing ROM is discarded and a new one is created. However, there is a problem that it is not economical to create a ROM.

SUMMARY OF THE INVENTION The present invention has been made in view of the foregoing points, and has been made in consideration of the above circumstances. A state transition which enables the efficient development of a new state transition operation system by reusing an existing state transition operation system. An object of the present invention is to provide a computer-readable recording medium on which an operation system, a generation method thereof, and a state transition operation system are recorded.

[0012]

A first feature of the present invention is as follows.
At least two state transition components that realize a partial operation specification obtained by dividing an operation specification that can be expressed as a state transition diagram, and a joining component that connects between the state transition components, wherein the joining component is When an event given from the outside does not involve switching of activation between the state transition parts, the event is distributed to any of the state transition parts, and the event involves activation switching between the state transition parts. A state transition operation system characterized by occasionally switching the activation of each state transition part and changing the internal state of the state transition part to be switched.

A second feature of the present invention is to extract transition data including an event corresponding to a state transition, a transition source state, a transition destination state, and an action based on an operation specification of the first state transition component. Creating a first transition data list, and generating transition data including an event corresponding to a state transition, a transition source state, a transition destination state, and an action based on a required operation specification of the state transition operation system. Extracting and creating a second transition data list; and when there is common transition data between the first transition data list and the second transition data list, the second transition data list A transition data that does not include the transition source or transition destination state included in the first transition data list is extracted from the transition data included in the list, and a third transition data list is extracted. And creating a second
Creating a fourth transition data list by removing a portion overlapping the first transition data list and the third transition data list from the third transition data list; and Creating a second state transition part to be used together with the first state transition part, and connecting the first state transition part and the second state transition part based on the fourth transition data list. Creating a joining part to be connected.

A third feature of the present invention is that at least two state transition parts for realizing a partial operation specification obtained by dividing an operation specification that can be expressed as a state transition diagram, and a connection between the respective state transition parts When the event given from the outside does not involve switching of activation between the state transition parts, the joint part sorts the event to one of the state transition parts, and the event A computer which records a state transition operation system, wherein the activation of each of the state transition parts is switched when the activation of the state transition parts is switched, and the internal state of the state transition part to be switched is changed. It is a readable recording medium.

According to the first to third aspects of the present invention, a new state transition operation system can be generated by reusing the state transition operation system, so that the new state transition operation system can be efficiently implemented. Can be developed. In addition, since the state transition parts and joint parts created in such a development process can be reused as sequence parts in the next new development process, the state transition operation system is made into a subsystem (parts). System development can proceed efficiently.

[0016]

Embodiments of the present invention will be described below with reference to the drawings. 1 to 12 are diagrams showing one embodiment of a state transition operation system and a generation method thereof according to the present invention. In the present embodiment, a case where the state transition operation system is applied to a sequence control system will be described as an example.

First, the configuration of the sequence control system will be described with reference to FIGS.

As shown in FIG. 1, the sequence control system includes at least two sequence parts (state transition parts) 1 for realizing a partial operation specification obtained by dividing an operation specification that can be expressed as a state transition diagram; Each sequence part 1
And a joining component 2 for connecting between the components. The joining component 2 can switch the activation of the sequence component 1 based on an event given from the outside.

As shown in FIG. 2, each of the sequence components 1 includes an event input unit 1a for receiving an externally applied event, a current state storage unit 1e for holding a current internal state, and an event input unit. State change / action start means 1d for changing the internal state currently held in the state storage means 1e and activating an action accompanying a state transition based on the event received by 1a; 1
and action output means 1f for realizing the operation content of the action started by d. In addition, each sequence component 1 has a state designating unit 1b that changes the internal state currently held in the state storage unit 1e according to the designation of the state given from the outside, and an inquiry about the state given from the outside. Accordingly, it has a state inquiry unit 1c for returning the current internal state held in the current state storage unit 1e, and an initialization unit 1g for initializing the internal state held in the current state storage unit 1e.

On the other hand, as shown in FIG.
An event input unit 2a for receiving an externally applied event; an active component data storage unit 2c for holding data representing an active sequence component; an event received by the event input unit 2a; An event handling unit 2b for allocating events, switching the start of each sequence component 1, and changing the internal state of the sequence component 1 to be switched based on the data held in the unit 2c. ing. Also, the joining component 2
A component communication unit 2d communicates with each sequence component 1 for events, internal state change requests, and internal state inquiry requests. Furthermore, the joining component 2
Action output means 2 for realizing the contents of an action to be started as needed when the start of each sequence component 1 is switched by the event handling processing means 2b
e and the data representing the sequence component held in the active component data storage means 1c are initialized to set the sequence component to be active at the start of use of the component, and to secure a communication path for communication by the component communication means 2d. And initialization means 2f.

Next, a method of generating a sequence control system having such a configuration will be described with reference to FIGS. Here, an existing sequence control system for realizing the operation specifications as shown in FIG. 4 is reused as a sequence component, and a sequence for realizing the operation specifications as shown in FIG. 5 by a programming language (C ++ language). The case where a control system is generated will be described as an example.

As shown in FIG. 6, first, an event corresponding to a state transition, a state of a transition source, a state of a transition destination and an action are determined based on the operation specifications of an existing sequence component (first state transition component). The included transition data is extracted to create a component sequence specification (first transition data list) (step 101).

Here, the "sequence specification" expresses the same content as a state transition diagram describing an operation specification by using the concept of a set. Specifically, a state transition in a state transition diagram is represented by transition data including four elements of an event, a transition source state, a transition destination state, and an action, and the entire operation specification is represented as a set of the transition data. I do. Here, when the state transition diagram as shown in FIG. 4 is expressed by a sequence specification, the following specification 1 is obtained.

Specification 1: {<event1, α, β, action1>, <even
t2, β, α, action2>} Since the operation specification described by the state transition diagram as shown in FIG. 4 is the operation specification of an existing sequence control system (sequence component) to be reused, Then, the above specification 1 is referred to as a component sequence specification.

Next, an event corresponding to a state transition based on a required operation specification of the sequence control system,
A request sequence specification (second transition data list) is created by extracting transition data including a transition source state, a transition destination state, and an action (step 102).

Here, the required sequence specification expresses the operation specification of the sequence control system to be realized as a sequence specification. here,
When the operation specifications described by the state transition diagram shown in FIG. 5 are to be realized, the required sequence specifications are as shown in the following specification 2. Specification 2: {<event1, α, β, action1>, <event2, β, α, ac
tion2>, <event3, γ, α, action3>, <event4, β, γ, actio
n4>, <event1, γ, δ, action5>, <event2, δ, γ, action6
>}

Next, it is determined whether or not the existing sequence component can be reused (step 103). here,
In order for existing sequence components to be reusable when implementing the required sequence control system, common transition data between the transition data included in the component sequence specification and the transition data included in the required sequence specification Must exist (reuse condition). Note that the common transition data means that the four elements of the transition source state, the transition destination state, and the action are all equal.

In step 103 described above, when it is determined that common transition data exists between the part sequence specification and the required sequence specification and the existing sequence part can be reused, it is included in the required sequence specification. Sequence data that does not include the state of the transition source or transition destination appearing in the part sequence specification from the transition data to be executed and extracts the difference sequence specification (third transition data list)
Is created (step 104).

Here, the difference sequence specification is a sequence specification in which a difference between the required sequence specification and the component sequence specification is extracted. Specifically, transition data that does not include the transition source or transition destination state appearing in the component sequence specification is extracted from the transition data included in the request sequence specification. When the above specification 1 is a part sequence specification and the above specification 2 is a required sequence specification, the difference sequence specification becomes the following specification 3 (see FIG. 7). Specification 3: {<event1, γ, δ, action5>, <event2, δ, γ, ac
tion6>} Next, a part that overlaps with the part sequence specification and the difference sequence specification is removed from the request sequence specification to create a joint sequence specification (fourth transition data list) (step 105).

Here, the joining sequence specification is a sequence specification for connecting a sequence component realizing the component sequence specification and a sequence component realizing the difference sequence specification. Specifically, it is a set of transition data that is not included in the part sequence specification or the difference sequence specification among the required sequence specifications. When the above specification 1 is a part sequence specification and the above specification 2 is a required sequence specification, the joining sequence is the following specification 4.
(See FIG. 8). Specification 4: {<event3, γ, α, action3>, <event4, β, γ, ac
tion4>}

Thereafter, a new sequence component (second state transition component) to be used together with the existing sequence component is created based on the differential sequence specification (step 106), and the existing sequence component and the new sequence component are created based on the joining sequence specification. A joining component for connecting the new sequence components is created (step 107).

Here, an existing sequence component corresponding to the component sequence specification, a new sequence component corresponding to the difference sequence specification, and a junction component corresponding to the junction sequence specification are implemented as programs in, for example, a programming language (C ++ language). Is done. Note that these programs are stored in various computer-readable recording media such as an internal storage device such as a memory or a hard disk on a computer, and an external storage device such as a flexible disk or a CD-ROM. (Central processing unit) and are sequentially read and executed.

As shown in FIG. 2, the sequence component 1 corresponding to either the component sequence specification or the difference sequence specification includes an event input unit 1a and a state designation unit 1.
b, status inquiry means 1c, status change / action activation means 1d, current status storage means 1e, action output means 1f, and initialization means 1g.

In the sequence component 1 shown in FIG. 2, the event input means 1a is for inputting an event to the sequence component 1 from the outside. O
This is realized by S or an event dispatch function provided by a programming language. The event input unit 1a notifies the state change / action start unit 1d of the input of the event. The state change / action activating means 1d is for performing the change of the internal state and the activation of the action based on the input event in accordance with the component sequence specification or the differential sequence specification.
The next state to be transitioned and the action to be activated are determined based on the current internal state held in the storage unit and the input event, and when the state needs to be changed, the current state is stored in the current state storage unit 1e. The held internal state is rewritten to the next state, and when it is necessary to activate the action, the action output unit 1f is notified of the activation of the action. The action output means 1f is for realizing the operation content of each action. The action output means 1f is realized by a function or the like for realizing the operation content of the action on the program, and performs the status change /
Notification of the activation of the action by the action activation means 1d is realized by calling these functions or the like. The current state storage means 1e is realized on the program as a variable that holds the current internal state. The state designating means 1b, when a state is designated from the outside, stores the current state storing means 1e.
Is rewritten to a value corresponding to the designated state, and is realized by a function or the like which rewrites a value stored in the current state storage means 1e which is a variable in a program. The state inquiry means 1c is for notifying the current internal state to the outside, and returns a value representing the current internal state by referring to a value stored in the current state storage means 1e which is a variable in the program. This is realized by a function or a function that returns a Boolean value indicating whether or not the current state is a state corresponding to a state given as an argument. The initializing means 1g is for initializing the internal state held in the current state storing means 1e. The program is activated before starting the use of the parts and initializes the value held in the current state storing means 1e. This is realized by a function or the like that rewrites a value corresponding to a state.

On the other hand, as shown in FIG. 3, the joining part 2 corresponding to the joining sequence specification has event input means 2a,
Event response processing means 2b, active component data storage means 2c, component communication means 2d, action output means 2
e, and initialization means 2f.

In the joining part 2 shown in FIG. 3, the event input means 2a is for inputting an event to the joining part 2 from the outside. And an event dispatch function provided by a programming language. The event input unit 2a receives all events included in the request sequence specification,
For example, when one event is input by calling one function, functions corresponding to all events included in the request sequence specification are created. The event input means 2a inputs the event input to the event response processing means 2
Notify b. When the event received by the event input unit 2a does not involve switching of activation between the sequence components 1, the event handling unit 2b distributes the event to one of the sequence components 1, and the event is activated between the sequence components 1. Is switched, the activation of each sequence component 1 is switched, and the internal state of each sequence component 1 is changed.

FIG. 9 is a flow chart for explaining the processing contents of the event input means 2a, the event correspondence processing means 2b and the like. As shown in FIG. 9, after the initialization processing by the initialization means 2f is completed (step 20).
1) An event is received by the event input means 2a (step 202). Then, the event correspondence processing unit 2b determines the component switching condition based on the input event and the data representing the currently active sequence component held in the active component data storage unit 2e (step 203). ). Here, the component switching condition is to determine whether it is necessary to switch and operate each sequence component that realizes each of the divided component sequence specification and the differential sequence specification. Specifically, the input event is represented by e, and the current state of the active sequence component is represented by S.
Then, it is determined whether or not transition data having e as an event (first element) and S as a transition source state (second element) exists in the joining sequence specification.

Here, when the component switching condition is satisfied, the action of the corresponding transition data is executed by the action output means 2e (step 204).
The internal state of the sequence component 1 to be switched is determined by the component communication unit 2d and the state designation unit 1b of the sequence component 1.
As a result, the state of the corresponding transition data is changed to the transition destination state (third element) (step 205). At the same time, data representing the sequence component to be switched is set in the active component data storage unit 2c (step 20).
6). Note that the order of the processing of steps 204 to 206 is arbitrary.

On the other hand, if the component switching condition is not satisfied, an active sequence component is obtained by referring to the active component data storage means 2c, and an event is transmitted to the active sequence component by the component communication means 2d. .

The initialization means 2f rewrites the data stored in the active component data storage means 2c into data representing a sequence component which becomes active at the start of use of the component, and the communication by the component communication means 2d. This is realized by a function or the like for securing a communication path to be performed.

FIGS. 10 to 12 show an existing sequence component corresponding to the component sequence specification, a new sequence component corresponding to the differential sequence specification, and a junction component corresponding to the junction sequence specification in a programming language (C ++ language). It is a figure showing an example at the time of implementing as a program.

The class Component shown in FIG. 10 is a program for mounting the sequence component 1 for realizing the component sequence specification of the above specification 1 (see FIG. 4). FIG.
0, the event input means 1a outputs the function event1 (), ev
It corresponds to ent2 (). Input of events from outside is performed by calling these functions. The action output means 1f corresponds to the functions action1 () and action2 (). Various actions such as output of data to an output buffer and activation of a timer are implemented inside these functions, but detailed description thereof is omitted here. The current state storing means 1e is realized by a variable state. Variable sta
te takes “Alpha” or “Beta” as a value, and when each value is taken, the current state of the sequence component Component becomes “α” or “β” (see FIG. 4). The initialization means 1g is realized as an initialization function Component (),
As a result, the value of the variable state is set to “Alpha” when an instance of the class Component is generated. By the operation of the initialization function Component (), the sequence component Com
The initial state of ponent is set as “α”. State change
The / action output means 1d is realized by a function body program of functions event1 () and event2 (). Function event1
(), Event2 () is the current stat every time a function call occurs
The change to the next state is obtained based on the value of e, and if a state transition is required, the value is rewritten. State designation means 1
b is realized by the function setState (). This function implements the change to the specified state by assigning the value given as an argument to state. The state inquiry means 1c is realized by the function isState (). This function determines whether the current state is the state given as an argument and returns the result.

The class Complement shown in FIG. 11 is a program for mounting the sequence component 1 for realizing the difference sequence specification of the above specification 3 (see FIG. 7). FIG.
As shown in FIG. 1, since the structure of this program is substantially the same as the structure of the program shown in FIG. 10, detailed description will be omitted.

The class Switcher shown in FIG. 12 is a program for mounting the joining component 2 that realizes the joining sequence specification 4 (see FIG. 8). In FIG. 12, the event input means 2a corresponds to functions event1 () to event4 (). Input of events from outside is performed by calling these functions. The active component data storing means 2c includes variables ComponentActiveFlag, Complem
Implemented by entActiveFlag. These variables correspond to the sequence components Component and Complement, respectively.
When the value is 1, it indicates that the sequence component is active, and when the value is 0, it indicates that the sequence component is not active. The component communication means 2d is a comp which is a pointer variable to the sequence component.
It is realized by onent and complement. Each of these holds the instance of the sequence component Component and the address of the instance of the sequence component Complement. In the C ++ language, a function of an instance can be called through a pointer variable. For this reason, the joint component Switcher can access the event input unit 1a, the state designation unit 1b, and the state inquiry unit 1c of the sequence component realized as a function of each instance using these pointer variables.

The initialization means 2f is realized as an initialization function Switcher (). The initialization function Switcher () takes the address of the instance of the sequence component Component as an argument,
The address of the instance of the sequence component Complement is taken, and each is substituted for the pointer variables component and complement, which are the component communication means 2d. As a result, the component communication means 2d is initialized, and the sequence component Componen
t, can be used to access Complement. Further, the initialization function Switcher () is a variable ComponentActiveFla that is the active component data storage unit 2c.
g and ComplementActiveFlag are set to 1 and 0, respectively. This allows active sequence components to be
Initialize to Component.

The event correspondence processing means 2b has a function event
It is realized by the function body program of 3 () and event4 (). The function event3 (), event4 ()
This is realized by two if statements inside. The process of executing the action when the component switching condition is satisfied, the process of changing the internal state of the sequence component to be switched, and the process of making the sequence component to be switched active and inactive the other are the function event3 () Call the function action3 (), the pointer variable component
Function setState () call to the sequence component specified by, variables ComponentActiveFlag, ComplementActiveFlag
Is realized by rewriting. In the function body program of the function event4 (), the function action4 () is called and the function to the sequence component specified by the pointer variable complement is
Call setState (), variables ComponentActiveFlag, Compl
This is realized by rewriting ementActiveFlag. on the other hand,
The processing when the component switching condition is not satisfied is defined by the functions event1 (), ev
This is realized by calling the event receiving functions event1 () and event2 () to the active sequence component inside ent2 (). The action output means 2e has a function
action3 () and action4 () correspond.

As described above, according to the present embodiment, the existing sequence control system for realizing the operation specifications (part sequence specifications) as shown in FIG. Since a sequence control system that realizes the required sequence specification can be generated, a new sequence control system can be efficiently developed.

The sequence parts (see FIG. 11) and the joint parts (see FIG. 12) created in such a development process.
Can also be reused as a sequence component in the next new development process, so that the sequence control system can be made into a subsystem (component) to efficiently advance system development.

In the above-described embodiment, the case where the present invention is applied to a sequence control system has been described. However, the present invention is not limited to this, and various state transition operation systems such as a lexical analysis system of a compiler are also applicable. And can be applied.

[0050]

Next, a specific embodiment of the sequence control system shown in FIGS. 1 to 12 will be described.

First Embodiment First, an embodiment in which the sequence control system shown in FIGS. 1 to 12 is applied to a TV control system will be described with reference to FIGS. Here, after developing a sequence control system that realizes the operation specifications described by the state transition diagram as shown in FIG. 13, this sequence control system is reused as a sequence component, and as shown in FIG. A case in which a sequence control system that realizes the operation specifications described by the state transition diagram will be described.

FIG. 15 shows a sequence component TvSequence1 for realizing the operation specifications shown in FIG.
++ language).
In the state transition diagram shown in FIG. 13, there are two types of events, “input of power button” and “input of channel selection button”, and therefore, the event input unit 1a is created to accept these events. The input of an event can correspond to a function call on a program. FIG.
In the program shown in FIG. 5, the event input means 1a
Two functions powerButtonEvent (), selectButtonEv
It has ent (), each of which has “power button input” from outside
The input of the event and the “tuning button input” event can be accepted as a call from outside of these functions. When an event is input, a state change / action activation means 1d changes the state corresponding to the event and activates the action. In the program shown in FIG. 15, the functions powerButtonEvent (), selectButtonEven
The function body program of t () corresponds to this. For example,
In the state change / action start means 1d realized as a function body program of the function powerButtonEvent (),
The variable state is set to "POWER_OF"
Based on whether the current state is "F" or "TUNING", it is determined whether the current state is the "power-off" state or the "tuning process" state, and an event corresponding to each state is determined. The state is changed and the action is activated.

The action output means 1f for realizing the action contents of the action includes functions powerOn (), powerOff (), s corresponding to the actions of "power relay on", "power relay off", and "channel switching processing", respectively.
Implemented as etChannel (char ch). Although the function body program of each function is omitted here,
In a TV control system, a program for transmitting data for instructing an operation to a control IC, which is an actual device, and actual processing such as calling of such a subroutine are implemented. The current state storing means 1e for holding the current state of the sequence component is realized as a variable state. The variable state is a variable of the enumeration type State, and takes "POWER_OFF" or "TUNING" as a value. When each value is taken, the current state of the sequence component is "power OFF" state or "tuning process". State is indicated. State specifying means 1 for forcibly changing the state from outside
b and the state inquiring means 1c for inquiring about the state from outside are respectively a function setState (State tmpStat
e), implemented as isState (State tmpState).
The function setState (State tmpState) realizes a change to a specified state by substituting a value given as an argument into a variable state in a function body program. Also, the function is
State (State tmpState) is a variable st that holds the value of the current state in the function body program with the value given as an argument
By comparing with ate and returning the result as a truth value, information about the current state is passed to the caller of the external function.

The initialization means 1g for initializing the state of the component is realized as an initialization function TvSequence1 (). In this case, "POW" is added to the variable state in the function body program.
By substituting the value of “ER_OFF”, the status is changed to “power OFF”.
Initialized to F "state.

Next, when the TV control system as shown in FIG. 15 already exists, this TV control system is reused as a sequence component to realize the operation specifications described by the state transition diagram shown in FIG. A procedure for generating a TV control system to be performed will be described.

As shown in FIG. 6, first, a component sequence specification is created based on the operation specification of an existing sequence component (step 101). Specifically, transitions in the state transition diagram shown in FIG. 13 are extracted, and transition data including four elements of an event corresponding to the transition, a transition source state, a transition destination state, and an action for each transition, A part sequence specification is created as a set of the transition data.
Note that the state transition diagram shown in FIG. 13 includes a transition from the “power OFF” state to the “tuning processing” state, a transition from the “tuning processing” state to the “power OFF” state, and a transition from the “tuning processing” state. Since there are three transitions to the “tuning process” state, the component sequence specification
It is created as a set of two transition data as shown in the following specification 5. Specification 5: {<power button input, power OFF, tuning process, power relay ON>, <power button input, tuning process, power OF
F, power relay off>, <tuning button input, tuning process, tuning process, channel switching process>}

Next, a required sequence specification is created based on the required operation specification of the TV control system (step 102). Specifically, a request sequence specification corresponding to the state transition diagram shown in FIG. 14 is created. The method of creation is the same as in step 101 described above, and the resulting required sequence specification is as shown in specification 6 below. The request sequence specification of the specification 6 has seven transition data corresponding to the seven transitions included in the state transition diagram shown in FIG. In the sixth transition data, two actions are enclosed in parentheses, which indicates that there are two actions for one transition. Specification 6: {<power button input, power OFF, tuning process, power relay ON>, <power button input, tuning process, power OF
F, power relay off>, <tuning button input, tuning process, tuning process, channel switching process><sleep timer button input, tuning process, sleep timer wait, sleep timer start
>, <Stop timer count end, sleep timer wait, power OFF, power relay ON>, <display button input, sleep timer wait, time display, (time display until power OFF,
Display timer start)>, <display timer count end, time display, rest timer wait, display clear>

Next, it is determined whether or not the existing sequence component can be reused (step 103). here,
As described above, the reuse condition is that common transition data exists between the transition data included in the component sequence specification and the transition data included in the required sequence specification. Here, when the above-mentioned specification 5 which is a part sequence specification is compared with the above-mentioned specification 6 which is a required sequence specification,
It can be seen that the three transition data included in the above specification 5 are equal to the respective transition data up to the third in the above specification 6. Therefore, it is determined that the sequence component shown in FIG. 15 is reusable.

In this case, from the transition data included in the required sequence specification of the above specification 6, transition data not including the state of the transition source or the transition destination appearing in the part sequence specification of the above specification 5 is extracted, and the difference sequence specification is made. It is created (step 104). Here, the state of the transition source or the transition destination appearing in the component sequence specification of the above specification 5 is “power supply O
FF "state and" tuning processing "state. When transition data not including these states is extracted from the transition data included in the request sequence specification of the above specification 6, the obtained difference sequence specification is the following specification 7. Specification 7: {<Display button input, rest timer wait, time display, (time display until power OFF, display timer start)>, <
Display timer end, time display, rest timer wait, display erase>}

Next, a part that overlaps with the part sequence specification of the above specification 5 and the difference sequence specification of the above specification 7 is removed from the required sequence specification of the above specification 6, and a joining sequence specification such as the following specification 8 is created. (Step 105). Specification 8: {<rest timer button input, channel selection processing, rest timer wait, rest timer start>, <rest timer count end, rest timer wait, power OFF, power relay ON>｝

Thereafter, a new sequence component to be used together with the existing sequence component is created based on the difference sequence specification of the above specification 7 (step 10).
6) Based on the joining sequence specification 8 described above, a joining component for connecting an existing sequence component and a new sequence component is created (step 107).

FIG. 16 is a diagram showing an example of a case where the sequence component TvSequence2 for realizing the difference sequence specification of the above specification 7 is implemented in a programming language (C ++ language). The structure of the program shown in FIG.
5 has almost the same structure as the program shown in FIG.

In the difference sequence specification of the above specification 7, "input of display button" and "end of display timer count"
Since there are two types of events, the event input unit 1a is created to accept these events. The input of an event can correspond to a function call on a program. In the program shown in FIG. 16, two functions displa are used as the event input means 1a.
It has yButtonEvent () and displayTimeOverEvent (), and can receive externally input "display button input" event and "display timer count end" event as external calls to these functions. When an event is input, the state change / action activation means 1d changes the state corresponding to the event and activates the action. In the program shown in FIG. 16, the function body program of the functions displayButtonEvent () and displayTimeOverEvent () Corresponds to this. For example, the function disp
In the state change / action initiating means 1d implemented as a function body program of layButtonEvent (), the current state is determined based on whether the variable state is "SLEEP_TIMER" or "TIME_DISPLAY" by a conditional branch by an if statement. Is determined to be in the "waiting for rest timer" state or the "time display" state, and only when in the "waiting for rest timer" state, the state corresponding to the event is changed and the action is started. It has become.

The action output means 1f for realizing the action contents of the action includes functions displayTime () and startDisp corresponding to the actions of "display time until power-off", "display timer start" and "display erase", respectively.
Implemented as layTimer () and eraseTime (). Although the function body program of each function is omitted here, in the TV control system, the control I
An actual process such as a program for transmitting data for instructing C to operate or a call of such a subroutine is implemented. The current state storing means 1e for holding the current state of the sequence component is realized as a variable state. The variable state is a variable of the enumeration type State, and takes the value “SLEEP_TIMER” or “TIME_DISPLAY”. When the respective values are taken, the current state of the sequence component is “Waiting for timer for rest” or “Time display”. "
State. The state specifying means 1b forcibly changing the state from the outside and the state inquiring means 1c for inquiring about the state from the outside are respectively a function setState (State t
mpState) and isState (State tmpState). The function setState (State tmpState) realizes a change to a specified state by substituting a value given as an argument into a variable state in a function body program. Also,
The function isState (State tmpState) compares the value given as an argument with the variable state which holds the value of the current state in the function body program, and returns the result as a truth value to the external function caller. It passes information about the current state.

The initialization means 1g for initializing the state of the component is realized as an initialization function TvSequence2 (). In this case, "SLE" is added to the variable state in the function body program.
By substituting the value of “EP_TIMER”, the state is initialized to “wait for a rest timer”.

FIG. 17 is a diagram showing an example of a case where the joining part TvSwitcher for realizing the joining sequence specification of the above specification 8 is implemented in a programming language (C ++ language). In the program shown in FIG. 17, the active component data storing means 2c is a variable of the enumeration type ActiveSequence.
Implemented as activeSequence. Variable activeSequ
ence takes "SEQ1" or "SEQ2" as a value, and each value is the currently active sequence component Tv.
It corresponds to Sequence1 or sequence component TvSequence2. The component communication means 2d is realized by seq1Ptr and seq2Ptr which are pointer variables to sequence components. These hold the address of the instance of the sequence component TvSequence1 and the address of the instance of the sequence component TvSequence2, respectively. In the C ++ language, a function of an instance can be called through a pointer variable. Therefore, the joining component TvSwitcher can access the event input unit 1a, the state specifying unit 1b, and the state inquiry unit 1c of the sequence component realized as a function of each instance using these pointer variables.

The action output means 2e describes the process of executing the action included in the joining sequence specification of the above specification 8. In the joining component TvSwitcher shown in FIG. 17, the action of the action of "power relay off" and "start of the sleep timer" is performed. Corresponding functions powerOff (), startSleepTi
Implemented as mer (). Although a function body program of each function is omitted here, in a TV control system, a program for transmitting data for instructing an operation to a control IC, which is an actual device, and a process such as calling of such a subroutine. Is implemented.

The initialization means 2f includes an initialization function TvSwitcher (T
vSequence1 * apSeq1, TvSequence2 * apSeq2). This initialization function receives, as arguments, the address of the instance of the sequence component TvSequence1 and the address of the instance of the sequence component TvSequence2, and stores them in the pointer variable seq1 which is the component communication means 2d.
Assign to Ptr and seq2Ptr. This initialization function is a variable activeSequ
By substituting "SEQ1" for the ence, the sequence component to be activated is initialized to the sequence component TvSequence1.

Here, the joining component TvSwitcher needs to be able to input all events included in the required sequence specification. Therefore, “power button input”, “tuning button input”, “sleep timer count end”, “sleep timer button input”, “display button input”, and “display timer count end” included in the above specification 6 are included. It is necessary to be able to input six events. Therefore, a function corresponding to the input of each event is realized as the event input means 2a, similarly to the sequence components TvSequence1 and TvSequence2 described above. These functions are powerBut
tonEvent (), selectButtonEvent (char ch), displayBut
tonEvent (), displayTimeOverEvent (), sleepButtonEve
nt () and sleepTimeOverEvent ().

When an event is input, processing corresponding to the event is performed by the event processing unit 2b. In the program shown in FIG. 17, a function body program of the function which is the event input unit 2a corresponds to this. The event handling unit 2b performs a component switching condition determination process based on the received event and the current state, a process when the component switching condition is satisfied, and a process when the component switching condition is not satisfied.

First, in the process of determining the component switching condition, when the input event is e and the current state of the active sequence component is S, e is the event (first
Element), and determine whether or not transition data having S as a transition source state (second element) exists in the joining sequence specification.
In this case, since the joining sequence specification is composed of two transition data, the combination of the event and the transition source state in the transition data in the joining sequence specification is <sleep timer button input, channel selection processing> and <O. It is possible to limit the timer to the end of the rest timer and wait for the rest timer.

Therefore, it is sufficient to judge the component switching condition only when the input event is “end of the rest timer count” or “input of the rest button”.
If any other event is input, the component switching condition is not satisfied. In other words, the function sleepButtonEve
As for the event input by calling a function other than nt () and sleepTimeOverEvent (), it is determined that the component switching condition is not satisfied at the time the function is called, so the process of determining the component switching condition can be omitted. . Therefore, the function
This judgment processing is incorporated only in the sleepButtonEvent () and sleepTimeOverEvent () function body programs.

For example, in the function body program of the function sleepButtonEvent (), the condition selection outside the doubly nested if statement refers to the variable activeSequence which is the active component data storage means 2 c to change the “tuning process” state. It is determined whether the owning sequence component is active or not, and the inner state if statement calls the isState () function, which is the state inquiry means 1c of this sequence component, so that the current state is "tuning process". It is determined whether it is in the state. As a result, the input of the “rest timer button input” event is known at the time the function is called, and the input event is “rest timer button input” and the current Is determined to be a "tuning process".

When the component switching condition is satisfied, three processes are required: activation of an action corresponding to the input event, switching of the active sequence component, and change of the internal state of the newly activated sequence component. In the function body program of the function sleepButtonEvent (), the function startSleepTimer () of the action output means 2e is called as activation of an action corresponding to the input of an event, and a sequence to be newly activated in the active component data storage means 2c as switching of active sequence components. By substituting the data representing the component and calling the setState () function using the pointer variable seq1Ptr, which is the component communication means 2d, to change the internal state of the newly activated sequence component, the state of the active sequence component is changed. Is set to the “Waiting timer wait” state.

If the component switching condition is not satisfied, the
Performs processing to input the event received by TvSwitcher to the currently active sequence component. For example, in the function powerButtonEvent (), it is determined that the component switching condition is not satisfied at the time this function is called, so the function body program implements only the process when the component switching condition is not satisfied. . However, since only the sequence component that realizes the component sequence specification of the above specification 5 accepts the "power button input" event, the event is transmitted to this sequence component only when this sequence component is active. Has become.

Next, the operation of the TV control system thus generated will be described.

The sequence components shown in FIGS. 15 and 16 and the joining components shown in FIG. 17 are realized as C ++ language classes, and when these are used, instances of these classes are generated. At this time, the initialization means 1g and 2f of each component implemented as the initialization function operate. Thereby, the sequence component Tv shown in FIG.
The sequence component TvSequence2 shown in FIG. 16 is initialized to a "power off" state, and the sequence component TvSequence2 shown in FIG. Also, in the joining component TvSwitcher, each sequence component is stored in a pointer variable which is the component communication means 2d.
By substituting the addresses of the instances of TvSequence1 and TvSequence2, a communication path between the joining component and each sequence component is secured, and the sequence component Tv is stored in the variable activeSequence that is the active component data storage means 2c.
Substitute the value "SEQ1" indicating that Sequence1 is active.

When the initialization processing as described above is completed, T
The V control system can receive the event. An external event is performed by calling each function as the event input means 2a. Hereinafter, the flow of processing after the event is called will be described assuming some cases.

First, the sequence component TvSequence
A description will be given of the flow of processing when the “power button input” event is input when 1 is active and in the “power OFF” state.

The input of the "power button input" event is performed by calling the function powerButtonEvent () of the joint component TvSwitcher. The function powerButtonEvent () is a joint component TvSwit to accept the "power button input" event
cher's event input means 2a. Function powerButtonE
When vent () is called, the operation corresponding to the “power button input” event is determined and executed by the event handling processing unit 2b. In this case, as described above, since the component switching condition is not satisfied when the event is input, only this event is transferred to the active sequence component. Since only the sequence component TvSequence1 receives the “power button input” event, the event handling process determines whether the sequence component TvSequence1 is currently active. When the sequence component TvSequence1 is active, the function powerButtonE which is the event input unit 1a that receives the “power button input” event of the sequence component TvSequence1
Call vent (). When the function powerButtonEvent () is called, the sequence component TvSequence1 refers to the variable state, which is the current state storage means 1e, in the event input means 1a, and determines whether or not the current state is the "power OFF" state. . In the case of the "power OFF" state, the function powerOn () which is the action output means 1f for executing the "power relay on" action is called. The above processing flow is shown in the event trace diagram of FIG.

Next, second, the sequence component TvSequence
A description will be given of the flow of processing when the "sleep timer button input" event is input when 1 is active and in the "tuning processing" state.

The input of the "sleep timer button input" event is performed by calling the function sleepButtonEvent () of the connection component TvSwitcher. The function SleepButtonEvent () is an event of the connection component TvSwitcher for receiving the "sleep timer button input" event. Input means 2a.
When the function sleepButtonEvent () is called, an operation corresponding to the “sleep timer button input” event is determined and executed by the event handling processing unit 2b. In this case, the component switching condition is determined first, but the component switching condition when the “sleep timer button input” event is input is “TvSequence1 is active and“ tuning process ”state”. It is. In order to determine the component switching condition, the joining component TvSwitcher first determines the variable activeSequence
To determine whether or not the sequence component TvSequence1 is active by determining whether or not this value is “SEQ1”. Furthermore, the sequence component TvSequ
When ence1 is active, in order to determine that the sequence component TvSequence1 is in the “tuning process” state, the sequence component TvSequence1 is communicated with the sequence component TvSequence1 via the pointer variable seq1Ptr which is the component communication means 2d. The function isState (), which is the state inquiry means 1b of the sequence component TvSequence1, is called with the value "TvSequence1 :: TUNING" indicating the "tuning process" state given as an argument. The sequence component TvSequence1 uses this function isS
In response to the call of tate (), a truth value indicating whether or not the value passed as the argument is equal to the current value of the current state storage means 1e is returned as the return value of the function. In response to this, when the state of the sequence component TvSequence1 is “tuning process”, the joining component TvSwitcher determines that the component switching condition is satisfied, and determines that the action corresponding to the “sleep timer button input” event is “O”. The execution of the “sleep timer start” action, the switching to the active sequence component TvSequence2, and the forced change of the state of the sequence component TvSequence2 to the “sleep timer wait” state are performed. The execution of the "sleep timer activation" action is performed by calling the function startSleepTimer () which is the corresponding action output means 2e. The switching of the active sequence component is performed by changing the value of the variable activeSequence, which is the active component data storage means 2c, to "SEQ2" which is a value indicating that TvSequence2 is active. In addition, forced change of status is performed by
A function set, which is the state specifying means 1b of the sequence component TvSequence2, via the pointer variable seq2Ptr which is the component communication means 2d for performing communication with TvSequence1, TvSequence2
This is performed by giving State () a value “TvSequence2 :: SLEEP_TIMER” representing the state of “waiting for a rest timer” as an argument. In the sequence component TvSequence2, when the function setState () is called, the value “TvSequence” passed as an argument to the variable state which is the current state storage means 1e.
By changing "2 :: SLEEP_TIMER", the state is changed to "waiting for a rest timer". The above processing flow is shown in the event trace diagram of FIG.

As described above, according to the first embodiment, when a sequence component TvSequence1 already exists, additional components TvSequence2 and TvSwitcher are newly created without changing the inside of the sequence component TvSequence1. A TV control system that realizes an extended operation specification as shown in FIG. 14 can be generated. This allows developers of TV control systems to use existing sequence components.
You don't need to understand the details inside TvSequece1,
Since the development can be advanced by grasping only the operation specifications described by the state transition diagram as shown in FIG. 13, a new TV control system can be efficiently developed.

Second Embodiment Next, another embodiment of the sequence control system shown in FIGS. 1 to 12 will be described with reference to FIGS. Here, a case will be described in which the sequence parts and the joint parts shown in FIGS. 10 to 12 are implemented not in C ++, which is an object-oriented language, but in C, which is a functional language.

The program shown in FIG. 20 is a sequence component for realizing the component sequence specification of the above specification 1 (see FIG. 4). In FIG. 20, the event input unit 1a corresponds to the functions Component_E1 () and Component_E2 ().
Input of events from outside is performed by calling these functions. The action output means 1f is a function Comp
It corresponds to onent_A1 () and Component_A2 (). Various actions such as outputting data to the output buffer and starting a timer are implemented inside these functions.
Here, detailed description is omitted. The current state store 1e is realized by the global variable Component_state. The global variable Component_state takes "Alpha" or "Beta" as a value, and when the respective value is taken, the current state of the sequence component Component is "α" or "β".
(See FIG. 4). The initializing means 1g includes an initialization function init
Implemented as Component (). This initialization function is called from the outside when using a sequence component, and changes the value of the global variable Component_state to “Alph
a), and sets the initial state of this sequence component to “α.” The state change / action output unit 1 d uses the function Compo
This is realized by the function body programs of nent_E1 () and Component_E2 (). Function Component_E1 (), Component_E2
() Finds a change to the next state based on the value of the current state every time a function call occurs, and rewrites the value when a state transition is required. State specifying means 1b is a function
Implemented by Component_setState (). This function realizes the change to the specified state by substituting the value given as an argument into the state. The state inquiry means 1c is realized by the function Component_isState (). This function determines whether the current state is the state given as an argument and returns the result.

The program shown in FIG. 21 is a sequence component for realizing the difference sequence specification (see FIG. 7) of the above specification 3. As shown in FIG. 21, the structure of this program is substantially the same as the structure of the program shown in FIG. 20, and a detailed description thereof will be omitted.

The program shown in FIG. 22 is a joining part for realizing the joining sequence specification (see FIG. 8) of the above specification 4. In FIG. 22, the event input means 2a has a function Sw
It corresponds to ithcer_E1 ()-Swithcer_E4 (). Input of events from outside is performed by calling these functions. Active parts data store 2c is a variable Swit
Implemented by cher_activeSequence. This variable takes “COMPONENT” or “COMPLEMENT” as a value, and indicates that either the sequence component Component or Complement is active when each value is taken. In this case, the component communication unit 2d is also used by each function as the event input unit 1a, the state designation unit 1b, and the state inquiry unit 1c of each sequence component. That is, since each function is defined as an external function in the C language, for example, the function Compone of the sequence component Component
net_isState () is a function of joining part Switcher Switcher_E3 ()
Can be called directly from.

The initialization means 2f includes an initialization function initSwitcher
(). The initialization function initSwitcher () is a variable Switcher_a which is the active component data storage means 2c.
Initialize the value of ctiveSequence to “COMPONENT”. Thereby, the active sequence component is initialized to Component.

The event correspondence processing means 2b is a function Switcher
_E3 () and Switcher_E4 () are implemented by function body programs. Judgment of component switching condition is Switcher_E
This is realized by two if statements inside 3 () and Switcher_E4 (). The process of executing the action when the component switching condition is satisfied, the process of changing the internal state of the sequence component to be switched, and the process of making the sequence component to be switched active and inactive the other are the functions Swit
In the main program of cher_E3 (), call the function Switcher_A3 (), call the function Componnent_setState (),
This is realized by rewriting the value of her_activeSequence to “COMPONENT”. In the function body program of the function Switcher_E4 (), the function Switcher_A4 () is called and the function
Call plement_setState (), variable Switcher_activeSeq
This is realized by rewriting the value of uence to “COMPLEMENT”. On the other hand, when the component switching condition is not satisfied,
Event_receiving function for the active sequence components inside Switcher_E1 () and Switcher_E2 ()
This is realized by calling E1 () and Complement_E1 (). The action output means 2e has the function Switcher_A3 (), S
witcher_A4 () is supported.

As described above, according to the second embodiment, a new sequence control system can be generated in the same manner as in the first embodiment by using the C language which is a functional language.
System development can be efficiently promoted by sub-systems (parts).

[0091]

As described above, according to the present invention, a new state transition operation system can be generated by reusing the state transition operation system, so that a new state transition operation system can be efficiently developed. can do. In addition, since the state transition parts and joint parts created in such a development process can be reused as sequence parts in the next new development process, the state transition operation system is made into a subsystem (parts). System development can proceed efficiently.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an embodiment of a state transition operation system (sequence control system) according to the present invention.

FIG. 2 is a block diagram showing details of a sequence component shown in FIG. 1;

FIG. 3 is a block diagram showing details of a joining component shown in FIG. 1;

FIG. 4 is a state transition diagram describing operation specifications of an existing sequence control system (sequence parts) to be reused.

FIG. 5 is a state transition diagram describing required operation specifications of the sequence control system.

FIG. 6 is a flowchart for explaining a generation method of the sequence control system shown in FIG. 1;

FIG. 7 is a state transition diagram corresponding to a difference sequence specification created based on the state transition diagrams of FIGS. 4 and 5;

FIG. 8 is a state transition diagram corresponding to the joining sequence specification created based on the state transition diagrams of FIGS. 4 and 5;

FIG. 9 is a flowchart for explaining processing contents in the joining component shown in FIGS. 1 and 3;

FIG. 10 is a view showing an example of a program for mounting a sequence component for realizing the operation specifications shown in FIG. 4;

FIG. 11 is a diagram showing an example of a program for mounting a sequence component for realizing the operation specifications shown in FIG. 7;

FIG. 12 is a view showing an example of a program for mounting a joint component realizing the operation specifications shown in FIG. 8;

FIG. 13 is a state transition diagram describing operation specifications of an existing TV control system (sequence parts) to be reused.

FIG. 14 is a state transition diagram describing required operation specifications of the TV control system.

FIG. 15 is a view showing an example of a program for mounting a sequence component for realizing the operation specifications shown in FIG. 13;

FIG. 16 is a diagram showing an example of a program for mounting a sequence component for realizing a difference sequence specification.

FIG. 17 is a diagram illustrating an example of a program for mounting a sequence component that realizes a joining sequence specification.

FIG. 18 is an event trace diagram for explaining an example of a processing flow in the TV control system.

FIG. 19 is an event trace diagram for explaining another example of the processing flow in the TV control system.

20 is a diagram showing another example of a program for mounting a sequence component that realizes the operation specifications shown in FIG. 4;

21 is a diagram showing another example of a program for mounting a sequence component that realizes the operation specifications shown in FIG. 7;

FIG. 22 is an exemplary view showing another example of a program for mounting a joint component realizing the operation specifications shown in FIG. 8;

FIG. 23 is a state transition diagram describing an example of an operation specification of a sequence control system (TV control system).

24 is a diagram showing an example of a sequence control program when the sequence control system shown in FIG. 23 is implemented in a programming language (C ++ language).

25 is a sequence control system (TV) shown in FIG.
FIG. 10 is a state transition diagram describing an example of an operation specification when a function of a “sleep timer” is added to the control system.

FIG. 26 is a diagram showing an example of a sequence control program for realizing the operation specifications shown in FIG. 25, which is created by changing the inside of the sequence control program shown in FIG. 24.

[Explanation of symbols]

 1 Sequence part (state transition part) 1a Event input means 1b State designation means 1c State inquiry means 1d State change / action activation means 1e Current state storage means 1f Action output means 1g Initialization means 2 Joint parts 2a Event input means 2b Event handling Processing means 2c Active component data storage means 2d Component communication means 2e Action output means 2f Initialization means

Claims (6)

[Claims] 1. A system comprising: at least two state transition parts for realizing a partial operation specification obtained by dividing an operation specification that can be expressed as a state transition diagram; and a joining part for connecting the state transition parts. The joining component, when an externally applied event does not involve switching of activation between the state transition components, distributes the event to any of the state transition components,
A state transition operation system, wherein when the event involves switching of activation between the state transition parts, the activation of each state transition part is switched, and the internal state of the state transition part to be switched to is changed. 2. Each of the state transition components includes an event input unit for receiving an externally applied event, a current state storage unit for holding a current internal state, and an event received by the event input unit. State changing means for changing an internal state held in the current state storing means, and state specifying means for changing an internal state held in the current state storing means in accordance with designation of an externally provided state Means, and a state inquiry means for returning a current internal state held in the current state storage means in response to an inquiry about a state given from outside, wherein the joining part is provided from outside. Event input means for receiving an event, and active component data for holding data representing active state transition components A storing unit, based on the event received by the event input unit and the data held in the active component data storing unit, distribution of an event, switching of activation of each of the state transition components, and a switching destination. And a component communication unit that communicates an event, an internal state change request, and an internal state inquiry request with each of the state transition components. 2. The state transition operation system according to claim 1, wherein: 3. An action activating means for activating an action associated with a state transition on the basis of an event received by the event input means, wherein each of the state transition components includes: an operation of the action activated by the action activating means; Further comprising: action output means for realizing the contents, wherein the joint part is an action output for realizing an operation content of an action started when the activation of each of the state transition parts is switched by the event handling processing means. 3. The state transition operation system according to claim 2, further comprising means. 4. Each of the state transition components further includes initialization means for initializing an internal state held in the current state storage means, and the joint component is held in the active component data storage means. 4. The state transition operation system according to claim 2, further comprising: initialization means for initializing data representing the state transition component being operated and for securing a communication path for performing communication by the component communication means. . 5. A first transition data list by extracting transition data including an event corresponding to a state transition, a transition source state, a transition destination state, and an action based on an operation specification of a first state transition component. And extracting the transition data including the event corresponding to the state transition, the state of the transition source, the state of the transition destination and the action based on the required operation specification of the state transition operation system, and performing the second transition Creating a data list; and when there is common transition data between the first transition data list and the second transition data list, the transition data included in the second transition data list Extracting transition data not including the transition source or transition destination state included in the first transition data list from there, and creating a third transition data list Creating a fourth transition data list by removing a portion of the second transition data list that overlaps with the first transition data list and the third transition data list; and the third transition Creating a second state transition part to be used with the first state transition part based on a data list; and the first state transition part and the second state based on the fourth transition data list Creating a joining part that connects the transition parts to each other. 6. At least two state transition parts for realizing a partial operation specification obtained by dividing an operation specification that can be expressed as a state transition diagram, and a joining part for connecting the state transition parts to each other, The joining component, when an externally applied event does not involve switching of activation between the state transition components, distributes the event to any of the state transition components,
A state transition operation system comprising: switching the activation of each state transition part when the event involves switching of activation between the state transition parts; and changing an internal state of the state transition part to be switched to. A computer-readable recording medium that has been recorded.