IP Library Granted Patent US 12,327,097
Granted Patent B2
US 12,327,097 · App. 18/430,529 · Granted Jun 10, 2025

Dependency management in software development

Inventor: Nate Shepherd (Bloomington, IL)
Assignee: State Farm Mutual Automobile Insurance Company
G06F8/433G06F8/10G06F8/75
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,327,097
App. No.
18/430,529
Granted
Jun 10, 2025
Kind
B2
Abstract

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.

Claims (103)

1. A computer-implemented method, comprising:

maintaining, by a software project management system, a plurality of dependency data objects that respectively represent dependency relationships between components of a software development project, wherein:

the plurality of dependency data objects are distinct from component data objects, maintained by the software project management system, that respectively represent the components of the software development project, and

an individual dependency data object of the plurality of dependency data objects;

represents an individual dependency relationship between two or more of the components of the software development project;

identifies the component data objects that represent the two or more of the components; and

comprises a state indicator that indicates a current state of the individual dependency relationship;

detecting, by the software project management system, changes to the dependency relationships over time;

automatically updating, by the software project management system, data stored in the plurality of dependency data objects based on the changes to the dependency relationships; and

displaying, by the software project management system, and based on the plurality of dependency data objects, information associated with one or more of the dependency relationships in a user interface,

wherein the information displayed in the user interface indicates current states of the one or more of the dependency relationships based on state indicators of the plurality of dependency data objects.

2. The computer-implemented method of claim 1 , wherein the information displayed via the user interface in association with a particular dependency relationship, based on a corresponding dependency data object of the plurality of dependency data objects, comprises one or more data types comprising at least one of:

a name of the particular dependency relationship,

a project identifier associated with the particular dependency relationship,

portfolio information associated with the particular dependency relationship,

an owner of the particular dependency relationship,

progress information associated with the particular dependency relationship, or

a date associated with the particular dependency relationship.

3. The computer-implemented method of claim 2 , wherein:

the user interface displays instances of the one or more data types associated with multiple dependency relationships, and

the information displayed via the user interface is at least one of filterable or sortable based on the one or more data types.

4. The computer-implemented method of claim 1 , wherein the user interface displays the information in association with at least one of:

program increments associated with the one or more of the dependency relationships, or

suppliers associated with the one or more of the dependency relationships.

5. The computer-implemented method of claim 1 , wherein the user interface displays visual representations of multiple dependency relationships, in association with multiple groups corresponding to multiple possible states of the dependency relationships, based on the state indicators of the plurality of dependency data objects.

6. The computer-implemented method of claim 5 , wherein at least one of the visual representations, associated with a particular dependency relationship, presents a warning indicator of an issue associated with the particular dependency relationship.

7. The computer-implemented method of claim 1 , wherein:

the user interface displays visual representations of:

the components, and

the dependency relationships between the components, and

the visual representations are associated with corresponding program increments.

8. The computer-implemented method of claim 1 , wherein the information displayed via the user interface:

comprises one or more data types, and

is displayed as a timeline representation of instances of the one or more data types, associated with at least one of the dependency relationships, based on date information indicated by the plurality of dependency data objects.

9. The computer-implemented method of claim 1 , wherein the changes include at least one of:

a changed date associated with a dependency relationship,

a changed state of the dependency relationship, or

a division of a component associated with the dependency relationship into multiple components.

10. The computer-implemented method of claim 1 , further comprising:

identifying, by the software project management system, types of the changes, and

sending, by the software project management system, notifications of the changes to entities, identified by the plurality of dependency data objects, associated with the types of the changes.

11. A computing system, comprising:

one or more processors; and

memory storing computer-executable instructions that, when executed by the one or more processors, cause the computing system to:

maintain a plurality of dependency data objects in association with a software project management system, wherein:

the plurality of dependency data objects represent dependency relationships between components of a software development project,

the plurality of dependency data objects are distinct from component data objects, maintained by the software project management system, that respectively represent the components of the software development project, and

an individual dependency data object of the plurality of dependency data objects:

represents an individual dependency relationship between two or more of the components of the software development project;

identifies the component data objects that represent the two or more of the components; and

comprises a state indicator that indicates a current state of the individual dependency relationship;

detect changes to the dependency relationships over time;

automatically update data stored in the plurality of dependency data objects, based on the changes to the dependency relationships; and

display, based on the plurality of dependency data objects, information associated with one or more of the dependency relationships in a user interface associated with the software project management system,

wherein the information displayed in the user interface indicates current states of the one or more of the dependency relationships based on state indicators of the plurality of dependency data objects.

12. The computing system of claim 11 , wherein the information displayed via the user interface in association with a particular dependency relationship, based on a corresponding dependency data object of the plurality of dependency data objects, comprises one or more data types comprising at least one of:

a name of the particular dependency relationship,

a project identifier associated with the particular dependency relationship,

portfolio information associated with the particular dependency relationship,

an owner of the particular dependency relationship,

progress information associated with the particular dependency relationship, or

a date associated with the particular dependency relationship.

13. The computing system of claim 11 , wherein the user interface displays the information in association with at least one of:

program increments associated with the one or more of the dependency relationships, or

suppliers associated with the one or more of the dependency relationships.

14. The computing system of claim 11 , wherein the user interface displays visual representations of multiple dependency relationships, in association with multiple groups corresponding to multiple possible states of the dependency relationships, based on the state indicators of the plurality of dependency data objects.

15. The computing system of claim 11 , wherein the computer-executable instructions further cause the computing system to:

identify types of the changes, and

send notifications of the changes to entities, identified by the plurality of dependency data objects, associated with the types of the changes.

16. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to:

maintain a plurality of dependency data objects in association with a software project management system, wherein:

the plurality of dependency data objects represent dependency relationships between components of a software development project,

the plurality of dependency data objects are distinct from component data objects, maintained by the software project management system, that respectively represent the components of the software development project, and

an individual dependency data object of the plurality of dependency data objects:

represents an individual dependency relationship between two or more of the components of the software development project;

identifies the component data objects that represent the two or more of the components; and

comprises a state indicator that indicates a current state of the individual dependency relationship;

detect changes to the dependency relationships over time;

automatically update data stored in the plurality of dependency data objects, based on the changes to the dependency relationships; and

display, based on the plurality of dependency data objects, information associated with one or more of the dependency relationships in a user interface associated with the software project management system,

wherein the information displayed in the user interface indicates current states of the one or more of the dependency relationships based on state indicators of the plurality of dependency data objects.

17. The one or more non-transitory computer-readable media of claim 16 , wherein the information displayed via the user interface in association with a particular dependency relationship, based on a corresponding dependency data object of the plurality of dependency data objects, comprises one or more data types comprising at least one of:

a name of the particular dependency relationship,

a project identifier associated with the particular dependency relationship,

portfolio information associated with the particular dependency relationship,

an owner of the particular dependency relationship,

progress information associated with the particular dependency relationship, or

a date associated with the particular dependency relationship.

18. The one or more non-transitory computer-readable media of claim 16 , wherein the user interface displays the information in association with at least one of:

program increments associated with the one or more of the dependency relationships.

19. The one or more non-transitory computer-readable media of claim 16 , wherein the user interface displays visual representations of multiple dependency relationships, in association with multiple groups corresponding to multiple possible states of the dependency relationships, based on the state indicators of the plurality of dependency data objects.

20. A system, comprising:

means for maintaining a plurality of dependency data objects in association with a software project management system, wherein:

the plurality of dependency data objects represent dependency relationships between components of a software development project,

the plurality of dependency data objects are distinct from component data objects, maintained by the software project management system, that respectively represent the components of the software development project, and

an individual dependency data object of the plurality of dependency data objects:

represents an individual dependency relationship between two or more of the components of the software development project;

identifies the component data objects that represent the two or more of the components; and

comprises a state indicator that indicates a current state of the individual dependency relationship;

means for detecting changes to the dependency relationships over time;

means for automatically updating data stored in the plurality of dependency data objects, based on the changes to the dependency relationships; and

means for displaying, based on the plurality of dependency data objects, information associated with one or more of the dependency relationships in a user interface associated with the software project management system,

wherein the information displayed in the user interface indicates current states of the one or more of the dependency relationships based on state indicators of the plurality of dependency data objects.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 15, 2024
From: SHEPHERD, NATE
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 068904/0784 →
Continuity (4)
Continuation 17853702 · Jun 29, 2022
Continuation 17025460 · Sep 18, 2020
Provisional Application 62902323 · Sep 18, 2019
Related Publication 20240176602A1 · May 30, 2024
References Cited (52)
US 8370803B1 · Holler et al. · 2013 [cited by applicant]
US 8813040B2 · Holler et al. · 2014 [cited by applicant]
US 9092575B2 · Koenig et al. · 2015 [cited by applicant]
US 10049337B2 · Mack et al. · 2018 [cited by applicant]
US 10083412B2 · Suntinger et al. · 2018 [cited by applicant]
US 10248387B2 · Bharthulwar · 2019 [cited by applicant]
US 10372421B2 · Mack et al. · 2019 [cited by applicant]
US 10452521B2 · Kaulgud et al. · 2019 [cited by applicant]
US 10540573B1 · Li et al. · 2020 [cited by applicant]
US 10719336B1 · Tsybulnyk · 2020 [cited by examiner]
US 10901731B2 · Adams et al. · 2021 [cited by applicant]
US 11093227B1 · Shteyman et al. · 2021 [cited by applicant]
US 11366833B2 · Garg et al. · 2022 [cited by applicant]
US 11592979B2 · Allington et al. · 2023 [cited by applicant]
US 20110289474A1 · Sukhenko · 2011 [cited by examiner]
US 20130152039A1 · Kemmler · 2013 [cited by applicant]
US 20140359555A1 · Holler et al. · 2014 [cited by applicant]
US 20150234801A1 · Michaels et al. · 2015 [cited by applicant]
US 20170061348A1 · Mack et al. · 2017 [cited by applicant]
US 20170083290A1 · Bharthulwar · 2017 [cited by examiner]
US 20170124499A1 · Gura et al. · 2017 [cited by applicant]
US 20180068271A1 · Abebe et al. · 2018 [cited by applicant]
US 20180075412A1 · Mandava · 2018 [cited by applicant]
US 20180365628A1 · Bhaskaran · 2018 [cited by applicant]
US 20190050771A1 · Meharwade et al. · 2019 [cited by applicant]
US 20190129701A1 · Hawrylo · 2019 [cited by applicant]
US 20190243644A1 · Jose · 2019 [cited by examiner]
US 20190278592A1 · Bansal · 2019 [cited by examiner]
US 20200159525A1 · Bhalla et al. · 2020 [cited by applicant]
US 20200159950A1 · Bodin et al. · 2020 [cited by applicant]
US 20200210934A1 · Bar-on et al. · 2020 [cited by applicant]
US 20200272554A1 · Sneed et al. · 2020 [cited by applicant]
US 20210011698A1 · Bond et al. · 2021 [cited by applicant]
US 20210089333A1 · Kodmad · 2021 [cited by applicant]
US 20210117907A1 · Gray · 2021 [cited by examiner]
US 20210157715A1 · Hand · 2021 [cited by examiner]
US 20210256453A1 · Morgan et al. · 2021 [cited by applicant]
US 20210397426A1 · Du · 2021 [cited by applicant]
US 20220006706A1 · Patodia et al. · 2022 [cited by applicant]
US 20220237108A1 · Jain et al. · 2022 [cited by applicant]
US 20220334813A1 · Shepherd · 2022 [cited by applicant]
US 20220334837A1 · Sa et al. · 2022 [cited by applicant]
CN 115016832B · 2022 [cited by applicant]
WO WO2017001417 · 2017 [cited by applicant]
Dimitrijevic, et al., “A comparative study of software tools for user story management”, Information and Software Technology 57, 2015, pp. 352-368. [cited by applicant]
Gayer, et al., “Computing Practices—Lightweight Traceability for the Agile Architect”, Computer Society IEEE, 2016, 8 pgs. [cited by applicant]
Mihalache, “Project Management Tools for Agile Teams”, Faculty of Cybernetics, Statistics and Economic Studies, Romania—Informatica Economica vol. 21, No. Apr. 2017, pp. 85-93. [cited by applicant]
Office Action for U.S. Appl. No. 17/025,460, mailed on Feb. 17, 2022, Sheperd, “Dependency Management in Software Development”, 14 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/025,460, mailed on Aug. 19, 2021, Sheperd, “Dependency Management in Software Development”, 11 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/853,702, mailed on Jun. 13, 2023, Shepherd, “Dependency Management in Software Development”, 14 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/853,702, mailed on Dec. 22, 2022, Sheperd, “Dependency Management in Software Development”, 13 Pages. [cited by applicant]
Silhavy et al., “Cybernetics Approaches in Intelligent Systems”, Advances in Intelligent Systems and Computing 661—Computational Methods in Systems and Software 2017, vol. 1, 405 pgs. [cited by applicant]