The progress management apparatus 3 and the progress management DB 31 are conventionally utilized, and the details of them are omitted. However, for example, data as shown in
Incidentally, although not shown, data concerning a name or type of the utilized package program, a hardware configuration in a component level, and a name or type of the Operating System (OS) may be stored in the progress management DB 31.
Moreover, the retracement processing apparatus 5 has a similar case extractor 51 that extracts data appropriate for causing the user to carry out the retracement (also called a similar case) from a retracement DB 53, and a retracement data generating processor 52 that obtains necessary task data from the progress management apparatus 3 or the user terminal, transmits data extracted by the similar case extractor 51 as an interface with the user, and registers, as the interface with the user, an issue/problem, a solution/improvement plan and the like, which are received from the user terminal, into the retracement DB 53.
For example, data as shown in
Next, a processing of the retracement processing apparatus 5 will be explained by using
Next, the retracement data generating processor 52 outputs the obtained task data to the similar case extractor 51, and the similar case extractor 51 carries out a first similar case search processing based on the task data (step S3). The first similar case search processing will be explained by using
First, the similar case extractor 51 identifies one unprocessed case from the retracement DB 53 (step S31). Then, it initializes a similarity s to 0 (step S33). Then, it compares the type of business in the task data with the type of business in the identified case (step S35). When they coincides each other (step S37: Yes route), it increments the similarity s by 1 as the similarity of the type of business is 1 (step S39). Then, the processing shifts to step S41.
When the types of business do not coincide each other (step S37: No route), or after the step S39, it compares a level of the development scale in the task data with a level of the development scale in the identified case (step S41). For example, a level (also called a stage) equal to or less than 100 man-months, a level greater than 100 man-months and less than 1000 man-months, and a level equal to or greater than 1000 man-months are classified, and it is judged whether or not the levels are identical. When the levels of the development levels are identical (step S43: Yes route), it increments the similarity s by 1 as the similarity of the development scale is 1 (step S45). Then, the processing shifts to step S47.
When the levels of the development scale are not identical each other (step S43: No route), or after the step S45, it compares a phase section in the task data with a phase section in the identified case (step S47). For example, the phase is classified into a “pre” section, “after” section, and “maintenance” section, and it is judged whether or not the sections are identical each other. When the phase sections are identical each other (step S49: Yes route), it increments the similarity s by 1 as the similarity of the phase is 1 (step S51). Then, the processing shifts to step S53.
When the phase sections are not identical each other (step S49: No route), or after the step S51, it compares a level of the delay in the task data with a level of the delay in the identified case (step S53). First, it calculates the number of delay days that is a difference between the schedule (i.e. plan) and the actual result in the task data, and calculates the number of delay days that is a difference between the schedule (i.e. plan) and the actual result in the identified case, and stores them into a storage device such as a main memory. Then, the number of delay days are classified into a level of 3 days or less in the delay, a level of 4 days to 9 days in the delay, and a level of 10 days or more, and it is judged whether or not the levels of the delay are identical each other. When the levels of the delay are identical (step S55: Yes route), it increments the similarity s by 1 as the similarity of the delay is 1 (step S57). Then, the processing shifts to a processing of
Next, it compares a utilizing package program in the task data with a utilizing package program in the identified case (step S59). When the utilizing package programs are identical (step S61: Yes route), it increments the similarity s by 1 as a similarity of the utilizing package program is 1 (step S63). Then, the processing shifts to step S65.
When the utilizing package programs are not identical each other (step S61: No route), or after the step S63, it compares the hardware configuration in the task data with the hardware configuration in the identified case in the component level (step S65) For example, it judges whether or not the types of the CPU are identical each other, whether or not the types of the hard disk are identical each other, and the like. Then, it calculates an identity rate s′ of the components as a similarity in the hardware configuration by dividing the number of identical components by the total number of components, and stores the similarity s′ into the storage device such as a main memory (step S67). Then, it update the similarity s by s=s+s′ (step S69).
Furthermore, it compares the OS in the task data with the OS in the identified case (step S71). When the OSs are identical (step S73: Yes route), it increments the similarity s by 1 as the similarity of the OS is 1 (step S75). Then, the processing shifts to step S77.
When the OSs are not identical each other (step S73: No route) or after the step S75, it stores the similarity s into the storage device such as a main memory in association with the case ID (step S77). Then, it judges whether or not all of the cases in the retracement DB 53 have been processed (step S79). When there is an unprocessed case, the processing returns to the step S31. On the other hand, when all of the cases in the retracement DB 53 have been processed, it sorts the cases based on the similarity s in descending order (step S81). Then, the processing returns to the original processing.
For example, data as shown in
Incidentally, when, in
By carrying out such a processing, it becomes possible to extract cases judged as being similar in the first stage from a list as shown in
For example, the similar case extractor 51 outputs the list as shown in
Then, the retracement data generating processor 52 narrows the cases to top predetermined-number cases from the list as shown in
The user terminal A receives the first input page data from the retracement processing apparatus 5, and displays the first input page on the display device. For example, a screen as shown in
The retracement data generating processor 52 of the retracement processing apparatus 5 receives data concerning the problem/issue from the user terminal A (step S8), and stores the data into the storage device such as a main memory. Then, it output the received data to the similar case extractor 51.
The similar case extractor 51 accepts the data from the retracement data generating processor 52, and carries out a second similar case search processing (step S9). This second similar case search processing will be explained by using
First, the similar case extractor 51 divides a sentence or sentences of the problem/issue that is the received data into words, and stores them into the storage device such as a main memory (step S91). Then, it identifies one unprocessed case in the retracement DB 53 (step S93). Incidentally, it is possible to simplify the processing, for example, by identifying one unprocessed case in the top 20, for example, of the list as shown in
Next, it obtains a sentence or sentences of the problem/issue of the identified unprocessed case from the retracement DB 53, divides the sentence or sentences into words, and stores them into the storage device such as a main memory (step S95). Then, it calculates a TF-IDF value for each word with respect to each of the task to be processed and the identified case, generates a vector p of the task to be processed and a vector q of the identified case based on the calculated TF-IDF values, calculates, as a similarity of the problem/issue, a cosine v (=(inner-product of p and q)/|p|/|q|. The value of the cosine is from 0 to 1.) of the vectors p and q, and stores the similarity of the problem/issue into the storage device such as a main memory (step S97).
After that, it calculates, as a new similarity s, a sum (s+v) of the similarity s, which has been calculated for the identified case, and the cosine v, and stores the sum into the list as shown in
Thus, as for the past cases, while considering the data of the problem/issue into account, the similarity is calculated. Incidentally, Although, in the second similar case search processing, the result of the first similar case search processing is used to omit the first similar case search processing itself, the second similar case search processing may be carried out in addition to the first similar case search processing, or in addition to the first similar case search processing in which thresholds such as the level and the section are changed.
For example, the similar case extractor 51 outputs the list as shown in
Returning to the explanation of
The user terminal A receives the second input page data from the retracement processing apparatus 5, and displays the second input page on the display device. For example, when “any requirement is not presented from the customer” is inputted in the input column 801 of the screen in
Here, while the user A refers to the “past cases”, he or she inputs the solution/improvement plan (e.g. “make a propose”) into the input column 901, and clicks the input button 902 or the narrow button 903 to instruct the user terminal A to transmit the input data to the retracement processing apparatus 5. The user A accepts the input from the user A, and transmits the data concerning the solution/improvement plan according to the instruction to the retracement processing apparatus 5.
The retracement data generating processor 52 of the retracement processing apparatus 5 receives the data concerning the solution/improvement plan from the user terminal A (step S14), and stores the data into the storage device such as a main memory. Then, it outputs the received data to the similar case extractor 51.
Then, the similar case extractor 51 receives the data from the retracement data generating processor 52, and carries out a third similar case search processing (step S15). This third similar case search processing will be explained by using
First, the similar case extractor 51 divides a sentence or sentences of the solution/improvement plan that is the received data into words, and stores them into the storage device such as a main memory (step S111). Then, it identifies one unprocessed case in the retracement DB 53 (step S113). Incidentally, it is possible to simplify the processing, for example, by identifying one unprocessed case in the top 20, for example, of the list as shown in
Next, it obtains a sentence or sentences of the solution/improvement plan of the identified unprocessed case from the retracement DB 53, divides the sentence or sentences into words, and stores them into the storage device such as a main memory (step S115). Then, it calculates a TF-IDF value for each word with respect to each of the task to be processed and the identified case, generates a vector p of the task to be processed and a vector q of the identified case based on the calculated TF-IDF values, calculates, as a similarity of the solution/improvement plan, a cosine w (=(inner-product of p and q)/|p|/|q|. The value of the cosine is from 0 to 1.) of the vectors p and q, and stores the similarity of the solution/improvement plan into the storage device such as a main memory (step S117).
After that, it calculates, as a new similarity s, a sum (s+w) of the similarity s, which has been calculated for the identified case, and the cosine w, and stores the sum into the list as shown in
Thus, as for the past cases, while considering the data of the solution/improvement plan into account, the similarity is calculated. Incidentally, although, in the third similar case search processing, the result of the first similar case search processing and the second similar case search processing is used to omit the first and second similar case search processings themselves, the third similar case search processing may be carried out in addition to the first and the second similar case search processing, or in addition to the first similar case search processing and the second similar case search processing in which thresholds such as the level and the section are changed.
For example, the similar case extractor 51 outputs the list as shown in
The retracement data generating processor 52 narrows the cases to the top predetermined-number cases from the list as shown in
The retracement data generating processor 52 judges whether the input button 902 on the screen shown in
When the narrowing is instructed (step S131: No route), the retracement data generating processor 52 generates third input page data by using the result of the third similar case search processing and the input data (data relating to the problem/issue, and data relating to the solution/improvement plan), and transmits the third input page data to the user terminal A (step S133).
The user terminal A receives the third input page data from the retracement processing apparatus 5, and displays it on the display device. For example, when an input “propose from us” is carried out and the narrow button 903 is clicked, a screen as shown in
While referring to the narrowed “past cases”, the user A can change the input content. Then, he or she clicks the input button 1302 or the narrow button 1303 to instruct the user terminal A to transmit the input data to the retracement processing apparatus 5. The user terminal A accepts the input from the user A, and transmits the data relating to the solution/improvement plan according to the instruction to the retracement processing apparatus 5. The processing returns to the step S14 of
On the other hand, when the input is instructed (step S131: Yes route), the retracement data generating processor 52 generates confirmation page data by using the result of the third similar case search processing and the input data (the data relating to the problem/issue and the data relating to the solution/improvement plan) and transmits it to the user terminal A (step S135).
The user terminal A receives the confirmation page data from the retracement processing apparatus 5, and displays it on the display device. For example, a screen as shown in
The retracement data generating processor 52 of the retracement processing apparatus 5 receives the data relating to the instruction from the user terminal A, and judges whether or not the confirmation is instructed or not (step S137). When the correction was instructed (step S137: No route), the processing returns to the step S7 of
On the other hand, when the confirmation instruction was carried out (step S137: Yes route), the retracement data generating processor 52 registers data obtained at the step S1 and the input data received at the steps S8 and S14 into the retracement DB 53 (step S139) That is, one record is added in the data shown in
When the processing as described above is carried out, while retracing the past cases, the user can input the problem/issue and the solution/improvement plan for this task, carry out the reflection and utilize the experience in the subsequent actions. That is, the similar failure can be prevented. In addition, the knowledge, which can be utilized by other users in future, can be accumulated.
As described above, although one embodiment of this invention was described, this invention is not limited to this embodiment. Specifically, the functional block diagram shown in
Moreover, when the solution/improvement plan is inputted, the input button 1401 and the correct button 1402 are provided, and when the problem/issue is inputted, only the input button 801 is provided in
In addition, although the example using TF-IDF was indicated, it is possible to calculate the word-based similarity by using other techniques.
Furthermore, although the application example to the projects of the system development was explained, this invention can be applied to projects of a hardware development or architectural projects. In an example of a storage system development, instead of the type of business, it is necessary to manage data of types such as a drive, controller, cabinet, and firmware. Moreover, in a case of the architectural project, it is necessary to manage data of the type of building such as a residence, office building, and bridge.
Furthermore, according to each case, the definition of the levels, the definition of the sections, the settings of the thresholds are adjusted. Therefore, the aforementioned example is mere an example.
Incidentally, the user terminal, the progress management apparatus 3, and the retracement processing apparatus 5 are computer devices as shown in
Although the present invention has been described with respect to a specific preferred embodiment thereof, various change and modifications may be suggested to one skilled in the art, and it is intended that the present invention encompass such changes and modifications as fall within the scope of the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2006-204277 | Jul 2006 | JP | national |