US 12,112,160 B1Granted

Systems and methods providing centralized communication across feature programming workflows

AssigneeCitibank, N.A.

InventorsLaura McNeil, Muthukumar Arunachalam, Srikanth Bezawada, Prag Sharma

Life of this patent

Estimating the term…

Loading patent…

Abstract

Systems and methods that provide centralized communication across feature programming workflows using software development lifecycle tools that dynamically determine temporal alerts are disclosed herein. By dynamically determining events that are temporally relevant, the system accounts for changes in an application timeline that comprises a plurality of events, in which each event of the plurality of events indicates when a respective feature of the plurality of features is available for use by the application, and in which the location of each event constantly changes.

Claims20

Dependent claims

A system for providing centralized communication across feature programming workflows using software development lifecycle tools that dynamically determine temporal alerts, the system comprising:

one or more processors;
and
a non-transitory, computer readable medium comprising instructions that when executed by the one or more processors cause operations comprising:
determining a software programming workflow, wherein the software programming workflow corresponds to production of an application comprising a plurality of features;
determining a first feature programming workflow, wherein the first feature programming workflow corresponds to production of a first feature of the plurality of features;
receiving a first output from one or more artificial intelligence models based on the software programming workflow and the first feature programming workflow, wherein the one or more artificial intelligence models have been trained on historic compliance data for historic event data;
determining a current status of the software programming workflow based on the first output;
determining a first location, in an application timeline, of a first event of a plurality of events, and a second location, in the application timeline, of a second event, in the plurality of events, based on the current status of the software programming workflow, wherein the first event indicates the first feature programming workflow is completed, wherein the second event indicates that a second feature programming workflow is completed, and wherein the current status is further based on a second output of the one or more artificial intelligence models;
determining a number of dependencies between the first feature programming workflow and the second feature programming workflow;
comparing the number of dependencies to a threshold number of dependencies;
in response to the number of dependencies exceeding the threshold number of dependencies, retrieving a threshold proximity for the second feature programming workflow, wherein the threshold proximity is based on a status of the second feature programming workflow;
and
determining that the second event of the plurality of events that is within the threshold proximity on the application timeline, wherein the second feature programming workflow corresponds to production of a second feature of the plurality of features.

10 more elements

A method for providing centralized communication across feature programming workflows using software development lifecycle tools that dynamically determine temporal alerts, the method comprising:

determining a software programming workflow, wherein the software programming workflow corresponds to production of an application comprising a plurality of features;
determining a first feature programming workflow, wherein the first feature programming workflow corresponds to production of a first feature of the plurality of features;
receiving a first output from one or more artificial intelligence models based on the software programming workflow and the first feature programming workflow, wherein the one or more artificial intelligence models have been trained on historic compliance data for historic event data;
determining a current status of the software programming workflow based on the first output;
determining a first location, in an application timeline, of a first event, in a plurality of events, and a second location, in the application timeline, of a second event, in the plurality of events, based on the current status of the software programming workflow, wherein the first event indicates the first feature programming workflow is completed, and wherein the second event indicates that a second feature programming workflow is completed;
determining a number of dependencies between the first feature programming workflow and the second feature programming workflow;
comparing the number of dependencies to a threshold number of dependencies;
in response to the number of dependencies exceeding the threshold number of dependencies, retrieving a threshold proximity for the second feature programming workflow, wherein the threshold proximity is based on a status of the second feature programming workflow;
determining that the second event is within the threshold proximity;
and
generating for display, on a user interface, a software development lifecycle tool status for the second feature programming workflow.

8 more elements

A non-transitory, computer readable medium comprising instructions that when executed by one or more processors cause operations comprising:

determining a software programming workflow, wherein the software programming workflow corresponds to production of an application comprising a plurality of features;
determining a first feature programming workflow, wherein the first feature programming workflow corresponds to production of a first feature of the plurality of features;
receiving a first output from one or more artificial intelligence models based on the software programming workflow and the first feature programming workflow, wherein the one or more artificial intelligence models have been trained on historic compliance data for historic event data;
determining a current status of the software programming workflow based on the first output;
determining a first location, in an application timeline, of a first event, in a plurality of events, and a second location, in the application timeline, of a second event, in the plurality of events, based on the current status of the software programming workflow, wherein the first event indicates the first feature programming workflow is completed, and wherein the second event indicates that a second feature programming workflow is completed;
determining a number of dependencies between the first feature programming workflow and the second feature programming workflow;
comparing the number of dependencies to a threshold number of dependencies;
in response to the number of dependencies exceeding the threshold number of dependencies, retrieving a threshold proximity for the second feature programming workflow, wherein the threshold proximity is based on a status of the second feature programming workflow;
determining that the second event is within the threshold proximity;
and
generating for display, on a user interface, a software development lifecycle tool status for the second feature programming workflow.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 18/474,162Filed 25 Sep 2023 · continuation
Priority: 30 Jun 2023
Granted: 8 Oct 2024
Term ends: Not estimatedThe source records don’t support an estimate.

Classification3 codes

G06F 8/70
Arrangements for software engineering: software maintenance or management
G06F 8/71
Software maintenance or management: version control ; Configuration management
G06F
Computing and data processing

Family

Application18/345,417Parent of this continuation · filed 30 Jun 2023
US 11,803,369 B1Parent of this continuation
US 12,112,160 B1This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key