Abstract:
A method including receiving a plurality of probability distributions corresponding to respective competitive goals, receiving an indication of a comparison goal, mapping the comparison goal to a domain independent comparison statistic characteristic, determining a plurality of statistical values of the probability distributions, receiving a selections of a comparison pattern specifying a designed comparison coordination for corresponding ones of the comparison statistic characteristics, converting the plurality of probability distributions into the designed comparison coordination, and displaying the probability distributions in the designed comparison coordination including values of the comparative statistic characteristics of the probability distributions.
Abstract:
A system and method for integrating entities using a graphic user interface (GUI) to provide user-interactive rule-based matching and difference reconciliation. In one aspect, a system for integrating entities employs a combination of default matching and reconciliation approaches and user tailoring to generate a composite entity from one or more input entities using a set of composition rules. The set of composition rules comprises a combination of default rules, as well as rules that represent user interactions that are performed via a graphical user interface when the user edits a composite result. The rules are captured and then stored persistently when the user requests that the composition be saved, such that the rules may be retrieved during a subsequent editing session associated with the same inputs. If the inputs change, the integration process (as specified by the rules) can automatically handle many changes. It is only when changed elements of the input are, or need to be, subject to specific rules that additional tailoring may be required.
Abstract:
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).
Abstract:
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.
Abstract:
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).
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:
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:
Supporting problem resolution of an organization, in one aspect, may include obtaining operational data associated with the organization, calculating operating metrics based on the operational data, detecting one or more metrics trends based on the calculated operational metrics, identifying one or more relations between the metric trends, and determining one or more SEM patterns from two or more of the calculated operational metrics and metric trends.