Adaptive Workflows Derived From Updates to Solution Building Block Architectures and Designs
Abstract
Provided is a method for the adaptive testing, updating and verification of a building block architecture and design, such as a solution building block (SBB) architecture design, in the event of a change to the building block architecture and or a component of the architecture. Typically, an on-demand, custom solution to a user or business's computing needs has a specific architecture and a common metadata definition that defines attributes and dependencies among components. When a specific, or target, component of the architecture, or SBB, is replaced or modified, the metadata associated with the new or modified component is placed in a building block repository. The system captures or recognizes the event and automatically generates workflows that enable a user to test, validate, implement and, if necessary, make additional changes to the architecture.
Claims
exact text as granted — not AI-modified1 . A method, comprising:
detecting a modification to metadata, stored in a building block repository, associated with a first computing component incorporated into a computing solution; generating a second computing component based upon the detected modification to the metadata; storing the second computing component in the building block repository; updating the computing solution, the updating comprising replacing the first computing component with the second computing component; generating a workflow scenario to test the updated computing solution; and executing the workflow scenario.
2 . The method of claim 1 , further comprising:
identifying an actor to execute the workflow scenario; and transmitting the workflow scenario to the identified actor for execution.
3 . The method of claim 2 , wherein the identified actor is an individual user with responsibilities corresponding to the workflow scenario.
4 . The method of claim 2 , wherein the identified actor is an automated system responsible for executing actions corresponding to the workflow scenario.
5 . The method of claim 1 , further comprising transmitting a report corresponding to the execution of the workflow scenario.
6 . The method of claim 5 , further comprising:
generating a third computing component corresponding to the second computing component if the transmitted report indicates that the computing solution is not meeting expectations in conjunction with the second computing component; storing the third computing component in the building block repository; updating the computing solution by replacing the second computing component with the third computing component; generating a second workflow scenario to test the second updated computing solution; and executing the second workflow scenario.
7 . The method of claim 5 , further comprising repeating the generating, storing updating, executing and transmitting with respect to additional computing solutions, workflow scenarios and reports as long as an additional transmitted report indicates that the computing solution is not meeting expectations in conjunction with a corresponding additional component.
8 . A system, comprising:
a processor; memory coupled to the processor; and logic, stored on the memory for execution on the processor, for:
detecting a modification to metadata, stored in a building block repository, associated with a first computing component incorporated into a computing solution;
generating a second computing component based upon the detected modification to the metadata;
storing the second computing component in the building block repository;
updating the computing solution, the updating comprising replacing the first computing component with the second computing component;
generating a workflow scenario to test the updated computing solution; and
executing the workflow scenario.
9 . The system of claim 8 , further comprising logic, stored on the memory for execution on the processor, for:
identifying an actor to execute the workflow scenario; and transmitting the workflow scenario to the identified actor for execution.
10 . The system of claim 9 , wherein the identified actor is an individual user with responsibilities corresponding to the workflow scenario.
11 . The system of claim 9 , wherein the identified actor is an automated system responsible for executing actions corresponding to the workflow scenario.
12 . The system of claim 8 , further comprising logic, stored on the memory for execution on the processor, for: transmitting a report corresponding to the execution of the workflow scenario.
13 . The system of claim 12 , further comprising logic, stored on the memory for execution on the processor, for:
generating a third computing component corresponding to the second computing component if the transmitted report indicates that the computing solution is not meeting expectations in conjunction with the second computing component; storing the third computing component in the building block repository; updating the computing solution by replacing the second computing component with the third computing component; generating a second workflow scenario to test the second updated computing solution; and executing the second workflow scenario.
14 . The method of claim 12 , further comprising logic, stored on the memory for execution on the processor, for repeating the generating, storing updating, executing and transmitting with respect to additional computing solutions, workflow scenarios and reports as long as an additional transmitted report indicates that the computing solution is not meeting expectations in conjunction with a corresponding additional component.
15 . A computer programming product, comprising:
a memory; and logic, stored on the memory for execution on a processor, for:
detecting a modification to metadata, stored in a building block repository, associated with a first computing component incorporated into a computing solution;
generating a second computing component based upon the detected modification to the metadata;
storing the second computing component in the building block repository;
updating the computing solution, the updating comprising replacing the first computing component with the second computing component;
generating a workflow scenario to test the updated computing solution; and
executing the workflow scenario.
16 . The computer programming product of claim 15 , further comprising logic, stored on the memory for execution on the processor, for:
identifying an actor to execute the workflow scenario; and transmitting the workflow scenario to the identified actor for execution.
17 . The computer programming product of claim 16 , wherein the identified actor is an individual user with responsibilities corresponding to the workflow scenario.
18 . The computer programming product of claim 15 , further comprising logic, stored on the memory for execution on the processor, for: transmitting a report corresponding to the execution of the workflow scenario.
19 . The system of claim 18 , further comprising logic, stored on the memory for execution on the processor, for:
generating a third computing component corresponding to the second computing component if the transmitted report indicates that the computing solution is not meeting expectations in conjunction with the second computing component; storing the third computing component in the building block repository; updating the computing solution by replacing the second computing component with the third computing component; generating a second workflow scenario to test the second updated computing solution; and executing the second workflow scenario.
20 . The method of claim 18 , further comprising logic, stored on the memory for execution on the processor, for repeating the generating, storing updating, executing and transmitting with respect to additional computing solutions, workflow scenarios and reports as long as an additional transmitted report indicates that the computing solution is not meeting expectations in conjunction with a corresponding additional component.Join the waitlist — get patent alerts
Track US2009276458A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.