Abstract: A system and method to automatically and continuously update the urgency rating of a backlog item associated with a technical debt item in a software development project are described. The technical debt represents potential additional work or rework associated with current code. The method includes a user defining a plurality of components that comprise the software development project. The method also includes a processor associating the technical debt with one or more components of the plurality of components, and the processor updating the urgency of the backlog item associated with the technical debt according to a function based on a development event associated with at least one of the one or more components.

Abstract: Reverse metadata viewing by multiple parties, in one aspect, determines one or more second users that share one or more concerns of the first user, enable the first user to select said one or more second users. One or more concerns of said selected one or more second users are determined based on metadata information in electronic artifacts associated with said selected one or more second users. The first user is enabled to explore said one or more concerns of said selected one or more second users.

Abstract: A system and method to automatically and continuously update the urgency rating of a backlog item associated with a technical debt item in a software development project are described. The technical debt represents potential additional work or rework associated with current code. The method includes a user defining a plurality of components that comprise the software development project. The method also includes a processor associating the technical debt with one or more components of the plurality of components, and the processor updating the urgency of the backlog item associated with the technical debt according to a function based on a development event associated with at least one of the one or more components.

Abstract: A system and method to automatically and continuously update the urgency rating of a backlog item associated with a technical debt item in a software development project are described. The technical debt represents potential additional work or rework associated with current code. The method includes a user defining a plurality of components that comprise the software development project. The method also includes a processor associating the technical debt with one or more components of the plurality of components, and the processor updating the urgency of the backlog item associated with the technical debt according to a function based on a development event associated with at least one of the one or more components.

Abstract: Incorporating user insights in predicting, diagnosing and remediating problems that threaten on-time delivery of a project may comprise gathering information. The information may be conveyed to one or more users. A user may be allowed to input a new value associated with the project, the new value assessed based on the information and representing an expert assessment of the information. The user may be allowed to also indicate a period of time the user considers the information to be applicable. The new value and the period of time may be incorporated into data used in a prediction algorithm that predicts probability distribution of completion time of the project as the project is progressing.

Abstract: A graphical interface module may provide a set of graphical presentations comprising at least: a Likelihood of Delivery chart showing a probability distribution of predicted delivery dates; a Delivery Date Risk Trend chart showing how the completion time for the project predicted according to the Likelihood of Delivery chart has changed over time; and a Burndown chart that shows at least work-items of planned work for the project. Each of the Likelihood of Delivery chart, the Delivery Date Risk Trend chart, and the Burndown chart has a timeline axis.

Abstract: A user may be allowed to specify a change in one or more parameter data associated with the project, the one or more parameter data used previously to compute a probability distribution of completion time of the project. The probability distribution of completion time of the project may be recomputed based on the change. The recomputed probability distribution of the completion time of the project may be presented. An option to save the recomputed probability distribution may be provided. An option may be provided to specify another change in one or more parameter data associated with the project and repeat the recomputing and the presenting procedures based on another change in one or more parameter data associated with the project.

Abstract: Historic and current development data associated with the project may be gathered. A catalog of patterns, each pattern associated with a data measure and an analysis routine capable of detecting the pattern according to the data measure in a given data set may be obtained. A pattern describes a particular indication in the historical and development data, which arises one or more of, at a discrete point in time or over a period of time. The analysis routine may be applied to the historic and current development data. A notification may be issued responsive to identifying the pattern in the historic and current development data. The applying and the issuing may be performed for each pattern in the catalog of patterns.

Abstract: A task effort estimator may determine a probability distribution of an estimated effort needed to complete unfinished tasks in a project based on one or more of a set of completed tasks belonging to a project and attributes associated with the completed tasks belonging to the project, a set of completed tasks not belonging to the project and attributes associated with the completed tasks not belonging to the project, or the combination of both. A project completion predictor may determine a probability distribution of completion time for the project based on the probability distribution of an estimated effort needed to complete the unfinished tasks in the project, and one or more resource and scheduling constraints associated with the project.

Abstract: A method (which can be computer implemented) for inferring whether at least a first relationship exists between at least first and second entities includes the steps of applying a first assessor to obtain a first confidence level pertaining to putative existence of said at least first relationship between said at least first and second entities, applying a second assessor to obtain a second confidence level pertaining to putative existence of said at least first relationship between said at least first and second entities, and combining said first and second confidence levels to obtain an overall inference whether said at least first relationship exists between said at least first and second entities.

Abstract: Reverse metadata viewing by multiple parties, in one aspect, determines one or more second users that share one or more concerns of the first user, enable the first user to select said one or more second users. One or more concerns of said selected one or more second users are determined based on metadata information in electronic artifacts associated with said selected one or more second users. The first user is enabled to explore said one or more concerns of said selected one or more second users.

Abstract: Systems and methods are provided to produce natural language interpretations of analytic operations in an automated manner, by associating with each analytic procedure a set of parameters that determine the interpretation of the resulting analysis.

Abstract: Software systems and methods for governance are presented supporting governance solution specification and enactment including assessing, defining, implementing deployment, and executing of the governance solution.

Abstract: A method, information processing system and computer readable medium for assessing risk in a software development project. The method includes receiving software project data for assessing risks in a software development project and identifying a plurality of focus areas for analysis. The method further includes defining a set of analysis tasks for each focus area and creating one or more rule sets for each analysis task, each rule set comprising one or more rules including software project data. The method further includes evaluating each rule set against the software project data summarizing results of evaluating each rule set corresponding to an analysis task. The method further includes providing a risk assessment value for each analysis task using the results of the summarizing element.

Abstract: Systems and methods are provided to produce natural language interpretations of analytic operations in an automated manner, by associating with each analytic procedure a set of parameters that determine the interpretation of the resulting analysis.

Abstract: A method (which can be computer implemented) for inferring whether at least a first relationship exists between at least first and second entities includes the steps of applying a first assessor to obtain a first confidence level pertaining to putative existence of said at least first relationship between said at least first and second entities, applying a second assessor to obtain a second confidence level pertaining to putative existence of said at least first relationship between said at least first and second entities, and combining said first and second confidence levels to obtain an overall inference whether said at least first relationship exists between said at least first and second entities.

Abstract: A method and system for automatically generating a test case for object-oriented software includes providing a model of the object-oriented software, determining a test state for the object-oriented software, and determining a sequence of test steps for the object-oriented software based upon the test state.

Abstract: A method, information processing system and computer readable medium for assessing risk in a software development project. The method includes receiving software project data for assessing risks in a software development project and identifying a plurality of focus areas for analysis. The method further includes defining a set of analysis tasks for each focus area and creating one or more rule sets for each analysis task, each rule set comprising one or more rules including software project data. The method further includes evaluating each rule set against the software project data summarizing results of evaluating each rule set corresponding to an analysis task. The method further includes providing a risk assessment value for each analysis task using the results of the summarizing element.