# US 2014/0208305 A1 · Automatically Identifying Criticality of Software Fixes Specific to a Client Deployment and Usage of Software Product

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0208305 A1
- Document ID: US20140208305A1
- Status: Published application
- Kind: A1
- Application number: 13/747,627
- Filed: 2013-01-23
- Published: 2014-07-24
- Earliest claimed: 2013-01-23
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Salil Ahuja; Amod V. Bhise; Pankuj Chachra
- Web page: https://patentgrep.com/patent/US20140208305A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A mechanism is provided in a data processing system for identifying criticality of a software fix. The mechanism obtains a criticality description associated with a software fix of a software product deployed on the data processing system. The mechanism determines a criticality value of the software fix based on computing environment of the data processing system and customer usage of the software product on the data processing system.

## Claims

### Claim 1

A method, in a data processing system, for identifying criticality of a software fix, the method comprising:
obtaining a criticality description associated with a software fix of a software product deployed on the data processing system; and
determining, by the data processing system, a criticality value of the software fix based on computing environment of the data processing system and customer usage of the software product on the data processing system.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining whether to apply the software fix to the software product on the data processing system based on the criticality value.

### Claim 3 (depends on 2)

The method of claim 2, wherein determining whether to apply the software fix comprises:
comparing the criticality value to a threshold; and
responsive to the criticality value being greater than the threshold, applying the software fix.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
monitoring and recording customer usage of the software product on the data processing system.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
responsive to determining customer usage of the software product has changed, determining a new criticality value of the software fix based on the computing environment of the data processing system and the customer usage of the software product.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
determining whether to apply the software fix to the software product on the data processing system based on the new criticality value.

### Claim 7 (depends on 1)

The method of claim 1, wherein obtaining the criticality description associated with the software fix comprises obtaining the criticality description from metadata associated with the software fix.

### Claim 8

A computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, causes the computing device to:
obtain a criticality description associated with a software fix of a software product deployed on the computing device; and
determine, by the computing device, a criticality value of the software fix based on computing environment of the computing device and customer usage of the software product on the computing device.

### Claim 9 (depends on 8)

The computer program product of claim 8, wherein the computer readable program further causes the computing device to:
determine whether to apply the software fix to the software product on the computing device based on the criticality value.

### Claim 10 (depends on 9)

The computer program product of claim 9, wherein determining whether to apply the software fix comprises:
comparing the criticality value to a threshold; and
responsive to the criticality value being greater than the threshold, applying the software fix.

### Claim 11 (depends on 8)

The computer program product of claim 8, wherein the computer readable program further causes the computing device to:
monitor and record customer usage of the software product on the computing device.

### Claim 12 (depends on 11)

The computer program product of claim 11, wherein the computer readable program further causes the computing device to:
responsive to determining customer usage of the software product has changed, determine a new criticality value of the software fix based on the computing environment of the computing device and the customer usage of the software product.

### Claim 13 (depends on 12)

The computer program product of claim 12, wherein the computer readable program further causes the computing device to:
determine whether to apply the software fix to the software product on the computing device based on the new criticality value.

### Claim 14 (depends on 8)

The computer program product of claim 8, wherein obtaining the criticality description associated with the software fix comprises obtaining the criticality description from metadata associated with the software fix.

### Claim 15 (depends on 8)

The computer program product of claim 8, wherein the computer readable program is stored in a computer readable storage medium in a data processing system and wherein the computer readable program was downloaded over a network from a remote data processing system.

### Claim 16 (depends on 8)

The computer program product of claim 8, wherein the computer readable program is stored in a computer readable storage medium in a server data processing system and wherein the computer readable program is downloaded over a network to a remote data processing system for use in a computer readable storage medium with the remote system.

### Claim 17

An apparatus, comprising:
a processor; and
a memory coupled to the processor, wherein the memory comprises instructions which, when executed by the processor, cause the processor to:
obtain a criticality description associated with a software fix of a software product deployed on a data processing system; and
determine, by the computing device, a criticality value of the software fix based on computing environment of the data processing system and customer usage of the software product on the data processing system.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein determining whether to apply the software fix comprises:
comparing the criticality value to a threshold; and
responsive to the criticality value being greater than the threshold, applying the software fix.

### Claim 19 (depends on 17)

The apparatus of claim 17, wherein the instructions further cause the processor to:
monitor and record customer usage of the software product on the computing device;
responsive to determining customer usage of the software product has changed, determine a new criticality value of the software fix based on the computing environment of the data processing system and the customer usage of the software product; and
determine whether to apply the software fix to the software product on the data processing system based on the new criticality value.

### Claim 20 (depends on 17)

The apparatus of claim 17, wherein obtaining the criticality description associated with the software fix comprises obtaining the criticality description from metadata associated with the software fix.
