# US 2025/0165249 A1 · System and method for centralized application development and pipeline management via event data streaming > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0165249 A1 - Document ID: US20250165249A1 - Status: Published application - Kind: A1 - Application number: 18/515,606 - Filed: 2023-11-21 - Published: 2025-05-22 - Earliest claimed: 2023-11-21 - Assignees: Bank of America Corporation - Applicants: Bank of America Corporation - Inventors: Lauderdale Sonnenberg Young; Peter Tavormina; Suresh Velagaleti - Web page: https://patentgrep.com/patent/US20250165249A1 ## CPC - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems, computer program products, and methods are described herein for centralized application development and pipeline management via event data streaming. The present disclosure embraces event data received from discrete components of an application development pipeline platform. The event data is received directly, via webhooks, or via change data capture. The event data is analyzed to determine conformity to a standardized data structure. If the discrete components already transmit and receive event data in the standardized data structure, the application development pipeline platform communicates with such discrete components directly. If the discrete components don't transmit and receive event data in the standardized data, a middleware layer receives the event data from the discrete components and transforms the event data from the discrete components to the standardized data structure. ## Claims ### Claim 1 A system for centralized application development and pipeline management via event data streaming, the system comprising: a processing device; a non-transitory storage device containing instructions when executed by the processing device, causes the processing device to perform the steps of: receiving event data from at least one discrete component of an application development pipeline platform, each discrete component operating independently and subject to its own development cycle; analyzing the event data to determine conformity to a standardized data structure; automatically generating an update signal whenever the event data from the at least one discrete component is received; and transmitting, based on the update signal, a display signal to display a pipeline progress on a graphical dashboard of a user interface, wherein the pipeline progress comprises the event data. ### Claim 2 (depends on 1) The system of claim 1, wherein the at least one discrete component transmits and receives event data in the standardized data structure. ### Claim 3 (depends on 1) The system of claim 1, wherein executing the instructions further causes the processing device to perform the steps of: receiving, at an adaptive middleware layer, the event data from the at least one discrete component, wherein the at least one discrete component transmits and receives event data in a non-standardized data structure; and converting, via the adaptive middleware layer, the event data from the at least one discrete component to the standardized data structure. ### Claim 4 (depends on 1) The system of claim 1, wherein receiving the event data from the at least one discrete component comprises receiving the event data via receiving the event data directly. ### Claim 5 (depends on 1) The system of claim 1, wherein receiving the event data from the at least one discrete component comprises receiving the event data via webhooks. ### Claim 6 (depends on 1) The system of claim 1, wherein receiving the event data from the at least one discrete component comprises receiving the event data via change data capture. ### Claim 7 (depends on 1) The system of claim 1, wherein the event data is an output of at least one selected from a group consisting of: version control, security, scanning, load testing, code review, and functional testing. ### Claim 8 A computer program product for centralized application development and pipeline management via event data streaming, the computer program product comprising a non-transitory computer-readable medium comprising code causing an apparatus to: receive event data from at least one discrete component of an application development pipeline platform, each discrete component operating independently and subject to its own development cycle; analyze the event data to determine conformity to a standardized data structure; automatically generate an update signal whenever the event data from the at least one discrete component is received; and transmit, based on the update signal, a display signal to display a pipeline progress on a graphical dashboard of a user interface, wherein the pipeline progress comprises the event data. ### Claim 9 (depends on 8) The computer program product of claim 8, wherein the at least one discrete component transmits and receives event data in the standardized data structure. ### Claim 10 (depends on 8) The computer program product of claim 8, wherein the code further causes the apparatus to: receive, at an adaptive middleware layer, the event data from the at least one discrete component, wherein the at least one discrete component transmits and receives event data in a non-standardized data structure; and convert, via the adaptive middleware layer, the event data from the at least one discrete component to the standardized data structure. ### Claim 11 (depends on 8) The computer program product of claim 8, wherein receiving the event data from the at least one discrete component comprises receiving the event data via receiving the event data directly. ### Claim 12 (depends on 8) The computer program product of claim 8, wherein receiving the event data from the at least one discrete component comprises receiving the event data via webhooks. ### Claim 13 (depends on 8) The computer program product of claim 8, wherein receiving the event data from the at least one discrete component comprises receiving the event data via change data capture. ### Claim 14 (depends on 8) The computer program product of claim 8, wherein the event data is an output of at least one selected from a group consisting of: version control, security, scanning, load testing, code review, and functional testing. ### Claim 15 A method for centralized application development and pipeline management via event data streaming, the method comprising: receiving event data from at least one discrete component of an application development pipeline platform, each discrete component operating independently and subject to its own development cycle; analyzing the event data to determine conformity to a standardized data structure; automatically generating an update signal whenever the event data from the at least one discrete component is received; and transmitting, based on the update signal, a display signal to display a pipeline progress on a graphical dashboard of a user interface, wherein the pipeline progress comprises the event data. ### Claim 16 (depends on 15) The method of claim 15, wherein the at least one discrete component transmits and receives event data in the standardized data structure. ### Claim 17 (depends on 15) The method of claim 15, further comprising: receiving, at an adaptive middleware layer, the event data from the at least one discrete component, wherein the at least one discrete component transmits and receives event data in a non-standardized data structure; and converting, via the adaptive middleware layer, the event data from the at least one discrete component to the standardized data structure. ### Claim 18 (depends on 15) The method of claim 15, wherein receiving the event data from the at least one discrete component comprises receiving the event data via webhooks. ### Claim 19 (depends on 15) The method of claim 15, wherein receiving the event data from the at least one discrete component comprises receiving the event data via change data capture. ### Claim 20 (depends on 15) The method of claim 15, wherein the event data is an output of at least one selected from a group consisting of: version control, security, scanning, load testing, code review, and functional testing.