Identifying impacted tests from statically collected data
US-9389986-B2 · Jul 12, 2016 · US
US9892029B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9892029-B2 |
| Application number | US-201514868713-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 29, 2015 |
| Priority date | Sep 29, 2015 |
| Publication date | Feb 13, 2018 |
| Grant date | Feb 13, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An apparatus for automatic conversion of existing systems management software applications to run in multiple middleware runtime frameworks by automating the unification of runtime framework ontologies and isolating runtime dependent code in the build process of system management applications through the introduction of a runtime dependency processor and performing runtime dependency analysis.
Opening claim text (preview).
Thus, having described the invention, what is claimed is: 1. A method for automatic conversion of existing systems management software applications to run in multiple middleware runtime frameworks comprising: scanning said frameworks of system management components to form individual function modules; mapping application program interface calls to a generic applicant program interface call layer by creating an association of said individual function modules; performing runtime dependency analysis by generating ontology alignment mechanisms and outputting a mapping table of ontologies; performing model unification by mapping runtime dependent functions to semantic counterparts using said ontology alignment mechanisms; generating multiple runtime independent proxy components for said system management components; and automatically refactoring each said system management components into two modules: a runtime independent module and a runtime dependent proxy module, wherein said runtime independent module replaces runtime dependent code with runtime independent code counterparts, wherein said model unification is dictionary-based, structure-based, or a combination thereof. 2. The method of claim 1 including utilizing a runtime dependency processing module to read unified ontologies and generate said multiple runtime independent proxy components from mapping relationships. 3. An apparatus for automatic conversion of existing systems management software applications to run in multiple middleware runtime frameworks comprising: a plurality of system management components; a scanner having a hardware processor configured to scan said system management components; a plurality of ontologies each associated with individual runtime frameworks analytically describing said runtime framework functions, methods, or arguments; an algorithmic component identifying and analyzing runtime dependent functions, methods, or arguments in said system management components by performing a runtime dependency analysis, and isolating said system management components using delegation and factor object patterns to form isolation layers; a runtime mapping module configured to unify said plurality of ontologies using data from said runtime dependency analysis, and form a mapping table of equivalent functions, methods, or arguments between each supported target runtime; and a runtime dependency processing module that applies data from said mapping table into said isolation layers, wherein said runtime dependency processing module utilizes said mapping table to automatically refactor each system management component into two modules: a runtime independent module and a runtime dependent proxy module, wherein said runtime independent module replaces runtime dependent code with runtime independent code counterparts, wherein said algorithmic component performs model unification of two or more ontologies such that a unified ontology includes a mapping of runtime dependent member functions to semantic counterparts, wherein said model unification is dictionary-based, structure-based, or a combination thereof. 4. The apparatus of claim 1 wherein said runtime dependency processing module output is applied to a collection of isolated logic code that delegates said runtime dependent functions, methods, or arguments to runtime independent proxy components supported by runtime dependent implementations. 5. The apparatus of claim 2 wherein said runtime dependent implementations support each of said runtime independent proxy components. 6. The apparatus of claim 2 wherein said runtime dependency analysis iterates through each of said system management component source code to identify members and methods that are runtime dependent. 7. The apparatus of claim 1 wherein dictionary-based model unification includes assigning a semantic meaning of an ontological element and comparing said semantic meaning to other ontological elements by identifying semantically equivalent constructs. 8. The apparatus of claim 1 wherein structure-based model unification includes forming a relationship between system management components and combining two or more distinct substructures. 9. The apparatus of claim 4 wherein an output of said algorithmic component is combined with an output of said runtime mapping module unification to form an automatic proxy substitution mapping for each runtime dependent code in each system management component. 10. The apparatus of claim 1 wherein said runtime dependent proxy module implements said runtime independent code counterparts, transferring runtime framework dependencies to said runtime dependent proxy modules.
for coverage analysis · CPC title
by tracing the execution of the program · CPC title
Analysis of software for verifying properties of programs (testing of software G06F11/3668) · CPC title
Unification in logic programming · CPC title
Dependency analysis; Data or control flow analysis · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.