Risk-adaptive agile software development

Patent metadata

Field	Value
Publication number	US-2018032929-A1
Application number	US-201615223522-A
Country	US
Kind code	A1
Filing date	Jul 29, 2016
Priority date	Jul 29, 2016
Publication date	Feb 1, 2018
Grant date	—

Abstract

Techniques are disclosed herein for implementing risk-adaptive system development. A model generator generates a displayed system model comprising displayed system components. A cycle generator determines a risk management cycle comprising a multiple risk management phases. The cycle generator generates a displayed risk management interface which includes multiple displayed risk management phases that are selected and sequenced within the displayed risk management interface based, at least in part, on the determined risk management cycle. The cycle generator further generates component objects that each correspond to a respective one within a set of the system components that have been selected for risk analysis. A display device displays each of the component objects within a respective one of the displayed risk management phases.

First claim

What is claimed is:

1 . A method for managing system development, said method comprising:
displaying, in a first user interface, a system model comprising system components; determining a risk management cycle comprising a plurality of risk management phases; displaying, in a risk management interface, risk management phases that are selected and sequenced within the risk management interface based, at least in part, on the determined risk management cycle; generating component objects that each correspond to a respective one within a set of the system components that have been selected for risk analysis; and displaying each of the component objects within a respective one of the displayed risk management phases.

2 . The method of claim 1 , further comprising, in response to a user input selection of one of the component objects, receiving and incorporating text input to be displayed by the selected component object.

3 . The method of claim 1 , further comprising selecting one or more of the management phases to be included in the risk management cycle based, at least in part, on the selected set of system components.

4 . The method of claim 1 , further comprising:
for each of at least two of the risk management phases,
identifying component objects that are associated with the risk management phase; and
for each of the identified component objects, storing risk analysis elements associated with the identified component object within a collection object that uniquely corresponds to the risk management phase.

5 . The method of claim 4 , wherein the risk analysis elements include risk management data entered via a user interface into corresponding component objects.

6 . The method of claim 4 , further comprising, in response to detecting an attempted movement of a first component object from a displayed risk management phase to a second risk management phase:
generating a risk condition query based, at least in part, on a risk analysis rule associated with the first risk management phase; and executing the risk condition query including,
retrieving, from a first collection object corresponding to the first risk management phase, a first set of risk analysis elements associated with the first component object; and
retrieving, from a second collection object corresponding to a risk management phase that precedes the first risk management phase, a second set of risk analysis elements associated with the first component object.

7 . The method of claim 6 , further comprising:
processing the retrieved risk analysis elements in accordance with the risk analysis rule that is associated with the first displayed risk management phase and the preceding displayed risk management phase; identifying a risk condition based, at least in part, on a result of said processing the retrieved risk analysis elements; and implementing a movement rejection action in response to said identifying the risk condition.

8 . The method of claim 7 , wherein the risk analysis rule defines a risk condition that depends on a specified relation between at least one of the risk analysis elements that is associated with the first component object and the first risk management phase and at least one of the risk analysis elements that is associated with the first component object and the preceding risk management phase.

9 . The method of claim 1 , wherein said determining a risk management cycle comprises:
determining risk factors associated with one or more of the set of the system components; and selecting phases to be included based, at least in part, on the determined risk factors.

10 . The method of claim 9 , further comprising:
determining a relation between at least two of the risk factors; and selecting phases to be included in the risk management cycle based, at least in part, on the determined relation between at least two of the risk factors.

11 . The method of claim 10 , wherein said determining a relation between the at least two of the risk factors comprises determining a causal relation between the at least two of the risk factors, said method further comprising sequencing two or more of the selected phases based, at least in part, on the determined causal relation.

12 . One or non-transitory more machine-readable storage media having program code for managing system development stored therein, the program code configured to:
display, in a first user interface, a system model comprising system components; determine a risk management cycle comprising a plurality of risk management phases; display, in a risk management interface, risk management phases that are selected and sequenced within the risk management interface based, at least in part, on the determined risk management cycle; generate component objects that each correspond to a respective one within a set of the system components that have been selected for risk analysis; and display each of the component objects within a respective one of the displayed risk management phases.

13 . The machine-readable storage media of claim 12 , further comprising, in response to a user input selection of one of the component objects, receiving and incorporating text input to be displayed by the selected component object.

14 . The machine-readable storage media of claim 12 , further comprising selecting one or more of the management phases to be included in the risk management cycle based, at least in part, on the selected set of system components.

15 . The machine-readable storage media of claim 12 , further comprising:
for each of at least two of the risk management phases,
identifying component objects that are associated with the risk management phase; and
for each of the identified component objects, storing risk analysis elements associated with the identified component object within a collection object that uniquely corresponds to the risk management phase.

16 . The machine-readable storage media of claim 15 , wherein the risk analysis elements include risk management data entered via a user interface into corresponding component objects.

17 . The machine-readable storage media of claim 15 , further comprising, in response to detecting an attempted movement of a first component object from a displayed risk management phase to a second risk management phase:
generating a risk condition query based, at least in part, on a risk analysis rule associated with the first risk management phase; and executing the risk condition query including,
retrieving, from a first collection object corresponding to the first risk management phase, a first set of risk analysis elements associated with the first component object; and
retrieving, from a second collection object corresponding to a risk management phase that precedes the first risk management phase, a second set of risk analysis elements associated with the first component object.

18 . The machine-readable storage media of claim 17 , further comprising:
processing the retrieved risk analysis elements in accordance with the risk analysis rule that is associated with the first displayed risk management phase and the preceding displayed risk management phase; identifying a risk condition based, at least in part, on a result of said processing the retrieved risk analysis elements; and implementing a movement rejection action in response to said identifying the risk condition.

19 . The machine-readable storage media of claim 18 , wherein the risk analysis rule defines a risk condition that

Assignees

• Ca Inc

Inventors

• Muntes-Mulero Victor
• Matthews Peter Brian
• Gupta Smrati
• Dominiak Jacek

Classifications

• G06Q10/0635 Primary

  Risk analysis of enterprise or organisation activities · CPC title