Parallel Processing Of Data
US-2024338235-A1 · Oct 10, 2024 · US
US2025265057A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2025265057-A1 |
| Application number | US-202519201749-A |
| Country | US |
| Kind code | A1 |
| Filing date | May 7, 2025 |
| Priority date | Sep 18, 2019 |
| Publication date | Aug 21, 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 software project management system can store object data about components of a software development project, such epics, features, and stories. The software project management system can also store dependency objects that reflect dependency relationships between two or more components of the software development project. The dependency objects can track status information about the dependency relationships, including expected completion dates, acceptance criteria, and state indicators. The information stored in the dependency objects can be updated over time as information about the dependency relationship changes. The software project management system can also use the dependency objects to display information in a user interface about one or more dependency relationships, such as to indicate which dependency relationships are on track or behind schedule.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method, comprising: maintaining, by a software project management system executed by a computing system, a plurality of dependency data objects that respectively represent corresponding dependency relationships between components of a software development project, wherein: the software project management system maintains component data objects, different from the plurality of dependency data objects, that respectively represent the components of the software development project, and the plurality of dependency data objects respectively identify the component data objects that represent the components associated with the corresponding dependency relationships; detecting, by the software project management system, a change to a dependency relationship represented by a particular dependency data object; automatically updating, by the software project management system, the particular dependency data object based on the change to the dependency relationship; and performing, by the software project management system, an action triggered based at least in part on updating of the particular dependency data object based on the change. 2 . The computer-implemented method of claim 1 , wherein the software project management system determines an action type, of the action, based at least in part on a type of the change or an update made to the particular dependency data object based on the change. 3 . The computer-implemented method of claim 1 , wherein the action comprises sending a notification to at least one entity associated with the dependency relationship. 4 . The computer-implemented method of claim 3 , further comprising identifying, by the software project management system, the at least one entity based on a type of the change or an update made to the particular dependency data object based on the change. 5 . The computer-implemented method of claim 3 , further comprising determining, by the software project management system, a notification type of the notification based on a type of the change or an update made to the particular dependency data object based on the change. 6 . The computer-implemented method of claim 3 , wherein the notification indicates at least one of the change to the dependency relationship or one or more corresponding updates made to the particular dependency data object. 7 . The computer-implemented method of claim 1 , wherein: the action comprises creating or updating a second dependency data object of the plurality of dependency data objects, and the second dependency data object is associated with a second dependency relationship that is impacted by the change to the dependency relationship. 8 . The computer-implemented method of claim 1 , wherein the action comprises displaying, via the software project management system, a prompt for a user to perform a user action based on the change. 9 . The computer-implemented method of claim 1 , wherein the action comprises updating information associated with the dependency relationship, displayed in a user interface of the software project management system, based on updating of the particular dependency data object. 10 . The computer-implemented method of claim 1 , wherein the change is associated with at least one of a state of the dependency relationship, a date associated with the dependency relationship, or the components of the software development project that are associated with the dependency relationship. 11 . A computing system, comprising: one or more processors; and memory storing computer-executable instructions associated with a software project management system that, when executed by the one or more processors, cause the software project management system to: maintain a plurality of dependency data objects that respectively represent corresponding dependency relationships between components of a software development project, wherein: the software project management system maintains component data objects, different from the plurality of dependency data objects, that respectively represent the components of the software development project, and the plurality of dependency data objects respectively identify the component data objects that represent the components associated with the corresponding dependency relationships; detect a change to a dependency relationship represented by a particular dependency data object; automatically update the particular dependency data object based on the change to the dependency relationship; and perform an action triggered based at least in part on updating of the particular dependency data object based on the change. 12 . The computing system of claim 11 , wherein the software project management system determines an action type, of the action, based at least in part on a type of the change or an update made to the particular dependency data object based on the change. 13 . The computing system of claim 11 , wherein the action comprises sending a notification to at least one entity associated with the dependency relationship. 14 . The computing system of claim 11 , wherein: the action comprises creating or updating a second dependency data object of the plurality of dependency data objects, and the second dependency data object is associated with a second dependency relationship that is impacted by the change to the dependency relationship. 15 . The computing system of claim 11 , wherein the action comprises updating information associated with the dependency relationship, displayed in a user interface of the software project management system, based on updating of the particular dependency data object. 16 . One or more non-transitory computer-readable media storing computer-executable instructions associated with a software project management system that, when executed by one or more processors, cause the software project management system to: maintain a plurality of dependency data objects that respectively represent corresponding dependency relationships between components of a software development project, wherein: the software project management system maintains component data objects, different from the plurality of dependency data objects, that respectively represent the components of the software development project, and the plurality of dependency data objects respectively identify the component data objects that represent the components associated with the corresponding dependency relationships; detect a change to a dependency relationship represented by a particular dependency data object; automatically update the particular dependency data object based on the change to the dependency relationship; and perform an action triggered based at least in part on updating of the particular dependency data object based on the change. 17 . The one or more non-transitory computer-readable media of claim 16 , wherein the software project management system determines an action type, of the action, based at least in part on a type of the change or an update made to the particular dependency data object based on the change. 18 . The one or more non-transitory computer-readable media of claim 16 , wherein the action comprises sending a notification to at least one entity associated with the dependency relationship. 19 . The one or more non-transitory computer-readable media of claim 16 , wherein: the action comprises creating or updating a second dependency data object of the plurality of dependency data objects
Requirements analysis; Specification techniques · CPC title
Structural analysis for program understanding · CPC title
Workflow collaboration or project management · CPC title
Dependency analysis; Data or control flow analysis · CPC title
Resource planning, allocation, distributing or scheduling for enterprises or organisations · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.