JPH08320856A - Dynamic model simulation device - Google Patents

Abstract

PURPOSE: To provide the simulation device for confirming the operation of a dynamic model which is one of object-oriented software design models and consists of a state transition machine and a participation object. CONSTITUTION: This device has a GUI part 100 having a function for interchanging information with users, a state transition administration part 200 which inputs an execution start instruction from the GUI part 100 to administer the state transition machine as a 1st constituent element of the dynamic model and finds a message to be executed on the basis of its internally administered state, an object administration part 300 which administers an object as a 2nd constituent element of the dynamic model and inputs the operated object name present in the message to be executed from the state administration part 200 to take out a method to be executed, and a method execution part 400 which inputs the method from the object administration part 300 and executes the method.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a simulation apparatus for confirming the operation of a dynamic model which is one of the design models of object-oriented software and is composed of a state transition machine and participating objects.

[0002]

2. Description of the Related Art A conventional technique will be described with reference to the drawings.

When simulating a dynamic model as shown in FIG. 10, a transition relation management table as shown in FIG. 13 is used. FIG. 13 shows an example of the dynamic model of FIG. Corresponding to each state name, there is a transition relationship that allows transition from the corresponding state. The transition relation consists of the label added to the arc of the dynamic model and the state name of the transition destination. In FIG. 10, the state Q1 indicated by the black circle is the initial state, and the double circle is the final state.

Next, the operation will be described with reference to the flowchart of FIG. When a simulation start instruction is given from the GUI unit 500 (step 710), the overall control 510 searches the state management unit 530 for an appropriate state, and sets an initial state in the current state holding unit 520 (step 711). In the example shown in FIGS. 10 and 13, Q
1 is set as the initial state. A test is performed as to whether or not this state is the end state (step 712). If it is the end state, the overall control 510 notifies the GUI unit 500 of the end of the simulation (step 717). If it is not the end state, the transition relation management unit 540 obtains the transition relation corresponding to the above state (step 713). Actually, the transition relation management unit 540 acquires the transition relation corresponding to the above state from the transition relation management table of FIG.
Next, the overall control 510 obtains a transition label from the acquired transition relation (step 714). When the transition relation is unique, the label of the transition relation is selected. If there are a plurality of transition relationships, the label is determined by inquiring the user through the GUI unit 500. Overall control 5
10 acquires the transition destination state name corresponding to the selected label, notifies the current state holding unit 520 of this state, and sets it (step 715). The overall control 510 is the GUI unit 50
The state change to 0 is notified and the display content is updated (step 716). Further, the process returns to step 712 to continue the simulation.

[0005]

As described above, in the conventional technique, the details of the label cannot be selected, so that there is a problem in that the simulation considering the participating objects embedded in the label of the dynamic model cannot be performed. It was That is, the conventional method has a problem that only a part of the function of the dynamic model composed of the state transition machine can be simulated.

An object of the present invention is to provide a simulation device for confirming the operation of a dynamic model which is one of the design models of object oriented software and is composed of a state transition machine and participating objects. .

[0007]

According to the present invention, a GUI unit 100 having a function of exchanging information with a user and the GUI unit for managing and executing a state transition machine which is a first component of a dynamic model are provided. State transition management unit 200 having a function of requesting a message to be executed based on a state internally managed by inputting an execution start instruction from the above, and managing the object that is the second component of the dynamic model An object management unit 300 having a function of inputting an operation target object name existing in a message to be executed from the transition management unit and extracting a method to be executed, and a method from the object management unit to execute the method It has a method execution unit 400 having a function.

[0008]

Next, the present invention will be described with reference to the drawings.

When simulating a dynamic model as shown in FIG. 10, a transition relation management table as shown in FIG. 12 is used. FIG. 12 shows an example of the dynamic model of FIG. Corresponding to each state name, there is a transition relationship that allows transition from the corresponding state. The transition relation is expressed by dividing the label added to the arc of the dynamic model into the message part and the condition part, and at the same time consists of the transition destination state name. In addition, an example of definition of a participating object in the dynamic model of FIGS. 11 and 10 is shown. It is the definition of the object referred to as a in the description of the dynamic model of FIG. It consists of three box descriptions, the first box is object a
Is composed of two internal variables index and data. The second box is end? Shows the behavior of the object a when the message is received, and the third box shows the behavior for the message next.

The dynamic model simulation apparatus of the present invention will be described with reference to FIGS. 1 to 5.

The dynamic model simulation apparatus of the present invention is shown in the block diagram of FIG. In this embodiment, the GUI
It is composed of a unit 100, a state transition management unit 200, an object management unit 300, and a method execution unit 400.

The GUI unit 100 has a function of exchanging information with the user. The state transition management unit 200 inputs the execution start instruction from the GUI unit 100 in order to manage and execute the state transition machine that is the first component of the dynamic model, and executes it based on the state internally managed. It has the function of requesting an appropriate message. The object management unit 300 manages the object that is the second component of the dynamic model, inputs the operation target object name existing in the message to be executed from the state transition management unit 200, and extracts the method to be executed. Have a function. Method execution unit 40
0 has a function of inputting a method from the object management unit 300 and executing the method.

FIG. 2 shows the state transition management unit 200 shown in FIG.
2 shows a detailed block diagram of FIG.

The state transition management unit 200 includes an overall control unit 21.
0, the state management unit 220, the current state holding unit 230,
It is composed of a transition relationship management unit 240 and a message interpretation unit 250.

The overall control unit 210 performs overall control to determine whether or not the processing is completed. The state management unit 220 manages a plurality of states that are elements of the state transition machine that is the first component of the dynamic model. In the example of the dynamic model shown in FIGS. 10 and 12, Q1, Q2 and Q3 are held. The current state holding unit 230 has a function of holding only the current state from the plurality of states, inputting an instruction from the overall control unit, and outputting the current state. The transition relation management unit 240 holds the transition relations related to the plurality of states, inputs the current state from the current state holding unit, and obtains the next state. That is, holding the transition relation management table shown in FIG.
Obtain the next state from the transition destination state name corresponding to the current state in the transition relationship. The message interpreting unit 250 has a function of inputting the transition relation corresponding to the current state from the transition relation managing unit and interpreting the message unit in the transition relation.

FIG. 3 shows the object management unit 3 shown in FIG.
00 shows a detailed block diagram of 00.

The object management unit 300 includes an object management environment unit 310 and an object reading unit 320.
And an object writing unit 330, a method management unit 340, and a method providing unit 350.

The object management environment unit 310 manages the correspondence between the object name and the object entity, and inputs the object name from the object reading unit 320 and the object writing unit 330. The object reading unit 320 inputs the object name from the state transition management unit 200 and accepts an object reading request. The object writing unit 330 inputs the object name from the method executing unit 400 and receives an object writing request. The method management unit 340 has a function of managing the method of each object and obtaining the method corresponding to the object entity obtained from the object management environment unit 310 according to the input from the object reading unit 320. The object entity may be held in the object management environment unit 310, or from the outside, the object writing unit 330.
You may enter by. The method providing unit 350 has a function of providing the obtained method to the method executing unit 400.

FIG. 4 shows the transition relationship management unit 240 shown in FIG.
2 shows a detailed block diagram of FIG.

The transition relation management unit 240 comprises a transition relation evaluation control unit 241, a transition relation extraction unit 242, a condition evaluation unit 243, and a return value reference unit 244.

The transition relation evaluation control unit 241 inputs the current state from the present state holding unit and controls the processing process. The transition relation extraction unit 242 has a function of managing states and transition relations related to the states, and extracts transition relations related to the states input from the transition relation evaluation unit. Condition evaluation unit 24
3 evaluates the condition of the transition relation input from the transition relation extracting unit. The return value reference unit 244 refers to the return value required in the condition evaluation process and outputs it to the condition evaluation unit.

FIG. 5 shows the method execution unit 400 shown in FIG.
2 shows a detailed block diagram of FIG.

The method execution unit 400 includes a method evaluation unit 410, a method reception unit 420, and a precondition evaluation unit 4.
30, a post-condition evaluation unit 440, an object access unit 450, and a return value management unit 460.

The method evaluation section 410 is a method receiving section 4.
The method from 20 is accepted as an input and the overall execution control is performed. The method receiving unit 420 receives the method from the object management unit as an input. The precondition evaluation unit 430 evaluates the precondition of the input method from the method evaluation control unit. Precondition evaluation unit 440
Evaluates the precondition of the input method from the method evaluation control unit. The object access unit 450 has a function of obtaining the value of the object referred to by the method input from the precondition evaluation unit and the postcondition evaluation unit. The return value management unit 460 manages the return value determined by the post-condition evaluation unit.

Next, the operation will be described with reference to the flowchart of FIG. When a simulation start instruction is given from the GUI unit 100 (step 610), the overall control unit 210 searches the state management unit 220 for the state to be obtained and sets the initial state in the current state holding unit 230 (step 611). ). Here, the transition relationship management unit 240 manages a transition relationship management table that is a correspondence table between states and transition relationships as shown in FIG. More detailed block diagram in FIG.
May be managed by. Usually, the initial state is known at the start of the simulation.
The corresponding state may be given from the I section 100.
In the example shown in FIGS. 10 and 12, Q1 is set as the initial state.

The overall control unit 210 tests whether this state is the end state (step 612). FIG.
When referring to the transition relation table of No. 2, there is a description of "end state" as the state name of the transition destination. In this case, the overall control unit 210 can perform the test of the end state. If the state set in the current state holding unit is the end state, the overall control unit 210 notifies the GUI unit 100 of the end of the simulation (step 624). If it is not the end state, the transition relation management unit 240 obtains the transition relation corresponding to the current state through the current state holding unit 230 (step 613). In this step, the transition relation evaluation control unit 2
Reference numeral 41 uses a table search function, which is one method of realizing the transition relation extraction unit 242, to retrieve the transition relation corresponding to the current state from the transition relation management table of FIG.
Here, this state is currently held by the state holding unit 230 and is an input to the transition relation management unit 240. More specifically, in FIG. 4 which is a block diagram, it may be considered as an input of the transition relation evaluation control unit 241. .

Next, the transition relation evaluation control section 241 extracts the condition section from the acquired transition relation, and evaluates the condition section using the condition evaluation section 243 (step 614). If the description of the conditional part is [true], it is understood that the conditional part is satisfied immediately. However, if there is a variable reference ret in the description of the condition part, the condition part must be evaluated by using the return value reference part 244 to obtain the value of ret. Therefore, the condition evaluation unit 243 tests whether or not there is a transition relationship in which the condition unit is satisfied (step 615). If there is no transition relation that satisfies the condition part, the procedure goes to step 624.

If there is a transition relation that has been established, the transition relation evaluation control unit 241 acquires the corresponding transition relation message unit and passes it to the message interpretation unit 250 (step 61).
6). The message interpreting unit 250 cuts out an object serving as a receiver from the message unit (step 61).
7). In the example of the first transition relationship in FIG. 12, a is a receiver object. The object management unit 300, which has been passed the object a of the receiver, obtains the substance of the object from the object management environment 310 via the object reading unit 320, and the method management unit 340 related to this object substance sends the above message to the message. Acquire a method to be executed (step 61)
3). In the above example, the message is a end? Is the end method of the object a? Method definition. An example of this is shown in FIG. In the above method definition, true described after "assumes:" indicates a precondition part. In addition, the expression using if described after "ensures:" indicates the postconditional part.

The method providing section 350 extracts the method, and the method receiving section 42 in the method executing section 400.
It outputs to 0 and transfers control to the method evaluation control unit 410.
The method evaluation control unit 410 receives the method by the method receiving unit 420, and causes the precondition evaluation unit 430 to evaluate the precondition (step 619). The contents described after the assumes: are evaluated as described above. When it is described as true as shown in the example of FIG. 11, the precondition is unconditionally satisfied. A test is made as to whether the precondition is satisfied (step 620). If the precondition is not satisfied, there is a possibility that the selected transition relationship is inconsistent, and thus the process proceeds to step 624. When it is satisfied, the post-condition evaluation unit 440 is requested to process the post-condition of the corresponding method (step 621). en
Evaluating the expression that follows after:
When the value of ndex is smaller than the value of length (data), the variable ret is set to no, and in the opposite case, the variable r is set.
It indicates that yes is set in et. In order to perform this processing, since index and data are internal variables of the object a, it is necessary to use the object access unit 450 to obtain a value.

As shown in FIG. 11, an ensu method is invoked in the case of the next message of FIG.
The postconditional part described after res: is index '
The process when the value of the state variable index of the object a is updated in the form of = index + 1 will be described.

First, the object access unit 450
Gives the object a and the state variable name index before update as an input to the object reading section 320 in the object management section 300, and retrieves a necessary value from the object management environment section 310. Further, the object access unit 450 updates the object entity managed by the object management environment unit 310 by supplying the object writing unit 330 with the object a, the state variable name index to be updated, and its value, index + 1. To do.

Since the variable ret is a special variable representing a return value, it needs to be managed by the return value management unit 460. In particular, the return value management unit 460 uses the return value reference unit 244.
By outputting the return value to, the value of the variable ret can be accessed by exchanging information at the level of the state transition management unit 200 and the method execution unit 400.

Next, the method evaluation control unit 410, that is, the method execution unit 400, can obtain the transition destination state of the corresponding transition relation from the transition relation management table managed by the state relation unit 220, and the overall control unit 210. Notifies the current state holding unit 230 of the transition destination state and sets it (step 622). The overall control unit 210 is the GUI unit 50.
The state change to 0 is notified and the display content is updated (step 623). Furthermore, the simulation is continued by returning to step 612. At this time, the current state holding unit 2
30 holds the transition destination state obtained in step 622, and the overall control unit 210 tests whether this state is the end state (step 612).

When a plurality of transition relation condition parts are satisfied in step 614, it is possible to add an operation of making an inquiry to the GUI unit 100 and narrowing down to the most appropriate transition relation. Is clear. In addition, when creating a dynamic model, it may be possible to promise in advance not to allow such nondeterminism that a plurality of transition relationships can fire at the same time.

[0035]

As described above, according to the present invention, the operation of a dynamic model, which is one of the design models of object-oriented software and is composed of a state transition machine and participating objects, can be confirmed. A simulation device can be provided.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of the present invention.

FIG. 2 is a diagram showing a configuration of a state transition management unit of the present invention.

FIG. 3 is a diagram showing a configuration of an object management unit of the present invention.

FIG. 4 is a diagram showing a configuration of a transition relationship management unit of the present invention.

FIG. 5 is a diagram showing a configuration of a method execution unit of the present invention.

FIG. 6 is a flowchart illustrating an embodiment of the present invention.

FIG. 7 is a flowchart illustrating an embodiment of the present invention.

FIG. 8 is a diagram illustrating a conventional example.

FIG. 9 is a flowchart illustrating a conventional example.

FIG. 10 is a diagram showing a dynamic model for explaining the content of the present invention.

FIG. 11 is a diagram showing a participating object definition used in a dynamic model for explaining the content of the present invention.

FIG. 12 is a diagram showing a transition relationship management table for explaining the content of the present invention.

FIG. 13 is a diagram showing a transition relationship management table for explaining the contents of a conventional example.

[Explanation of symbols]

 100 GUI unit 200 State transition management unit 210 Overall control unit 220 State management unit 230 Current state holding unit 240 Transition relation management unit 241 Transition relation evaluation control unit 242 Transition relation extraction unit 243 Condition evaluation unit 244 Return value reference unit 250 Message interpretation unit 300 object management unit 310 object management environment unit 320 object reading unit 330 object writing unit 340 method management unit 350 method providing unit 400 method executing unit 410 method evaluation control unit 420 method receiving unit 430 pre-condition evaluation unit 440 post-condition evaluation unit 450 Object access part 460 Return value management part

Claims (5)

[Claims] 1. A GUI unit having a function of exchanging information with a user and an execution start instruction from the GUI unit for managing and executing a state transition machine which is a first component of a dynamic model. In the message to be executed from the state transition management unit that manages the object that is the second component of the dynamic model and has the function to obtain the message to be executed based on the state managed internally It is characterized by having an object management unit having a function of inputting an existing operation target object name and extracting a method to be executed, and a method execution unit having a function of inputting a method from the object management unit and executing the method. Dynamic model simulation device. 2. The state transition management section receives an execution start instruction from the GUI section and judges whether or not the processing is completed. A state management unit that manages a plurality of states that are elements of the state transition machine, and a function that holds only the current state from the plurality of states and outputs the current state according to an instruction from the overall control unit. A current state holding unit, a transition relation management unit that holds the transition relations related to the plurality of states, inputs the current state from the current state holding unit, and obtains the next state; A message interpreting unit that inputs a transition relation corresponding to the current state and interprets the message unit of the transition relation, and has a function of requesting a message to be executed by inputting an execution start instruction from the GUI unit. Dynamic model simulation apparatus according to claim 1, symptoms. 3. The object management unit receives an object read request by inputting an object name from the state transition management unit, and an object receiving an object write request by inputting an object name from the method execution unit. The writing section,
The object management environment unit that manages the correspondence relationship between the object name and the object entity, inputs the object name from the object reading unit and the object writing unit, and outputs the corresponding object entity, and manages the method of each object, A method management unit having a function of requesting a method corresponding to an object entity obtained from the object management environment unit in accordance with an input from the object reading unit, and a method providing unit providing the method execution unit with the requested method. The dynamic model simulation device according to claim 1, wherein: 4. The transition relation management unit has a transition relation evaluation control unit for inputting a current state from the current state holding unit and controlling a processing process, and a function for managing a state and a transition relation related thereto. A transition relation fetching unit that fetches a transition relation related to the state input from the transition relation evaluation unit, a condition evaluation unit that performs condition evaluation of the transition relation input from the transition relation fetching unit, and a necessary in the condition evaluation process. The dynamic model simulation device according to claim 2, further comprising: a return value reference unit that refers to the return value and outputs the condition value to the condition evaluation unit. 5. The method execution unit, a method reception unit that receives a method from the object management unit as an input, a method evaluation control unit that receives the method from the method reception unit as an input, and controls the overall execution, A precondition evaluation unit that evaluates the preconditions of the input method from the method evaluation control unit, a postcondition evaluation unit that evaluates the postconditions of the input method from the method evaluation control unit, and the precondition evaluation unit and postconditions. An object access unit having a function of obtaining a value of an object referred to by a method input from the evaluation unit, and a return value management unit managing the return value determined by the post-condition evaluation unit. Item 1. The dynamic model simulation device according to Item 1.