JP2000056956A - Device and method for converting request specification model into other system model - Google Patents

Abstract

PROBLEM TO BE SOLVED: To convert a request specification model into another system model by extracting constituents being the execution entity of an internal procedure from a character thereby reflecting them on another system model. SOLUTION: A request specification model file is read from a request specification model file input part 104 and the scenario of constituents of a request specification model inputted to a character information storage part 105 is stored in a scenario information storage part 106. An entity information generation part 108 generates an entity based on an entity information generation rule. A process information generation part 109 generates a process based on a process information generation rule. A matrix information generation part 113 generates a matrix showing an access relation from the process to the entity. An other system model output part 116 integrates the entity, the process and the matrix and outputs an other system model file.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a scenario in which component information relating to components constituting a system development target task and procedure chain information which records a procedure startup sequence in or between components are recorded. The present invention also relates to a required specification model / other format model conversion device for converting a required specification model defined by the above to a model of another format, and a conversion method therefor.

[0002]

2. Description of the Related Art As a technique for defining required specifications in system development, for example, as described in Japanese Patent Application Laid-Open No. 9-81611, a character which is an element constituting a target task is defined and given to the character. There is a technique for defining required specifications by inputting real-world operations as fragmentary concrete examples of scenarios called scenes using data and procedures.

[0003] The characters referred to here are "people" and specific "objects" appearing in the required specifications, and other conceptual "abstract objects". A character has its name, display graphic information expressing its image, retained internal data information and internal procedure information. The internal data information held by the character is called an attribute, and the internal procedure information held by the character is called a message.

[0004] A scenario is a fragmentary example of a required specification. A scenario has, as constituent elements, information on a scene and characters appearing in the scenario. A scene is the activation of an internal procedure between characters.

[0005] The internal procedure is an operation or a process of accessing and executing, for example, referencing or updating between characters, such as accessing a database from a computer.

There is a required specification model / other format model conversion technology as a technology for converting a required specification model file defined by the required specification definition technology so that it can be used by a program which handles a model file of another format.

The requirement specification model / other format model conversion technique is to convert a requirement specification model file defined by the above requirement specification definition program according to the data format of the other format model file input by another program. This is a technology that allows a program to input, edit, and display on a display device.

[0008]

The conventional technique for defining the required specifications as described above does not provide a method for clearly indicating a character that is a subject that executes an internal procedure.

Further, even in the above-described conventional required specification model / other format model conversion technology, no method has been provided for extracting a character which is a subject that executes an internal procedure. For this reason, in the other-format model obtained by the conventional requirement specification conversion technology, the subject of executing the internal procedure in the system is ambiguous, and it has been difficult to perform a system analysis operation such as checking a relationship between system components.

[0010] An object of the present invention is to convert a requirement specification model into another format model by extracting a component which is a subject that executes an internal procedure from a character and reflecting the component in the other format model. Another object of the present invention is to provide another model conversion device.

[0011]

In order to achieve the above object, a required specification model / other format model conversion apparatus and method according to the present invention expresses names and appearances held by elements constituting a system development target business. Structural element information that records display graphic information, data names, and procedure names, and procedure call sequence information that records the call sequence of procedures between components, or procedure call sequence information that records the call sequence of procedures within components In the requirement specification model / other format model conversion device and method for converting the requirement specification model defined by the scenario that holds the model into a model of another format, the requirement specification model is stored in a computer-readable storage device,
The requirement specification model file including the requirement specification model is read from the requirement specification model file input means.

The component information obtained from the requirement specification model file input by the requirement specification model file input means is stored in the component information storage means. In addition, a scenario obtained from the requirement specification model file input by the requirement specification model file input means is stored in the scenario information storage means.

The action main information generation means generates action main element information which is a component for executing a procedure in the other format model based on the scenario information stored in the scenario information storage means. The element of the other format model generated by the operation main information generating means is stored in a computer-writable storage device.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is a block diagram of a computer for performing a required specification model conversion in the present embodiment. In the present embodiment, a matrix indicating processes, entities, and access relationships from processes to entities in information engineering, which is a comprehensive methodology for system development, is generated from the requirement specification model.

[0015] As a technology relating to information engineering, for example, Texas Instruments
uments, Inc. , "A Guide to In
formation Engineering usin
g the IEF "(Japanese title:" CASE Practical Guide "), ISBN4-8222-7136-6 is known.

The process referred to here refers to an element for executing access such as reference, update, input / output, etc., to system components, such as referring to a screen, updating a form, and the like. An entity is
For example, it is a system component, such as a screen or a form, which is accessed by a process.
The matrix refers to a table of an access relationship from a process that is a component of the system to an entity that is also a component of the system.

In FIG. 1, a processing device 102 is a computer such as a personal computer or a workstation. The main storage device of the processing device 102 or an external storage device connected to the processing device 102 includes a character name for identifying a character which is an element constituting the character information, an attribute for storing a value indicating a state of the character, and a character Character information storage unit 105 that stores a bitmap type indicating the appearance of the character, a scenario identifier that identifies a scenario that is an element constituting scenario information, and a scenario that stores a scene that constitutes the scenario Information storage unit 106, entity information storage unit 11 that stores entity information generated by entity information generation unit 108
1. Each storage unit includes a process information storage unit 112 that stores the process information generated by the process information generation unit 109 and a matrix information storage unit 115 that stores the matrix information generated by the matrix information generation unit.

The processing device 102 has a function based on a required specification model file input unit 104 for reading a required specification model file stored in a computer-readable input storage device 101 and character information extracted from a character information storage unit 105. Then, it is determined whether or not the character is a target of entity information generation based on the bitmap type of the character. If the target is a generation target, the entity information generation unit 108 that generates an entity and the scenario information extracted from the scenario information storage unit 106 are used. A process information generating unit 109 for generating a process;
And a matrix information generation unit 113 that generates a matrix based on the entity information stored in the entity information storage unit 111, the process information stored in the process information storage unit 112, and the scenario information stored in the scenario information storage unit 106. It has each processing unit. These processing units are specifically stored in a main storage device of the processing device 102 or an external storage device connected to the processing device 102,
It is a program module that constitutes the requirement specification model / other format model conversion program in the present embodiment,
The functions are realized by being executed by the processing device 102.

The entity information generation unit 108 determines whether to generate an entity from a character according to the entity information generation rules stored in the entity information generation rule unit 107. Process information generator 10
9 determines whether or not to generate a process from the scenario information according to the process information generation rule stored in the process information generation rule unit 110. Matrix information generation unit 1
13 determines whether to generate a matrix in accordance with the process information generation rules stored in the matrix information generation rule unit 114.

FIG. 2 shows a requirement specification model creation program 201 which is an external program, a requirement specification model / other format model conversion program executed by the processing device 102,
FIG. 9 is a diagram showing a procedure for connecting the external specification model input program 202 as an external program and performing a process from generation of a required specification model file to generation of a matrix file. The requirement specification model creation program 201 is a program for generating a requirement specification model file. The input storage device 101 stores a requirement specification model file created by the requirement specification model creation program 201. The processing device 102 converts the requirement specification model file 201 stored in the input storage device 101 into a matrix and stores the matrix in the output storage device 103. Output storage device 10
The other-format model file stored in 3 is input by another-format model input program 202 which is another external program.

FIG. 3 shows the details of the input storage device 101.

A required specification model file 301 is stored in the input storage device 101. The requirement specification model file 301 is composed of character information 302 that holds information on a character that is a component of the development target business, and scenario information 310 that holds information on a scenario that is a specific example of the target business.

The character information 302 has a character name 303 as an identifier, a bitmap type 304, an attribute 305 representing internal data of the character, and a message 308 as an internal procedure of the character. The attribute 305 includes an attribute name 306 as an identifier and an attribute value 307 representing a data value. The message 308 includes a message name 309 as an identifier.

The scenario information 310 is composed of a scenario name 311, which is an identifier, and scene information 312, which indicates a sequence of activation of a procedure between characters in the scenario.
The scene information 312 includes a message transmission character name 314 representing a character requesting activation of a procedure by message transmission, a message receiving character name 315 representing a character receiving a message and activating the procedure, and represents a procedure to be activated. It is composed of a message name 316, attribute comparison information 317 which is a condition for activating a procedure, and attribute substitution information 323 where processing is performed by activating the procedure. The attribute comparison information 317 includes an attribute comparison information identifier 318, a comparison source character name 319, a comparison source attribute name 320, a comparison destination character name 321, and a comparison destination attribute name 322.
It is composed of The attribute assignment information 323 includes an attribute assignment information identifier 324, an assignment source character name 325, an assignment source attribute name 326, an assignment destination character name 327, and an assignment destination attribute name 328.

The attribute comparison information identifier 318 is all attribute comparison information 317 of the scene information 312 to which it belongs.
Are unique. Also, the attribute assignment information identifier 324
Is unique in all the attribute assignment information 323 of the scene information 312 to which it belongs.

FIG. 4 shows the details of the character information storage unit 105. Character information 401 is stored in the character information storage unit 105.

The character information 401 has a character name 402 as an identifier, a bitmap type 403, an attribute 404 indicating internal data of the character, and a message 407 as an internal procedure of the character. The attribute 404 includes an attribute name 405 as an identifier and an attribute value 406 representing a data value. The message 407 includes a message name 408 which is an identifier.

FIG. 5 shows details of the scenario information storage unit 106. The scenario information storage unit 106 stores scenario information 501. The scenario information 501 includes a scenario name 502, which is an identifier, and scene information 503, which indicates a startup sequence of procedures between characters in the scenario. The scene information 503 includes a message transmission character name 505 representing a character requesting activation of a procedure by message transmission, a message receiving character name 506 representing a character receiving a message and activating the procedure, and represents a procedure to be activated. It is composed of a message name 507, attribute comparison information 508 which is a condition for activating a procedure, and attribute assignment information 514 for performing processing by activating the procedure. The attribute comparison information 508 is the attribute comparison information identifier 50
9, comparison source character name 510, comparison source attribute name 5
11, a comparison destination character name 512, and a comparison destination attribute name 513.

The attribute assignment information 514 includes an attribute assignment information identifier 515, an assignment source character name 516, an assignment source attribute name 517, an assignment destination character name 518, and an assignment destination attribute name 519.

The attribute comparison information identifier 509 is all attribute comparison information 508 of the scene information 503 to which it belongs.
Are unique. Also, an attribute assignment information identifier 515
Is unique in all the attribute assignment information 514 of the scene information 503 to which it belongs.

FIG. 6 is a detailed diagram of the entity information storage unit 111. The entity information storage unit 111 stores entity information 601 generated from the character information 401. Entity information 601
Is the entity name 6 for identifying the entity
02.

FIG. 7 is a detailed diagram of the process information storage unit 112. The process information storage unit 112 stores a message transmission character name 505, a message reception character name 506, a comparison source character name 510, a comparison destination character name 512, and an assignment source character name 51 in all scene information 503 in the scenario information 501.
6 and the process information generated from the substitution destination character name 518 are stored collectively for each scene.

The process information storage unit 112 stores process information 701 for each scene. The scene-based process information 701 includes a source scenario name 702 for identifying a source scenario, a source scene number 703 for identifying a source scene, and process information 704. The process information 704 includes a process identifier 705 for identifying a process, a source character name 706 for identifying a source character, and a role type 707 in a scene.

When the character that generates the process information has a role of transmitting a message or receiving a message,
“Message transmission” or “message reception” is set in the role type 707 in the scene. When the character of the process information generation source is an attribute comparison source or an attribute comparison destination, a pair of “attribute comparison source” or “attribute comparison destination” and an attribute comparison information identifier is set in the role type 707 in the scene. . If the character of the process information generation source is an attribute assignment source or an attribute assignment destination, the role type 707 in the scene is “attribute assignment source” or “attribute assignment destination”.
And an attribute assignment information identifier pair are set.

FIG. 8 is a detailed diagram of the matrix information storage unit 115. In the matrix information storage unit, access information from a process to an entity is stored collectively for each process.

The matrix information storage unit 115 stores access information 801 for each process. The process-specific access information 801 stores a process identifier 802 for identifying a process, and one-to-one entity access information 803, which is access information for an entity accessed by the process identified by the process identifier. You.

The one-process-one-entity access information 803 stores an access destination entity name 804 for identifying an access destination entity, and an access type 805 such as reference or update.

FIG. 9 shows an entity information generation rule unit 10.
FIG. 7 is a detailed view of FIG. Entity information generation rule 107
Includes a bitmap type search key 901 which is a key for searching whether or not to be entity information generation target based on the character bitmap type, and information on whether or not to be entity information generation target. There is entity information generation information 902 to be stored.

FIG. 10 shows a process information generation rule section 110.
FIG. The process information generation rule unit 110 includes:
A bitmap type search key 1001, which is a key for searching whether or not to be the process information generation target based on the character bitmap type, and information on whether or not the process information generation target is stored. There is process information generation information 1002.

FIG. 11 shows a matrix information generation rule section 11.
FIG. 4 is a detailed view of FIG. Matrix information generation rule section 114
Sets the access relationship between the process and the entity by classifying it by the role of the process and the entity in the scene. The matrix information generation rule unit 114 includes a process role search key 11 for specifying an access relation.
01, and an entity role search key 1102. The matrix information generation rule unit 114 also specifies whether to create an access relationship between the process and the entity by specifying the process role search key 1101 and the entity role search key 1102, and, if so, what type of access relationship. Access generation information 1103, which is information on whether or not to create, is stored.

Hereinafter, a conversion process from a required specification model to a matrix (required specification model conversion process) according to the present embodiment will be described.

FIG. 12 is a flowchart showing the flow of the required specification model conversion process in the processing device 102.

First, the required specification model file input unit 10
4 inputs the requirement specification model file 301 stored in the input storage device 101 and outputs the requirement specification model file 3
Character information 302 is extracted from 01 and stored as character information 401 in the character information storage unit 105. Similarly, the scenario information 310 extracted from the requirement specification model file 301 is stored in the scenario information storage unit 1.
06 is stored as scenario information 501 (step 1201).

Next, the entity information generation unit 108
The entity information generation rule unit 1 refers to the character information 401 stored in the character information storage unit 105.
An entity is generated in accordance with the entity information generation rule stored in 07. Entity information generation unit 108
Stores the generated entity in the entity information storage unit 1
11 is stored. (Step 1202).

Next, the process information generation unit 109 generates the scenario information 501 stored in the scenario information storage unit 106.
, And according to the process information generation rule stored in the process information generation rule unit 110, the scene-specific process information 7
01 is generated. The process information generation unit 109 stores the generated process information in the process information storage unit 112 (Step 1203).

Next, the matrix information generation unit 113 executes the entity information 601 stored in the entity information storage unit 111, the scenario information 501 stored in the scenario information storage unit 106, and the process information stored in the process information storage unit 112. With reference to the information 701, matrix information is generated according to the matrix information generation rule stored in the matrix information generation rule unit 114. The matrix information generation unit 113 stores the generated matrix information in the matrix information storage unit 115 (Step 1204).

Next, another format model file output unit 116
Integrates the generated entity information, process information, and matrix information and outputs them to the output storage device (step 1205).

FIG. 13 is a detailed flowchart of step 1202.

First, the entity information generation unit 108
The character information 401 stored in the character information storage unit 105 is obtained (step 1301).

Next, the entity information generating unit 108
The bitmap type 403 stored in the character information 401 is obtained. (Step 1302).

Next, the entity information generation unit 108
From the entity information generation rule 903 stored in the entity information generation rule unit 107, the bitmap type 40
The entity generation information 902 is acquired using the key 3 as a key (step 1303).

Next, the entity information generation unit 108
By referring to the acquired entity information generation information 902, it is checked whether or not the target is the entity information generation target (step 1304). If not, the entity information generation unit 108 does nothing. If it is a generation target, the entity information generation unit 108
Generate The entity information generation unit 108 sets the character name 401 as the entity name 602 (Step 1305).

The entity information generator 108 repeats steps 1301, 1302, 1303, 1304, and 1305 until all character information has been obtained.

FIG. 14 is a detailed flowchart of step 1203.

First, the process information generation unit 109 generates the scenario information 501 stored in the scenario information storage unit 106.
Scene information 503 is sequentially obtained (step 140).
1).

Next, the process information generating section 109 generates process information 701 for each scene, and sets the scenario name 502 as the source scenario name 702 and the scene number 504 as the source scene number 703 (step 140).
2).

Next, the process information generation unit 109 extracts the message transmission character name 50 from the scene information 503.
5 is acquired (step 1403).

Next, the process information generator 109 generates process information 704 based on the character name 505 (step 1404).

Next, the process information generation unit 109 extracts the message reception character name 50 from the scene information 503.
6 is obtained (step 1405).

Next, the process information generator 109 generates process information 704 based on the message receiving character name 506 (step 1406).

Next, the process information generator 109 acquires the attribute comparison information 508 of the scene information 503 (Step 1407).

Next, the process information generation unit 109 generates the process information 704 based on the comparison source character name 510 in the attribute comparison information 508 (step 140).
8).

Next, the process information generator 109 generates process information 704 based on the comparison target character name 512 (step 1409).

The process information generation unit 109 executes Step 1
407, step 1408, and step 1409,
Repeat until all attribute comparison information 508 is obtained.

Next, the process information generator 109 acquires the attribute assignment information 514 of the scene information 503 (step 1410).

Next, the process information generation unit 109 generates process information based on the substitution source character name 516 in the attribute substitution information 514 (step 1411).

Next, the process information generation unit 109 generates the process information 704 based on the substitution destination character name 518 in the attribute substitution information 514 (step 141).
2).

The process information generation unit 109 executes Step 1
410, step 1411, and step 1412,
The process is repeated until all the attribute assignment information 514 has been obtained.

The process information generation unit 109 executes Step 1
401, step 1402, step 1403, step 1404, step 1405, step 1406, step 1407, step 1408, step 140
9. Steps 1410, 1411 and 1412 are repeated until all scene information 503 has been obtained.

FIG. 15 shows steps 1404 and 1
406 is a detailed flowchart of step 1408, step 1409, step 1411, and step 1412.

First, the process information generation unit 109 generates the scene-specific process information 7 generated in step 1402.
From step 01, process information 704 having the same character name is searched (step 1501). If process information is found, step 1502, step 1503,
Step 1504, Step 1505, and Step 1
Step 506 is not performed.

If no process information is found, the process information generating unit 109 sets the character name 505, 506, 510, 512, 516, or 5 in the scene information.
Based on No. 18, the character information 401 having the same name among the character information 401 stored in the character information storage unit 105 is obtained (step 1502).

Next, the process information generation unit 109 converts the acquired character information 401 into bitmap type 4
03 (step 1503).

Next, the process information generation unit 109 acquires the process generation information 1002 from the process information generation rule unit 110 using the bitmap type 403 as a key (step 1504).

Next, the process information generation unit 109 refers to the acquired process generation information 1002 and checks whether or not it is a process information generation target (step 1505).

In the case of a process information generation target, the process information generation unit 109 generates the process information 704, and outputs a process identifier 705 and a generation source character name 706.
Is set in the process information 701 for each scene.

The process identifier 705 has only to be unique over all the process information. In the generation source character name 76, the generation source character name 505,
506, 510, 512, 516, or 518 are set (step 1506).

Next, the process information generation unit 109 adds the role type 707 in the scene to the process information (step 1507).

FIG. 16 is a detailed flowchart of step 1204.

First, the matrix information generation unit 113 stores the process information 7 for each scene from the process information storage unit 112.
01 is obtained (step 1601).

Next, the matrix information generation section 113 acquires the source scenario name 702 and the scene information 503 specified by the source scene number 703 stored in the per-scene process information 701 (step 160).
2).

Next, the matrix information generating section 113 acquires process information 704 from the process information 701 for each scene (step 1603).

Next, the matrix information generation unit 113 generates access information 801 for each process based on the process information 704 and the scene information 503, and
05 is set as the process identifier 802 (step 1604).

The matrix information generation unit 113 executes steps 1603, 1604, and 1605
Are repeated until all process information 704 stored in the scene-by-scene process information 701 has been acquired.

The matrix information generation section 113 repeats steps 1601, 1602, 1603, 1604, and 1605 until all the scene-based process information 701 stored in the process information storage section 112 has been obtained.

FIG. 17 is a detailed flowchart of step 1605.

At the beginning of FIG. 17, process information 704 is obtained in step 1603. Step 1
602 obtains scene information 503.

First, the matrix information generation unit 113 acquires the message transmission character name 505 from the scene information 503 (step 1701).

Next, the matrix information generation unit 113 executes the process information 704, the message transmission character name 5
The one-to-one entity access information 803 is generated based on the role type “message transmission” in the scene 05 and the scene, and stored in the per-process access information 801 (step 1702).

Next, the matrix information generation unit 113 acquires the message receiving character name 506 from the scene information 503 (step 1703).

Next, the matrix information generating section 113 executes the process information 704, the message receiving character name 5
06, and the one-process-to-one entity access information 803 is generated based on the role type "message received" in the scene and stored in the per-process access information 801 (step 1704).

Next, the matrix information generating section 113 sequentially acquires the attribute comparison information 508 from the scene information 503 (step 1705).

Next, the matrix information generation unit 113 calculates the comparison source character name 510 from the attribute comparison information 508.
Is acquired (step 1706).

Next, the matrix information generating unit 113 processes the one-to-one entity access information 803 based on the process information 704, the comparison source character name 510, the role type “attribute comparison source” in the scene, and the attribute comparison information identifier 509. Is generated and stored in the process-specific access information 801 (step 1707).

Next, the matrix information generation unit 113 calculates the comparison destination character name 512 from the attribute comparison information 508.
Is acquired (step 1708).

Next, the matrix information generation unit 113 obtains one-to-one entity access information based on the process information 704, the comparison target character name 512, the role type “attribute comparison destination” in the scene, and the attribute comparison information identifier 509. 803 is generated and stored in the process-specific access information 801 (step 1709).

The matrix information generation unit 113 converts the steps 1705, 1706, 1707, 1708, and 1709 into scene information 5
This process is repeated until all the attribute comparison information 508 possessed by No. 03 is obtained.

Next, the matrix information generating unit 113 acquires the attribute assignment information 514 from the scene information 503 (step 1710).

Next, the matrix information generation unit 113 calculates the attribute assignment source character name 5 from the attribute assignment information 514.
16 (step 1711).

Next, the matrix information generator 113 processes the process information 704, the attribute substitution source character name 51,
6. The one-process-to-one entity access information 803 is generated based on the role type “attribute assignment source” in the scene and the attribute assignment information identifier 515, and the per-process access information 8
01 (step 1712).

Next, the matrix information generation unit 113 calculates the attribute substitution destination character name 5 from the attribute substitution information 514.
18 is obtained (step 1713).

Next, the matrix information generating section 113 executes the process information 704,
8. One-process-one-entity access information 803 is generated based on the role type “attribute substitution destination” in the scene and the attribute substitution information identifier 515, and stored in the per-process access information 801 (step 1714).

The matrix information generation unit 113 executes the steps 1710, 1711, 1712, 1713, and 1714 as scene information 5
This process is repeated until all the attribute assignment information 514 of the information 03 has been acquired.

FIG. 18 shows steps 1702 and 1
704, Step 1707, Step 1709, Step 1712, and Step 1714 are detailed flowcharts.

At the beginning of FIG. 18, process information 70
4. Each character name 505 in the scene information 503,
506, 510, 512, 516, or 518, and the character name 50 in the scene information 503
5, the role type in the scene with the character name 506, the message type as the role type in the scene with the character name 506, the attribute type as the role type in the scene with the character name 510, and the attribute comparison information The identifier 509, the role type in the scene with the character name 512, “attribute comparison destination” and the attribute comparison information identifier 509,
Either “attribute assignment source” and attribute assignment information identifier 515 as the role type in the scene with the character name 516, or “attribute assignment destination” and attribute assignment information identifier 515 as the role type in the scene with the character name 518 are obtained. ing.

The role type in the scene obtained at the beginning of FIG. 18 is used by the matrix information generation unit 113 as an entity role search key 1102 in the matrix information generation rule unit 114. The character name obtained at the beginning of FIG.
Is used to obtain entity information 601.

First, the matrix information generation unit 113 reads the character names 505, 506, 510, 512, and 51 obtained at the beginning of FIG. 18 from the entity information storage unit 111.
6 or entity information 6 specified by 518
01 (step 1801). Entity information 6
If there is no 01, the process ends.

Next, the matrix information generation unit 113 sequentially acquires the role type 707 in the scene from the process information 704 (step 1802).

Next, the matrix information generation unit 113 determines the role type 70 in the scene acquired from the process information 704.
7 and the role types in the scene obtained at the beginning of FIG. 18 are compared. If both are the attribute comparison source or the attribute comparison destination and the attribute comparison information identifiers are different, nothing is performed (step 1803).

Similarly, if both are the attribute assignment source or attribute assignment destination and the attribute assignment information identifiers are different, nothing is performed (step 1804).

When the entity information 601 exists, the matrix information generation unit 113 sends the role type 707 in the scene stored in the process information 704 from the matrix information generation rule unit 114 and the role type 707 in the scene obtained at the beginning of FIG. The access generation information 1103 specified by the role type is obtained (step 1805).

Next, the matrix information generation unit 113 checks whether or not the access information is to be generated based on the access generation information 1103 (step 1806). If not, the process ends.

In the case of a generation target, the matrix information generation unit 1
13 searches the process-by-process access information 801 for one-to-one entity access information 803 where the access destination entity name 804 is the same as the character name obtained at the beginning of FIG. 18 (step 1807).

If the one-to-one entity access information 803 is not found, the matrix information generator 113 newly generates one-to-one entity access information 803 (step 1808).

Next, the matrix information generating unit 113 adds an access type to the one-to-one entity access information 803 obtained in step 1807 or the one-to-one entity access information 803 generated in step 1808 (step 180).
9).

The matrix information generation unit 113 executes steps 1802, 1803, 1804, 1805, 1806, 1807,
Steps 1808 and 1809 are repeated until acquisition of the role types 707 for all scenes included in the process information 704 is completed.

FIG. 19 shows a specific example of a character in the requirement specification model created by the requirement specification model creation program 201.

The requirement specification model creation program 201 creates a character set 1901. A set of characters 1901 includes characters 1902, 1
Characters 903, 1904, 1906, and 1907 are stored.

The character 1902 “sales person” has the bitmap type “human”. Character 1903
The “product database” has a bitmap type “graphic”. The character 1904 “terminal” has a bitmap type “screen”. The character 1906 “property” has the bitmap type “building”. Character 190
7 “Customer” has the bitmap type “Human”. The attributes and messages of each character are 1908,
1909, 1910, 1911 and 1912.

FIG. 20 shows a specific example of a scenario in the requirement specification model created by the requirement specification model creation program 201.

The scenario 2001 “sales business” has a scene 2002 with a scene number of 1 and a scene 2003 with a scene number of 2.

In the scene 2002, the character transmitting the message is the character 2004 “sales manager”. The character receiving the message is the character 2005 “terminal”. The comparison source character of the attribute comparison is the character 2007 “property”. The comparison target character for attribute comparison is character 2.
008 “customer”. The substitution source character of the attribute substitution is the character 2007 “property”. The substitution destination character of the attribute substitution is the character 2006 “product database”.

In the scene 2003, the character transmitting the message is the character 2012 “terminal”.
It is. The character receiving the message is character 2011 “salesman”. The comparison source character of the attribute comparison is the character 2014 “product database”. The comparison target character of the attribute comparison is the character 2015 “property”. The substitution source character of the attribute substitution is the character 2014 “product database”. The substitution destination character of the attribute substitution is the character 2012 “terminal”.

FIG. 21 shows a matrix 2101 obtained by converting the required specification model shown in FIGS. 19 and 20 by the processing device 103. The matrix 2101 includes a process list 2102, an entity list 2103, and an access type from a process to an entity.

In this embodiment, the processing device 102 sets the process identifier to “a unique number for all processes”.
+ “:” + “Generation source character name” + “:” + “scenario name” + “:” + “scene number”.

[0126]

As described above, according to the present invention,
At the time of conversion from the requirement specification model to the other format model, it is possible to generate the main component of the operation or the component of the other format model to be operated.

[Brief description of the drawings]

FIG. 1 is a schematic configuration diagram of a system for performing a model conversion process to be requested in an embodiment of the present invention.

FIG. 2 is a schematic diagram showing cooperation between a required specification model / other format model conversion program and an external program.

FIG. 3 is a detailed view of a required specification model file stored in an input storage device.

FIG. 4 is a detailed diagram of a character information storage unit.

FIG. 5 is a detailed diagram of a scenario information storage unit.

FIG. 6 is a detailed diagram of an entity information storage unit.

FIG. 7 is a detailed diagram of a process information storage unit.

FIG. 8 is a detailed diagram of a matrix information storage unit.

FIG. 9 is a detailed diagram of an entity information generation rule unit.

FIG. 10 is a detailed diagram of a process information generation rule unit.

FIG. 11 is a detailed diagram of a matrix information generation rule unit.

FIG. 12 is a flowchart illustrating an outline of a required specification model conversion process.

FIG. 13 is a detailed flowchart of an entity information generation process.

FIG. 14 is a detailed flowchart of a process information generation process.

FIG. 15 is a detailed flowchart of a process of generating process information based on a character name.

FIG. 16 is a detailed flowchart of a matrix information generation process.

FIG. 17 is a detailed flowchart of a process of generating access information to an entity from a process.

FIG. 18 is a detailed flowchart of a process of generating access information from one process to one entity.

FIG. 19 is an explanatory diagram of a character of a requirement specification model created by a requirement specification model creation program.

FIG. 20 is an explanatory diagram of a scenario of a requirement specification model created by a requirement specification model creation program.

FIG. 21 is an explanatory diagram of a matrix obtained by conversion by a required specification model conversion process.

[Explanation of symbols]

 101 ... input storage device 102 ... processing device 103 ... output storage device 104 ... required specification model file input unit 105 ... character information storage unit 106 ... scenario information storage unit 107 ... Entity information generation storage unit 108 Entity information generation unit 109 Process information generation unit 110 Process information generation rule unit 111 Entity information storage unit 112 Process information storage unit 113 Matrix information generation unit 114 ・ ・ ・ Matrix information generation rule unit 115 ・ ・ ・ Matrix information storage unit 116 ・ ・ ・ Other format model file output unit

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Naoki Igarashi 2-4-1, Ichibancho, Aoba-ku, Sendai, Miyagi Prefecture Within Hitachi Tohoku Software Co., Ltd. (72) Inventor Noboru Takahashi Ichiban, Aoba-ku, Sendai, Miyagi Hitachi, Tohoku Software Co., Ltd., (2-1) 2-4-1, Machi Morita 890 Kashimada, Saiwai-ku, Kawasaki-shi, Kanagawa 12-12 Hitachi, Ltd. Information Systems Division F-term (reference) 5B076 DD02

Claims (2)

[Claims] 1. Component information that records names held by elements composing a system development target business, display graphic information expressing appearance, data names, and procedure names, and a procedure activation sequence between the components. A requirement specification model that converts a requirement specification model defined by recorded procedure invocation sequence information or a scenario that holds procedure invocation sequence information in which the procedure invocation sequence of the above-described components is recorded into a model in another format. In the other format model converter, a requirement specification model file input means for reading a requirement specification model file comprising the requirement specification model stored in a computer-readable storage device, and the requirement specification input by the requirement specification model file input means Component information storage means for storing the component information obtained from the model file A scenario information storage unit for storing a scenario obtained from the requirement specification model file input by the requirement specification model file input unit; and executing the procedure based on the scenario information stored in the scenario information storage unit. A requirement specification model comprising: operation main information generation means for generating operation main element information as constituent elements; and another format model file output means for storing the operation main information in a computer-writable storage device. Other format model converter. 2. Component information that records names held by elements constituting a system development target business, display graphic information expressing appearance, data names, and procedure names, and a procedure activation sequence between the components. A requirement specification model that converts a requirement specification model defined by recorded procedure invocation sequence information or a scenario that holds procedure invocation sequence information in which the procedure invocation sequence of the above-described components is recorded into a model in another format. In the other format model conversion method, a requirement specification model file stored in a computer-readable storage device and holding the requirement specification model is read, and a component that executes the above-described procedure in the other format model based on the scenario information. Generate certain operation main element information and store the operation main information in a computer-writable storage device Required specifications Model other formal model conversion method according to claim Rukoto.