Transaction prediction modeling method
US-9195693-B2 · Nov 24, 2015 · US
US9600505B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9600505-B2 |
| Application number | US-201414493597-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 23, 2014 |
| Priority date | Sep 23, 2014 |
| Publication date | Mar 21, 2017 |
| Grant date | Mar 21, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system includes reception of a plurality of findings output by runtime checks executed by a plurality of computing systems, determination of whether a first one of the findings is a duplicate of an already-stored finding, storage, in a case it is determined that the first finding is not a duplicate of an already-stored finding, of the first finding in association with a finding identifier, and generation of a message including the finding identifier and information describing a problem associated with the finding.
Opening claim text (preview).
What is claimed is: 1. A system comprising: a computing device comprising: a memory storing processor-executable program code; and a processor to execute the processor-executable program code in order to cause the computing device to: receive a plurality of findings output by runtime checks executed by a plurality of computing systems; determine that a first finding is a duplicate finding of an already-stored finding; determine whether the first finding should be ignored by determining whether the already-stored finding has been at least one of addressed by a correction and assigned to an exception; in response to determining that the already-stored finding has not been addressed by a correction or assigned to an exception, determine whether the already-stored finding was stored within a predetermined period of time with respect to a current time; and in response to determining that the already-stored finding was not stored within the predetermined period of time, determine that the first finding should not be ignored, store the first finding in association with a finding identifier, and generate a message including the finding identifier and information describing a problem associated with the first finding. 2. A system according to claim 1 , wherein the message further comprises information describing a solution to the problem. 3. A system according to claim 1 , wherein the determining whether the already-stored finding has been at least one of addressed by a correction and assigned to an exception comprises determining whether the already-stored finding has been assigned to an exception based on indications of exceptions stored in an exceptions table; and in response to determining that the already-stored finding has not been assigned to an exception, determining that the first finding should not be ignored. 4. A system according to claim 1 , wherein, in response to determining that the already-stored finding has not been at least one of addressed by a correction and assigned to an exception, the determining further comprises determining whether the already-stored finding was stored within a predetermined period of time with respect to a current time; and in response to determining that the already-stored finding was not stored within the predetermined period of time, determining that the first finding should not be ignored. 5. A system according to claim 1 , further comprising: a second computing device comprising: a second memory storing second processor-executable program code; and a second processor to execute the second processor-executable program code in order to cause the second computing device to: receive the message; present the message; receive a first identifier of a code change and a second identifier of a support package including the code change; and store the first identifier and the second identifier in association with the finding identifier. 6. A non-transitory computer-readable medium storing program code, the program code executable by a processor of a computing system to cause the computing system to: receive a plurality of findings output by runtime checks executed by a plurality of computing systems; determine that a first finding is a duplicate finding of an already-stored finding; determine whether the first finding should be ignored by determining whether the already-stored finding has been at least one of addressed by a correction and assigned to an exception; in response to determining that the already-stored finding has not been addressed by a correction or assigned to an exception, determine whether the already-stored finding was stored within a predetermined period of time with respect to a current time; and in response to determining that the already-stored finding was not stored within the predetermined period of time, determine that the first finding should not be ignored, store the first finding in association with a finding identifier, and generate a message including the finding identifier and information describing a problem associated with the first finding. 7. A medium according to claim 6 , wherein the message further comprises information describing a solution to the problem. 8. A medium according to claim 6 , wherein the determining whether the already-stored finding has been at least one of addressed by a correction and assigned to an exception comprises determining whether the already-stored finding has been assigned to an exception based on indications of exceptions stored in an exceptions table; and in response to determining that the already-stored finding has not been assigned to an exception, the computer system determines that the first finding should not be ignored. 9. A medium according to claim 6 , wherein, in response to determining that the already-stored finding has not been at least one of addressed by a correction and assigned to an exception, the method further comprises determining whether the already-stored finding was stored within a predetermined period of time with respect to a current time; and in response to determining that the already-stored finding was not stored within the predetermined period of time, determining that the first finding should not be ignored. 10. A medium according to claim 6 , wherein the program code is further executable by a processor of a computing system to cause the computing system to: receive the message; present the message; receive a first identifier of a code change and a second identifier of a support package including the code change; and store the first identifier and the second identifier in association with the finding identifier. 11. A computer-implemented method comprising: receiving a plurality of findings output by runtime checks executed by a plurality of computing systems; determining that a first finding is a duplicate finding of an already-stored finding; determining whether the first finding should be ignored by determining whether the already-stored finding has been at least one of addressed by a correction and assigned to an exception; in response to determining that the already-stored finding has not been addressed by a correction or assigned to an exception, determine whether the already-stored finding was stored within a predetermined period of time with respect to a current time; and in response to determining that the already-stored finding was not stored within the predetermined period of time, determine that the first finding should not be ignored, store the first finding in association with a finding identifier, and generate a message including the finding identifier and information describing a problem associated with the first finding. 12. A method according to claim 11 , wherein the message further comprises information describing a solution to the problem. 13. A method according to claim 11 , wherein the determining whether the already-stored finding has been at least one of addressed by a correction and assigned to an exception comprises determining whether the already-stored finding has been assigned to an exception based on indications of exceptions stored in an exceptions table; and in response to determining that the already-stored finding has not been assigned to an exception, determining that the first finding should not be ignored. 14. A method according to claim 11 , further comprising: in response to determining that the already-stored finding has not been at least one of addressed by a correction and assigned to an exception, determining whether the already-stored finding was stored within a predetermined period of time with respect to a current
Physics · mapped topic
Program code verification, e.g. Java bytecode verification, proof-carrying code (high-level semantic checks G06F8/43; prevention of errors by analysis, debugging or testing of software G06F11/36) · CPC title
Database tuning (G06F16/2282 takes precedence; database performance monitoring G06F11/3409) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.