JP2014048745A - Use case scenario creation support device, use case scenario creation method, and use case scenario creation support program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To support a creation of a use case scenario with no omission based on a relation with an actor and input/output information between respective use case scenarios.SOLUTION: A computer system 10 reads a business requirement scenario and actor information of the business corresponding to the business requirement scenario from a storage part 4, and executes processing in which a business use case scenario relating to the business is generated with an actor as a subject in a simple sentence obtained by analyzing the business requirement scenario and stored in a storage part 4, and processing in which information of the correspondence relation in the storage part 4 with respect to the actor of the generated business use case scenario is read, and based on the read information, another actor associated with the actor generates the business use case scenario of the related business to be executed in relation to the business use case scenario so as to be stored in the storage part 4.

Description

  The present invention relates to a use case scenario creation support apparatus, a use case scenario creation support method, and a use case scenario creation support program. Specifically, the relationship between actors and input / output information between each use case scenario This technology relates to technology that supports the creation of a complete use case scenario.

  In business system development, business function hierarchies, business flows, and use case scenarios are often created and used. Among them, regarding the use case scenario, a technique for generating a use case scenario by accepting from the user selection of a configuration pattern of the use case scenario, an actor name, target information, and a verb is proposed.

  Examples of such prior art include, for example, the name of an actor that is a process execution subject, which is a constituent element of a use case scenario, target information of a process executed by the actor, and verb information corresponding to the processing content executed by the actor A choice table defining the choices, a use case scenario description table defining 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, and the use The combination information of each use case scenario pattern is read from the case scenario description table, and the options for each of the actor name, target information, and verb defined in the combination information are read from the option table, for each use case scenario pattern In the string A screen output means for generating data of an input screen that accepts selection of an actor name, target information, and a verb within the range of the options and displaying them on an output interface, and through the input screen, a use case scenario selection instruction and the use Accepts an instruction to select an actor name, target information, and verb in a case scenario, and uses the existing use case scenario information consisting of a combination of the actor name, target information, and verb specified in the character string by the selection instruction. There has been proposed a use case scenario creation support system (Patent Document 1) that includes scenario acquisition means for storing in a use case scenario description information table.

JP 2009-151742 A

  When creating a use case scenario according to the prior art, a user can perform a use case scenario creation operation one sentence at a time while referring to a description list in accordance with a scenario pattern that has been patterned in advance. However, it is difficult to generate all the scenario use cases without omission while reliably considering the mutual relationship between each actor and input / output information between the use case scenarios related in the flow.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a technology that supports the creation of a complete use case scenario based on the relationship between actors and input / output information between the use case scenarios.

  The use case scenario creation support device of the present invention that solves the above problems includes input information when executing a task, output information when executing the task based on the input information, information of an actor that executes the task, In addition, information on the business requirement scenario describing the contents of the corresponding business, and information on the correspondence between the actor in each business and the other actor involved in the actor through the predetermined action in the relevant business are stored. Read the storage unit, the business requirement scenario, and the actor information of the business corresponding to the business requirement scenario from the storage unit and analyze the business requirement scenario, and use the relevant actor as the subject for the business use related to the business Business use case scenario conversion unit that generates a case scenario and stores it in the storage unit, and the generated business use For the actor in the service scenario, the information on the correspondence relationship in the storage unit is read, and based on the read information, another actor involved in the relevant actor uses the business use of the related business to be executed in relation to the business use case scenario. And an additional business use case scenario generation unit that generates a case scenario and stores the case scenario in a storage unit.

  Further, the business use case scenario creation support method of the present invention includes input information when executing a business, output information when executing the business based on the input information, information of an actor executing the business, and A storage unit that stores information on the business requirement scenario describing the content of the corresponding business, information on the correspondence between the actor in each business and the other actor involved in the actor through a predetermined action in the business In a simple sentence obtained by analyzing the business requirement scenario and the business requirement scenario and the actor information of the business corresponding to the business requirement scenario from the storage unit, the computer equipped with The process of generating a business use case scenario and storing it in the storage unit, and the generated business use case scenario Business use case scenario of a related business to be executed in relation to the business use case scenario by another actor involved in the corresponding actor based on the read information. Is generated and stored in the storage unit.

  In addition, the use case scenario creation support program of the present invention includes input information when executing a business, output information when executing the business based on the input information, information of an actor executing the business, and A storage unit that stores information on business requirement scenarios describing the content of business, actors in each business, and correspondence information between actors involved in the business through predetermined actions in the business Read the business requirement scenario and the actor information of the business corresponding to the business requirement scenario from the storage unit, and analyze the business requirement scenario in a simple sentence obtained from the corresponding computer. Processing for generating a use case scenario and storing it in the storage unit, and the generated business use case scenario For the actor, the information on the correspondence in the storage unit is read, and based on the read information, the business use case scenario of the related business that another actor involved in the actor should execute in relation to the business use case scenario. And generating and storing the data in the storage unit.

  According to the present invention, it is possible to support creation of a use case scenario with no omission based on the relationship of actors and input / output information between the use case scenarios.

It is a figure which shows the function structural example of the use case scenario creation assistance apparatus which concerns on this embodiment. It is a figure which shows the hardware structural example of the use case scenario creation assistance apparatus in this embodiment. It is a figure which shows the example of the business function hierarchy table in this embodiment. It is a figure which shows the example of the business requirement scenario table in this embodiment. It is a figure which shows the example of the business use case scenario table in this embodiment. It is a figure which shows the example of the business use case scenario conditional sentence table in this embodiment. It is a figure which shows the example of the business use case scenario order table in this embodiment. It is a figure which shows the example of the actor related information table in this embodiment. It is a figure which shows the example of the actor business pattern table in this embodiment. It is a figure which shows the example of the predicate table in this embodiment. It is a flowchart which shows the procedure example 1 of the use case scenario creation assistance method in this embodiment. It is a flowchart which shows the procedure example 2 of the use case scenario creation assistance method in this embodiment. It is a flowchart which shows the procedure example 3 of the use case scenario creation assistance method in this embodiment. It is a flowchart which shows the example 4 of a procedure of the use case scenario creation assistance method in this embodiment. It is a figure which shows the example 1 of a screen in this embodiment. It is a figure which shows the example 2 of a screen in this embodiment. It is a figure which shows the example 3 of a screen in this embodiment.

--- Example of device configuration ---
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a diagram illustrating a functional configuration example of a use case scenario creation support apparatus 10 according to the present embodiment. FIG. 2 is a diagram illustrating a hardware configuration example of the use case scenario creation support apparatus 10 according to the present embodiment. It is. The same reference numerals indicate the same components. The use case scenario creation support apparatus 10 is a computer system that supports creation of a complete use case scenario based on the relationship between actors and input / output information between the use case scenarios.

  The functional units included in the use case scenario creation support apparatus 10 of this embodiment will be described. The functional unit described below can be said to be a functional block implemented by executing the program 5 held in the storage device 4 by the use case scenario creation support device 10 as an information processing device (see also FIG. 2). The storage device 4 (storage unit) describes at least input information for executing a job, output information when the job is executed based on the input information, and information on an actor executing the job. Business function hierarchy table 4100, business requirement scenario table 4200 including at least business requirement scenario information describing the contents of the relevant business, actors in each business, and the relevant business involved in the actors through predetermined actions An actor related information table 4310 in which at least information on the correspondence relationship with another actor is described is stored. The use case scenario creation support apparatus 10 of the present embodiment holds other tables, but details will be described later including the above-described tables.

  The use case scenario creation support apparatus 10 according to the present embodiment reads from the storage device 4 the business requirement scenario of the business requirement scenario table 4200 and the actor information of the business corresponding to the business requirement scenario in the business function hierarchy table 4100. In the single sentence obtained by analyzing the business requirement scenario, a business use case scenario related to the business is generated with the corresponding actor as the subject, and this is stored in the business use case scenario table 4410 in the business use case scenario DB 44 of the storage device 4. The business use case scenario conversion unit 12 is provided.

  The use case scenario creation support apparatus 10 of this embodiment includes a business requirement scenario definition unit 11. The business requirement scenario definition unit 11 displays input information, output information, and actor information on the display device 3 for each use case from the business function hierarchy table 4100 in the business function hierarchy DB 41, and the user describes based on this display. The business requirement scenario definition obtained is acquired via the input device 2, and the acquired business requirement scenario data is stored in the business requirement scenario table 4200 in the business requirement scenario DB 42. Of course, the use case scenario creation support apparatus 10 may not include the business requirement scenario definition unit 11 and may store necessary data such as business requirement scenarios in the business requirement scenario table 4200 of the storage device 4 in advance. .

  Further, the use case scenario creation support apparatus 10 of the present embodiment reads the stored information related to the actor related information table 4310 in the actor related information DB 43 of the storage device 4 for the actors of the generated business use case scenario, and uses the read information as the read information. Based on this, another actor involved in the corresponding actor generates a business use case scenario of a related business to be executed in relation to the business use case scenario, and this is used as a business use case in the business use case scenario DB 44 of the storage device 4. An additional business use case scenario generation unit 13 stored in the scenario table 4410 is provided.

  The use case scenario creation support apparatus 10 of the present embodiment includes a predicate DB 45 in the storage device 4. The predicate DB 45 holds a predicate table 4500 in which information on options related to the predicate among the subject, predicate, and object constituting the business use case scenario is described.

  In this case, when the business use case scenario conversion unit 12 analyzes the business requirement scenario and obtains a single sentence, the predicate candidate extracted from the business requirement scenario by the analysis is used as a predicate group as each option in the predicate table 4500. , And a predicate candidate that has a similar meaning to the predicate candidate is specified by a general language analysis process or the like, and the specified option is further set as a predicate of the single sentence.

  In addition, the use case scenario creation support apparatus 10 according to the present embodiment holds a condition presence / absence code value as information indicating the presence / absence of an execution condition for the predetermined action in the correspondence relationship in the above-described actor-related information table 4310. doing. In addition, the use case scenario creation support apparatus 10 holds an actor task pattern table 4320 in the storage device 4. The actor business pattern table 4320 is a table in which information indicating the contents of the execution condition is described. For example, in the actor related information table 4310, when the condition presence / absence code is “1”, that is, there is a branch condition, This is information for generating a conditional statement. Details of the actor task pattern table 4320 will be described later.

  In this case, the additional business use case scenario generation unit 13 reads the correspondence information and the condition presence / absence code value in the actor related information table 4310 of the storage device 4 for the actor of the generated business use case scenario. When there is an execution condition for the predetermined action, the content of the execution condition corresponding to the corresponding execution condition is acquired from the above-described actor business pattern table 4320, and the subject matter of the condition determination indicated by the content of the execution condition is applicable Extracted from the business requirement scenario of business (derived from the above-mentioned business requirement scenario table 4200), generates a conditional statement that describes whether or not the content of the execution condition is satisfied with respect to the target item, and uses this as a business use of the storage device 4 Business Use Case Scenario Condition Statement Table in Case Scenario DB 44 Further it has a function of storing in 4420.

  In addition, the additional business use case scenario generation unit 13 obtains information on different actions depending on whether or not the contents of the execution condition are satisfied from the contents of the execution condition. Based on whether or not the content of the execution condition indicated by the conditional statement is satisfied by generating a business use case scenario for each business in which the separate actor executes the corresponding action. The business use case scenario of each business branching from the business is further provided with a function of performing association with the conditional statement and storing it in the business use case scenario table 4410 of the storage device 4.

  Further, the additional business use case scenario generation unit 13 described above further includes a function for displaying the business use case scenario generated for the business and the business use case scenario generated for the related business on the display device 3. .

  In addition, when the above-described additional business use case scenario generation unit 13 displays each business use case scenario generated for the business and the related business on the display device 3, the user selects a business use case scenario to be modified from the user. A reception field that is an appropriate interface to be received is displayed together, and a correction instruction from the user is received by the input device 2 for the business use case scenario that has been selected for correction in the reception field, and the correction instruction is received. A function for executing correction processing of the corresponding business use case scenario is further provided.

  In addition, when the additional business use case scenario generation unit 13 receives the selection of the correction target in the reception field, the pop-up form of the input field that is an interface for receiving a correction instruction for the business use case scenario to be corrected is displayed. The display device 3 is further provided with a function of displaying it and receiving the correction instruction from the user in the input field.

  The additional business use case scenario generation unit 13 displays an instruction to change the order of the business use case scenarios when the business use case scenarios generated for the business and the related business are displayed on the display device 3. The function further includes a function for displaying a reception field that is an interface received from, and executing processing for changing the arrangement order between the corresponding business use case scenarios in accordance with the change instruction received in the reception field.

  Further, the additional business use case scenario generation unit 13 described above displays the relationship between the business use case scenarios (execution order, branching) when displaying the business use case scenarios generated for the business and the related business on the display device 3. Etc.), and an instruction to change the arrangement order between business use case scenarios is obtained by accepting, via the input device 2, a drag-and-drop operation to a predetermined position of the corresponding business use case scenario during the display. In addition, it further has a function of executing a process for changing the arrangement order between the corresponding business use case scenarios in accordance with the acquired change instruction.

  Further, the additional business use case scenario generation unit 13 described above displays different display attributes (for example, characters and characters) on the display device 3 between the business use case scenario generated for the business and the business use case scenario generated for the related business. And a function of executing processing for display with a line color, highlighting of underline and outline, etc.).

  The hardware configuration of the above-described use case scenario creation support apparatus 10 is as shown in FIG. The use case scenario creation support apparatus 10 performs overall control of the apparatus itself by executing a storage device 4 (storage unit) composed of an appropriate non-volatile storage device such as a hard disk drive and a program 5 held in the storage device 4. In addition, a CPU 1 that is an arithmetic device that performs various determinations, calculations, and control processes, an input device 2 that receives input from a user by key-in and mouse gestures, a display device 3 such as a display that outputs processing data, and the like. The storage device 4 stores at least a program 5 for implementing functions necessary for the use case scenario creation support device 10 of the present embodiment and data 6 such as various tables and databases. The storage device 4 may be provided in a separate device via the network and the use case scenario creation support device 10, or may be provided integrally.

--- Data structure example ---
Next, an example of the structure of data used by the use case scenario creation support apparatus 10 of this embodiment will be described. FIG. 3 is a diagram showing an example of the business function hierarchy table 4100 stored in the business function hierarchy DB 41 in the present embodiment. As shown in FIG. 3, the business function hierarchy table 4100 includes a management code 4101 that is identification information of a corresponding subtask, a subtask 4102 that is the name of the subtask, a use case code 4103 for managing a corresponding use case, and use case identification information. It includes a record including each value of an actor 4104, input information 4105, output information 4106, and actor 4107 as actor information.

  FIG. 4 is a diagram showing an example of the business requirement scenario table 4200 stored in the business requirement scenario DB 42 in the present embodiment. As shown in FIG. 4, the business requirement scenario table 4200 includes a business requirement scenario code 4201, which is business requirement scenario identification information, and input information (same as the input information in the record of the corresponding subtask in the business function hierarchy table 4100). 4202, output information 4203 (same as the output information in the record of the corresponding subtask in the business function hierarchy table 4100), and a record including each value of the business requirement scenario 4204.

  FIG. 5 is a diagram showing an example of the business use case scenario table 4410 stored in the business use case scenario DB 44 in the present embodiment. As shown in FIG. 5, this business use case scenario table 4410 includes a business UC scenario code 4411 as identification information of a business use case scenario, input information 4412, output information 4413, an actor 4414 of the corresponding business use case scenario, and an object 4415. , And a record including each value of the predicate 4416.

  FIG. 6 is a diagram showing an example of the business use case scenario condition statement table 4420 stored in the business use case scenario DB 44 in this embodiment. As shown in FIG. 6, the business use case scenario conditional statement table 4420 includes a business UC scenario code 4421 for identifying a business use case scenario including a conditional statement, and a record including each value of the conditional statement 4422. Yes.

  FIG. 7 is a diagram showing an example of the business use case scenario order table 4430 stored in the business use case scenario DB 44 in this embodiment. As shown in FIG. 7, the business use case scenario order table 4430 includes a use case code 4431 for managing business use case scenarios in units of use cases, a scenario order code 4432 indicating the order of business use case scenarios, and It is composed of records including values of the business UC scenario code 4433 of the corresponding business use case scenario.

  FIG. 8 is a diagram showing an example of the actor related information table 4310 stored in the actor related information DB 43 in the present embodiment. As shown in FIG. 8, this actor related information table 4310 includes a related information management code 4311 for managing actor related information in units of actors, an actor 4312, another actor 4313 related to the corresponding actor, and a corresponding actor. An action 4314 to be performed on another actor, a condition presence / absence code 4315 indicating the presence / absence of a subsequent branch condition for the above action, and a record including each value of the organization 4316 to which the actor 4312 belongs are configured.

  FIG. 9 is a diagram showing an example of the actor work pattern table 4320 stored in the actor related information DB 43 in the present embodiment. When the condition presence / absence code in the above-mentioned actor-related information table 4310 is “1”, that is, there is a branch condition, the actor work pattern table 4320 stores information for generating the conditional statement.

  As shown in FIG. 9, such an actor business pattern table 4320 includes a management code 4321 for managing records in units of branch conditions, division contents 4322 indicating items to be judged for branch conditions, and possible variations of items indicated by the division contents 4322. , And a record including business pattern 4320 corresponding to a predicate in a business use case scenario.

  FIG. 10 is a diagram showing an example of the predicate table 4500 stored in the predicate DB 45 in the present embodiment. This predicate table 4500 stores predicates used for business use case scenario conversion, additional business use case scenario generation, and actor business pattern setting. As shown in FIG. 10, the predicate table 4500 includes a predicate code 4501 for identifying a record for each predicate and a record including each value of a predicate 4502 set in advance.

--- Processing example 1 ---
Hereinafter, the 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 5 that the use case scenario creation support apparatus 10 reads into the storage device 4 and executes. And this program 5 is comprised from the code | cord | chord for performing various operation | movement demonstrated below.

  FIG. 11 is a flowchart showing a procedure example 1 of the use case scenario creation support method in the present embodiment. First, the business requirement scenario definition unit 11 in the use case scenario creation support apparatus 10 receives input information, output information, and actor information from the business function hierarchy table 4100 in the business function hierarchy DB 41 to the display apparatus 3 in units of use cases. The business requirement scenario definition displayed by the user and described by the user based on this display is obtained via the input device 2, and the business requirement scenario code (code for uniquely identifying the business requirement scenario) is obtained in the obtained business requirement scenario data. Is stored in the business requirement scenario table 4200 in the business requirement scenario DB 42 (step 100).

  Next, the business use case scenario conversion unit 12 in the use case scenario creation support apparatus 10 decomposes the business requirement scenario acquired as described above at the word level, and searches for conjunctions by morphological analysis processing. When the conjunction is present, the business use case scenario conversion unit 12 divides the scenario sentence before and after the corresponding conjunction to obtain a plurality of simple sentences (step 110). For example, with regard to the business requirement scenario of “When application documents are received, the application contents are inspected and necessary documents are checked for leaks”, “Accept application documents”, “Inspect application contents”, “Attach required documents” A simple sentence "Check for leaks" is obtained. The same applies to the following, but the use case scenario creation support apparatus 10 is provided with various language analysis processing engines such as morphological analysis and syntax analysis for such processing.

  Subsequently, the business use case scenario conversion unit 12 converts the business requirement scenario divided into the single sentence format as described above into “object + predicate”, that is, “△△△ ○” regardless of the subject. (Step 120). For the predicate, the business use case scenario conversion unit 12 searches the predicate choice stored in the predicate table 4500 of the predicate DB 45 for a predicate similar to the word included in the single sentence, and the above-mentioned “object” It is set as a predicate in “+ Predicate”. For example, for the single sentence “check application contents”, the business use case scenario conversion unit 12 searches the predicate table 4500 for the word “confirmation” and identifies the predicate “confirm” as having similar meaning. And get the sentence “Confirm application details”.

  Next, the business use case scenario conversion unit 12 fetches the business scenario from the business function hierarchy table 4100 of the business function hierarchy DB 41 into the business requirement scenario converted into each sentence of “object + predicate” as described above. Actor information 4107 is added to generate a business use case scenario in the form of “subject (actor) + object + predicate”, that is, “□□ is △△△”, and this is used as a business use case scenario table 4410. (Step 130).

  Subsequently, the additional business use case scenario generation unit 13 in the use case scenario creation support apparatus 10 searches the actor related information table 4310 of the actor related information DB 43 for information on the business use case scenario actor generated in step 130 described above. Is performed (step 140), and it is determined whether there is another actor related to the corresponding actor (step 150).

  As a result of the determination, if another related actor exists (step 150: Yes), the additional business use case scenario generation unit 13 advances the process to step 160. For example, if the corresponding actor is “person in charge” and information retrieval is performed in the actor-related information table 4310 using this “person in charge” as a key, in the case of the example of FIG. The existence of “approver” can be specified as another actor related to “”. On the other hand, when another related actor does not exist (step 150: No), the additional business use case scenario generation unit 13 advances the process to step 170.

  In step 160, the additional business use case scenario generation unit 13 extracts the action 4314 and the condition presence / absence code 4315 of the other actor “approver” described above from the actor related information table 4310 of the actor related information DB 43. In the example of the actor-related information table 4310 in FIG. 8, “Approve” can be extracted as the action 4314 in which “Approver” is the actor, and “1” can be extracted as the condition presence / absence code 4315.

  Further, when the extracted condition presence / absence code 4315 is “1”, that is, there is a condition for executing the corresponding action 4314, the additional business use case scenario generation unit 13 uses the value of the related information management code 4311 in the corresponding record as a key. The actor business pattern table 4320 is searched to identify a record having a management code 4321 that matches all or a predetermined digit with the value of the related information management code 4311, and extracts each value of the corresponding record. Details of step 160 will be described later with reference to FIG. In the example of the actor business pattern table 4320 in FIG. 9, each record of management codes 4321 “C123-01” and “C123-02” whose leading digits match the value “123-457” of the related information management code 4311. As the values of each applicable record, values such as category content “deficient”, category “none”, business pattern “approve”, category content “deficient”, category “present”, business pattern “not approved” Can be extracted.

  Subsequently, the additional business use case scenario generation unit 13 determines, for example, whether there are a plurality of other related actors for the above-mentioned corresponding actor “person in charge” (step 170). As a result of the determination, when there are a plurality of different actors (step 170: Yes), the additional business use case scenario generation unit 13 advances the processing to step 180. In the example of FIG. 8, since there is only one “approver” as another actor associated with the actor “person in charge”, there is “a plurality of other actors”. When there are not a plurality of different actors (step 170: No), the additional business use case scenario generation unit 13 advances the process to step 190.

  In step 180, the additional business use case scenario generation unit 13 sets a business order for the business performed between the actor “person in charge” and a plurality of other actors related thereto, for example. The information is associated with the corresponding use case code and stored in the business use case scenario order table 4430 illustrated in FIG. 7 (step 180). As an example of the business order setting process, for example, the additional business use case scenario generation unit 13 reads each of the above-mentioned corresponding actors from the actor related information table 4310 and each organization 4316 of each of a plurality of other actors related thereto. A value is extracted, a business having the same value of the organization 4316 between the corresponding actor and another actor, that is, a business having the same organization is specified, and the business order is determined in such a manner that the business in the same organization is given priority.

  Subsequently, the additional business use case scenario generation unit 13 determines that another actor involved in the corresponding actor is determined based on information obtained from the actor related information table 4310 and the actor business pattern table 4320 regarding the corresponding actor and the other actor. A business use case scenario of a related business to be executed in relation to a business use case scenario related to an actor (which is already stored in the business use case scenario table 4410) is generated, and the order of the corresponding business use case scenario already registered is generated. Based on the relationship (the business order set in step 180 above), it is added to the business use case scenario table 4410 (step 190). Details of step 190 will be described later with reference to FIG.

  Next, the additional business use case scenario generation unit 13 reads out all the generated business use case scenarios including the business use case scenario generated in step 190 described above from the business use case scenario table 4410, and displays the display device 3. (Step 200). In this display process, the additional business use case scenario generation unit 13 accepts, from the input device 2, a designation of correction from the user for the business use case scenario being displayed.

  FIG. 15 shows an example of a business use case scenario confirmation screen 10000 that is a display screen for the business use case scenario described above. The business use case scenario confirmation screen 10000 illustrated in FIG. 15 includes a business use case scenario display area 10010, a check box 10030 for accepting a correction designation from the user for each business use case scenario, and a newly added business use case scenario. The display area 10020 includes an order change check box 10040 for accepting designation of order change of business use case scenarios from the user, and a confirmation button 10050 for accepting designation of correction confirmation from the user. The business use case scenario generated for the business and the business use case scenario generated for the related business are displayed with different display attributes on the business use case scenario confirmation screen 10000. In the example in the figure, the display about the business use case scenario generated for the related business is underlined.

  When the designation of correction as described above is received from the user via the business use case scenario confirmation screen 10000 shown in FIG. 15, the additional business use case scenario generation unit 13 displays a confirmation button in the business use case scenario confirmation screen 10000. In response to a click on a predetermined icon such as 10050, for example, it is determined that the correction contents for the corresponding business use case scenario specified by the check box 10030 are confirmed (step 210: Yes), and the process proceeds to step 220. On the other hand, when the correction designation from the user has not been received (step 210: No), the additional business use case scenario generation unit 13 proceeds with the process to step 230.

  In step 220, the additional business use case scenario generation unit 13 changes the business use case scenario, the business use case scenario conditional statement (described later), and the business use case scenario order, for which the correction contents have been confirmed, according to the user's correction specification. (Step 220). Details of step 220 will be described later with reference to FIG.

  Next, the additional business use case scenario generation unit 13 converts the business use case scenario, the business use case scenario conditional statement, and the business use case scenario order created and additionally generated in the steps so far into the business use case scenario table 4410, The business use case scenario condition statement table 4420 and the business use case scenario order table 4430 are stored (step 230), and the flow ends.

--- Processing example 2 ---
Next, details of the processing in step 160 shown in FIG. 11 will be described with reference to FIG. FIG. 12 is a flowchart showing a procedure example 2 of the use case scenario creation support method in the present embodiment. In this case, the additional business use case scenario generation unit 13 extracts each value of the above-mentioned another actor 4313, action 4314, and condition presence / absence code 4315 from the actor related information table 4310 of FIG. 8 (step 161). In the example of the actor-related information table 4310 in FIG. 8, “approver” as another actor related to “person in charge”, “approval” as an action 4314 in which this “approver” becomes an actor, and the condition presence / absence code 4315 “1” can be extracted.

  Further, the additional business use case scenario generation unit 13 determines whether or not the extracted condition presence / absence code 4315 is “1”, that is, there is a condition for executing the corresponding action 4314 (step 162). If there is a condition for executing the corresponding action (step 162: Yes), the additional business use case scenario generation unit 13 searches the actor business pattern table 4320 using the value of the related information management code 4311 in the corresponding record as a key, A record having a management code 4321 whose value matches all or a predetermined digit with the value of the related information management code 4311 is specified, and each value of the corresponding record is extracted (step 163). In the example of the actor business pattern table 4320 in FIG. 9, each record of management codes 4321 “C123-01” and “C123-02” whose leading digits match the value “123-457” of the related information management code 4311. As the values of each applicable record, values such as category content “deficient”, category “none”, business pattern “approve”, category content “deficient”, category “present”, business pattern “not approved” Can be extracted.

  On the other hand, if there is no branch condition, that is, the condition presence / absence code is “0” (step 162: No), the additional business use case scenario generation unit 13 ends this flow.

  Subsequently, the additional business use case scenario generation unit 13 searches the action “approval” of the above-mentioned separate actor “approver” for a plurality of business patterns that are not captured (step 164). As a result of this search, if there is something that has not been captured (step 164: Yes), the additional business use case scenario generation unit 13 returns the processing to step 163. On the other hand, when there is no data that has not been captured (step 164: No), the additional business use case scenario generation unit 13 ends this flow.

--- Processing example 3 ---
Next, details of the processing in step 190 shown in FIG. 11 will be described with reference to FIG. FIG. 13 is a flowchart showing a procedure example 3 of the use case scenario creation support method in the present embodiment. In this case, the additional business use case scenario generation unit 13 conditionally branches the business use case scenario based on the information of the corresponding actor and other actors captured in step 160 described above (including the value of the condition presence / absence code 4315). (Step 191). If the result of this determination is that conditional branching occurs (step 191: Yes), the additional business use case scenario generation unit 13 advances the processing to step 195. On the other hand, when the conditional branch does not occur (step 191: No), the additional business use case scenario generation unit 13 advances the processing to step 192.

  In step 192, the additional business use case scenario generation unit 13 performs an action performed by the corresponding actor on another actor based on information obtained from the actor related information table 4310 and the actor business pattern table 4320 regarding the corresponding actor and the other actor. Is identified. Further, the additional business use case scenario generation unit 13 generates a sentence (for example, the person in charge requests approval from the approver) in which the corresponding actor is set as the subject and the action for the other actor specified in step 192 is set as a predicate. (Step 193).

  Next, the additional business use case scenario generation unit 13 takes in the information corresponding to the object from the input information and output information of the business requirement scenario table 4200 in FIG. 4 (eg, application content), and in step 193 described above In addition to the generated subject and predicate statements, a business use case scenario (for example, the person in charge asks the approver to approve the application contents) is generated (step 194). The process proceeds to step 197.

  Further, the additional business use case scenario generation unit 13 generates a conditional statement from the business requirement scenario and the business pattern category contents 4322 and 4323 obtained from the actor business pattern table 4320 (step 195). In the above example, it is possible to create a conditional statement such as “when there is no deficiency in the application contents”.

  In this case, the additional business use case scenario generation unit 13 obtains from the actor business pattern table 4320 the condition determination target items indicated by the category content 4322 and the category 4323 (the content of the execution condition), that is, “incomplete” ”,“ None ”should be judged,“ Application content ”is extracted from the business requirement scenario of the relevant business, and whether or not the“ deficiency ”that is the execution condition for the subject matter satisfies the condition of“ None ” The described conditional statement is generated.

  Subsequently, the additional business use case scenario generation unit 13 obtains, from the business requirement scenario, the actor related information table 4310, and the actor business pattern table 4320, the business use case scenario following the conditional statement generated in step 195 described above. Then, a business use case scenario in the form of “subject + object + predicate” such as “the approver approves the application contents” is generated and registered in the business use case scenario table 4410 (step 196), and the process is stepped. Proceed to 197.

  Further, the additional business use case scenario generation unit 13 refers to the above-described business use case scenario order table 4430 (information is set in the above step 180), and determines whether there is a next business according to the business order. (Step 197). As a result of this determination, when the next job exists (step 197: Yes), the additional job use case scenario generation unit 13 returns the process to step 191. On the other hand, when the next business does not exist (step 197: No), the additional business use case scenario generation unit 13 ends this flow.

--- Processing example 4 ---
Next, details of the processing in step 220 shown in FIG. 11 will be described with reference to FIG. FIG. 14 is a flowchart showing a procedure example 4 of the use case scenario creation support method in the present embodiment. In this case, the additional business use case scenario generation unit 13 reads out all the generated business use case scenarios including the business use case scenario generated in step 190 described above from the business use case scenario table 4410, and displays the display device 3. It is assumed that the input device 2 accepts a correction designation from the user for the business use case scenario being displayed. When such a modification specification is received from the user, the additional business use case scenario generation unit 13 receives a click on a predetermined icon or the like on the display screen, and confirms the correction content for the corresponding business use case scenario (step 221).

  Subsequently, the additional business use case scenario generation unit 13 determines whether the business use case scenario to be corrected is the business use case scenario itself, a conditional statement of the business use case scenario, or the business use case scenario order. (Step 222). This determination can be made from the specified content of the correction received on the above-described business use case scenario confirmation screen 10000 via the input device 2. For example, when the confirmation button 10050 is pressed with the designation in the check box 10030, the correction target can be determined as the business use case scenario itself. In addition, when the confirmation button 10050 is pressed in a state in which the check box 10030 corresponding to the conditional statement “to case” is entered, it can be determined that the correction target is a business use case scenario conditional statement. Further, when the confirmation button 10050 is pressed while the order change check box 10040 is checked, it can be determined that the correction target is the business use case scenario order.

  As a result of this determination, if the correction target is the business use case scenario itself (step 222: business use case scenario), the additional business use case scenario generation unit 13 advances the processing to step 223. On the other hand, when the correction target is a business use case scenario conditional statement (step 222: conditional statement), the additional business use case scenario generation unit 13 advances the process to step 224. On the other hand, when the correction target is the business use case scenario order (step 222: order), the additional business use case scenario generation unit 13 advances the processing to step 225.

  In step 223, the additional business use case scenario generation unit 13 corrects the corresponding part specified by the user in the corresponding business use case scenario according to the correction content specified by the user, and stores the corresponding data in the business use case scenario table 4410. Update and finish this flow. FIG. 16 shows an example of a business use case scenario correction screen 11000. The modification screen 11000 in FIG. 16 displays the business use case scenario designated by the check box 10030 on the business use case scenario confirmation screen 10000 described above, and designates the user's modification designation for the business use case scenario to be modified. It includes a configuration in which a balloon 11010 as an interface to accept is popped up. In addition, the correction screen 11000 includes a display of a correction button 11020 that accepts confirmation of correction by the user. The balloon 11010 described above is an interface that receives input for each element of “subject, object, predicate” in the business use case scenario. When the correction button 11020 is pressed in the balloon 11010, the additional business use case scenario generation unit 13 determines that the correction is confirmed.

  Further, in step 224, the additional business use case scenario generation unit 13 corrects the corresponding part specified by the user in the corresponding business use case scenario conditional sentence according to the correction content specified by the user, and the business use case scenario conditional sentence. The table 4420 is updated, and this flow is finished. This conditional sentence correction process is also performed by accepting the user's correction designation with the balloon 11000, as described above.

  In step 225, the additional business use case scenario generation unit 13 corrects the user-specified corresponding part in the corresponding business use case scenario order according to the user-specified correction content, and the business use case scenario order table 4430. And finish this flow. For example, in the above-described business use case scenario confirmation screen 10000, when the confirm button 10050 is pressed while the order change check box 10040 is checked, the additional business use case scenario generation unit 13 is exemplified in FIG. The business use case scenario order correction screen 12000 is displayed on the display device 3.

  In this case, the additional business use case scenario generation unit 13 refers to the business use case scenario order table 4430 for the order relationship between each business use case scenario, and displays each business use case scenario including the order relationship between the business use case scenarios. Will do. Specifically, the business use case scenario order correction screen 12000 displayed in this way is composed of an area 12010 for displaying a business use case scenario using the business UC scenario code as a key, and an area 12020 for visualizing the relationship between the business use case scenarios. ing.

  An area 12020 that visualizes the relationship between business use case scenarios is an area 12030 that displays the connection between business use case scenarios, a cursor 12040 that indicates the corresponding business use case scenario when the order is changed, and The confirmation button 12050 is used to confirm a business use case scenario whose order has been changed. When the user drags and drops a specific business use case scenario via the cursor 12040, the additional business use case scenario generation unit 13 orders the business use case scenario in relation to other business use case scenarios. Will be changed.

  Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications can be made without departing from the scope of the invention.

  According to this embodiment, it is possible to support the creation of a complete use case scenario based on the relationship between actors and input / output information between the use case scenarios.

  At least the following will be clarified by the description of the present specification. That is, in the business use case scenario creation support apparatus according to the present embodiment, the storage unit further stores information on options related to a predicate among subjects, predicates, and objects constituting the business use case scenario. When the use case scenario conversion unit analyzes the business requirement scenario and obtains a single sentence, the predicate candidate extracted from the business requirement scenario by the analysis is compared with the option in the storage unit, A similar thing may be specified and set as a predicate of the single sentence.

  Further, in the business use case scenario creation support apparatus of the present embodiment, the storage unit further includes information indicating the presence or absence of an execution condition and information indicating the content of the execution condition with respect to the predetermined action in the correspondence relationship. The additional business use case scenario generation unit stores the correspondence information in the storage unit and information indicating the presence or absence of the execution condition for the actor of the generated business use case scenario, and the predetermined action If there is an execution condition related to, the contents of the execution condition corresponding to the execution condition are acquired from the storage unit, the items for condition judgment indicated by the contents of the execution condition are extracted from the business requirement scenario of the corresponding business, and the target Processing to generate a conditional statement that describes whether or not the contents of the execution condition are satisfied for the item and store it in the storage unit Is performed may be.

  Further, in the business use case scenario creation support device of the present embodiment, the additional business use case scenario generation unit obtains information on different actions depending on whether or not the content of the execution condition is satisfied from the content of the execution condition. Based on the acquired information of each action, the separate actor generates a business use case scenario for each business that executes the corresponding action, and the generated business use case scenario is indicated by the conditional statement. The business use case scenario of each business that branches off from the business depending on whether or not the content of the condition is satisfied may be stored in the storage unit following the conditional statement.

  Further, in the business use case scenario creation support device of the present embodiment, the additional business use case scenario generation unit displays a business use case scenario generated for the business and a business use case scenario generated for the related business. It is also possible to further execute processing to be displayed on the screen.

  Further, in the business use case scenario creation support device of the present embodiment, the additional business use case scenario generation unit is configured to display a correction target when displaying each business use case scenario generated for the business and the related business on a display device. Display the acceptance column for accepting the selection of the business use case scenario from the user, and for the business use case scenario that received the selection of the modification target in the acceptance column, accept the modification instruction from the user at the input device, and The modification process of the corresponding business use case scenario according to the instruction may be further executed.

  Further, in the business use case scenario creation support apparatus of the present embodiment, the additional business use case scenario generation unit corrects the business use case scenario to be corrected when receiving the selection of the correction target in the reception column. An instruction input field may be displayed on a display device in a pop-up format, and the correction instruction from the user may be received in the input field.

  Further, in the business use case scenario creation support device of the present embodiment, the additional business use case scenario generation unit displays the business use case scenario generated for the business and the related business on a display device. Displays an acceptance column for accepting an instruction for changing the order of arrangement between scenarios from the user, and further executes an order change process for the corresponding business use case scenarios according to the change instruction accepted in the acceptance column. It is good.

  Further, in the business use case scenario creation support apparatus of the present embodiment, the additional business use case scenario generation unit displays each business use case scenario generated for the business and the related business on a display device. Display the relationship between the case scenarios, and obtain an instruction to change the order of arrangement between the business use case scenarios by accepting a drag-and-drop operation to the specified position of the relevant business use case scenario in the display. In accordance with the acquired change instruction, the process of changing the order of arrangement between the corresponding business use case scenarios may be further executed.

  Further, in the business use case scenario creation support device of the present embodiment, the additional business use case scenario generation unit displays the business use case scenario generated for the business and the business use case scenario generated for the related business. Processing for displaying with different display attributes in the apparatus may be further executed.

1 CPU
2 Input device 3 Display device 4 Storage device (storage unit)
10 Use Case Scenario Creation Support Device 11 Business Requirement Scenario Definition Unit 12 Business Use Case Scenario Conversion Unit 13 Additional Business Use Case Scenario Generation Unit 41 Business Function Hierarchy DB
42 Business requirement scenario DB
43 Actor-related information DB
44 Business use case scenario DB
45 Predicate DB
4100 Business function hierarchy table 4200 Business requirement scenario table 4310 Actor related information table 4320 Actor business pattern table 4410 Business use case scenario table 4420 Business use case scenario condition statement table 4430 Business use case scenario order table 4500 Predicate table 10000 Business use case scenario confirmation Screen 11000 Business use case scenario modification screen 12000 Business use case scenario order modification screen

Claims (12)

Input information when executing a job, output information when the job is executed based on the input information, information on actors executing the job, and information on the business requirement scenario describing the contents of the job , A storage unit storing information on correspondence between actors in each business and another actor involved in the actor through a predetermined action in the business,
Read the business requirement scenario and the actor information of the business corresponding to the business requirement scenario from the storage unit, and generate the business use case scenario for the business with the subject as the subject in the single sentence obtained by analyzing the business requirement scenario The business use case scenario conversion unit, which is stored in the storage unit,
For the actor of the generated business use case scenario, the information on the correspondence relationship in the storage unit is read, and another actor involved in the actor is executed in relation to the business use case scenario based on the read information. An additional business use case scenario generation unit that generates a business use case scenario of a related business to be stored and stores it in a storage unit;
A business use case scenario creation support apparatus characterized by comprising: The storage unit further stores information on options related to the predicate among the subject, predicate, and object constituting the business use case scenario,
When the business use case scenario conversion unit analyzes the business requirement scenario and obtains a single sentence, the predicate candidate extracted from the business requirement scenario by analysis is compared with the option in the storage unit, and the predescription word in the option A thing similar to the candidate is identified and set as a predicate of the single sentence.
The business use case scenario creation support apparatus according to claim 1. The storage unit further stores information indicating the presence or absence of an execution condition and information indicating the content of the execution condition for the predetermined action in the correspondence relationship,
The additional business use case scenario generation unit reads the correspondence information in the storage unit and information indicating the presence or absence of the execution condition for the actor of the generated business use case scenario, and there is an execution condition for the predetermined action In this case, the content of the execution condition corresponding to the execution condition is acquired from the storage unit, the condition determination target item indicated by the execution condition content is extracted from the business requirement scenario of the corresponding operation, and the execution condition is To generate a conditional statement that describes whether or not the content of the condition is satisfied and to store it in the storage unit,
The business use case scenario creation support apparatus according to claim 1. The additional business use case scenario generation unit acquires information on different actions depending on whether or not the content of the execution condition is satisfied from the content of the execution condition, and based on the acquired information on each action, A separate actor creates a business use case scenario for each business that executes the corresponding action, and branches the generated business use case scenario from the business depending on whether or not the execution condition indicated by the conditional statement is satisfied As a business use case scenario for each business to be performed, it is stored in the storage unit following the conditional statement.
The business use case scenario creation support apparatus according to claim 3.   The additional business use case scenario generation unit further executes processing for displaying a business use case scenario generated for the business and a business use case scenario generated for the related business on a display device. The business use case scenario creation support apparatus according to claim 1.   The additional business use case scenario generation unit displays a reception field for accepting selection of a business use case scenario to be modified from a user when displaying each business use case scenario generated for the business and the related business on a display device. Then, for a business use case scenario that has been selected for correction in the reception field, the input device receives a correction instruction from the user, and further executes the correction process for the corresponding business use case scenario according to the correction instruction. The business use case scenario creation support apparatus according to claim 5, wherein: The additional business use case scenario generation unit displays a correction instruction input field on a display device in a pop-up format for the business use case scenario to be corrected when receiving the selection of the correction target in the reception field, 7. The business use case scenario creation support device according to claim 5, wherein the modification instruction from the user is received in the input field. Support device.   The additional business use case scenario generation unit includes a reception field for receiving an instruction to change the arrangement order between business use case scenarios from a user when displaying each business use case scenario generated for the business and the related business on a display device. 6. The business use case scenario according to claim 5, further comprising a process of changing the arrangement order between the corresponding business use case scenarios according to the change instruction received and received in the reception field. Creation support device.   The additional business use case scenario generation unit displays each business use case scenario generated for the business and the related business, including a relationship between the business use case scenarios, on the display device. An instruction to change the arrangement order between the business use case scenarios is acquired by accepting a drag-and-drop operation to a predetermined position of the corresponding business use case scenario in the display, and according to the acquired change instruction, 9. The business use case scenario creation support apparatus according to claim 8, wherein the arrangement order change processing is further executed.   The additional business use case scenario generation unit further executes a process of displaying the business use case scenario generated for the business and the business use case scenario generated for the related business with different display attributes on the display device. The business use case scenario creation support apparatus according to claim 5, wherein the business use case scenario creation support apparatus is provided. Input information when executing a job, output information when the job is executed based on the input information, information on actors executing the job, and information on the business requirement scenario describing the contents of the job , A computer having a storage unit storing information on correspondence between actors in each business and other actors involved in the actor through a predetermined action in the business,
Read the business requirement scenario and the actor information of the business corresponding to the business requirement scenario from the storage unit, and generate the business use case scenario for the business with the subject as the subject in the single sentence obtained by analyzing the business requirement scenario Processing to be stored in the storage unit,
For the actor of the generated business use case scenario, the information on the correspondence relationship in the storage unit is read, and another actor involved in the actor is executed in relation to the business use case scenario based on the read information. Processing to generate a business use case scenario for the relevant business and store it in the storage unit;
Use case scenario creation support method characterized by executing Input information when executing a job, output information when the job is executed based on the input information, information on actors executing the job, and information on the business requirement scenario describing the contents of the job , In a computer having a storage unit that stores actors in each business and information on the correspondence between other actors involved in the actor through a predetermined action in the business,
Read the business requirement scenario and the actor information of the business corresponding to the business requirement scenario from the storage unit, and generate the business use case scenario for the business with the subject as the subject in the single sentence obtained by analyzing the business requirement scenario Processing to be stored in the storage unit,
For the actor of the generated business use case scenario, the information on the correspondence relationship in the storage unit is read, and another actor involved in the actor is executed in relation to the business use case scenario based on the read information. Processing to generate a business use case scenario for the relevant business and store it in the storage unit;
Use case scenario creation support program characterized by running