Abstract: A system, method, and computer program product are provided for automatically creating and submitting defect information associated with defects identified during a software development lifecycle to a defect tracking system. In use, creation of a defect ticket is initiated for an identified defect for submission to a defect tracking system, the identified defect being identified during a software development life cycle. Additionally, a list of potential originating teams from which the identified defect was potentially identified is presented, the list of potential originating teams being presented in a user selectable format. Further, a list of teams in which to assign the identified defect is presented, the list of teams in which to assign the identified defect being presented in a user selectable format. Furthermore, a user selected originating team and a user selected team in which to assign the identified defect is identified.

Abstract: A system generates a test path set in a very efficient manner. The test path set may be tailored to test a target physical system, such as a complex set of source code, a manufacturing line of multiple process nodes, or other physical system. The system may generate the test path set to meet certain goals in testing the target physical system, for example comprehensive testing of system paths, system nodes, or particular subsets. As one example, the system may efficiently generate a test path set that uses the minimum number of test paths to test a coverage goal, for example traversing each of the prime paths in the target physical system.

Abstract: A system and method is provided for configuring compatibility algorithms for testing compatibility of applications with a platform. The method is performed by one or more processors and comprises attaching compatibility algorithms associated with compatibility applications with meta data or executable code. The method also comprises receiving a request for determining which compatibility algorithms are compatible with a platform, wherein the request includes one or more attributes of the platform. The method further comprises comparing the one or more attributes of the platform with the attached meta data or attached executable code, and identifying at least one compatibility algorithm based on the comparison such that the identified compatibility algorithm determines whether to run the identified compatibility algorithm.

Abstract: Three methods for converting sketch shapes into semantic elements by way of a semantic editor are disclosed. First, a method for conversion of a sketch shape that is part of a nested shape combination, which includes a sketch shape either hosting or nested within a semantic element. Second, a method for conversion of sketch shapes to semantic elements by storing sketch shape names and sketch shape descriptions in correlation with specific semantic elements and properties. The stored correlation is referenced for subsequent sketch shapes names or descriptions that are the same or a subset of the stored sketch shape name or description. Third, a method of conversion of one or more sketch shapes into a semantic template containing a plurality of semantic elements. Each of the one or more sketch shapes is mapped to a specific semantic element within the semantic template.

Abstract: Analyzing technical solutions for supporting desired business capabilities includes constructing a plurality of alternative technical solutions, wherein each alternative technical solution comprises a respective set of technology components, wherein each technology component provides support for a respective requirement associated with fulfilling a respective one of a plurality of desired business capabilities. Then an implementation roadmap can be generated comprising any technology component that is a member of more than one of the respective sets of technology components; and this implementation roadmap can then be provided as output.

Abstract: A method for processing a function with a plurality of execution spaces is disclosed. The method comprises creating an internal compiler representation for the function. Creating the internal compiler representation comprises copying substantially all lexical tokens corresponding to a body of the function. Further, the creating comprises inserting the lexical tokens into a plurality of conditional if-statements, wherein a conditional if-statement is generated for each corresponding execution space of said plurality of execution spaces, and wherein each conditional if-statement determines which execution space the function is executing in. During compilation, the method finally comprises performing overload resolution at a call site of an overloaded function by checking for compatibility with a first execution space specified by one of the plurality of conditional if-statements, wherein the overloaded function is called within the body of the function.

Abstract: Disclosed is a program distribution device that enables to distribute programs in a more appropriate order with respect to an electronic device to which the programs are distributed. The program distribution device includes an appropriateness determination unit which executes an appropriateness determination processing on the basis of policy information, and distributes the update program to the target device in accordance with a result of determination.

Abstract: An automatic test apparatus for embedded software, an automatic testing method thereof and a test scenario composing method may be used to detect an unpredictable problem as well as a predictable problem that may occur under user's conditions and reproduce various events. The automatic testing apparatus may include a keyword composer which extracts a keyword from status information output by executing the embedded software, and composes a keyword list using the extracted keywords, an output analyzer which analyzes the output from the execution of the embedded software based on the composed keyword list, a control command generator which loads at least one scenario previously stored in accordance with the analysis results, and generates an instruction list corresponding to a predetermined event status, and a test processor which processes the embedded software to reproduce the event status based on the generated instruction list.

Abstract: Techniques for using a software logistics protocol include initiating, using the software logistics protocol, a software logistics process, the software logistics protocol being a common application programming interface (API) for controlling and managing the life cycle and operation of a plurality of different software logistics processes; monitoring, using the software logistics protocol, the progress of execution of the software logistics process; and gathering, using the software logistics protocol, output information from the software logistics process after the software logistics process finishes executing.

Abstract: Aspects of the subject matter described herein relate to searching. In aspects, a software package may be received and transformed into searchable data. Static and dynamic analysis may be performed on code and data included in the software package. A data structure is created that may index the code, metadata, indexable resources, and analysis artifacts associated with the software package. The data structure may be used to satisfy queries and the transformed data and analysis artifacts may be made available for viewing.

Abstract: Disclosed herein are systems, methods, and computer-readable storage media for identifying and remediating risky source files. An example system configured to practice the method can gather data describing each file in a source code repository, and generate, using a weighted algorithm based on empirical relationships between the data and customer-found defects, a risk score for each file in the source code repository, wherein the weighted algorithm prioritizes factors based on predictiveness of defects. Then the system can generate a list of files having risk scores above a threshold, and make risk-mitigation recommendations based on the risk scores. A file can include a single file or a collection of files such as a module. The system can identify, for each file in the list of files having risk scores above the threshold, a respective risk type, and make the risk-mitigation recommendation for each file based on the respective risk type.

Abstract: A method and system are provided for deriving a resultant software code from an originating ordered list of instructions that does not include overlapping branch logic. The method may include deriving a plurality of unordered software constructs from a sequence of processor instructions; associating software constructs in accordance with an original logic of the sequence of processor instructions; determining and resolving memory precedence conflicts within the associated plurality of software constructs; resolving forward branch logic structures into conditional logic constructs; resolving back branch logic structures into loop logic constructs; and/or applying the plurality of unordered software constructs in a programming operation by a parallel execution logic circuitry. The resultant plurality of unordered software constructs may be converted into programming reconfigurable logic, computers or processors, and also by means of a computer network or an electronics communications network.

Abstract: A system and computer-executed method automatically generate a sequence diagram from Class-Responsibility-Collaborator (CRC) information. The CRC information identifies objects, responsibility information for each object, and collaborator information for each object, and the CRC information corresponds with each activity in an activity diagram. The method includes storing, in a storage device, the objects and corresponding class types of the objects according to the CRC information and associating, by a processor, each of the objects with one or more other objects according to the collaborator information of the CRC information. The method also includes determining, by the processor, messages from each of the objects to associated objects according to the responsibility information, and the processor automatically generating the sequence diagram including the objects and the messages among the objects.

Abstract: A method for pre-testing software compatibility is illustrated. A system and software information of an operating system is extracted. While that a patch or new software will be installed in the operating system is detected, whether a compatibility test should be executed is determined. While that the compatibility test should be executed is detected, a virtual machine with a first clone system is generated, wherein the first clone system is generated according to the system and software information. The patch or the new software is installed in the first clone system to generate a second clone system. The compatibility test for the second clone system is executed. According to a result of the compatibility test, whether the patch or new software can be installed in the operating system or the second clone system can be switched to be used is determined.

Abstract: A system and method can support a deferred reference in an object-oriented programming language environment. The object-oriented programming language environment can include an interface that can provide a deferred reference to an object that will be available at a future time. Furthermore, after receiving a request from a caller to get the object based on the deferred reference, the interface can return the object to the caller when the object is available or can indicate to the caller when the object is not currently available and/or when the object will never become available.

Abstract: A system and method to automatically and continuously update the urgency rating of a backlog item associated with a technical debt item in a software development project are described. The technical debt represents potential additional work or rework associated with current code. The method includes a user defining a plurality of components that comprise the software development project. The method also includes a processor associating the technical debt with one or more components of the plurality of components, and the processor updating the urgency of the backlog item associated with the technical debt according to a function based on a development event associated with at least one of the one or more components.

Abstract: A system and method to automatically and continuously update the urgency rating of a backlog item associated with a technical debt item in a software development project are described. The technical debt represents potential additional work or rework associated with current code. The method includes a user defining a plurality of components that comprise the software development project. The method also includes a processor associating the technical debt with one or more components of the plurality of components, and the processor updating the urgency of the backlog item associated with the technical debt according to a function based on a development event associated with at least one of the one or more components.