Program code optimization using iterative application of machine learning model
US-2025156161-A1 · May 15, 2025 · US
US2025321725A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2025321725-A1 |
| Application number | US-202418631281-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 10, 2024 |
| Priority date | Apr 10, 2024 |
| Publication date | Oct 16, 2025 |
| Grant date | — |
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.
A data processing system includes a processor, and a memory storing executable instructions which, when executed by the processor, causes the processor, alone or in combination with other processors, to implement: a united data platform for extracting data from a software release pipeline for specific software; a software change insights module to generate insights into changes to the specific software on a per build basis using the extracted data; a deployment insights module to generate deployment insights using the extracted data; and a dashboard to organize the generated insights and intelligently route deployment of a build to upgrade the specific software based on the generated insights to expedite deployment.
Opening claim text (preview).
What is claimed is: 1 . A data processing system comprising: a processor, and a memory storing executable instructions which, when executed by the processor, causes the processor, alone or in combination with other processors, to implement: a united data platform for extracting data from a software release pipeline for specific software; a software change insights module to generate insights into changes to the specific software on a per build basis using the extracted data; a deployment insights module to generate deployment insights using the extracted data; and a dashboard to organize the generated insights and intelligently route deployment of a build to upgrade the specific software based on the generated insights. 2 . The data processing system of claim 1 , wherein the united data platform extracts data from a code source data repository, a build data store and a deployment data store in the software release pipeline. 3 . The data processing system of claim 1 , wherein the software change insights module identifies commits and pull requests with each build and extracts code changes for each pull request. 4 . The data processing system of claim 3 , wherein the software change insights module comprises a code summarization module to call a number of Large Language Models (LLMs) trained on programming code, the call comprising a prompt to summarize changes to the specific software based on the extracted code changes. 5 . The data processing system of claim 4 , wherein the number of LLMs comprises multiple LLMs, each LLM being trained on a different programming language. 6 . The data processing system of claim 1 , wherein the software change insights module comprises a pull request metrics engine to categorize a code change for each pull request in the software release pipeline. 7 . The data processing system of claim 6 , wherein the pull request metrics engine further categorizes a build approval for each build in the software release pipeline. 8 . The data processing system of claim 1 , wherein the software change insights module comprises a build insights dashboard to present a summarization of changes being made to the specific software by the software release pipeline as determined using a number of Large Language Models (LLMs) trained on programming code. 9 . The data processing system of claim 1 , wherein the deployment insights module extracts build, saturation and deployment metrics from the software release pipeline. 10 . The data processing system of claim 9 , wherein the deployment insights module further summarizes a deployment implemented by the software release pipeline using the extracted metrics. 11 . The data processing system of claim 10 , wherein the deployment insights module further categorizes the deployment by type. 12 . The data processing system of claim 11 , wherein the deployment insights module further comprises a deployment insights dashboard to present deployment insights based on the summarization and category of the deployment. 13 . The data processing system of claim 1 , further comprising an insights module to support the dashboard and to processing administrator queries for insights on a per build basis generated by the software change insights module and deployment insights module. 14 . The data processing system of claim 13 , wherein the insights module accepts administrator queries in natural language. 15 . A method comprising: extracting data from a software release pipeline for specific software; generating insights into changes to the specific software on a per build basis using the extracted data; generating deployment insights using the extracted data; and intelligently routing deployment of a build to upgrade the specific software based on the generated insights to expedite deployment. 16 . The method of claim 15 , further comprising extracting data from a code source data repository, a build data store and a deployment data store in the software release pipeline. 17 . The method of claim 15 , wherein the insights into changes to the specific software are generated by: identifying commits and pull requests with each build and extracting code changes for each pull request; calling a number of Large Language Models (LLMs) trained on programming code, the call comprising a prompt to summarize changes to the specific software based on the extracted code changes; categorizing a code change for each pull request in the software release pipeline; and implementing a build insights dashboard to present a summarization of changes being made to the specific software by the software release pipeline as determined using a number of Large Language Models (LLMs) trained on programming code. 18 . The method of claim 17 , wherein the number of LLMs comprises multiple LLMs, each LLM being trained on a different programming language. 19 . The method of claim 15 , wherein the deployment insights are generated by: extracting build, saturation and deployment metrics from the software release pipeline; summarizing a deployment implemented by the software release pipeline using the extracted metrics; categorizing the deployment by type; and implementing a deployment insights dashboard to present deployment insights based on the summarization and category of the deployment. 20 . A data processing system comprising: a processor, and a memory storing executable instructions which, when executed by the processor, causes the processor, alone or in combination with other processors, to implement: a united data platform for extracting data from a software release pipeline for specific software; a software change insights module to generate insights into changes to the specific software on a per build basis using the extracted data; a deployment insights module to generate deployment insights using the extracted data; and a dashboard to organize the generated insights and a database to provide the generated insights for software changes and deployments on a per build basis as queried by administrators of the software release pipeline.
Software deployment · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
Natural language analysis (semantic analysis of natural language G06F40/30) · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.