JP7361596B2 - Message processing device, message processing system and message processing program - Google Patents

Description

The present invention relates to sending and receiving messages between multiple instances related to software development or operation.

Traditionally, chat systems to promote information sharing among developers or task management systems to manage the list of tasks to be performed by developers and their progress have been used to improve the efficiency of software development. There is. Furthermore, conventionally, bots have been used to connect multiple systems to facilitate coordination between systems. For example, Patent Document 1 describes that by connecting a chat system and an SMS (shot message service) system using a bot, short messages can be sent using input to the chat system. In addition, a bot has conventionally operated a task management system via the chat system by connecting the chat system and the task management system. This reduces the cost required to manipulate information.

In software development, it is difficult for one organization (hereinafter referred to as an "instance") to complete the process of designing, developing, testing, and operating all the components to be developed. Therefore, multiple instances often proceed with development while checking each other's progress.

In software development that is performed using multiple instances, the type of development management system held by each instance or the conditions for disclosing information are often different for each instance. Therefore, developers manually shared information across instances using email or telephone.

Japanese Patent Application Publication No. 2018-116455

In a rapidly changing business environment, the requirements for software are changing rapidly, so it is necessary to keep up with these changes and create new business value. Therefore, it is necessary to increase the frequency of software releases, and an increase in the lead time until the release of a function leads to a loss of trust or a loss of sales opportunities. In software development, the time required to share information between instances has a significant impact on the lead time from functional requirements definition to release.

If information is shared between instances manually, it takes time, and work gets delayed while waiting for a response from the other instance. In addition, manual information sharing causes time and effort, leading to problems such as a reduction in the frequency of real-time information transmission and the occurrence of discrepancies in shared information. As a result, developers make decisions based on outdated and uncertain information from other instances, making it difficult to make correct decisions regarding their own team's activities, such as selecting tasks, and making it difficult to maximize the value provided by the instance. becomes impossible.

Furthermore, even if information sharing between instances is automatically performed by a bot, there is a problem in that mere automation cannot handle cases where message access privileges are determined individually for each instance.

The present invention was made to solve the above problems, and involves the development of software to automatically share information between multiple instances in which access rights to transmitted messages are individually determined. The purpose is to

The message processing device of the present invention is capable of transmitting and receiving messages using a message transmitting and receiving device that is installed in each of a plurality of instances that develop or operate the same software and have a unique development management system, and that transmits and receives messages between the multiple instances. A message management unit that is a message processing device to be controlled and that receives messages from a message transmitting/receiving device refers to instance information that associates an instance of a message sender with an instance that has access rights to the message, and processes the message. The message distribution unit determines a target instance from a plurality of instances based on the instance of the transmission source of the message received by the management unit and the instance information, and distributes the message received by the message management unit to the target instance.

Since the message processing device of the present invention determines the target instance based on the instance information, when the access control rules for sending messages are different for each instance, the message processing device sends the message to the appropriate instance according to the access control rules of the source instance. can be delivered.

1 is a diagram showing the configuration of a message processing system according to a first embodiment; FIG. It is a diagram showing the data format of messages stored in a message DB. It is a diagram showing instance information stored in an instance DB. It is a diagram showing message processing information stored in a message processing DB. It is a flowchart regarding message transmission and reception between the operation department and the development department. 1 is a diagram showing a hardware configuration of a message processing system. 1 is a diagram showing a hardware configuration of a message processing system. FIG. 3 is a diagram illustrating an example of arrangement of message processing devices and instances with respect to network segments; FIG. 3 is a diagram illustrating an example of arrangement of message processing devices and instances with respect to network segments; FIG. 3 is a diagram illustrating an example of arrangement of message processing devices and instances with respect to network segments;

<A. Embodiment 1>
<A-1. Configuration>
FIG. 1 is a diagram showing the configuration of a message processing system 101 according to the first embodiment. The message processing system 101 includes an instance A, an instance B, and a message processing device 30.

Instance A and instance B are both organizations that develop or operate the same software, and for example, instance A corresponds to the development department and instance B corresponds to the operation department. Instances A and B each have their own development management system 10, and further have a message transmitting device 41 and a message receiving device 42.

The development management system 10 includes, for example, a chat system 11, a task management system 12, a build management system 13, and a version management system 14. The chat system 11 is used for communication between workers within each instance. The task management system 12 manages tasks performed by workers. The build management system 13 performs automatic testing or automatic building of software. The version management system 14 manages software versions. Instance A and instance B each have their own development management system 10, so for example, a worker 40 belonging to instance A can operate the development management system 10 in instance A, but instance B The development management system 10 within the company cannot be operated.

In the example of FIG. 1, the message processing system 101 includes instances A and B. In the example shown in FIG. However, the number of instances provided by the message processing system 101 is not limited to two.

Instances A and B have a message transmitting device 41 that transmits messages to the message processing device 30 and a message receiving device 42 that receives messages from the message processing device 30. For convenience of explanation, FIG. 1 shows the configuration of the message transmitting device 41 in instance A and the configuration of the message receiving device 42 in instance B, but in reality, instances A and B are the same as the message transmitting device 41. It has both a message receiving device 42. In other words, instances A and B have message transmitting and receiving devices that transmit and receive messages.

The message transmitting device 41 includes an event detecting section 15, a message generating section 16, and a message transmitting section 17. The event detection unit 15 detects events issued by the development management system. The message generation unit 16 generates a message based on the content of the event detected by the event detection unit 15. The message transmitter 17 transmits the message generated by the message generator 16 to the message processing device 30.

The message receiving device 42 includes a message receiving section 18, a job executing section 19, and a message processing database (DB) 20. The message receiving unit 18 receives messages from the message processing device 30. The job execution unit 19 receives a job from the job generation unit 36 of the message processing device 30 and executes the job. The message processing DB 20 stores message processing information. That is, the message processing DB 20 functions as a message processing information storage section. The message processing information is information in which the type of message is associated with the content of the process that the instance to which the message receiving device 42 belongs should perform when receiving the message.

The message processing device 30 includes a message management section 31, a message database (DB) 32, an ID generation section 33, an instance database (DB) 34, a message distribution section 35, and a job generation section 36. The message management section 31 receives a message from the message transmission section 17 of the message transmission device 41 and stores the received message in the message DB 32. Therefore, the message DB 32 functions as a message storage section.

FIG. 2 shows the data format of messages stored in the message DB 32. The message includes an ID (message_id) for uniquely identifying the message, a message type (message_kind), sender information (from), and message contents (props). The sender information (from) includes the name of the sender's instance (instance_name), the identification ID of the sender's development management system (system_id), and the identification ID of the element in the sender's development management system (item_id). ). The content of the message differs depending on the type of message. For example, the content of a message with ID=1001 and type "task" is the type of event that occurred (event_kind) "new creation (create)" and the name of the task to be executed by the event that occurred (task_name) "〇 "Add function of 〇", the identification ID (task_id) of the task "10", and the name of the reporter (repoeter_name) "〇〇".

Additionally, if the message is one of a series of messages, it includes information on the sender (origin) of the first message. The sender information (origin) item of the first message is the same as the sender information (from) item of this message.

As shown in FIG. 2, each message stored in the message DB 32 is given an ID (message_id) for uniquely identifying the message. Based on this, the ID generation section 33 generates a new ID that has not been assigned to any message yet, and provides it to the message generation section 16 of the message transmission device 41. The message generation unit 16 generates a message by adding the new ID obtained from the ID generation unit 33.

The instance DB 34 stores instance information regarding instances within the message processing system 101, in other words, instances belonging to the same network as the message processing device 30. That is, the instance DB 34 functions as an instance information storage unit. FIG. 3 shows a specific example of instance information. In the example of FIG. 3, the instance information includes instance name, site information, department information, affiliated project, and access control information. Instance names include development department 1, development department 2, operation department 1, and so on. The site information is information on the location where the instance is located, such as the Tokyo office, Osaka office, Hyogo office, etc. The department type is the type of instance, such as development or operation. The projects to which the user belongs are projects 1, 2, and so on. Access control includes information on instances that can access the transmission information of each instance. In this way, the instance information is information that associates an instance that is a message sender with an instance that has access rights to messages sent from the instance.

The message distribution unit 35 refers to the instance DB 34, determines the target instance (hereinafter referred to as “target instance”) to which the message received by the message management unit 31 is to be distributed, and distributes the message to the target instance.

The job generation unit 36 refers to the message processing DB 20 of the target instance, generates a job as a process to be performed by the target instance on the message to be distributed, and sends the job to the job execution unit 19 of the target instance.

FIG. 4 shows a specific example of message processing information stored in the message processing DB 20. The message processing information is information that defines the processing to be performed on received messages for each type of message. For example, in the example of FIG. 4, in the message processing information, a process of "adding a task to correct a defect to the task management system" is defined for a "message about a new defect." Further, for the "chat message for the own instance", the process of "posting the message to the chat system" is defined.

<A-2. Operation>
FIG. 5 shows a flowchart regarding message transmission and reception between the operation department and the development department when a problem occurs. The operation of the message processing system 101 will be described below with reference to FIG. In the following explanation, as an example, the operation department is the worker of instance A, the development department is the worker of instance B, the operation department bot is the message sending device 41 and message receiving device 42 of instance A, and the development department bot is the message of instance B. They are treated as a transmitting device 41 and a message receiving device 42.

First, the operation department registers defect X in the defect monitoring system (step S1). Here, the defect monitoring system is one of the development management systems that instance A has. Next, the operation department bot notifies the development department of the registration of defect X (step S2). Specifically, the event detection unit 15 detects the occurrence of an event of sending a registration message for defect X. Then, a registration message for defect X is generated by the message generation unit 16 and transmitted to the message processing device 30 by the message transmission unit 17. The registration message for defect X is a message that notifies that defect X has been registered in the defect monitoring system of the operation department.

In the message processing device 30, when the message management unit 31 receives the registration message of defect X, it stores it in the message DB 32. Then, the message distribution unit 35 learns from the registration message of defect X that the source instance is the operation department, and refers to the instance DB 34 to obtain access control information for the operation department. Then, the message distribution unit 35 determines the target instance to which the registration message of defect X is to be distributed, according to the access control information of the operation department. Here, it is assumed that the access control information for the operation department specifies that the development department can view the defect registration message. In this case, the message distribution unit 35 sets the development department as the target instance and distributes the registration message of defect X to the development department. In this way, a registration message for defect X is sent from the operation department to the development department via the message processing device 30.

When the development department bot receives the registration message for defect X, it registers task Y corresponding to defect X in the task management system 12 (step S3). Specifically, in instance B, the message receiving unit 18 receives the registration message of defect X, and the job execution unit 19 acquires the job corresponding to the registration message of defect X from the job generating unit 36 of the message processing device 30. Here, the job generation unit 36 acquires the processing contents of instance B for the registered message of defect generate. In the example of FIG. 4, in response to the "message about a new defect," "add a task to correct defect A job called "Register task Y to be executed in the task management system 12" is generated and sent to the job execution unit 19 of instance B. Then, the job execution unit 19 registers the task Y in the task management system 12. Furthermore, the job execution unit 19 associates the defect X with the task Y (step S4).

Next, the development department worker changes the status of task Y to in progress in the task management system 12 (step S5). The development department bot then notifies the operation department of the change in the status of task Y (step S6). Specifically, the message transmitting device 41 of the instance B transmits a message to the instance A via the message processing device 30 notifying that the status of the task Y corresponding to the defect X has been changed to in progress.

When the operation department bot receives the message, it changes the status of defect X to in progress in the task management system 12 of instance A (step S7). Then, the operator in the operation department adds details of the defect X in the task management system 12 (step S8). After that, the operation department bot notifies the development department of the details of defect X (step S9). Specifically, the message transmitting device 41 of the instance A transmits a message notifying the details of the defect X to the instance B via the message processing device 30.

When the development department bot receives the message, it adds the details of the defect X to the task Y in the task management system 12 of the instance B (step S10).

Thereafter, when the development department worker completes task Y, he changes the status of task Y to completed in the task management system 12 of instance B (step S11). The development department bot then notifies the operation department of the change in the status of task Y (step S12). Specifically, the message transmitting device 41 of the instance B transmits a message to the instance A via the message processing device 30 notifying that the status of the task Y corresponding to the defect X has been changed to treated.

When the operation department bot receives the message, it changes the status of defect X to treated in the task management system 12 of instance A (step S13). Thereafter, after confirming that defect X has been corrected, the operator in the operations department changes the status of defect X to completed in the task management system 12 of instance A (step S14). The operation department bot then notifies the development department of the change in the status of defect X (step S15). Specifically, the message transmitting device 41 of the instance A transmits a message to the instance B via the message processing device 30 notifying that the status of the defect X has been changed to completed.

When the development department bot receives the message, it changes the status of task Y to completed in the task management system 12 of instance B (step S16).

<A-3. Hardware configuration>
The configurations of the message transmitting device 41, message receiving device 42, and message processing device 30 described above are realized by a processing circuit 81 shown in FIG. That is, the processing circuit 81 includes an event detection section 15, a message generation section 16, a message transmission section 17, a message reception section 18, a job execution section 19, a message processing DB 20, a message management section 31, a message DB 32, an ID generation section 33, and an instance. It includes a DB 34, a message distribution section 35, and a job generation section 36 (hereinafter referred to as "message distribution section 35, etc."). Dedicated hardware may be applied to the processing circuit 81, or a processor that executes a program stored in memory may be applied. The processor is, for example, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, a DSP (Digital Signal Processor), or the like.

When the processing circuit 81 is dedicated hardware, the processing circuit 81 may be, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Circuit). Gate Array), or a combination of these. The functions of each section, such as the section .

When the processing circuit 81 is a processor, the functions of the message distribution unit 35 and the like are realized by a combination of software and the like (software, firmware, or software and firmware). Software etc. are written as programs and stored in memory. As shown in FIG. 7, a processor 82 applied to a processing circuit 81 realizes the functions of each part by reading and executing a program stored in a memory 83. That is, the message processing device 30 performs the step of receiving a message from the message transmitting device 41, and refers to the instance information in which the instance of the source of the message is associated with the instance that has access rights to the message, and processes the received message. Stores a program that results in the following steps being executed: determining a target instance from multiple instances based on the source instance and instance information; and delivering a received message to the target instance. A memory 83 is provided for the purpose. In other words, this program can be said to cause a computer to execute the procedure or method of the message distribution unit 35 and the like. Here, the memory 83 includes nonvolatile memory such as RAM (Random Access Memory), ROM (Read Only Memory), flash memory, EPROM (Erasable Programmable Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory). or volatile semiconductor memory, HDD (Hard Disk Drive), magnetic disk, flexible disk, optical disk, compact disk, mini disk, DVD (Digital Versatile Disk) and its drive device, or any storage medium that will be used in the future. There may be.

The above has described a configuration in which each function of the message distribution unit 35 and the like is realized by either hardware, software, or the like. However, the present invention is not limited to this, and a configuration may be adopted in which a part of the message management section 31 etc. is realized by dedicated hardware, and another part is realized by software or the like. For example, the function of the message generation unit 16 is realized by a processing circuit as dedicated hardware, and for other functions, the processing circuit 81 as a processor 82 reads and executes a program stored in the memory 83. It is possible to realize this.

As described above, the processing circuit can realize each of the above functions using hardware, software, etc., or a combination thereof. Note that the message processing DB 20, message DB 32, and instance DB 34 are composed of the memory 83, but they may be composed of a single memory 83, or each may be composed of individual memories.

There is no need for a one-to-one relationship between the message processing device 30 and the instance. The configurations of the message processing device 30, message transmitting device 41, and message receiving device 42 that make up the bot network do not depend on the arrangement of network segments or servers. For example, as shown in FIG. 8, instance A, instance B, and message processing device 30 may be installed in different network segments A, B, and C, respectively. Alternatively, as shown in FIG. 9, instance A and message processing device 30 may be installed in the same network segment A, and instance B may be installed in another network segment B. Alternatively, as shown in FIG. 10, instance A, instance B, and message processing device 30 may be installed in the same network segment A.

As shown in FIGS. 9 and 10, if the message processing device 30 is set to the same network segment A as instance A, network segment A becomes a base that plays a role like a host, and other network segments Even if the message processing device 30 is not installed in the remote location, it is possible to jointly develop software at a remote location without worrying about gaps between instances of development environments or protocols. Furthermore, as shown in FIG. 8, even if the message processing device 30 is installed in network segment B where there is no instance, network segment B becomes a base that plays a role like a host, resulting in the same effect as above. is obtained.

<A-4. Effect＞
The message processing device 30 of the first embodiment is provided in each of a plurality of instances A and B that develop or operate the same software and have a unique development management system 10, and is configured to send and receive messages between the plurality of instances A and B. Controls the sending and receiving of messages by the message sending and receiving device. The message processing device 30 refers to the message management unit 31 that receives messages from the message transmitting/receiving device, the instance information in which the instance of the message transmission source is associated with the instance that has access rights to the message, and the message management unit 31 receives the message from the message transmitting and receiving device. The message distribution unit 35 determines a target instance from a plurality of instances based on the instance of the source of the message received by the message management unit 31 and instance information, and distributes the message received by the message management unit 31 to the target instance. Therefore, according to the message processing device 30, when the access control rules for transmission messages are different for each instance, the message can be distributed to an appropriate instance according to the access control rules of the transmission source instance.

The message processing device 30 also acquires message processing information in which the type of the message is associated with the content of the process to be executed when receiving the message, from the target instance, and the message processing information that associates the type of the message with the content of the process to be executed when receiving the message, and The job generation unit 36 may also include a job generation unit 36 that generates a job to be executed by the target instance based on the message processing information and sends it to the target instance. In this case, according to the message processing device 30, when the processing rules for received messages are different for each instance, it is possible to instruct an appropriate job according to the processing rules of the target instance.

Furthermore, the message processing device 30 may further include an instance DB 34 that is an instance information storage unit that stores instance information. In this case, the message processing device 30 can easily add or delete instance information.

The message processing system 101 of the first embodiment includes a message transmitting/receiving device that is provided in each of a plurality of instances that develop or operate the same software and has a unique development management system, and that transmits and receives messages between the plurality of instances. A message processing device 30 that controls message transmission and reception by the message transmission and reception device is provided. Each message transmitting/receiving device includes an event detection unit 15 that detects an event that occurs in the development management system of its own instance, a message generation unit 16 that generates a message based on the event detected by the event detection unit 15, and a message generation unit 16. The message transmitting unit 17 transmits the generated message to the message processing device. The message processing device 30 refers to the message management unit 31 that receives the message from the message transmitting unit 17 of the message transmitting/receiving device, and the instance information that associates the instance of the message transmission source with the instance that has the right to access the message. A message distribution unit 35 determines a target instance from a plurality of instances based on the instance of the source of the message received by the message management unit 31 and instance information, and distributes the message received by the message management unit 31 to the target instance. and. Each message transmitting/receiving device has a message receiving section 18 that receives a message from the message distribution section 35 of the message processing device 30, and executes a job on the development management system 10 of its own instance according to the message received by the message receiving section 18. A job execution unit 19 is provided. Therefore, according to the message processing system 101, when the access control rules for messages sent from the own instance are different for each instance, the message can be delivered to the appropriate instance according to the access control rules of the source instance. can.

Further, in the message processing system 101, the message processing device 30 acquires message processing information in which the type of the message is associated with the content of the process to be executed when receiving the message from the target instance, and the message distribution unit distributes the message processing information. The job execution unit 19 includes a job generation unit 36 that generates a job to be executed by the target instance based on the message type and message processing information and sends it to the target instance. The message transmitting/receiving device receives a job from and executes the job on the development management system 10 of its own instance, and includes a message processing DB that is a message processing information storage unit that stores message processing information. Therefore, according to the message processing system 101, when the processing rules for received messages are different for each instance, an appropriate job can be executed in the target instance according to the processing rules of the target instance.

Note that within the scope of the invention, the embodiments of the present invention can be freely combined, and the embodiments can be modified or omitted as appropriate.

10 Development management system, 11 Chat system, 12 Task management system, 13 Build management system, 14 Version control system, 15 Event detection unit, 16 Message generation unit, 17 Message transmission unit, 18 Message reception unit, 19 Job execution unit, 20 Message processing DB, 30 Message processing device, 31 Message management unit, 32 Message DB, 33 ID generation unit, 34 Instance DB, 35 Message distribution unit, 36 Job generation unit, 40 Operator, 41 Message transmission device, 42 Message reception device , 81 processing circuit, 82 processor, 83 memory, 101 message processing system.

Claims (6)

A message processing device that controls the sending and receiving of messages of a message sending and receiving device that is installed in each of a plurality of instances that develop or operate the same software and has a unique development management system, and that sends and receives messages between the plurality of instances. There it is,
a message management unit that receives the message from the message transmitting/receiving device;
The instance of the sender of the message and the instance information received by the message management unit refer to the instance information in which the instance of the sender of the message is associated with the instance that has access rights to the message. a message distribution unit that determines a target instance from the plurality of instances based on the above, and distributes the message received by the message management unit to the target instance,
Message processing device. Message processing information in which the type of the message is associated with the content of the process to be executed when receiving the message is acquired from the target instance, and the type of the message and the message processing information to be distributed by the message distribution unit are obtained. further comprising a job generation unit that generates a job to be executed by the target instance based on the above, and transmits the job to the target instance.
Message processing device according to claim 1. further comprising an instance information storage unit that stores the instance information;
A message processing device according to claim 1 or claim 2. a message transmitting/receiving device that is provided in each of a plurality of instances that develop or operate the same software and has a unique development management system, and that transmits and receives messages between the plurality of instances;
a message processing device that controls transmission and reception of the message by the message transmission and reception device;
A message processing system comprising:
Each of the message transmitting and receiving devices includes:
an event detection unit that detects an event occurring in the development management system of its own instance;
a message generation unit that generates the message based on the event detected by the event detection unit;
a message transmitting unit that transmits the message generated by the message generating unit to the message processing device,
The message processing device includes:
a message management unit that receives the message from the message transmission unit of the message transmission/reception device;
The instance of the sender of the message and the instance information received by the message management unit refer to the instance information in which the instance of the sender of the message is associated with the instance that has access rights to the message. a message distribution unit that determines a target instance from the plurality of instances based on the above, and distributes the message received by the message management unit to the target instance,
Each of the message transmitting and receiving devices includes:
a message receiving unit that receives the message from the message distribution unit of the message processing device;
a job execution unit that executes a job on the development management system of its own instance according to the message received by the message reception unit;
Message processing system. The message processing device includes:
Message processing information in which the type of the message is associated with the content of the process to be executed when receiving the message is acquired from the target instance, and the type of the message and the message processing information to be distributed by the message distribution unit are obtained. further comprising a job generation unit that generates the job to be executed by the target instance based on the above, and transmits the job to the target instance,
The job execution unit receives the job from the job generation unit of the message processing device, and executes the job on the development management system of its own instance,
The message transmitting/receiving device further includes a message processing information storage unit that stores the message processing information.
5. The message processing system according to claim 4. computer,
A message processing device that controls the sending and receiving of messages of a message sending and receiving device that is installed in each of a plurality of instances that develop or operate the same software and has a unique development management system, and that sends and receives messages between the plurality of instances. There it is,
a message management unit that receives the message from the message transmitting/receiving device;
The instance of the sender of the message and the instance information received by the message management unit refer to the instance information in which the instance of the sender of the message is associated with the instance that has access rights to the message. to operate as a message distribution unit that determines a target instance from the plurality of instances based on the above, and distributes the message received by the message management unit to the target instance;
Message processing program.

Images