JP2005025456A - Problem management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a problem management system capable of displaying a list of problems, searching it, and outputting it to an external file by minimum access to a database. <P>SOLUTION: This problem management system is provided with a problem management data holding means 2 holding occurring problems as problem management data, a table creation means 3 creating an index update information table 23 when one of the problem management data is updated, and a table transmission means 4 transmitting the index update information table 23 to another problem management system. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a problem management system, and more particularly to a problem management system that is installed in at least two dispersed areas and cooperates with each other to solve problems that have occurred.
[0002]
[Prior art]
When developing a product such as software, it may be more efficient to develop a load distribution at each site in a plurality of different regions than to develop at one site.
[0003]
In general, for example, at sites that develop large-scale software, problems such as the occurrence of problems that occur there and the progress of problem solving, or the management data for such problems are output to a file. The person is doing. The problem management system described above is constructed for this purpose.
[0004]
Since such a problem management system is built for the above development bases, if multiple development bases are scattered in different regions as described above, the problem management systems are also built for each development base. Must.
[0005]
Then, it is necessary to create a common problem management environment while coordinating between these multiple problem management systems. Otherwise, smooth problem management cannot be performed for the problem manager.
[0006]
Therefore, in the past, the above problem management has been performed in such a way that the problem manager autonomously refers to the problem management system at the development base in each region as appropriate. However, various improvement measures have been proposed so far because the burden imposed on the problem manager is too heavy.
[0007]
The following Patent Documents 1 and 2 are conventional examples of such improvements.
[0008]
[Patent Document 1]
JP 2001-22855 A
[Patent Document 2]
Japanese Patent No. 2762384
[0009]
[Problems to be solved by the invention]
According to the above-mentioned patent document 1 (Japanese Patent Laid-Open No. 2001-22855), “by transferring all the problem occurrence data registered in the problem management system and its solution data to the problem management system at a base in another region. , “I share the same problem management information among all problem management systems”.
[0010]
However, as will become clear from the explanation below, the improvement measures are fundamentally different from the improvement measures according to the present invention such as “displaying a list of problems, searching, outputting to an external file, etc. with minimal access to the database”. Is different.
[0011]
According to the above-mentioned Patent Document 2 (Japanese Patent No. 2762384),
[1] Means to compile issued, analysis, confirmation, etc. for each work group,
[2] Means for judging a related person from the contents of the issuance card and sending the issuance card to the related person by e-mail;
In order to solve this problem, the company has taken measures to automate the distribution of information in problem processing and reduce the time required for information distribution and the burden on product developers.
[0012]
However, as will become clear from the explanation given later, the improvement measures are also fundamental to the improvement measures according to the present invention such as “displaying a list of problems, searching, outputting to an external file, etc. with minimal access to the database”. Is different.
[0013]
Therefore, the present invention is not limited to directly referring to the problem management system installed in each region in product development such as software in a plurality of dispersed regions, and to all of the problem occurrence data and its solution data. To provide a problem management system that makes it possible to display a list of problems, search, output to an external file, etc. with minimal access without transferring to a local problem management system It is the purpose.
[0014]
[Means for Solving the Problems]
FIG. 1 is a basic configuration diagram showing a first aspect of a problem management system according to the present invention.
FIG. 2 is a basic configuration diagram showing a second aspect of the problem management system according to the present invention.
FIG. 3 is a basic configuration diagram showing a third aspect of the problem management system according to the present invention.
[0015]
(I) The first aspect (FIG. 1) relates to a mechanism for transferring problem management data to a problem management system in another area.
(Ii) The second aspect (FIG. 2) relates to a mechanism for a problem manager to search for required problem management data and display a list of the results.
(Iii) The third aspect (FIG. 3) relates to a mechanism for a problem manager to output required problem management data to an external file.
[0016]
(I) First, referring to FIG. 1 (first mode), the main components are a problem management data holding means 2, a table creation means 3, and a table transmission means 4.
[0017]
This system is basically a problem management system that is installed in at least two dispersed areas and cooperates with each other to solve problems that have occurred in each. here,
The problem management data holding means 2 holds a problem that has occurred as problem management data.
The table creation means 3 creates, as an index update information table (update TB) 23, data that should be linked with each other in the distributed areas when any of the above-described problem management data is updated. Is,
The table transmission means 4 transmits the index update information table 23 to the other problem management system.
[0018]
More specifically, the problem management data holding means 2 includes at least an index information table (IND / TB) 21 and a problem information table (information TB) 22 as a problem management data holding table.
[0019]
The index information table 21 includes items for linking to the problem information table 22, items relating to problem occurrence data relating to the problem that has occurred, and items relating to progress data indicating progress toward solving the problem. (See FIG. 6).
[0020]
In addition, the problem information table 22 includes items relating to the countermeasure against the problem that has occurred, and items relating to analysis for the countermeasure, as well as items to be linked with the index information table 21. (See FIG. 7).
[0021]
The problem management system further includes problem occurrence data registration means 1. This is means for connecting to the problem management data holding means 2 and the table creation means 3 described above, and interprets the problem occurrence data relating to the above-mentioned problem that has been input, and the index information table 21 and the problem information. The contents of the information table 22 are updated, and the table creation means 3 for creating the index update information table 23 is activated in accordance with the update.
[0022]
On the other hand, the problem management system also includes a table receiving unit 5 and a table rewriting unit 6.
[0023]
The table receiving means 5 receives the index update information table (23) similarly created in the other problem management system,
The table rewriting means 6 refers to the received index update information table (23) and rewrites the contents of the index update information table 23 included in the problem management data holding means 2.
[0024]
As described above, according to the first aspect, by introducing the index update information table 23 re-edited only to necessary problem management data required by the problem manager, it is possible to minimize the access. It becomes possible to share common problem management information among problem management systems at a plurality of bases.
[0025]
(Ii) Next, referring to FIG. 2 (second mode), the main components are a search condition input means 11, a problem list creation means 12, and a problem list display means 13.
[0026]
This problem management system is basically a system configured according to the first aspect (FIG. 1) as described above, and further includes at least the above-described means 11, 12, and 13. here,
The search condition input means 11 is for inputting the search conditions when searching the data held in the problem management data holding means 2 described above.
The problem list creating means 12 creates a problem according to the inputted search condition as a problem list based on the data held in the problem management data holding means 2.
The problem list display means 13 displays the created problem list to the outside as an output from the problem management system.
[0027]
More specifically, the problem management data holding means 2 has an index information table 21, a problem information table 22, and an index update information table 23 as shown in FIG. The problem list creating means 12 interprets the contents of these tables 21 to 23 and creates the above problem list.
[0028]
In this case, the problem list creating means 12 creates the above problem list as the problem list management table 14, and the problem list display means 13 refers to the problem list management table 14 and performs the above display. can do.
[0029]
As described above, according to the second aspect, when the problem manager wants to search for the required problem management data, the problem management data obtained by merging the problem management data in the problem management system in another area is also obtained. Since the problem list creation means 12 refers to the problem management data holding means 2 to acquire the search data and displays the search data on the problem list display means 13, the problem manager can select a desired problem in the problem management system at all locations. Problem management data can be acquired with minimal access.
[0030]
(Iii) Still referring to FIG. 3 (third mode), the main components are an output condition input means 31 and an external file creation means 32.
[0031]
The present problem management system is basically a system configured according to the first aspect (FIG. 1) as described above, and further includes at least the above means 31 and 32. here,
The output condition input means 31 inputs the file output condition when outputting the data held in the problem management data holding means 2 to the external file 33 outside the problem management system.
The external file creation means 32 creates the external file 33 while referring to the data held in the problem management data holding means 2 according to the file output conditions.
[0032]
More preferably, it further includes an external file information collection unit 34 that cooperates with the external file creation unit 32 described above. This external file information collecting means 34 obtains, for example, more detailed data held in the problem management data holding means (2) in the other problem management system, and this is used as the external file in the external file creation means 32 described above. It is made to use for preparation of 33 further.
[0033]
In this case, it is desirable to further include external file merging means 35. The means 35 combines the output from the external file creation means 32 and the more detailed output obtained from the other problem management system via the external file information collection means 34 into the external file 33. Supply.
[0034]
As described above, according to the third aspect, when the problem manager wants to move the required problem management data to the external file 33, the problem management data in the problem management system in another region is also merged. The required problem management data can be acquired from the problem management data with minimal access and stored in the external file 33.
[0035]
DETAILED DESCRIPTION OF THE INVENTION
Specific examples of the problem management system according to the first, second, and third aspects of the present invention will be described below.
[0036]
FIG. 4 is a diagram (part 1) showing a specific example of the problem management system according to the first mode (FIG. 1).
FIG. 5 is the same figure (the 2).
[0037]
Hereinafter, FIG. 4 and FIG. 5 will be described.
[0038]
Reference numeral 100 in FIG. 4 indicates a problem management system installed in the base 1, and 200 in FIG. 5 indicates a problem management system installed in the base 2 in another area. The base 1 and the base 2 are connected by some kind of communication network NW, for example, a LAN or a public network.
[0039]
The problem management systems 100 and 200 have the same configuration, but the system 100 mainly represents registration and transmission processing of problem management data, and the system 200 mainly represents reception processing thereof. Yes.
[0040]
In the problem management system 100, the generated problem data is input (registered) from the terminal PC1 such as a personal computer to the problem occurrence data registration means 110 (corresponding to 1 in FIG. 1). Further, it is held as problem management data in the problem management data holding means 2 (see FIG. 1).
[0041]
The problem management data includes an index information table 151 (21 in FIG. 1) and a problem information table 152 (22 in FIG. 1), and further includes an index update information table. In this index information table 151, problem registration data or progress data, for example, a problem registration number, a server ID of a problem management system in which a problem is registered, a problem title, a problem occurrence date, a problem countermeasure status, and the like are registered. The problem information table 152 registers problem countermeasure data or problem analysis data, for example, problem countermeasure date, problem countermeasure content, problem resolution date, problem resolution content, and the like. These tables 151 and 152 are shown in the figure.
[0042]
FIG. 6 is a diagram showing a specific example of the contents of the index information table 151.
FIG. 7 is a diagram showing a specific example of the contents of the problem information table 152.
[0043]
The problem occurrence data registration means 110 in FIG. 4 will be described in more detail. The means 110 interprets the problem occurrence data input from the terminal PC1 and updates the contents of the index information table 151 and the problem information table 152.
[0044]
Further, the problem occurrence data registration unit 110 completes the writing of the problem management data into the index information table 151 and the problem information table 152, and at the same time, the index update information table creation unit 120 (3 in FIG. 1) uses the index update information. A table 153 (23 in FIG. 1) is created.
[0045]
When the creation of the index update information table 153 is completed, the index update information table creation unit 120 notifies the index update information table transmission / reception unit 140 (here, corresponding to 4 in FIG. 1) of the completion of creation.
[0046]
The index update information table transmission / reception unit 140 that has received the notification of the completion of the interpretation interprets the server ID-server correspondence table 154 and performs the index update information table 153 for all the defined servers (problem management systems). Send.
[0047]
The server ID-server correspondence table 154 defines a server ID of a problem management system installed in another area, for example, a number for identifying the problem management system 100 or the problem management system 200, and a server address, for example, an IP address. Has been. An example is shown in the figure.
[0048]
FIG. 8 is a diagram showing a specific example of the contents of the server ID-server correspondence table 154.
[0049]
Hereinafter, the reception operation of the problem management system 200 installed in the base 2 corresponding to the server ID 2 defined in the server ID-server correspondence table 154 will be described with reference to FIG.
[0050]
The index update information table transmission / reception means 240 (corresponding to 5 in FIG. 1) in the problem management system 200 that has received the index update information table 153 transmitted from the problem management system 100 side as described above is the table 153. Simultaneously with the completion of reception, the index update information table rewriting means 230 (6 in FIG. 1) is notified of the completion of reception.
[0051]
Upon receiving the notification of completion, the index update information table rewriting means 230 stores the received index update information table 253 ′ as the index update information table 253 in the problem management system 200. An example of this table 253 is shown in the figure.
[0052]
FIG. 9 is a diagram showing a specific example of the contents of the index update information table 253 (153).
[0053]
Note that this means in FIG. 4 corresponding to the index update information table rewriting means 230 in FIG. 5 corresponding to the index update information table creation means 120 of FIG. Similarly, the means 210 (1) in FIG. 5 corresponds to the means 110 (1) in FIG.
[0054]
FIG. 10 is a diagram showing a specific example of the problem management system according to the second mode (FIG. 2).
[0055]
The problem management system 200 shown in FIG. 10 has the function of the problem management system described with reference to FIGS.
[0056]
Further, the contents of the index update information table 153 received from the problem management system 100 described with reference to FIG. 4 are stored as the index update information table 253.
[0057]
In the problem management system 200 of FIG. 10, the search condition input means 250 (11 in FIG. 2) is activated from the terminal PC2 such as a personal computer, and allows the user to arbitrarily select the search condition. This search condition input means 250 notifies the problem list creation means 260 (12 in FIG. 2) of a problem list creation request in accordance with the search conditions selected by the user from the PC 2.
[0058]
Upon receiving the notification of the creation request, the problem list creation unit 260 interprets the index information table 251 and the index update information table 253 described above, and creates the problem list management table 255 (14 in FIG. 2). When the creation of the problem list management table 255 is completed, the problem list creation unit 260 notifies the problem list display unit 270 (13 in FIG. 2) of the completion.
[0059]
The problem list display means 270 that has received the notification of completion displays the problem list as a search result on the display of the terminal PC 2 while referring to the problem list table 255.
[0060]
FIG. 11 is a diagram (part 1) showing a specific example of the problem management system according to the third mode (FIG. 3).
FIG. 12 is the same figure (the 2).
[0061]
The problem management system 200 shown in FIG. 11 has the function of the problem management system described with reference to FIGS.
[0062]
The contents of the index update information table 153 received from the problem management system 100 described with reference to FIG. 4 are stored as the index update information table 253.
[0063]
In the problem management system 200 of FIG. 11, the file output condition input means 280 (31 in FIG. 3) is activated from the terminal PC2 such as a personal computer, and the user arbitrarily sets the file output conditions to the external file 258 (33 in FIG. 3). Allows you to choose.
[0064]
The file output condition input means 280 creates the file output condition table 257 according to the above file output conditions selected by the user. At the same time, the external file creation means 291 (33 in FIG. 3) is notified of the external file creation request. This table 257 is shown in the figure.
[0065]
FIG. 13 is a diagram showing a specific example of the file output condition table 257.
[0066]
The external file creation means 291 that has received the creation request notification interprets the file output condition table 257, the index information table 251 and the problem information table 252 described above, and creates the file output management table 256. This table 256 is shown in the figure.
[0067]
FIG. 14 is a diagram showing a specific example of the file output management table 256. The same applies to the similar file output management tables 256 ′ and 256 ″ and the table 156.
[0068]
Next, the external file creation means 291 interprets the index update information table 253 and the server ID / server correspondence table 254 (FIG. 8), and sends the server ID / server correspondence to the external file information collection means 292 (34 in FIG. 3). An external file transmission request is made to the problem management system 100 (FIG. 12) defined in the table 254.
[0069]
The external file information collection unit 292 (34) that has received the transmission request notifies the problem management system 100 of FIG. 12 of the external file transmission request with the contents of the file output condition table 257.
[0070]
The following shows the transmission / reception operation of the file output management table in the problem management system 100 installed at the site 1 defined in the server ID-server correspondence table 254.
[0071]
The external file information collection unit 192 of the problem management system 100 that has received a transmission request to an external file from the problem management system 200 (FIG. 11) notifies the external file creation unit 191 of the transmission request. Upon receiving this notification, the external file creation means 191 interprets the contents of the file output condition table 257, the index information table 151 within itself, and the problem information table 152, and creates the file output management table 156 (FIG. 14). create.
[0072]
At the same time as the creation of the file output management table 156 is completed, the external file creation unit 191 notifies the external file information collection unit 192 of the completion. The external file information collection unit 192 that has received the completion notification transmits the contents of the file output management table 156 to the problem management system 200 side in FIG.
[0073]
Thus, the problem management system 200 of FIG. 11 that has once received the contents of the file output management table 156 transmitted from the problem management system 100 of FIG. 12 in the table 256 ″ has its own external file information collection means 292 ( In 34), simultaneously with the completion of the reception, the external file creation means 291 (32) is notified of the reception completion.
[0074]
Receiving this completion notification, the external file creation means 291 stores the contents of the file output management table 156 received from the problem management system 100 side as a file output management table 256 ′ in the problem management system 200. Simultaneously with the completion of storage in the file output management table 256 ′, the external file creation unit 291 (32) notifies the external file output unit 295 of the completion of the storage.
[0075]
The external file output unit 295 that has received the notification of the completion of storage refers to the file output management table 256 and the file output management table 256 ′, and stores the external file 258 (33) in a location specified by the user. External file 258 is shown in the figure.
[0076]
FIG. 15 is a diagram showing an example of the contents of the external file 258.
[0077]
By constructing the external file 258 of this figure as, for example, a CSV (Comma Separated Value) file and providing it outside the problem management system, other problem managers can summarize the problem management status in a graph, for example. Can be easily performed.
[0078]
The embodiment of the present invention described above is as follows.
[0079]
(Appendix 1) A problem management system that is installed in at least two dispersed areas and cooperates with each other to solve problems that have occurred.
Problem management data holding means for holding the occurred problem as problem management data;
When any of the problem management data is updated, table creation means for creating, as an index update information table, data that should be coordinated between the distributed regions among the update data;
Table transmission means for transmitting the index update information table to the other problem management system;
A problem management system comprising:
[0080]
(Supplementary Note 2) The problem management data holding means has at least an index information table and a problem information table as the problem management data holding table,
The index information table includes items relating to the problem information table, items relating to the problem occurrence data relating to the problem that has occurred, and items relating to progress data indicating progress toward solving the problem. Including
The problem information table includes an item for linking with the index information table, an item related to the problem countermeasure data related to the countermeasure for the problem that has occurred, and an item related to analysis for the countermeasure. The problem management system according to Supplementary Note 1.
[0081]
(Additional remark 3) It is a means connected to the said problem management data holding means and the said table preparation means respectively, Comprising: The problem occurrence data which concerns on the said generated problem which were input, the said index information table and problem information The problem management system according to claim 2, further comprising a problem occurrence data registration unit that updates each content of the table and activates the table creation unit that creates the index update information table in accordance with the update. .
[0082]
(Appendix 4) Table receiving means for receiving an index update information table similarly created in the other problem management system;
Table rewriting means for rewriting the contents of the index update information table of the problem management data holding means with reference to the received index update information table;
The problem management system according to appendix 1, further comprising:
[0083]
(Supplementary Note 5) When searching for data held in the problem management data holding means, search condition input means for inputting the search condition;
A problem list creating means for creating a problem according to the input search condition as a problem list based on the data held in the problem management data holding means;
A problem list display means for displaying the created problem list externally as an output from the problem management system;
The problem management system according to appendix 1, further comprising:
[0084]
(Supplementary Note 6) The problem management data holding means includes an index information table, a problem information table, and an index update information table, and the problem list creating means interprets the contents of these tables and The problem management system according to appendix 5, wherein a list is created.
[0085]
(Additional remark 7) The said problem list preparation means produces the said problem list as a problem list management table, The said problem list display means performs said display with reference to this problem list management table 6. The problem management system according to 6.
[0086]
(Appendix 8) Output condition input means for inputting the file output condition when outputting the data held in the problem management data holding means to an external file outside the problem management system;
External file creation means for creating the external file while referring to the data held in the problem management data holding means according to the file output condition;
The problem management system according to appendix 1, further comprising:
[0087]
(Additional remark 9) The external file information collection means cooperated with the said external file creation means is further provided,
The external file information collecting means acquires data held in the problem management data holding means in the other problem management system, and further supplies this to the creation of the external file in the external file creation means The problem management system according to appendix 8.
[0088]
(Supplementary Note 10) An external file that supplies both the output from the external file creation means and the output obtained from the other problem management system via the external file information collection means to the external file. The problem management system according to appendix 9, further comprising merging means.
[0089]
【The invention's effect】
By applying the present invention described above to a problem management system, in development in a distributed area, the partner system can be used to directly reference all problem occurrence data and solution data without directly referring to the problem management system installed in each area. The problem manager can grasp the problem occurrence status or progress status, output the problem management data to a file, etc. Furthermore, since access to the database at each site can be kept to a minimum, the server load is reduced, and therefore the response to grasping the problem is improved.
[Brief description of the drawings]
FIG. 1 is a basic configuration diagram showing a first aspect of a problem management system according to the present invention.
FIG. 2 is a basic configuration diagram showing a second aspect of the problem management system according to the present invention.
FIG. 3 is a basic configuration diagram showing a third aspect of the problem management system according to the present invention.
FIG. 4 is a diagram (part 1) illustrating a specific example of the problem management system according to the first mode (FIG. 1);
FIG. 5 is a diagram (part 2) illustrating a specific example of the problem management system according to the first mode (FIG. 1);
6 is a diagram showing a specific example of contents of an index information table 151. FIG.
7 is a diagram showing a specific example of the contents of a problem information table 152. FIG.
8 is a diagram showing a specific example of the contents of a server ID-server correspondence table 154. FIG.
FIG. 9 is a diagram showing a specific example of contents of an index update information table 253 (153).
FIG. 10 is a diagram showing a specific example of the problem management system according to the second mode (FIG. 2).
FIG. 11 is a diagram (part 1) illustrating a specific example of a problem management system according to a third mode (FIG. 3);
FIG. 12 is a (second) diagram illustrating a specific example of the problem management system according to the third mode (FIG. 3);
13 is a diagram showing a specific example of a file output condition table 257. FIG.
14 is a diagram showing a specific example of a file output management table 256. FIG.
15 is a diagram showing an example of the contents of an external file 258. FIG.
[Explanation of symbols]
1 ... Problem occurrence data registration means
2 ... Problem management data holding means
3 ... Table creation means
4 ... Table transmission means
5 ... Table receiving means
6 ... Table rewriting means
11 ... Search condition input means
12 ... Question list creation means
13 ... Problem list display means
14 ... Problem list management table
21 ... Index information table
22 ... Problem information table
23 ... Index update information table
31 ... Output condition input means
32 ... External file creation means
33 ... External file
34. External file information collecting means
35 ... External file merging means

Claims (3)

A problem management system that is installed in at least two distributed areas and works with each other to solve problems that occur in each area.
Problem management data holding means for holding the occurred problem as problem management data;
When any of the problem management data is updated, table creation means for creating, as an index update information table, data that should be coordinated between the distributed regions among the update data;
Table transmission means for transmitting the index update information table to the other problem management system;
A problem management system comprising: Search condition input means for inputting the search condition when searching the data held in the problem management data holding means;
A problem list creating means for creating a problem according to the input search condition as a problem list based on the data held in the problem management data holding means;
A problem list display means for displaying the created problem list externally as an output from the problem management system;
The problem management system according to claim 1, further comprising: Output condition input means for inputting the file output condition when outputting the data held in the problem management data holding means to an external file outside the problem management system;
External file creation means for creating the external file while referring to the data held in the problem management data holding means according to the file output condition;
The problem management system according to claim 1, further comprising:

Images