JP2009151742A - Use case scenario creation support system, use case scenario creation support method, and use case scenario creation support program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To accurately retrieve a similar use case or component as a candidate for commonization by supporting the creation of a use case scenario or component. <P>SOLUTION: This use case scenario creation support system 100 comprises a screen output means 110 for reading the option of each of an actor name, objective information, and verb defined in the combination information of use case scenario patterns from an option table and generating and displaying the data on an input screen for accepting, within the range of option, the option of the actor name, objective information, and verb in a character string for each use case scenario pattern; and a scenario acquiring means 111 for accepting the instruction of the selection of a use case scenario, and the instruction of selection of an actor name, objective information, and verb in the use case scenario, and storing, in an information table having an existing use case scenario, the information on a scenario comprising the combination of an actor name, objective information, and verb specified in the character string by the instruction of selection. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a use case scenario creation support system, a use case scenario creation support method, and a use case scenario creation support program. Specifically, the use case scenario describes a function of a system in a design process of object-oriented software development. In particular, the present invention relates to a technology for supporting creation of a component designed from description of a use case scenario, and particularly to a technology for supporting creation in consideration of searching for similar use cases and components.

  In the use case design for object-oriented system development, two use cases having similar functions are made common to improve productivity. By using this standardization, the amount of description of the use case design document is reduced, and the entire system can be designed with a small amount of work. When standardizing use cases, the character strings of the use case scenario descriptions that make up the use case specifications are compared. If the descriptions are similar in two different use cases, the two use cases are candidates for common use. . In the case of development of a large-scale system such as an annuity system, a huge amount of work time is required when the work for searching for a common candidate is performed by a human.

As a method for solving such a problem, mechanically measuring use case scenario descriptions and similarity between use cases and searching for similar use cases from the system are implemented. At this time, a simple character string matching method is generally used for mechanical measurement of the similarity of the use case scenario description. As an advanced measurement method, a method for mechanically calculating use case scenario description and use case distance as shown in Patent Document 1 and quantifying the appropriateness of the entire system design is proposed. ing. This method uses the verbs and keywords in the use case scenario description to detect the number of the verbs and keywords commonly appearing in the use case scenario descriptions of two different use cases, and the distance between the use case scenario descriptions. Measure. Next, the distance between the two use cases is digitized using the distance between the use case scenario descriptions.
JP-A-10-301770

  The common candidate use case extraction method using the prior art has the following four problems.

  First of all, because even similar use case scenario descriptions are described by different designers with different notations, the similarity between use case scenarios is calculated based on simple string matching, verbs, and keywords. However, there is still a possibility that it is judged that they are not similar. As an example, if there is a use case scenario in which the insured claims benefits from the office, even if the description of the use case scenario has the same content, There are cases where the description is different from “to make a claim” or “to make a request for pension benefits from the office”. In such a case, conventionally, these use case scenarios are not regarded as similar use case scenario descriptions.

  Secondly, there is a possibility that even use case scenario descriptions having different meanings may be erroneously determined to be similar in measurement of similarity using only verbs and keywords. For example, “<System> <updates> <name item> of <customer table >>” and “<System> <updates <name item> using <customer table >>> Consider case scenario description. Here, the part enclosed in parentheses in the use case scenario description is a verb and a keyword. Conventionally, the two use case scenario descriptions are mistakenly regarded as similar use case scenario descriptions although their meanings are different.

  Third, when searching for a similar use case that is a candidate for sharing, the conventional method performs a large number of character string operations, and there is a situation in which the search time becomes long. In particular, in the case of a large-scale system such as an annuity system, a large number of use case scenario descriptions are designed. Therefore, performing string operations such as string matching and verb / keyword extraction using conventional methods will save a lot of search time. It will be necessary. Since similar use cases are frequently searched during design, shortening the search time is an important issue from the viewpoint of improving the efficiency of design work.

  Fourthly, there is a situation in which the user is not presented with information related to pension work such as a target pension system, such as the target pension system, in determining the use case similarity by the user. Whether or not use cases are similar to each other is ultimately determined by humans, but only the use case similarity values and use case scenario descriptions presented by conventional methods can be used as judgment materials. Not enough and information about the application is needed.

  Furthermore, after designing the use case scenario (basic design process) as described above, the component design (detailed design process) based on the description of the use case scenario is executed. It was necessary to make components common. When the components are shared, common components are searched based on the design information of the designed components. For this reason, it is likely that a wasteful process such as reworking of the designed component is likely to occur in order to share the components.

  In addition, the task of extracting candidates for commonization among components and determining whether or not commonization is possible is carried out by an expert who has a predetermined experience, but the site of large-scale system development (eg, component) It has been difficult in terms of time and cost to extract common candidates and determine whether or not commonization can be performed by such experts.

  Therefore, the present invention has been made in view of the above problems, and aims to provide a technique for supporting the creation of use case scenarios and components, and capable of accurately searching for similar use cases and components that are candidates for sharing. And

  The use case scenario creation support system of the present invention is a computer system that supports creation of a use case scenario. The use case scenario is a constituent element of the use case scenario. Information, and an option table that defines the choices of each information of the verb according to the processing content executed by the actor, and for each use case scenario pattern, the actor name, target information in the character string forming the corresponding use case scenario, And the use case scenario description table that defines combination information of verbs, and the combination information of each use case scenario pattern is read from the use case scenario description table, and the actor name, target information, and verb defined in the combination information Choices for each of Screen output means for reading from the option table, generating input screen data for accepting selection of an actor name, target information, and verb in a character string for each use case scenario pattern within the range of the options and displaying the data on an output interface And accepting the use case scenario selection instruction and the actor name, target information, and verb selection instruction in the use case scenario through the input screen, and the actor name and target specified in the character string by the selection instruction A scenario acquisition means for storing information on the use case scenario comprising information and a combination of verbs in an existing use case scenario description information table.

  The use case scenario creation support system reads use case scenario information from the existing use case scenario description information table and a use case scenario of another use case different from the use case to which the use case scenario belongs, The use case scenario pattern, actor name, target information, and verb match between the use case scenarios read out here are determined, and if the number of use case scenarios that match all the information is more than a certain number, Assuming that the use case and the other use case are similar use case groups, a similar case specifying means for displaying information on the use case group on an output interface may be provided.

  Further, in the existing use case scenario description information table of the use case scenario creation support system, each use case scenario pattern, actor name, target information, and verb information included in each use case scenario uniquely identifies each information. It is an identifiable ID, and the similar case specifying means determines whether use case scenario pattern, actor name, target information, and verb information match between use case scenarios read from the existing use case scenario description information table. In doing so, it is possible to determine whether the IDs of the respective information match.

  Further, in the use case scenario creation support system, the existing use case scenario description information table stores information on a business to which the corresponding use case is applied for each use case scenario, and the similar case specifying means includes the Along with the information on the use case group, the information on the business to be applied to the corresponding use case may be read from the existing use case scenario description information table and displayed on the output interface. In addition, as information on the target business of the applicable use case, for example, information on the pension business of the target pension system and the target pension type can be assumed.

  Further, in the use case scenario creation support system, for a use case scenario read from a predetermined storage device or acquired from an input interface, the actor name, target information, and verb included in the character string, and the actor name and target information are included. , And a permutation of the verb in the character string, each use case scenario pattern in the use case scenario description table is matched, and if any use case scenario pattern included in the use case scenario description table does not match, A new use case scenario pattern including the actor name, target information, and verb included in the character string of the use case scenario and the permutation information in the character string of the actor name, target information, and verb Case scenario description table Register may be equipped with a use-case scenario analysis means.

  In the use case scenario description table, as a use case scenario pattern, (1) “actor” is “target information 1” as “verb”, and (2) “actor” is “target information 1” as “target information 2”. "Verb", (3) "Actor" is "Target information 1" and "Target information 2" are "Verbs", (4) "Actor" is "Target information 1" to "Target information 2" is "Verb" (5) “Actor” is assumed to have five types of patterns, “target information 1” as input and “target information 2” as “verb”.

  The use case scenario creation support system includes an existing component information table storing information on existing components designed from the use case scenario, a use case, a use case scenario belonging to the use case, and a component of the use case scenario. A storage device that stores a use case / component association information table that defines the correspondence relationship between the component and the specification of the component for the predetermined use case scenario received by the input interface, The existing component information stored in the existing component information table is collated to identify an existing component that includes the same character string as the specified component. Displays the list of existing components specified in step 4 on the output interface, accepts the common component specification from the existing components in the list on the input interface, and associates it with the specified use case scenario in the use case / component association information table Similar component specifying means for setting information on the common component may be provided.

  Further, in the use case scenario creation support system, the similar component specifying unit includes a use case A in which the similar case specifying unit cannot determine that the number of use case scenarios in which the respective pieces of information all match is a predetermined number or more. Detects a set with other use case B, accepts designation of component a for use case scenario belonging to use case A and component b for use case scenario belonging to other use case B by the input interface, and designates here. The information of the designated component a received and the information of the designated component b are collated to identify a set of components that include the same predetermined character string between the designated components a and b, and the component set identified here Squirrel Is displayed on the output interface, the designation of the common component from the component set of the list is received by the input interface, and is associated with the use case scenarios of the use case A and the use case B in the use case / component association information table. Information on the common component may be set.

  In addition, the use case scenario creation support method of the present invention is a computer that supports the creation of a use case scenario. The name of the actor that is the execution subject of the process, which is a constituent element of the use case scenario, and the target information of the process that the actor performs , And an option table that defines verb information options according to the processing executed by the actor, and for each use case scenario pattern, the actor name, target information, and target information in the character string forming the corresponding use case scenario, and A use case scenario description table defining verb combination information in the storage device, reading the combination information of each use case scenario pattern from the use case scenario description table, and an actor name defined in the combination information; For each of the target information and verb A screen that reads out options from the option table, generates data of an input screen that accepts an actor name, target information, and verb selection in a character string for each use case scenario pattern within the range of the options, and displays it on the output interface. Accept the use case scenario selection instruction and the actor name, target information, and verb selection instruction in the use case scenario through the output process and the input screen, and the actor name specified in the character string by the selection instruction And a scenario acquisition process for storing use case scenario information comprising a combination of target information and verb in an existing use case scenario description information table.

  In addition, the use case scenario creation support program of the present invention is a constituent element of a use case scenario to support the creation of a use case scenario, an actor name that is an execution subject of a process, target information of a process executed by the actor, And an option table that defines options for each information of the verb according to the processing content executed by the actor, and the actor name, target information, and verb in the character string forming the corresponding use case scenario for each use case scenario pattern A computer having a use case scenario description table defining combination information of the storage device, and reading the combination information of each use case scenario pattern from the use case scenario description table, and an actor name defined in the combination information, Target information and verb For each use case scenario pattern, an input screen data that accepts an actor name, target information, and verb selection in the character string is generated and displayed on the output interface. Step, through the input screen, accepts a use case scenario selection instruction and an actor name, target information, and verb selection instruction in the use case scenario, and the actor name specified in the character string by the selection instruction, A program that executes a step of storing use case scenario information including target information and a combination of verbs in an existing use case scenario description information table.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.

  According to the present invention, it is possible to support the creation of use case scenarios and components, and to search for similar use cases and components that are candidates for sharing with high accuracy.

--- System configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a configuration diagram of a use case scenario creation support system system 100 according to this embodiment. A use case scenario creation support system 100 (hereinafter, system 100) in the present embodiment is a computer system that supports use case scenario creation. The system 100 reads out the program 102 stored in the storage device 101 such as a non-volatile memory into the memory 103 and executes it by the CPU 104 as an arithmetic device in order to realize the function of executing the use case scenario creation support method. In addition, the system 100 is connected to an external device such as various buttons generally provided in a computer device, an input interface 105 such as a keyboard, an output interface 106 such as an LED or a display, and an operation terminal 200 used by a user. A communication device 107 that performs communication is included.

  Next, functional units that are configured and held by the system 100 based on the program 102 will be described. The system includes the existing use case scenario description information table 126, the use case scenario description table 127, and the option table 128 in the storage device 101 or can be used via the network 140 (the tables are stored in the devices on the network). ).

  The system 100 reads combination information of each use case scenario pattern from the use case scenario description table 127, and selects options for each of the actor name, target information, and verb determined in the combination information from the option table 128. A screen output unit 110 is provided that generates data of an input screen that accepts selection of an actor name, target information, and verb in a character string for each read-out and use case scenario pattern within a range of the options and displays the data on the output interface 106. .

  Further, the system 100 accepts a use case scenario selection instruction and an actor name, target information, and verb selection instruction in the use case scenario through the input screen, and is specified in the character string by the selection instruction. A scenario acquisition unit 111 that stores use case scenario information including a combination of an actor name, target information, and a verb in an existing use case scenario description information table 126.

  Further, the system 100 reads the use case scenario information from the existing use case scenario description information table 126 and the use case scenario of another use case different from the use case to which the use case scenario belongs, and reads it here. The use case scenario pattern, actor name, target information, and verb information are determined to match between the use case scenarios. And the other use cases are similar use case groups, and similar case specifying means 112 is provided for displaying information on the use case groups on the output interface 106.

  In the existing use case scenario description information table 126, each use case scenario pattern, actor name, target information, and verb information included in each use case scenario is an ID that can uniquely identify each information. Is preferable. In this case, the similar case specifying unit 112 determines whether the use case scenario pattern, the actor name, the target information, and the verb information match between the use case scenarios read from the existing use case scenario description information table 126. Therefore, it is determined whether the IDs of the respective information match.

  In addition, the existing use case scenario description information table 126 may store information on the business to which the corresponding use case is applied for each use case scenario. In this case, the similar case specifying unit 112 reads out the information on the business to be applied to the use case together with the information on the use case group from the existing use case scenario description information table 126 and displays it on the output interface 106. Is preferable. In addition, as information on the target business of the applicable use case, for example, information on the pension business of the target pension system and the target pension type can be assumed.

  In addition, the system 100 reads the actor name, target information, and verb included in the character string of the use case scenario read from a predetermined storage device or acquired from the input interface 105, and the actor name, target information, and verb. The permutation in the character string is compared with each use case scenario pattern in the use case scenario description table 127, and if the use case scenario pattern included in the use case scenario description table 127 does not match, A new use case scenario pattern including the actor name, target information, and verb included in the character string of the case scenario and permutation information in the character string of the actor name, target information, and verb is used as the use case. Registered in the scenario description table 127 To may be provided with a use case scenario analysis means 113.

  The use case scenario description table 127 includes (1) “actor” as “target information 1” as “verb” and (2) “actor” as “target information 1” as “target information” as use case scenario patterns. 2 is “verb”, (3) “actor” is “target information 1” and “target information 2” is “verb”, and (4) “actor” is “target information 1” to “target information 2”. It is assumed that “verb” and (5) “actor” have five types of patterns, “target information 1” as input and “target information 2” as “verb”.

  The function units 110 to 113 in the system 100 described so far may be realized as hardware, or as a program stored in an appropriate storage device such as a memory or an HDD (Hard Disk Drive). Also good. In this case, the CPU of each device constituting the system 100 reads the corresponding program from the storage device into the memory in accordance with the program execution, and executes it.

--- Example of table structure ---
Next, the structure of the table used by the system 100 in this embodiment will be described. FIG. 2 shows data structures of (a) an existing use case information table 125, (b) an existing use case scenario description information table 126, (c) a use case scenario description table 127, and (d) an option table 128 in this embodiment. It is a figure which shows an example.

  The existing use case information table 125 is a table for storing use case information composed of use case scenarios, and a record is generated using a use case ID for identifying use case information registered in the system 100 as a key. Has been. The use case ID is uniquely set for all use cases in the system 100. Such an existing use case information table 125 is a set of records in which each information of system name, use case name, use case outline, pension system, and pension type is associated with the use case ID as a key. “System name” indicates the name of the system where the use case is registered, “Use case name” stores the name of the use case as a character string, and “Use case overview” is performed by the use case. An overview of the process is shown. “Pension system” indicates a pension system that is processed by the use case, and “Pension type” indicates a pension type that is processed by the use case.

  The existing use case scenario description information table 126 is a table for storing use case scenario information including combinations of actor names, target information, and verbs specified in character strings. The existing use case scenario description information table 126 is, for example, a use case scenario with a use case ID (relationship with that of the existing use case information table 125) as information for identifying the use case to which the use case scenario description belongs as a key. ID (uniquely set for use case scenario description), use case scenario order (use case scenario description in order within use case. In the design document, use case scenario description follows the order of use case scenario order. The use case scenario pattern ID, the actor name ID, the information name ID1, the information name ID2, the information name ID3, and the verb ID form a set of associated records.

  The use case scenario pattern ID indicates information for identifying the sentence description pattern of the use case scenario description, the actor name ID indicates information for identifying the actor name of the use case scenario description, and the information name ID 1 is Indicates an ID for identifying the information name of the first target information described in the use case scenario description, and the information name ID2 is an ID for identifying the information name of the second target information described in the use case scenario description. The information name ID3 indicates an ID for identifying the information name of the third target information described in the use case scenario description. The verb ID indicates an ID for identifying the verb described in the use case scenario description. . Here, “information name 2” does not store information when there is one information name that needs to be described in the use case scenario description. Similarly, “information name 3” does not store information when there is one or two information names that need to be described in the use case scenario description.

  As described above, in the existing use case scenario description information table 126, each use case scenario pattern, actor name, target information, and verb information included in each use case scenario has an ID that can uniquely identify each information. It has become.

  In addition, the existing use case scenario description information table 126 preferably stores information on the application target business of the corresponding use case for each use case scenario. However, in the example of the present embodiment, In the existing use case information table 125, “pension system” and “pension type” are stored. Since the existing use case information table 125 is a relational database in which the existing use case scenario description information table 126 and the use case ID are linked to a key, both can be regarded as an integrated table.

  The use case scenario description table 127 is a table that defines, for each use case scenario pattern, combination information of the actor name, target information, and verb in a character string forming the corresponding use case scenario. This use case scenario description table 127 uses a use case scenario pattern ID for identifying a use case scenario description pattern (uniquely set for all use case scenario patterns) as a key, and a scenario character string. It is a collection of associated records. The scenario character string includes information on an actor name, an information name, and a verb, and these pieces of information are obtained by using information in an actor name table 128a, an information name table 128b, and a verb table 128c that constitute the option table 128, respectively. For example, “<actor>” is expressed in the character string so that it can be replaced.

  In addition, the option table 128 includes, as constituent elements of a use case scenario, the name of an actor that is an execution subject of processing, target information of processing executed by the actor, and verb information corresponding to processing details executed by the actor It is a table that defines the options. In this embodiment, the option table 128 includes an actor name table 128a, an information name table 128b, and a verb table 128c.

  The actor name table 128a is a collection of records in which the actor names are associated with the actor ID (uniquely set for all actor names) identifying the actor name used in the use case scenario description as a key. ing.

  Further, the information name table 128b associates information names with an information name ID (uniquely set for all information names) for identifying an information name (target information) used in the use case scenario description as a key. It is a collection of records.

  The verb table 128c is a collection of records in which verbs are associated with each other using a verb ID (uniquely set for all verbs) for identifying a verb used in the use case scenario description as a key. .

--- Processing flow example 1 ---
Hereinafter, an actual procedure of the use case scenario creation support method in the present embodiment will be described with reference to the drawings. Various operations corresponding to the use case scenario creation support method described below are realized by a program that the system 100 reads into the memory and executes. And this program is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 3 is a flowchart showing a processing procedure example 1 of the use case scenario creation support method of the present embodiment, FIG. 6 is a diagram showing an example of an input screen of the present embodiment, and FIG. 7 is a diagram of the present embodiment. It is a figure which shows the example of a search result screen. Here, a process in which the system 100 performs creation support when a user creates a use case scenario using the operation terminal 200 connected to the system 100 via the network 140 will be described. In this case, the screen output unit 110 of the system 100 transmits, for example, use case selection screen data (stored in the storage device 101 of the system 100) to the operation terminal 200, and accepts a use case selection instruction (s100). ). It is assumed that the selection screen includes, for example, an interface capable of selecting a use case application target (insurance system, pension type).

  The screen output unit 110 uses the application target in the existing use case information table 125 based on a use case selection instruction (including use case application target information) obtained from the operation terminal 200 via the selection screen. The use case corresponding to is specified (s101). Then, the screen output means 110 reads the use case scenario pattern associated with the use case specified here from the use case scenario description table 127 (s102). Also, the combination information of each use case scenario pattern read here is also read from the use case scenario description table 127, and options for each of the actor name, target information, and verb determined in the combination information are displayed in the option table. Read from 128 (s103).

  As shown in the input screen 600 of FIG. 6, the screen output means 110 is an input screen that accepts selection of an actor name, target information, and verb in a character string for each of a plurality of use case scenario patterns within the range of the options. Data is generated and transmitted to the operation terminal 200 (s104). For example, the input screen 600 is an interface for selecting a user-desired scenario pattern from the use case scenario patterns on the operation terminal 200 and selecting an actor name, target information, and verb options. ing. As such an interface for selection, for example, a pull-down or a radio button can be assumed.

  In the example of FIG. 6, the user selects scenario pattern “pattern 3”, actor name “system”, information name 1 “invoice number”, information name 2 “resident card number”, and verb “match”. Therefore, the created use case scenario is “The system matches the invoice number and resident card number”.

  The scenario acquisition unit 111 of the system 100 uses the input screen 600 from the operation terminal 200 to select a use case scenario pattern: “pattern 3” and an actor name in the use case scenario pattern: “system”, target information: information Accepts a selection instruction of name 1 “invoice number”, information name 2 “resident card number”, and verb: “match”, and the actor name, target information, and information specified in the character string by the selection instruction Use case scenario consisting of a combination of verbs: The system acquires the information “The system matches the bill number and resident card number” and stores it in the existing use case scenario description information table 126 (s105).

--- Processing flow example 2 ---
FIG. 4 is a flowchart showing a processing procedure example 2 of the use case scenario creation support method of the present embodiment, and FIG. 7 is a diagram showing an example of a search result screen of the present embodiment. Next, a similar use case search process will be described. In this case, the similar case identification unit 112 of the system 100 first extracts one use case from the existing use case information table 125 according to, for example, the registration order (s200). The use case taken out here is referred to as use case (A). Further, the similar case specifying unit 112 extracts one other use case different from the use case (A) from the existing use case information table 125 (s201). This is a use case (B).

  Next, the similar case specifying means 112 extracts one use case scenario of the use case (A) from the existing use case scenario description information table 126 according to the order of use case scenario ranking (s202). This is a use case scenario (a). In addition, the similar case specifying unit 112 extracts one use case scenario of the use case (B) from the existing use case scenario description information table 126 according to the order of use case scenario (s203). This is a use case scenario (b).

  The similar case specifying unit 112 checks whether the use case scenario pattern ID, the actor name ID, the information name ID1, the information name ID2, the information name ID3, and the verb ID are all equal for the use case scenarios (a) and (b). (S204). When the matching process with the use case scenario (a) is processed for all use case scenarios of the use case (B) (s205: Yes), the process proceeds to step s206. On the other hand, when there is an unprocessed use case scenario for the use case (B) (s205: No), the process returns to step s203.

  In the matching process of all use case scenarios of the use case (B) with respect to the use case scenario (a) in the steps s203 to s205, there is a use case scenario in which the IDs match in the use case (B). In this case, the similarity value between the use case scenario (a) and the predetermined use case scenario of the use case (B) is set to 1 (s206). On the other hand, if there is no use case scenario that matches the IDs in use case (B) in the matching process, the similarity value between use case scenario (a) and use case (B) is set to 0. .

  When all the use case scenarios of the use case (A) other than the use case scenario (a) have been collated (s207: Yes), the process is moved to step s208. On the other hand, when an unprocessed use case scenario remains for the use case (A) (s207: No), the process returns to step s202.

The similar case specifying unit 112 calculates the similar values of the use case (A) and the use case (B) that have been matched in matching between use case scenarios using the following calculation formula (s208). .
(Sum of similar values of all use case scenarios of use case (A)) x 2 / (sum of the number of use case scenarios of use case (A) and use case (B)) = similar value

  The similar case specifying unit 112 stores similar value data calculated by such a calculation formula in the storage device 101 for each set of use cases.

  When the similar case specifying unit 112 performs the process for all combinations of use cases in the existing use case information table 125 (s209: Yes), the process proceeds to step s210. On the other hand, when a combination of unprocessed use cases remains (s209: No), the process returns to step s200.

  Next, the similar case specifying unit 112 reads the similar values from the storage device 101 to the memory 103, specifies a predetermined number of use case groups (a set of use cases determined to be similar to each other) in descending order of the similar values, Information on this use case group is transmitted to the operation terminal 200 (s210). As shown in the search result screen 700 of FIG. 7, the similar use case search result is displayed in the information column 701 of each use case constituting the use case group by the actor name, use ID, use case name, and use case summary. Each information of the pension system, the pension type, and the use case scenario are displayed. Further, a similar value of the corresponding use case group is displayed in the similar value column 702.

  The operation terminal 200 receives the search result screen 700 from the system 100, displays it on an output interface such as a display device, etc., for use by the user.

--- Processing flow example 3 ---
FIG. 5 is a flowchart showing a processing procedure example 3 of the use case scenario creation support method of the present embodiment. Next, use case scenario pattern new registration processing will be described. In this case, the use case scenario analysis means 113 of the system 100 first extracts one use case that has not been subjected to the pattern analysis from the existing use case information table 125 (s300). Then, the use case scenario analyzing unit 113 extracts one use case scenario of the use case extracted in step s300 from the existing use case scenario description information table 126 according to the order of use case scenario (s301).

  The use case scenario analysis unit 113 sets the search position to the first character for the use case scenario extracted in step s301 (s302). Then, a search is made for a match with the actor name in the actor name table 128a from the search position of the use case scenario (s303). Then, the search position is set one character after the actor name in the use case scenario matched in step s303 (s304).

  Subsequently, the use case scenario analysis means 113 searches the information name table 128b for a matching character string after the use case scenario search position (s305). If there is a plurality of matched information names as a result of this search, the information name with the most matching position in the use case scenario is regarded as matched (s306).

  Further, the use case scenario analysis unit 113 sets the search position one character after the information name in the use case scenario that is matched in step s306 (s307). If there is a character string that matches the information name in the information name table 128b after the search position of this use case scenario (s308: Yes), the process returns to step s306. On the other hand, if there is no character string that matches the information name in the information name table 128b after the search position (s308: No), the process proceeds to step s309.

  Next, the use case scenario analysis unit 113 searches the verb table 128c for a matching character string after the use case scenario search position (s309). The use case scenario analysis unit 113 identifies an actor name, an information name, and a verb in the use case scenario through a series of processes from steps s301 to s309. Next, the use case scenario analysis means 113 performs “<actor>” for an actor name (for example, “system is”) and an information name (for example, “resident card number”) in the use case scenario. Depending on the order in the character string, “<information name 1>” or “<information name 2>” or “<information name 3>”, and the verb (for example, “match”) are replaced with “<verb>”, respectively. Perform (s310). As a result, the use case scenario analysis unit 113 converts the use case scenario into a pattern character string such as “<actor> <information name 1> <verb>”. Subsequently, the use case scenario analyzing unit 113 compares the use case scenario information patterned in the step s310 with each use case scenario pattern (scenario character string) in the use case scenario description table 127, and If it is not in the use case scenario description table 127, it is stored in the use case scenario description table 127 as a new scenario pattern (scenario character string) (s311).

  The use case scenario analysis means 113 returns the processing to step s301 when there is an unprocessed use case scenario among the use cases extracted in step s300 (s312: Yes). On the other hand, when there is no unprocessed use case scenario (s312: No), the process proceeds to step s313.

  The use case scenario analysis unit 113 returns the processing to step s300 when there is a use case in the existing use case information table 125 that has not been processed by the use case scenario analysis unit 113 (s313: Yes). . On the other hand, when there is no use case that has not been processed by the use case scenario analysis unit 113 (s313: No), the process is terminated.

  According to the present embodiment, the description of the use case scenario is composed of options (scenario pattern, actor name, target information, verb) prepared in advance by the system side, so the description does not become irregular for each designer. Thus, an accurate search for similar use cases can be performed efficiently. In particular, in a large-scale system such as an annuity system, since the environment is such that many designers design and create many use case scenarios, the above-described effect is great.

  In addition, when searching for similar use cases, it is possible to use only IDs and numbers as the information to be compared between use cases (actor names, target information, verbs, etc. are converted into IDs), and string matching by conventional methods Thus, a faster search is possible. In particular, in a large-scale system such as an annuity system, the use case scenario description and the number of use cases become enormous, so the above-described effect is great.

  In addition, when displaying information on similar use cases on the screen, for example, by displaying design information related to pension work that is the application target of a system using use cases, it is easier for humans to determine commonization candidates. become. In particular, in systems that handle business specifications based on complex laws such as pension systems, it is necessary to comprehensively consider information other than use case scenario description when considering common use cases. Therefore, the above effect is great.

--System configuration in other embodiments ---
Next, processing that the system 100 supports to share components designed from use case scenarios will be described. FIG. 8 is an overall configuration diagram of a use case scenario creation support system according to another embodiment. Here, the system 100 includes the above-described units 110 to 113 in the same manner, but since the functions are the same, the description thereof is omitted here. The system 100 in this embodiment newly includes the following storage devices and means.

  The system 100 in this embodiment includes an existing component information table 129 storing information on existing components designed from use case scenarios, use cases, use case scenarios belonging to the use cases, and components of the use case scenarios. A storage device 101 that stores a use case / component association information table 131 that defines the correspondence relationship of

  In this case, the system 100 receives the designation of the component for the predetermined use case scenario by the input interface 105, the information of the designated component accepted here, and the existing component stored in the existing component information table 129. The existing component including the same character string as the predetermined character string included in the designated component is identified, and the list of the existing components identified here is displayed on the output interface 106. A designation of a common component from among the components is received by the input interface 105, and the common component is associated with the predetermined use case scenario in the use case / component association information table 131. Setting the capital of information comprises a similar component identifying means 114.

  In addition, the similar component specifying unit 114 sets the use case A and other use cases B in which the similar case specifying unit 112 cannot determine that the number of use case scenarios in which the pieces of information all match is a predetermined number or more. The input interface 105 accepts the designation of the component a for the use case scenario belonging to the use case A and the component b for the use case scenario belonging to the other use case B, and the designation of the designated component a accepted here The information and the information of the designated component b are collated to identify a set of components that include the same predetermined character string between the designated components a and b, and a list of the identified component set is output to the output interface 106. The common component designation from the component set of the list is received by the input interface 105, and the common component is associated with the use case scenarios of the use case A and the use case B in the use case / component association information table 131. This information may be set.

  The similar component specifying unit 114 in the system 100 shown here may be realized as hardware, as in the units 110 to 113, or an appropriate storage device such as a memory or HDD (Hard Disk Drive). It may be realized as a program stored in In this case, the CPU of each device constituting the system 100 reads the corresponding program from the storage device into the memory in accordance with the program execution, and executes it.

--- Table structure examples in other embodiments ---
Here, an example of the data structure of a table provided in the storage device 101 in addition to the tables 125 to 128 described above in the system 100 according to another embodiment will be described. FIG. 9 is a diagram showing data configuration examples of (a) existing component information table 129, (b) component pattern table 130, and (c) use case / component association information table 131 in the present embodiment.

  Here, the existing component information table 129 is a table for storing information on existing components designed from use case scenarios, and a record is generated using a component ID for identifying component information registered in the system 100 as a key. Has been. The component ID is uniquely set for all components in the system 100. Such an existing component information table 129 is a collection of records in which each component name, component pattern ID, information name ID, and verb ID information are associated with each other using the component ID as a key.

  In addition, the component pattern table 130 may be integrated with the existing component information table 129 and the component pattern ID as a key (configuration in claims), but in the present embodiment, the component pattern ID is used as a key. A relational database linked to each other. This component pattern table 130 is a table for storing information on the constituent pattern of the character string in the component. The component pattern table 130 uses the component pattern ID as a key to specify a character string constituting the component, for example, “<information name 1> <verb>”. A set of records in which character string pattern information such as “<information name 1> and <information name 2> is <verb>” and “<information name 1> and <information name 2> is <verb>” It is a body.

  The use case / component association information table 131 is a table that defines the correspondence between use cases, use case scenarios belonging to the use cases, and components of the use case scenarios. A record is generated using a use case ID for identifying use case information registered in the system 100 as a key. The use case / component association information table 131 uses the use case ID as a key, and records that associate each information of the ID of the use case scenario belonging to the corresponding use case and the ID of the component associated with the use case scenario. It is an aggregate of.

--- Example of processing flow in another embodiment 1 ---
Subsequently, an example of a processing procedure of the use case scenario creation support method in this embodiment will be described. FIG. 10 is a flowchart showing a processing procedure example 1 of the use case scenario creation support method of another embodiment. In this case, the screen output unit 110 of the system 100 transmits, for example, use case selection screen data (stored in the storage device 101 of the system 100) to the operation terminal 200, and accepts a use case selection instruction (s1000). ). As the selection screen, for example, the input screen 1200 of FIG. 12 can be assumed, and it is assumed that an interface capable of selecting a use case application target (insurance system, pension type) is included. The example of FIG. 12 shows a situation in which “instruct transmission / reception of pension split information” is selected from the user by a pull-down menu as a use case.

  The screen output unit 110 uses the application target in the existing use case information table 125 based on a use case selection instruction (including use case application target information) obtained from the operation terminal 200 via the selection screen. The use case corresponding to is specified (s1001). The screen output means 110 reads the use case scenario pattern associated with the use case specified here from the use case scenario description table 127 (s1002). Also, the combination information of each use case scenario pattern read here is also read from the use case scenario description table 127, and options for each of the actor name, target information, and verb determined in the combination information are displayed in the option table. Read from 128 (s1003).

  As shown in the input screen 1200 of FIG. 12, the screen output unit 110 is an input screen that accepts selection of an actor name, an information name, and a verb in a character string for each of a plurality of use case scenario patterns within the range of the options. Data is generated and transmitted to the operation terminal 200 (s1004). For example, on the operation terminal 200, the input screen 1200 selects a user-desired scenario pattern (in the figure: patterns 1 to 5) from among the use case scenario patterns, and the actor name, information name, and verb It is an interface to select from the choices. As such an interface for selection, for example, a pull-down or a radio button can be assumed.

  In the example of FIG. 12, the user uses the use case scenario: “add new”, scenario pattern: “pattern 1”, actor name “system”, information name 1 “pension benefit processing result information”, and verb “edit”. Since it is selected, the use case scenario to be created is not an existing use case scenario but a new one, and its content is “the system edits pension benefit processing result information”.

  Subsequently, the scenario acquisition unit 111 of the system 100 receives the use case scenario pattern selection instruction: “pattern 1” and the actor name in the use case scenario pattern from the operation terminal 200 through the input screen 1200: “system”, target Information: Information name 1 “Pension benefit processing result information” and verb: “Edit” selection instruction is accepted, and the combination of actor name, information name, and verb specified in the character string by the selection instruction Use case scenario: Information “system edits pension benefit processing result information” is acquired and stored in the existing use case scenario description information table 126 (s1005).

  Next, the similar component specifying unit 114 of the system 100 has acquired information of a predetermined use case scenario: “the system edits the pension benefit processing result information” up to step s105. The designation of the component is accepted on the input screen 1200 (input interface 105) (s1006). In the example of the input screen 1200 of FIG. 12, component data “edit pension benefit processing result information” is extracted from the use case scenario information on the system side and displayed in the display column 1250. The user recognizes the component information in the display field 1250, and if it is determined that a change is necessary, the user presses the “change / display component information” button 1251 to execute the editing operation of the component data. On the other hand, on the system side, it is only necessary to detect the pressing of the “component information change / display” button 1251 and accept the editing work in the display field 1250 (that is, the display field 1250 only when the button 1251 is pressed). Editing work such as writing, deleting, and moving text data.)

  On the other hand, when the user accepts the component data “Edit pension benefit processing result information”, the user presses the determination button 1252. Then, it is assumed that the similar component specifying unit 114 receives the designation of the component for the use case scenario by pressing this button.

  Subsequently, the similar component specifying unit 114 collates the information on the designated component received in step s1006 with the information on the existing component stored in the existing component information table 129. An existing component including the same character string as the predetermined character string is specified (s1007). In the above example, the similar component specifying unit 114 compares the component information “edit pension benefit processing result information” with the existing component information stored in the existing component information table 129. Then, the existing component including the information “pension benefit processing result information” as the information name and “edit” as the verb is specified.

  A search result screen example 1300 of FIG. 13 is shown as an example of the screen displaying the information of the existing component specified by the similar component specifying unit 114 in this way. In this screen example, the similar component specifying unit 114 specifies the existing component having the component ID “CPS00000001” and the existing component having the component ID “CPS00000002”. Thus, the similar component specifying unit 114 displays the list 1310 of existing components specified in the step s1007 on the search result screen example 1300 (output interface 106).

  In addition, the similar component specifying unit 114 receives the designation of the common component from the existing components in the list 1310 through the input interface 105 (s1008). In this example, the existing component “CPS00000001” “Edit pension benefit processing result information” is specified, and this is the same content as the component in the display field 1250 of the input screen 1200. The radio button 1330 corresponding to the existing component “CPS00000001” is checked, and the enter button 1312 is pressed. Of course, when the existing component included in the list 1310 cannot be determined to have the same content as the component in the display field 1250 of the input screen 1200 and correction is necessary, the user presses the component information change / display button 1311. To do. At this time, the similar component specifying unit 114 may accept editing work in the component name column 1320 in the list 1310, for example.

  The similar component specifying unit 114 receives the check of the radio button 1330 and the press of the decision button 1312, makes the existing component “CPS00000001” a common component, and uses the predetermined use case scenario in the use case / component association information table 131. The information of the common component is set in association with (s1009). If the ID of the predetermined use case scenario is “UC00000004”, the similar component specifying unit 114 assigns the use case scenario ID “UCS00000001” to the use case ID of “UC00000004” in the use case / component association information table 131. "And the component ID" CPS00000001 "which is a common component are set in association with each other.

  The similar component specifying unit 114 is a set of use cases A and other use cases B in which the similar case specifying unit 112 cannot determine that the number of use case scenarios in which the respective information all match is a certain number or more. May be detected. In this case, the similar component specifying unit 114 receives the designation of the component a for the use case scenario belonging to the use case A and the component b for the use case scenario belonging to the other use case B by the input interface 105 (similar to step s1006). ).

  Then, the similar component specifying unit 114 collates the information of the designated component a that has received the designation here with the information of the designated component b, and finds a component that includes the same predetermined character string between the designated components a and b. Identify the set. For example, in the same manner as described above, a set of components that commonly include character strings such as “pension benefit processing result information” and “edit” are specified.

  Next, the similar component specifying unit 114 displays the list of component sets specified here on the output interface 106, and accepts the designation of the common component from the component set of the list by the input interface 105 (similar to step s1008). . The similar component specifying unit 114 sets the information of the common component in association with the use case scenarios of the use case A and the use case B in the use case / component association information table 131. That is, between the use case A and other use cases B in which the similar case specifying unit 112 cannot determine that the number of use case scenarios in which the respective pieces of information all match is a predetermined number or more (in other words, between use cases In this case, the candidate of the component that can be shared (the list) is presented to the user, and the common component is specified and set.

--- Example of processing flow in another embodiment 2 ---
Here, details of the common component specifying process will be described. FIG. 11 is a flowchart showing a processing procedure example 2 of the use case scenario creation support method of another embodiment. In this case, the similar component specifying unit 114 of the system 100 receives and specifies the designation of the component via the operation terminal 200, similarly to the step s1006 (s400). The component specified here is assumed to be a component “A”.

  Next, the similar component specifying unit 114 extracts one other component different from the component “A” from the existing component information table 129 (s401). Further, the similar component specifying unit 114 checks whether the component pattern ID, the information name ID1, the information name ID2, the information name ID3, and the verb ID are equal for the components “A” and “B”. s402).

  As a result of the collation, when the information name IDs match between the components “A” and “B”, the similar component specifying unit 114 stores the collation result of the information name ID as “1” in the memory 103, If the information name IDs do not match, the information name ID collation result is stored as “0” in the memory 103 (s403).

  When the verb IDs match between the components “A” and “B” as a result of the collation, the similar component specifying unit 114 stores the verb ID collation result as “1” in the memory 103. If the verb IDs do not match, the verification result of the verb ID is stored as “0” in the memory 103 (s404).

  After executing steps s401 to s404, the similar component specifying unit 114 confirms whether processing has been performed for all combinations of components in the existing component information table 129, and performs processing until processing has been performed for all combinations of components. Is looped (s405: No → s401).

  On the other hand, when the processing is performed for all the combinations of components in the existing component information table 129 (s405: Yes), the similar component specifying unit 114 reads the collation result of the information name ID and the verb ID from the memory 103. The component group in which any one of the matching results is “1” is specified. Then, the component group information sorted by the collation result of the information name ID and the verb ID is transmitted to the operation terminal 200 as in the step s1008 (s406).

  Based on the common component selection instruction (including component application information) obtained from the operation terminal 200, the similar component specifying unit 114 uses the common component linking destination use case (in the above example, “A”, “B”). ”) And the use case scenario description, the use case / component association information table 131 is updated (s407).

  According to the other embodiment described above, when a component is designed (detailed design process) based on the description of the use case scenario, which is executed after the use case scenario design (basic design process), the component is the same as the use case scenario. Can be shared efficiently and at low cost. When this component is shared, common components are searched based on the design information of the component before the design, so that wasteful processes such as rework for the designed component occur when trying to share the component. Also disappear.

  In addition, it is possible to extract candidates that can be shared among components, and reduce the burden on experts on the task of determining whether or not to perform commonization. Even with a scale of several thousand), it becomes easy to quickly extract common candidates and the like.

  Therefore, creation of use case scenarios and components is supported, and similar use cases and components that are candidates for common use can be searched with high accuracy.

  As mentioned above, although embodiment of this invention was described concretely based on the embodiment, it is not limited to this and can be variously changed in the range which does not deviate from the summary.

1 is an overall configuration diagram of a use case scenario creation support system in the present embodiment. It is a figure which shows each data structural example of (a) existing use case information table in this embodiment, (b) existing use case scenario description information table, (c) use case scenario description table, and (d) choice table. It is a flowchart which shows the process procedure example 1 of the use case scenario creation assistance method of this embodiment. It is a flowchart which shows process sequence example 2 of the use case scenario creation assistance method of this embodiment. It is a flowchart which shows process sequence example 3 of the use case scenario creation assistance method of this embodiment. It is a figure which shows the example of an input screen of this embodiment. It is a figure which shows the example of a search result screen of this embodiment. It is a whole block diagram of the use case scenario creation assistance system in other embodiment. It is a figure which shows each data structural example of (a) existing component information table in this embodiment, (b) component pattern table, and (c) use case component linked information table. It is a flowchart which shows the process procedure example 1 of the use case scenario creation assistance method of other embodiment. It is a flowchart which shows process sequence example 2 of the use case scenario creation assistance method of other embodiment. It is a figure which shows the example of an input screen of other embodiment. It is a figure which shows the example of a search result screen of other embodiment.

Explanation of symbols

100 Use Case Scenario Creation Support System 101 Storage Device 102 Program 103 Memory 104 CPU
105 Input Interface 106 Output Interface 107 Communication Device 110 Screen Output Unit 111 Scenario Acquisition Unit 112 Similar Case Identification Unit 113 Use Case Scenario Analysis Unit 114 Similar Component Identification Unit 125 Existing Use Case Information Table 126 Existing Use Case Scenario Description Information Table 127 Use Case Scenario description table 128 Choice table (actor name table, information name table, verb table)
129 Existing component information table 130 Component pattern table 131 Use case / component linked information table 140 Network 200 Operation terminal

Claims (9)

A computer system that supports the creation of use case scenarios,
An option table that defines the actor name that is the execution subject of the process, which is a constituent element of the use case scenario, the target information of the process executed by the actor, and the verb information according to the process executed by the actor ,
For each use case scenario pattern, a use case scenario description table that defines combination information of the actor name, target information, and verb in the character string forming the corresponding use case scenario;
The combination information of each use case scenario pattern is read from the use case scenario description table, and the options for the actor name, target information, and verb defined in the combination information are read from the option table, and the use case scenario Screen output means for generating data of an input screen that accepts selection of an actor name, target information, and verb in a character string for each pattern within the range of the options, and displaying it on an output interface;
Accepting the use case scenario selection instruction and the actor name, target information, and verb selection instruction in the use case scenario through the input screen, and the actor name, target information specified in the character string by the selection instruction, Scenario acquisition means for storing use case scenario information consisting of a combination of a verb and a verb in an existing use case scenario description information table;
A use case scenario creation support system characterized by comprising:   Read the use case scenario information from the existing use case scenario description information table and the use case scenario of another use case different from the use case to which this use case scenario belongs, and use cases between the read use case scenarios The match of the scenario pattern, actor name, target information, and verb information is determined, and the use case and the other use cases are similar if the number of use case scenarios that match all the information is equal to or greater than a certain number. The use case scenario creation support system according to claim 1, further comprising a similar case specifying unit that displays information on the use case group on an output interface as a use case group to be used. In the existing use case scenario description information table, each use case scenario pattern, actor name, target information, and verb information included in each use case scenario is an ID that can uniquely identify each information.
The similar case specifying means determines whether the use case scenario pattern, actor name, target information, and verb information match between use case scenarios read from the existing use case scenario description information table. To determine the match of
The use case scenario creation support system according to claim 2. The existing use case scenario description information table stores information on the applicable business of the use case for each use case scenario,
The similar case specifying means is for reading out the information on the business to be applied of the corresponding use case together with the information on the use case group from the existing use case scenario description information table and displaying it on the output interface.
The use case scenario creation support system according to claim 2 or 3.   For a use case scenario that is read from a predetermined storage device or acquired from an input interface, the actor name, target information, and verb included in the character string, and the permutation of the actor name, target information, and verb in the character string For each of the use case scenario patterns in the use case scenario description table, and if it does not match any use case scenario pattern included in the use case scenario description table, the actor name included in the character string of the use case scenario, A use case scenario in which a new use case scenario pattern including target information and verbs and permutation information in the character string of the actor name, target information, and verb is registered in the use case scenario description table. Specially equipped with analysis means Use Case Scenario generation support system according to any one of claims 1 to 4. An existing component information table that stores information on existing components designed from use case scenarios, and use case components that define the correspondence between use cases, use case scenarios belonging to the use cases, and components of the use case scenarios A storage device for storing a linked information table;
The specification of a component for a predetermined use case scenario is received by the input interface, and the specification of the specified component received here is collated with the information of the existing component stored in the existing component information table. An existing component that includes the same character string as the predetermined character string included in the component is identified, the list of the existing components identified here is displayed on the output interface, and the common component specification from the existing components in the list is input interface. And a similar component specifying means for setting the information of the common component in association with the predetermined use case scenario in the use case / component association information table. Use Case Scenario generation support system according to any one of claims 1 to 5 symptoms.   The similar component specifying unit detects a set of use cases A and other use cases B that the similar case specifying unit could not determine that the use case scenario group in which all the pieces of information all match is a certain number or more, The specification of component a for the use case scenario belonging to use case A and component b for the use case scenario belonging to other use case B is received by the input interface, and the information of designated component a and the designated component b received here. To identify a set of components containing the same predetermined character string between the designated components a and b, and display a list of the specified component set on the output interface. Component The common component specification from the input set is received by the input interface, and the common component information is set in association with the use case scenarios of the use case A and the use case B in the use case / component association information table. The use case scenario creation support system according to claim 6, A computer that supports the creation of use case scenarios
An option table that defines the actor name that is the execution subject of the process, which is a constituent element of the use case scenario, the target information of the process executed by the actor, and the verb information according to the process executed by the actor ,
For each use case scenario pattern, the storage device includes a use case scenario description table that defines combination information of the actor name, target information, and verb in the character string that forms the corresponding use case scenario.
The combination information of each use case scenario pattern is read from the use case scenario description table, and the options for the actor name, target information, and verb defined in the combination information are read from the option table, and the use case scenario Screen output processing for generating data of an input screen that accepts an actor name, target information, and verb selection in a character string for each pattern within the range of the options and displaying them on an output interface;
Accepting the use case scenario selection instruction and the actor name, target information, and verb selection instruction in the use case scenario through the input screen, and the actor name, target information specified in the character string by the selection instruction, Scenario acquisition process that stores use case scenario information consisting of combinations of verbs and verbs in an existing use case scenario description information table;
Use case scenario creation support method characterized by executing In order to support the creation of use case scenarios, the name of the actor that is the execution subject of the process, the target information of the process executed by the actor, and the verb corresponding to the processing content executed by the actor are the components of the use case scenario An option table that defines options for each information, and a use case scenario description table that defines combination information of the actor name, target information, and verb in the character string forming the corresponding use case scenario for each use case scenario pattern In the computer provided in the storage device,
The combination information of each use case scenario pattern is read from the use case scenario description table, and the options for the actor name, target information, and verb defined in the combination information are read from the option table, and the use case scenario Generating input screen data for accepting selection of an actor name, target information, and verb in a character string for each pattern within the range of the options, and displaying the data on an output interface;
Accepting the use case scenario selection instruction and the actor name, target information, and verb selection instruction in the use case scenario through the input screen, and the actor name, target information specified in the character string by the selection instruction, Storing use case scenario information consisting of a combination of a verb and a verb in an existing use case scenario description information table;
Use case scenario creation support program to execute.