Abstract: According to one aspect of the present disclosure a system and technique for deploying an application in a cloud computing environment includes: a collecting module executable by a processor unit to collect, when a user is deploying an application, metadata and instructions on deploying the application, the metadata comprising service metadata, application metadata and topology metadata, wherein the service metadata comprise metadata on a service required for deploying the application, the application metadata comprise metadata on the application, and the topology metadata comprise metadata indicative of a relationship between the service and the application; and a storing module executable by the processor unit to store the collected metadata and instructions as a model for re-deploying the application.

Abstract: A technique for deploying an application in a cloud computing environment includes: collecting, when a user is deploying an application, metadata and instructions on deploying the application, the metadata comprising service metadata, application metadata and topology metadata, wherein the service metadata comprise metadata on a service required for deploying the application, the application metadata comprise metadata on the application, and the topology metadata comprise metadata indicative of a relationship between the service and the application; and storing the collected metadata and instructions as a model for re-deploying the application.

Abstract: Constructing a logical tree topology in a parallel computer that includes compute nodes, where each node executes a number of tasks and at least one node executes a number of tasks different from another node includes: identifying a compute node executing a greatest number of tasks; selecting, as a global root, a task from the identified compute node, including assigning the task as a local root of the identified compute node and assigning each of the other tasks of the identified compute node as a child of the local root; selecting, from each of the other compute nodes, one task to be a local root, including assigning each task other than the local root as a child of the local root; and assigning each local root of the other compute nodes to be a child of one of the tasks of the identified compute node other than the global root.

Abstract: A method of searching for and installing a software product on a device is provided. One or more capabilities needed by the device to be served by a software product are determined. The one or more capabilities needed by the device are communicated from a software life cycle management agent on the device to a yellow pages agent outside the device, the communicating comprising formulating a request comprising a list of the capabilities encoded in a description language that defines the capabilities semantically. Then locations of one or more software products matching the one or more capabilities needed by the device may be received from the yellow pages agent. One of the one or more software products to install may be selected based on automatically evaluated criteria. Then the selected software product may be downloaded using its received location, and the selected software product may be installed on the device.

Abstract: The disclosed embodiments include methods and systems for providing predictive quality analysis. Consistent with disclosed embodiments, a system may receive input data associated with a software program and compare the input data with one or more predetermined analysis parameters. The system may further determine at least one risk rating based on the comparison, wherein each risk rating corresponds to a distinct software category. The system may perform additional operations, including determining at least one adjustment to the software program based on the determined at least one risk rating, and prioritizing the at least one adjustment based on a predetermined adjustment priority standard. Furthermore, the system may provide a report including at least an indication of the at least one prioritized adjustment, a timeline for implementing the at least one prioritized adjustment, and plan implementing the at least one prioritized adjustment.

Abstract: Constructing a logical tree topology in a parallel computer that includes compute nodes, where each node executes a number of tasks and at least one node executes a number of tasks different from another node includes: identifying a compute node executing a greatest number of tasks; selecting, as a global root, a task from the identified compute node, including assigning the task as a local root of the identified compute node and assigning each of the other tasks of the identified compute node as a child of the local root; selecting, from each of the other compute nodes, one task to be a local root, including assigning each task other than the local root as a child of the local root; and assigning each local root of the other compute nodes to be a child of one of the tasks of the identified compute node other than the global root.

Abstract: A social networking system user is prompted to take an action or is provided with additional information associated with a location where the user has checked-in or has associated with content using a tag. When an input including the check-in or tagged location is received, the social networking system selects one or more actions based on the location, the user, and/or contextual information included in the input. A prompt identifying the one or more of the selected actions is generated and presented to the user.

Abstract: Techniques provided implement automatic data type annotation in dynamically-typed source code. A codebase, which may comprise a plurality of source code files, is scanned at a global level. The resulting scanned data may describe characteristics of the codebase, including variable and function usage. Based on inferences drawn from the scanning, data types are determined for different variables, expressions, or functions to facilitate conversion from dynamically-typed source code to statically-typed source code. For example, if a function is called once with a parameter value of data type A (e.g., class A), and another time with a parameter value of data type B (e.g., class B), a conversion tool may annotate the parameter variable in the declaration of the function with a data type D (e.g., class d) when data type D is identified as a common ancestor (e.g., superclass) to both data type A and data type B.

Abstract: A computer system is provided comprising a client computer, a management server computer, and a communications network. The client computer includes hardware and software for executing an application utilizing data, files and code downloaded from the management server computer. The management server computer includes the data, files and code required by the client computer for executing the application. The management server computer includes hardware and software for registering the client computer to receive electronic change notifications for any updates made to the data, files and code at the management server computer. The client computer includes hardware and software for updating data, files and code from the management server computer prior to further execution of the application with any outdated data, files or code once an electronic change notification has been received.

Abstract: The described embodiments include a program code testing system that determines the vulnerability of multi-threaded program code to soft errors. For multi-threaded program code, two to more threads from the program code may access shared architectural structures while the program code is being executed. The program code testing system determines accesses of architectural structures made by the two or more threads of the multi-threaded program code and uses the determined accesses to determine a time for which the program code is exposed to soft errors. From this time, the program code testing system determines a vulnerability of the program code to soft errors.

Abstract: In a method for managing updates for a software product, receiving a request to install a software product update, wherein the software product update modifies a software product on a computing device. The method further includes identifying a first set of one or more functions of the software product that are to be modified by the software product update. The method further includes identifying historical usage information corresponding to the software product, wherein the historical usage information indicates a second set of one or more functions of the software product and a number of times each respective function of the second set of one or more functions of the software product has been used by the computing device. The method further includes determining whether the software product update modifies at least one function of the software product that corresponds to historical usage information that exceeds a minimum usage threshold condition.

Abstract: Methods of managing observability code in an application program include generating an application program including an observability point, the observability point including a location in the application at which observability code, or a call to observability code, can be inserted, loading the application program into a memory of a target system, retrieving observability information from an observability point information file, and inserting the observability code, or the call to the observability code, at the observability point in the memory of the target system using the observability information retrieved from the observability point information file.

Abstract: Debugging a debug target software by: (i) generating a first log file set, including at least one log file, based upon how the computer hardware set executes the instructions of the computer software set; (ii) responsive to a first error in the execution of the computer software set, examining at least a portion of the first log file set; and (iii) creating, based at least in part upon the examination of the first log file set, augmented logging instructions for generating augmented logging information, which is helpful for debugging.

Abstract: A method, non-transitory computer readable medium, and apparatus that quantitatively assesses the impact of a project change request to software quality including determining at least one initial project request defect value based on an initial project request effort value and a defect insertion rate, determining at least one project change request defect value based on a project change request effort value and the defect insertion rate, comparing at least one project change request defect value to at least one initial project request defect value, and providing a quality impact value based on the result of the comparison.

Abstract: A consistency assessment system for assessment of consistency of a software product includes a mapping module to obtain a plurality of configuration elements associated with the software product being developed, where each of the plurality of configuration elements influence software product development. Each of the plurality of configuration elements pertains to one of a plurality of element categories influencing software product development. The mapping module further identifies based on one or more identifiers, association of at least one configuration element from among the plurality of configuration elements with at least one another configuration element from among the plurality of configuration elements. Upon identification, an assessing module determines a requirement consistency index (RCI) for assessment of consistency of the software product. The RCI indicates an overall consistency of the software product.

Abstract: A system and method for updating an accessory device are described. A software upgrade for upgrading an accessory device is received from a wireless network at a wireless device. In response, it is automatically determined at the wireless device whether the accessory device is in communication with the wireless device. Upon determining that the accessory device is in communication with the wireless device, the software upgrade is forwarded from the wireless device to the accessory device to enable upgrade of the accessory device according to the software upgrade.

Abstract: Techniques described herein relate to updating firmware of multiple non-volatile memory devices having diverse configurations using a common update file. The non-volatile memory device may include a flash memory device having a non-volatile memory array. Particular implementations described herein relate to circuits, devices, systems, and methods that update, with a common update file, firmware residing on multiple non-volatile memory devices having diverse configurations.

Abstract: A computer-implemented method is disclosed in which locations of a plurality of Job Control Language (JCL) tests are obtained from a primary database supporting a software testing management platform. The locations the locations of the plurality of JCL tests are transmitted to a mainframe computing system (MCS) to initiate execution of the JCL tests. Based on transmitting the JCL test locations, execution IDs are retrieved for each of the plurality of JCL tests from the MCS. For each JCL test, the execution ID and an initial status of the JCL test are stored in the primary database. A query is transmitted to the MCS to determine an execution status of a given one of the JCL tests. Based on transmitting the query, a status update is received from the MCS for the JCL test, and the initial status of the JCL test in the primary database is selectively updated.

Abstract: A method for creating as test case for a client can include identifying an object in the client using a parser module. A list of potential test case tasks for testing the client can be populated from the parser module into a test case task window. A test case flow can be built by placing a desired task from the list of potential test case tasks in a test case development window. The method can continue by assigning the object to the desired task in the test case development window. The test case can be generated from the test case flow.

Abstract: Exemplary methods, apparatuses, and systems generate a plurality of possible branch traces for a computer program. Each possible branch trace represents different sequences of branch instructions that may be executed while the computer program is running. Each branch instruction has a corresponding identifier. A branch trace value is generated for at least one of the plurality of possible branch traces. Generating the branch trace value includes performing a mathematical or logical operation between a first identifier and each subsequent identifier of the possible branch trace to obtain the branch trace value. An output including a branch trace is generated based upon a match between a run-time branch trace value and the at least one generated branch trace value.