International Business Machines Corporation

Peri L Tarr

Tamir Klinger

Peter Kenneth Malkin

Paul Michael Matchen

Mark N Wegman

Evelyn Duesterwald

Murray Robert Cantor

Stanley M Sutton

Harold Leon Ossher

Clay Edwin Williams

Matthew N Kaplan

Vincent Joseph Kruskal

Martin J Hirzel

Jacquelyn Annette Martino

Dharmashankar Subramanian

Brent Tzion Hailpern

David John Piorkowski

Frank J Budinsky

Patrick A Wagstrom

Stanley M Sutton, Jr

William H Harrison

Steven R Dobson

Systems and methods to generate a cognitive model are described. A particular example of a system includes a memory including program code having an application programming interface and a user interface, and a processor configured to access the memory and to execute the program code to generate a cognitive model, to run analysis on the cognitive model to determine a factor that is impacting a performance of the cognitive model, to determine an action based on the factor, to report at least one of the factor and the action to a user, and to use the action to generate a second cognitive model.

Conversational optimization of cognitive models

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.

GUI support for diagnosing and remediating problems that threaten on-time delivery of software and systems

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.

Detecting patterns that increase the risk of late delivery of a software project

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.

Incorporating user insights into predicting, diagnosing and remediating problems that threaten on-time delivery of software and systems

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.

Exploring the impact of changing project parameters on the likely delivery date of a project

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.

System and method for automatically determining relationships between software artifacts using multiple evidence sources

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.

Predicting likelihood of on-time product delivery, diagnosing issues that threaten delivery, and exploration of likely outcome of different solutions

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.

Reverse metadata viewing by multiple parties

A method of software evolution, software evolution system and program product therefor. A context specification handler stores context specifications describing requirements on context-adapted software. A Software Part Semantics Specification (SPSS) handler stores software part semantics specifications. A Software Implementation (SI) handler stores SIs. Behavior History handler stores a history of active software behavior analysis results of monitoring previous versions. A software rendering handler combines software behavior history with context specification, software part semantics specifications and SIs and distributes (and optionally deploys) context-adapted software. A software inspector continuously monitors context behavior of deployed versions and selectively identifies active context-adapted software failing to satisfy context specification for reassembly of a new version(s).

Software development, deployment and evolution system, method and program product

Providing element dossiers may include obtaining records of relationships between elements from all lifecycle phases of interest, and querying and retrieving a list of all elements related to a target element using the relationship records including relationships between intermediary adjacent lifecycle phases. The method also includes determining inferential and correlation based relationships among dynamically changing elements.

Method of providing element dossiers that include elements from nonadjacent lifecycle phases

A system (and method) for identifying concerns includes a specifying device for specifying at least one initial concern, and an identifying device for identifying at least one related concern having a relationship with at least one initial concern.

System and method for identifying concerns

There is provided a method for generating a software module based upon elements from multiple software modules. The method includes the step of extracting a plurality of sets of elements from the multiple software modules based upon at least one extraction criterion. Any elements in the sets that violate at least one correctness and completeness criterion are identified. The violating elements are automatically brought into compliance with the at least one correctness and completeness criterion. A plurality of single software modules is generated, wherein each of the single software modules contains one of the sets of elements. The plurality of single software modules are composed to form a final, single software module. The extracting step may include the steps of: classifying the elements in the multiple software modules according to concerns the elements pertain to; representing the concerns by a multi-dimensional space, wherein each dimension represents a type of concern, each coordinate on a dimension represents a concern of that type, and each point in the space represents an element; and representing the at least one extraction criterion in terms of the multi-dimensional space.

Growing community of inventors

Hawthorne, NY, United States of America

Peri L Tarr