Abstract: This document describes various techniques for creating, modifying, and using graphical mashups. In one embodiment, a graphical mashup is created based on locations of graphical representations of objects in a working area. Logical connections between the objects are created based on the objects' locations relative to each other. Alternatively or additionally, the techniques may enable a user to create or modify a graphical mashup by adding or deleting objects, modifying logical connections between objects, annotating objects, or abstracting the graphical mashup.

Abstract: Some embodiments of multiple organization support in a networked system have been presented. In one embodiment, a centralized server manages a networked system, which includes the centralized server and a set of computing machines coupled to each other within an internal network of a customer. The centralized server segregates data within the networked system by grouping data into the concept of an organization created by the customer in order to isolate the organizations.

Abstract: Embodiments of the present invention address deficiencies of the art in respect to defect classification for software development and provide a method, system and computer program product for automated defect classification in a software development tool. In an embodiment of the invention, a defect classification method can be provided. The method can include computing differences between versions of a line of source code, lexically analyzing the computed differences to produce a lexical construct, mapping the lexical construct to a classification, and assigning the defect classification to the line of source code.

Abstract: A version control system includes a mechanism for a learning roadmap based on information available from a source repository. More particularly, the mechanism generates an easily understandable timeline of a project and a directory of developers based on information available in the version control system that contains the source content of a project. The timeline for the project may be tied to the directory of developers. Under each date in the timeline, a list of developers and their roles and commits may be listed.

Abstract: Described herein are interactive graphical user interfaces that visualize execution behavior of source code together with theoretical execution behavior of the source code together with the source code itself. Structure of the source code is analyzed to determine theoretical execution behavior of the source code. Thereafter, symbolic execution of the source code is undertaken to output an execution trace. The execution trace is shown together with the theoretical execution behavior of the source code.

Abstract: Techniques are provided for testing one or more applications across multiple operating systems (OSs) using virtualization. A device includes a virtualization application and a dispatcher. The virtualization application allows a plurality of guest OSs to execute on a device. The dispatcher is configured to cause a particular file to be stored in a particular location. Each guest OS includes a listener that detects when a file is stored in the particular location. When the listener of each guest OS detects that the particular file is stored in the particular location, the guest OS is configured to perform one or more tasks associated with the particular file. Each guest OS is configured to generate output in response to performing the one or more tasks. The dispatcher is further configured to analyze the output from each of the guest OSs.

Abstract: State data can be separated from an existing software stack stored in one or more computer storage units in a computer system. The existing software stack can include operating system software and application software, and the state data can represent one or more states of the existing software stack. An image can be stored in one or more computer storage units in the computer system, and the stored image can form an updated software stack including operating system and application software. In addition, the updated software stack can be configured using the state data.

Abstract: A method and system reuse data logs generated from testing of programmable devices in order to provide an input file of parameter values and settings for use in automatically configuring a device simulator. The programmable device testing process generates a data log output with data formatted so that parameter data are associated with unique variable labels. The data log output file is processed in a parser operation that filters out private and unnecessary information, organizes the data and generates a simulation input file in a format compatible with the simulator. The process can be fully automated.

Abstract: Techniques are disclosed for generating fast vector masking SIMD code corresponding to source code having a conditional statement, where the SIMD code replaces the conditional statements with vector SIMD operations. One technique includes performing conditional masking using vector operations, bit masking operations, and bitwise logical operations. The need for conditional statements in SIMD code is thereby removed, allowing SIMD hardware to avoid having to use branch prediction. This reduces the number of pipeline stalls and results in increased utilization of the SIMD computational units.

Abstract: Tools and techniques for providing an assessment of a prospective configuration change in a production database environment. In some cases, tools may record a series of transactions in a production database. This set of transactions can then be replayed by the tools in a test database, both before and after the configuration change has been performed. The performance of the workload in this test environment can be measured under both conditions (pre-change and post-change) to provide insight into a performance impact that might result from implementing the configuration change in the production environment.

Abstract: An aspect of the present invention mitigates reduction in availability level during maintenance of nodes in a cluster. In one embodiment, on receiving an indication that a maintenance activity is to be performed on the cluster, a scaling out of the cluster is first performed to add some nodes having the maintenance activity already performed, followed by a scaling in of the cluster to remove some of the nodes in the cluster which do not yet have the maintenance activity performed. The scaling out is performed before any scaling in of the cluster such that the number of nodes available in the cluster after the scaling in is not less than the number of nodes in the cluster at the time of receiving the indication. Accordingly, the reduction in availability level (which is based on the number of nodes available) is mitigated.

Abstract: A method for processing, in a platform having one or more processors and memories, an object including elementary information of same type. The method decomposes the object to be processed into at least two sub-objects of N elementary information each, all the sub-objects having the same quantity N of elementary information, the processing performing at least one sequence of specific operations on the elementary information of each sub-object performing, for each sub-object, at least N times each specific operation, such that each elementary information for each sub-object is applied at least one time, and N results are produced for each specific operation, the sequence of specific operations being such that at least one specific operation of the sequence produces, at least once during its N applications, a result used for the processing of another sub-object.

Abstract: Automatically backing up one or more computers across a network to a backup device coupled to the network through one of the computers connected to the network. In one embodiment, a user connects the backup device to a first network connected computer which triggers the launch, installation, setup and configuration of the associated software on the first computer thereby performing a backup operation of data from the first computer to the backup device. The user then connects the backup device to a second network connected computer which triggers the launch, installation, setup and configuration of the associated software on the second computer thereby performing a backup operation of data from the second computer to the backup device. Furthermore, the associated software installed on the second computer triggers communication with and a backup of data from the first computer across the network through the second computer to the backup device.

Abstract: A plug-in framework is invoked within a plug-in, where the plug-in framework includes a software library configured to define, register, and configure plug-ins, where the plug-in includes a software module that extends or customizes functionality of a software application that is external to the plug-in, and where the plug-in includes a mapping name. A plug-in instance declaration is searched, by the plug-in framework, for a mapping that includes the mapping name, where the plug-in instance declaration is located within a plug-in file, and where the plug-in declaration comprises one or more mappings. When a mapping of the mapping name to the value is found, the value is returned, by the plug-in framework, to the plug-in based on the mapping. The plug-in framework also allows a plug-in provider to associate a plug-in with metadata.

Abstract: A technique for managing package dependencies for an application installation. A set of used files for the application and a package for a respective file in the set of used files are identified, and names of the identified packages are added to an original package list of package names for the application, wherein the original package list defines package dependencies. Responsive to a determination that the identified packages can be located, that the files within the identified packages can be found, and that the files within the identified packages were used, the original list of package names for the application is updated to form an updated list of managed package dependencies. A difference list between the updated list and the original list of package names is created, and the application is selectively installed using a combination of the original list of package names and the difference list.

Abstract: Embodiments described herein are directed to updating the various software associated with a distributed application in a piecemeal fashion. All instances of the software are analyzed and separated into different portions, called “roles.” Each instance of a role is strategically assigned to an update domain based on the structural information included in the service model of the distributed application. The distributed application is upgraded one update at a time by selecting an update or host update domain, bringing the roles assigned thereto offline, updating the offline roles, bringing the roles back online, and repeating for other update or host update domains.

Abstract: A computer implemented method for the verification of concurrent software programs wherein the concurrent software program is partitioned into subsets named concurrent trace programs (CTPs) and each of the CTPs is evaluated using a satisfiability-based (SAT) symbolic analysis. By applying the SAT analysis to individual CTPs in isolation the symbolic analysis is advantageously more scalable and efficient.

Abstract: System and method for creating platform-specific self-extracting client packages using a production server are described. In one embodiment, the method comprises compiling a source file on a first build server comprising a first computing platform to produce a first executable seed file for the first computing platform and compiling the source file on a second build server comprising a second computing platform to produce a second executable seed file for the second computing platform; and providing the first and second executable seed files to a production server comprising the first computing platform. The production server uses the first executable seed file to create a first client package and a second client package, wherein the first client package is designed to be installed and execute on a first workstation running on the first computing platform and the second client package is designed to be installed and execute on a second workstation running on the second computing platform.

Abstract: A method of matching one or more software plug-ins to a user, the method including: defining one or more trigger events based on one or more actions of an application; monitoring a use of the application for the one or more trigger events; generating a suggestion of one or more plug-ins based on the use of the application; and generating a notification including the suggestion.

Abstract: Embodiments of the invention provide techniques for presenting energy consumption information in an IDE tool. In one embodiment, the IDE tool may be configured to determine energy requirements associated with specific elements of the source code, and to present graphical indications of energy requirements along with those code elements. Such energy requirements may be determined by matching code elements to a stored data structure describing energy requirements for executing various code elements. The stored data may be based on predefined standards, and/or may be based on historical measurements of energy consumption during prior instances of executing code elements on a target computer system. Additionally, developers may specify priority for compiling portions of source code, according to desired energy requirements.