Abstract: A method for performing automatic trace retrieval includes receiving a first and second model for a system or service (S10). The first model includes a first plurality of model artifacts at least partially represented by a first semantic style and the second model includes a second plurality of artifacts at least partially represented by a second semantic style. Training data including one or more correspondences between artifacts of the first plurality of model artifacts and artifacts of the second plurality of artifacts is collected. A semantic transformation table is generated for converting between the first and second semantic styles using the collected training data (S11). The generated semantic transformation table is used in tracing associations between artifacts of the first plurality of artifacts and artifacts of the second plurality of artifacts (S12).

Abstract: A method for generating a computer model representing constraints and desired functions for generating a product or service includes receiving user-selected items including requirements, features, dangers, goals, processes, stakeholders, or objects that are defined by a predetermined meta-model. A data element for each of the selected items received from the user is added to the computer model. A relationship is defined between the data element of the data elements and the defined relationships between the data elements are added to the computer model. The meta-model defines relationships between requirements and features, requirements and dangers, and requirements and goals. A graphical notation library defines a unique descriptive icon for each class of the selected items received from the user.

Abstract: The present invention provides a graphical user interface for presentation, exploration and verification of patient information. In various embodiments, a method is provided for browsing mined patient information. The method includes selecting patient information to view, at least some of the patient information being probabilistic, presenting the selected patient information on a screen, the selected patient information including links to related information. The selected patient information may include elements, factoids, and/or conclusions. The selected patient information may include an element linked to unstructured information. For example, an element linked to a note with highlighted information may be presented. Additionally, the unstructured information may include medical images and waveform information.

Abstract: A system for hazards analysis includes: a memory device for storing a program; a processor in communication with the memory device, the processor operative with the program to: access the memory device to obtain information specifying a system to be analyzed; build functional block diagrams using the information specifying the system to be analyzed; receive user-input hazards analysis elements; and use the functional block diagrams, the user-input hazards analysis elements and tree fault analysis for hazards analysis.

Abstract: A method for modeling requirements of a product includes defining an abstract use case for each feature of said product, hierarchically decomposing each abstract use case until concrete use cases are specified for each feature, depicting every actor who would use the product as communicating with a concrete use case through a boundary, and programmatically extracting requirements from the use case diagram. Programmatically extracting requirements further includes converting use case diagrams into directed acyclic graphs, where each use case corresponds to a node of a graph and each relationship between a pair of use cases is represented by a directed edge between the corresponding pair of nodes in the graph where a directed edge points from a parent node to a child node, converting the directed acyclic graph into a tree, and searching the tree to extract the requirements.

Abstract: A method for extracting requirements of an architectural software model comprises providing a use case model as a directed graph of the architectural software model comprising nodes corresponding to use cases and relations between nodes, and creating, automatically, a tree comprising a root node corresponding to an abstract use case and at least one leaf node corresponding to one of an abstract use case and a concrete use case.

Abstract: A video capture tool includes a video camera for capturing a communication, a computer receiving a video feed of the video camera, wherein a logical structure of the communication is previously input to the computer as computer readable code, a display, displaying a graphical user interface for annotating the video feed using the computer, wherein the graphical user interface includes a first control embodied in computer readable code executed by the computer for splitting the video feed into at least two portions according to the logical structure of the communication and a second control embodied in computer readable code executed by the computer for annotating at least one of the two portions, and a database embodied in computer readable code for storing an annotated portion of the video feed.

Abstract: A system for hazards analysis includes: a memory device for storing a program; a processor in communication with the memory device, the processor operative with the program to: access the memory device to obtain information specifying a system to be analyzed; build functional block diagrams using the information specifying the system to be analyzed; receive user-input hazards analysis elements; and use the functional block diagrams, the user-input hazards analysis elements and tree fault analysis for hazards analysis.

Abstract: A method for modeling requirements of a product includes defining an abstract use case for each feature of said product; hierarchically decomposing each abstract use case until concrete use cases are specified for each feature; depicting every actor who would use said product as communicating with a concrete use case through a boundary; and programmatically extracting requirements from said use case diagram. Programmatically extracting requirements further includes converting use case diagrams into directed acyclic graphs, wherein each use case corresponds to a node of a graph, and each relationship between a pair of use cases is represented by a directed edge between the corresponding pair of nodes in said graph, wherein a directed edge points from a parent node to a child node, converting said directed acyclic graph into a tree, and searching said tree to extract said requirements.

Abstract: A method for extracting requirements of an architectural software model comprises providing a use case model as a directed graph of the architectural software model comprising nodes corresponding to use cases and relations between nodes, and creating, automatically, a tree comprising a root node corresponding to an abstract use case and at least one leaf node corresponding to one of an abstract use case and a concrete use case.

Abstract: The present invention provides a graphical user interface for presentation, exploration and verification of patient information. In various embodiments, a method is provided for browsing mined patient information. The method includes selecting patient information to view, at least some of the patient information being probabilistic, presenting the selected patient information on a screen, the selected patient information including links to related information. The selected patient information may include elements, factoids, and/or conclusions. The selected patient information may include an element linked to unstructured information. For example, an element linked to a note with highlighted information may be presented. Additionally, the unstructured information may include medical images and waveform information.