JPH06348482A - Object directional analysis/design supporting system - Google Patents

Abstract

(57) [Summary] [Purpose] Providing an object-oriented analysis and design support system that can convert various diagrams that describe the functions of objects into high-level Petri nets and perform consistency checking and verification. [Structure] A token generation unit 3 that converts the specifications of each object in the object diagram 2 into a token, and a class that replaces each object in the object communication diagram 4 with a transition and replaces an event with a place to generate a high-level Petri net. Dynamic specification converter 5
And a state diagram 6 in place, an event guard condition in a transition, an event in a transition name, a state transition in an arc, an action at transition in an arc function, and a dynamic specification conversion unit 7 in a class, The transition of the petri net of the functional specification conversion unit 9 and the dynamic specification conversion unit between classes 5 that replaces the bubble in the data flow diagram 8 with the transition and the flow into the place and generates the high level petri net is replaced with the high level petri net. Petri net refinement unit 10 to replace with net
And

Description

Detailed Description of the Invention

[0001]

[Industrial application] The present invention relates to an object-oriented analysis / design support system that applies a high-level Petri net to software analysis and design based on an object-oriented analysis / design methodology.

[0002]

The following are references relating to object-oriented design methodologies and high level Petri nets in the present invention.

(1) Rambo and others (Translated by Eiichi Hanyuda):
Object-Oriented Methodology OMT Toppan Co., Ltd., Published in 1992 (2) Hisao Shiizuka: Case Study Petri Net-From Basics to Computer Tools Corona Publishing Co., Ltd., 1992 In object-oriented CASE tools, when a class or object receives an event A state diagram that uses a state transition diagram, etc., is provided to describe the dynamic behavior in.
However, since this state diagram is a diagram description format based on informal semantics, formal consistency check and verification cannot be performed. Furthermore, an object diagram is used to describe static aspects of the design target such as hierarchical relationships and aggregation relationships of classes and objects, and aspects of dynamic behavior between classes such as exchange of events or messages between classes. An object communication diagram is provided by the object-oriented CASE tool, and a data flow diagram is provided by the object-oriented CASE tool to describe the logic of processing in the class, that is, the detailed flow of processing. Since the above diagrams are based on different informal semantics, the overall consistency of whether or not there is consistency between the above diagrams that describe the same design object from different aspects. It's hard to see.

[0004]

In the above object-oriented analysis / design methodology, an object diagram for describing static specifications of objects, an object communication diagram for describing interactions between objects, and a dynamic specification of objects are described. Places and bars that are represented by nodes in circles in the form of representations in which a number of formal verification and simulation techniques are established from the state diagram to be created and the data flow diagram that describes the functions realized by the object. Alternatively, a token having a net structure composed of two types of transition nodes and arcs represented by rectangular nodes, and a data structure for moving within a place on the net structure,
Introduce a system for centralized conversion to a high-level Petri net composed of. In addition, this system provides an object-oriented analysis and design support system that enables high-level Petri nets to be checked and verified as a whole with the formal verification and simulation technologies provided. provide.

[0005]

[Means for Solving the Problem] A means for generating a token in a high-level Petri net from an object diagram, a means for generating a high-level Petri net corresponding to a dynamic specification between classes from an object communication diagram, and a state. A means to generate a high-level petri net corresponding to a dynamic specification in a class from a diagram, a means to generate a high-level petri net that describes the function of each object from a data flow diagram, and the above-mentioned means Generating high level petri nets that combine the tokens with the high level petri nets.

[0006]

Operation: A high-level Petri net is generated and fused from each diagram in the conventional object-oriented analysis / design methodology. First, the attribute definitions of the objects described in the object diagram are aggregated to define the token type in the high-level Petri net. And
Each object in the object communication diagram is replaced with a transition in the high-level Petri net, and an event between the objects is replaced with a place to generate a net structure of the high-level Petri net. Furthermore, the behavior in the class represented by the state diagram is converted into a high-level Petri net net structure by replacing states with places and events with transitions. Furthermore, the function represented by a bubble, which is a node in the data flow diagram, is replaced with a transition, and the flow of data represented by an arc is replaced with a place, and converted into a net structure of a high-level Petri net.

Then, the net structure of the high-level Petri net converted from the state diagram is embedded in the transition part of the net structure of the high-level Petri net converted from the object communication diagram. Furthermore, next, to the transition part of the net structure of the high-level Petri net to convert from the state diagram, to the high-level level to convert from the data flow diagram
Embed and fuse the net structure of Petri nets. Then, by arranging the tokens in the place representing the initial state, each diagram is fused, and a high-level Petri net capable of formal verification that is expressed collectively is generated.

[0008]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

Referring to FIG. 1 showing the configuration of an embodiment of the present invention, an object-oriented analysis / design support system 1
Is a token generation unit 3 that converts the specifications of each object or class consisting of the attribute definitions described in the object diagram 2 into tokens of the same type, and the transition of each object in the object communication diagram 4 and the event between the objects. A high-level Petri net net structure is generated by substituting a place, and the inter-class dynamic specification conversion unit 5 that assigns a message type to the place and the state of each class described in the state diagram 6 Places on high-level Petri nets, event card conditions as transitions, events as transition names,
In-class dynamic specification conversion unit 7 that generates a net structure in a high-level Petri net that converts state transitions into arcs and actions executed during transitions into arc functions, and the functions represented by a data flow diagram 8 Is a transition, and a flow is a place. A functional specification conversion unit 9 that generates a high-level Petri net that replaces
And the high level obtained from the interclass dynamic specification conversion unit 5.
The transition of the net structure of the Petri net is refined by replacing it with the net structure of the high-level Petri net that corresponds to the internal behavior of the transition generated in the in-class dynamic specification conversion unit 7, The transition function appearing in the high-level Petri net generated in the specification conversion unit 7 is refined by the net structure of the high-level Petri net corresponding to this function generated in the functional specification conversion unit 9 to generate a token. And a Petri net refinement unit 11 for converting the token obtained by the unit 3 into a high level Petri net 10.

Next, this embodiment will be described in detail. Referring to FIG. 2 which illustrates an object diagram 2 which is a token generated by the token generation unit 3 and an input of the talk generation unit 3, the object diagram 2
By defining the type of each attribute as it is as a type in the set from the object diagram (Fig. 2 (a)) in which all the attributes described in 1 are set as a set, the type of the same type as the specification of the object itself is defined. Convert to a token (Fig. 2 (b)).

Referring now to FIG. 3, which illustrates the transformation of the object communication diagram 4 into a high level Petri net, the object communication diagram (FIG.
The object described in (a)) is a transition in the high-level Petri net (FIG. 3B), the arc corresponding to the exchange of messages is an arc connecting the transition and the place, or the place and the place and the transition. Are converted into arcs that connect to each other, and for the place corresponding to the message having data, the type of token flowing as data is added to the place.

Next, referring to FIG. 4 exemplifying conversion of a state transition in a class from a state diagram into a net structure of a high-level Petri net, an action or activity such as event transmission is expressed by an arc. From the state transition diagram or a subset of the state chart (FIG. 4A), etc., the high-level Petri net (FIG.
(B)) is generated. Further, a high level Petri net of the state diagram for the "processing machine" illustrated in FIG. 3B is illustrated in FIG. The conversion procedure will be described with reference to FIG. 5 showing a conversion procedure from a state diagram to a high level Petri net. First, a state of the state diagram is defined as a place. If there is a state name, the state name is used as the place name (step 1). Next, the transition of the state diagram is defined as a transition (step 2). Furthermore, in the case of a transition having a guard condition, the guard condition is defined as a predicate in the transition (step 2.1). When the transition uses information other than the object targeted by the state diagram, the arc labeled by the type corresponding to the information is set as the input arc to the corresponding transition (step 2.2). Explaining with the example of FIG. 4, the arc labeled with “V” input to the “fill confirmation” transition corresponds to the above-mentioned input arc.

Furthermore, when an event is sent as an action in the transition, the "confirm release" transition of FIG. 4B adds an output arc labeled with the type of event data to the transition (step 2. 3). Explaining with the example of FIG. 4B, the arc labeled by the "fill confirmation" output from the "release confirmation" transition corresponds to the above-mentioned output arc.

Next, the action at each transition is pasted as the arc function of the output arc of the transition (step 3). Explaining with the example of FIG. 4B, the addition processing in “filling completion” corresponds to this arc function. Then, the type of this object is given to the arc and labeled with the type (step 4). The above procedure transforms the state diagram into a high level Petri net.

Further, referring to FIG. 6 exemplifying the conversion from the data flow diagram to the high-level Petri net, the function represented by the data flow diagram (FIG. 6 (a)) is used as a transition. Each place is replaced to generate a high-level Petri net (Fig. 6 (b)), the token type flowing through the flow is given to the place, and the same type of bubble input flow type is used as the transition input arc. Give.
In addition, when the control flow exists, FIG.
In addition to the place that represents the control flow itself, a place that represents an external event that triggers the control flow is added to the control flow indicated by the dashed line labeled "ack" in The input place to the transition corresponding to the bubble (the “storage process” transition illustrated in FIG. 6) (the place labeled ack in FIG. 6B).

Furthermore, when a data store exists, a bidirectional arc is formed between the place representing the data store and the transition corresponding to the access or update, regardless of whether the data store is accessed or updated. Haru.

The Petri net refining unit 11 shown in FIG.
Token generated by the conversion of the token generation unit 3 illustrated in FIG. 2B and the net of the high-level net generated by the conversion of the interclass dynamic specification conversion unit 5 illustrated in FIG. The structure (FIG. 3B), the net structure of the high-level net generated by the conversion of the in-class dynamic specification conversion unit 3 illustrated in FIG. 4 (FIG. 6B), and the example illustrated in FIG. FIG. 8 exemplifies a high-level net fused to one generated by fusing the net structure of the high-level net corresponding to the state diagram of the “machining machine” in FIG. 3A. To do. The transition of the net structure of the high-level Petri net, which is converted from the object communication diagram illustrated in FIG. 3, is converted into “machine” and “tank”, and the state diagram is converted, which is equivalent to the “machine” illustrated in FIG. 7. The high-level Petri net net structure and the high-level Petri net net structure corresponding to the “tank” illustrated in FIG. 4 are embedded, respectively, and further converted from the embedded state diagram. The net structure of the high-level Petri net illustrated in FIG. 6, which is converted from the data flow diagram, is embedded and fused in the transition “processing step 2” of the net structure of the high-level Petri net “processing machine” illustrated. The "tank" illustrated in FIG. 2 is placed in the "empty" state which represents the initial state of the "tank" in FIG. By placing a token of "class,
Generates a high-level Petri net that can be formalized and represents each diagram together.

[0018]

According to the conventional object-oriented analysis / design methodology, since a plurality of diagrams based on informal semantics are provided, formal consistency check and verification can be performed on the description contents of each diagram. Can not. Furthermore, it is difficult to confirm the overall consistency such as whether consistency is established between the above diagrams that describe the same design object from different aspects. However, according to the present invention, by integrating all the diagrams and converting them into one high-level Petri net, many formal verification techniques and simulation techniques provided for the high-level Petri net are provided. Can be used for overall consistency and consistency checking and verification. Therefore, object-oriented analysis
It is possible to verify the correctness of specifications in the design process and find bugs in specifications during the analysis / design stage.

Then, it is possible to reduce the cost of modifying the specifications in the software production downstream process and to produce highly reliable object-oriented software.

[Brief description of drawings]

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

FIG. 2 is a child diagram (a) showing an object diagram that is an input of the token generation unit, and a child diagram (b) illustrating a token generated by the token generation unit.

FIG. 3 is a child diagram (a) illustrating an object communication diagram and a child diagram (b) illustrating conversion to a high-level Petri net.

FIG. 4 is a child diagram (a) illustrating a state diagram.
FIG. 6B is a child diagram (b) illustrating conversion into a high-level Petri net.

FIG. 5 is a diagram showing a conversion procedure from a state diagram to a high level Petri net.

FIG. 6 is a child diagram (a) illustrating a data flow diagram and a child diagram (b) illustrating a conversion to a high level Petri net.

FIG. 7 is a diagram illustrating a high-level Petri net corresponding to a state diagram corresponding to the “machining machine” portion illustrated in FIG. 3;

FIG. 8 is a diagram exemplifying a high-level Petri net generated from the generation results of FIGS. 2, 3, 4, 6, and 7 by the Petri net refining unit.

[Explanation of symbols] 1 Object-oriented analysis / design support system 2 Object diagram 3 Token generator 4 Object communication diagram 5 Dynamic specification conversion unit between classes 6 State diagram 7 Dynamic specification conversion unit within class 8 Data flow diagram 9 Functional specification Converter 10 High-level Petri net 11 Petri net refiner

Claims (1)

[Claims] 1. A structure is attached to a token in a Petri net from an object diagram that describes static aspects of a design target such as hierarchical relationships and aggregation relationships of classes and objects when software is analyzed and designed based on an object-oriented design methodology. Describes the means of generating tokens in high-level Petri nets and the aspect of dynamic behavior between classes such as exchange of events or messages between classes when analyzing and designing software based on object-oriented design methodology A method for generating a net structure of a high-level Petri net that represents a dynamic specification between classes from an object communication diagram and a class or object receives an event when analyzing and designing software based on an object-oriented design methodology. Line Based on an object-oriented design methodology and a means for generating a net structure of a high-level Petri net that represents a dynamic specification in a class from a state diagram that describes dynamic behavior in a target class such as a description of a power process. When analyzing and designing software by means of means, a means to generate a net structure of a high level Petri net representing the functions realized by each class from the data flow diagram that describes the logic of processing within a class, that is, the detailed flow of processing. An object-oriented analysis / design support system having: means for generating a high-level perinet that combines and fuses the net structure and tokens of the high-level perinet generated by each of the above means.