JP2018142054A - Development support system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To support development operation through an interaction by chat.SOLUTION: A development support system 1 includes: an information storage unit for storing a plurality of pieces of first information 220 configured by defining meta information of a plurality of pieces of design information 240, second information 230 configured by defining relations between the plurality of pieces of first information, and third information 320 defining a template of interaction components prepared with respect to operation commonly implemented on the plurality of pieces of design information; an interaction scenario information generation unit 310 for generating an interaction component 330 for operation of each design information and interaction scenario information 340 for operation unit based on each design information on the basis of each first information, second information, and third information; and an interaction scenario information processing unit 311 for operating a chat apparatus 4 on the basis of each interaction component and each interaction scenario information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a development support system and method.

  Chat tools are sometimes used to improve communication efficiency by promoting communication among people involved in system development. In the chat tool, it is possible to share exchanges for each topic using a mechanism called a channel, for example. For this reason, in system development, a chat tool may be used to share progress and issues among a plurality of users.

  On the other hand, Patent Document 1 is known as a technique for creating a dialogue scenario for realizing dialogue control between a person and a system. In Patent Document 1, a dialogue scenario is generated from a document in which functions and operation methods of devices and computer programs are described in a natural language.

JP 2008-145769 A

  In system development, in order to share design information among developers, various design documents are created through development. The design document created in each process becomes an input to other design documents inside and outside the process. The design document is created based on a predetermined writing method. How to write these design documents and the relationship between the design documents are defined in the guides. However, because there are a lot of guides, it takes time for developers to find the necessary guides from many guides, and it takes a lot of time to develop a system with reference to the discovered guides. Requires a lot of effort.

  By the way, in the chat tool, a chat bot that reacts to a user's remark in chat is known. The chat bot automatically responds to the user's remarks or calls a function of another system based on the user remarks. If a chat bot is used, system development by a user can be supported through dialogue.

  In order to develop a desired chatbot, it is necessary to efficiently create a program that realizes interactive control between the user (system developer) and the chatbot. However, as described above, since various design documents and guides exist in each process of system development, it is difficult and time-consuming to develop a chatbot that supports the user's work.

  Note that Patent Document 1 is not a technique using chat, but in Patent Document 1, it is necessary to previously define a rule for extracting items to be a dialogue sentence that constitutes a dialogue scenario from a document. Therefore, the method of Patent Document 1 requires labor for defining rules by analyzing the text of guides related to system development. Furthermore, since the relationship between design information is complicated and may be illustrated instead of text, analysis is difficult with the document item extraction rule.

  The present invention has been made in view of the above problems, and an object thereof is to provide a development support system and method that can support system development work through chat dialogue.

  In order to solve the above-described problem, a development support system according to one aspect of the present invention is a development support system that supports system development work through chat, and includes a plurality of first definitions each defining meta information of a plurality of design information. 1 information, 2nd information which defines the relationship between several 1st information, and 3rd information which defines the model of the dialog component prepared regarding the work implemented in common with several design information An information storage unit for storing third information obtained by associating a template of a command input from the user with a template of a message to be presented to the user, each first information, second information, and third A dialogue scenario information generation unit that generates a dialogue component for each work of each design information based on the information, a dialogue scenario information for each work unit based on each design information, and each dialogue component and each dialogue scenario information. And a dialog scenario information processing unit for operating the cam device Zui.

  ADVANTAGE OF THE INVENTION According to this invention, the dialog component for every work of each design information and the dialog scenario information for every work unit based on each design information are generable. And according to this invention, a user's system development work can be supported by operating a chat apparatus based on each dialog component and each dialog scenario information.

It is explanatory drawing which shows the function structure of a development assistance system. It is explanatory drawing which shows the mode of system development. It is a hardware block diagram of a development support system. It is a software block diagram of a development support system. It is an example of composition of design information meta information. It is an example of composition of information which shows relation between design information meta information. It is a structural example of design information. It is a structural example of the information which shows the relationship between design information. It is an example of composition of a design information dialogue part. It is a structural example of a dialog component. It is an example of a structure of dialog scenario information. It is an example of a structure of channel information. It is an example of composition of user information. It is an example of a screen of a chat channel menu. It is the example of a screen following FIG. The example of the operation screen of design information is shown. The other example of the operation screen of design information is shown. Another example of the design information operation screen is shown. The other example of the operation screen of design information is shown. It is a flowchart of the process which produces | generates dialog scenario information. It is a flowchart of the process which produces | generates a dialog component. It is a flowchart of a dialogue process. It is a flowchart which shows the process of dialog scenario information. It is a flowchart of the process which concerns on 2nd Example and monitors a chat.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In this embodiment, dialogue scenario information is generated using existing design information meta-information, and a user's system development work is supported through dialogue on chat using dialogue scenario information.

  As will be described later, the dialogue scenario information generation unit 310 of the development support system includes design information meta information 220 that defines meta information of various design information included in the design information management unit 210 of the design information repository apparatus 2, and various design information meta. Design information meta information relation 230 that defines a relation between information, and design information in which dialogue contents for work performed in common on all design information 240 in the dialogue scenario information generation unit 310 of the dialogue scenario processing device 3 are converted into parts. From the dialogue component 320, a dialogue component 330 corresponding to the work of various design information is generated. Further, the dialog scenario information generation unit 310 generates dialog scenario information 340 for each work unit of various design information from the dialog component 330, and generates channel information 350 on the chat device 4.

  The dialogue processing unit 411 of the chat device 4 processes the word of the developer (user) input from the client device 5 using the channel information 350. The dialogue processing unit 411 uses the dialogue scenario information 340 and the dialogue component 330 to process the command reception and instruction response for development support in the dialogue scenario information processing unit 311.

  Note that the developer can also access the design information editing unit 211 of the design information repository apparatus 2 in the course of the conversation on the chat. Thereby, the developer can inquire, newly register and edit various design information through chat.

  According to the development support system 1 according to the present embodiment, it is possible to automatically and efficiently generate dialogue scenario information 340 for supporting the work of the developer who creates the design information 240 by chat dialogue. Furthermore, the development support system 1 according to the present embodiment can support the developer's work through a chat dialog based on the dialog scenario information 340.

  Examples will be described with reference to FIGS. First, the functional configuration of the development support system 1 will be described using the description of FIG. Next, an overview of how the development support system 1 supports system development work will be described with reference to the explanatory diagram of FIG. Furthermore, the development support system 1 according to the present embodiment will be described in the order of “apparatus configuration”, “data configuration”, and “processing configuration”.

  The development support system 1 includes, for example, a design information repository device 2, a dialogue scenario processing device 3 (see FIG. 3), a chat device 4, and a client device 5.

  The dialogue scenario processing device 3 includes a dialogue scenario information generation unit 310 that generates dialogue scenario information, and a dialogue scenario information processing unit 311 that processes the dialogue scenario information. The design information repository apparatus 2 stores and manages, for example, design information meta information 220, design information meta information related 230, design information 240, and design information related 250. Each information 220-250 is later mentioned in FIGS. The design information repository device 2 and the storage unit 31 of the dialogue scenario processing device 3 are examples of the “information storage unit”.

  The dialogue scenario information generation unit 310 is an example of design information meta information 220 that is an example of “first information”, design information meta information related 230 that is an example of “second information”, and “third information”. Based on the design information dialogue component 320, the dialogue component 330 and the dialogue scenario information 340 are generated.

  The design information dialogue component 320 may be manually registered in advance by the administrator U1 of the development support system 1 or may be automatically acquired from a server (not shown). The design information dialogue component 320 will be described later with reference to FIG. The interactive component 330 will be described later with reference to FIG. The dialogue scenario information 340 will be described later with reference to FIG.

  The dialogue scenario information generation unit 310 also generates channel information 350. The channel information 350 will be described later with reference to FIG. The client device 5 is connected to the chat device 4, and the user U2 who is a system developer chats with the chat device 4 on the permitted channel. Chat device 4 controls chat based on user information 420 set in advance. The user information 420 will be described later with reference to FIG.

  The chat device 4 includes a dialogue processing unit 411 as described later with reference to FIG. The dialogue scenario information processing unit 311 receives information (character string, command) input from the user U2 via the dialogue processing unit 411, and interacts with the user U2 using the dialogue scenario information 340 and the dialogue component 320.

  For example, when the user U2 inputs a command (S1), the dialogue scenario information processing unit 311 requests the command processing in cooperation with the design information repository apparatus 2 (S2). Upon receiving the processing result from the design information repository device 2 (S3), the dialogue scenario information processing unit 311 returns the processing result together with the instruction response sentence to the client device 5 (S4). Here, the instruction response text is a message including either a message instructing the user U2 or a message in response to a request from the user U2.

  FIG. 2 is an explanatory diagram showing a state in which system development is supported using chat. The administrator U1 of the development support system 1 generates a bot for supporting system development work in advance. The created chat bot interacts with the user U2 based on the interaction component 330 and the interaction scenario information 340. Thereby, the user U2 can process each process such as “requirement definition”, “design”, “detailed design / implementation”, “test”, “release / operation” with the support of the bot. For example, each user U2 engaged in system development can exchange information with other users through chat and receive instructions from the bot on what to do next. Furthermore, each user U2 can access and edit design information through the bot.

  --Device configuration--

  FIG. 3 is a hardware configuration diagram of the development support system 1. As described above, the development support system 1 is a computer system including the design information repository device 2, the dialogue scenario processing device 3, the chat device 4, and the client device 5. The development support system 1 can be composed of a single computer, or can be composed of a plurality of computers as shown in FIG. The devices 2 to 5 may be configured as separate computers, and may be interconnected via the communication network CN, or the functions of the devices 2 to 5 may be implemented on a single computer.

  The design information repository apparatus 2 includes, for example, a calculation unit 20, a storage unit 21, a communication unit 22, and a user interface unit (UI unit in the figure) 23.

  The calculation unit 20 reads and executes a predetermined computer program stored in the storage unit 21, thereby realizing functions such as the design information management unit 210 and the design information editing unit 211 shown in FIG. The storage unit 21 can be configured by a storage device such as a read only memory (ROM), a random access memory (RAM), a solid state drive (SSD), and a hard disk drive (HDD).

  The communication unit 22 is a device connected to the communication network CN. The design information repository apparatus 2 can perform bidirectional communication with other apparatuses from the communication unit 22 via the communication network CN. The user interface unit 23 is a device for exchanging information with an operator such as the developer U1, and includes an information input device and an information output device (both not shown). The information input device is, for example, a keyboard, a touch panel, a pointing device, a switch, a voice recognition device, a motion recognition device, or the like. The information output device is, for example, a display, a printer, a voice synthesizer, or the like.

  Similarly, the dialogue scenario processing apparatus 3 includes a calculation unit 30, a storage unit 31, a communication unit 32, and a user interface unit 33. Similarly, the chat device 4 includes a calculation unit 40, a storage unit 41, a communication unit 42, and a user interface unit 43. The client device 5 also includes a calculation unit 50, a storage unit 51, a communication unit 52, and a user interface unit 53. Since the roles of the calculation unit, the storage unit, the communication unit, and the user interface unit are the same as those described in the design information repository apparatus 2, further description is omitted.

  FIG. 4 is a software configuration diagram of the development support system 1. In the figure, basic configurations such as an operating system, a library, and a driver are omitted.

  The design information repository apparatus 2 includes a computer program for realizing the design information management unit 210 and the design information editing unit 211. The design information management unit 210 is a function for managing each data of the design information meta information 220, the design information meta information related 230, the design information 240, and the design information related 250. These pieces of information 220 to 250 are stored in the storage unit 21 of the design information repository apparatus 2 and are read and written by the design information management unit 210.

  The design information editing unit 211 is a function for inquiring, registering, editing, and updating each data 220 to 250 managed by the design information management unit 210. The design information editing unit 211 is an example of a “design information update unit”.

  The dialogue scenario processing apparatus 3 includes a computer program for realizing the dialogue scenario information generation unit 310 and the dialogue scenario information processing unit 311. The dialog scenario information generation unit 310 is a function that generates a dialog part 330, dialog scenario information 340, and channel information 350 from the design information meta information 220, the design information meta information relation 230, and the design information dialog part 320.

  The dialogue scenario information processing unit 311 displays an instruction response sentence 335 of the dialogue component 330 based on the dialogue scenario information 340 in response to an acceptance command 334 (see FIG. 10) specified by the dialogue component 330 input by the user. Or a script 336 is executed.

  The chat device 4 includes a computer program for realizing the channel information management unit 410 and the dialogue processing unit 411. The channel information management unit 410 has a function of managing channel information 350 that is a unit of chat and user information 420 that is a candidate for participation in each channel.

  The dialogue processing unit 411 is a function that displays a channel selected by the user based on the channel information 350 and the user information 420, and receives an input from the user to process the chat. The dialogue processing unit 411 may be provided with a chat monitoring unit 412 that appears in an embodiment described later.

  The client device 5 has a browser 510. The user U <b> 2 can use the chat service provided by the chat device 4 using the browser 510.

  --Data structure--

  An example of data used in the development support system 1 will be described with reference to FIGS.

  FIG. 5 is an example of the design information meta information 220. The design information meta information 220 is meta information of the design information 240. The design information meta information 220 includes, for example, an ID 221, a process 222, a type 223, an inquiry URL (Uniform Resource Locator) 224, a new registration URL 225, an edit URL 226, and a description 227.

  The ID 221 is information for uniquely identifying the design information meta information. Step 222 is information for distinguishing the step of creating the design information 240. Step 222 includes, for example, a step of creating internal design information and a step of creating detailed design information. The type 223 is a type of the design information 240. Types 223 include, for example, component design, class design, and method design. The inquiry URL 224 is an address for calling a function (design information inquiry) of the design information editing unit 211. The new registration URL 225 is an address for calling a function (design information registration) of the design information editing unit 211. The edit URL 226 is an address for calling a function of the design information editing unit 211 (design information editing). The description 227 is an explanatory text including a hyperlink to a guide or the like for defining design information.

  FIG. 6 is an example of the design information meta-information relation 230. The design information meta information relation 230 is data defining a relation between a plurality of design information meta information 220. The design information meta information association 230 includes, for example, an ID 231, an association source ID 232, an association destination ID 233, and an association type 234.

  The ID 231 is information for uniquely identifying the design information meta information relation. The association source ID 232 is information indicating the design information meta information 220 of the association source. The relation destination ID 233 is information indicating the design information meta information 220 of the relation destination. The association type 234 is information indicating a type of association between the design information meta information 220 of the association source and the design information meta information 220 of the association destination. Examples of association types include reference and aggregation.

  FIG. 7 is an example of the design information 240. The design information 240 includes, for example, an ID 241, a meta information ID 242, a design information name 243, a review state 244, and contents 245.

  The ID 241 is information for uniquely identifying design information. The meta information ID 242 is an ID of the design information meta information 220 indicating the type of the design information 240. In the meta information ID 242, any value of the ID 221 shown in FIG. 5 is set. The design information name 243 indicates the name of the design information 240. The review state 244 indicates the review state of the design information 240. The content 245 is entity data of the design information 240.

  FIG. 8 is an example of design information related 250. The design information association 250 is data that defines a relationship between a plurality of design information 240. The design information related 250 includes, for example, an ID 251, a related source ID 252, and a related destination ID 253.

  The ID 251 is information for uniquely identifying the design information relation. The association source ID 252 is information indicating the design information 240 of the association source. The relation destination ID 253 is information indicating the design information 240 of the relation destination.

  FIG. 9 shows an example of a design information dialogue component 320 which is a model of the dialogue component 330. The design information dialogue component 320 includes, for example, an ID 321, a type 322, a condition 323, an acceptance command template 324, an instruction response sentence template 325, and a next ID 326.

  The ID 321 is information for uniquely identifying the design information dialogue component. The type 322 is information that defines the type of design information dialogue component. Types include “create” and “edit”. The condition 323 indicates a condition for executing the interactive component. In the condition 323, the value of the design information dialogue component ID 321 can be entered. The accepted command template 324 is information defining a template of a command accepted from the user. The instruction response sentence model 325 is information that defines a model of an instruction response sentence presented to the user after receiving a command. The next ID 326 is information indicating the next design information dialogue part.

  FIG. 10 shows an example of the interactive component 330. The interactive component 330 includes, for example, an ID 331, a type 332, a condition 333, an acceptance command 334, an instruction response sentence 335, a script 336, and a next ID 337.

  The ID 331 is information that uniquely identifies the interactive component. The type 332 indicates the type of interactive component. Types include, for example, “create detailed design information” and “common”. The condition 333 indicates a condition for executing the interactive component. The acceptance command 334 is information defining a command accepted from the user. The instruction response text 335 is information that defines an instruction response text to be presented to the user after receiving the command. The script 336 is information that defines a script (program) to be executed when a command is received. The next ID 337 is information indicating the next dialog part.

  FIG. 11 shows an example of the dialogue scenario information 340. The dialogue scenario information 340 includes, for example, an ID 341, a design work name 342, and an applied dialogue component ID 343.

  The ID 341 is information for uniquely identifying the dialogue scenario information. The design work name 342 indicates the name of the design work. The applied dialogue component ID 343 indicates the dialogue component 330 applied to the work specified by the design work name 342.

  FIG. 12 shows an example of channel information 350. The channel information 350 defines a chat channel. The channel information 350 includes, for example, an ID 351, a channel name 352, a dialogue scenario information ID 353, and a participating user ID 354.

  The ID 351 is information for uniquely identifying a channel. The channel name 352 defines the name of the channel. Dialog scenario information ID353 shows the dialog scenario information applied in a channel. The participating user ID 354 is information that identifies a user who participates in the channel.

  FIG. 13 is an example of user information 420 for managing information about the user U2 who is a developer. The user information 420 includes, for example, an ID 421, a user name 422, an authority 423, and an e-mail address 424.

  The ID 421 is information that uniquely identifies the user. The user name 422 defines the name of the user. The authority 423 defines the authority that the user has. The e-mail address 424 is an e-mail address that the user has. Instead of the e-mail address or together with the e-mail address, information about other contact means such as a telephone number may be registered.

  --System operation--

  The operation of the system 1 will be described with reference to FIGS. 14 and 15 are examples of chat screens. 16 to 19 are examples of screens for editing design information. FIG. 20 is a flowchart of processing for generating dialogue scenario information. FIG. 21 is a flowchart of processing for generating a dialogue component.

  With reference to FIG. 20, the process (S10) which produces | generates dialog scenario information is demonstrated. The dialogue scenario information generation unit 310 reads the design information meta information 220 from the design information repository apparatus 2 (S11). Specifically, the dialogue scenario information generating unit 310 is connected to the communication unit 22 of the design information repository device 2 from the communication unit 32 of the dialogue scenario processing device 3 via the communication network CN. The design information management unit 210 of the design information repository apparatus 2 reads the design information meta information 220 from the storage unit 21 and transmits it to the dialogue scenario information generation unit 310.

  Similar to step S11, the dialogue scenario information generation unit 310 reads the design information meta-information relation 230 from the storage unit 21 by the process of the design information management unit 210 (S12).

  Further, the dialogue scenario information generation unit 310 reads the design information dialogue component 320 from the storage unit 31 of the dialogue scenario processing device 3 (S13).

  The dialogue scenario information generation unit 310 generates the dialogue component 330 based on the information 220, 230, 320 acquired in steps S11 to S13, and stores the generated dialogue component 330 in the storage unit 31 (S14). Details of the process (S14) for generating the interactive component 330 will be described later with reference to FIG.

  The dialogue scenario information generation unit 310 extracts a record for each dialogue component type 332 of the dialogue component 330 generated in step S14 and a record that is “common”, generates dialogue scenario information 340 from these records, and stores the storage unit 31. (S15).

  The dialogue scenario information generation unit 310 extracts, for example, a record of the dialogue component 330 whose dialogue component type 332 is “create detailed design information” and a record of the “common” dialogue component 330, and the dialogue of the ID 331 of the dialogue scenario information 340. The scenario information ID 341 is numbered. The dialogue scenario information generation unit 310 copies the design work name 342 from the dialogue component type 332. The dialogue scenario information generation unit 310 copies the dialogue component ID 331 of the dialogue component 330 having the dialogue component type 332 of “detailed design information creation” and “common” as the application dialogue component ID 343 to the application dialogue component ID 343 to obtain the dialogue scenario information. 340 is generated. The dialogue scenario information generation unit 310 stores the generated dialogue scenario information 340 in the storage unit 31.

  The dialogue scenario information generation unit 310 generates channel information 350 from the dialogue scenario information 340 generated in step S15, and sends the generated channel information 350 to the chat device 4 via the communication unit 32, the communication network CN, and the communication unit 42. The data is transferred and stored in the storage unit 41 (S16).

  For example, the channel ID 351 of the channel information 350 is newly assigned. Then, the design work name 342 of the dialogue scenario information 340 is copied to the channel name 352, the dialogue scenario information ID 341 of the dialogue scenario information 340 is copied to the dialogue scenario information ID 353, and “*” is defined as the participating user ID 354. Here, “*” means all users.

  FIG. 21 is a flowchart of the interactive component generation process shown as step S14 in FIG.

  The dialogue scenario information generation unit 310 extracts an unprocessed record group from records having the same “process” value from the design information meta information 220 read in step S11 of FIG. 20 (S21). The dialogue scenario information generation unit 310 repeats the process with step S28 until there is no unprocessed record group extracted at step S21. In the example of FIG. 5, records having design information meta information IDs “0020” and “0021” having “details” as step 222 are extracted from the design information meta information 220.

  The dialogue scenario information generation unit 310 uses the design information meta information association 230 to identify the relationship of the design information meta information in the process whose association type is “aggregation” (S22). Specifically, the dialogue scenario information generation unit 310 extracts the design information meta-information relation 230 related to the record group extracted in step S21, and extracts those whose association type 234 is “aggregation” from the extracted. Then, the dialogue scenario information generation unit 310 identifies the association source and the association destination related to aggregation, and specifies the route design information meta information 220 that does not include the association source.

  For example, the record of the design information meta information related 230 including the design information meta information ID 221 “0020” or “0021” in either the related source design information meta information ID 232 or the related destination design information meta information ID 233 is the design information meta information. Assume that the related IDs 231 are “0051” and “0052”.

  Among them, a record whose relation type 234 is “aggregation” is a record whose design information meta-information relation ID 231 is “0052”. Therefore, the record whose design information meta information ID 221 of the design information meta information 220 is “0020” is a root. As a related destination, a record whose design information meta information ID 221 of the design information meta information 220 is “0021” (hereinafter referred to as child design information meta information with respect to the root) is identified.

  The dialogue scenario information generation unit 310 extracts unprocessed design information meta information 220 from the record group of the design information meta information 220 extracted in step S21 (S23). The dialogue scenario information generation unit 310 repeats step S23 until there is no unprocessed record (S27). For example, it is assumed that the design information meta information 220 having the root design information meta information ID 221 of “0020” and the type 223 of “class design information” is extracted.

  The dialogue scenario information generation unit 310 extracts one unprocessed record from the design information dialogue component 320 read in step S13 (S24). The dialogue scenario information generation unit 310 repeats step S24 until there are no unprocessed records (S26).

  The dialogue scenario information generation unit 310 generates a dialogue component 330 based on the design information meta information 220 extracted in step S23 and the design information dialogue component 320 extracted in step S24, and stores it in the storage unit 31 (S25). .

  For example, for the “class design information” that is the route extracted in step S23, the design information dialogue component ID 322 is “6000” as the record in which the design information dialogue component type 322 of the design information dialogue component 320 is “design information creation”. A process for generating an interactive component when “6001”, “6002”, and “6500” exist will be described.

  When the design information dialogue component ID is a record of “6000” (see FIG. 9), the dialogue scenario information generation unit 310 assigns the dialogue component ID 331 of the dialogue component 330 as “8020” (see FIG. 10). A character string “create detailed design information” is created by combining the process “detail” of “class design information” and the design information dialogue component type “design information creation” with the design information dialogue component ID “6000”.

  The dialogue scenario information generation unit 310 creates a dialogue component type 332 of the dialogue component 330 and sets “$ {design information type}” of the received command template 304 “start ($ {design information type})” as design information meta information 220. By replacing with the type 223, “start (class design information)” is created as the acceptance command 334.

  The dialogue scenario information generation unit 310 copies the dialogue execution condition 323 “begin” to the dialogue execution condition 333.

  The dialogue scenario information generation unit 310 generates “$ {related destination design information}” by using the instruction response sentence template 325 “[based on“ $ {related source design information} ”] ($ {design information inquiry URL}). “$ {}” Of “please create” based on the design information source design information meta ID 232, the design information inquiry URL 224, and the related destination design information 253, respectively. ] (Http: // ...) to create "class design information". Is generated as an instruction response sentence 335.

  Note that the dialogue execution condition 323 “begin” is copied to the dialogue execution condition 333 only in the case of a route.

  If the design information dialogue component ID is “6001” in the record, the dialogue scenario information generation unit 310 numbers the dialogue component ID 331 of the dialogue component 330 as “8030”.

  The dialogue scenario information generation unit 310 combines the process “detail” of “class design information” and the design information dialogue component type “design information creation” with the design information dialogue component ID “6001” to create “detailed design information creation”. And the character string is set as the dialogue component type 332 of the dialogue component 330.

  The dialogue scenario information generation unit 310 replaces “$ {design information type}” of the acceptance command template 304 “finish ($ {design information type})” with the type 223, thereby replacing “finish (class design information)”. Created as an acceptance command 334.

  The dialogue scenario information generation unit 310 performs the instruction response sentence template 325 “register [created“ $ {design information type} ”” ($ {design information new registration URL}). "$ {}" Portion of "" based on the type 223 and the design information new registration URL 225, the instruction response sentence 335 "created [register" class design information "" (http: // ...) Please give me. Is generated.

  The dialogue scenario information generation unit 310 assigns the next execution dialogue component ID “8040” by assigning the dialogue component ID to the next design information dialogue component ID “6002”.

  If the design information dialogue component ID is “6002” in the record, the dialogue scenario information generation unit 310 numbers the dialogue component ID 331 of the dialogue component 330 as “8040”.

  The dialogue scenario information generation unit 310 combines the process “detail” of “class design information” and the design information dialogue component type 322 “design information creation” with the design information dialogue component ID “6002” to create “detailed design information creation”. And the character string is set as the dialogue component type 332 of the dialogue component 330.

  The dialogue scenario information generation unit 310 creates the instruction response sentence template 325 “$ (# 1) {“ $ {design information type} ””}. "$ (# 1) {}" uses not only the other design information of its own but also the creation of design information of the design information type when there are children, using the character string enclosed in {}. Create a separate "class design information" or child "method design information" as a special prompting response. The instruction response sentence 335 is generated.

  When the design information dialogue component ID is “6500”, the dialogue scenario information generation unit 310 numbers the dialogue component ID 331 of the dialogue component 330 as “8080”.

  The dialogue scenario information generation unit 310 combines the process “detail” of “class design information” and the design information dialogue component type 322 “design information creation” with the design information dialogue component ID “6002” to create “detailed design information creation”. And the character string is set as the interactive part type 332 of the interactive part 330.

  The dialogue scenario information generation unit 310 replaces “$ {design information type}” of the acceptance command template 304 “doc ($ {design information type})” with the type 223, thereby replacing “doc (class design information)”. Created as an acceptance command 334.

  The dialogue scenario information generation unit 310 replaces the “$ {}” part of the instruction response sentence template 325 “$ {description}” with the explanation 227, thereby design information for defining the instruction response sentence 335 “class specification in detail”. Please refer to [Class Design Guide] (http: // ...) for detailed definition method. Is generated.

  The dialogue scenario information generation unit 310 numbers “8100” as the dialogue component ID 331 of the dialogue component 330 because “design information editing” is included in the design dialogue information type 322 of the design information dialogue component 320.

  The dialogue scenario information generation unit 310 combines the process “detail” of “class design information” with the design information dialogue component type 322 “design information edit” whose design information dialogue component ID is “6002”, And the character string is set as the interactive part type 332 of the interactive part 330.

  The dialogue scenario information generation unit 310 replaces “$ {design information type}” of the acceptance command template 304 “doc ($ {design information type})” with the type 223, thereby replacing “doc (class design information)”. Created as an acceptance command 334.

  The dialogue scenario information generation unit 310 replaces the “$ {}” part of the instruction response sentence template 325 “$ {description}” with the explanation 227, thereby design information for defining the instruction response sentence 335 “class specification in detail”. Please refer to [Class Design Guide] (http: // ...) for detailed definition method. Is generated.

  Similarly, the dialog component 330 is generated for the child “method design information” extracted in step S23.

  As described above, the dialogue scenario information generation unit 310 can generate the dialogue component 330, the dialogue scenario information 340, and the channel information 350 from the design information meta information 220, the design information meta information relation 230, and the design information dialogue component 320.

  FIG. 22 is a flowchart showing the conversation process in the chat. By connecting to the chat device 4 using the browser 510 of the client device 5, the user can proceed with system development work while receiving work support by chat. The client device 5 can be connected to the chat device 4 via the communication unit 52, the communication network CN, and the communication unit 42. The dialogue processing unit 411 of the chat device 4 automatically responds to the character string input from the browser 510.

  The dialogue processing unit 411 of the chat device 4 reads the channel information 350 from the storage unit 41 and displays the “chat / channel menu” on the browser 510 of the client device 5 (S30).

  FIG. 14 shows an example of the chat / channel menu screen G1. The chat / channel menu screen G1 presents menus such as “create internal design information”, “edit internal design information”, “create detailed design information”, and “edit detailed design information” to the user, for example. The user can create or edit desired design information by selecting a desired menu from the screen G1.

  Returning to FIG. The chat device 4 reads the channel information 350 corresponding to the channel selected by the user through the browser 510 from the storage unit 41, and displays the chat screen on the browser 510 based on the channel information 350 (S31). That is, the chat device 4 transmits the chat screen generated based on the channel information 350 to the browser 510 of the client device 5 via the communication network CN or the like.

  At the same time that the channel is opened, the dialogue processing unit 411 of the chat device 4 calls the dialogue scenario information 340 of the dialogue scenario processing device 3 to identify a record having the same design work name 342 as the opened channel information name. Read from the storage unit 31. Furthermore, the dialogue processing unit 411 reads the record of the dialogue component 330 having the dialogue component ID 331 specified by the applied dialogue component ID 343 of the read record, and the record in which the dialogue execution condition 333 is “begin” in the read record. Is identified. The dialogue processing unit 411 displays the instruction response text 335 of the identified record as the first information from the chat device 4 on the browser 510 of each user participating in the channel.

  Refer to FIG. FIG. 15 shows a display example of a channel when the user selects a menu called detailed design information creation GP110 from the chat / channel menu G1.

  “Bot” on the channel indicates a chat bot that the chat device 4 automatically generates in response to a user input. The chat bot is realized when the dialogue scenario information processing unit 311 responds based on the dialogue scenario information 340 and the dialogue component 330 according to the processing result of the dialogue processing unit 411.

  “Hoge” and “Leader” on the channel indicate users registered in the user information 420. The user displayed as “Leader” is an example of “predetermined upper user” or “predetermined notification destination” or “upper user”. Each user can input a command or a message via the browser 510 of the client device 5 to be used.

  Returning to FIG. The dialogue processing unit 411 of the chat device 4 monitors whether the user has input information via the browser 510 (S32). Information input to the browser 510 by the user is transmitted to the chat device 4 via the communication network CN or the like.

  When the dialogue processing unit 411 detects an input from the user (S32: YES), the dialogue processing unit 411 determines whether a command is included in the information input by the user (S33). If the dialogue processing unit 411 determines that the command is not included (S33: NO), the dialogue processing unit 411 displays the information input by the user in the channel in step S32. Thereby, information (message) input by a certain user is displayed on the browser 510 used by each user participating in the channel. Thereafter, the processing of the dialogue processing unit 411 returns to step S32 and waits until information is input from any of the users participating in the channel.

  If it is determined in step S32 that the command is included in the information received from the user (S33: YES), the chat device 4 determines whether the command is an end command (S35).

  If the command received from the user is an end command (S35: YES), the chat device 4 closes the channel and ends the process (S36). When it is determined that a command other than the end command is included in the information input by the user (S35: NO), the chat device 4 calls the dialogue scenario information processing unit 311 and the dialogue scenario information processing described later with reference to FIG. (S37) is executed. The chat device 4 displays the instruction response text, error message, etc. returned from the dialogue scenario information processing unit 311 on the browser 510 of each user participating in the channel, and then returns to step S32.

  FIG. 23 shows the processing content (S37) of the dialogue scenario information processing unit 311 that is called and executed from the dialogue processing unit 411 of the chat device 4.

  The dialogue scenario information processing unit 311 determines whether the command in the information input from the user in step S32 of FIG. 22 can be accepted (S41). That is, the dialogue scenario information processing unit 311 determines whether or not there is a record in the dialogue component 330 illustrated in FIG. 10 in which the same command as the command input by the user is registered in the received command 334.

  When there is a record corresponding to the command input by the user (S41: YES), the dialogue scenario information processing unit 311 acquires the record from the dialogue component 330 and proceeds to step S43.

  When the record corresponding to the command input by the user is not found in the dialog component 330 (S41: NO), the dialog scenario information processing unit 311 determines that the command input by the user cannot be accepted and performs error processing (S42).

  In the error processing, for example, an error message indicating that the input command cannot be processed is returned to the caller interaction processing unit 411. Even when the record corresponding to the command input by the user can be acquired from the dialog component 330, if the dialog component specified by the dialog execution condition 333 is not executed in advance, the command input by the user is accepted. It is determined that it cannot be performed, and error processing is performed (S42).

  If the dialogue scenario information processing unit 311 determines that the command input by the user is acceptable (S41: YES), the dialogue scenario information processing unit 311 reads the instruction response sentence from the instruction response sentence 335 in the record corresponding to the command, and It returns to the dialogue processing unit 411.

  The dialogue scenario information processing unit 311 executes the script defined in the script 336 of the record corresponding to the command input by the user (S44). A script is an arbitrary computer program that can be executed by the arithmetic unit 30 of the dialogue scenario processing apparatus 3.

  The dialogue scenario information processing unit 311 determines whether a dialogue component to be executed next is registered in the next ID 337 of the record corresponding to the command input by the user (S45). Steps S43 and S44 are executed for the interactive component. When the interactive component to be executed next is not registered (S45: NO), this process is terminated, and the process returns to step S37 of FIG.

  A specific example of the processing of FIGS. 22 and 23 will be described with reference to FIG. First, in step S31, the frame of the screen G2 and the wording GP 210 are displayed on the browser 510. The underlined part of the wording GP 210 represents a hyperlink to the URL specified by “()” of “[] ()” in the instruction response sentence 335. When the user selects a hyperlink displayed as an underline character string of the wording GP 210, the function (design information inquiry) of the design information management unit 210 is called and the screen G 3 of FIG. 16 is displayed on the browser 510.

  The wording GP211 is a wording input by the user “Hoge”, the command “/ finish (class design information)” is processed in step S37 (steps S41 to S45), and the wording GP212 and GP213 are displayed on the browser 510.

  When a hyperlink displayed as an underline character string of the wording GP 212 is selected, the function (design information registration) of the design information management unit 210 is called, and the screen 4 in FIG. .

  The wording GP 214 is a word inputted by the user “Hoge”, the command “/ doc (method design information)” is processed in step S 37, and the wording GP 215 is displayed on the browser 510. When a hyperlink displayed with an underline character string of the wording GP 215 is selected, a document (design guide) designated by the URL of the hyperlink is displayed on the browser 510.

  The wording GP 216 is the wording input by the user “Hoge”, the command “/ start (method design information)” is processed in step S 37, and the wording GP 217 is displayed on the browser 510. When the hyperlink of the wording GP 217 is selected, the design information management unit 210 is called and the screen G 5 of FIG.

  The wording GP 218 is the wording input by the user “Hoge”, the command “/ finish (method design information)” is processed in step S 37, and the wording GP 219 and GP 220 are displayed on the browser 510. When a hyperlink displayed as an underline character string of the wording GP 219 is selected, the function (design information registration) of the design information management unit 210 is called, and the screen G 6 in FIG. 19 is displayed on the browser 510. .

  The wording GP 221 is a word inputted by the user “Leader”, and is displayed on the browser 510 in step S34.

  The wording GP 222 is a word inputted by the user “Hoge” and is displayed on the browser 510 in step S34.

  The wording GP 223 is a word inputted by the user “Hoge”, and the command “/ review (# 200, # 300)” is executed in step S44. As a result, the process of the design information management unit 210 is executed, and the review state 244 of the design information ID 241 designated by # is set to “True”.

  The wording GP 224 is a word inputted by the user “Hoge”, the command “/ end” is determined in step S35, and the channel is closed in step S36.

  According to the development support system 1 of the present embodiment, by using the channel information 350, the dialogue scenario information 340, and the dialogue component 330, development is automatically supported in response to the words input by the user (developer). Function (chat bot) can be realized efficiently. This function can be realized by the channel information management unit 410, the dialogue processing unit 411, and the dialogue scenario information processing unit 311.

  The development support system 1 according to the present embodiment can receive and process a command input by the user through chat, and can return an appropriate instruction response to the client device 5 used by the user. Therefore, the user can proceed with development work while receiving appropriate advice, and usability is improved.

  In the development support system 1 of the present embodiment, the design information editing unit 211 of the design information repository apparatus 2 can be accessed in the course of dialogue, so that various design information 240 and design information related 250 can be updated in a chat. Can display and create and edit. In the development support system 1 according to the present embodiment, the user can advance the development work in the chat while receiving the advice (instruction response) for supporting the development work in the chat, and the usability is improved.

  A second embodiment will be described with reference to FIG. Since this embodiment corresponds to a modification of the first embodiment, the difference from the first embodiment will be mainly described. In this embodiment, the content of chat is monitored, and notification can be made to the superior according to the content.

  FIG. 24 shows processing executed by the chat monitoring unit 412 of the dialogue processing unit 411 of the chat device 4. The chat monitoring unit 412 monitors each channel and acquires information input to each channel (S51).

  The chat monitoring unit 412 analyzes the acquired input information (S52), and determines whether to notify a superior (such as an administrator) from the analysis result (S53). For example, when a predetermined keyword is included in the input information or when a predetermined command is included in the input information, it is set in advance to notify the superior.

  When chat monitoring unit 412 determines that there is no need to notify the superior (S53: NO), it returns to step S51. On the other hand, if it is determined that it is necessary to notify the superior (S53: YES), the chat monitoring unit 412 creates an outline of the chat content and notifies the superior (S54). For example, a predetermined range of chat contents including a predetermined keyword or a predetermined command is extracted and transmitted to a superior as a chat outline.

  Furthermore, the chat monitoring unit 412 can send an e-mail to a superior to notify the user to confirm the chat (S55).

  Configuring this embodiment like this also achieves the same operational effects as the first embodiment. Furthermore, according to the present embodiment, according to the contents of the user's chat, it is possible to send an outline of the chat to the user's superior, and to call attention to confirm the chat. Therefore, the superior can efficiently monitor the user's development work and give necessary advice. The superior can efficiently manage a plurality of users.

  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.

  In the above, the processing example of the dialog scenario information generation unit and the dialog scenario information processing unit in the dialog scenario processing device has been described. However, the processing may be generated as a program running on the chatbot framework as means for realizing these processes.

  Moreover, although the chat using a character was taken as an example in the above, it may be realized by a chat tool using voice. Further, instead of the chat tool, an e-mail tool may be used as an alternative means.

  In addition, this invention is not limited to said each Example, Various modifications are included. For example, the above embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. In addition, each of the above-described configurations, functions, processing units, processing units, and the like may be realized in a cloud system by designing a part or all of them with, for example, a virtual machine.

  In addition, each of the above-described configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files for realizing each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

  Further, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

  Moreover, each component of the present invention can be arbitrarily selected, and an invention having a selected configuration is also included in the present invention. Further, the configurations described in the claims can be combined with combinations other than those specified in the claims.

  1: Development support system, 2: Design information repository device, 3: Dialogue scenario processing device, 4: Chat device, 5: Client device, 210: Design information management unit, 211: Design information editing unit, 220: Design information meta information 230: Design information meta information related, 240: Design information, 250: Design information related, 310: Dialogue scenario information generation unit, 311: Dialogue scenario information processing unit, 320: Design information dialogue part, 330: Dialogue part, 340: Dialog scenario information, 350: Channel information, 410: Channel information management unit, 411: Dialog processing unit, 412: Chat monitoring unit, 510: Browser

Claims (11)

A development support system that supports system development work through chat,
It is implemented in common to a plurality of first information that respectively defines meta information of a plurality of design information, a second information that defines a relationship between the plurality of first information, and the plurality of design information. Third information that defines a template of an interactive component prepared for the work to be performed, and that associates a template of a command input from the user with a template of a message to be presented to the user. An information storage unit for storing;
Dialogue for generating dialogue parts for each work of the design information and dialogue scenario information for each work unit based on the design information based on the first information, the second information, and the third information. A scenario information generator,
A dialogue scenario information processing unit for operating the chat device based on each dialogue component and each dialogue scenario information;
Development support system with The dialog scenario information generation unit generates the dialog component and the dialog scenario information for supporting the system development work.
The development support system according to claim 1. The chat device includes a dialogue processing unit that analyzes information input from a user and performs dialogue with the user,
The dialogue scenario information processing unit supports the system development work by operating the dialogue processing unit based on information input from the dialogue processing unit by the user, the dialogue parts, and the dialogue scenario information. ,
The development support system according to claim 2. A design information update unit that updates predetermined design information of the plurality of design information based on information input from the dialog processing unit by the user;
The development support system according to claim 3. The interactive component displayed on the chat device may include predetermined link information related to predetermined design information among the plurality of design information.
The development support system according to claim 3. When the user selects the predetermined link information, a predetermined screen associated with the predetermined link information is displayed on the chat device.
The development support system according to claim 5. The chat device can generate a plurality of channels,
Each channel is associated with a channel name based on the name of the design work, an identifier for specifying the interaction scenario information to be used, and an identifier for specifying the user who participates.
The development support system according to claim 3. The dialogue processing unit includes a chat monitoring unit,
The chat monitoring unit notifies a predetermined upper user based on an analysis result of information input from the user.
The development support system according to claim 3. The dialogue processing unit includes a chat monitoring unit,
The chat monitoring unit generates a summary of the conversation content with the user and notifies a predetermined notification destination.
The development support system according to claim 3. The predetermined notification destination is a high-order user positioned above the user.
The development support system according to claim 9. A development support method in which a computer supports system development work through chat,
It is implemented in common to a plurality of first information that respectively defines meta information of a plurality of design information, a second information that defines a relationship between the plurality of first information, and the plurality of design information. Third information that defines a template of an interactive component prepared for the work to be performed, and that associates a template of a command input from the user with a template of a message to be presented to the user. Hold and
Based on the first information, the second information, and the third information, generate interactive parts for each work of the design information, and interactive scenario information for each work unit based on the design information,
The chat device is operated based on each dialogue part and each dialogue scenario information.
Development support method.

Images