JPH06324967A - Message sequence diagram generating method - Google Patents

Abstract

PURPOSE:To easily perform the addition and change of a generating condition by selecting a constituting element whose condition can be changed by displaying a changeable condition candidate list. CONSTITUTION:A message sequence generating function 105 generates a message sequence to satisfy generating condition information 112 from state transition information 111, and generates message sequence information 113. A message sequence diagram display function 106 displays a message sequence diagram based on the message sequence information 113 on a display device 204. A message sequence customize function 107 provides the constituting element whose condition can be added or changed out of the constituting elements of a displayed message sequence diagram, and makes a user input a content desired to be added or changed, and performs the generation of the message sequence and display of a generated message sequence diagram based on the generating condition on which an inputted content is reflected.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a message sequence diagram generation method, and more particularly to a message sequence diagram generation method for mechanically generating a message sequence diagram relating to communication software in which design specifications are expressed in a state transition table.

[0002]

2. Description of the Related Art As a message sequence diagram generation method for mechanically creating a message sequence diagram related to communication software specifications, the following method is conventionally known.

(1) For example, Atsushi Ito et al., Mutual conversion of sequence charts and state transition diagrams for design and analysis of communication software specifications, IEICE Technical Research Report, Vol. 91, No. 93 (1991). June 20, 2013) Third
As described on page 7 to page 46, a method for automatically generating a message sequence based on a process-based maximum arrival transition sequence verification method from a plurality of state transition diagram specifications.

(2) For example, Kenji Mori et al., Reverse engineering in communication protocol design, 19
A method for automatically generating a message sequence based on reachability analysis from multiple state transition diagram specifications, as described in 91st IEICE Spring Conference Lecture Proceedings, Volume 3, Volume 98. The method of giving the constraint conditions that characterize the generated message sequence as the product, sum, and complement of partial message sequences corresponding to each state transition diagram.

(3) For example, as described in Japanese Patent Application No. 4-322430, for a plurality of state transition specifications, constraint conditions regarding states and events are input from a state transition table displayed on a dialogue terminal, and A method of automatically generating a message sequence that satisfies a constraint according to a specified priority.

[0006]

The above-mentioned prior art has the following problems as a message sequence diagram generation method. First, in order to generate a message sequence diagram from the state transition table, it is necessary to input in advance a generation condition for specifying the message sequence diagram to be generated. However, it is difficult for the user to input a complete combination of generation conditions for all message sequence diagrams that the user wants to generate. Usually, a method of obtaining a desired message sequence diagram by first generating a set of message sequence diagrams that satisfy some incomplete conditions and then changing and adding the conditions is adopted.

However, in the conventional technique, the generation condition is changed,
The user-friendliness was not taken into consideration, such as having to re-enter as a new condition even when wanting to add. Furthermore, the related art does not consider the relationship between the message sequence diagram initially generated and the message sequence diagram obtained by changing and adding the conditions, and the generated message sequence diagrams are only in sequential order. Since it is not saved, it is not easy for the user to search for the desired message sequence when performing confirmation or the like.

A first object of the present invention is to provide a method for generating a message sequence diagram, which can easily change and add generation conditions for a generated message sequence diagram.

A second object of the present invention is to provide a message sequence diagram generation method capable of efficiently storing and managing a generated message sequence diagram.

[0010]

In the information processing apparatus having a computer and a dialogue terminal, it is possible to specify the components of the message sequence diagram displayed on the dialogue terminal and change the condition. A changeable condition candidate list for each constituent element and selecting from the list, a means for changing the generation condition for the constituent element, and a means for generating a message sequence diagram conforming to the changed generation condition. , And a means for displaying a message sequence diagram based on the generated message sequence on an interactive terminal.

The second purpose is to store means for storing relational information between the message sequence diagram before the generation condition is changed and the message sequence diagram after the generation condition is changed, and both message sequence diagrams are stored from the stored relational information. It is achieved by having a means for calling and displaying.

[0012]

The user can interactively customize the message sequence diagram by designating the components of the message sequence diagram displayed on the interactive terminal and changing the generation conditions for the components. At this time,
For a component whose condition can be changed, a changeable condition candidate list is displayed, and the user can easily add or change the generation condition by selecting from the list.

Further, by storing the change history of the original message sequence diagram and the changed message sequence diagram as related information, a large number of message sequence diagrams are associated and stored and managed, and retrieved as necessary. Can be displayed.

[0014]

FIG. 2 is a diagram showing an example of hardware of a message sequence diagram generator to which the present invention is applied.
An input device 201 including a keyboard and a mouse for inputting commands from a user, a processing device 202 for performing internal processing of a computer, and a storage device 2 for storing data and programs.
03, display device 2 for displaying command execution results, stored data contents, messages to users, etc.
It consists of 04.

FIG. 1 is a diagram showing an example of a functional configuration of an apparatus that realizes the message sequence diagram generation method of the present invention. The execution control function 101 receives a command from the input device 201 and executes each function.

The state transition specification editing function 102 assists the user in newly creating and modifying the state transition specification,
The state transition information 111 is generated and corrected. The input / output relation information input function 103 displays the transmission / reception relation information of the message of the state transition specification described for each module, allows the user to input confirmation, correction, and addition of the relation information, and updates the state transition information 111. . The generation condition information input function 104 supports the user to input a condition for generating a message sequence diagram using the state transition information 111, and stores the generation condition information 112.

The message sequence generation function 105
A message sequence satisfying the generation condition information 112 is generated from the state transition information 111, and message sequence information 113 is generated. The message sequence diagram display function 106 displays a message sequence diagram based on the message sequence information 113 on the display device 204.
The message sequence customization function 107 presents the constituent elements of the displayed message sequence diagram in which conditions can be added or changed, prompts the user to input the contents to be added or changed, and generates the contents reflecting the input contents. The message sequence is generated based on the condition, and the generated message sequence diagram is displayed. The message sequence association function 108 retrieves the associated message sequence diagram for the message sequence diagram specified by the user and displays it.

The details of the procedure for customizing the generated message sequence diagram will be described below. However, the execution control function 101, the state transition specification editing function 10
2, details of realizing the input / output relation information input function 103, the generation condition information input function 104, the message sequence generation function 105, and the message sequence diagram display function 106 are described in, for example, Japanese Patent Application No. 4-322430. Therefore, the description is omitted.

From the state transition specification editing function 102 and the input / output relation information input function 103, state transition information 111 is generated and stored in the formats shown in FIGS.

Entry 3 of the state transition table list shown in FIG.
00 exists in correspondence with the state transition table, and the state transition table identifier 301 assigned by the device side, the state transition table name 302 input by the user, the pointer 303 to the state list, the pointer 304 to the event list 304, the state transition list Pointer 305, pointer 30 to the next state transition table entry
It consists of 6.

The state list entry 400 shown in FIG.
Is a status identifier 401 assigned by the device side, a status name 402 entered by the user, and a pointer to the next status entry.
It consists of 403.

Entry 50 of the event list shown in FIG.
0 is an event identifier 501 assigned by the device side, an event name 502 entered by the user, a message flag 503 indicating whether the event is a message received from another state transition table, or a sender when the event is a received message A state transition table identifier 504 and a pointer 505 to the next event entry.

Entry 60 of the state transition list shown in FIG.
0 is a state transition identifier 601 assigned by the device side, and an identifier 602 of the state entry 400 corresponding to the state transition process.
And an identifier 603 of the event entry 500, a condition identifier 604 representing a branch condition of the state transition process, a condition name 605, a pointer 606 to a process record for each condition,
It consists of a pointer 607 to the next state transition entry.

The processing record 700 shown in FIG. 7 comprises an identifier 701 of a transition destination state after the processing is completed, and a pointer 702 to an operation list included in the processing.

The operation list entry 800 shown in FIG. 8 exists for each operation, and the operation identifier 80 assigned by the device side.
1, an operation name 802 entered by the user, a message flag 803 indicating whether the operation is a message to be sent to another state transition table, a destination state transition table identifier 804 when the operation is a transmission message, a destination state It consists of an event identifier 805 corresponding to the transmission message in the transition table, a channel identifier 806 described later, and a pointer 807 to the next operation entry.

Channel list entry 90 shown in FIG.
0 is a channel identifier 901 assigned by the device side, a source state transition table identifier 902, a destination state transition table identifier 9
03, and a pointer 904 to the next channel entry.

From the generation condition information input function 104 of FIG. 1, generation condition information 112 for generating a message sequence diagram is generated and stored in the formats shown in FIGS. 10 to 14.

Entry 1 of the generation condition list shown in FIG.
000 exists corresponding to the state transition table, and the state transition table identifier 1001, the initial state identifier 1002, the initial event identifier 1003, the terminal state identifier 1004, the terminal event identifier 1005, and the pointer 1 to the passing state list are generated.
006, a pointer 1007 to the passing event list, a pointer 1008 to the non-passing state list, a pointer 1009 to the non-passing event list, a pointer 1010 to the passing state transition list, and a pointer 1011 to the next generation condition entry.

Entry 1 of the passage status list shown in FIG.
Reference numeral 100 includes a transit status identifier 1101 and a pointer 1102 to the next transit status list.

The entry 1200 of the passing event list shown in FIG. 12 comprises a passing event identifier 1201 and a pointer 1202 to the next passing event entry.

The non-passing status list entry 1300 shown in FIG. 13 comprises a non-passing status identifier 1301 and a pointer 1302 to the next non-passing status entry.

The non-passing event list entry 1400 shown in FIG. 14 comprises a non-passing event identifier 1401 and a pointer 1402 to the next non-passing event entry.

Message sequence generation function 10 of FIG.
5, message sequence information 113 is generated and stored in the formats shown in FIGS. Entry 1 of the sequence group list shown in FIG. 15 corresponding to the message sequence of the message sequence information 113.
Allocate 500. The entry 1500 of the sequence group list includes a sequence identifier 1501 (corresponding to a sequence number described later) assigned by the device side, a pointer 1502 to a sequence list described later, and a pointer 150 to a corresponding entry of the generation condition list 1000.
3, a change source sequence identifier 1504, a pointer 1501 to a change destination sequence identifier list to be described later, a pointer 1150 to a transition sequence change list to be described later, and a pointer 1507 to a next sequence group entry.

An entry 1600 of the sequence list shown in FIG. 16 is a global state identifier 1601, which will be described later.
It consists of a pointer 1602 to the next sequence entry.

An entry 1900 of the global state list shown in FIG. 19 is a global state identifier 1901 assigned on the device side, a pointer 1902 to a local state list corresponding to a target state transition table, and a channel state list corresponding to a channel. Pointer 1903, pointer 1 to the pass condition record for checking the pass condition in the generation conditions existing for each global state entry
904, transition source global state identifier 1905 indicating the global state before reaching the corresponding global state
Event occurrence state transition table identifier 190 that indicates the location of the event that occurred when the corresponding global state was reached
6, the state transition identifier 1907 of the state transition entry 600 executed when reaching the corresponding global state,
It consists of a pointer 1908 to the next global state entry.

The entry 2000 of the local state list shown in FIG. 20 comprises a state transition table identifier 2001, a local state identifier 2002 assigned by the device side, and a pointer 2003 to the next local state entry.

The entry 2100 of the channel status list shown in FIG. 21 is a channel identifier 21 assigned by the device side.
01, a channel status 2102 indicating the presence or absence of a message on the channel, a pointer 2103 to a message list indicating a message identifier when the channel status is “message present”, and a pointer 2 to the next channel status entry 2
It consists of 104.

The message list entry 2200 shown in FIG. 22 comprises a destination event identifier 2201 indicating the event identifier at the destination of the message and a pointer 2202 to the next message entry.

The pass condition record 2300 shown in FIG.
Consists of a pointer 2301 to the pass state check list and a pointer 2302 to the pass event check list.

The entry 2400 of the pass state check list shown in FIG. 24 corresponds to the pass state entry 1100 and corresponds to the state transition table identifier 2401 and the pass state identifier 240.
2, a passage flag 2403, and a pointer 2404 to the next passage state check entry.

The entry 2500 of the pass event check list shown in FIG. 25 is a pass event entry 1200.
Corresponding to the state transition table identifier 2501, passage event identifier 2502, passage flag 2503, and pointer 2504 to the next passage event check entry.

Message sequence diagram display function 1 of FIG.
06 displays the message sequence diagram based on the message sequence information 113 on the display device 204 in the format shown in FIG. In FIG. 27, there is a display screen 2700 corresponding to the generated message sequence, and the “previous figure” button 2
By operating 707 and the "next figure" button 2708, another message sequence diagram generated from the same generation condition can be displayed. "Customize"
The button 2710 and the “related” button 2709 are respectively the message sequence customization function 10 described later.
7 and the message sequence association function 108. Further, by operating the “end” button 2706, the screen display is ended.

The display screen is a sequence number 2701 which is an identifier in the entire generated message sequence of the displayed message sequence diagram, a message sequence diagram 2703, and a vertical and horizontal display showing the relative positions of the parts currently displayed on the screen. Scrollbars 2704 and 2
It consists of 705.

The message sequence diagram shows a state transition table name 2702, a state symbol and name 2711, a line symbol 2712 showing the time axis on which the state transition process is executed in correspondence with the state transition table, a received message or an internally generated event. Event symbol and name 2713 corresponding to
A branch condition symbol and name 2714, an action symbol and name 2715 corresponding to a specific action inside, and an action symbol and name 2716 corresponding to a transmission message.

The message sequence customizing function 107 of FIG. 1 uses the "customize" button 271 of FIG.
It is activated when 0 is selected. The subsequent procedure will be described with reference to the flowcharts shown in FIGS. 31 to 33 and FIGS. 28 to 30.

First, the change condition input block 31 shown in FIG.
Execute 01. Details are shown in FIG. Block 320
1, the change type selection screen 2800 shown in FIG. 28 is displayed on the interactive terminal, and the user changes the branch condition 280.
1, a message change 2802 or a message addition 2803 button is selected. The selection by the user is performed using a pointing device connected to the input device (the same applies hereinafter). In block 3202, the change type is acquired from the screen.

In block 3203, if the change branch condition is selected, the message sequence diagram 270.
3, the symbol 2901 representing the branch condition is selectable, and the changeable candidate list 2902 of branch conditions shown in FIG. 29 for the symbol designated by the user is represented by the symbol 290 representing the branch condition.
Display next to 1 (block 3204).

In block 3203, if message modification is selected, the message sequence diagram 27
A symbol 2714 representing a message is made selectable on 03, and a modifiable message candidate list 3003 shown in FIG. 30 is displayed beside the symbol 3001 representing a message for the symbol designated by the user (block 3205).

At block 3203, if message addition is selected, message sequence diagram 2703.
The position on the line symbol 2712 can be designated above, and the candidate list 3003 of the addable message shown in FIG. 30 is displayed beside the line symbol 3002 at the position designated by the user (block 3206).

At block 3207, if the user selects a change from the display list, the change is obtained.

Further, an entry 1800 of the transition sequence change list shown in FIG. 18 is created and the acquired data is stored. An entry 1800 of the transition sequence change list is a global state identifier 1801 corresponding to a change location, a change type flag 1802 indicating any one of change of branch condition, change of message, and addition of message. Identifier or event identifier) 1803
It consists of a pointer 1804 to the next transition sequence change entry. Finally, the generated transition sequence change entry is registered in the sequence group entry 1500.

Subsequently, the customization initialization block 3102 of FIG. 31 is executed. Details are shown in FIG. In block 3301, an entry 1600 of the sequence list is generated by excluding all the subsequent entries including the entry corresponding to the changed portion from the sequence list to be changed, and registers it in the sequence group entry 1500. In block 3302, a copy of the entry 1900 of the global state list corresponding to the changed portion is created, a global transition to be executed is obtained from the transition sequence change list 1800, applied to the above-mentioned global state, and the global state after the transition is sequenced. Set the search start status.

In block 3303, the generation condition entry 1000 of the source sequence group entry 1500 is changed.
Of the transition sequence change list 1800 is registered in the transit sequence change list 1800, the change type is message change, and the pre-change message is the initial message.
Delete this event if it is included in the passing / terminating event list. Further, the contents of the generation condition entry are stored in the generation condition information 112.

In block 3304, a duplicate entry of the global state for starting the sequence search is generated, a new global state identifier is assigned, and the original global state identifier is set in the transition source global state identifier, as shown in FIG. Add to the sequence generation candidate list.
The entry 2600 of the sequence generation candidate list in FIG.
Global state identifier 26 that is a candidate for sequence search
01, pointer 2 to the next sequence generation candidate entry
It consists of 602.

Subsequently, in the sequence search block 3103 of FIG. 31, the message sequence generation function 10
5 is used to generate a message sequence that matches the generation condition after the transition sequence is changed.

Subsequently, in block 3104 of FIG. 31, if the sequence is generated, proceed to block 3105. In the sequence association block 3105, the change source sequence identifier 1504 of the newly generated sequence group list 1500 is set, the change destination sequence identifier entry 1700 is created in the sequence group list 1500 to be changed, and the change destination sequence identifier 1701 is set. Register after setting.

The modification destination sequence identifier entry 1700 shown in FIG. 17 is a modification destination sequence identifier 1701 and a pointer 170 to the next modification destination sequence identifier entry.
It consists of two. Finally, in the sequence diagram display update block 3106 of FIG. 31, the message sequence diagram display function 106 is used to display the changed message sequence diagram, and the process ends. In block 3104 of FIG. 31, if the sequence is not generated, the sequence group entry 1500 is discarded and the process ends.

The message sequence associating function 108 of FIG. 1 is activated when the "association" button 2709 of FIG. 27 is selected. The subsequent procedure will be described with reference to the flowchart shown in FIG. 35 and FIG. 34.

First, in block 3501 of FIG. 35, the sequence group entry 1500 corresponding to the displayed message sequence diagram is searched to obtain a list of source sequence numbers (corresponding to sequence identifiers) and destination sequence numbers. At block 3502, the calling sequence selection screen 3400 shown in FIG. 34 is displayed. The display screen 3400 includes a label 3401 of a change source sequence number and a list 34 of a change destination sequence number.
02, an “execute” button 3403 for executing the selection process, and a “cancel” button 3404 for canceling the selection process. At block 3503, the sequence number to be called is acquired from the display screen 3400. Finally, in block 3504, the message sequence diagram display function 106 is utilized to display the called message sequence diagram 2703 and terminate.

[0060]

According to the present invention, the following can be achieved. That is, (1) the derived sequence and the exception sequence can be automatically generated by customizing the already generated message sequence diagram.

(2) The generation conditions can be easily added and changed on the display terminal.

(3) A similar message sequence diagram can be stored and managed using the generation condition as a key.

Therefore, it is possible to promptly show what the designer needs in the message sequence diagram which is easy to understand for the state transition table whose contents are difficult to grasp, so that the verification, review and maintenance of the specifications become easy. .

[Brief description of drawings]

FIG. 1 is a block diagram showing an example of an apparatus that implements a message sequence diagram generation method of the present invention.

FIG. 2 is a block diagram showing an example of hardware of a message sequence diagram generation device to which the present invention is applied.

FIG. 3 is an explanatory diagram showing an example of a state transition table list.

FIG. 4 is an explanatory diagram showing an example of a status list.

FIG. 5 is an explanatory diagram showing an example of an event list.

FIG. 6 is an explanatory diagram showing an example of a state transition list.

FIG. 7 is an explanatory diagram showing an example of a processing record.

FIG. 8 is an explanatory diagram showing an example of an operation list.

FIG. 9 is an explanatory diagram showing an example of a channel list.

FIG. 10 is an explanatory diagram showing an example of a generation condition list.

FIG. 11 is an explanatory diagram showing an example of a passing state list.

FIG. 12 is an explanatory diagram showing an example of a passing event list.

FIG. 13 is an explanatory diagram showing an example of a non-passing state list.

FIG. 14 is an explanatory diagram showing an example of a non-passing event list.

FIG. 15 is an explanatory diagram showing an example of a sequence group list.

FIG. 16 is an explanatory diagram showing an example of a sequence list.

FIG. 17 is an explanatory diagram showing an example of a change destination sequence identifier list.

FIG. 18 is an explanatory diagram showing an example of a transition sequence change list.

FIG. 19 is an explanatory diagram showing an example of a global status list.

FIG. 20 is an explanatory diagram showing an example of a local status list.

FIG. 21 is an explanatory diagram showing an example of a channel status list.

FIG. 22 is an explanatory diagram showing an example of a message list.

FIG. 23 is an explanatory diagram showing an example of a passage condition record.

FIG. 24 is an explanatory diagram showing an example of a passing state check list.

FIG. 25 is an explanatory diagram showing an example of a passing event check list.

FIG. 26 is an explanatory diagram showing an example of a sequence generation candidate list.

FIG. 27 is a block diagram showing an example of a sequence diagram display screen.

FIG. 28 is an explanatory diagram showing an example of a change type selection screen.

FIG. 29 is an explanatory diagram showing an example of display of a branch condition change candidate list.

FIG. 30 is an explanatory diagram showing an example of a message change / addition candidate list.

FIG. 31 is a flowchart outlining a message sequence customization function.

FIG. 32 is a flowchart of change condition input processing of the message sequence customization function.

FIG. 33 is a flowchart of customization initialization processing of the message sequence customization function.

FIG. 34 is an explanatory diagram showing an example of a calling sequence selection screen.

FIG. 35 is a flowchart outlining a message sequence association function.

[Explanation of symbols]

101 ... Execution control, 201 ... Input device, 204 ... Display device.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Haruo Sakurai Inventor Haruo Sakurai 5030 Totsuka-cho, Totsuka-ku, Yokohama, Kanagawa Software Development Division, Hitachi Ltd. (72) Kosuke Yata 5030 Totsuka-cho, Totsuka-ku, Yokohama Address Incorporated company Hitachi, Ltd. Software Development Headquarters (72) Inventor Takeki Fujinami 5030 Totsuka-cho, Totsuka-ku, Yokohama, Kanagawa Prefecture Incorporated Company Hitachi Ltd. Software Development Headquarters

Claims (2)

[Claims] 1. A method for generating a message sequence diagram expressing a time-series behavior of software from a state transition table describing a control structure of software by using an information processing device having a computer and a dialogue terminal. , Specifying a constituent element of the message sequence diagram displayed on the interactive terminal, displaying a list of modifiable generation condition candidates and selecting from the generation condition candidate list regarding the constituent element of which the generation condition can be changed. A message characterized by changing the generation condition relating to the constituent element, generating a message sequence conforming to the changed generation condition, and displaying a message sequence diagram based on the generated message sequence on an interactive terminal. Sequence diagram generation method. 2. The message sequence diagram conforming to the changed generation condition according to claim 1, is displayed on the interactive terminal, and the relationship information between the message sequence diagram before the change and the message sequence diagram after the change is displayed. A message sequence diagram generation method for storing and recalling and displaying both message sequence diagrams from the stored relationship information.