System and method to determine defect risks in software solutions

US9558464B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9558464-B2
Application numberUS-201414160954-A
CountryUS
Kind codeB2
Filing dateJan 22, 2014
Priority dateSep 11, 2009
Publication dateJan 31, 2017
Grant dateJan 31, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method is implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions. The programming instructions are operable to receive one or more risk factors, receive one or more contexts, identify one or more context relationships and associate the one or more contexts with the one or more risk factors. Additionally, the programming instructions are operable to map the one or more risk factors for an associated context to a software defect related risk consequence to determine a risk model and execute a risk-based testing based on the risk model to determine a defect related risk evaluation for a software development project.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: determining risk factor definitions, the determining comprising: collecting risk factors that influence an injection of defects during a software development process; defining how to measure each of the collected risk factors; creating a list of risk factors from the collected risk factors; analyzing the list of risk factors; and re-factoring the list of risk factors, wherein the re-factoring the list of risk factors comprises determining, by at least one computer device, a relationship between each of the collected risk factors, wherein measuring each of the collected risk factors is performed by subdividing each of the collected risk factors, including a connection complexity factor, into sub-factors, and calculating a risk factor value for the collected risk factors from sub-factor values, the connection complexity factor being broken down into at least four orthogonal sub-factors comprising cross platform, data transformation, third-party integration and new protocol. 2. The method of claim 1 , wherein the determining the risk factor definitions is performed automatically via an expert system. 3. The method of claim 1 , wherein the collecting the risk factors includes using a literature survey that can influence the injection of the defects during the software development process. 4. The method of claim 1 , wherein the determining the relationship between each of the collected risk factors comprises identifying ambiguities or overlaps between each of the collected risk factors. 5. The method of claim 1 , wherein the re-factoring the list of risk factors comprises making the list of risk factors orthogonal based on the analyzing. 6. The method of claim 5 , wherein the orthogonal list of risk factors requires that every two risk factors are independent of each other. 7. The method of claim 1 , wherein the determining the relationship between each of the collected risk factors comprises determining at least one of three different relationships between each of the collected risk factors, the three different relationships includes: (i) subset, (ii) equivalent, and (iii) overlap. 8. The method of claim 1 , wherein the re-factoring further comprises at least one of deleting, merging, splitting, and adding at least one of the collected risk factors from the list of risk factors. 9. A system comprising: a CPU, a computer readable memory and a computer readable storage medium; program instructions to collect risk factors; program instructions to measure each of the collected risk factors by subdividing each of the collected risk factors, including a connection complexity factor, into sub-factors, and calculating a risk factor value for the collected risk factors from sub-factor values, the connection complexity factor being broken down into at least four orthogonal sub-factors comprising cross platform, data transformation, third-party integration and new protocol; program instructions to create a list of the collected risk factors; program instructions to analyze the list of the collected risk factors; program instructions to determine a relationship between the collected risk factors in the list of collected risk factors; and program instructions to re-factor the list of the collected risk factors, wherein the program instructions are stored on the computer readable storage medium for execution by the CPU via the computer readable memory. 10. The system of claim 9 , wherein the program instructions to determine the risk factor value subdivides each of the collected risk factors into sub-factors and calculates the risk factor value for the collected risk factors from sub-factor values. 11. The system of claim 10 , wherein the program instructions to re-factor the list of the collected risk factors comprises making the list of risk factors orthogonal based on the analyzing. 12. The system of claim 11 , wherein the orthogonal list of risk factors requires that every two risk factors are independent of each other.

Assignees

Inventors

Classifications

  • Reliability or availability analysis · CPC title

  • Risk analysis of enterprise or organisation activities · CPC title

  • Requirements analysis; Specification techniques · CPC title

  • Performance evaluation by tracing or monitoring · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9558464B2 cover?
A method is implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions. The programming instructions are operable to receive one or more risk factors, receive one or more contexts, identify one or more context relationships and associate the one or more contexts with the one or more risk factor…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification G06Q10/0635. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jan 31 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).