JP6676564B2 - Development support system and method - Google Patents

Description

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

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

  On the other hand, Patent Literature 1 is known as a technique for creating a dialog scenario that realizes a dialog control between a person and a system. In Patent Literature 1, a dialog scenario is generated from a document in which functions and operation methods of a device and a computer program are described in a natural language.

JP 2008-145770 A

  In system development, various design documents are created through development in order to share design information among developers. The design document created in each process is an input to other design documents inside and outside the process. The design document is created based on a fixed writing style. Guides define how to write these design documents and the relationships between the design documents. However, due to the large number of guides, developers have trouble finding the necessary guides from many guides, and it takes a lot of time to develop a system while referring to the guides they have found. Needs great effort.

  By the way, as a chat tool, a chatbot that responds to a user's remark in a chat is known. The chatbot automatically replies to a user's utterance or calls a function of another system based on the user's utterance. By using a chatbot, it is possible to support system development by a user through dialogue.

  In order to develop a desired chatbot, it is necessary to efficiently create a program that realizes interactive control between a 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 a user's work.

  It should be noted that Patent Literature 1 is not a technique using chat, but in Patent Literature 1, it is necessary to define in advance rules for extracting items as dialogue sentences constituting a dialogue scenario from a document. Therefore, in the method of Patent Document 1, it takes effort to analyze the text of guides related to system development and define rules. Further, since the relationship between design information is complicated and may be illustrated instead of a sentence, it is difficult to analyze with the item extraction rule of the document.

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

  In order to solve the above problems, a development support system according to one aspect of the present invention is a development support system that supports a system development work through a chat, and includes a plurality of first and second meta information of a plurality of design information. One piece of information, second information that defines a relationship between a plurality of pieces of first information, and third information that defines a model of a dialog component prepared for work performed in common with a plurality of pieces of design information. An information storage unit for storing third information in which a template of a command input from the user and a template of a message to be presented to the user are associated; a first information, a second information, and a third information; A dialog component for each operation of each design information, a dialog scenario information generating unit that generates dialog scenario information for each work unit based on each design information, and a dialog component for each dialog component and each dialog scenario information based on the information. And a dialog scenario information processing unit for operating the cam device Zui.

  According to the present invention, it is possible to generate a dialog component for each task of each design information and dialog scenario information for each task based on each design information. According to the present invention, the system development work of the user can be supported by operating the chat device based on each dialog component and each dialog scenario information.

It is an explanatory view showing a functional configuration of a development support system. FIG. 3 is an explanatory diagram showing a state of system development. It is a hardware block diagram of a development support system. FIG. 2 is a software configuration diagram of a development support system. It is an example of composition of design information meta information. It is a structural example of the information which shows the relationship between design information meta information. It is a structural example of design information. It is an example of composition of the information which shows the relation between design information. It is an example of composition of a design information dialog part. It is an example of composition of a dialog part. It is an example of composition of dialog scenario information. It is a structural example of channel information. It is an example of composition of user information. It is a screen example of a chat channel menu. It is an example of a screen following FIG. 4 shows an example of an operation screen for design information. 9 shows another example of an operation screen for design information. 9 shows yet another example of an operation screen for design information. 9 shows another example of an operation screen for design information. 9 is a flowchart of a process for generating conversation scenario information. It is a flowchart of a process of generating a dialog component. It is a flowchart of an interactive process. It is a flowchart which shows the process of dialog scenario information. 13 is a flowchart of a process for monitoring a chat according to the second embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the present embodiment, dialog scenario information is generated using existing design information meta information, and a user's system development work is supported through a dialog on a chat using the dialog 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 held by the design information management unit 210 of the design information repository device 2, and various design information meta A design information meta information relation 230 defining the relation between information, and design information in which the contents of the dialog for the work performed in common in all the design information 240 in the dialog scenario information generating unit 310 of the dialog scenario processing device 3 are made into parts. A dialog component 330 corresponding to the work of various design information is generated from the dialog component 320. Further, the dialog scenario information generation unit 310 generates the dialog scenario information 340 from the dialog component 330 for each work of various design information, and generates the channel information 350 on the chat device 4.

  The interaction processing unit 411 of the chat device 4 processes the developer (user) text 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 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 device 2 in the course of the dialogue on the chat. Thereby, the developer can inquire, newly register and edit various design information through the chat.

  According to the development support system 1 according to the present embodiment, the dialog scenario information 340 for supporting the work of the developer who creates the design information 240 through the dialog on the chat can be efficiently and automatically generated. Further, the development support system 1 according to the present embodiment can support the developer's work based on the dialog scenario information 340 through a dialog on a chat.

  An embodiment 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 overall image in which the development support system 1 supports the system development work will be described with reference to the explanatory diagram of FIG. Further, 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 dialog scenario processing device 3 (see FIG. 3), a chat device 4, and a client device 5.

  The dialog scenario processing device 3 includes a dialog scenario information generating unit 310 that generates dialog scenario information, and a dialog scenario information processing unit 311 that processes the dialog scenario information. The design information repository device 2 stores and manages, for example, design information meta information 220, design information meta information relation 230, design information 240, and design information relation 250. The information 220 to 250 will be described later with reference to FIGS. The design information repository device 2 and the storage unit 31 of the dialog scenario processing device 3 are examples of an “information storage unit”.

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

  The design information dialogue component 320 may be manually registered in advance by the manager U1 of the development support system 1, or may be automatically obtained 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 dialog scenario information 340 will be described later with reference to FIG.

  The dialog 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. The 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 has a dialog processing unit 411 as described later with reference to FIG. The dialog scenario information processing unit 311 receives information (character strings, commands) input from the user U2 via the dialog processing unit 411, and interacts with the user U2 using the dialog scenario information 340 and the dialog component 320.

  For example, when the user U2 inputs a command (S1), the dialog scenario information processing unit 311 requests processing of the command in cooperation with the design information repository device 2 (S2). Upon receiving the processing result from the design information repository device 2 (S3), the dialog scenario information processing unit 311 returns the processing result to the client device 5 together with the instruction response sentence (S4). Here, the instruction response sentence is a message including either a message instructing the user U2 or a message responding 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 manager U1 of the development support system 1 generates a bot for supporting the system development work in advance. The created chat bot interacts with the user U2 based on the dialog component 330 and the dialog scenario information 340. Thus, the user U2 can process each process such as “requirement definition”, “design”, “detailed design / implementation”, “test”, and “release / operation” while receiving the support of the bot. For example, each user U2 involved in the system development can exchange information with each other user through chat, and can receive an instruction such as what to do next from the bot. Further, each user U2 can access and edit the 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 dialog scenario processing device 3, the chat device 4, and the client device 5. The development support system 1 can be composed of one computer, or can be composed of a plurality of computers as shown in FIG. Each of the devices 2 to 5 may be configured as a separate computer and interconnected via a communication network CN, or the functions of the devices 2 to 5 may be implemented on one computer.

  The design information repository device 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 arithmetic unit 20 reads and executes a predetermined computer program stored in the storage unit 21 to realize 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 that connects to the communication network CN. The design information repository device 2 can perform two-way communication with another device 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 (neither is 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, and the like. The information output device is, for example, a display, a printer, a voice synthesizer, or the like.

  Similarly, the dialog scenario processing device 3 also 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. The functions 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 device 2, and further description will be 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 device 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 has a function of managing each data of the design information meta information 220, the design information meta information relation 230, the design information 240, and the design information relation 250. The pieces of information 220 to 250 are stored in the storage unit 21 of the design information repository device 2 and are read and written by the design information management unit 210.

  The design information editing unit 211 has a function of inquiring, registering, editing, and updating each of the 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 dialog scenario processing device 3 includes a computer program for realizing a dialog scenario information generating unit 310 and a dialog scenario information processing unit 311. The dialog scenario information generation unit 310 has a function of generating a dialog component 330, dialog scenario information 340, and channel information 350 from the design information meta information 220, the design information meta information association 230, and the design information dialog component 320.

  The dialog scenario information processing unit 311 displays an instruction response sentence 335 of the dialog component 330 based on the dialog scenario information 340 in response to the reception command 334 (see FIG. 10) specified by the dialog component 330 input by the user. And a function for executing the script 336.

  The chat device 4 includes a computer program for realizing the channel information management unit 410 and the interaction 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 interaction processing unit 411 has a function of displaying a channel selected by the user based on the channel information 350 and the user information 420, and accepting an input from the user to process a 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 U2 can use the chat service provided by the chat device 4 using the browser 510.

  ――Data structure――

  Examples 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 newly registered 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 the type of the design information 240. The type 223 includes, for example, component design, class design, and method design. The inquiry URL 224 is an address for calling a function of the design information editing unit 211 (design information inquiry). The newly registered URL 225 is an address for calling a function of the design information editing unit 211 (registration of design information). The edit URL 226 is an address for calling a function of the design information editing unit 211 (edit of design information). The description 227 is a description including a hyperlink to a guide or the like for defining the design information.

  FIG. 6 is an example of the design information meta information association 230. The design information meta information association 230 is data that defines the association between the 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 relation source ID 232 is information indicating the design information meta information 220 of the relation source. The association destination ID 233 is information indicating the design information meta information 220 of the association destination. The association type 234 is information indicating the 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. The type of association includes, for example, 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 a content 245.

  The ID 241 is information for uniquely identifying the 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. Any value of the ID 221 shown in FIG. 5 is set in the meta information ID 242. 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 the design information relation 250. The design information relation 250 is data that defines a relation between the plurality of design information 240. The design information relation 250 includes, for example, an ID 251, a relation source ID 252, and a relation destination ID 253.

  The ID 251 is information for uniquely identifying a design information relation. The relation source ID 252 is information indicating the design information 240 of the relation 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 dialog part 320 which is a model of the dialog part 330. The design information dialogue component 320 includes, for example, an ID 321, a type 322, a condition 323, a received command template 324, an instruction / response template 325, and a next ID 326.

  The ID 321 is information for uniquely identifying the design information interactive component. The type 322 is information that defines the type of the design information interactive component. Types include “create” and “edit”. The condition 323 indicates a condition when the interactive component is executed. The condition 323 can include the value of the design information interactive component ID 321. The reception command template 324 is information that defines a template of a command received from the user. The instruction response message template 325 is information that defines a template of an instruction response message to be presented to the user after receiving the command. The next ID 326 is information indicating the next design information interactive component.

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

  The ID 331 is information for uniquely identifying a dialog component. The type 332 indicates the type of the interactive component. The types include, for example, “creation of detailed design information” and “common”. The condition 333 indicates a condition when the interactive component is executed. The accept command 334 is information that defines a command accepted from the user. The instruction response sentence 335 is information that defines an instruction response sentence 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 dialogue component.

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

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

  FIG. 12 shows an example of the channel information 350. Channel information 350 defines a chat channel. The channel information 350 includes, for example, an ID 351, a channel name 352, a dialog 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 a channel. The dialog scenario information ID 353 indicates the dialog scenario information applied in the channel. The participating user ID 354 is information for identifying 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, a right 423, and an e-mail address 424.

  The ID 421 is information for uniquely identifying a user. The user name 422 defines the name of the user. The authority 423 defines the authority of the user. The e-mail address 424 is an e-mail address of the user. Note that information about other communication means such as a telephone number may be registered instead of or together with the e-mail address.

  -System operation-

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

  The process (S10) for generating the dialog scenario information will be described with reference to FIG. The dialog scenario information generation unit 310 reads the design information meta information 220 from the design information repository device 2 (S11). Specifically, the dialog scenario information generation unit 310 connects to the communication unit 22 of the design information repository device 2 from the communication unit 32 of the dialog scenario processing device 3 via the communication network CN. The design information management unit 210 of the design information repository device 2 reads out the design information meta information 220 from the storage unit 21 and transmits it to the dialog scenario information generation unit 310.

  As in step S11, the dialog scenario information generation unit 310 reads the design information meta information association 230 from the storage unit 21 by the processing of the design information management unit 210 (S12).

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

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

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

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

  The dialog scenario information generation unit 310 generates channel information 350 from the dialog scenario information 340 generated in step S15, and transmits 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 dialog scenario information 340 is copied to the channel name 352, the dialog scenario information ID 341 of the dialog scenario information 340 is copied to the dialog scenario information ID 353, and “*” is defined as the participating user ID 354. Here, “*” means all users.

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

  The dialog 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 dialog scenario information generation unit 310 repeats the processing with step S28 until there is no more unprocessed record group extracted in step S21. In the example of FIG. 5, records of design information meta information IDs “0020” and “0021” having “details” are extracted as steps 222 in the design information meta information 220.

  The dialog 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 “aggregate” (S22). More specifically, the dialog scenario information generation unit 310 extracts the design information meta information relation 230 related to the record group extracted in step S21, and extracts the one whose relation type 234 is “aggregate” from the extracted information. Then, the dialog scenario information generation unit 310 identifies the related source and the related destination related to the aggregation, and specifies the design information meta information 220 of the route that does not include the related source.

  For example, the record of the design information meta information relation 230 containing 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, the record whose relation type 234 is “aggregate” is the 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 the root. As the related destination, a record whose design information meta information ID 221 of the design information meta information 220 is “0021” (hereinafter, this record is referred to as child design information meta information with respect to the root) is identified.

  The dialog 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 dialog scenario information generation unit 310 repeats step S23 until there are no unprocessed records (S27). For example, it is assumed that the design information meta information ID 221 that is the root is “0020” and the type 223 is the design information meta information 220 of “class design information”.

  The dialog scenario information generation unit 310 extracts one unprocessed record from the design information dialog components 320 read in step S13 (S24). The dialog scenario information generation unit 310 repeats step S24 until there is no unprocessed record (S26).

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

  For example, with respect to the “class design information” which is the route extracted in step S23, the design information interactive component type 322 of the design information interactive component 320 is a record whose design information interactive component is “design information creation”, and the design information interactive component ID is “6000”. Processing for generating a dialogue component when “6001”, “6002”, and “6500” are present will be described.

  In the case where the design information dialog part ID is a record of “6000” (see FIG. 9), the dialog scenario information generation unit 310 numbers the dialog part ID 331 of the dialog part 330 as “8020” (see FIG. 10). A character string "Create detailed design information" is created by combining the process "Details" of "Class design information" and the design information interactive part type "Design information creation" whose design information interactive part ID is "6000".

  The dialog scenario information generation unit 310 creates the dialog component type 332 of the dialog component 330, and converts “{design information type}” of the received command template 304 “start ({design information type})” into the design information meta information 220. “Start (class design information)” is created as the reception command 334 by replacing the type with the type 223.

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

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

  Copying the dialog execution condition 323 “begin” to the dialog execution condition 333 is limited to the root.

  If the design information dialog component ID is “6001”, the dialog scenario information generation unit 310 assigns the dialog component ID 331 of the dialog component 330 as “8030”.

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

  The dialog scenario information generation unit 310 replaces “finish (class design information)” of the received command template 304 “finish ({design information type})” with the type 223 to replace “finish (class design information)”. Created as an accept command 334.

  The dialog scenario information generation unit 310 performs the instruction response template 325 “Created [Register“ {design information type} ”]” ({design information new registration URL}). Of the "@" of the ".", Based on the type 223 and the newly registered URL of the design information 225, the instruction response sentence 335 "Created [Register" class design information "] (http: // ...) Please give me. Is generated.

  The dialog scenario information generation unit 310 allocates the next execution dialog component ID “8040” by allocating the dialog component ID to the next design information dialog component ID “6002”.

  If the design information dialog component ID is “6002”, the dialog scenario information generation unit 310 assigns the dialog component ID 331 of the dialog component 330 as “8040”.

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

  The dialog scenario information generating unit 310 creates the instruction response template 325 “{(# 1)}“ {design information type} ”}. , “{(# 1)}” uses a character string enclosed by ｛｝ to create not only its own separate design information but also the creation of design information of that design information type when there are children. As a special directive to prompt, please create another "class design information" or a child "method design information". Is generated.

  When the design information dialog part ID is “6500”, the dialog scenario information generation unit 310 assigns the dialog part ID 331 of the dialog part 330 as “8080”.

  The dialog scenario information generation unit 310 combines the process “detail” of “class design information” and the design information dialog component type 322 “design information creation” with the design information dialog component ID of “6002” into “detailed design information creation”. Is created as the dialog part type 332 of the dialog part 330.

  The dialog scenario information generating unit 310 replaces “{design information type}” of the received command template 304 “doc ({design information type})” with the type 223, thereby converting “doc (class design information)”. Created as an accept command 334.

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

  Since the design interaction information type 322 of the design information interaction component 320 also includes “design information editing”, the interaction scenario information generation unit 310 assigns the interaction component ID 331 of the interaction component 330 as “8100”.

  The dialog scenario information generation unit 310 combines the process “detail” of “class design information” with the design information dialog component type 322 “design information edit” of which design information dialog component ID is “6002” to “edit detailed design information”. Is created as the dialog part type 332 of the dialog part 330.

  The dialog scenario information generating unit 310 replaces “{design information type}” of the received command template 304 “doc ({design information type})” with the type 223, thereby converting “doc (class design information)”. Created as an accept command 334.

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

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

  As described above, the dialog scenario information generation unit 310 can generate the dialog component 330, the dialog 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 dialog component 320.

  FIG. 22 is a flowchart showing a chat dialogue process. 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 a character string input from the browser 510.

  The interactive processing unit 411 of the chat device 4 reads the channel information 350 from the storage unit 41 and displays a “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 a menu 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 channel information 350 corresponding to the channel selected by the user via the browser 510 from the storage unit 41, and displays a 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.

  Simultaneously with the opening of the channel, the dialog processing unit 411 of the chat apparatus 4 calls the dialog scenario information 340 of the dialog scenario processing apparatus 3 and specifies a record having the same design work name 342 as the opened channel information name. Read from the storage unit 31. Further, the dialog processing unit 411 reads the record of the dialog component 330 having the dialog component ID 331 designated by the applied dialog component ID 343 of the read record, and records in which the dialog execution condition 333 is “begin” in the read record. To identify. The interaction processing unit 411 displays the instruction response sentence 335 of the specified record as the first information from the chat device 4 on the browser 510 of each user participating in the channel.

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

  “Bot” on the channel indicates a chatbot automatically generated by the chat device 4 in response to a user input. The chatbot is realized by the dialog scenario information processing unit 311 responding based on the dialog scenario information 340 and the dialog component 330 according to the processing result of the dialog processing unit 411.

  “Hoge” and “Leader” on the channel indicate a user registered in the user information 420. The user displayed in “Leader” is an example of “predetermined high-order user”, “predetermined notification destination”, or “high-order user”. Each user can input commands and messages via the browser 510 of the client device 5 to be used.

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

  When detecting an input from the user (S32: YES), the interaction processing unit 411 determines whether a command is included in the information input by the user (S33). When determining that the command is not included (S33: NO), the dialog processing unit 411 displays information input by the user in step S32 on the channel. As a result, information (message) input by a certain user is displayed on the browser 510 used by each user participating in the channel. After that, the process of the interaction 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 information received from the user includes a command (S33: YES), the chat device 4 determines whether the command is an end command (S35).

  When the command received from the user is the end command (S35: YES), the chat device 4 closes the channel and ends the process (S36). When it is determined that the information input by the user includes a command other than the end command (S35: NO), the chat device 4 calls the dialog scenario information processing unit 311 and performs the dialog scenario information processing described later with reference to FIG. (S37) is executed. The chat device 4 displays the instruction response sentence, the error message, and the like 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 dialog scenario information processing section 311 which is called and executed by the dialog processing section 411 of the chat device 4.

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

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

  If 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 an error process (S42).

  In the error processing, for example, an error message indicating that the input command cannot be processed is returned to the call processing unit 411. Even if the record corresponding to the command input by the user can be obtained from the dialog component 330, if the dialog component specified by the dialog execution condition 333 has not been 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 dialog scenario information processing section 311 determines that the command input by the user is acceptable (S41: YES), the dialog scenario information processing section 311 reads the instruction response sentence from the instruction response sentence 335 in the record corresponding to the command, and reads the instruction response sentence. Return to the dialogue processing unit 411.

  The dialog scenario information processing section 311 executes the script defined in the script 336 of the record corresponding to the command input by the user (S44). The script is any computer program that can be executed by the calculation unit 30 of the dialog scenario processing device 3.

  The dialog scenario information processing unit 311 determines whether a dialog component to be executed next is registered in the next ID 337 of the record corresponding to the command input by the user (S45), and if it is registered (S45: YES), Steps S43 and S44 are executed for the dialog component. If the dialog component to be executed next has not been registered (S45: NO), this process ends, and the process returns to step S37 in FIG. 22, which is the calling source.

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

  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 with an underlined character string of the wording GP212 is selected, the function (registration of design information) of the design information management unit 210 is called, and the screen 4 in FIG. .

  The wording GP214 is a wording input by the user “Hoge”, the command “/ doc (method design information)” is processed in step S37, and the wording GP215 is displayed on the browser 510. When a hyperlink displayed with an underlined character string of the wording GP215 is selected, a document (design guide) specified by the URL of the hyperlink is displayed on the browser 510.

  The wording GP216 is a wording input by the user “Hoge”, the command “/ start (method design information)” is processed in step S37, and the wording GP217 is displayed on the browser 510. When the hyperlink of the wording GP217 is selected, the design information management unit 210 is called, and the screen G5 of FIG.

  The word GP218 is a word input by the user “Hoge”, the command “/ finish (method design information)” is processed in step S37, and the words GP219 and GP220 are displayed on the browser 510. When the hyperlink displayed with the underlined character string of the wording GP219 is selected, the function (registration of design information) of the design information management unit 210 is called, and the screen G6 of FIG. .

  The wording GP221 is a wording input by the user “Leader”, and is displayed on the browser 510 in step S34.

  The wording GP222 is a wording input by the user “Hoge” and is displayed on the browser 510 in step S34.

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

  The wording GP224 is a wording input 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 dialog scenario information 340, and the dialog component 330, development is supported by automatically responding to a word input by a user (developer). Function (chat bot) can be realized efficiently. This function can be realized by the channel information management unit 410, the dialog processing unit 411, and the dialog scenario information processing unit 311.

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

  In the development support system 1 of the present embodiment, since the design information editing unit 211 of the design information repository device 2 can be accessed during the dialogue, the various design information 240 and the design information related 250 can be updated and updated in the chat. Can view, register and edit. In the development support system 1 according to the present embodiment, the user can proceed with the development work in the chat while receiving advice (instruction / response) for supporting the development work in the chat, thereby improving usability.

  A second embodiment will be described with reference to FIG. Since the present embodiment corresponds to a modification of the first embodiment, the description will focus on differences from the first embodiment. In the present embodiment, the content of the chat is monitored, and a higher order person can be notified according to the content.

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

  The chat monitoring unit 412 analyzes the acquired input information (S52), and determines from the analysis result whether to notify a superior (administrator or the like) (S53). For example, if a predetermined keyword is included in the input information or a predetermined command is included in the input information, a setting is made in advance to notify a higher order person.

  If the chat monitoring unit 412 determines that there is no need to notify the superior (S53: NO), the process 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 chat content of a predetermined range including a predetermined keyword or a predetermined command is extracted, and the extracted chat content is transmitted to a superior as a chat summary.

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

  The present embodiment configured as described above has the same operation and effect as the first embodiment. Further, in this embodiment, according to the contents of the chat of the user, an outline of the chat can be transmitted to a superior of the user, and a caution can be given to confirm the chat. Therefore, the superior can efficiently monitor the development work of the user 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 can be variously modified without departing from the gist thereof.

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

  In the above description, a chat using characters has been described as an example, but a chat tool using voice may be used. Further, an email tool instead of a chat tool may be used as an alternative.

  The present invention is not limited to the above embodiments, but includes various modifications. For example, each of the above embodiments has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to those having all the configurations described above.

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

  In addition, the above-described configurations, functions, and the like may be implemented by software by a processor interpreting and executing a program that implements each function. Information such as a program, a table, and a file 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.

  In addition, control lines and information lines are shown as necessary for the description, and do not necessarily indicate all control lines and information lines on a product. In fact, it can be considered that almost all components are connected to each other.

  In addition, each component of the present invention can be arbitrarily selected, and an invention having the selected configuration is also included in the present invention. Further, the configurations described in the claims can be combined other than the combinations explicitly stated in the claims.

  1: Development support system, 2: Design information repository device, 3: Dialog 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: dialog scenario information generation unit, 311: dialog scenario information processing unit, 320: design information dialog component, 330: dialog component, 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.
A plurality of pieces of first information defining meta information of a plurality of pieces of design information; a second piece of information defining a relationship between the plurality of pieces of first information; And the third information defining a template of a dialog component prepared for an operation to be performed, the template being a command of a user input and a template of a message to be presented to the user. An information storage unit for storing;
A dialog for generating a dialog component for each work of the design information and a dialog 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 generation unit,
A dialogue scenario information processing unit that operates a chat device based on the respective dialogue parts and each dialogue scenario information,
Development support system with The dialog scenario information generating 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 an interaction processing unit that analyzes information input from the user and performs an interaction with the user,
The dialog scenario information processing unit supports the system development work by operating the dialog processing unit based on information input by the user from the dialog processing unit, the respective dialog components, and the respective dialog 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 by the user from the interaction processing unit,
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 of 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 of the channels is associated with a channel name based on the name of the design work, an identifier that specifies the dialog scenario information to be used, and an identifier that specifies the participating user.
The development support system according to claim 3. The interaction processing unit includes a chat monitoring unit,
The chat monitoring unit notifies a predetermined upper-level user based on an analysis result of information input from the user.
The development support system according to claim 3. The interaction processing unit includes a chat monitoring unit,
The chat monitoring unit generates a summary of the content of the conversation with the user and notifies a predetermined notification destination,
The development support system according to claim 3. The predetermined notification destination is a higher-order user located at a higher rank of the user,
The development support system according to claim 9. A development support method in which a computer supports system development work through chat,
A plurality of pieces of first information defining meta information of a plurality of pieces of design information; a second piece of information defining a relationship between the plurality of pieces of first information; And the third information defining a template of a dialog component prepared for an operation to be performed, the template being a command of a user input and 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 components for each operation of the design information and interactive scenario information for each operation unit based on the design information,
Operating a chat device based on the dialog components and the dialog scenario information,
Development support method.

Images