JPH0981611A - Input method and acquisition method for request specification - Google Patents

Abstract

PROBLEM TO BE SOLVED: To acquire the request specifications of a development object from a customer and to prepare the entire request specifications just by the interactive operation of a screen using a scenario editor and a model editor, etc. SOLUTION: On a computer, elements for constituting the development object are arranged by using fundamental constituting element parts on the scenario editor and constituting element information is set. Then, a procedure activation chain is defined by specifying the procedure of defined constituting elements in an order for performing calling and activation chain information is generated inside the computer as scenario data. Then, a defined scenario group is selected and reflected on the model editor and the entire request specifications are prepared. At the time, a procedure title to be called next is obtained from the defined procedure chain information and a program for performing animation display on a connection line between the constituting elements is generated. Finally, by executing a generated animation program, the procedure activation chain of the development object is animation displayed and the request specifications are prepared.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to acquisition of required specifications in developing a development target application using a computer, and more particularly to a method of visualizing and acquiring the required specifications and a method of visually displaying them. Acquiring refers to interactively making various modifications and changes to the visualized requirement specifications to finalize the completed requirement specifications.

[0002]

2. Description of the Related Art Software development is essential for the development of electronic devices such as computers. In particular, at the stage of studying new models and methods, it is important to input sketches of various device configurations as models, perform simulations, evaluate the results, and repeat this to examine the design policy. . It is also important to convey the design policy to the parties concerned accurately and in an easy-to-understand manner.

Similarly, in the development of software application systems, it is an important task to interactively create required specifications in the design stage of required specifications and present them to customers in a visually easy-to-understand form. It has become to.

On the other hand, in order to create a required specification in system development, a request is heard between a customer, a system engineer, and a person who acquires the required specification from the customer and confirms the specification of the system. This process is repeated until the engineer finally creates the required specifications, has the customer evaluate them, and there is no change and the specifications that meet the customer's requirements are made. The system developer implements the system based on the requirements specification determined by the customer and the system engineer. If there is a difference between the realized system and the customer's request, the required specifications are recreated and the system is realized again.

For example, “Information Processing Society of Japan, Object-Oriented Software Technology Symposium Proceedings, pp. 1-11 (199
1), ODETTE: Design support construction environment based on object-oriented CLOS ”, first, the parts to be designed are defined by a programming language program, and the actual entity of the procedure held by the parts is also defined. Set by writing a program. Next, the setting of the display graphic information of the component is first arbitrarily drawn by the operator with a mouse or the like, and is associated with the component information previously programmed and defined. Next, an animation program is defined by the program and set in the part information and display graphic information. In setting the animation program, first, the procedure for starting the animation is set in the above component information. Then, a procedure for animation is defined using the above-mentioned display graphic information and set in the above-mentioned display graphic information.
Next, the operator interactively creates part information in the memory of the computer. After the generation is completed, the simulation is executed by executing the procedure of component information. The result of the simulation is displayed by executing the animation program. The execution of the animation program is specifically performed as follows.

First, the animation starting procedure is executed, and the animation procedure is started and executed. By executing the animation procedure, the display graphic information is updated. As a result, the figure is transformed so as to match the new display figure information, and the animation is executed.

In the prior arts described in Japanese Patent Laid-Open No. 4-348428 and Japanese Patent Laid-Open No. 5-210955, the data and procedures for holding the target parts of the designed system are programming languages. We provide an environment for interactively defining display graphics of parts and behaviors when the display graphics are realized. In addition, the simulation of the procedure held by the part is executed, and the operation image of the display figure when the part is realized is displayed as an animation, and the specifications at the design stage and the image at the time of realization are visually confirmed to evaluate the specifications. There is.
In order to create specifications that better meet customer requirements, it is necessary to repeatedly evaluate visual specifications.

Regarding the description of the required specifications, there is a description method called a scenario. A scenario is a method that directly describes the external behavior of the system from the user's perspective. For example, Pei Hsia et.al., "Formal Approach to Scenari
Analysis ", IEEE Software, March 1994, p33-41 (1994)
In the telephone switching system as an example, a procedure for inputting, confirming, and prototyping based on a group of input scenarios based on a scenario tree of operation names of end users and calling of system functions is shown.

[0009]

When the above-mentioned conventional technique is applied, the system engineer must be able to program, but in the conventional business form, for example, a person who listens to the required specifications from the customer generally needs the programming technique. Therefore, it is necessary to acquire programming skills to visualize the required specifications. Therefore, it was quite difficult for many system engineers to use.

Further, in the above-mentioned prior art, when the required specifications are changed, especially when the constituent parts are changed, it is necessary to redefine the program of the constituent parts. Generally, the program is changed while evaluating the specifications. It was not easy to add.

Further, in order to visualize and create the required specifications, it is necessary to abstract the content heard from the customer as a procedure, and then program and input it. The abstraction process for migrating the requirement specifications of the real world to the computer world is generally not easy for a system engineer who listens to the requirement specifications at a position close to the real world.

Then, a change in specifications that occurs when a customer has evaluated the created visualization requirement specifications, for example, the addition of exceptional processing, is performed as a program showing the requirement specifications of the entire development target at once. It was difficult to change to create.

When the entire requirement specification is created, it is expected that a large number of partially visualized requirement specifications input by the user will be generated. Further, there may be a plurality of users who input. Therefore, it can be expected that it will be difficult for the user to grasp all the visualized requirement specifications that have been input, as well as the visualized requirement specifications that are edited to create the specifications that meet the customer's requirements.

Further, when the user intentionally specifies a relation from among a large number of visualized requirement specifications while inputting the requirement specifications, it is not easy to grasp the relation between the visualized requirement specifications. There wasn't.

Further, the scenario description method of Hsia's paper does not take into consideration the fact that the scenario is easy to understand, and it is difficult for the user to confirm each scenario. Further, since only the operation name and the function call are described, it is difficult to express the specifications regarding the flow of data and the change of the terminal screen. Moreover, it did not fully mention the method of efficiently generating prototyping from the input scenario group. In addition, since the scenario groups are entered in a single tree, it is difficult to display and interactively edit the complex and diverse scenario groups due to screen size restrictions.

A first object of the present invention is to define an activation chain of components and procedures between components by a programless interactive operation when a system engineer obtains a required specification to be developed from a customer. is there.

A second object of the present invention is to make it possible to input the components to be input and the procedures held by the components as specific examples of real-world operations when acquiring the required specifications to be developed. is there.

A third object of the present invention is to enable input of constituent elements to be input and the flow of procedures held by the constituent elements in fine units when acquiring the required specifications to be developed.

A fourth object of the present invention is to grasp all of the visualized requirement specifications inputted by the user, which constitute the entire requirement specification.

A fifth object of the present invention is to explicitly display a visualized relationship between requirements even if the user intentionally specifies the relationship while inputting the requirements.

[0021]

In order to achieve the above object, in the present invention, a scenario editor is used to input required specifications in a scenario. A scenario is a sequence in which a procedure held by a component to be developed is called, is a continuous chain without branching, and is a partial specification of the entire required specification.
In addition, the elements that make up the scenario are input in concrete cases. What is the scenario editor? A function for interactively setting and defining scenario components from the basic parts that are the source of the scenario components, and an interactive operation function for defining the procedure invocation chain between the components. Consists of. The basic component initially holds no information, so it can be defined as any element that constitutes the development target. Also, scenario data is generated inside the computer from the scenario input by the interactive operation.

Further, in order to achieve the above object, in the present invention, a visualized overall requirement specification is created using a model editor. The model editor has a function of integrating the scenario groups defined by the scenario editor and a function of displaying the created requirement specifications as an animation. Further, from the above-mentioned integrated scenario group, a definition program of the constituent elements of the entire requirement specification and a program for animation-displaying the chain operation from the procedure invocation chain information of the scenario are generated.

In order to achieve the above object, the present invention creates common information from a scenario input using a scenario editor. The scenario editor generates common information according to an operation in which the user intentionally specifies a relation between scenarios when the scenario is input to the scenario editor. The common information is scenario information that is common to the scenarios designated by the user.

In order to achieve the above object, the present invention creates an overall scenario relationship by visualizing all the scenario groups input to create the overall requirement specifications using the scenario relationship diagram editor. The scenario relation diagram editor is a function to generate the whole scenario related information from the common information of the scenario group generated by the above scenario editor, and the generated whole scenario related information to find all the scenarios in the whole requirement specification. It consists of a function of visualizing and displaying the relation between scenarios, and an interactive operation function for acquiring the relation information between scenarios.

[0025]

By using the scenario editor of the present invention, the constituent elements of the scenario are interactively set and defined, the procedure invocation chain between the constituent elements is defined, and the scenario data is generated in the computer. A system engineer who does not have one can easily create visualized requirements.

Further, by using the scenario editor of the present invention, any element constituting the development target can be interactively set with the constituent elements of the scenario from the definable basic parts.
By defining, the requirement specifications can be directly input to the visualized requirement world on a computer in the form of concrete examples in the real world.

The scenario group, which is obtained by subdividing the requirement specifications visualized using the scenario editor of the invention described above, is integrated using the model editor, and the definition program of the components of the overall requirement specification and the procedure activation of the scenario are started. By generating a program that animates the behavior of the chain from the chain information and creating a visualized overall requirement specification, when the requirement specification is changed or added, the input requirement specifications are subdivided interactively. By changing / adding to
It is possible to easily change the visualized overall requirement specifications.

Further, by using the scenario relation diagram editor of the above-mentioned invention, all scenarios in the overall requirement specifications are visualized,
By displaying the relationships between the scenarios, it is possible to easily grasp the whole of the visualized requirement specifications that have been subdivided and input to create the overall requirement specifications and the relationship between the requirement specifications.

[0029]

Embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a flowchart showing a procedure of a method of inputting and displaying a required specification according to an embodiment of the present invention. FIG.
The schematic configuration of the requirement specification creating system used in this embodiment is shown in FIG.

First, the procedure of the method for inputting and displaying the required specifications according to the embodiment of the present invention will be described with reference to FIG.

First, the customer and the system engineer arrange the constituent elements of the development target on a scenario editor by using the basic parts and the constituent elements that meet the required specifications on the scenario editor (102). Next, the component information of the component is defined (103). The component information to be defined is defined by an interactive operation for each component name, held data name, procedure name, and display figure. Then, the procedure activation chain is defined by designating the procedures of the defined constituent elements in the order of activation (105). The defined procedure invocation chain is displayed on the scenario editor. When the scenario definition is completed, the scenario information defined above is generated in the computer as scenario data (106). Next, it is defined that the procedure invocation chain defined in the scenario is common to the procedure invocation chain defined in another scenario (104).

Then, by selecting the scenario group defined above, the related information of the entire scenario is created and displayed (11
Four).

Next, the scenario group defined above is selected in order to create the entire visualization requirement specification (108). Then, the selected scenario group is displayed on the model editor, and the scenario group is integrated for each component (109). Then, the connection graphic is displayed on the model editor from the display graphic of the component and the procedure activation chain information between each component. Further, the procedure name to be called next is acquired from the defined procedure invocation chain information, and a program for displaying an animation on the connection between the constituent elements is generated (110).

By executing the entire requirement specification created by integrating the scenario groups, the procedure invocation chain to be developed is animated (113) to create a visualized requirement specification.

Next, an outline of the requirement specification creating system used in this embodiment will be described. As shown in FIG. 2, the requirement specification creating system used in the procedure (FIG. 1) of the method of inputting and displaying the visualized requirement specifications of the present embodiment has a memory 201, a CPU
213 and a terminal 214. In memory 201,
Programming language processor 202, scenario editor 203,
Model editor 204 and scenario relation diagram editor 216
Is installed. By operating these in accordance with the procedure of inputting and displaying the visualized requirement specifications, the scenario information 206, the overall requirement specification information 209, the overall requirement specification program 226, and the overall scenario that are definition information of each scenario input by the operator. Related information 218 is generated. The scenario name 206 of the scenario is used as the scenario information 206.
15, the scenario unique number 221, each piece of component information 207 configuring the scenario, the procedure invocation chain information 208, and the commonization information 217 are held. As the component information 207, the component graphic information 222, the component name 223, the data name 224, and the procedure name 225 are held. Also, common information 2
The reference information 220 and the reference information 219 are held as 17. Then, as the overall requirement specification information 209, the overall component element information 210 and the overall procedure invocation chain definition 211 are held. Then, as the overall requirement specification program 226, an overall constituent element program 227, an overall procedure invocation chain program 228, and a chain action animation program 229 are held.

The programming language processor 202 uses CLOS (Co
It is a language processing system that meets the specifications of the mmon Lisp Object System) and has functions such as class definition, instance generation, generic function control, and slot access. CLOS
The language specification of is, for example, DGBoblow, et. Al., ″ Common
Lisp Object System Specification ″, ANSI X3J13Doc
ument00-002R (1988).

As shown in FIG. 3, the scenario editor 203
The screen configuration of is composed of an area 301 for registering basic parts for creating the constituent elements of the scenario, a scenario definition area 304, and an input area 305 for displaying a comment from the system or for setting by the operator. In this embodiment, as the basic parts to be registered in order to create the constituents of the scenario, the basic parts 302 that are static constituents and the constituents as the arguments held by the procedure invocation chain are stored. A basic component 303 to be prepared is prepared and displayed in an area 301 in which the basic component is registered. A group of parts drawn on the scenario definition area 304 constitutes one scenario. Components 306, 307, 308 are static components that hold the procedures in this scenario,
Created from 2.

The argument component 309 is a component that cannot hold a procedure, and is an argument held by the procedure invocation chain defined in the scenario. Connection 310 is a component 306,
Between 307, a connection 311 indicates that a procedure invocation chain is defined between the components 307 and 308. The correspondence between the area of each component on the scenario definition area 304 and the component information 207 will be described using the component 306. As shown in FIG. 4, in the component information 207 of the component, the component graphic 222 is in the component graphic display area 401, the component name 223 is in the component name display area 402, and the data name 224.
Is displayed in the data name display area 403, and the procedure name 225 is displayed in the procedure name area 404. Also, the data specific value display area 405
Indicates the specific value held by the data.

As shown in FIG. 5, the model editor 204
Integrates the entered scenarios to create the overall requirements,
An area 501 for visualizing display and an area 502 for displaying a comment from the system. Parts groups 503, 504, 505 drawn on the overall requirement specification visualization display area 501 of FIG.
Is a component of the visualized overall requirement specification, and displays a component graphic 222 of the component defined in the scenario.
Connection lines 506 and 507 represent that the procedure invocation chain is defined between the components in the overall requirement specification. The balloon 508 displays the procedure name 510 to be called next from the calling component 503 to the component 504 holding the procedure to be called next, and moves on the connection line 507. Further, the display graphic 509 of the argument component is a display graphic of the component corresponding to the argument held by the procedure to be called next from the component 503 of the calling source to the component 504 holding the procedure to be called next. Display 509 and move on connection 507.

Next, the procedure of the method of inputting and displaying the required specifications in this embodiment will be described in detail by taking the sales management system as an example.

First, one scenario of the sales management system is input on the scenario editor in response to the operator's input (step 101). First, the elements constituting the scenario are arranged (step 102), and the constituent element information 207 of the constituent elements is set (step 103).

FIG. 6 is a detailed flowchart of procedures 102 and 103 for arranging scenario components and setting component information. 7 and 9 to 12 are examples of screen displays in the procedure of FIG. Procedures 102 and 103 for arranging scenario components and setting component information will be described in detail below with reference to FIGS. 6, 7, and 9 to 12.

First, the operator edits the scenario editor.
Display 203 (step 601). Then, as shown in FIG. 7, the components of the scenario are arranged according to the system comment 701 of the displayed scenario editor 203. First, the operator selects the basic parts 302 and 303 which are the elements constituting the scenario of the displayed scenario editor (step 602). Next, the selected basic component is placed in the scenario definition area 304 (step 603). Figure 7
Basic parts 702 and 70 placed in the scenario definition area 304 of
Reference numerals 3, 704, and 705 show the state in which the graphics of the constituent elements of the scenario are arranged (step 603).

Next, the constituent elements of the scenario for which the constituent element information is set are selected from the several constituent elements shown in FIG. 7 (step 604). Next, the component information of the selected component is defined (step 605). First, in order to define the name of the selected component 702 (step 606), the name definition menu 902 in the component menu 901 is selected from the menu of the scenario editor 203. FIG.
Indicates that the menu 902 is selected. Then, according to the displayed system comment 903 of the scenario editor 203, the names of the constituent elements of the scenario are input. Here, the component name of the component 702 is defined as “customer” 904. Then, as shown in FIG. 10, the component name defined in the component 1001 is displayed.

Next, in order to define the data name held by the selected component 1005 (step 607), from the menu of the scenario editor 203, the data name definition menu 1002 in the component menu 901 is selected. Select. FIG.
Indicates that the menu 1002 is selected. Then, according to the system comment 1003 of the displayed scenario editor 203, the data name is input. Here are the components
One of the data names of 1005 is defined as "customer name" 1004. Then, the "customer name" 1004 defined in the component 1101 is displayed as the data name 1105 of the component.

Then, in order to define the procedure name held by the selected component 1001 (step 608), the procedure name definition menu 1102 in the component menu 901 is selected from the menu of the scenario editor 203. FIG.
Shows that the menu 1102 is selected. Then, according to the displayed system comment 1103 of the scenario editor 203, the name of the procedure is input. Here, one of the procedure names of the component 1001 is defined as “request for quotation” 1104. Then, the “quotation request” 11 defined in the component 1201
04 is displayed as the procedure name 1206 of the component 1201.

Then, in order to define the component graphic of the selected component 1201 (step 609), the component graphic definition menu in the component menu 901 is selected from the menu of the scenario editor 203 as shown in FIG. Select 1202. FIG. 12 shows how the menu 1202 is selected. By selecting the menu 1202, the graphic definition editor 1203 is activated and displayed. Scenario editor 203
According to the system comment 1204 displayed above, the component graphic 1205 of the selected component is defined. And
As shown in FIG. 14, which will be described later, the constituent element graphic 1205 defined in the constituent element 1403 is displayed as the constituent element graphic 1413 of the constituent element.

Definition of data name held by the above-mentioned component (step 607), definition of procedure name held by the component (step 608), and definition of component figure of the component (step 609) The order of doing is not specified. Next, an activation chain of procedures held by each set component is defined (step 105).

FIG. 13 is a detailed flowchart of the procedure 105 for defining the activation chain of the procedure held by each component. 14 to 16 are examples of screen displays in the procedure of FIG. Hereinafter, with reference to FIGS. 13 to 16,
The procedure 105 for defining the procedure invocation chain of the scenario will be described in detail.

First, the operator selects the procedure activation chain definition menu 1402 of the scenario menu 1401 from the displayed menu of the scenario editor 203.
FIG. 14 shows how the menu 1402 is selected. On the screen, constituent elements 1403, 1404, 1405, 1406 of the scenario generated in steps 102, 103 of FIG. 1 are displayed.
Next, the scenario name is set to define the procedure invocation chain (step 1301). First, a scenario name is defined according to the system comment 1408 of the displayed scenario editor 203 (step 1304). Here, "general quotation service" 1409 is input. Next, enter the scenario name "general quotation service" 1409 you entered in the scenario editor.
It is displayed 1410 on the scenario definition area 304 in 203 (step 1305).

Next, the activation chain of the procedure held by the component is defined (step 1306). First, according to the system comment 1501 of the displayed scenario editor 203,
The component holding the procedure to be activated is selected (step 1302). In FIG. 14, the component 1403 that holds the procedure to be initially activated in the scenario is selected. In FIG. 15, the component 1404 holding the procedure to be activated next to the procedure 1411 defined in FIG. 14 is selected. Next, it is determined whether or not the procedure name to be called is in the component (step 1307). When there is a procedure to be called, the procedure name 1411 or 1502 to be called is selected from the procedure list in the selected constituent elements 1403 and 1404 (step
1308).

Next, an arrow line representing the procedure invocation chain is drawn on the scenario editor 203 (step 1303). An arrow line 1407 that represents a procedure invocation sequence that is initially activated is a scenario name 141 displayed on the scenario definition area 304.
A component 1403 that holds 0 and the procedure 1411 to be activated initially
Draw in between. The arrow line 1503 expressing the procedure invocation sequence after the initial stage is a component holding the previously activated procedure 1411.
Draw between 1403 and the component 1404 that holds the procedure 1502 to be activated. Then, the procedure name to be activated is indicated on the arrow lines 1407 and 1503 that represent the chain between the components, and the activation chain name 1412,
It is drawn as 1504 (step 1311). Next, when the above defined activation chain holds the arguments and the activation conditions of the procedure activation chain, each information is set as a chain attribute (step 1312).

On the other hand, if the procedure to be called does not exist in the component, the activation chain name is set. First, the operator determines whether to define the activation chain name by himself (step 1314). When the operator himself defines the activation chain name, he inputs the name of the activation chain (step 1309). On the other hand, when the operator does not define the activation chain name himself, the system defines a name other than the procedure name held by the selected component as the activation chain name (step 1315). Then, the defined invocation chain name is added to the procedure name 225 of the component information 207 as the procedure name to be called in the component and drawn as the procedure name of the component drawn on the scenario editor 203 ( Step 1310). Next, the input activation chain name is drawn on the arrow representing the chain (step 1311) and the chain attribute is set (step 1312).

Then, when ending the chain definition, as shown in FIG. 16, the definition end menu 1601 of the scenario menu 1401 is selected from the menu of the scenario editor 203 (step 1313). Then, when the definition of the procedure invocation chain is completed, the relationship in which the procedure invocation chain is defined among the components is displayed by connecting lines 1602 and 1603 (step 106). Next, the scenario data held inside the computer of the scenario input in steps 102, 103 and 105 is generated (step
1316).

FIG. 17 is a detailed flowchart of the procedure 106 for generating the data held inside the scenario computer. FIG. 34 shows an example of scenario data generated by the procedure of FIG. 17 with respect to the scenario (FIG. 16) input by the procedure of step 101. Hereinafter, FIG. 16, FIG. 17 and FIG.
The procedure 106 for generating the held data in the computer of the scenario will be described in detail using.

First, the scenario name 1410 defined by the operator is acquired from the input scenario (step 1712),
A unique number 3402 for managing a scenario is generated (step 1703). Then, with respect to the acquired scenario name 1410 and the generated scenario specific number 3402, the scenario name 215 and the scenario specific number 221 (FIG. 34 (a)) of the scenario information held inside the computer are generated (step 1
713). Here, “general quotation service” 1410 acquired as the scenario name 215 and “1” 3402 as the generated scenario unique number 221 are generated as the scenario information 206 held inside the computer.

Next, the constituent element information of the constituent elements is generated from the input scenario as internal computer data (step 1701). First, the constituent elements on the scenario editor 203 are analyzed (step 1702). In step 1702, first, the components 1403, 1404, 14 input on the scenario editor are input.
Get the component name 1413 from the information of 05 and 1406 (step
1704), the component element graphic 1414 and the display position are acquired as the component element graphic information (step 1705), and the data name 16
04, ... Is acquired (step 1706), and the procedure name 1411 is acquired (step 1707).

Then, scenario information 206 (FIG. 34 (b)) for the component information held inside the computer is generated corresponding to the obtained component information (step 170).
8). Here, the acquired component name 141 shown in FIG.
For “3”, “customer” 3404 is generated as the component name 223 of the scenario information held inside the computer. In addition, with respect to the acquired component graphic 1414 and the display position, the component graphic information 222 of the scenario information held inside the computer.
As the coordinates of the figure and the pattern data (340 in FIG. 34 (b)).
7, 3408) is generated. Data name of the acquired component 4
03, the data name of the component inside the computer 224
(3405 in FIG. 34B) is generated. With respect to the acquired procedure name 404 of the component, the procedure name 225 (3406 of FIG. 34B) of the component is generated inside the computer.

Next, procedure invocation chain information is generated as computer internal data from the procedure invocation chain defined by the scenario editor 203 (step 1709). First, the definition history of the procedure invocation chain defined on the scenario editor 203 is acquired from the interactive operation information (step 1710). And
From the acquired history information of the procedure invocation chain definition, scenario information (FIG. 34 (c)) regarding the procedure invocation chain between the constituent elements held inside the computer is generated (step 1711).

FIG. 8 is a detailed flowchart of the procedure 1711 for generating the scenario information regarding the procedure invocation chain between the constituent elements held in the computer from the acquired history information of the procedure invocation chain definition. Hereinafter, the procedure for generating the scenario information regarding the procedure invocation chain between the components held in the computer from the acquired history information of the procedure invocation chain definition will be described in detail with reference to FIG.

First, the procedure information to be activated is generated from the history information of the procedure activation chain definition (step 80).
1). First, the procedure name to be activated from the acquired history information is set as the procedure activation chain information (step 802). Then, the component holding the procedure is set as the procedure information to be activated (step 803).

Next, each information set as the chain attribute of the procedure invocation chain is organized by information type and is generated as chain attribute information (step 804). First, with respect to the start condition for starting the internal procedure, the start condition information is generated from the history information in which the chain attribute is set (step 80).
Five). Next, the argument information held by the procedure invocation chain is generated (step 806). Then, the substitution information held by the procedure invocation chain is generated (step 807).

Then, it is determined whether or not there is a procedure to be activated next, and if there is a procedure, the above procedure is repeated, and if not, the generation of the procedure activation chain information ends.

Next, setting of the chain attribute (step 1312) of the procedure invocation chain definition (FIG. 13) will be described using a concrete example.

FIG. 18 is a detailed flowchart of the procedure 1312 for setting the chain attribute held by the procedure invocation chain. Hereinafter, the procedure for setting the chain attribute held by the procedure invocation chain will be described in detail with reference to FIG.

The operator sets an argument component as an argument of the procedure invocation chain as a chain attribute held by the procedure invocation chain (step 1801). As a chain attribute, the operator sets a concrete value in the data held by the constituent element (step 1802) or a concrete value of the data held by another constituent element (step 1803). Then, as a chain attribute, the operator sets a condition statement as a condition for starting the procedure (step 1804) or a condition based on a concrete value of data held by the component (step 1805). The above argument component which is a chain attribute,
There is no limitation on the order in which the operator sets the concrete value of the data, the start condition statement, and the concrete value of the start condition data.

Next, the setting of the above chain attributes held by the procedure invocation chain will be described. First, FIG. 21 is a detailed flowchart of a procedure 1801 for setting an argument component as a chain attribute held by the procedure invocation chain. Also,
FIG. 19 is a screen display example of the procedure in FIG. Hereinafter, with reference to FIGS. 21 and 19, a procedure 1801 for setting an argument component as a chain attribute held by the procedure invocation chain
Will be described in detail.

First, as shown in FIG. 14, the operator selects the procedure activation chain definition menu 1402 of the scenario menu 1401 from the menu of the displayed scenario editor 203 to activate the procedure activation chain definition function,
Draw an invocation chain 1407 of a procedure that wants to hold an argument component as an argument as a chain attribute. Next, the argument component is set to the chain attribute of the drawn activation chain (step 18).
01). First, the argument setting menu 1902 of the message menu 1901 is selected from the menu of the scenario editor 203 (step 2101).

FIG. 19 shows how the menu 1902 is selected. On the screen, constituent elements 1403, 1404, 1405, 1406 of the scenario generated in steps 102 and 103 of FIG. 1 and initial operation information 1407, 1410, 1412 of the procedure invocation chain generated in step 1301 are displayed. . Then, according to the displayed system comment 1903 of the scenario editor 203, the argument component 1406 is selected (step 210).
2). Then, from the selected argument component 1406, a connection 1904 expressing that the procedure activation chain holds an argument is drawn in the activation chain name 1412 on the drawn arrow line 1407 (step 2103).

Next, FIG. 47 is a detailed flowchart of the step 1802 of setting a concrete value in the data of the component as a chain attribute held by the procedure invocation chain. Also, FIG.
47 is a screen display example of the procedure in FIG. 47. The procedure for setting a concrete value in the data of the component as the chain attribute held by the procedure invocation chain will be described in detail below with reference to FIGS. 47 and 20.

First, as shown in FIG. 14, the operator selects the procedure activation chain definition menu 1402 of the scenario menu 1401 from the displayed menu of the scenario editor 203 to activate the procedure activation chain definition function,
The activation chain 1503 of the procedure for which a concrete value is to be set in the data of the component as the chain attribute is drawn. Next, concrete values are set in the data of the constituent elements (step 1802). First, a component whose data is to be set to a specific value is selected (step 4701). Next, the internal data concrete value setting menu 2001 of the component menu 901 is selected from the menu of the scenario editor 203 (step 4702).

FIG. 20 shows how the menu 2001 is selected. Next, the internal data whose specific value you want to set is set.
Select the data name 2002 (step 4703) and according to the system comment 2003 of the displayed scenario editor 203,
A concrete value is input to the internal data (step 4704). Here, "A company" 2004 is input. Then, the specific value 2005 of the input internal data is drawn corresponding to the internal data name 2002 in the selected component (step 4705).
Then, it is judged whether or not the component is set as an argument component of the procedure activation chain being drawn (step
4706). If the component is not the argument component of the drawn procedure invocation chain, the drawn arrow 15
A connection line 2006 is drawn between the activation chain name 1504 on 03 and the selected component 1406 (step 4707).

Next, FIG. 48 shows a detailed procedure 1803 of setting the concrete value of the data of one constituent element to the concrete value of the data of another constituent element as the chain attribute held by the procedure invocation chain. It is a flowchart. Further, FIG. 45 is a screen display example of the procedure in FIG. Hereinafter, FIG. 48 and FIG.
5, the procedure for setting the concrete value of the data of one constituent element to the concrete value of the data of another constituent element as a chain attribute held by the procedure invocation chain will be described in detail.

First, as shown in FIG. 14, the operator selects the procedure activation chain definition menu 1402 of the scenario menu 1401 from the displayed menu of the scenario editor 203 to activate the procedure activation chain definition function,
As the chain attribute, the activation chain 1407 of the procedure in which it is desired to set the concrete value of the data of one constituent element to the concrete value of the data of another constituent element is drawn. Next, the concrete value of the data of one constituent element is set to the concrete value of the data of another constituent element (step 1803). First, a component for which a specific value is to be set in the data is selected (step 4801). Next, the internal data concrete value reference menu 4501 of the component element menu 901 is selected from the menu of the scenario editor 203 (step 480).
2).

FIG. 45 shows how the menu 4501 is selected. Next, the internal data whose specific value you want to set is set.
Data name 4502 is selected (step 4803). Then, according to the displayed system comment of the scenario editor 203, first, the component 4512 to be referred to is selected (step 48).
04) and then, according to the system comment 4503 of the displayed scenario editor 203, the internal data 4509 of the component to be referred to is selected (step 4805). Here, the estimated amount of money 4509 that is the data of the slip 4512 that is the argument component
Select And the concrete value held by the referenced data
4510 is acquired (step 4806), and the concrete value 4504 of the selected internal data to be referred to is drawn corresponding to the internal data name 4502 in the constituent element for which the concrete value of the data is set (step 4806). 4807). An arrow line 4508 is drawn between the data 4502 for which a specific value is to be set and the referenced data 4509 (step 48).
08) do. Then, it is determined whether or not the component for setting the concrete value and the component for referencing the concrete value are set as the argument components of the drawn procedure invocation chain (steps 4809 and 4810). If the constituent element is not the argument constituent element of the procedure activation chain being drawn, between the constituent elements for which the activation chain name 4506 and the concrete value of the data on the drawn arrow line 4505 are to be set, and A connection line 4507 is drawn between the starting chain name 4506 on the drawn arrow line 4505 and the constituent element 4512 that refers to the concrete value of the data (step 48).
11, 4812).

Next, FIG. 22 shows a procedure for setting a procedure start condition statement as a chain attribute held by the procedure start chain.
It is a detailed flowchart of 1804. Also, FIG.
23 is a screen display example of the procedure in FIG. 22. Hereinafter, FIG.
23 and FIG. 23, the procedure for setting the procedure activation condition statement as the chain attribute held by the procedure activation chain will be described in detail.

First, as shown in FIG. 14, the operator selects the procedure activation chain definition menu 1402 of the scenario menu 1401 from the displayed menu of the scenario editor 203 to activate the procedure activation chain definition function,
The procedure activation chain 2303 in which the procedure activation condition statement is to be set as the chain attribute is drawn. Next, a procedure activation condition statement is set (step 1804). First, the scenario editor 20
From the menu of 3, the start condition statement setting menu 2301 of the start chain menu 1901 is selected (step 2201).

FIG. 23 shows how the menu 2301 is selected. On the screen, the constituent elements 1403, 1404, 1405, 1406 of the scenario generated in steps 102 and 103 of FIG. 1 and the procedure invocation chain 2 generated in step 105 and specified above
303 is displayed. Next, according to the displayed system comment 2304 of the scenario editor 203, a procedure start condition sentence is input (step 2202). here,
Enter "Approximate estimation time" 2305. Then, the activation condition statement 2306 of the input procedure is drawn on the scenario editor 203 (step 2203).

Next, FIG. 24 is a detailed flowchart of the procedure 1805 for setting the internal data value of the component as the activation condition value as the chain attribute held by the procedure activation chain. 30 is a screen display example of the procedure in FIG. The procedure for setting the internal data value as the activation condition value as the chain attribute held by the procedure invocation chain will be described in detail below with reference to FIGS. 24 and 30.

First, as shown in FIG. 14, the operator selects the procedure activation chain definition menu 1402 of the scenario menu 1401 from the displayed menu of the scenario editor 203 to activate the procedure activation chain definition function,
A procedure activation chain 2303 for which a procedure activation condition value is set as a chain attribute is drawn. Next, the procedure start condition value is set (step 1805). First, a component for setting a procedure activation condition value in data is selected (step 240).
1). Next, the activation condition value setting menu 3001 of the activation chain menu 1901 is selected from the menu of the scenario editor 203 (step 2402).

FIG. 30 shows how the menu 3001 is selected. Next, the internal data name 2002 of the component for setting the procedure start condition value is selected (step 2403), and according to the system comment 3002 of the displayed scenario editor 203, the procedure start condition is set in the internal data. Input a value (step 2404). Here, "Company B" 3003 is input. Then, the internal data name 20 in the selected component
The input start condition value 3004 is drawn corresponding to 02 (step 2405). Then, it is determined whether or not the component is set as an argument component of the drawn procedure invocation chain (step 2406). If the component is not the argument component of the drawn procedure activation chain, the connection 3005 is drawn between the activation chain name 2302 on the drawn arrow line 2303 and the selected component 1406 (step 2407).

Next, a method of displaying the scenario input in step 101 as an event flow diagram will be described.

FIG. 25 is a flowchart displayed in the procedure of displaying the input scenario as an event flow diagram. 26 and 27 are examples of one screen display of the procedure in FIG. 25. The procedure for displaying the input scenario in the event flow diagram will be described below with reference to FIGS. 25 to 27.

First, the operator inputs a scenario (step 101) and displays the input scenario on the scenario editor 203 (step 2501). Next, the displayed scenario is displayed in the event flow (step 250).
2). First, the operator selects the procedure activation diagram definition menu 2601 of the scenario menu 1401 from the menu of the scenario editor 203 displaying the input scenario (step 2503). FIG. 26 shows how the menu 2601 is selected. On the screen, steps 102 and 103 in FIG.
Scenario components 1403, 1404, 1405 generated by
1406 and connection lines 1602 and 1603 between the components defining the procedure invocation chain generated in step 106 are displayed.

Next, the constituent element information on the scenario is acquired (step 2504), and the respective constituent elements 1403, 1404, 1405 are displayed as nodes 2701, 2703, 2705 on the event flow (step 2505). Next, all the procedure invocation chain information of the scenario is acquired (step 2506), and all the arrow lines expressing the procedure invocation chain are displayed from the procedure invocation chain information acquired using the displayed node as a terminal (step 250).
7). FIG. 27 is an example in which the procedure invocation chain of the scenario that is input and designated (FIG. 26) is displayed in an event flow diagram. The node of the event flow is composed of a combination 2701, 2703, 2705 of a constituent element graphic and a constituent element name, and straight lines 2702, 2704, 2706 which are the terminals of the arrow in the activation chain. Straight line 2702,
2704 and 2706 represent the time course of the activation chain from top to bottom. As the procedure invocation chain information to be displayed, the scenario name 2707 and all procedure invocation chains in the scenario are indicated by arrows and procedure names 2708, 2709, 2710, 2711, 2712.
To display.

Next, the overall requirement specifications are created (step 107). FIG. 29 is a detailed flowchart before the display of the procedure 107 of creating the overall requirement specifications. Also, FIG.
[FIG. 30] is a one-screen display example of overall requirement specifications created in the procedure of FIG. 29. Then, FIG. 46 shows an example of a program of the overall requirement specifications generated by the procedure of FIG. FIG.
33 to 33 are detailed flowcharts of the overall requirement specification program generation step 110 in FIG. Hereinafter, with reference to FIGS. 29, 5, 46, and 31 to 33,
The procedure 107 for creating the overall requirement specifications will be described in detail.

First, the scenario input in step 101 is selected (step 108). Next, the selected scenario groups are integrated on the model editor 204 (step 109). First, the model editor 204 is displayed (step 2901), and the selected scenario group is interactively arranged and integrated on the model editor 204 (step 2902). Then, only the component graphics 503, 504, and 505 of the components of the arranged scenario group are drawn as the components of the overall requirement specification (step
2903). Next, the connection lines 506 and 507 expressing the procedure activation chain between the components are drawn (step 2904).

Then, a program corresponding to the overall requirement specifications integrated on the model editor 204 is generated (step 110). First, the scenario information 206 held inside the computer of each integrated scenario is acquired (step 2905).

Next, the constituent element information 207 of each scenario is integrated for each constituent element, and a constituent element program 227 is generated from the integrated development target overall constituent element information 210 (step 2906). In step 2906, first, it is determined whether or not the constituent element in the scenario to be integrated exists on the model editor 204 (step 3101). If it does not exist, it is generated as the component element information 210 held by the overall requirement specification (step 3102). On the other hand, if it exists, it is determined whether or not the data name exists in the existing constituent element 210 (step 3103). If it does not exist, the data name is added to the existing component information 210 (step 3
104). On the other hand, if it exists, it is determined whether or not the procedure name exists in the existing component 210 (step 3
105). If it does not exist, the procedure name is added to the existing component information 210 (step 3106). A corresponding component program 227 is generated from the component information 210 of the overall requirement specifications generated by the above procedure (step 3107).
A program 4601 is generated corresponding to the component name 223 of the component information of the development target general viewing requirement specification, a program 4602 is generated corresponding to the component graphic information 222, and a program 4603 is generated corresponding to the procedure 225. To generate.

Next, the procedure invocation chain information of the overall requirement specifications
211 is generated, and the corresponding procedure invocation chain program 228 is generated (step 2907). First, the procedure invocation chain information 217 held inside the computer of each scenario to be integrated is acquired (step 3201). Next, the procedure invocation chain information 211 of the overall requirement is generated for each procedure name (step 3
202). The procedure invocation chain information 211 of the overall requirement specifications is, for each procedure name, a scenario management unique number, a component name in which the procedure is held, a procedure name to be called next, argument information and an invocation condition held in the procedure invocation chain to be called next. Holds information. Next, a corresponding procedure activation chain information program 228 is generated from the procedure activation chain information of the overall requirement specification generated for each procedure name in the above procedure (step 3
203).

Next, the processing program 205 for animating the activation chain is generated from the procedure activation chain information 211 of the overall requirement specifications generated in the above step 2907 (step 2908). First, the component name defined from the procedure name is acquired (step 3301), and the procedure name to be called next is acquired (step 3302). Then, the component name in which the procedure name to be called next is defined is acquired (step 3303).

Further, it is judged whether the activation condition information, the activation condition internal data value information or the activation condition statement information is set as a chain attribute for the procedure group to be activated next (step 3304). If the activation condition information is not set for all the chain attributes of the procedure group to be activated next, a program for activating all the procedures is generated (step 3305). When the start condition internal data value information is set as the chain attribute for the procedure group (step
1805) determines whether the data value of the specified component matches the set start condition internal data value, and generates a program that starts the next procedure only when it is true. (Step 3306). In addition, activation condition statement information is set as a chain attribute for the procedure group (step 1804).
If so, the activation condition statement is displayed, and only when the operator confirms that it is true, a program for invoking the next procedure is generated (step 3306).

Next, the above step 3301 and step 33
On the connection line 506 between the constituent elements 503 and 504 acquired in 03, from the call source constituent element 503 to the call destination constituent element 504,
A processing program for drawing and moving the procedure name 508 to be called next is generated (step 3309).

Next, it is judged whether or not the argument component is set as the chain attribute of the procedure invocation chain (step 33).
07). If the argument component is set as the chain attribute of the procedure invocation chain, the connection between the components 503 and 504 acquired in step 3301 and step 3303 above.
506, from the caller component 503 to the callee component 50
A processing program 4605 that draws and moves the component graphic 509 of the argument component toward 4 is generated (step
3308).

Next, taking a sales management system as an example, a method of defining a scenario group including a procedure invocation sequence that is executed in parallel from a certain point in time of activation of a plurality of procedures, and a method of visualizing and displaying a relation of all scenarios to be developed. For the procedure
This will be described in detail.

FIG. 28 is a detailed flowchart of a procedure 104 for defining a scenario group including a procedure invocation chain that is executed in parallel from a certain point in time when two procedures are invoked, and a visualization display procedure 114 related to the entire development target scenario. is there. 34 and 35 are the first and second scenario information input in the initial stage in FIG. 28. Also, FIG.
6 and 37 are screen display examples for designating the common part of the scenario in FIG. Hereinafter, with reference to FIGS. 28 and 34 to 37, a method of defining a scenario group including a procedure invocation chain that is executed in parallel from a certain point in time of activation of two procedures, and a visualization display method related to the entire scenario of development target Will be described.

First, the first scenario to be referenced is input according to step 101, and the first scenario information (FIG. 34) is entered.
Generate Next, a second scenario referring to the first scenario is input according to step 101, and second scenario information (FIG. 35) is generated.

Next, it is specified that the procedure invocation chain of the second scenario that is input is referred to by the procedure invocation chain of the second scenario, and the procedure specified between the first and second scenarios is specified. Designate that the activation chains are common (step 2801). First, refer to the second scenario 3601
The arrow 3605 representing the procedure invocation chain referred to above is displayed, and the reference procedure 3602 is selected. Next, the same designation menu 3603 is selected from the menu of the scenario editor 203. FIG. 36 shows how the menu 3603 is selected. Then, according to the system comment 3604 of the displayed scenario editor 203, the first scenario 3701 is displayed on the scenario editor 203 (FIG. 37), and the arrow of the procedure invocation chain referred to by the procedure invocation chain of the second scenario is referenced. 3703 is displayed and the referenced procedure 3702 is selected.

Next, the specified first scenario scenario information (FIG. 34) and the scenario information of the second scenario (FIG. 3)
Information indicating that the procedure designated as common to 5) exists is generated as common information (step 28).
02).

FIG. 38 is a detailed flowchart of a procedure 2802 for generating common scenario information. In addition, FIGS. 39 and 40 are examples of scenario information including common information generated in the procedure of FIG. Hereinafter, FIG. 38 to FIG.
The procedure 2802 for generating scenario common information will be described in detail using 0.

First, information for generating common information is acquired in the first scenario information (FIG. 34) and the second scenario information (FIG. 35) (step 3801). First, the procedure invocation chain information of the referenced scenario (first scenario)
3416 is acquired (step 3802) and the unique number 3402 of the referenced scenario is acquired (step 3803). Next, the procedure invocation chain information 3503 of the reference scenario (second scenario) is acquired (step 3804), and the reference scenario unique number 35
Get 02 (step 3805).

Next, the commonization information 3901 is generated in the scenario information of the referenced scenario from the information for generating the commonization information acquired in the above procedure 3801 (step 3806). First, from the acquired referenced procedure activation chain information 3416, the position information of the referenced procedure activation chain of the referenced common information 3901
As 3902, the sequence from the beginning in the chaining scenario 3903
Then, a part 3417 of the obtained information 3416 is set, and further, conceptual position information 3904 indicating whether the position of the chain is the beginning, the middle 3909, or the end is generated from the information 3416.
In this embodiment, the position of the referenced procedure invocation chain is intermediate 39.
09. Next, the unique number 35 of the retrieved reference scenario
02 is set as the referenced common information 3905. And
From the procedure name 3505 and the procedure unique number 3506 of the acquired reference destination procedure invocation information, the information 3505 and 3506 are respectively referred to as common reference information 3906 related to the procedure 3907 and 3907.
Set to 908.

Next, the commonization information 4001 is generated in the scenario information of the reference scenario from the commonization information generation information acquired in the above step 3801 (step 3807). First, from the acquired reference procedure activation chain information 3503, reference common information 4001
As the position information 4002 of the reference procedure activation chain of the above, a part 3504 of the information 3503 that has acquired the order 4003 from the beginning in the chain scenario is set, and the position of the chain starts from the information 3503.
Concept position information 4004 indicating either 4009, intermediate, or last is generated. The position of the reference procedure invocation chain in the present embodiment is the head 4009. Next, the unique number 3402 of the acquired referenced scenario is set as the reference common information 4005. Then, from the procedure name 3418 and the procedure unique number 3419 of the acquired referenced procedure invocation chain information, information 3418, 341 is set as the referenced common information 4006 regarding the procedure.
Set 9 to 4007 and 4008 respectively.

Then, the acquired referenced procedure unique number 4010 is set in the referenced procedure unique number 3413 of the referenced scenario information (step 3808). Next, in the case where the procedure continuously defines the activation chain for the above-mentioned input first and second scenarios, the scenario is input (step 101). Next, in order to create the development target overall scenario related information, the scenario information of the scenario group defined above 20
6 Common information 217 to scenario-related information for the entire development target
Create 218 (step 114). First, select the scenario entered in step 101, and
Place on top 6 (step 2803).

Next, scenario related information of the entire development target is generated (step 2804). FIG. 41 is a detailed flowchart of the procedure 2804 for generating scenario-related information for the entire development target. Further, FIG. 42 is an example of scenario-related information generated by the procedure of FIG. 41. The procedure 2804 for generating scenario-related information for the entire development target will be described in detail below with reference to FIGS. 41 and 42.

First, the referenced information 220 included in the shared information 217 in the scenario information 206 of the scenario selected above is acquired (step 4101). If there is referenced information,
Get the scenario specific number 221 of the scenario (Step 41
02). Next, scenario related information 4201 is newly generated (step 4103). First, the acquired scenario unique number 221 is set to the related unique number 4202 (step 4104). here,
Scenario specific number 3402 in the referenced scenario information (Fig. 39)
Is set as the related unique number 4202 of the scenario related information 4201. Next, related information between scenarios is generated from the referenced information 220 of the acquired common information 217 (step 41).
05). As related information between scenarios, each scenario name 4203, scenario unique number 4204, and procedure invocation chain information common between scenarios are generated as a common partial scenario 4205. And as the common part scenario 4205,
Position information 4206 in which a procedure invocation chain is defined, component name 4209 holding the procedure, procedure name 4211 and unique number 4212, and procedure attribute information of the procedure invocation chain
Holds 4213 and 4214. In the case of a referenced scenario, all the related information between the scenarios is set.

Next, the reference destination information 219 of the common information 217 in the scenario information 206 of the scenario selected above is acquired.
(Step 4108). If there is reference destination information, first, the referenced procedure unique number 4006 in the common information 217 of the reference destination scenario is acquired (step 4106). Next, in the existing development target overall scenario related information 218, the referenced procedure unique number 4
It is determined whether there is a related unique number 4202 that matches 006 (step 4107). If the referenced procedure unique number 4006 does not match, new scenario related information is generated (step 4
103), the referenced procedure unique number 4006 acquired as the associated unique number 4202 is set (step 4104). If there is a related unique number 4202 that matches the referenced procedure unique number 4006, the scenario related information of the matching related unique number is updated (step 4105). In the case of the reference destination scenario, among the related information between the scenarios, information other than the component name 4209, the procedure name 4211 and the unique number 4212 that hold the procedure related to the commonly designated procedure invocation chain is set.

Next, the whole development target scenario related information is displayed on the scenario related diagram editor (step 2805). As shown in FIG. 43, the scenario relationship diagram editor 4301 includes an area 4302 for displaying scenario relationships of the entire development target and an area 4303 for displaying related information.

FIG. 43 is an example of a method of displaying the development target overall scenario related information. The area 4302 for displaying the scenario relation of the entire development target is composed of a graphic 4304 expressing the scenario defined by the user and a connection line 4311 expressing the relation between the scenarios. Further, the terminals (4305 to 4310) of the connection line 4311 expressing the relationship between scenarios are displayed in different cases depending on the position of the chain in the scenario of the same designated procedure. The terminals 4305 and 4306 are used when the position of the same designated procedure is the beginning of the scenario. Terminal 43
07 and 4308 are used when the position of the same designated procedure is in the middle of the scenario. The terminals 4309 and 4310 are used when the position of the same designated procedure is at the end of the scenario. In addition, the relation between referenced and referenced by the same designated procedure is represented by the shape of the terminal. In this embodiment, the reference terminals are represented by white circles 4305, 4308, 4309, and the referenced terminals are represented by black circles.
Expressed as 4306, 4307, 4310.

FIG. 44 shows an example of sales management of a method of displaying the development target overall scenario related information. The area 4302 for displaying the scenario relation of the entire development target is composed of figures 4401 and 4402 expressing the scenario defined by the user and a connection line 4311 expressing the relation of the scenario. Related connection 4311
When is selected, a part of the scenario related information is displayed in the related information display area 4303.

[0111]

According to the present invention, various attributes of system components are interactively defined, and a procedure activation chain is defined interactively for each scenario, thereby facilitating the required specifications of a large-scale system. Can be earned. Therefore, according to the present invention, unlike the conventional case, it is not necessary to investigate the constituent elements required for the system in advance and write the program, and it is necessary to write the program every time the constituent elements of the required specifications are changed. Since there is no such thing, even a system engineer with no programming knowledge can acquire specifications.
In addition, since the scenario can be input by an interactive operation, it is possible to easily create and change the required specifications at the meeting with the customer.

Further, according to the present invention, a program for displaying a motion animation of a procedural motion chain of the entire system can be automatically generated by integrating the defined and input scenario groups. Therefore, according to the present invention, when the visualized required specifications of the entire system are evaluated with the customer, the specifications that have occurred can be easily changed interactively on the spot on a scenario-by-scenario basis, and an animation is displayed on the spot. Easy to do. In addition, it is possible to reduce the work that is required when the required specifications are changed as in the related art.

Further, according to the present invention, the relationship of a large amount of requirement specifications of a large-scale system can be visualized even if the user does not perform a new operation, especially the requirement specification in which the user explicitly specifies the relationship. Can be displayed. Therefore, according to the present invention, it is possible to easily confirm the relationship between the required specifications of the entire system.

Further, according to the present invention, since the relationship of the required specifications of the entire system is displayed, the scenario to be edited can be easily searched.

[Brief description of drawings]

FIG. 1 is a flowchart showing a procedure for inputting and displaying a required specification according to an embodiment of the present invention.

FIG. 2 is a schematic configuration diagram of a requirement specification acquisition and creation system used in the embodiment of FIG.

FIG. 3 is a screen display example of a scenario input on the scenario editor of FIG.

FIG. 4 is a screen display example of elements constituting the scenario of FIG.

FIG. 5 is a screen display example of requirement specifications created on the model editor of FIG.

6 is a flowchart showing a detailed procedure of arrangement of scenario components and setting of component information in FIG. 1. FIG.

FIG. 7 is a screen display example when a scenario editor is displayed and constituent element basic parts are arranged.

FIG. 8 is a flowchart showing a detailed procedure of generating procedure activation chain information in FIG.

FIG. 9 is an example of a screen display in which names are set for component basic parts.

FIG. 10 is a surface display example in which data names of constituent elements are set.

FIG. 11 is a surface display example in which procedure names of constituent elements are set.

FIG. 12 is a surface display example in which constituent element graphics of constituent elements are defined.

13 is a flowchart showing a detailed procedure for defining a procedure invocation chain of each component of FIG.

14 is a screen display example of the procedure activation chain initial activation operation definition of FIG. 13. FIG.

FIG. 15 is a screen display example of the procedure activation chain definition of FIG.

FIG. 16 is an example of a screen display for ending the procedure activation chain definition.

FIG. 17 is a flowchart showing a detailed procedure of generating scenario information of FIG. 1.

FIG. 18 is a flowchart showing a procedure for setting a chain attribute in a procedure invocation chain. 4 is a flowchart showing a procedure for holding an argument component in the.

19 is a screen display example of initial setting of argument components set as chain attributes of the procedure invocation chain of FIG.

20 is a screen display example of data specific value setting which is set as a chain attribute of the procedure invocation chain of FIG.

FIG. 21 is a flowchart showing a procedure for holding a component as an argument in the chain attribute of the procedure invocation chain in FIG.

22 is a flowchart showing a procedure for setting a conditional statement for activating a procedure in the chain attribute of the procedure activating chain in FIG.

23 is a screen display example in which a conditional statement for activating a procedure is set as a chain attribute of the procedure activating chain in FIG.

FIG. 24 is a flowchart showing a procedure for setting an activation condition value for activating a procedure in the chain attribute of the procedure activation chain of FIG. 18 in the data of the component.

FIG. 25 is a flowchart showing a procedure for creating and displaying an event flow diagram based on the scenario information input in FIG.

FIG. 26 is a screen display example of the scenario input in FIG.

27 is a screen display example of an event flow generated from the scenario information displayed in FIG.

FIG. 28 is a flowchart showing a procedure for creating related information of a scenario of overall requirement specifications.

FIG. 29 is a flowchart showing a detailed procedure for creating the overall requirement specification of FIG. 1.

30 is a screen display example in which a condition value for activating a procedure is set as a chain attribute of the procedure activating chain in FIG.

31 is a flowchart showing a detailed procedure of generating the component program of FIG. 29. FIG.

FIG. 32 is a flowchart showing a detailed procedure of generating a procedure invocation chain program of FIG. 29.

FIG. 33 is a flowchart showing a detailed procedure of generating the chain motion animation program of FIG. 29.

FIG. 34 is an example of scenario information generated by the scenario information generation of FIG. 1.

FIG. 35 is an example of scenario information generated by the scenario information generation of FIG. 1.

FIG. 36 is a screen display example in which the same procedure as another scenario is designated for the scenario input in the scenario input of FIG. 1.

37 is a screen display example of a scenario input by the scenario input of FIG. 1. FIG.

FIG. 38 is a flowchart showing a detailed procedure of generating shared information of the scenario of FIG. 28.

FIG. 39 is an example of scenario information including the commonized information generated in FIG. 38.

FIG. 40 is an example of scenario information including the commonized information generated in FIG.

FIG. 41 is a flowchart showing a detailed procedure of generating scenario related information of the whole of FIG. 28.

FIG. 42 is an example of the entire scenario-related information generated by the generation of the entire scenario-related information in FIG. 41.

FIG. 43 is an example of display of overall scenario related information in FIG. 28.

FIG. 44 is an example of display of overall scenario related information in FIG. 28.

45 is a screen display example in which a value held by another data is set to the data as a chain attribute of the procedure invocation chain in FIG.

FIG. 46 is an example of a program generated by the overall requirement specification program generation of FIG. 1.

FIG. 47 is a flow chart showing a procedure for setting a concrete value in data as a chain attribute of the procedure invocation chain in FIG.

48 is a flowchart showing a procedure for setting a value held by another data to the data as a chain attribute of the procedure invocation chain of FIG.

[Explanation of symbols]

101 ... Scenario input, 108 ... Overall requirement specification creation, 113 ... Startup chain animation display, 114 ... Overall scenario related information creation, 203 ... Scenario editor, 204 ... Model editor, 216 ... Scenario related diagram editor, 206 ... Scenario information, 209 … Overall requirement specification information, 226… Overall requirement specification program, 217… Common information generation, 218… Overall scenario related information, 508… Balloon

Front Page Continuation (72) Inventor Hisashi Takahashi 5-20-1 Kamimizuhonmachi, Kodaira-shi, Tokyo Within Hitachi Ultra LSI Engineering Co., Ltd. (72) Inventor Shoichi Kubo, Kodaira, Tokyo 5-20 Mizumotocho No. 1 Hitachi Hitachi LSE Engineering Co., Ltd.

Claims (37)

[Claims] 1. A step of arranging an element constituting a development target on a screen of a computer terminal, a step of designating a name, a data name held by the element and a procedure name of each of the arranged element, and the element. By displaying the list of procedures held by the menu as a menu and repeating the operation of selecting a predetermined item from the menu, for each procedure of the constituents, the activation chain of the procedures between the constituent elements including the procedure,
Alternatively, a step of designating an activation chain of a procedure in a component, component element information recording the designated component name, data name, and procedure name, procedure activation chain information recording the procedure activation chain, and the component information. And a method for inputting required specifications, which comprises a step of generating scenario information holding respective names and unique numbers for the activation chain information. 2. A step of arranging elements constituting a development target on a screen of a computer terminal and displaying the arranged components on the screen of the computer terminal, and each configuration arranged and displayed on the screen of the computer terminal. A step of designating an element, a data name and a procedure name held by the component, and displaying each of the designated names in the component displayed on the screen of the computer terminal; and for each procedure of the component, By displaying a procedure list of procedures held by a component in a menu and displaying the procedure activation sequence between the components including the procedure, and repeating the operation of selecting from the menu, the component is A step of designating an activation chain of a procedure to be held and displaying the procedure activation chain held by the specified component by an arrow between the components displayed on the screen of the computer terminal A scenario in which the component information in which the specified component name, data name, and procedure name are recorded, the procedure invocation chain information in which the procedure invocation chain is recorded, and the name and unique number for the component information and invocation chain information are held. A method for obtaining a requirement specification, comprising the step of generating information. 3. A step of arranging an element constituting a development target on a screen of a computer terminal and displaying the arranged component on the screen of the computer terminal, and each configuration arranged and displayed on the screen of the computer terminal. A step of designating an element, a data name and a procedure name held by the component, and displaying each of the designated names in the component displayed on the screen of the computer terminal; and for each procedure of the component, By displaying a procedure list of procedures held by a component in a menu and displaying the procedure activation sequence between the components including the procedure, and repeating the operation of selecting from the menu, the component is A step of designating an activation chain of a procedure to be held and displaying the procedure activation chain held by the specified component by an arrow between the components displayed on the screen of the computer terminal A scenario in which the component information in which the specified component name, data name, and procedure name are recorded, the procedure invocation chain information in which the procedure invocation chain is recorded, and the name and unique number for the component information and invocation chain information are held. A step of generating information, and a step of sequentially displaying an activation chain of a procedure held by a component with an arrow line between the components on the screen of the computer terminal according to the generated procedure activation chain information. How to obtain the required specifications. 4. In the step of designating the procedure invocation chain held by the component of the requirement specification input method of claim 1, the procedure invocation chain is entered by entering a procedure name other than the procedure names listed in the menu. Specify,
A request characterized in that in the step of generating component element information, the input procedure name is generated as component element information, and in the step of generating procedure activation chain information, procedure activation chain information including the input procedure is generated. How to enter specifications. 5. A procedure is activated by inputting a procedure name other than the procedure names listed in the menu in the step of designating and displaying the procedure activation chain held by the constituent elements of the requirement specification obtaining method of claim 2. A chain is specified, the input procedure name is displayed in the component on the computer terminal, the specified procedure invocation chain is displayed by the arrow between the components displayed on the screen of the computer terminal, and the component information is displayed. In the generation step, the input procedure name is generated as component information, and in the procedure activation sequence information generation step, the procedure activation sequence information including the input procedure is generated to obtain a required specification. Method. 6. In the step of designating a procedure activation chain held by a component of the requirement specification input method according to claim 1, by designating a component, a procedure name other than the procedure name held by the component is generated. By specifying the procedure invocation sequence, the generated procedure name is generated as the component information in the step of generating the component element information, and the procedure activation chain including the generated procedure is generated in the step of generating the procedure activation chain information. A method of inputting a requirement specification characterized by generating information. 7. The procedure name other than the procedure name held by the constituent element by specifying the constituent element in the step of designating and displaying the procedure invocation chain held by the constituent element of the requirement specification obtaining method according to claim 2. By specifying the procedure invocation chain, displaying the generated procedure name in the component on the computer terminal, and displaying the specified procedure invocation chain on the screen of the computer terminal. In the component information generation step, the generated procedure name is generated as component information, and in the procedure activation chain information generation step, the procedure activation chain information including the generated procedure is generated. How to obtain characteristic requirements. 8. In the step of designating a procedure invocation chain held by a component of the requirement specification input method according to claim 1, a conditional statement for activating a procedure is input for a certain procedure invocation chain, and procedure invocation chain information is input. In the step of generating, the input method of the requirement specification is characterized in that the input activation condition statement is generated as activation condition information of the procedure activation chain information. 9. In the step of designating and displaying a procedure invocation chain held by a component of the requirement specification obtaining method of claim 2, a conditional statement for activating a procedure is input to a certain procedure invocation chain, and the input A request specification characterized in that the activated start condition statement is displayed on the screen of the computer terminal, and in the step of generating the procedure start chain information, the input start condition statement is generated as the start condition information of the procedure start chain information. How to get. 10. In the step of designating a procedure invocation chain held by the constituent elements of the requirement specification obtaining method of claim 3, a conditional statement for activating a procedure is input to a certain procedure invocation chain, and procedure invocation chain information is entered. In the step of generating, the input start condition statement is generated as the start condition information of the procedure start chain information, and in the step of sequentially displaying the procedure start chain information, the computer is executed according to the procedure start chain information including the start condition information. A method for obtaining required specifications, characterized by displaying the input start condition sentence on the terminal screen. 11. A data name held by a component holding a procedure for a certain procedure starting chain in the step of designating a procedure starting chain held by a component of the request specification input method according to claim 1. , Or one or more data names held by other components are specified, the condition value for the procedure to be activated is input as the value of the specified data name, and in the step of generating the procedure activation chain information. A method for inputting a required specification, characterized in that a condition value for activating a procedure entered corresponding to the designated data name and the data name is generated as activation condition information of the procedure activation chain information. 12. In the step of designating and displaying a procedure invocation chain held by a component of the requirement specification obtaining method of claim 2, for a certain procedure invocation chain, a data held by a component holding the procedure is stored. One or more data names or data names held by other components are specified, the condition value for starting the procedure is input as the value of the specified data name, and the input procedure is started. The condition value for displaying the specified data name in the component holding the specified data name displayed on the screen of the computer terminal, and in the step of generating the procedure invocation chain information, the specified data name and A method for obtaining a required specification, characterized in that a condition value for activating an input procedure corresponding to the data name is generated as activation condition information of the procedure activation chain information. 13. A data name held by a component holding a procedure for a procedure starting chain in a step of designating a procedure starting chain held by a component of the requirement specification obtaining method according to claim 3. , Or one or more data names held by other components are specified, the condition value for the procedure to be activated is input as the value of the specified data name, and in the step of generating the procedure activation chain information. In the step of generating a condition value for activating the entered procedure corresponding to the specified data name and the data name as activation condition information of the procedure activation chain information, and sequentially displaying the procedure activation chain information, According to the procedure activation chain information including the activation condition information, the input is input in the component holding the designated data name displayed on the screen of the computer terminal. Acquisition method request specification procedure and displaying the condition value to start. 14. In the step of designating a procedure invocation chain held by a component of the request specification input method according to claim 1, for a procedure invocation chain, one component other than the component holding the procedure is provided. Alternatively, a request specification input method is characterized in that a plurality of components are designated and the designated component is generated as argument information of the procedure activation chain information in the step of generating the procedure activation chain information. 15. In a step of designating and displaying a procedure invocation chain held by a component of the requirement specification acquiring method according to claim 2, a component other than a component holding the procedure is set for a certain procedure invocation chain. Specify one or more,
A connection line is displayed between the arrow of the procedure invocation chain displayed on the screen of the computer terminal and the component specified as the argument, and in the step of generating procedure invocation chain information, the specified component is connected to the procedure. A method for obtaining a requirement specification, which is characterized in that it is generated as argument information of activation chain information. 16. In the step of designating a procedure invocation chain held by a component of the request specification acquisition method according to claim 3, for a certain procedure invocation chain, one component other than the component holding the procedure is provided. Alternatively, in the step of generating the procedure invocation chain information, in the step of generating the procedure invocation chain information, the specified component is generated as the argument information of the procedure invocation chain information, and in the step of sequentially displaying the procedure invocation chain information, the procedure including the argument information A request specification acquiring method characterized in that a connection line is displayed between an arrow line of a procedure starting chain holding the argument information displayed on a screen of a computer terminal and a component element designated as an argument according to the starting chain information. 17. A data name held by a component holding a procedure for a procedure invocation chain in a step of designating a procedure invocation chain held by a component of the requirement specification input method according to claim 1. , Or one or more data names held by other components are specified, a value for the data name is set, and a value for the specified data name is set in the step of generating procedure invocation chain information. A request specification input method characterized in that a constituent element holding the specified data name is generated as argument information of the procedure invocation chain information and as argument information of the procedure invocation chain information. 18. In a step of designating and displaying a procedure invocation chain held by a component of the requirement specification obtaining method according to claim 2, for a certain procedure invocation chain, a data held by a component holding the procedure is stored. One or more data names or data names held by other components are specified, a value for the data name is set, and a value for the set data name is displayed on the screen of the computer terminal. It is displayed in the component holding the specified data name, and
A connection line is displayed between the arrow of the procedure invocation chain displayed on the screen of the computer terminal and the component specified as the argument, and in the step of generating the procedure invocation chain information, the specified data name A request specification acquiring method characterized in that a value is generated as substitution information of procedure invocation chain information, and a component holding the specified data name is generated as argument information of procedure invocation chain information. 19. In the step of designating a procedure invocation chain held by a component of the requirement specification obtaining method of claim 3, for a procedure invocation chain, a data name held by a component holding the procedure , Or one or more data names held by other components are specified, a value for the data name is set, and a value for the specified data name is set in the step of generating procedure invocation chain information. In the step of generating the component holding the specified data name as the argument information of the procedure invocation chain information as the substitution information of the procedure invocation chain information and sequentially displaying the procedure invocation chain information, the substitution information and the argument information According to the procedure invocation chain information including "," the setting is made in the component holding the specified data name displayed on the screen of the computer terminal. Acquisition of required specifications characterized by displaying a value for a data name and displaying a connection line between the arrow and a component of a procedure invocation chain holding the argument information displayed on the screen of the computer terminal Method. 20. In the step of designating a procedure invocation chain held by a component of the request specification input method according to claim 1, a data name and a value thereof retained by a component are given to a certain procedure invocation chain. A value held by the data name held by the specified component in the step of generating the procedure invocation chain information by specifying the data name held by the other component whose value is to be set. Is set as a value held by the data name held by the above-mentioned separately specified component, as substitution information of the procedure invocation chain information, and
A method of inputting a required specification, characterized in that the certain specified component and the separately specified component are generated as argument information of procedure invocation chain information. 21. In the step of designating and displaying a procedure invocation chain held by a component of the requirement specification acquisition method according to claim 2, a data name held by a component and a data name held by the component for a procedure invocation chain A value is specified, a data name held by another component whose value is to be set is specified, and the data name held by the specified component displayed on the screen of the computer terminal is separated from the data name described above. The arrow to the data name held by the specified component and the value of the data name held by the specified component specified above are displayed in the component specified separately above to generate the procedure invocation chain information. In the step, the value held by the data name held by the specified component is set as the value held by the data name held by the separately specified component as the substitution information of the procedure invocation chain information. Te, also, a method of obtaining required specifications and generates the specified components separately above and some components described above as the argument information of the procedure starting chain information. 22. In the step of designating a procedure invocation chain held by a component of the requirement specification acquisition method according to claim 3, a data name retained by a certain component and its value are assigned to a procedure invocation chain. A value held by the data name held by the specified component in the step of generating the procedure invocation chain information by specifying the data name held by the other component whose value is to be set. Is set as a value held by the data name held by the above-mentioned separately specified component, as substitution information of the procedure invocation chain information, and
In the step of generating the specified certain component and the separately specified component as argument information of the procedure invocation chain information and sequentially displaying the procedure invocation chain information, according to the procedure invocation chain information including the substitution information and the argument information. , From the data name held by the specified component displayed on the screen of the computer terminal to the data name held by the separately specified component is an arrow line and the specified component is The value of the data name to be held is displayed in the above-mentioned separately designated component, and the arrow between the procedure invocation chain holding the argument information displayed on the screen of the computer terminal and the connection between the components are connected. A method for obtaining required specifications characterized by displaying. 23. In the step of designating a procedure invocation chain held by a component of the requirement specification input method according to claim 1, the step of inputting a conditional statement to activate a procedure for a certain procedure invocation chain; One or more data names held by the component holding the data, or data names held by other components are specified, and the condition value for the procedure to be activated is set as the value of the specified data name. A step of inputting, and a step of specifying one or more data names held by the component holding the procedure or data names held by other components and setting a value for the data name. , A step of designating one or a plurality of components other than the component holding the procedure, and a data name held by a certain component and its value are designated, and the other structure to be set It has a step of designating the data name held by the element, and corresponds to each of the above steps in the step of generating the procedure activation chain information, and generates the input activation condition statement as the activation condition information of the procedure activation chain information. And a step of generating a condition value corresponding to the designated data name and the data name for activating the input procedure as activation condition information of the procedure activation chain information, and the specified component. A step of generating as argument information of the procedure invocation chain information, a value for the specified data name as substitution information of the procedure invocation chain information, and a component holding the specified data name as the procedure invocation chain information. And the value stored in the data name held by the specified component is separately described above. The value held by the data name held by the specified component is used as the substitution information of the procedure invocation chain information, and the specified component and the separately designated component are stored in the procedure invocation chain information. And a step of generating it as argument information, and the activation condition information, the argument information, and the substitution information held by each of the generated procedure invocation chain information, regardless of the order defined in each procedure invocation chain information. Requirement specification input method characterized by management. 24. In the step of designating a procedure invocation chain held by the constituent elements of the requirement specification obtaining method of claim 3, a step of inputting a conditional statement to activate a procedure for a certain procedure invocation chain; One or more data names held by the component holding the data, or data names held by other components are specified, and the condition value for the procedure to be activated is set as the value of the specified data name. A step of inputting, and a step of specifying one or more data names held by the component holding the procedure or data names held by other components and setting a value for the data name. , A step of designating one or a plurality of components other than the component holding the procedure, and a data name held by a certain component and its value are designated, and the other structure to be set It has a step of designating the data name held by the element, and corresponds to each of the above steps in the step of generating the procedure activation chain information, and generates the input activation condition statement as the activation condition information of the procedure activation chain information. And a step of generating a condition value corresponding to the designated data name and the data name for activating the input procedure as activation condition information of the procedure activation chain information, and the specified component. A step of generating as argument information of the procedure invocation chain information, a value for the specified data name as substitution information of the procedure invocation chain information, and a component holding the specified data name as the procedure invocation chain information. And the value stored in the data name held by the specified component is separately described above. The value held by the data name held by the specified component is used as the substitution information of the procedure invocation chain information, and the specified component and the separately designated component are stored in the procedure invocation chain information. And a step of generating it as argument information, and irrespective of the order defined in each procedure invocation chain information, the invocation condition information, argument information, and substitution information held by each of the generated procedure invocation chain information In the step of managing and sequentially displaying the procedure invocation chain information, after displaying the procedure invocation chain on the screen of the computer terminal with an arrow, according to the above-mentioned activation condition information of the procedure invocation chain information on the screen of the computer terminal. , The condition value for starting the input procedure is displayed in the input start condition statement or the component holding the specified data name, and the procedure is displayed. According to the generated argument information of the activation chain information, display the connection between the arrow of the procedure activation chain holding the generated argument information and the component specified as the argument, and according to the generated substitution information of the procedure activation chain information. , The value for the set data name in the component holding the specified data name, or the data name held by the separately specified component from the data name held by the specified certain component A method of obtaining a required specification, characterized in that an arrow line to a data name and a value of a data name held by a certain designated component are displayed in the separately designated component. 25. In the method for inputting requirement specifications according to claim 1, after the step of generating scenario information, a component is made a node from the component information of the generated scenario information, and a procedure activation chain information of the scenario information is used. A method of inputting required specifications, comprising the step of generating an event flow diagram with a procedure invocation chain as an event and displaying the generated event flow diagram on a screen of a computer terminal. 26. A step of arranging an element constituting a development target on a screen of a computer terminal, a step of designating a name, a data name held by the element, and a procedure name of each of the arranged element, For each procedure, a list of procedures held by the component is displayed as a menu, and the activation chain of the procedure between the components including the procedure or the activation chain of the procedure within the component is displayed as a menu, and the operation of selecting from the menu is repeated. Thereby specifying the activation chain of the procedure held by the component, component information in which the designated component name, data name, and procedure name are recorded, procedure activation chain information in which the procedure invocation sequence is recorded, and the configuration A step of generating scenario information holding a name and a unique number for the element information and the activation chain information,
By inputting the scenario information group by repeating the above steps, by specifying some of the scenario information groups generated in the above step, and by the same component name from each component information held by the specified scenario information group A step of integrating the data name and the procedure name held by the component to generate the entire component information, and generating the component program for the entire component information;
A step of generating overall procedure invocation chain information from the procedure invocation chain information of the specified scenario information group, and generating a procedure invocation chain program for the entire procedure invocation chain information; On the screen of the computer terminal by executing the step of generating the chain action animation program for displaying the animation in which the procedure name moves between the constituent elements arranged by the input method A method for obtaining required specifications, characterized by including a step for displaying. 27. In the step of designating a procedure invocation chain held by a component of the request specification obtaining method of claim 26, a conditional statement for activating a procedure is input to a certain procedure invocation chain, and procedure invocation chain information is entered. In the step of generating, the step of generating the input start condition statement as the start condition information of the procedure start chain information is generated, and in the step of generating the chain action animation program of the procedure start chain, the input start condition statement is displayed and established. A method for obtaining requirement specifications, which is characterized in that a program for specifying whether or not to generate is generated, and a program for executing a chain action animation of a procedure invocation chain is generated only when it is specified to hold. 28. In the step of designating the procedure invocation chain held by the component of the request specification acquisition method, the data name held by the component holding the procedure for a certain procedure invocation chain, Alternatively, one or more data names held by other components are designated, a condition value for activating the procedure is input as the value of the designated data name, and in the step of generating procedure activation chain information, A step of generating a condition value for activating the entered procedure corresponding to the specified data name and the data name as activation condition information of the procedure activation chain information, and generating a chain action animation program of the procedure activation chain. In the above, whether the value of the data name specified by the start condition information is the condition value input corresponding to the specified data name. Emergence determines, acquisition method request specification and generates a program for executing the chaining operation animation procedure starting chain only if it is true. 29. In the step of designating a procedure invocation chain held by a component of the requirement specification obtaining method according to claim 26, for a procedure invocation chain, one component other than the component holding the procedure is provided. Alternatively, in the step of generating the procedure invocation chain information, a plurality of the specified elements are generated as the argument information of the procedure invocation chain information, and in the step of generating the chain action animation program of the procedure invocation chain, Is generated as an argument to generate an animation program in which the constituent element graphic of the constituent element moves, and the argument information is used to generate a program for activating the procedure using the specified constituent element as an argument. Acquisition method. 30. In the step of designating a procedure invocation chain held by a component of the requirement specification obtaining method according to claim 26, for a procedure invocation chain, a data name held by a component holding the procedure , Or one or more data names held by other components are specified, a value for the data name is set, and a value for the specified data name is set in the step of generating procedure invocation chain information. In the step of generating the component holding the specified data name as the argument information of the procedure invocation chain information as the substitution information of the procedure invocation chain information and generating the chain action animation program of the procedure invocation chain, Generate an animation program in which the component figure of the component holding the specified data name moves, Acquisition method request specification and generates a program that sets the input to the data name value - specified de of the input information. 31. In the step of designating a procedure invocation chain held by a component of the request specification acquisition method according to claim 26, a data name retained by a component and a value thereof are assigned to a procedure invocation chain. A value held by the data name held by the specified component in the step of generating the procedure invocation chain information by specifying the data name held by the other component whose value is to be set. Is set as a value held by the data name held by the separately designated component as the substitution information of the procedure activation chain information, and the procedure of the certain designated component and the separately designated component is started. Generate as argument information of chain information,
In the step of generating the chain action animation program of the procedure invocation chain, it is desired to generate an animation program in which the component figure of the component holding each of the specified data names moves between the component and set the value by the substitution information. A method for obtaining a required specification, characterized in that a program for setting a value held by a data name held by a certain specified component as a data name is generated. 32. In the step of designating a procedure invocation chain held by the constituent elements of the requirement specification obtaining method of claim 26, the step of inputting a conditional statement to activate a procedure for a certain procedure invocation chain; One or more data names held by the component holding the data, or data names held by other components are specified, and the condition value for the procedure to be activated is set as the value of the specified data name. A step of inputting, and a step of specifying one or more data names held by the component holding the procedure or data names held by other components and setting a value for the data name. , A step of designating one or a plurality of components other than the component holding the procedure, and a data name held by a certain component and its value are designated, and another value to be set is set. It has a step of designating the data name held by the component, and corresponds to each of the above steps in the step of generating the procedure activation chain information, and the input activation condition statement is used as the activation condition information of the procedure activation chain information. A step of generating, a step of generating a condition value corresponding to the designated data name and the data name for activating the inputted procedure as activation condition information of the procedure activation chain information, and the designated component As the argument information of the procedure invocation chain information, the value for the specified data name as the substitution information of the procedure invocation chain information, and the component holding the specified data name is the procedure invocation chain. The step of generating it as argument information of the information and the value held by the data name held by the specified certain constituent element The value held by the data name held by the specified component is used as the substitution information of the procedure invocation chain information, and the certain specified component and the separately specified component are stored in the procedure invocation chain information. And a step of generating as argument information,
The activation condition information, the argument information, and the substitution information held by each generated procedure invocation chain information are managed for each information regardless of the order defined in each procedure invocation chain information, and the chain action animation program of the procedure invocation chain In the step of generating, a program that displays the above-mentioned input start condition sentence from the start condition information and specifies whether it holds, and a program that executes the chain action animation of the procedure start chain only when it is specified that it holds It is determined whether the value of the generated or specified data name is the condition value input corresponding to the specified data name, and the chain operation animation of the procedure invocation chain is executed only when the value is true. Generates a program and, from the argument information, the configuration of the components specified between the components as the above arguments An animation program in which elementary figures move and a program for activating the procedure by using the specified component as an argument by the argument information and setting a value input to the specified data name from the substitution information. A method for obtaining required specifications, which is characterized in that a program for generating or setting a value held by a data name held by a certain component specified above to a data name for which a value is to be set is generated. 33. In the step of designating a procedure invocation chain held by a constituent element in the process of inputting a requirement specification by repeating the requirement specification inputting method according to claim 26, among the first scenario information of a certain requirement specification. When the constituent element name and the procedure name are the same as the constituent element name and the procedure name in the second scenario information of another requirement specification, the constituent element and the procedure of the second scenario information are In the step of generating the procedure invocation chain information that specifies that the constituent element and the procedure of one scenario information are the same, the scenario unique number of each scenario information that specifies the same In the step of generating the commonization information and generating the procedure invocation chain program for the whole procedure invocation chain information, The same program is generated for the procedure invocation chain of the same name for a component of one name, and a separate program is generated for the procedure invocation chain to be subsequently activated, and a chain action animation program of the procedure invocation chain is generated. In the step of generating, the same action animation program of the procedure invocation chain of the same name with respect to the designated component of the same name is produced in the same sequence action animation program, and the chain action animation of the procedure invocation sequence to be subsequently activated is different. In the step of generating a chain action animation program and executing and displaying the chain action animation of the procedure invocation chain, one chain action animation is executed and displayed for the same procedure chain invocation specified above and specified separately. It is different for procedural chain start Run a chain operation animation, acquisition method request specification and displaying. 34. A step of arranging an element constituting a development target on a screen of a computer terminal, a step of designating a name, a data name held by the element and a procedure name of each of the arranged element, and the element For each procedure, the list of procedures held by the component is displayed as a menu, and the operation chain of the procedure within the component or the sequence of activation of the procedure within the component is displayed, and the operation to select from the general menu is repeated. Thereby specifying the activation chain of the procedure held by the component, component information in which the designated component name, data name, and procedure name are recorded, procedure activation chain information in which the procedure invocation sequence is recorded, and the configuration And a step of generating scenario information holding a name and a unique number for the element information and the activation chain information. In the step of specifying the procedure invocation chain of the component in the process of inputting the requirement specification by repeating the requirement specification input method described above, a certain component name and a certain procedure name in the first scenario information of a certain requirement specification are different. Component name and procedure name in the second scenario information of the required specifications of the second scenario information, the component and procedure of the second scenario information are the component and procedure of the first scenario information. Is specified, and the step of generating common information in each scenario information from the scenario unique number of each scenario information specifying the same, and the procedure specified to be the same After the step of continuously defining the procedure to be activated separately for each requirement specification and generating the corresponding scenario information, the generated scenario information The step of generating the common information from the common information, and the step of generating the related information between the entire visualization requirement specifications from the common information of the requirement specification group generated in the above as scenario related information, A requirement specification characterized by including a graphic representing the entire requirement group of the entire requirement specification and a step of displaying the whole scenario related information by displaying a connection between the scenario related information and the related requirement specifications. How to get. 35. The scenario information corresponding to the constituent element and the procedure designated to be the same in the step of generating the commonization information of the scenario information for each requirement specification that is the same designation according to claim 34. Is generated as common information of scenario information, and the scenario related information is displayed by selecting a connection representing the displayed relationship in the step of displaying the whole scenario related information. How to obtain the required specifications. 36. The scenario information corresponding to the component and procedure designated to be the same in the step of generating the commonization information of the scenario information according to claim 34 for each requirement specified to be the same. And a chained position in each requirement specification of the same designated procedure as the common information of the scenario information, and in the step of displaying the whole scenario related information, the same designated procedure of the scenario related information is displayed. A method for obtaining a requirement specification, characterized in that a position connecting a related requirement specification is identified from a chained position in each requirement specification and displayed, thereby displaying whole scenario related information. 37. The step of designating that the constituent element and procedure of the second scenario information according to claim 34 are the same as the constituent element and procedure of the first scenario information. In the step of designating that the scenario information refers to the component and procedure of the first scenario information, and generating the commonization information of the scenario information for each of the identically designated requirement specifications, the reference direction designated above In the step of generating general scenario information as common information and displaying the whole scenario related information, displaying that the second scenario information refers to the first scenario information by a connection between related requirement specifications. A method for obtaining required specifications, characterized by being equipped with.