JP2006146504A - Downtime management system, downtime monitoring terminal, and downtime management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide compensations so as to meet the dissatisfaction of purchasers in the event of a new bug in software. <P>SOLUTION: The downtime management system includes one or two or more monitored terminals 10 that execute software, a downtime monitoring terminal 20 that is connected to the monitored terminals to monitor the process of the software executed by the monitored terminals; upon detecting that the process of the software has stopped, starts measuring downtime while collecting bug information from the monitored terminals and sending this bug information to a software company's terminal; and, after receiving a correction program corresponding to the bug information from the software company's terminal, ends measuring the downtime and sends the measured downtime to the software company's terminal, and a software company's terminal 30 that receives the bug information from the downtime monitoring terminal; sends the correction program corresponding to the bug information to the downtime monitoring terminal; and receives the downtime from the downtime monitoring terminal. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to user compensation for software defects, and in particular, a downtime management system in which a software development company compensates a user according to downtime by measuring software downtime, and downtime The present invention relates to a monitoring terminal and a downtime management program.

Traditionally, software development companies have provided correction programs for new bugs in software that they have developed in the form of after-sales services, and have provided implicit compensation.
However, the software buyers have not been given a clear compensation standard for the time (downtime) when the software was unavailable, and they were not responsible for compensation.

By the way, there are various factors in the occurrence of a new bug in software, so it is difficult to ask the developer for the responsibility. However, as long as software is provided in the form of software usage rights, the software is buggy. It is inevitable that the software development company will have some responsibility for the time unavailable due to However, to date, no process has been established for software development companies to be responsible.
In addition, when a new bug occurred in software developed by a software development company, the downtime caused by the bug was not measured, and there were no special restrictions that encouraged the rapid creation of correction programs.

Because of these issues, software buyers are unable to know when a new bug is found in the software and when a fix for it will be provided, and the after-sales service of each software development company is good. I couldn't judge what was wrong.
As a result, the purchaser of software suffered a great disadvantage when purchasing new software.

Here, in order to positively collect new bug information discovered by the user without delay, a bug information reduction system that makes it possible to determine the importance of the bug information and to pay the corresponding price has been proposed. (For example, refer to Patent Document 1).
According to this conventional bug information reduction system, when a software purchaser finds a bug, he / she reports it to the software development company, and according to the novelty, importance and usefulness of the bug. It is said that the physical and time damage suffered by the appearance of bugs can be compensated, and the dissatisfaction can be resolved, and at the same time the reliability of software development companies can be improved. Yes.

Japanese Patent Laid-Open No. 2002-024414

However, although this conventional bug information reduction system can compensate the reporter of new bugs in software, other users who suffered damage in the same way using the software, It does not allow for proper compensation.
When a new bug occurs in the software, it is desirable to provide appropriate compensation by the software development company to all purchasers who could not use the software due to the bug, but according to the conventional system, Compensation is given only to the earliest reporters, and it cannot be said that the original responsibility of the software development company is sufficiently feasible.

That is, it is desirable that the software development company compensates all purchasers of software for the time when the software cannot be used.
In addition, the conventional bug information reduction system calculates the value based on the importance and usefulness of the new bug. In addition to the fact that the importance of the bug is based on the circumstances of the developer, Since judgments are made by humans, there is a high possibility that the judgments will vary, and it has not been possible to provide compensation in proportion to actual dissatisfaction with the software purchasers.

  The present invention is considered in view of the above circumstances, and it is possible to perform compensation proportional to each buyer's dissatisfaction by measuring system downtime and performing compensation proportional to the time. An object is to provide a downtime management system, a downtime monitoring terminal, and a downtime management program.

  In order to achieve the above object, a downtime management system of the present invention is a downtime management system for measuring downtime of software executed in a monitored terminal by the downtime monitoring terminal, and is one or two for executing the software. The above monitored terminal and the software process connected to the monitored terminal and executed on the monitored terminal are monitored, and when the stop of the software process is detected, the downtime measurement is started and the monitored terminal After collecting bug information from the software company, sending the bug information to the software company terminal, receiving the correction program corresponding to the bug information from the software company terminal, ending the downtime measurement and measuring the measured downtime to the software company Bug information from downtime monitoring terminal and downtime monitoring terminal sent to terminal Received and transmits the fix for the bugs to downtime monitoring terminal is configured to have a software company terminal receiving the downtime from downtime monitoring terminal.

If the downtime management system has such a configuration, the downtime monitoring terminal can measure the downtime of the software in one or more monitored terminals and transmit it to the software company terminal. This software downtime represents the time that the purchaser of the software was originally able to use but was unable to use it due to a bug in the software.
Therefore, by measuring this downtime, it becomes possible to clarify the responsibility of the developer for the disadvantage suffered by the purchaser.
In addition, the software development company can grasp the disadvantages suffered by the purchaser of the software more specifically by downtime. Compensation can be performed.

  In addition, about the concrete measuring method of downtime, it can be set as various methods. For example, from the time when the downtime monitoring terminal detects that the process has stopped at the monitored terminal to the time when the downtime monitoring terminal receives the correction program from the software company terminal, It can be downtime.

The downtime management system of the present invention is configured such that when the software company terminal receives downtime from the downtime monitoring terminal, the compensation request for each monitored terminal corresponding to the downtime is transmitted to the financial institution terminal. .
If the downtime management system is configured in this way, if downtime occurs in the software being executed in the monitored terminal, a compensation request corresponding to the downtime for each monitored terminal is issued from the software company terminal to the financial institution. It can be automatically sent to the terminal.
For this reason, the software development company can automatically make a compensation request to a financial institution for a software purchaser who has been disadvantaged due to downtime, and can quickly compensate for the disadvantage.

  Also, the downtime management system of the present invention receives the name and downtime of the correction program transmitted from the software company terminal, and provides the bug information for providing the name and downtime of the correction program so that they can be accessed via a communication line. It has a configuration having a terminal.

If the downtime management system is configured in this way, the relationship between the downtime of the monitored terminal detected by the downtime monitoring terminal and each software correction program is disclosed on the Web by the bug information terminal. can do.
In other words, the software development company can provide the software purchaser with a standard for software reliability (the number of occurrences of bugs and a list of downtime), and the reliability can be improved.
In addition, by disclosing downtime and the like on the Web in this way, it is possible to prompt the software development company to create correction programs quickly and reduce the bug occurrence rate, and to reduce system downtime. Is also possible.

In the downtime management system of the present invention, the monitored terminal receives the correction program from the downtime monitoring terminal or the bug information terminal.
If the downtime management system is configured as described above, the monitored terminal can receive the correction program created by the software development company via the downtime monitoring terminal, and can also be released on the web by the bug information terminal. It is possible to download the modified program and update the corresponding software.

  The downtime monitoring terminal of the present invention is connected to one or more monitored terminals, measures the downtime of software executed in the monitored terminal, and transmits the measured downtime to the software company terminal. A process monitoring unit that is a downtime monitoring terminal that monitors a software process executed on a monitored terminal and detects the stop of the software process, and the process monitoring unit detects the stop of the software process. When the stop of the software process is detected by the downtime measuring means that starts the downtime measurement and ends the downtime measurement when the correction program is received from the software company terminal and the process monitoring means, Bug information collection means for collecting bug information from monitored terminals, and collected bug information Was transmitted to the software company terminal receives a fix for the software company terminal Bugs, a configuration equipped with a transmission and reception means for transmitting the down time that is measured in the soft company terminal.

  In the downtime monitoring terminal of the present invention, when the transmission / reception means receives the correction program from the software company terminal, the transmission / reception means transmits the correction program to the monitored terminal.

  Also, the downtime management program of the present invention causes a downtime monitoring terminal connected to one or more monitored terminals to measure the downtime of software executed in the monitored terminal, and the downtime is a software company terminal. Downtime management program to be transmitted to the process, the downtime monitoring terminal monitoring the software process executed on the monitored terminal and detecting the stop of the software process, the process monitoring means When a process stoppage is detected, downtime measurement is started, and when a correction program is received from a software company terminal, downtime measurement means and process monitoring means terminate the downtime measurement. When a stop is detected, a bug is detected from the monitored terminal Bug information collecting means for collecting information, sending / receiving means for sending the collected bug information to the software company terminal, receiving a correction program corresponding to the bug information from the software company terminal, and sending the measured downtime to the software company terminal As a configuration to function as.

  In the downtime management program of the present invention, the transmission / reception means transmits the correction program to the monitored terminal when receiving the correction program from the software company terminal.

If the downtime monitoring terminal and the downtime management program are configured as described above, the downtime monitoring terminal can measure the downtime of the system related to the software executed on the monitored terminal. By transmitting the information to the terminal, the software development company can specifically grasp the disadvantage of the software purchaser.
In addition, the downtime monitoring terminal can transmit the correction program for the software received from the software company terminal to the monitored terminal that has caused the system down by the program, so that the monitored terminal can be recovered quickly. Can do.

  According to the present invention, the monitored terminal is monitored by the downtime monitoring terminal, and the downtime of the software is measured and transmitted to the software company terminal, so that compensation in proportion to the downtime can be performed. It is possible to realize compensation proportional to the dissatisfaction of

Hereinafter, a preferred embodiment of a downtime management system according to the present invention will be described with reference to the drawings.
In addition, the downtime management system of this invention shown to the following embodiment is operate | moved by the computer controlled by the program. The CPU of the computer sends a command to each component of the computer based on the program, and predetermined processing required for the operation of the downtime monitoring terminal, such as process monitoring processing, downtime measurement processing, bug information collection processing, etc. To do. Thus, each process and operation in the downtime management system of the present invention can be realized by specific means in which the program and the computer cooperate.

The program is stored in advance in a recording medium such as a ROM and a RAM, and is executed by causing the computer to read the program from a recording medium mounted on the computer. For example, the program may be read by the computer via a communication line.
Further, the recording medium for storing the program can be constituted by, for example, a semiconductor memory, a magnetic disk, an optical disk, or any other recording means that can be read by any computer.

[First embodiment]
First, the structure of 1st embodiment of this invention is demonstrated with reference to FIG.1 and FIG.2. FIG. 1 is a block diagram showing the configuration of the downtime management system of the present embodiment. FIG. 2 is a block diagram showing a configuration of a downtime monitoring terminal in the downtime management system of the system.
As shown in FIG. 1, the downtime management system of this embodiment includes a monitored terminal 10 (10-1 to 10-n), a downtime monitoring terminal 20, a software development company terminal (software company terminal) 30, and a known one. It has a bug DB 31, a bug information terminal 40, a financial institution terminal 50, and a communication line 60.

  The monitored terminal 10 is an information processing system configured by an information processing device such as one or a plurality of workstations, servers, personal computers, etc., on which software to be monitored is installed. Moreover, as this monitored terminal 10, as shown to the figure, it can also be set as one or two or more information processing systems.

The downtime monitoring terminal 20 is an information processing apparatus such as a personal computer having a function of constantly monitoring software processes executed on the monitored terminal 10.
As shown in FIG. 2, the downtime monitoring terminal 20 includes a process monitoring unit 21, a downtime measuring unit 22, a bug information collecting unit 23, and a transmission / reception unit 24, and performs processing executed by each unit. A terminal with a built-in shell or program.
The process monitoring means 21 constantly monitors the software process executed on the monitored terminal 10 and detects the stop of the process.
When the process monitoring unit 21 detects that the process on the monitored terminal 10 is stopped, the downtime measuring unit 22 measures the stop time of the process.

When the process monitoring unit 21 detects that the process on the monitored terminal 10 is stopped, the bug information collecting unit 23 receives bug related information (core, dump, stack trace, debug information, etc.) from the monitored terminal 10. These are collectively referred to as bug information).
The transmission / reception unit 24 transmits the downtime measured by the downtime measurement unit 22 and the bug information extracted by the bug information collection unit 23 to the software company terminal 30.

The software company terminal 30 is an information processing apparatus such as a personal computer, receives bug information collected by the downtime monitoring terminal 20, and develops software for the software down in the monitored terminal 10 based on the bug information. This is a terminal that transmits a correction program created by a company to the downtime monitoring terminal 20.
The software company terminal 30 receives the downtime corresponding to the correction program from the downtime monitoring terminal 20 and transmits the downtime and the name of the correction program to the bug information terminal 50. Then, in accordance with this downtime, compensation is performed in accordance with a predetermined agreement from the software development company to the software purchaser.

In the present embodiment, the software company terminal 30 transmits a compensation request to the purchaser of the software in an amount proportional to the software downtime, for example, to the financial institution terminal 50, and the financial institution compensates for the downtime. It is assumed that the transfer is made.
The method for calculating the compensation amount corresponding to the downtime is not particularly limited. For example, the software company terminal 30 converts the downtime into a compensation amount based on a predetermined calculation formula, and includes this compensation amount in the compensation request. It can be transmitted to the financial institution terminal 50.

  Also, the transfer destination specifying method is not particularly limited. For example, a customer DB that stores the identification information of the monitored terminal 10 or the transfer destination information for each piece of identification information of the software purchaser in the software company terminal 30 in advance. The downtime monitoring terminal 20 transmits the identification information of the monitored terminal 10 to the software company terminal 30 together with the downtime, and the software company terminal 30 specifies the transfer destination information from the customer DB based on the identification information etc. Then, the transfer destination information can be included in the compensation request and transmitted to the financial institution terminal 50.

The known bug DB 31 is a database in which bug information already known by the software development company is stored. The software development company inquires whether or not the bug information received from the downtime monitoring terminal 20 by the software company terminal 30 is registered in the known bug DB 31 to easily determine whether the bug is a new bug or a known bug. Judgment can be made. If the bug is a new bug, a correction program is created by the software development company.
It should be noted that the already created correction program is registered in the known bug DB 31 in correspondence with the known bug information, and when the bug information received from the downtime monitoring terminal 20 is a known bug, the corresponding correction program is displayed. It is also preferable to enable automatic transmission to the downtime monitoring terminal 20.

The bug information terminal 40 is an information processing apparatus such as a personal computer used by a software development company, stores the downtime received from the software company terminal 30 and the name of the correction program, and publishes it on the Web.
The financial institution terminal 50 is an information processing apparatus in an institution that performs a transfer of compensation equivalent to software downtime.

As the communication line 60, any publicly known public line, commercial line, or dedicated line known in the art can be used. The downtime monitoring terminal 20, the software company terminal 30, the bug information terminal 40, and the financial institution terminal 50 can be configured by the same or separate communication lines.
Further, the communication line 60 is a line that can be connected between the downtime monitoring terminal 20, the software company terminal 30, the bug information terminal 40, and the financial institution terminal 50 by radio or wire, for example, a public line network, It can be constituted by a private line network, an Internet line network and an intranet network.

Next, a processing procedure in the downtime management system of this embodiment will be described with reference to FIG.
This figure is an operation procedure diagram showing a processing procedure in the downtime management system of the present embodiment. In the figure, a portion displayed by a dotted line is a portion manually performed by a software developer, and is displayed in the same format in the following embodiments.

  Further, in the following processing procedure, when transmitting / receiving various data exchanged between terminals, for example, bug information, downtime, correction program, etc., which software is associated with which monitored terminal 10 simultaneously. By transmitting and receiving together information for identifying such as, it is possible to appropriately associate the corresponding bug information, downtime, correction program, etc. with each other. Such identification information is not particularly limited and will be omitted in the following description.

First, the software process executed in the monitored terminal 10 is a process monitoring shell (ps (process status) command (process display command in UNIX (registered trademark)) or process monitoring software) on the downtime monitoring terminal 20. Are constantly monitored (step 10).
Next, when the process is stopped in the monitored terminal 10 (step 11), the downtime monitoring terminal 20 detects the stop of the process in the monitored terminal 10 (step 12). It should be noted that the downtime monitoring terminal 20 does not detect the stop of the process for those that are not caused by a software bug such as stop by forced termination based on the type of process stop in the monitored terminal 10.

When the downtime monitoring terminal 20 detects the stop of the process, the downtime monitoring terminal 20 starts measuring the downtime and activates the information collection shell, so that bug information (core, dump, stack trace, debug information, etc.) is received from the monitored terminal 10. ) Is collected (step 13).
When the collection of the bug information is completed, the downtime monitoring terminal 20 transmits this bug information to the software company terminal 30 (step 14).

  The software development company queries the known bug DB 31 based on the bug information received by the software company terminal 30 to determine whether the bug that caused the process stop in the monitored terminal 10 is new or known. Judgment. If it is determined that the bug is a new bug, a correction program for correcting the bug is created (step 15) and input to the software company terminal 30. If it is determined that the bug is a known bug, the already created correction program is input to the software company terminal 30.

The software company terminal 30 transmits the input correction program to the downtime monitoring terminal 20 (step 16).
When the downtime monitoring terminal 20 receives the correction program, the downtime monitoring terminal 20 transmits the correction program to the monitored terminal 10, updates and restarts the software related to the stopped process, and confirms the normal operation of the stopped process. The system downtime measurement due to the stop of the process is terminated (step 17).

Then, the downtime monitoring terminal 20 transmits the measured downtime together with the identification information of the monitored terminal 10 to the software company terminal 30 (step 18).
The software company terminal 30 calculates a corresponding compensation amount based on the received downtime. Further, the customer DB or the like is searched based on the identification information of the monitored terminal 10 and the transfer destination information of the purchaser of the corresponding software is acquired. Then, a compensation request including the compensation amount and the transfer destination information is transmitted to the financial institution terminal 50 (step 19).
On the other hand, in the financial institution, the transfer to the software purchaser is executed and the compensation is completed (step 20).

Further, the software company terminal 30 transmits the downtime corresponding to the name of the correction program to the bug information terminal 40 (step 21).
Then, the bug information terminal 40 publishes the received downtime corresponding to the name of the correction program on the Web (step 22). FIG. 4 shows an example of the name of the correction program and the downtime disclosed by the bug information terminal 40 in this way.
It should be noted that the order of compensation requests for financial institutions in steps 19 and 20 and the disclosure of the names of correction programs and the like in steps 21 and 22 may be interchanged.

As described above, according to the downtime management system of the present embodiment, it is possible to measure the software downtime in one or more monitored terminals and transmit it to the software company terminal.
For this reason, the software development company can grasp the disadvantages suffered by the purchaser of the software more specifically by downtime. Compensation can be performed.

In addition, the relationship between the system downtime in the monitored terminal detected by the downtime monitoring terminal and each software correction program is disclosed on the Web by the bug information terminal, so that the software purchaser can It is possible to provide a standard for the reliability of the system, and it is possible to improve the reliability.
Furthermore, by releasing downtime etc. on the Web in this way, it is possible to prompt the software development company to create correction programs quickly and to reduce the bug occurrence rate, and to reduce system downtime. Is also possible.

[Second Embodiment]
Next, a second embodiment of the present invention will be described with reference to FIG. This figure is a block diagram showing the configuration of the downtime management system of the present embodiment.
This embodiment is different from the first embodiment in that the monitored terminal 10 receives a correction program from a website provided by the bug information terminal 40. About another point, it is the same as that of 1st embodiment.

That is, as shown in FIG. 5, the monitored terminal 10 in this embodiment is not directly connected to the downtime monitoring terminal 20 but is connected to the downtime monitoring terminal 20 via the communication line 60.
Then, the downtime monitoring terminal 20 monitors the process of the monitored terminal 10 via the communication line 60, and as in the case of the first embodiment, as shown in FIG. Measurement, collection of bug information, transmission to the software company terminal 30, and reception of the correction program from the software company terminal 30 (steps 30 to 36).

In the present embodiment, the software company terminal 30 transmits the correction program to the bug information terminal 40 in step 36. Thereby, the bug information terminal 40 can publish the correction program on the Web.
Next, the downtime monitoring terminal 20 transmits the name of the correction program to the monitored terminal 10 and ends the downtime measurement (step 37).
Then, the measured downtime is transmitted to the software company terminal 30 (step 38), and the software company terminal 30 transmits this downtime to the bug information terminal 40 (step 39). Thereby, the bug information terminal 40 can publish the correction program and the corresponding downtime on the Web (step 40).

The monitored terminal 10 can restore the system by accessing the website provided by the bug information terminal 40, downloading the correction program, updating the software having the bug, and restarting. (Step 41).
On the other hand, as in the first embodiment, the software company terminal 30 transmits a compensation request corresponding to the downtime to the financial institution terminal 50 (step 42), and the financial institution terminal 50 side compensates the purchaser. (Step 43).

  As described above, according to the downtime management system of the present embodiment, the downtime monitoring terminal 20 can monitor the monitored terminal 10 via the communication line 60 and measure the software downtime. The general user who purchased the software can be compensated by the downtime management system of the present invention.

It goes without saying that the present invention is not limited to the above embodiment, and that various modifications can be made within the scope of the present invention.
For example, by combining the first embodiment and the second embodiment and having the configuration shown in FIG. 5, the monitored terminal 10 can receive the correction program from the monitoring terminal 20 and the bug information terminal 40 places the correction program on the Web. It is possible to make changes as appropriate, for example, by making the monitored terminal 10 receive a correction program from the bug information terminal 40.

  The present invention can be used to monitor a downtime of an in-house system by providing a downtime monitoring terminal in an in-house LAN, and can be widely used via a communication line by providing a downtime monitoring terminal on the software development company side. It can also be used to monitor system downtime at a general user's terminal and can be used to implement compensation for these downtimes.

It is a block diagram which shows the structure of the downtime management system of 1st embodiment of this invention. It is a block diagram which shows the structure of the downtime monitoring terminal in the downtime management system of 1st embodiment of this invention. It is an operation | movement procedure figure which shows the process sequence in the downtime management system of 1st embodiment of this invention. It is a figure which shows the example of disclosure of the correction program name and downtime in the downtime management system of 1st embodiment of this invention. It is a block diagram which shows the structure of the downtime management system of 2nd embodiment of this invention. It is an operation | movement procedure figure which shows the process sequence in the downtime management system of 2nd embodiment of this invention.

Explanation of symbols

10 (10-1 to 10-n) Monitored terminal 20 Downtime monitoring terminal 21 Process monitoring means 22 Downtime measuring means 23 Bug information collecting means 24 Transmission / reception means 30 Software company terminal 31 Known bug DB
40 Bug information terminal 50 Financial institution terminal 60 Communication line

Claims (8)

A downtime management system for measuring downtime of software executed in a monitored terminal by the downtime monitoring terminal,
One or more of the monitored terminals executing software;
The software process connected to the monitored terminal and executed on the monitored terminal is monitored, and when the stop of the software process is detected, downtime measurement is started and a bug is detected from the monitored terminal. After collecting information and sending the bug information to the software company terminal and receiving the correction program corresponding to the bug information from the software company terminal, the measurement of the downtime is terminated and the measured downtime is The downtime monitoring terminal to be transmitted to the software company terminal;
The software company terminal that receives the bug information from the downtime monitoring terminal, transmits a correction program corresponding to the bug information to the downtime monitoring terminal, and receives the downtime from the downtime monitoring terminal; A downtime management system characterized by comprising:   2. The down of claim 1, wherein when the software company terminal receives downtime from the downtime monitoring terminal, the software company terminal transmits a compensation request for each monitored terminal corresponding to the downtime to the financial institution terminal. Time management system. A bug information terminal that receives the name of the correction program and the downtime transmitted from the software company terminal, and provides the name of the correction program and the downtime in an accessible manner via a communication line. The downtime management system according to claim 1 or 2.   The downtime management system according to claim 3, wherein the monitored terminal receives a correction program from the downtime monitoring terminal or the bug information terminal. A downtime monitoring terminal connected to one or more monitored terminals, measuring a downtime of software executed in the monitored terminal, and transmitting the measured downtime to the software company terminal,
Process monitoring means for monitoring the software process executed in the monitored terminal and detecting the stop of the software process;
When the process monitoring means detects that the process of the software is stopped, it starts downtime measurement, and when a correction program is received from the software company terminal, downtime measurement means ends the downtime measurement;
When the process monitoring means detects that the software process is stopped, bug information collecting means for collecting bug information from the monitored terminal;
Transmitting / receiving means for transmitting the collected bug information to a software company terminal, receiving a correction program corresponding to the bug information from the software company terminal, and transmitting the measured downtime to the software company terminal; A downtime monitoring terminal characterized by that.   6. The downtime monitoring terminal according to claim 5, wherein when the correction program is received from the software company terminal, the transmission / reception means transmits the correction program to the monitored terminal. A downtime management program for causing a downtime monitoring terminal connected to one or more monitored terminals to measure a downtime of software executed in the monitored terminal and transmitting the downtime to a software company terminal. ,
The downtime monitoring terminal,
Process monitoring means for monitoring the software process executed in the monitored terminal and detecting the stop of the software process;
Downtime measuring means for starting downtime measurement when the process monitoring means detects that the process of the software is stopped, and ending the downtime measurement when a correction program is received from the software company terminal;
A bug information collecting means for collecting bug information from the monitored terminal when the process monitoring means detects that the software process is stopped;
Transmitting the collected bug information to a software company terminal, receiving a correction program corresponding to the bug information from the software company terminal, and functioning as transmission / reception means for transmitting the measured downtime to the software company terminal. A featured downtime management program.   8. The downtime management program according to claim 7, wherein when the correction program is received from the software company terminal, the transmission / reception means transmits the correction program to the monitored terminal.

Images