Abstract: A knowledge generation machine (KGM) that collects information of varying types from a plurality of different sources is provided. The KGM uses this information to understand, correlate, and expand a dependency model in order to realize a set of dependencies for a software component. The KGM provides an adaptive dependency model that detects new sources of information and creates new dependencies and dependency types based on that new information. A dependency is given a weighting that is used to resolve potentially circular dependencies.

Abstract: The present invention is directed to automatically analyzing software systems for identifying faults or bugs and/or detection of malicious code. In various embodiments, the present invention measures code coverage for high priority invocable program elements, uses a relaxed coverage estimation technique that, instead of guaranteeing which code units will be executed, guarantees that at least a certain number of code units will be executed, determines and solves constraints in code to identify infeasible paths containing one or more selected nodes, determines, for a composite data type, a range of values for each of at least two non-composite data fields, and/or translates, prior to code analysis complex code into simpler code having fewer operators.

Abstract: A method for synchronizing an original code base (OCB) with a superset code base (SCB) which is a superset of the OCB. The method includes obtaining the OCB, obtaining the SCB and determining a file pair difference between the OCB and the SCB. An action table is accessed to retrieve actions based on a classification of each OCB file, a classification of each SCB file, and file pair difference. The actions are assembled into an action file. The actions in the action file are executed to synchronize the OCB and the SCB.

Abstract: A user interface for displaying source data and a translated copy of a segment of the source data is provided. The user interface includes a first display portion for displaying at least a subset of the source data on the display. The user interface includes a second display portion for displaying a translated copy of a selected segment of source data on the display.

Abstract: Those files accessed by tools during a build process are invisibly tracked in such a way that the information can then be used to drive an incremental build of just enough files to bring the build fully up to date. The tracking information includes the association between distinct tool processes. Each build tool has its own file activity tracked, each thread of operation within tools are tracked separately and a tracking log is associated with a chain of tool processes so that when the tracking logs are interpreted the context in which they were created is preserved.

Abstract: Modeling a component-based application includes modeling communication capabilities of components of the application, modeling a plan for interlinking components of the application, modeling communications capabilities of a compound component composed of a plurality of constituent components, and determining if interlinked components are compatible to communicate validly in the application.

Abstract: A method and apparatus for dynamic binary translator to support precise exceptions with minimal optimization constraints. In one embodiment, the method includes the translation of a source binary application generated for a source instruction set architecture (ISA) into a sequential, intermediate representation (IR) of the source binary application. In one embodiment, the sequential IR is modified to incorporate exception recovery information for each of the exception instructions identified from the source binary application to enable a dynamic binary translator (DBT) to represent exception recovery values as regular values used by IR instructions. In one embodiment, the sequential IR may be optimized with a constraint on movement of an exception instruction downward past an irreversible instruction to form a non-sequential IR. In one embodiment, the non-sequential IR is optimized to form a translated binary application for a target ISA. Other embodiments are described and claimed.

Abstract: A target graphics document containing graphics data may be used as a starting point to automatically generate one or more test cases as a sequence of test events to re-create the appearance of the target graphics document. The target document may be examined to determine the layers, graphics data within each layer, and the attributes of the graphics data. Based on the determined data, a sequence of input device actions may be generated to create a test document having graphics data based at least in part on the target document. In some cases, the generated input device actions may create a test document containing graphics data identical to that of the target document. In some cases, some user randomness may be applied to the generated input device actions to simulate ‘real-world’ user inaccuracy. In some cases, typical user manipulation of an input device may be applied to simulate ‘real-world’ usage.

Abstract: Tools and methods are described herein that allows for measuring and using the relationship between artifacts of a software design, such as requirements, test plans, and so on. The relationship can be quantified by determining a relationship quotient for quantifying a similarity between components of software design artifacts and presenting the quantified relationships to a user, such as a software designer, so that he or she can account for the relationship between such components during design changes and so on. The relationship quotient is made more representative of substantive similarity by selecting the key terms that are to be submitted to a similarity analysis such that words that are too common in the English language, such as conjunctions, articles, etc., are not used. Ubiquity of certain key terms in an enterprise is accounted for by adding a term significance weight to the similarity analysis.

Abstract: Methods for handling zero-length allocations are disclosed. An example of such a method may include returning a self-describing/diagnosing dynamic address that has all the properties required for a secure implementation. Another example may include returning a series of different addresses (instead of a single address per process) to improve supportability. Yet another example may include maintaining diagnostic information about the original allocation for ease of problem resolution.

Abstract: The present invention is a method for manipulating source code in a text editor, which includes receiving an input, the input designating an identifier. The method further includes associating a plurality of source code fragments with the identifier. Additionally, the method includes adding comment characters to each source code fragment of the plurality of source code fragments associated with the identifier.

Abstract: A method and system is provided that allows a well-behaved program to execute more quickly than dynamically typed programming languages did in the past, thereby allowing a the dynamically typed language to be competitive with static declarative programming languages. A method includes converting lines of source code representing functions to byte-codes representing functions, selecting a subsequence of the byte-codes based on the byte-codes and the dynamic run-time properties of program variables, generating processor instructions in a compiler for the subsequence, and interpreting the byte-codes not contained in the subsequence.

Abstract: Those files accessed by tools during a build process are invisibly tracked in such a way that the information can then be used to drive an incremental build of just enough files to bring the build fully up to date. The tracking information includes the association between distinct tool processes. Each build tool has its own file activity tracked, each thread of operation within tools are tracked separately and a tracking log is associated with a chain of tool processes so that when the tracking logs are interpreted the context in which they were created is preserved.

Abstract: XPS documents are created and accessed via a collection of interfaces of various classes of an application programming interface. The application programming interface includes a document sequence class for reading and writing the document sequence of the XPS document, a fixed document class for reading and writing the fixed documents of the document sequence, a page class for reading and writing the pages of the fixed documents, and a resource class for accessing the resources of each page. Applications seeking to create or read XPS documents may utilize the application programming interface such that the complexities of creating and accessing the XPS document are abstracted away.

Abstract: Computer system and method automatically generates a test source code for checking validity of an application written in an object oriented language. The application includes objects accessible through an interface implementing programming rules and object behavior rules. For each object, the invention extracts object methods and attributes of the object interface which are impacted by the object behavior rules and extracts the object identification. The invention fills the variable fields of a source code template with the extracted information. The template non variable source code is in conformance with the programming rules and implements a scenario for checking a set of object behavior rules; thus the filled template forms a generated test source code. For distributed applications, the specifications may be EJB or CORBA and the Test Generator uses templates for checking the life-cycle (creation, persistency, removal) of deployed objects.

Abstract: An update applicability data model is used to define relationships between an instance of a hardware device and an instance of an associated software component in an inventory context and a packaging context. A hardware device instance is correlated with an instance of the associated software component in the inventory context. Instances of hardware devices are compared in the inventory context. Instances of software components are compared in the inventory context and in the packaging context. Instances of hardware devices are grouped in the inventory context. Instances of software components are grouped in the inventory context and in the packaging context. Whether to update an instance of a software component associated with an instance of a hardware device using the update applicability data model is determined.