Methods and systems for generating metadata describing dependencies for composable elements
First Claim
1. A method of generating, maintaining, combining, and storing metadata which describe dependencies for composable elements, the method comprising:
- maintaining a database describing information about a plurality of composable elements, wherein each of the plurality of composable elements has associated metadata to describe dependencies for each of the plurality of composable elements, wherein the metadata describes both tangible dependencies known to a developer of the composable element at compile time of that composable element and intangible dependencies that are unknown to the developer of the composable element at compile time of that composable element, and wherein each of the composable elements include one or more of;
a combination, a reprogramming, or a repurposing of software components and/or services;
receiving a request to compose, modify, update, re-program, or re-purpose two or more of the plurality of composable elements into a new element;
determining common dependencies among the two or more composable elements;
determining redundant dependencies among the two or more composable elements;
combining the dependencies to include each of any redundant dependencies from the combined components as well as any dependencies unique to each of the combined components or services, and any dependency that is common to more than one, then the more restrictive component dependency is utilized within the new element, wherein each dependency includes an associated level of dependency value and the higher the level of dependency value the more restrictive the dependency, and wherein the determination of the utilization of the common dependency is determined based on each of the levels of dependency of the common dependencies;
determining new dependencies needed for the new element based on the combined dependencies, the new dependencies comprising at least one intangible dependency; and
generating metadata for the new element to include each of the common dependencies and each of the new dependencies.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments of the invention provide systems and methods for generating metadata describing dependencies for composable elements. The method includes maintaining a database of composable elements. Each composable element may have associated metadata to describe dependencies for the composable elements. The method may further include receiving a request to compose two or more of the composable elements into a new element. The method may then compare the dependencies of the two or more composable elements in order to determine dependencies common to the two or more composable elements and unique to the two or more composable elements. Further, the method may determine a level of restriction for each of the common dependencies and generate metadata for the new element to include each of the unique dependencies and each of the common dependencies, wherein the common dependencies are set to the highest level of restriction.
-
Citations
20 Claims
-
1. A method of generating, maintaining, combining, and storing metadata which describe dependencies for composable elements, the method comprising:
-
maintaining a database describing information about a plurality of composable elements, wherein each of the plurality of composable elements has associated metadata to describe dependencies for each of the plurality of composable elements, wherein the metadata describes both tangible dependencies known to a developer of the composable element at compile time of that composable element and intangible dependencies that are unknown to the developer of the composable element at compile time of that composable element, and wherein each of the composable elements include one or more of;
a combination, a reprogramming, or a repurposing of software components and/or services;receiving a request to compose, modify, update, re-program, or re-purpose two or more of the plurality of composable elements into a new element; determining common dependencies among the two or more composable elements; determining redundant dependencies among the two or more composable elements; combining the dependencies to include each of any redundant dependencies from the combined components as well as any dependencies unique to each of the combined components or services, and any dependency that is common to more than one, then the more restrictive component dependency is utilized within the new element, wherein each dependency includes an associated level of dependency value and the higher the level of dependency value the more restrictive the dependency, and wherein the determination of the utilization of the common dependency is determined based on each of the levels of dependency of the common dependencies; determining new dependencies needed for the new element based on the combined dependencies, the new dependencies comprising at least one intangible dependency; and generating metadata for the new element to include each of the common dependencies and each of the new dependencies. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A system for generating, maintaining, combining, and storing metadata which describe dependencies for composable elements, the system comprising:
-
a memory device; and a computer processor in communication with the memory device, wherein the memory device has sets of instructions stored therein which, when executed by the computer processor, cause the computer processor to; store at a database a plurality of composable elements, wherein each of the plurality of composable elements has associated metadata to describe dependencies for each of the plurality of composable elements, wherein the metadata describes both tangible dependencies known to a developer of the composable element at compile time of that composable element and intangible dependencies that are unknown to the developer of the composable element at compile time of that composable element, and wherein the composable elements includes one or more of;
a combination, a reprogramming, or a repurposing of software components and/or services; andreceive at an Operations Support System/Business Support System (OSS/BSS) coupled with the database a request to compose two or more of the plurality of composable elements into a new element, compare dependencies of the two or more of the plurality of composable elements in order to determine dependencies common to the two or more of the plurality of composable elements and unique to the two or more of the plurality of composable elements, determine redundant dependencies among the two or more composable elements, combine the dependencies to include each of any redundant dependencies from the combined components as well as any dependencies unique to each of the combined components or services, and any dependency that is common to more than one, then the more restrictive component dependency is utilized within the new element, determining new dependencies needed for the new element based on the combined dependencies, the new dependencies comprising at least one intangible dependency, and generate metadata for the new element to include each of the unique dependencies and each of the common dependencies, wherein each dependency includes an associated level of dependency value and the higher the level of dependency value the more restrictive the dependency, and wherein the determination of the utilization of the common dependency is determined based on each of the levels of dependency of the common dependencies. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
14. A non-transitory machine-readable medium for generating, maintaining, combining, and storing metadata which describe dependencies for composable elements which, when executed by a machine, causes the machine to:
-
maintain a database describing information about a plurality of composable elements, wherein each of the plurality of composable elements has associated metadata to describe dependencies for each of the plurality of composable elements, wherein the metadata describes both tangible dependencies known to a developer of the composable element at compile time of that composable element and intangible dependencies that are unknown to the developer of the composable element at compile time of that composable element, and wherein the composable elements include one or more of;
a combination, a reprogramming, or a repurposing of software components and/or services;receive a request to compose, modify, update, reprogram, or repurpose two or more of the plurality of composable elements into a new element; determine common dependencies among the two or more composable elements; determine redundant dependencies among the two or more composable elements; combine the dependencies to include each of any redundant dependencies from the combined components as well as any dependencies unique to each of the combined components or services, and any dependency that is common to more than one, then the more restrictive component dependency is utilized within the new element, wherein each dependency includes an associated level of dependency value and the higher the level of dependency value the more restrictive the dependency, and wherein the determination of the utilization of the common dependency is determined based on each of the levels of dependency of the common dependencies; determine new dependencies needed for the new element based on the combined dependencies, the new dependencies comprising at least one intangible dependency; and generate metadata for the new element to include each of the common dependencies and each of the new dependencies. - View Dependent Claims (15, 16, 17, 18, 19, 20)
-
Specification