Abstract: Systems and methods to autonomously generate emergent software delivery value stream graphs from work units (e.g., tasks) that are created and managed through different specialized software tools by the many teams of an entity (e.g., company, other organization) involved in large software delivery activities. The emergent software delivery value stream graphs may be produced by autonomously monitoring and integrating the activity from individual software development tools. Additionally or alternatively, emergent software delivery value stream graphs may be produced by altering a previously captured event stream based on a description of changes to a development stage stream and team information. The generated value streams may be analyzed and/or visualized to report on various aspects of the software development for an organization.

Abstract: A system for synchronizing states in associated for data records has been developed. The system includes a first data repository (R1) containing a first data record (DR1) and a second data repository (R2) containing a second data record (DR2). The system also includes a synchronizer that initiates synchronization activity between DR1 and DR2. Upon change in DR1, the system generates a listing of all possible target states for DR2 and determines the correct target state of DR2 from the listing of possible target states. The system then determines if DR2 is in the correct target state. If not, the system transitions DR2 to the correct target state, and synchronizes the data of DR2 with DR1.

Abstract: Systems and methods synchronize artifact relationships across a plurality of repositories. One example method includes mapping a first relationship of a first relationship type between a first source artifact in a first repository and a second source artifact to a second relationship of a second relationship type between a first target artifact in a second repository and a second target artifact according to a relationship mapping provided by a schema mapping guide. One example system includes a repository synchronizer to synchronize artifact relationship across at least first and second repositories. The repository synchronizer can include at least one processor. The example system can further include one or more schema mapping guides that provide one or more relationship mappings between the first and second repositories.

Abstract: A system for detecting and repairing errors in synchronization links for data records includes a first data repository containing a first data record that maintains a data field which links to associated data records) and a self-reference record. The system also includes a second data repository containing a second data record that also maintains a data field which links to associated data records) and a self-reference record. The system also includes a synchronizer that maintains a data table containing the addresses of the first and second data records and the status of any previous synchronization activity.