JP6291454B2 - Business process diagram generation apparatus, business process diagram generation program, and business process diagram generation method - Google Patents

Description

  The present invention relates to a document format conversion technique, and more particularly to a business process diagram generation apparatus, a business process diagram generation program, and a business process diagram generation method for generating a business process diagram from a standardized document.

At present, automation is underway in various processes of system development. For example, system developers can automate conversion between models and source code by modeling from system design to manufacturing using an automated tool using MDA (Model Driven Architecture). Has been done. At this time, the system design is described in the form of a reusable model using, for example, UML (Unified Modeling Language).
In addition, for a certain type of system, there may be a blueprint (model) that has already been defined as past accumulation. For example, in the field of network management systems (operation systems), system requirements, functional specifications, and the like are based on M.I. of ITU-T (International Telecommunication Union Telecommunication Standardization Sector). It is defined as a standard by the 3700 series (http://www.itu.int/rec/T-REC-M/en).

  On the other hand, attempts have been made to automate conversion between models from the viewpoint of automating some processes in system development. For example, a technique for verifying the consistency between a state machine diagram and an activity diagram in UML is disclosed (see Non-Patent Document 1). Here, the state machine diagram describes the behavior of the individual objects constituting the system based on the state transitions that can be observed from the outside. Further, the activity diagram represents the behavior of the system as an operation flow performed by objects and actors constituting the system.

Masato Nomura and one other, "Consistency analysis between UML state machine and activity diagram", IEICE Technical Report, IEICE, November 2011, SWIM2011-29, p.65-70

However, in the technique using the conventional MDA tool, it is assumed that a model as a design drawing is described in advance and converted into data in UML or the like. Therefore, there is a problem that it takes a cost to create a model to be a design drawing of the system, that is, to design and develop the model itself.
As mentioned above, there are already models defined as standards in the field of operation systems, but many of these standardized documents are text documents written in natural language, and in order to actually use them, It was necessary for the designer to read the document, understand the content, and convert it to UML or the like.
In addition, as with the technique described in Non-Patent Document 1, although some processes (between the state machine diagram and activity diagram) are suggested to be automated, a system design document (hereinafter referred to as “standardization”) that has already been defined as a standard has been suggested. None of them could be converted into a business process diagram.

  The present invention has been made in view of such a background, and the present invention is a business process diagram generation apparatus capable of generating a business process diagram from a standardized document that defines a system design in an upstream process of operation system development. An object is to provide a business process diagram generation program and a business process diagram generation method.

  In order to solve the above-described problems, the invention described in claim 1 includes a use case table relating to a business process, a class definition defining data attributes relating to the business process as classes, and individual operation contents in the business process. Storage means for storing reconstruction rule information indicating rules for converting a standardized document including the described operation table into structured data based on a structured format; and taking the standardized document into the reconstruction rule information With reference to the data restructuring means for converting to the structured data, the structured data obtained by subjecting the structured data of the use case table to natural language processing and converting the processing contents shown in the use case table to a state transition diagram Sub-process analysis means for generating, the use case table, the A process conversion unit that generates a business process diagram using each structured data of a class definition, the operation table, and the state transition diagram, and the process conversion unit refers to the structured data of the use case table Then, extract the use case name in the use case, describe the activity of the business process diagram, refer to the structured data of the use case table, extract the operation in the use case, and extract the operation The operation content indicating the same operation is obtained from the operation table and described in the business process diagram, and the state transition indicated in the state transition diagram is referred to by referring to the structured data of the generated state transition diagram. As the activity in the business process diagram, the branch of the state is added to the business process diagram. Describes the order relationship between the activities as gateways and messages, extracts the data attributes of the class by referring to the structured data of the class definition, and performs the same operations as the operations indicated by the extracted data attributes A business process diagram generating apparatus, wherein the business process diagram is generated by acquiring contents from the operation table and associating the class with the acquired operation contents and describing them in the business process diagram It was.

  The invention described in claim 5 includes a use case table related to a business process, a class definition that defines the attribute of data related to the business process as a class, and an operation table that describes individual operation contents in the business process. A business process diagram generation method of a business process diagram generation device that generates a business process diagram using a standardized document, wherein the business process diagram generation device converts the standardized document into structured data based on a structured format. Storage means for storing reconstruction rule information indicating a rule to be converted into the standard document, the step of taking in the standardized document and referring to the reconstruction rule information and converting it into the structured data; and the use case Table structured data in natural language Processing and generating structured data obtained by converting the processing contents shown in the use case table into a state transition diagram, and extracting the use case name in the use case with reference to the structured data in the use case table Describe the activity of the business process diagram, refer to the structured data of the use case table, extract the operation in the use case, and extract the operation content indicating the same operation as the extracted operation from the operation table. Obtain and describe in the business process diagram, refer to the structured data of the generated state transition diagram, use the state transition shown in the state transition diagram as the activity in the business process diagram, and branch the state As the gateway and message in the business process diagram. Describing the order relationship between them, referring to the structured data of the class definition, extracting the attribute of the data of the class, and obtaining the same operation content as the operation indicated by the attribute of the extracted data from the operation table And generating the business process diagram by associating the class with the acquired operation content and describing it in the business process diagram. .

By doing so, the business process diagram generation device takes in standardized documents including use case tables, class definitions, and operation tables, and refers to reconstruction rule information to convert each standardized document into structured data. Can do. Then, the business process diagram generating device performs natural language processing on the structured data of the use case table, and converts the processing content shown in the use case table into a state transition diagram. Subsequently, the business process diagram generating device generates a business process diagram using each structured data of the use case table, the class definition, the operation table, and the state transition diagram.
Therefore, the business process diagram generation apparatus can generate a business process diagram (automatically) by analyzing each item described in the standardized document based on the standardized document regarding the design of the operation system. Therefore, it is possible to reduce the cost of operation system development (particularly the design process).

  In the invention according to claim 2, the sub-process analysis means parses the processing contents of the use case shown in the use case table, sets the contents shown in the main sentence as a state, and shows the contents shown in the subordinate sentence State transition diagram in the use case as the state transition, and the process conversion means uses the state transition in the state transition diagram in the use case as the use case name of the use case in the business process diagram. The business process diagram generation device according to claim 1, wherein the business process diagram generation device is described as an activity of a sub-process of the described activity.

  By doing so, the business process diagram generation device can create a state transition diagram of processing in the use case shown in the use case table and describe it as a sub-process of the activity in the business process diagram.

  According to a third aspect of the present invention, the standardized document is an M.D. The business process diagram generation apparatus according to claim 1, wherein the business process diagram generation apparatus is a standardized document having a format defined in 3020.

  In this way, the M.I. Data generated in accordance with a standardized document in a format defined in 3020 can be used to generate a business process diagram.

  The invention described in claim 4 is a business process diagram generation program for causing a computer to function as the business process diagram generation apparatus according to any one of claims 1 to 3.

  In this way, a general computer can be caused to function as the business process diagram generation device according to any one of claims 1 to 3.

  According to the present invention, there are provided a business process diagram generation apparatus, a business process diagram generation program, and a business process diagram generation method for generating a business process diagram from a standardized document that defines system design in an upstream process of operation system development. can do.

It is a figure which shows the example in which "Requirement" was described in the standardization document. It is a figure which shows the example in which the "Use Case table" was described in the standardized document. It is a figure which shows the example in which the "class diagram" and the "IOC definition" were described in the standardization document. It is a figure which shows the example in which the "state transition diagram" was described in the standardization document. It is a figure which shows the example in which the "operation table" was described in the standardization document. It is a functional block diagram which shows the structural example of the business process diagram production | generation apparatus which concerns on this embodiment. It is the figure which converted "Requirement" in a standardized document (PDF format) into a standardized document (XML format). It is the figure which converted the "use case table" in a standardized document (PDF format) into the standardized document (XML format). It is a figure which illustrates the reconstruction rule information which concerns on this embodiment. It is a figure which shows the example which restructured the use case table | surface to the structured data of XML format. It is a figure which shows the example which reconfigure | reconstructed the IOC definition to the structured data of the XML format. It is a figure which shows the example which reconstructed the operation table into the structured data of the XML format. It is a block diagram which shows the function structure of the sub process analysis part which concerns on this embodiment. It is a figure for demonstrating preparation of the sub process table by the sub process table preparation part which concerns on this embodiment. FIG. 14A is a diagram illustrating an example item of “Step” in the use case table. FIG. 14B is a diagram illustrating the sub-process table created by the sub-process table creating unit. It is a figure which illustrates the state transition diagram (in a use case) which the state transition diagram preparation part concerning this embodiment created. It is a figure for demonstrating creation of the state transition diagram (between use cases) by the state transition diagram preparation part which concerns on this embodiment. FIG. 16A is a diagram illustrating an example of items of “Preconditions”, “Begins when”, “Ends when”, and “Post Conditions” in the use case table. FIG. 16B is a diagram illustrating a state transition diagram (between use cases) created by the state transition diagram creation unit. It is a block diagram which shows the function structure of the process conversion part which concerns on this embodiment. It is a figure which shows the example which the business process diagram setting part which concerns on this embodiment set three pools, "operator", "NML / EML", and "NE" in a business process diagram. It is a figure which shows the example which the activity extraction part which concerns on this embodiment has arrange | positioned the use case name as an activity in the operator pool of a business process diagram. It is a figure which shows the example which the operation extraction part which concerns on this embodiment extracted the operation corresponding to a use case, and has arrange | positioned as an activity on a business process diagram. It is a figure which shows the example which the flow creation part which concerns on this embodiment described the order relationship between the activities of a business process diagram based on a state transition diagram (between use cases). It is a figure which shows the example which the data arrangement | positioning part which concerns on this embodiment linked | related the data shown by IOC definition, and the message between pools, and has arrange | positioned on a business process diagram. It is a figure which shows the example which the subprocess diagram creation part concerning this embodiment described the subprocess with respect to activity based on a state transition diagram (in a use case). It is a figure which illustrates the business process figure which the process conversion part which concerns on this embodiment outputs.

Next, a business process diagram generation apparatus 1 (see FIG. 6) and the like in a mode for carrying out the present invention (hereinafter referred to as “this embodiment”) will be described.
The business process diagram generating apparatus 1 according to the present embodiment takes in a standardized document related to the design of an operation system and analyzes each item described in the standardized document, thereby generating a business process diagram 300 (see FIG. 24 described later). Generate (automatically). Here, FIG. 24 is an example represented based on BPMN (Business Process Modeling Notation), which is generally used as a business process diagram. In BPMN, the content of processing is described in a rounded rectangle symbol representing an activity, and the activity is connected by a sequence flow represented by an arrow. Various events are represented by circles, and conditional branches are represented by diamonds.

  In the field of operation systems, standards for system design models (requirements, functional specifications, processing contents, etc.) are defined. The business process diagram generating apparatus 1 according to the present embodiment can reduce the design cost of operation system development by reusing the information (standardized document). Further, by adopting the business process diagram 300, it is possible to connect to execution on the workflow engine by adding necessary information in the subsequent process, and the development cost can be reduced.

<Standardized document>
First, a standardized document (structured document) to be processed by the business process diagram generating apparatus 1 according to the present embodiment will be described.
Here, the business process diagram generation apparatus 1 is an M.I. 3020; A standardized document written in the format actually used in the 3700 series will be described as an example. For example, this M.M. M. 3700 series. 3703 (alarm management) and M.I. In 3704 (performance management), the contents necessary for the design of the operation system are M. It is described as a standardized document according to the format defined in 3020. In the present embodiment, this M.D. A standardized document in the format defined in 3030, specifically, M.30. Among the items described in the 3700 series (particularly M.3703, M.3704), at least “requirements”, “use case tables”, “class diagrams etc.”, “state transition diagrams”, “operation tables” It shall be described as a standardized document.
Hereinafter, the standardized document according to the present embodiment will be described in detail.

1 is a diagram illustrating an example (“6.2.1 Requirements” of ITU-T M.3703) in which “Requirements” is described in a standardized document. This “requirement” includes information such as “what you want to achieve” and “what you need to do”.
In addition, in the “Requirement”, each requirement is described in a format in which “Requirement ID” is added. FIG. 1 shows an example in which “REQ-FM-FUN-01” and “REQ-FM-FUN-02” are assigned to each requirement as “Requirement ID”.
The specific contents of each requirement are not described in detail because they are not related to the present invention. To the extent necessary for the description of the description format of the standardized document, the M.I. The 3700 series (particularly, M.3703, M.3704) is cited and described. Similarly, in the following description of the standardized document, it is described within the scope necessary for the description of the description format.

2 is a diagram showing an example (“6.3.4 Use Cases” in ITU-T M. 3703) in which a “Use Case table” is described in a standardized document.
The use case table describes requirements (processing) for the system from the viewpoint of the system user. In this use case table, as shown in FIG. 2, “Set alarm filter” is described as the use case name, and “Goal”, “Actor and roles” (actors) are used as the use case stages. And roles), "Telecom resources,""Assumptions,""Preconditions,""Beginswhen,""Step,""Endswhen," and "Exceptions." (Exception), “Post Conditions” and “Traceability” are set, and their contents are described.

  Note that the item “Step (processing)” is not limited to one of “Step 1” shown in FIG. 2, but may be described in a plurality, such as “Step 2” and “Step 3”. As for the use case table, a plurality of use case tables may be described in one standardized document. In “6.3.4 Use Cases” of 3703, following “6.3.4.1 Use case: Set alarm filter” shown in FIG. 2, “6.3.4.2 Use Case: Notification of alarm change "is described.

3 is an example in which “class diagram” (data model) and object class definition (IOC (Information Object Class) definition) are described in a standardized document (“7.2.2 Class diagram” “7.2” of ITU-T M.3704). .3 Information object class definitions ”). Hereinafter, the “class diagram” (data model) and the IOC definition may be collectively referred to as “IOC information”.
The class diagram shown in FIG. 3A is created in order to clarify the static structure (data structure) of the entire system, in which the classes constituting the system and the interrelationships between the classes are described. In the IOC definition shown in FIG. 3B, the requirements belonging to each class are defined as the “Requirement ID” described above.

  4 is a diagram illustrating an example (“7.2.3.2.4 State diagram” of ITU-T M.3704) in which a “state transition diagram” is described in a standardized document. The state transition diagram is a diagram illustrating a state that changes with the passage of time or operation. Here, the state is represented by a rounded rectangle and the state transition (trigger) is represented by an arrow.

5 is a diagram showing an example (“7.3.3 Interface PMIRPOperations” of ITU-T M.3704) in which an “operation table” is described in a standardized document. The operation table describes an operation (operation) executed when a certain requirement is satisfied, and parameters (input parameter, output parameter) when the operation is executed.
The table indicated by reference numeral (a) in FIG. 5 shows an example in which “Requirement ID” that is an identifier of the requirement (Requirement) described in association with an operation name (Operation name) indicating each operation is described. . The table shown in FIG. 5B shows an example in which “moClass” or the like is described as an input parameter (Input parameter) when the operation is “createMeasurementJob”. 5 shows an example in which “measurementJobId” or the like is described as an output parameter (Output parameter) when the operation is “createMeasurementJob”.

The business process diagram generation apparatus 1 is a document in which the “requirements”, “use case tables”, “IOC information” (class diagrams and IOC definitions), “state transition diagrams”, and “operation tables” described above are standardized. Based on the above, a business process diagram 300 (see FIG. 24) is generated. As a result, the design cost of operation system development can be reduced. In addition, by forming the business process diagram 300, it is possible to connect to the execution on the workflow engine by adding necessary information in the subsequent process, so that the development cost can be reduced.
Business process diagrams are not defined in UML, but in UML rules, they are notation similar to activity diagrams and are easy to convert, so convert the generated business process diagrams to UML and use them. It is also possible to do.

<Business process diagram generator>
Next, the business process diagram generating device 1 will be described.
The business process diagram generation device 1 is a device that generates a business process diagram 300 (see FIG. 24) from the standardized document, and is configured by a computer including a control unit, a storage unit, and an input / output unit (all not shown). The
Here, the storage unit (storage means) is configured by a hard disk, a flash memory, a RAM (Random Access Memory), and the like, and stores reconstruction rule information 200 and the like to be described later.
The input / output unit is an input / output interface for transmitting / receiving information to / from an external device and an input / output interface for inputting / outputting information to / from an input device such as a keyboard (not shown) or an output device such as a monitor. It consists of.
The control unit controls all the processes executed by the business process diagram generating device 1 and implements each function described below. In addition, this control part is implement | achieved when CPU (Central Processing Unit) expand | deploys and executes the program (business process figure production | generation program) stored in the memory | storage part of this business process figure production | generation apparatus 1 on RAM, for example. .

FIG. 6 is a functional block diagram illustrating a configuration example of the business process diagram generating device 1 according to the present embodiment.
As shown in FIG. 6, the control unit of the business process diagram generating apparatus 1 includes a data extraction unit 10 (data reconstruction unit), a reconstruction unit 20 (data reconstruction unit), and a sub-process analysis unit 30 (sub-process analysis unit). ) And a process conversion unit 40 (process conversion means).

The data extraction unit 10 (data reconstruction unit) reads the standardized document (here, a document in PDF (Portable Document Format) format) and converts it into a structured format (for example, XML format). Convert and output as a standardized document (XML format).
The restructuring unit 20 (data restructuring means) reads the standardized document (XML format) output from the data extraction unit 10 and semantically structures the requirements, use case table, IOC information, state transition diagram, and operation table. Are reconstructed and output as structured data (XML format). At this time, the reconstruction unit 20 reconstructs each piece of information by referring to the reconstruction rule information 200 (FIG. 9 described later) stored in advance in the storage unit.
The sub-process analysis unit 30 (sub-process analysis means) performs natural language processing on the use case table, and sub-process table (see FIG. 14B described later) and state transition diagram (in the use case) (FIG. 15 described later). And a state transition diagram (between use cases) (see FIG. 16B described later) are output. A state transition diagram (in a use case) is a diagram showing a state transition in a certain use case. A state transition diagram (between use cases) is a diagram showing state transitions between a plurality of use cases.
The process conversion unit 40 (process conversion means) includes requirements, use case tables, IOC information (“class diagram (data model)” and “IOC definition”), various types created by the reconstruction unit 20 and the sub-process analysis unit 30. State transition diagram and structured data of operation table (XML format) are read and output as a business process diagram.
Hereinafter, these functions will be described in detail.

≪Data extraction part≫
The data extraction unit 10 (see FIG. 6) includes “requirements”, “use case tables”, “IOC information” (class diagram and IOC definition), “state transition diagram”, described in a standardized document (PDF format), Information such as an “operation table” is taken in, lexical analysis is performed, converted into a structured format (XML format or the like), and output as a standardized document (XML format). Note that the conversion from the PDF format of the standardized document to the XML format by the data extraction unit 10 can be performed using existing technology (for example, “https: // helpx. adobe.com/jp/acrobat/kb/558.html ").

FIG. 7 is a diagram in which a part (see FIG. 1) in which “Requirement” is described in a standardized document (PDF format) is mechanically converted into a standardized document (XML format) using existing technology. . Further, FIG. 8 shows that a part (see FIG. 2) in which a “use case table” is described in a standardized document (PDF format) is mechanically converted into a standardized document (XML format) using existing technology. FIG.
Similarly, the data extraction unit 10 also mechanically uses the existing technology for a part in which “IOC information”, “state transition diagram”, “operation table”, etc. are written in a standardized document (PDF format). Convert to standardized document (XML format).

≪Reconstruction Department≫
The reconstruction unit 20 (see FIG. 6) reads each standardized document (XML format) output from the data extraction unit 10 and refers to the reconstruction rule information 200 (FIG. 9) stored in the storage unit. Create and output information such as requirements, use case table, IOC information, state transition diagram, operation table, etc. The semantically structured information may hereinafter be referred to as “structured data”. Also, “semantically structured” is different from the above-mentioned “mechanically” structured XML data, and is based on the content of the basic information (standardized document written in PDF format). This means that elements, attributes, text data, and the like are described (see FIGS. 10 to 12 to be described later).

FIG. 9 is a diagram illustrating the reconstruction rule information 200 according to this embodiment.
In the reconstruction rule information 200, “Path before conversion” and “Path after conversion” are described in association with each other. In the example shown in FIG. 9, with respect to “Goal” in the use case table, the location where “Goal” is described and the location where the value of the element “Goal” is described are “Path before conversion” and “Path after conversion” is associated. In the reconstruction rule information 200, conversion rules are stored so that items described in a standardized document (PDF format) can be reconstructed as semantically structured information (structured data in XML format). It is decided.

  FIG. 10 is a diagram illustrating an example in which the reconstruction unit 20 refers to the reconstruction rule information 200 and reconstructs the use case table into semantically structured information (structured data in XML format). . FIG. 11 shows the standardization document (XML format) output by the data extraction unit 10 for the standardized document (PDF format) that defines the IOC definition shown in FIG. It is a figure which shows the example reconfigure | reconstructed into the information (structured data of XML format) of the IOC definition semantically structured with reference to the information. 12 shows the standardized document (XML format) output by the data extraction unit 10 for the standardized document (PDF format) that defines the operation table shown in FIG. 5, and the reconstruction unit 20 obtains the reconstruction rule information. FIG. 10 is a diagram illustrating an example of reconstructing operation table information (structured data in XML format) semantically structured with reference to 200;

  In the standardized document, since the description requirement (style) is determined in advance, the conversion content can be designated in advance as the reconstruction rule information 200 for each item. Therefore, the reconstruction unit 20 refers to the reconstruction rule information 200 for each information (requirement, use case table, IOC information, state transition diagram, operation table) of the standardized document (XML format) that has been taken in. It is possible to reconstruct and output the structured data in XML format reflecting the contents of the standardized document.

≪Sub process analysis department≫
The sub-process analysis unit 30 (see FIG. 6) performs natural language processing on the use case table, sub-process table (see FIG. 14B), state transition diagram (in the use case) (see FIG. 15), and state A transition diagram (between use cases) (see FIG. 16B) is output.
FIG. 13 is a block diagram illustrating a detailed functional configuration of the sub-process analysis unit 30. As shown in FIG. 13, the sub-process analysis unit 30 includes a lexical analysis unit 31, a sub-process table creation unit 32, and a state transition diagram creation unit 33.

The lexical analysis unit 31 refers to the structured data of the use case table output from the reconstruction unit 20, and separates the contents described in the use case table for each lexical. Specifically, the lexical analysis unit 31 performs an analysis of dividing the content of “Step (means)” in the use case table for each lexical phrase.
Using the output information from the lexical analyzer 31, the sub-process table generator 32 decomposes the “Step (means)” item of the use case table into a subject and a predicate by syntactic analysis, and generates a sub-process table.

  Here, the “Step (means)” item in the use case table will be described on the assumption that “Step 1”, “Step 2.1”, and “Step 2.2” are set as shown in FIG. . Note that the sub-process analysis unit 30 performs processing by acquiring information obtained by reconstructing the standardized document into XML-format structured data from the restructuring unit 20, but the description is easy to understand in FIG. Therefore, the use case table is illustrated and described in the form of a PDF format based on the use case table.

  The sub-process table creation unit 32 parses the content of “Step” in this use case table, extracts the text shown in the main sentence, decomposes it into the subject (subject) and the predicate (content), and stores them in the use case table To do. Further, the sub-process table creation unit 32 converts a sentence whose subject is not “manager” (administrator) and “agent” (actor of processing) into a command statement indicating the processing content, and converts it into a use case table. Store.

  FIG. 14B shows the sub-process table created by the sub-process table creating unit 32 as described above. 14B, the sub-process table creation unit 32 actually performs processing as structured data in the XML format, but here it is illustrated in a table format for easy understanding.

For example, the sub-process table creation unit 32 refers to “Step 1” in the use case table shown in FIG. 14A, and reads “The manager sends a request to the agent... [1]) is determined as the main sentence. Then, the sub-process table creation unit 32 extracts “The manager” as the subject (subject), extracts “Send a request to the agent” as the predicate (content), and displays the sub-process table shown in FIG. Stored in the process table (see symbol [1] in FIG. 14B).
In addition, the sub-process table creation unit 32 refers to “Step 2.1” in the use case table and determines that “the job ID will be returned to the manager” (see reference numeral [2] in FIG. 14A) as the main text. To do. Then, since the subject (subject) is neither “manager” nor “agent”, the sub-process table creation unit 32 converts the sentence into a command sentence indicating the processing content and sets it as “Return job ID to the manager”. And stored in the contents column of the sub-process table of FIG. At that time, “−” indicating that the subject is neither “manager” nor “agent” is stored in the subject (see reference numeral [2] in FIG. 14B).
In this way, the sub-process table creation unit 32 can extract the subject and contents of the process indicated by “Step” of each use case table, and create a sub-process table.

The state transition diagram creation unit 33 (see FIG. 13) creates a state transition diagram (within a use case) and a state transition diagram (between use cases).
The state transition diagram creation unit 33 refers to the contents of “Step” in the use case table shown in FIG. 14A and the subprocess table (FIG. 14B) created by the subprocess table creation unit 32. Create a state transition diagram (in the use case).

  Specifically, the state transition diagram creating unit 33 refers to FIG. 14A, and in the contents of “Step” of the use case table, the state transition table generates subordinate sentences for the main sentence including the If clause and the Other clause. It is treated as a “state”. In addition, the contents of the sub-process table are handled as state transitions (triggers).

FIG. 15 is a diagram illustrating a state transition diagram (in a use case) created by the state transition diagram creation unit 33. As shown in FIG. 15, the If clause, Other clause, and subordinate sentences to the main text are indicated by a circle (◯) as a state, and the contents of the sub-process table are indicated by an arrow (→) as a state transition (trigger). Yes.
In this way, the state transition diagram creation unit 33 can create a state transition diagram (within a use case) for each use case table.

  Further, the state transition diagram creation unit 33 refers to “Preconditions”, “Begins when”, “Ends when”, “Post Conditions” in each use case table, Create an order relationship and transition pattern between use cases as a state transition diagram (between use cases).

As shown in FIG. 16, the state transition diagram creation unit 33 performs “Preconditions”, “Begins when”, “Ends when”, “Post Conditions” for each of the plurality of use case tables. Condition) ”is processed in natural language to analyze the order relationship and transition pattern between use cases, and describe the use case name of each use case table as a trigger for state transition.
As described above, the sub-process analysis unit 30 performs processing by obtaining information obtained by reconstructing the standardized document into XML-structured data from the restructuring unit 20, but for ease of explanation, FIG. In FIG. 16A, the use case table is illustrated in the form of a PDF format, and in FIG. 16B, the state transition diagram is illustrated.

The state transition diagram (between use cases) in FIG. 16B is, for example, after “6.3.4.1 Create a measurement job”, “6.3.4.2 Suspend a measurement job” and “6.3.4.5 Stop a measurement job”. ”Indicates that the process branches and the state transitions. Note that the item number of the use case table such as “6.3.4.1” may be described in the state transition diagram (between use cases) or may be omitted.
In this way, the state transition diagram creation unit 33 can create a state transition diagram (between use cases) indicating the order and transition pattern between the use cases.

≪Process conversion part≫
The process conversion unit 40 (see FIG. 6) displays requirements, use case tables, IOC information (class diagrams and IOC definitions), various state transition diagrams, and operation tables created by the reconstruction unit 20 and the sub-process analysis unit 30. Read and output as a business process diagram 300.
FIG. 17 is a block diagram illustrating a detailed functional configuration of the process conversion unit 40. As shown in FIG. 17, the process conversion unit 40 includes a business process diagram setting unit 41, an activity extraction unit 42, an operation extraction unit 43, a flow creation unit 44, a data arrangement unit 45, and a sub-process diagram creation unit. 46.

Note that the process conversion unit 40 converts the requirements, use case tables, IOC information (class diagrams and IOC definitions), various state transition diagrams, and operation tables created by the reconstruction unit 20 and the sub-process analysis unit 30 into an XML format. It is obtained and processed as structured data. However, in the diagrams related to the process conversion unit 40 shown below, in order to make the explanation easy to understand, the use case table and the operation table are illustrated by the representation in the PDF, and the state transition diagram is also expressed in the XML format. Instead, it will be described with a representation of a state transition diagram defined by UML or the like.
In addition, as a pre-process for starting the generation process of the business process diagram 300, the process conversion unit 40 extracts a plurality of acquired state transition diagrams and analyzes them to create a state transition diagram that merges them. May be.

The business process diagram setting unit 41 (see FIG. 17) generates an empty business process diagram 300 and sets a pool for a layer that is a subject of process processing.
In FIG. 18, the business process diagram setting unit 41 sets three pools of “operator”, “NML / EML” (Network Management Layer / Element Management Layer), and “NE” (Network Element) in the business process diagram 300. It is a figure which shows an example. In the present embodiment, a case where the business process diagram generation apparatus 1 creates a business process diagram 300 of network design will be described as an example. Therefore, here, the business process diagram setting unit 41 relates to the “operator” pool (hereinafter referred to as “operator pool”) related to the management of the entire system, the connection between networks, and the setting and processing of each network device. An NML / EML pool (hereinafter referred to as an “NML / EML pool”) and an “NE” pool (hereinafter referred to as an “NE pool”) that executes processing of individual network devices are business. Assume that the process diagram 300 is set.

The activity extraction unit 42 (see FIG. 17) extracts use cases that can be “activity” on the business process diagram 300 based on the use case table.
Specifically, the activity extraction unit 42 refers to “Begins When” at the start of each use case table, and starts with “The manager” as the subject of the manager. A thing is detected, and its use case (use case name) is placed in the operator pool as an activity.
In addition, the activity extraction unit 42 refers to “Begins When” at the same time from items in the use case table, and detects items whose agent is the subject, that is, items beginning with “The agent”. Then, the use case (use case name) is placed in the NML / EML pool as an activity.

In FIG. 19, the activity extraction unit 42 refers to “Begins When” at the start of the use case table, detects a sentence whose subject is “The manager”, and creates “Create a measurement job” and “ An example in which the use case name “Suspend a measurement job” is arranged as an activity in the operator pool of the business process diagram 300 is shown.
In this way, the activity extraction unit 42 can arrange activities in the operator pool and the NML / EML pool of the business process diagram 300.

  The operation extraction unit 43 (see FIG. 17) detects the corresponding operation from the operation table as a message transmitted and received by the activity corresponding to each use case extracted by the activity extraction unit 42, and arranges it on the business process diagram 300. That is, the operation extraction unit 43 performs an operation of extracting an operation corresponding to each use case and arranging the operation on the business process diagram 300.

  Specifically, the operation extraction unit 43 extracts “RequirementID” described in “Traceability” of the use case table, and extracts the “RequirementID” and each operation described in the operation table. Search for an operation name that matches "RequirementID". Then, the operation extraction unit 43 arranges the searched operation name as an activity at the position of the NML / EML pool directly under the activity of the use case.

  Then, the operation extraction unit 43 creates a message flow (dotted arrow) from the use case activity arranged in the operator pool to the corresponding operation activity arranged in the NML / EML pool. Further, the operation extraction unit 43 describes the input parameters described in the operation table in the message flow. Further, the operation extraction unit 43 creates a message flow from the operation activity arranged in the NML / EML pool to the use case activity arranged in the operator pool. Then, the operation extraction unit 43 describes the output parameter described in the operation table in the message flow.

In addition, when there is no operation corresponding to the use case, the operation extracting unit 43 displays the use case activity with a color or a comment so that the fact is understood. Also good.
In addition, regarding an operation in which a message is exchanged with the NE, a message flow (dotted arrow) is described between the NML / EML pool and the NE pool.

In FIG. 20, the operation extraction unit 43 performs “REQ-PM-FUN-01, REQ-PM-FUN” described in “Traceability” of the use case table “6.3.4.1 Create a measurement job”. -02 ”is extracted, and“ createMeasurementjob ”is detected as an operation name (Operation name) in which the extracted“ RequirementID ”and“ RequirementID ”of each operation described in the operation table match. Then, the operation extraction unit 43 arranges the activity “createMeasurementJob ()” at the position of the NML / EML pool directly under the use case activity “Create a measurement job”.
Next, the operation extracting unit 43 sends a message flow from the use case activity “Create a measurement job” arranged in the operator pool to the corresponding operation activity “createMeasurementJob ()” arranged in the NML / EML pool. Create (dotted arrow). Further, the operation extracting unit 43 extracts and describes “moClass” or the like as the parameter name of the input parameter described in the operation table in the message flow. Similarly, the operation extraction unit 43 changes the message flow from the operation activity “createMeasurementJob ()” arranged in the NML / EML pool to the use case activity “Create a measurement job” arranged in the operator pool. Extract the parameter name of the output parameter (such as “measurementJobId”) described in the operation table.

  In this way, the operation extraction unit 43 can detect a corresponding operation from the operation table as a message transmitted and received by each activity extracted by the activity extraction unit 42 and arrange it as an activity on the business process diagram 300. Further, the operation extraction unit 43 can describe input parameters and output parameters in the message flow.

The flow creation unit 44 (see FIG. 17) describes the order relationship between activities in the business process diagram 300 based on the state transition diagram (between use cases) generated by the sub-process analysis unit 30.
Specifically, the flow creation unit 44 associates the trigger of state transition in the state transition diagram (between use cases) with the activity of the operator pool in the business process diagram 300. Further, the branch of the state in the state transition diagram (between use cases) is made to correspond to the gateway and the message in the business process diagram 300.

FIG. 21 shows the business process diagram 300 based on the state transition diagram (between use cases) (see FIG. 16B) created by the flow creation unit 44 by the sub-process analysis unit 30 (state transition diagram creation unit 33). It is a figure which shows the example which described the order relationship between these activities.
As shown in FIG. 21, a state transition (trigger) in a state transition diagram (between use cases) is regarded as an activity. For example, “6.3.4.1 Create a measurement job” is set to “Create a measurement job” of the activity in the business process diagram 300, and other state transitions (triggers) are similarly associated with activities in the business process diagram 300. Then, describe the order relationship between activities along the state transitions shown in the state transition diagram (between use cases). Then, the branch of the state in the state transition diagram (between use cases) is associated with the gateway and the message in the business process diagram 300.

  By doing so, the flow creation unit 44 can describe the order between activities in the business process diagram 300. In addition, the flow creation unit 44 can transmit a message required when the state branches to the corresponding activity in the NML / EML pool.

The data placement unit 45 (see FIG. 17) displays the IOC definition used in each activity as “note” (display indicating supplementary contents) and “relation” (display indicating association between data and flow) in the business process diagram 300. Use to describe. That is, the data placement unit 45 performs processing for associating the data indicated by the IOC definition and the message between pools on the business process diagram 300 (see FIG. 22).
Specifically, the data placement unit 45 refers to the IOC definition and creates an IOC list based on the class name (Class name) of the IOC definition. FIG. 22 shows an example in which “PMIRP”, “MeasurementJob”, and “Thresholdmonitor” are created as the IOC list. Subsequently, the data placement unit 45 refers to the input parameter and output parameter of each operation table, and if any of the following conditions is met, the class name of the corresponding IOC list is assigned to the operator pool and the NML / EML. It is displayed as a “note” over the message flow connecting the pools, and the data indicated by the class name in the IOC list and the message flow are connected using “relation”.

(Condition 1) In the “Information Type” column of the input parameter or output parameter in the operation table, the class name described at the top is referred to, and the class name matches the class name in the IOC list.
(Condition 2) The operation name excluding “Id” at the end from the “Name” column of the input parameter or output parameter of the operation table matches the class name of the IOC.

  In FIG. 22, since “MeasurementJob” is written at the top of the “Information Type” column of the output parameter whose operation name is “CreateMeasurementJob”, it matches the class name of the IOC list and satisfies (Condition 1). Yes. The operation name obtained by removing “Id” from the end of the “Name” column is “measurementJob”, which matches the class name of the IOC, and satisfies (Condition 2). Therefore, the data arrangement unit 45 describes “MeasurmentJob” as the class name of the IOC list in the note, and displays it over the message flow connecting the operator pool and the NML / EML pool. Are linked using "relation".

  In this way, the data arrangement unit 45 assigns the data class related to the message between the operator pool and the NML / EML pool to the business process diagram 300 when any of the above (condition 1) (condition 2) is satisfied. Can be arranged.

The sub-process diagram creation unit 46 (see FIG. 17) describes a sub-process diagram for each activity based on the state transition diagram (in the use case) generated by the sub-process analysis unit 30.
Specifically, the sub-process diagram creation unit 46 uses the state transition diagram (in the use case) created by the state transition diagram creation unit 33 under the activity corresponding to the sub-process table analyzed by the sub-process analysis unit 30. State transitions (triggers) are described as subprocess order.

FIG. 23 is a diagram illustrating an example in which the sub-process diagram creating unit 46 describes a sub-process for an activity based on a state transition diagram (in a use case). FIG. 23 shows an example in which a subprocess of “Create Measurement Job” is described.
The sub-process diagram creation unit 46 describes the sub-process of “Create Measurement Job” in the business process diagram 300 with reference to the state transition diagram (in the use case) shown in FIG. At that time, the sub-process diagram creation unit 46 describes the state transition (trigger) of the state transition diagram (in the use case) as the activity of the sub-process.

  In this way, the sub-process diagram creating unit 46 can arrange the sub-process indicating the detailed processing flow for each activity described in the NML / EML pool on the business process diagram 300. Therefore, the process conversion unit 40 can generate and output the business process diagram 300 shown in FIG. The business process diagram 300 shown in FIG. 24 can be converted into a UML format such as a state transition diagram or a class diagram and output, so that it can be used in other system development.

  As described above, according to the business process diagram generation device 1, the business process diagram generation program, and the business process diagram generation method according to the present embodiment, the standardized document is captured and described in the standardized document. Each item can be analyzed to generate a business process diagram (automatically). Therefore, it is possible to reduce the cost of operation system development (particularly the design process).

1 Business Process Diagram Generation Device 10 Data Extraction Unit (Data Reconstruction Means)
20 Reconstruction unit (data reconstruction means)
30 Sub-process analysis unit (sub-process analysis means)
31 lexical analysis unit 32 sub-process table creation unit 33 state transition diagram creation unit 40 process conversion unit (process conversion means)
41 business process diagram setting unit 42 activity extraction unit 43 operation extraction unit 44 flow creation unit 45 data allocation unit 46 subprocess diagram creation unit 200 reconstruction rule information 300 business process diagram

Claims (5)

Based on a structured format, a standardized document including a business case use case table, a class definition that defines the attributes of data related to the business process as a class, and an operation table that describes individual operations in the business process Storage means for storing reconstruction rule information indicating a rule to be converted into structured data;
Data reconstructing means for taking in the standardized document, referring to the reconstructing rule information, and converting it into the structured data;
Sub-process analysis means for processing structured data of the use case table in natural language, and generating structured data obtained by converting the processing contents shown in the use case table into a state transition diagram;
Process conversion means for generating a business process diagram using each structured data of the use case table, the class definition, the operation table, and the state transition diagram,
The process conversion means includes
Refer to the structured data of the use case table, extract the use case name in the use case, describe the activity of the business process diagram,
With reference to the structured data of the use case table, an operation in the use case is extracted, the operation content indicating the same operation as the extracted operation is acquired from the operation table and described in the business process diagram,
With reference to the structured data of the generated state transition diagram, the state transition shown in the state transition diagram is the activity in the business process diagram, and the branch of the state is the gateway and message in the business process diagram, Describe the order relationship between the activities,
The attribute of the data of the class is extracted by referring to the structured data of the class definition, the same operation content as the operation indicated by the attribute of the extracted data is acquired from the operation table, and the class and the acquired A business process diagram generation apparatus, characterized in that the business process diagram is generated by associating an operation content with the business process diagram. The sub-process analysis means includes
Parse the content of the use case processing shown in the use case table, make the content shown in the main sentence a state, create the state transition diagram in the use case with the content shown in the subordinate sentence as the state transition,
The process conversion means includes
The state transition of the state transition diagram in the use case is described as an activity of a sub-process of the activity described as the use case name of the use case in the business process diagram. The business process diagram generation device described.   The standardized document is ITU-T M.264. The business process diagram generation device according to claim 1, wherein the business process diagram generation device is a standardized document having a format defined in 3020.   A business process diagram generation program for causing a computer to function as the business process diagram generation device according to any one of claims 1 to 3. Generate a business process diagram using a standardized document that includes a use case table for business processes, a class definition that defines the attributes of data related to the business process as classes, and an operation table that describes the individual operations in the business process A business process diagram generation method for a business process diagram generation device
The business process diagram generation device includes:
Storage means for storing reconstruction rule information indicating rules for converting the standardized document into structured data based on a structured format;
Capturing the standardized document, referring to the reconstruction rule information, and converting to the structured data;
Processing the structured data of the use case table with natural language, and generating structured data obtained by converting the processing content shown in the use case table into a state transition diagram;
Referring to the structured data of the use case table, extract the use case name in the use case, describe the activity of the business process diagram,
With reference to the structured data of the use case table, an operation in the use case is extracted, the operation content indicating the same operation as the extracted operation is acquired from the operation table and described in the business process diagram,
With reference to the structured data of the generated state transition diagram, the state transition shown in the state transition diagram is the activity in the business process diagram, and the branch of the state is the gateway and message in the business process diagram, Describe the order relationship between the activities,
The attribute of the data of the class is extracted by referring to the structured data of the class definition, the same operation content as the operation indicated by the attribute of the extracted data is acquired from the operation table, and the class and the acquired Generating the business process diagram by associating an operation content with the business process diagram,
A process for generating a business process diagram, characterized in that:

Images