Abstract: A method includes, by one or more computing devices, determining code-under-test configured for execution on a computing device to be evaluated, creating a plurality of test cases based on the symbolic execution and including a plurality of constraints, selectively conducting abstract interpretation on the constraints, selectively conducting Satisfiability Modulo Theory (“SMT”) solving on the constraints, and validating or invalidating the code-under-test based on at least the SMT solving and the abstract interpretation. The abstract interpretation includes using a plurality of abstract interpretation models based on the constraints of the test case and over-approximating the constraints of the test case.

Abstract: A system and method can support compliance tests with annotation based standards using an expectation library. The expectation library can convert one or more descriptive assertions into a structured data model, wherein the one or more descriptive assertions describe one or more annotations. Furthermore, the expectation library can parse a source file that contains the one or more annotations based on the structured data model. Additionally, the expectation library can obtain information related to the one or more annotations of the source file from the structured data model.

Abstract: An embodiment is directed to determining, by a compiler, that a call to a named barrier is matched across all of a plurality of threads, and based at least in part on determining that the call to the named barrier is matched across all of the plurality of threads, replacing, by the compiler, the named barrier with an unnamed barrier.

Abstract: Systems and methods for generating profiling data include monitoring the execution of a task on a thread of a program. Profiling data may be generated that includes metrics regarding the execution of the task. A profiling data aggregation service may aggregate generated profiling data from a plurality of devices that execute the program.

Abstract: A system and method includes obtaining and storing, on a computer readable storage device, a list of a set of test cases designed to test logical code units in multiple objects of a software program in a design environment, identifying a first set logical code units covered by the test cases, identifying a second set of logical code units corresponding to a productive environment, and comparing, via a computer, the first and second sets of logical code units to generate an evaluation of the test cases for the software program in the productive environment.

Abstract: In an embodiment, a cloud debug breakpoint, assigned to a first user, is established in a program at a first server in a cloud, wherein the first user selects the first server at which the program executes, from among servers in the cloud. The program at the servers in the cloud is executed, in response to requests from users. The program at the first server in the cloud is executed, in response to all requests from the first user to the program. If an identifier of a user that sent a request that the program was executing at a time that execution of the program at the first server reaches the cloud debug breakpoint matches an identifier of the first user assigned to the cloud debug breakpoint, the execution of the program is halted and control of a processor is given to a debugger.

Abstract: A system and method is provided for automatically resolving dependencies of Java Archive (Jar) files, for use with software development tools such as Maven. A Maven coordinate determination logic is used to generate Maven coordinate information for, e.g., an Open Service Gateway Initiative (OSGi)-based Jar file. In accordance with an embodiment, an OSGi class loader is used to automatically determine Maven coordinates and dependency information based on the contents of the Jar, and store the coordinates and dependency information in a generated Project Object Model (POM) file.

Abstract: A method for determining a comprehensiveness of software requirements tests for testing a software application includes receiving data that defines artifacts of a software project. A first sub-link between at least one application requirement and at least one code module of the application code is identified. The first sub-link indicates a relationship between the application requirement and the code module. A second sub-link between at least one test case and the code module is identified. The second sub-link indicates a relationship between the test case and the module. A traceability link between the test case and the application requirement is determined based on the first sub-link and the second sub-link. The traceability link indicates that the test case tests the software application for compliance with the application requirement.

Abstract: Structural information of a process is stored as an instance hierarchy (e.g. parent-child relation) between occurrence nodes comprising occurrence identifications (IDs) and links to objects of an object pool. Efficient management of process versions (e.g. design, build, test, productive, archive) is accomplished by handling occurrences and corresponding linked objects so that a minimum set of data is physically copied. An algorithm governing the physical copying of process data, is described.

Abstract: The present invention discloses a method for inserting code into .Net program and an apparatus therefor, relating to the field of information security. The method comprises the steps of: writing information of code to be inserted to import table of a .Net executable file; adding address of the code to be inserted to import address table (IAT) of the .Net executable file to form a new import address table; change offset address of entry point of the .Net executable file to address of the new IAT; and change flag in header of metadata table of the .Net executable file to enable the .Net executable file to meet certification requirements when being executed. The apparatus comprises a writing module, a forming module, and a modification module. The method and apparatus provided by the present invention implement code insertion into .Net executable file without the dependency on assembly and disassembly tools and are easy to use.